Message Processing

SA z/OS assigns all the messages of a certain application to the work operator (AUTWRKnn by default) that is associated with the application. If the AT action uses standard SA z/OS capabilities (that is, SA z/OS commands), the work operator processes the messages in the following steps:

  1. The message flows through the ATs.
  2. If the message matches the AT condition, then SA z/OS data model is applied, which includes automation flag checking, code matching, threshold comparison, pass evaluation, and message capturing.
  3. Finally, the command is executed, or the outstanding reply is answered.

The following information is intended for advanced users.

There are two places where you can modify the processing for single messages:

  • You can overrule the AUTWRKnn automation operators where SA assigns the messages by default. Follow these steps:
    1. First, Set the AOF_ASSIGN_JOBNAME advanced automation option to 0, which enables "ASSIGN BY MESSAGE ID" take precedence over "ASSIGN BY JOBNAME".
    2. Then, use the NetView ASSIGN command with the MSG parameter to redirect the message to the automation operator you want. That particular message is then assigned to your specified automation operator, while all other messages still run on the AUTWRKnn automation operators that are assigned by SA z/OS.

    However, make this modification with care because it suspends SA z/OS load balancing and breaks the serialized command processing for that application.

  • You can overrule the automation operator that SA assigned to execute the command. To do so, specify an automated function together with the command in the MESSAGES/USER DATA policy in the Customization Dialog.

    Execution of the command is then routed to the automation operator that is specified for the automated function. The AT and data model processing are running on the specified automation operator and thus proper sequencing is guaranteed.

    SA z/OS internally uses the AOFEXCMD command to queue the specified automation operator. The AOFEXCMD routine checks whether the requested automation operator is available. If not available, it queues the command to a backup operator, so that in any case the command does not run on the current automation operator.

    It is recommended that you make this modification only for special reasons, for example, for long running commands. It's because it can break the serialized command processing for that application, if not all commands are executed on the same automation operator.