Troubleshooting
Problem
Defined a JES2 message to be automated on in MVS components, but the message does not seem to be trapped in the automation table.
Symptom
Have set up a JES2 message ($HASPxxx) in MVS Components to be automated on and kick off a specific action.
When the message is issued and is shown in the netlog, it does not hit the automation table. There is no CNM493I issued for this message while other non-JES2 messages are being automated on with no problems.
Cause
SA puts application messages into groups in the Automation table at Build time.
These are messages supplied by SA along with User Defined messages.
The groups are based on Applications. So, JES2 messages are in a group named INGJES, CICS messages are in a group named INGCICS, IMS is in INGIMS...
This grouping is done for performance reasons.
If a Application is not defined to SA to be managed, then there is no reason to check for these messages in the Automation Table - so they are disabled. You can see what groups are Active by using the AUTOTBL STATUS command in NetView. The command output will show something like this to indicate which groups are not Active:
BNH363I THE AUTOMATION TABLE CONTAINS THE FOLLOWING
DISABLED STATEMENTS
TABLE: INGMSG01 INCLUDE: __n/a___ GROUP : INGCICS TABLE: INGMSG01 INCLUDE: __n/a___ GROUP : INGIMAGE TABLE: INGMSG01 INCLUDE: __n/a___ GROUP : INGIMS TABLE: INGMSG01 INCLUDE: __n/a___ GROUP : INGJES2 TABLE: INGMSG01 INCLUDE: __n/a___ GROUP : INGJES3
Diagnosing The Problem
Check the Automation Tables to see where the message in question is located.
Take a JES2 message for example. In NetView, BR INGMSG01 to see the SA Automation Table, and search for the message in question. Then, see if it is defined in a group. The following statement sets up a GROUP for JES2 IF (GROUP:INGJES2) MSGID = . 'HASP' . & DOMAINID = %AOFDOM% THEN
BEGIN;messages:
In order for that Group - INGJES2 to be used for Automation, it must be Active. This is what the AUTOTBL STATUS command shows - what groups are active. In this case, INGJES2 is disabled, so no statements in the group will be evaluated.
If the message added via MVS Component in this example is not being automated on, check and see if it is defined in a GROUP, and then check to see if the GROUP is active.
Resolving The Problem
There are two ways to resolve this scenario and get the message automated on:
1) Create an APL with the type (ex: JES2) and define
the Policy such that SAzOS will perform no automation or monitoring
on this Application. Link it to an APG that is linked to the MVS
system or systems you want the trap for the message (ex $HASPxxx) to be active on.
Rebuild and reload the ACF.
2) Code the message in question manually in SA Automation Table INGMSGU1. The U1 stands for User Table 1 - is available to manually code Automation statements into.
Was this topic helpful?
Document Information
Modified date:
08 August 2018
UID
swg21606686