Thanks for the reply.
That is in fact going to be the method I will use
Programmer/Analyst, Direct Response
"If you're going through Hell, keep going" - Winston Churchill
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Thursday, October 25, 2012 12:27 PM
To: Midrange Systems Technical Discussion
Subject: Re: Trapping a QSHELL command error in CL
Not exactly... but you could MONMSG for QSH0002, then RCVMSG (like Luis
said) and extract the errno and reason code from the message data. If you determine it's an error your program didn't want to handle, you could re-send the message at that point (via SNDPGMMSG, for example.)
On 10/25/2012 7:55 AM, Alan Shore wrote:
Hi Scott - thanks for your reply.
I do know about MONMSG, that can be used to trap an error, as well as the availability of DOWHILE, DOUNTIL and DOFOR commands that can be used to implement loops.
What I didn't know (and just found out late last night) was that you
could use MONMSG to capture QSH0002 errors
However, that is just TOO all encompassing.
The question is - Can I capture the QSH0002 for ONLY error code 3489 reason code 4?
So far, my investigation has not discovered anything
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l
Disclaimer: This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.