Introduction › How the Started Task Works › How Tasks Work: Post-Spool › SYSOUT Application Interface

SYSOUT Application Interface

With the SYSOUT Application Interface, network input data sets are processed as follows:

• Network input data sets from a job or a DD statement that are not defined to database are created under an UNDEF report if the NETUNDEF initialization parameter is set to YES.

  If an UNDEF report is not defined or the NETUNDEF initialization parameter is set to NO, the network input data is requeued to or copied to a new data set under the new class, new destination, and/or new forms referenced by the NETCLSL, NETDEST, and NETFORMS initialization parameters. The NETREQUE initialization parameter determines whether these network input data sets are requeued or copied.

• The copied, distributed, or UNDEF reports appear under the name of the started task.
  • Requeued network input data sets retain their original job name, job ID, and accounting information.
  • These network input data sets reside in a non-held status even if the new class references a held class.
  • If an error occurs while re-queuing the network input data set, the network input data set is placed in a held status.
• Output statement parameters, such as PAGEDEF, FORMDEF, NAME, ADDRESS, TITLE, and so on, are retrieved and processed the same as in the pre-spool environment.
• Accounting information is obtained.

  Reports distributed through network input do not have the accounting information attached, but it is accessible through user exits and it is retained in archival copies of the report.

• The copies parameter is supported for report distribution specifications that indicate copies as "*".
• COPIES= supplied on a /*JOBPARM statement is not captured.

Example 1

Assume that CA Deliver runs at node N1 and that SYSOUT class E has been reserved and defined to CA Deliver for network input.

To have a report routed to and printed by CA Deliver, it must be created with the following attributes:

DEST=N1
SYSOUT=E

From another CPU, for non-shared JES spool, the JCL is as follows:

//STEP1    EXEC PGM=IEBGENER
//SYSUT1   DD   DSN=JCL.DATA(LISTING),DISP=SHR
//SYSUT2   DD   SYSOUT=E,DEST=N1
//SYSIN    DD   DUMMY
//SYSPRINT DD SYSOUT=A

In this example, the initialization parameter NETCLSL must be set to NETCLSL=E/A, where the value A is the class to which SYSOUT data is to be written if the extracted job does not match the definition in the database.

Example 2

Assume that CA Deliver runs at node N1 and that destination R100 has been reserved and defined to CA Deliver for network input. To have a report routed to and printed by CA Deliver, it must be created with the following attribute:

DEST=N1R100

From another CPU, for non-shared JES spool, the JCL is:

//STEP1    EXEC PGM=IEBGENER
//SYSUT1   DD   DSN=JCL.DATA(LISTING),DISP=SHR
//SYSUT2   DD   SYSOUT=B,DEST=N1R100
//SYSIN    DD   DUMMY
//SYSPRINT DD SYSOUT=A

In this example, the initialization parameter NETDEST must be set to NETDEST=R100.