Re: Global MONMSG and SNDPGMMSG *ESCAPE -- 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.

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 01/10/2018
12:47:34 PM:

On Wed, Jan 10, 2018 at 10:39 AM, <dlclark@xxxxxxxxxxxxxxxx> wrote:

Are there documented circumstances where an escape message

sent by

SNDPGMMSG would *not* trigger the action defined by the global MONMSG
specified at the beginning of the CL program? I have one that is

doing

that and I want to know what I have to change to make it honor the

global

MONMSG. The global MONMSG and the SNDPGMMSG are coded as follows.

MONMSG MSGID(CPD0000 CPE0000 CPF0000 MCH0000 WSE0000) +
EXEC(GOTO CMDLBL(ABORT))

CHKOBJ OBJ(&LIBOPT/IMLFDTLV02) OBJTYPE(*FILE)
MONMSG MSGID(CPF9801 CPF9802 CPF9810) EXEC(DO)
SNDPGMMSG MSGID(WSE9897) MSGF(&MSGFLIB/&MSGF) +
MSGDTA('No access to data library' *BCAT +
&LIBOPT *BCAT 'or no LIFO detail +
file.') MSGTYPE(*ESCAPE)
ENDDO

What's the message?

There is no message. The job just ends, without joblog, at the
point where the SNDPGMMSG issues the escape message shown above. I have
run it through debug and confirmed the information I am relaying here.

Sincerely,

Dave Clark

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.