Re: Trapping a QSHELL command error in CL

[Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>]

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