CA XCOM Data Transport Wildcard Transfers: "DirTree" - How it works

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

Summary: 
Rules for sending wildcard transfers between platforms

Background:  

Dirtree works in three different ways.

  • First it allows you to transfer the entire contents of an MVS PDS file down to a specific Windows, Linux or Unix 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.
  • The second purpose is to allow Window, Unix or Linux to 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.
  • The third way to use the Dirtree feature is to transfer an entire directory from Window, Unix or Linux to another Windows, Linux or Unix platform.

Instructions: 

JCL Example Sending from MVS to Windows:
TYPE=SEND
FILEOPT=REPLACE
FILETYPE=FILE
LFILE=XCOM.TEST.PDS(*)
FILE=C:\Testdirtree\*

This example assumes that the Windows 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.

Sample parameters to send from XCOM for Windows to z/OS

Local File C:\Testdirtree\*
Remote File XCOM.TEST.PDSname(*)

 

Tips

  1. The *, or wildcard, can be used to send some of the contents of a Windows directory.  i.e. 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 i.e. C\Testdirtree\*.txt will transfer all of the .txt files only.
  3. This can also be used on NT initiated receives from MVS. C:\Users\*.doc will all of the PDS members to be created with the .doc extension. MVS PDS members do not have file extensions.
  4. Local File=C:\Users\test.txt will cause all of the PDS members to be 1 .txt file. There will be a 1 line separation between the members.
  5. SUSPEND and RESUME cannot be used with wildcard transfers with DirTree support.
  6. Do not use *.*. Instead always use * to indicate file names.
  7. z/OS will not accept names that start with a number.
  8. 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.
  9. It is necessary to make sure that Windows, Unix and Linux filenames are unique in the first 8 characters to use this feature. If you have multiple files in a 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. This functionality was in the product already.