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:
- 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
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.