z/OS Message Classes

The Job log of a z/OS Job is stored in a job entry subsystem (JES) spool which distinguishes message classes. Each of these classes has a one-digit description that either shows a character (A-Z) or a number (0-9). Through the z/OS Agent, you can write the Job output to the message class that you have defined in the Job object, extend the Job log to include the Job output plus the JES statistics (JESMSGLG, JESJCL, and JESYSMSG), read messages, or route the Job log to message classes and include them in the Job log, release the Job log for printing and delete it.

This page includes the following:

Defining the Relevant Settings

  • In the INI file of the Agent
  • In the Job object itself
  • Dynamically with a script through Job attributes

It is recommended that you specify the settings that are most frequently used in the INI file of the Agent, and use them as a template. Define Jobs that require specific settings directly in the object or via script. The definitions that are made in the Job object overrule the settings that are made in the INI file.

The list below shows all the parameters and settings that you can define in the INI file of the Agent, in Job objects, and through scripts. You can adjust them to structure your Job logs to fit your requirements.

  • Handling the complexity of the Job log:
    • INI file of the Agent
      Parameter: completeJobout=
    • z/OS page of the Job object

      • Agent default configuration
      Store JES executions and Job output 
      Store JES executions 

    • Scripting
      Job attribute: MVS_COMPLETEJOBOUT
  • Handling the Job output:
    • INI file of the Agent
      Not available
    • z/OS page of the Job object
      MSGCLASS
    • Scripting
      Job attribute: MVS_MSGCLASS
  • Handling the identification of classes
    • INI file of the Agent
      Parameter: getMsgClass=
    • z/OS page of the Job object
      Obtain Message Classes
    • Scripting
      Job attribute: MVS_GETMSGCLASSES
  • Defining the message classes to which the class should be routed
    • INI file of the Agent
      Parameter: routeMsgClass
    • z/OS page of the Job object
      Route MessageClasses
    • Scripting
      Job attribute: MVS_ROUTEMSGCLASS
  • Releasing the Job log for printing
    • INI file of the Agent
      Parameter: relMsgClass=
    • z/OS page of the Job object

      • Agent default configuration
      Release after reading
      Do not release

    • Scripting
      Job attribute: MVS_RELMSGCLASS
  • Deleting the Job log
    • INI file of the Agent
      Parameter: jobPurge=
    • z/OS page of the Job object

      • Agent default configuration
      Delete after reading
      Do not purge

    • Scripting
      Job attribute: MVS_JOBPURGE

Note: On step level, you can define a message class within a Job to redirect and filter particular messages.

For further details, see

  • Agent z/OS

    • See a description of all the parameters that are available in the INI file of the z/OS Agent

  • z/OS (OS/390)

    • Learn more about the Job attributes that are available for z/OS Jobs and how you can define them.

  • OS/390 Jobs

    • Get detailed information about the Job object and its specific parameters that you can define.OS/390 Jobs

Using an Output Management System

If you plan to use an Output Management System such as BETA92, you need to:

  • define the message class in which the Job output is stored. This message class must be read.
  • Define the message class that is assigned to the Output Management System and redirect the Job log to it.

    Important! In some Output Management Systems, the Msgclass must be a write-enabled class as otherwise, it cannot be processed. In this case, do not connect an external writer to this class because the output would be processed by this writer.
  • Do not delete the Job log in the JES spool.

    Tip: Use a separate message class for the Automation Engine.

Example:

The following example illustrates how you configure directly in the Job object that the Job log should be routed.

The Job writes its output into the message class B. This message class and message class A are read and obtained. The order of the message classes is important when you route the Job log. In this example, message class A is routed to K, and B is routed to message class J.

See also: