Process Flow of WTORs

All WTORs that are issued at a system should be forwarded to NetView. Otherwise SA z/OS is not able to process them.

To achieve this, specify YES for Route all WTORs to AT in policy BUILD CONTROL of Entry Type MSG. For details of this Entry Type and policy, refer to IBM Z System Automation Defining Automation Policy. Otherwise the following definition in the message revision table has to be added:

UPON (OTHERMSG)
  SELECT
* Ensure all WTORs are being automated
    WHEN (WQE SUBSTR 345 C2D ^= "+0")
      REVISE("Y" AUTOMATE)
    OTHERWISE
  END

Incoming WTORs are processed by the NetView automation table (AT) and this triggers commands according to the processing purpose:

Called automation routine	Processing Purpose
ISSUEACT	Issue commands or replies (or both) that have been defined to a subsystem. Store the WTOR if it has not been replied to.
ACTIVMSG, HALTMSG, TERMMSG	Update the status of the subsystem that issued the WTOR. Issue defined commands or replies (or both). Store the WTOR if it has not been replied to.
INGMON	Issue commands or replies (or both) that have been defined to a monitor resource. Store the WTOR if it has not been replied to.
OUTREP	Store the WTOR.

The commands (other than OUTREP) are routed to the first active task that is defined in the AT synonym %AOFOPGSSOPER%. Thus they are usually routed to the work operator of the subsystem that issued the WTOR. This is done based on the job name that is associated with the WTOR.

Automation routines that process WTORs from subsystems that are not defined in SA z/OS or are from MVS components are routed to tasks that the WTORs have been assigned to based on their message ID.

The OUTREP command is routed to the first active task that is defined in the AT synonym %AOFOPSYSOPER%.