JES2 considerations

Total Object Manager (TOM) uses IBM job entry subsystem 2 (JES2) services, such as writing messages to the job log, and automatically connects to JES2 when its available. TOM also automatically disconnects from JES2 when it is terminating.

If you configure TOM to manage JES2, start TOM with the SUB=MSTR parameter. STCs started without SUB=MSTR must be stopped before stopping JES2. Therefore, you should define those STM objects with the JES2 object as a dependency. When you request a SHUTSYS, the dependent objects are stopped before TOM stops the JES2 object.

For more information about controlling and operating JES2, see "Controlling the JES2 environment" in the IBM Documentation. Use this information to appropriately define the JES2 object attributes and policies for TOM in each system or sysplex.

You can use the Generic Stateless Management (GSM) Extension to define JES2 resources as GSM objects, which can depend on the JES2 object. Examples of JES2 resources that you can define are job initiators and devices (printers, readers, etc.) You might need to define a stop recovery command for a JES2 logical initiator. This recovery command determines the name and identifier of the batch job stream running in the logical initiator and then terminates the batch job. This allows the initiator to stop and drain in a timely manner. 

As an alternative to GSM objects, you can use the JESDOWN EXEC that is distributed with BMC AMI Ops Automation to stop JES2 objects. However, you might need to customize this EXEC. For more information, see JESDOWN-sample-EXEC.