Re: nested MONMSG -- MIDRANGE-L

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

Hi Jerry

You can put a global MONMSG right after the DCLs - this should have a GOTO to a message handler near the bottom of your code. Your regular stuff should have a GOTO to jump beyond the handler.

Any MONMSG within the body of the code overrides the global one.

HTH
Vern

On 9/27/2016 6:01 PM, Jerry Draper wrote:

In our backup routine we do a:

SAVLIB *ALLUSR

SAVDLO

SAV (ifs)

We want to monitor the SAVLIB for CPF3777 (not all libs saved) and ignore
it

However we want to monitor for any other message and do a SNDPGMMSG if
that happens.

How can we do this?

Like this?
PGM
SAVLIB *ALLUSR
MONMSG CPF3777
MONMSG CPF0000 EXEC(SNDPGMMSG blah blah)

SAVDLO
MONMSG CPF0000 EXEC(SNDPGMMSG blah blah)
SAV (ifs)
MONMSG CPF0000 EXEC(SNDPGMMSG blah blah)
ENDPGM

or this:

PGM
MONMSG CPF0000 EXEC(SNDPGMMSG blah blah)

SAVLIB *ALLUSR
MONMSG CPF3777

SAVDLO
SAV (ifs)
ENDPGM

Jerry

--
--
Jerry Draper, Trilobyte Software Systems, since 1976
IBMi, Network, and Connectivity Specialists, LAN/WAN/VPN
Representing WinTronix, Synapse, HiT, and others .....
(415) 457-3431; [1]www.trilosoft.com

References

Visible links
1. http://www.trilosoft.com/

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.