Performing Library (PDS) Transfers to and from CA XCOM Data Transport for z/OS

Document ID : KB000028200
Last Modified Date : 14/02/2018
Show Technical Document Details

Summary: 

Here is how to use the feature for library transfers to and from the mainframe. Examples are shown with the Windows directory structure- use the appropriate UNIX and Linux names when transferring to UNIX or Linux.

Instructions:  

  1. When you send the entire contents of an MVS PDS file down to a specific directory in a single transfer, the PDS members will be saved as individual files on the partner side with the mainframe member name as the file name. There will be no file extension given on the partner side. Here is an example transferring to Windows. The syntax is the same to the other partners.
    Example:
    TYPE=SEND
    FILEOPT=REPLACE
    FILETYPE=FILE
    LFILE=XCOM.TEST.PDS(*)
    FILE=C:\Testdirtree\*

    This example assumes that the NT system already has an existing directory, 'Testdirtree' on the C drive. Replace will create any new files and overwrite any existing files of the same name.

  2. UNIX, LINUX and Windows can send all the files within a given directory to a PDS data set on MVS or z/OS in one transfer. The individual file members will be placed in the PDS as individual members of a PDS. The member name on the MVS side is limited to 8 characters. Here are sample parameter values from the NT initiated transfer.
    Local File C:\Testdirtree\*
    Remote File XCOM.TEST.PDSname(*)

Additional Information: 

  1. The *, or wildcard, can be used to send some of the contents of a Windows directory
    C:\Testdirtree\a*

    will send only the files that begin with 'a'

  2. The *, or wildcard, can be used to transfer files with a certain suffix
    C\Testdirtree\*.txt

    will transfer all of the .txt files only. This can also be used on Windows initiated receives from MVS.

    C:\Users\userid\*.doc

    will cause all of the PDS members to be created with the .doc extension on Windows.

  3. Specifying
    Local File=C:\Users\userid\JT.txt

    will cause all of the PDS members to be in single .txt file. There will be a 1 line separation between the members

  4. SUSPEND and RESUME cannot be used with wildcard transfers with DirTree support
  5. Do not use *.*. Instead always use * to indicate file names
  6. z/OS will not accept names that start with a number
  7. z/OS only supports some of the National Characters. The $, #, and @ are supported. The _, -, +, and : are not supported. These characters can not be used as part of the PDS name. The transfers will fail with XCOMM0226E - Member Name Missing or Invalid
  8. While Windows supports file names with _ and - , MVS does not. If the file has a _ or - within the first 8 characters the transfer with fail with XCOMM0226E - Member Name Missing Or Invalid. Same as above but '_' is a common Windows, UNIX and Linux file name separator
  9. It is necessary to make sure that Windows filenames are unique in the first 8 characters to use this feature. If you have multiple files in a Windows directory with the same name and the first 8 characters are identical, MVS will truncate the filename after 8 characters so all the files will have the same name. The second one will replace the first one and so on for multiple files
  10. If you attempt to use dirtree to transfer all of the files of a directory to a sequential file instead of a pds, the transfer will be successful but there will be no member names because the MVS file is not a PDS.