SA z/OS Unexpected AOF204I message at initialization for routine INGSTOBS

Answer

This was the message client observed at initialization of SA z/OS Agent region:

AOF204I : EXPECTED PARAMETERS MISSING OR INVALID FOR REQUEST INGSTOBS - AUTOOPER

INGSTOBS is the 'status observer' task within SA z/OS.

Documentation for it is here:
http://publibfi.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/ing4r500/2.1.40?

INGSTOBS Purpose
The INGSTOBS routine lets you subscribe as a status observer for one or more resources. Whenever a status change occurs, the automation manager sends you a notification.

INGSTOBS Syntax
INGSTOBS REGISTER DEREGISTER LIST , exitname , autoop , res

For background, when a SA z/OS managed resource (ie. APG, APL, MTR) enters a status change, then if a user (or autotask) is registered against that resource, then processing can take place based on that change of status. One can call any code of your choice (the status observer exit) and run it on an autotask of your choice.

For instance, SA z/OS uses INGSTOBS internally to track all APG groups, so that when they have a status change the routine INGRYSOS runs and post an SDF update for the APG. This makes sense when considering that an APG does not have an UP/DOWN message but we still need to post accurate SDF information for them. This is what you client sees when entering INGSTOBS LIST; the list of all APGs monitored and the INGRYSOS routine performing the status updates to SDF for those note APGs.

Examining customer log resulted in determining these events were related to the AOF204I message.

AUTOTASK OPID=IHSSAUT1
AUTOTASK OPID=IHSSAUT2
CNM570I STARTING AUTOMATION TASK IHSSAUT1
CNM570I STARTING AUTOMATION TASK IHSSAUT2
DSI530I 'IHSSAUT1' : 'OST' IS READY AND WAITING FOR WORK
DSI530I 'IHSSAUT2' : 'OST' IS READY AND WAITING FOR WORK

IHSSSTRT
IHS750I OUTPUT DISPLAY FOLLOWS:
AOF204I 11:58:14 : EXPECTED PARAMETERS MISSING OR INVALID FOR REQUEST
AUTOOPER
IHS708I TIVOLI BUSINESS SYSTEMS MANAGER-SA INITIALIZATION COMPLETED
IHS746E SEND TO PPI RECEIVER NETVAOP FAILED WITH RC 26. PUMP IS NOT ACTIVE WITH PPI=YES

From these log excerpts, client is using TBSM (tivoli business system manager) software, and has made customizations in SA z/OS and NetView in order to integrate the TBSM "Event Pump" from z/OS into automation under SA/NV.


From the TBSM Event Pump documentation...

These components enable the integration of System Automation for z/OS with Event Pump:

System Automation for z/OS application programming interface (API), which is available through the general status observer facility and implemented in the automation manager, enables users to register an exit to gather status information for specific resources or resource types. Event Pump uses the exit to capture all application (APL) and application group (APG) information.

When the AOF540I message is trapped in the NetView® message automation table, the Event Pump-System Automation for z/OS interface is initialized, which runs the IHSSSTRT program (which invokes INGSTOBS to register a status observer exit process).


The finding here is that the SA z/OS INGSTOBS routine is producing the AOF204I message because the IHS* related autotasks are not defined as SA Autotask Operators (within the PDB option AOP), because the client had defined the autotasks 'external' to SA (via excmd, auxinit, or direct AUTOTASK cmds).

The latest documentation for TBSM Event Pump has this reflected in their setup instructions (as opposed to older releases), to define the autotasks within the SA policy file.


IBM Tivoli Event Pump for z/OS, Version 4.2.2
Updating the System Automation for z/OS control file

Define the IHSSAUT1 and IHSSAUT2 operator IDs in your automation control file using the SAzOS customization dialog.
Rebuild your automation control file and issue the INGAMS command from the NetView command line on your System Automation for z/OS® agent.