×
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.
Were they escape messages ?
MONMSG will only capture escape messages I believe.
Regards,
Richard Schoen
Web:
http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
----------------------------------------------------------------------
message: 1
date: Mon, 17 May 2021 14:23:01 +0000
from: Kevin Bucknum <Kevin@xxxxxxxxxxxxxxxxxxx>
subject: Re: Mult MONMSG not working as expected
MONMSG's are all handled separately. If you have multiple monmsg's after a command, each one of them is checked in order. So the CPA09E was ignored by the first monmsg because you don't have an EXEC. The second one then checks it, and it qualifies, so it executes your code.
On Mon, 2021-05-17 at 09:16 -0500, Justin Taylor wrote:
I have this snippet of CLLE code:
SAV DEV(()) OBJ(()) SAVACT(*YES) SEQNBR(*END) +
EXPDATE() ENDOPT(*LEAVE) ASYNCBRING(*YES)
MONMSG MSGID(CPFA09E CPD384E CPF3837 CPF3838)
MONMSG MSGID(CPF0000) EXEC(DO)
/* more code here */
ENDDO
My intent is to ignore CPFA09E CPD384E CPF3837 CPF3838 message IDs, and run
the "more code here" for everything else. For the SAV command, the joblog
shows CPFA09E then CPD384E. My CL didn't ignore them and executed "more
code here" instead. Any idea what I'm missing?
midrange.com
