Re: Mult MONMSG not working as expected

[Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>]

Of course you also could just put the RETURN in place of the GOTO inside the DO and be done with it, unless there are other things to do.

Jim Oberholtzer
Agile Technology Architects



> On May 18, 2021, at 1:20 PM, Justin Taylor <jtaylor.0ab@xxxxxxxxx> wrote:
>
> I must be missing something.  Your code looks exactly like mine.  It
> matches the first MONMSG, proceeds to the second MONMSG and "GOTO HI" is
> executed.  If the first MONMSG matches, I need to skip subsequent MONMSG.
>
> Can you explain what I'm missing?
>
> Thanks
>
> date: Mon, 17 May 2021 20:27:54 +0000
> > 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.
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com