|
Notice that in the job log the message CPF9801 is being sent by program QSNDDTAQ, so what seems to be happening is that whatever value is in &NAME is not the same value that >is being passed on the call to QSNDDTAQ. As you are not showing us these parameters, I can only guess. But it is clear that the error is being issued from the API and not the >CHKOBJ.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Smith, Mike
Sent: Tuesday, June 19, 2012 11:39
To: midrange-l@xxxxxxxxxxxx
Subject: MONMSG question
So I had something weird happen the other day. I got called on a program failing and when I looked at it, I don't see why the MONMSG did not handle it.
I have to be missing something basic...
The CL program is passed several parameters, there's a DCLF, some variables defined and then the programs starts.
There are no Global MONMSG.
The program does a couple security things and then starts a loop.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.