Messages not accumulated although Message Automation correctly set up

book

Article ID: 128595

calendar_today

Updated On:

Products

CA Vantage Storage Resource Manager

Issue/Introduction

The Message automation script to capture the VAN1503I and VAN1504I  volume init messages is not working on some systems, while it works correctly on other systems. 
All seems to be configured correctly for Message automation and the MSGTRIGS member contains corresponding entries to pass these messages.
However, these Console messages are not captured in the concerned environment.
When the Message automation script is fired manually, it says No messages accumulated as below:
VAN0771I FIRE     of Automation Script CONMSG   script1   NOT Done - No messages accumulated

 

Cause

The AUTO attribute for the messages that are not identified in the MPFLSTxx PARMLIB member has been set to NO
Therefore, messages that are not identified in MPFLSTxx are not eligible for processing by an automation subsystem, i.e. Vantage Message Automation.

Environment

Release:
Component: VANT

Resolution

Change the AUTO attribute for the messages you want to use by Vantage message automation to YES in MPFLSTxx PARMLIB member, 
by setting AUTO(YES) for .NO_ENTRY (or by parameter AUTO(YES) for the msgid).
This is documented by IBM in section "Statements and parameters for MPFLSTxx" at link - 
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieae200/conparm.htm 

AUTO(YES|NO|token) 
for msgid, specifies whether the message is eligible for processing by an automation subsystem. 
for .NO_ENTRY, specifies for messages that are not identified in MPFLSTxx, AUTO indicates whether the message is eligible for processing by an automation subsystem 
NO - Makes the message ineligible for automation processing. 
YES - Makes the message eligible for automation processing. 

.NO_ENTRY specifies the message processing options for all messages that are not specified in MPFLSTxx members.
The options that you specify on the .NO_ENTRY statement override the system defaults for messages that are not specified in this member.
On the .NO_ENTRY statement, you can specify whether all messages not specified in the MPFLSTxx member are to be considered eligible for automation processing, retained, and suppressed. 
 

Additional Information

There is difference in the .NO_ENTRY definition in the MPFLSTxx PARMLIB member between the system where the automation works and the one where it doesn't. 
N 0020000 SYS1 19036 21:20:22.33 STC29747 00000094 VAN1504I ... 
N 0020000 SYS3 19008 08:52:50.62 STC80995 00000084 VAN1504I ... 

The message is suppressed on both systems, but the difference is in the following flag: 
......1. - automation requested (AUTO) 
This flag indicates if the message is eligible for automation.
The EMCS console used by Vantage accepts the messages eligible for automation.
That's the reason why the message automation works on some systems even if they are suppressed. 

As per IBM documentation: 
.NO_ENTRY specifies the message processing options for all messages that are NOT specified in MPFLSTxx members. 
See parameter AUTO of msgid and of .NO_ENTRY in section "Statements and parameters for MPFLSTxx" at link - 
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieae200/conparm.htm 

In systems where the automation works is the following: 
SYS1 does not have .NO_ENTRY 
or
SYS2: 
OPS1180I MESSAGE ID -MPF SUPPRESS RETAIN AUTO TOKEN EXIT 
OPS1180I .NO_ENTRY -00 NO YES YES 

->AUTO YES is the default for all messages. 

In systems where the automation does not work is the following: 
SYS3 and SYS4: 
OPS1180I MESSAGE ID -MPF SUPPRESS RETAIN AUTO TOKEN EXIT 
OPS1180I .NO_ENTRY -00 NO NO NO 

->AUTO NO is the default for all messages.