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


MPut subcommand—Copy multiple data sets to the remote host

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

Purpose

Use the MPut subcommand to copy multiple data sets from your local host to the remote host.

Format

Read syntax diagramSkip visual syntax diagram
         .----------------.   
         V                |   
>>-MPut----local_data_set-+------------------------------------><

Parameters

local_data_set
Specifies the name of the file on your local host being sent to the remote host.

Because more than one data set can be copied with the MPut subcommand, the local_data_set parameter of this subcommand can be repeated many times, with each local_data_set separated by a blank space. You can use the asterisk (*) character for pattern matching when specifying the local_data_set with the MPut subcommand.

When the wildcard symbol (*) is used in the filename parameter, and the GLOB subcommand is set to expand metacharacters in file names, the LISTSUBdir option affects the result of MPut. For more information about the LISTSUBdir option, see LOCSIte subcommand—Specify site information to the local host, or the LISTSUBDIR statement (FTP client and server) details in z/OS Communications Server: IP Configuration Reference.

Examples

The following is a sample entry and response that displays after using the MPut subcommand to send selected files.
Command:
mput file*
Mput FILE1 (Yes|No|Quit|Stop prompting)? yes
>>>PORT 9,67,113,57,5,128
200 Port request OK.
>>>STOR FILE1
125 Storing data set /u/user31/temp/FILE1
250 Transfer completed successfully.
164 bytes transferred in 0.010 seconds.  Transfer rate 16.40 Kbytes/sec.
Mput FILE2 (Yes|No|Quit|Stop prompting)? no
Mput FILE3 (Yes|No|Quit|Stop prompting)? yes
>>>PORT 9,67,113,57,5,129
200 Port request OK.
>>>STOR FILE3
125 Storing data set /u/user31/temp/FILE3
250 Transfer completed successfully.
164 bytes transferred in 0.010 seconds.  Transfer rate 16.40 Kbytes/sec.
Command:
dir
>>>PORT 9,67,113,57,5,130
200 Port request OK.
>>>LIST
125 List started OK
total 16
-rw-r-----   1 USER31   SYS1         162 Aug 14 13:20 FILE1
-rw-r-----   1 USER31   SYS1         162 Aug 14 13:21 FILE3
250 List completed successfully.
Command:
Results:
  • FTP maintains the attributes of a data set that is transmitted between a client and a server. However, when you use the MPut subcommand, FTP might truncate data records and you might lose data, if:
    • You are creating a new file at the server and the value of LRecl, as shown by the STAtus subcommand, is a value less than the LRecl of the transmitted data set and SENDSite has been set to OFF, FTP truncates the transmitted data set.
    • The data set name already exists at the receiving site and the logical record length (LRecl) of the data set at the receiving site is less than the LRecl of the transmitted data set, FTP truncates the transmitted data set.
  • By default, if you use the MPut subcommand, the remote host creates files with the same names as those specified in local_data_set and overwrites any existing files with those names.

    To put files on the remote host with unique file names, you must have set unique storage on before issuing the MPut command. Use the SUnique subcommand to change the storage method.

  • If you specify one or more incorrect parameters with the MPut subcommand, an error message specifying the incorrect parameter is displayed. All correct files are transferred, regardless of any incorrect parameters, and do not need to be reissued.
  • When UNIXFILETYPE=FIFO is configured at the FTP client, and the local directory is a z/OS® UNIX directory, the following apply:
    • Named pipes are transferred; transfers from existing z/OS UNIX regular files will fail.
    • FTP is unable to read from the named pipe until another process on the z/OS client host opens the named pipe for writing. The z/OS FTP client waits up to the number of seconds specified by the FIFOOPENTIME value for another process to open the named pipe.
    • FTP waits up to the number of seconds specified by the FIFOIOTIME value for each read from the named pipe to complete. If the client cannot read any data from the named pipe for the number of seconds specified by the FIFOIOTIME value, the file transfer fails.
    • Sending the named pipe permanently removes data from the named pipe.
  • If the FTP server is a z/OS FTP server, the server UNIXFILETYPE configuration option is set to FIFO, and the remote file directory is a z/OS UNIX file system directory, the server creates the remote files as named pipes rather than as regular files.

    The FTP server creates named pipes using the same names as those specified in the local file and appends to existing named pipes with those names. The FTP server rejects transfers into z/OS UNIX regular files with the same names as those specified in the local file.

    For more information about using z/OS UNIX named pipes, see Using z/OS UNIX System Services named pipes.

Requirement: To send a data set to the remote host, you must have a defined working directory on the remote host and write privileges to the files in this working directory.
Restriction: The MPut subcommand is not applicable to generation data groups (GDGs).
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 ).