CA XCOM Data Transport r11.5 Enhanced Features › Metatransfers

Metatransfers

CA XCOM Data Transport r11.5 introduced metatransfers, that is, transfers containing control information.

Using metatransfers allows you to do the following:

• Schedule transfers to a remote CA XCOM Data Transport server running r11.5 or above, using the –c5 option.
• Schedule inquire transfers to a remote CA XCOM Data Transport server running r11.5 or above, using the –c6 option.
• Retrieve history records to a remote CA XCOM Data Transport server running r11.5 or above, using the –c7 option. For more information, see History Command Option (-c7) in this chapter.

Note: If the remote server is z/OS, it can be either r11.5 or r11.6.

You can perform metatransfers across the following mainframe and distributed platforms:

• z/OS
• UNIX and Linux
• Windows

The following parameters have been added or updated to support metatransfers and to allow z/OS and UNIX parameters to be used in Windows:

• AGE—Specifies the number of days of history records that are retained when a purge procedure is executed.
• CKPT (alias of CHECKPOINT_COUNT)—Defines how often (based on record count) the sending system requests a checkpoint to be taken.
• CODE (alias of CODE_FLAG)—Identifies the type of data being transferred.
• DROPSESS—Indicates whether CA XCOM Data Transport drops an LU-to-LU session at the conclusion of a scheduled file transfer.
• EPRTY—Indicates the execution priority for the request on the remote z/OS system.
• FILE (alias of REMOTE_FILE)—The name of the file on the remote system that is being transferred.
• FILEDATA—Indicates how a remote USS file is allocated on the remote z/OS system when performing a receive file transfer on the local Windows system.
• GROUP—Valid only on a metatransfer (-c5); the group ID to use on the CA XCOM Data Transport system receiving a metatransfer.
• HIST_FILE—The name of the file to contain the history records returned by the inquire function (-c6) or when retrieving history records (-c7).
• HOLD_TRANSFER—Prevents a QUEUE=YES transfer from starting until explicitly released.
• INQ_FILE—Specifies the complete path and file name that will contain the information required to do an inquire on a transfer (-c6).
• INQ_WAIT—Specifies how long CA XCOM Data Transport should wait (in hours (hh), minutes (mm), and seconds (ss)) for transfers to complete when doing an inquire on a transfer (-c6).
• IPNAME (alias of REMOTE_SYSTEM)—For TCP/IP protocols, the name of the remote system that receives a file, job, or report.
• IPPORT (alias of PORT)—The number of the TCP/IP port on the remote CA XCOM Data Transport server.
• LDOMAIN—The domain associated with LUSERID and LPASSWORD, if the target system is Windows, when handling a metatransfer (-c5) or a history record retrieval transfer (-c7).
• LFILE (alias of LOCAL_FILE)—The name of the file on the local system that is being transferred.
• LIST—Valid only on a metatransfer (-c5); the list ID to use on the CA XCOM Data Transport system receiving a metatransfer.
• LPASS (alias of LPASSWORD)—The password of the local user to be validated on the CA XCOM Data Transport server handling a metatransfer (-c5) or a history record retrieval transfer (-c7).
• LU—Valid only on a metatransfer (-c5); the LU to use on the CA XCOM Data Transport system receiving a metatransfer.
• LUSER (alias of LUSERID)—The user ID to use on the CA XCOM Data Transport system receiving a metatransfer (-c5) or a history record retrieval transfer (-c7).
• PROGLIB— Specifies the PDSE program library for a transfer to a CA XCOM Data Transport for z/OS system.
• RELEASE—Valid for both normal schedules and metatransfers when the remote partner is z/OS. Tells CA XCOM Data Transport for z/OS to release unused DASD space.
• RNOTIFY (alias of NOTIFYR and NOTIFY)—Specifies the remote user notification type when sending data to a remote system.
• RNOTIFYNAME (alias of NOTIFY_NAME and NOTIFYNAME)—Specifies the remote user notification type when sending data to a remote system.
• SECURE_SCHEDULE—Specifies whether the metatransfer ( c5, c6, or c7) uses SSL.
• SPRTY—Indicates the scheduling priority of a metatransfer request.
• STARTDATE (alias of START_DATE, but with extra functionality)—Specifies the date when the transfer is to begin. Used only when QUEUE=YES.
• STARTTIME (alias of START_TIME, but with extra functionality)—Specifies the time when the transfer is to begin. Used only when QUEUE=YES.
• STCIP—Specifies the IP address of the CA XCOM Data Transport server to handle the metatransfer ( c5, c6, or c7).
• STCPORT—Specifies the TCP/IP port number of the CA XCOM Data Transport server to handle the metatransfer request ( c5, c6, or c7).
• SYSUDATA (alias of USER_DATA)—An open field where a user can specify any text associated with the transfer.
• TDUDATA (alias of TRANSFER_USR_DATA)—An open field where a user can specify any text associated with the transfer.
• TRANSFER_ID (alias of TRANSFER_NAME)—Allows the user to enter information to identify the file transfer request.
• TRANSFER_NAME (alias of TRANSFER_ID)—Allows the user to enter information to identify the file transfer request.
• TRUNCATE (alias of TRUNCATION)—Indicates whether CA XCOM Data Transport truncates excess characters in the source file if the record exceeds the maximum record length.
• USER—Valid only on a metatransfer (-c5); the user ID to use on the CA XCOM Data Transport system receiving a metatransfer.

For more information, see the CA XCOM Data Transport for UNIX and Linux User Guide.