When rerouting the data set, your exit routine should ensure the data set has the proper authority for the target node. If your routine accepts SYSOUT already rejected by RACF®, there will not be an audit record for the subsequent data set create. The owner of the data set is the userid of the job that created the SYSOUT, even if that userid could not own the data on your system and RACF does not validate the assigned userid. If you are using security labels, RACF assigns a SECLABEL of SYSLOW to the data set created.

Expanding the JCT Control Block: You can add, expand, locate, or remove extensions to the job control table ($JCT) control block from this exit using the $JCTX macro extension service. For example, you can use these extensions to store job-related information. For more information, see z/OS JES2 Macros

Related Exits: If you code Exit 55, it may also be necessary for you to code a parallel Exit 39 to provide the same function for SNA and BSC lines.