JLS system agents and JES2 cold start

JLS System Agents can have unique limit values for each JES2 Member. In the current JLS implementation, they are associated with the corresponding JES2 Member by keeping this member's JES2 number. These numbers along with the other agent information are saved in the TM control file.

If an installation changes JES2 member numbers in the JES2 configuration and cold starts JES2, the existing numbers in the saved system agent data are going to be interpreted differently. The result is that after such a JES2 cold start some JLS system agents may have incorrect limit values.

To prevent this issue, it would be advisable to set all JLS system agents to limit zero before implementing such JES2 changes and to set them  again to the intended limit values after a JES2 cold start is completed.

To set JLS system agents to a certain limit value the 'JLS SET ...' command can be used. To do this for several agents it could be more convenient to place the commands in a sequential file and to execute them by using a single 'TM BATCH ...' command. Refer to the ThruPut Manager Command Reference Guide for more information about the commands.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*