Global MONMSG and SNDPGMMSG *ESCAPE -- MIDRANGE-L

Subject: Global MONMSG and SNDPGMMSG *ESCAPE
From: dlclark@xxxxxxxxxxxxxxxx
Date: Wed, 10 Jan 2018 12:39:42 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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

Sincerely,

Dave Clark

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Global MONMSG and SNDPGMMSG *ESCAPE , Charles Wilt

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.