z/OS Communications Server: IP User's Guide and Commands
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


LMkdir subcommand—Create a directory on the local host

z/OS Communications Server: IP User's Guide and Commands
SC27-3662-00

Purpose

Use the LMkdir subcommand to create a PDS, PDSE, or z/OS® UNIX file system directory on the local host. This subcommand provides you with an easy way to create a directory in the local host for data transfer.

Format

Read syntax diagramSkip visual syntax diagram
>>-LMkdir--directory--+---------------------------+------------><
                      '-(--like--remote_directory-'   

Parameters

directory
Specifies the name of the PDS, PDSE, or z/OS UNIX file system directory to be created.
remote_directory
Specifies the name of a remote MVS™ PDS or PDSE that is to be a model for the directory to be created. This parameter is valid only when directory is a PDS or PDSE name. If you specify this parameter, the local site variables will change, and FTP will open and read the remote data set.

Examples

In this example, before LMkdir is issued, the local host had the following data sets:
  • MVSUSER.ISPF.ISPPROF
  • MVSUSER.JCL.CNTL
  • MVSUSER.SMFTEST
  • MVSUSER.TCPIP.DATA
  User:  ftp 1.1.2.3
System:    IBM FTP CS/390 V2R10   1997  314 01:11 UTC
           220-EZAFTSRV IBM CS/390 V2R10 at EMU.ABC.OZ, 17:04:12 on 08/03/97
           220 Connection will close if idle for more than 5 minutes.
           NAME (<host>:tsouserid):
 
  User:  mvsuser
System:    >>>USER mvsuser
           331 Send password please.
           Password:
           >>>PASS ********
           230 MVSUSER is logged on.
           Command:
  User:  lpwd
System:    Local directory is MVSUSER.
           Command:
  User:  lcd ftp
System:    Local directory name set to MVSUSER.FTP.
           Command:
  User:  lmkdir example
System:    MVSUSER.FTP.EXAMPLE created.
           Command:

MVSUSER.FTP.EXAMPLE has now been created. You can the same result directly with the LMKDIR 'MVSUSER.FTP.EXAMPLE' command.

This example illustrates the use of the (like parameter:
Command: 
lmkdir 'mvsuser.example.linklib' (like 'sys1.linklib' 
>>> XDSI 'sys1.linklib' 
200 SITE PDSTYPE=PDS RECFM=U BLKSIZE=32760 DIRECTORY=800 LRECL=0 PRIMARY=482 SECONDARY=30 CYLINDERS 
local site variables have changed 
MVSUSER.EXAMPLE.LINKLIB created. 
Command: 
After the LMkdir subcommands were issued, the local host had the following data sets under MVSUSER:
  • MVSUSER.FTP.EXAMPLE
  • MVSUSER.ISPF.ISPPROF
  • MVSUSER.JCL.CNTL
  • MVSUSER.SMFTEST
  • MVSUSER.TCPIP.DATA
  • MVSUSER.EXAMPLE.LINKLIB

Usage

  • FTP provides no subcommand to display a list of local directory entries. You should use TSO ISPF facility to check whether the directory is created by the LMkdir subcommand.
  • If you are running FTP in a z/OS UNIX environment, you can use the ! subcommand to check the status of z/OS UNIX file system directories.
  • The directory value is appended to the local current working directory to form the name of the created PDS, PDSE, or z/OS UNIX file system directory. To override the local current working directory, specify an absolute z/OS UNIX file system path name:
    /directory
    or a fully qualifed name in quotes:
    'directory'

    When directory is a PDS or a PDSE name, the data set characteristics of the newly allocated PDS or PDSE are determined by the settings of the local site variables.

  • You can use the (like parameter of the lmkdir subcommand to specify a PDS or PDSE on the server host that has characteristics you want the local directory to have.
    • The (like option is valid only when both client and server are z/OS V1R5 or later, and the working directory for both the client and server is an MVS high level qualifier (HLQ).
    • If you use the (like parameter, the local site variables will change.
    • The FTP client will set the local site variables for you so the new PDS or PDSE is created with characteristics similar to the remote directory. The client, however, can approximate only certain characteristics of the data set such as space type, primary, and secondary. For complete control over these characteristics, do not use the (like parameter.
    • FTP must open and read the remote directory to determine its characteristics. If this is not acceptable, do not use the (like parameter.
    • Only the 3390 device architecture is supported. If the (like parameter is used for directories residing on other types of devices, unpredictable results will occur. Use of the (like parameter when the source or target directories do not reside on a 3390 architecture device is not recommended.
    • If the remote data set is migrated, the server will inspect the AUTORECALL setting to determine whether to recall the data set or fail the request. If AUTORECALL is true, FTP will attempt to recall the data set; otherwise it will fail the request. Similarly, if the remote data set is not mounted, the server will inspect the AUTOMOUNT setting to determine whether to mount the data set or fail the request. If AUTOMOUNT is true, the server will attempt to mount the data set; otherwise, it will fail the request. You can change the server's AUTOMOUNT and AUTORECALL settings with the SITE subcommand. Choosing AUTOMOUNT or AUTORECALL could result in a long delay as the server waits for the data set to become available.
Related Topics:

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2013
This information center is Built on Eclipse™ ( www.eclipse.org ).