Previous Topic: Advantages of Using the Process SYSOUT Interface

Next Topic: Overview—Sending Reports with PSO


Process

The CA XCOM Data Transport server must be active and have PSO enabled if file transfers are to be queued. The only transmissions that can be queued for transfer while the server is down are Process SYSOUT JES spool files.

PSO can be disabled in a CA XCOM Data Transport server by specifying PSO=NO on the XCOMXFER EXEC parameter only. For more information, see the Default Options Table in the chapter "Configuration Parameters" in the CA XCOM Data Transport for z/OS Administration Guide.

Note: PSO is not supported in the XCOMPLEX. The XCOMPLEX Admin Server cannot be used to distribute PSO transfers requests.

While it is running, the CA XCOM Data Transport server continually scans the JES output queue for files to be sent to any of the destinations or writers (defined in the CA XCOM Data Transport control library) that it services. When CA XCOM Data Transport recognizes work in its serviced JES destinations or writers, it executes a file transfer to the targeted system.

CA XCOM Data Transport can scan the JES spool for either a specific destination or an external writer. An external writer can direct output to a specific printer on a remote system to permit a more detailed specification than is available when using RJE.

You can use the destination parameter PSOWAIT to control whether output is pulled from the JES spool immediately and held in temporary data sets or is allowed to remain on the JES queue until a session is available to transmit it on. For more information on the use of PSOWAIT, see the section Using PSOWAIT in this chapter.

Note: PSOWAIT is not a valid option for a TCP/IP transfer.