Re: Mult MONMSG not working as expected

from: "Hiebert, Chris" <chris.hiebert@xxxxxxxxxxxxxx>
subject: RE: Mult MONMSG not working as expected

A GOTO is not necessary.

For example here are two scenarios:

1. This SAV command received message ID CPFA09E as an Escape message
(instead of as a diagnostic message). In that case this code would "GOTO
LO" because CPFA09E would be a "HIT" in the first MONMSG block and thus
break out of the MONMSG processing with the default "INGORE" because of the
lack of EXEC on that MONMSG.


2. This SAV command received message id CPF3794 as an Escape message.
Then that would be a Miss on the first MONMSG block, which then falls to
the second MONMSG which it "Hits" since it's an Any-CPF error (CPF0000). So
that process would hit the /* more code here */ "GOTO HI" section.


SAV DEV(()) OBJ(()) SAVACT(*YES) SEQNBR(*END) +
EXPDATE() ENDOPT(*LEAVE) ASYNCBRING(*YES)
MONMSG MSGID(CPFA09E CPD384E CPF3837 CPF3838) /* if any
of these HIT then monmsg process stops here */
MONMSG MSGID(CPF0000) EXEC(DO)
/* more code here */
GOTO HI
ENDDO
GOTO LO

LO: RETURN

HI: RETURN

ENDPGM



Chris Hiebert
Senior Programmer/Analyst
Disclaimer: Any views or opinions presented are solely those of the author
and do not necessarily represent those of the company.