Post-Installation Configuration Considerations › JES2

JES2

Because CA Top Secret does not make any modifications to JES2 (or its control blocks), it makes certain assumptions about the offset of the JCT control block fields:

• JCTINDEV (input device)
• JCTROUTE (NJE input device)
• JCTNJHDR (NJE header)

JCT offsets are determined automatically based on the JES level detected at CA Top Secret initialization. If your installation has made modifications to the JES2 JCT control block which shift the original offsets, the following procedure allows CA Top Secret to correctly locate the source of a batch job:

• Verify the version of primary JES2 running at your installation
• Verify the offsets of the affected JCT fields
• Use the CA Top Secret JCT control option to make adjustments

JES Startup Considerations

The following considerations apply to JES startup:

• You can start the CA Top Secret address space before JES starts. You should not provide a $$$LOG$$ SYSOUT DD statement in the JCL. Thus, when JES becomes active, CA Top Secret dynamically allocates and begins using a $$$LOG$$ SYSOUT data set.

  Note: You cannot see the $$$LOG$$ spool file until JES is started.

• For CPF nodes that are defined in the Node Descriptor Table (NDT), CA Top Secret performs the following activities if CA Top Secret starts before JES:
  • While JES is inactive, CA Top Secret ignores journal files that are associated with the node.
  • After JES is activated, CA Top Secret dynamically allocates and opens SYSOUT journal files for each node (if no SYSOUT DD statements exist in the JCL) and allocates and opens the incoming RECVCMDS journal file.

  Note: CPF nodes that are defined through the parameter file are not eligible for SYSOUT spool allocation when JES has started after CA Top Secret.

• After JES becomes active, CA Top Secret dynamically allocates SYSOUT files for LDS journal and trace data sets. CA Top Secret allocates these data sets only if no DD statements exist in the JCL.

  If JES is terminated before CA Top Secret, CA Top Secret closes any opened SYSOUT data sets. CPF continues to send and receive commands, but no activity is logged to SYSOUT journal files. LDS continues to process outbound commands and commit them to the LDS recovery file. When JES restarts, these commands are propagated.