× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



A minor point, but *ESCAPEs are not the only type of message that triggers
a MONMSG. But for sure *DIAG, *INFO, and other run of the mill types do
not.

On Tue, May 18, 2021 at 5:51 PM Hiebert, Chris <chris.hiebert@xxxxxxxxxxxxxx>
wrote:

I must be missing something. Your code looks exactly like mine.
Yes. Diagnostic Messages never never never trigger a MONMSG condition.
Only Escape Messages trigger a MONMSG condition.

It matches the first MONMSG, proceeds to the second MONMSG and "GOTO HI"
is executed.
No it does not. If it had matched the first MONMSG then it would NEVER
proceed to the second.

If the first MONMSG matches, I need to skip subsequent MONMSG.
This is how MONMSG works by default. There is never a fall through of
MONMSG.


I mentioned multiple times that the only message type that you monitor is
an Escape message.


Kevin also mentioned "I did go look through some of our save logs, and
CPFA09E and CPD384E are both diagnostic messages in our saves."

I don't know what Escape message you are getting, but I think it might be
something like:
CPF3794 Save or restore operation ended unsuccessfully.

If you debug your program and set a breakpoint inside the MONMSG code, you
should be able to see the Last Message in the joblog and determine what
message you are actually catching.

A CL program will never receive more than one Escape message from one
command.
Once a single Escape message is received from the command that processing
is done and control returns to the CL program.
And the processing either handles the error with a MONMSG or another
Escape message is sent to the caller of the CL program.


Hope this helps clear it up.

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.


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf
Of Justin Taylor
Sent: Tuesday, May 18, 2021 12:20 PM
To: MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Mult MONMSG not working as expected

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

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




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.