File transfer variables enable you to extract information about file transfer events.You can use the variables to pass values to the following:
The following example shows the use of variables in the text to be sent to the user, USER01, in response to an event that satisfies the file transfer rule.
PROD------------ File Transfer : User Notification Details -------------------- Command ===> Short Description .. File transfer status and source Notify ............. USER01 Text ............... &ZRFPRODUCT,&ZRFSRCADDR,&ZRFSTATUS,&ZRFSRCNAME,&ZRFSRCTYPE
Contains the abend code.
Contains the number of blocks read during the transfer.
Contains the number of blocks written during the transfer.
Contains the compression percentage of the file transfer.
Contains the type of data set transferred by an IBM CS FTP server or FTP client (for example, ASCII, EBCDIC, IMAGE, DOUBLEBYTE, or UCS2).
Contains the data type transferred by an IBM CS FTP server or FTP client (for example, SEQ, PDS, or HFS).
Contains the date when the transfer ended in yyyymmdd format. See also &ZRFENDDATE.
Contains the date when the transfer ended in dd-mmm-yyyy format. See also &ZRFEDATE.
Contains the time when the transfer ended in hh.mm.ss format. See also &ZRFETIME.
Contains the time when the transfer ended in hhmmss format. See also &ZRFENDTIME.
Contains the failure code.
Contains the failure description.
Contains the type of data transfer operation (command) handled by an IBM CS server or FTP client (for example, RETRIEVE, APPEND, STORE, or STOREUNIQUE).
Contains the name of the file transfer application.
Contains the time between the CA XCOM Data Transport for z/OS transfer request and the start of the actual transfer.
Contains the type of protocol used for a CA XCOM Data Transport for z/OS transfer.
Contains the type of file transfer product.
Contains the number of records read during the transfer.
Contains the number of records written during the transfer.
Contains the number of times an alert has been raised for a file transfer event.
Contains the date when the transfer started in yyyymmdd format. See also &ZRFSTARTDATE.
Contains the address or node name of the source of the transfer.
Contains the name of the source file.
Contains the date when the transfer started in dd-mmm-yyyy format. See also &ZRFSDATE.
Contains the time when the transfer started in hh.mm.ss format. See also &ZRFSTIME.
Contains the monitored transfer status: START, END, or FAILURE.
Contains the ID of the CA TCPaccess FTP Server for z/OS started task or job.
Contains the time when the transfer started in hhmmss format. See also &ZRFSTARTTIME.
Contains the TCP/IP stack name used by an IBM CS FTP server or FTP client.
Contains the address or node name of the target of the transfer.
Contains the name of the target file.
Contains the ID of the user that performs the transfer.
Contains the number of bytes transferred. See also &ZRFXFRDBYTES.
Contains the number of bytes transferred but converted to kilobytes, megabytes, gigabytes, or terabytes. See also &ZRFXFRAMT.
Contains the transfer rate in kilobytes, megabytes, gigabytes, or terabytes per second. See also &ZRFXFRRATE.
Contains the time, in seconds, taken for the transfer.
Contains one of the following values:
Contains the transfer rate in bytes per second. See also &ZRFXFRDRATE.
Contains the CA XCOM Data Transport for z/OS transfer type (EXECUTE or SCHEDULE).
Contains the transmission mode for a transfer handled by an IBM CS FTP server or FTP client (for example, BLOCKED, COMPRESSED, or STREAM.
Note: The &ZRFBLKIN and &ZRFRECIN variables are applicable to CONNECT:Direct transfers only. The &ZRFBLKOUT and &ZRFRECOUT variables are applicable to CONNECT:Direct and CONNECT:Mailbox transfers only. Whether the amount of data read or written is in blocks or records depends on the file format.
| Copyright © 2010 CA. All rights reserved. |
|