Performing Library Transfers to and from CA XCOM for Z/OS

Products

• XCOM Data Transport
• XCOM Data Transport - Windows
• XCOM Data Transport - Linux PC
• XCOM Data Transport - z/OS

Issue/Introduction

This article shows how to use the feature named 'library transfers' between MVS and non-MVS platforms. Examples are shown with the Windows directory structure- use the appropriate UNIX and Linux names when transferring to UNIX or Linux.

 

Environment

Release: ESBXCM99000-11-CA-XCOM Data Transport-Extended Support Basic
Component:

Resolution

1. When sending the entire contents of an MVS PDS file down to a specific non-mainframe 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 resulting member names on the MVS side will consist of the first 8 characters of the file names. Here are sample parameter values from the NT initiated transfer.
   

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

Additional Information

 

1. The wildcard can be also used to send some of the contents of a Windows directory. For example,

   C:\Testdirtree\a*

   will send only the files that begin with 'a'

2. The wildcard can be used to transfer files with a certain suffix. For example
   

   C\Testdirtree\*.txt

   will transfer all of the .txt files only.
   
   This can also be used on Windows initiated receives from MVS. That is, the following example:
   

   C:\Users\userid\*.doc

   will cause all of the PDS members to be created with the .doc extension on Windows.
   
   
3. Sending a PDS with wildcard in the member name to a Windows file specified without wildcards causes all the members in the PDS to be concatenated into the Windows file with a 1-line separator between 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. If the Windows file names contain special characters, they will be copied into the resulting member names which will then be 'non-standard member names'. These names are valid as per MVS rules (which allow almost any combination of 8 bytes as a member name) but may make the member names unusable in certain situations. For example, it won't be possible to specify a non-standard member name in a JCL DD statement.
7. 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
   
   
8. 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.