Environment: ZOS 2.1 with JES3; OPS/MVS automation
Question: Is there a way to prevent messages being placed on the SSI after
Message Flood Automation has determined the message is not to be queued to a
console and or SYSLOG. As it stands right now, our automation product,
OPS/MVS still sees the messages even though MFA has suppressed the display
of messages to SYSLOG and consoles. We have interrogated the flag settings
in IEAVMXIT to check if the messages have been processed by MFA and have
turned on the request delete flags, but, to no avail.
The mapping macro for the flags is IEZVX100, the Dsect that we have
addressable to is CTXT, and, the fields of interest are
45 (2D) BITSTRING 1 CTXTSFB2 STATUS FLAGS BYTE TWO
1... .... CTXTSRET "X'80'" MSG TO BE
RETAINED BY AMRF
.1.. .... CTXTSAUT "X'40'" AUTOMATION
SPECIFIED
..1. .... CTXTSNMD "X'20'" PRIMARY
SUBSYSTEM
MODIFICATIONS NOT
ALLOWED
...1 .... CTXTSRIS "X'10'" REISSUED
MESSAGE
.... 1... CTXT_PROCESSED_BY_MFA
"X'08'" Message
Flood
Automation processed
this message
.... .1.. CTXT_MSG_TO_BE_DELETED
"X'04'" Message will
be deleted
.... ..1. CTXT_WTOR_MONITORED_BY_AUTOR
"X'02'" WTOR is
being
monitored by
Auto-Reply
processing
49 (31) BITSTRING 1 CTXTRFB2 REQUEST FLAGS BYTE
TWO
1... .... CTXTRDTM "X'80'" DELETE THE
MESSAGE (NO HARDCOPY
AND NO DISPLAY)
I set the CTXFRB2 flag to Delete, but, to no avail. I know that Automation
packages can choose to ignore this setting, which appears to be the case in
our environment.
Is anyone else using Message Flood Automation, and, have you been successful
in preventing messages being picked up by your automation packages?
Kenneth J. Kripke
[email protected]
Sincerely Yours;
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
