× 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.


  1.  Home
  2. MIDRANGE-L
  3. October 2012

Re: Trapping a QSHELL command error in CL

Hi Alan,

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
MONMSG(QSH0002)
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


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.