Starting Your Product › How to Configure Without CA CSM › Update the JES Configuration Names Table › How the JES Configuration Names Table Works

How the JES Configuration Names Table Works

When a CA SYSVIEW session initializes, it searches the JES parmlib member to find a matching OS system name in the SysName column. This match to the JES subsystem provides access to JES-related commands.

Matches are made as follows:

• The value for the JESNAME parameter specified in the GEN module is compared with the JES subsystem ID specified in the JES column.

  If it matches, the following occurs:

  1. The JES configuration module specified in the Module column is loaded.
  2. The JES product level and service level assembled into the JES configuration module are then compared with the product and service level of the JES subsystem:
     • If they match, the search is complete.
     • If they do not match, the search continues for another matching system name in the SysNames column.
• A search of the entire JES parmlib member finds a match on the JES product level but the service levels do not match:
  • The matching JES configuration module is used and a warning message is displayed saying the service levels do not match.
  • The maintenance has been applied.
  • The JES configuration module must be reassembled.
• A match cannot be found for a JES configuration module:
  • The JES services initialization terminates.
  • The JES-related commands cannot be used.
• You can use the ANY system name to match any system name, but the JES configuration module product and service levels must match the running JES subsystem.
• Generic wildcard matching is not performed on any column in the JES parmlib member.