A specific report created by a Control‑M production job can be routed using NJE services to a VM machine (user), simply by defining the destination of the report in the job’s JCL. The following examples demonstrate how to implement this using standard MVS and JES statements:

• Route the report to a certain VM user using parameter DEST=(node,user) in the appropriate DD statement:

//REPORT DD SYSOUT=A,DEST=(VMPROD,USER1)

• Route the report to a specified VM user using an MVS OUTPUT statement and the report’s DD statement referencing that MVS OUTPUT statement

//JOB1 JOB ...
//OUTREP OUTPUT DEST=VMPROD.USER1
//STEP1 EXEC PGM=...
//REPORT DD SYSOUT=A,OUTPUT=*.OUTREP

• Route printed sysout files of the job to a specified VM user using a JES2 /*ROUTE PRINT statement:

Punched sysout files of the job can be sent to VM using the JES2 /*ROUTE PUNCH statement. A punched SYSOUT file consists of 80-character records. Most sites define JES output CLASS B as a punch class.

The following figure shows Routing the Production Job’s Report to VM using JCL:

Figure 30 Routing the Production Job’s Report to VM using JCL