The region on the left in the figure in the section Verify the Installation (TYPE=EXECUTE Transfer) represents a batch job or TSO address space that is executing a file transfer between itself and a CA XCOM Data Transport server. The program XCOMJOB is executing in the region. Notice that XCOMJOB is executing a direct (non‑queued) transfer, also known as a TYPE=EXECUTE transfer (because of the specification PARM='TYPE=EXECUTE' in the JCL for XCOMJOB). In this type of transfer, the batch job or TSO address space synchronously transfers a file to or from a CA XCOM Data Transport server. The batch job or TSO address space enters a wait state until the transfer is complete.
The members XCOMJOBE and XCOMIVP1 in CAI.CBXGJCL contain sample jobs that initiate TYPE=EXECUTE transfers.
To perform a direct file transfer (TYPE=EXECUTE).
Add a JOB card and modify the XCOMIVP1 job (as indicated) before submitting it.
If the transfer was successful when the job completes, the XCOMLOG data set contains lines similar to the following display:
XCOMM0008I XCOM00 ACB OPENED SUCCESSFULLY XCOMM0009I COMPILED UNDER VTAM V6 R1 M2 - EXECUTING UNDER VTAM V6 R1 M2 5695-117 TYPE=SEND LU=XCOMAPPL FILETYPE=FILE FILEOPT=CREATE LFILE=FILE.A FILE=FILE.B XCOMM0155I XCOMAPPL ‑ LOGON EXIT ENTERED XCOMM0402I REQUEST NUMBER 002000 ASSIGNED TO TRANSFER REQUEST XCOMM0137I 00000020 RECORDS SENT SUCCESSFULLY - FILE=FILE.A XCOMM0151I XCOMAPPL SESSION ENDED
Note: Specifying an unsupported parameter or an invalid value for a parameter results in the CA XCOM Data Transport job terminating before execution. This applies to an EXEC PARM or a Configuration member parameter. A message indicating which parameter caused termination is displayed in the XCOMINIT log.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|