Re: Error handling over multiple call levels

[Tim Adair <tadair@xxxxxxxxxxxxxxxx>]

A big Thank You to everyone who responded.  I chose to go with the 
method of submitting each individual job step to batch, and monitoring 
with GET_JOB_INFO.  I monitor until the job's status is either blank 
(completed) or MSGW (error).  If it's MSGW, I put a popup window message 
on the screen ("Error - Do Not Touch") and go into a loop that 
continuously checks the status until the error is resolved (i.e. status 
is no longer MSGW) and then the job continues normally.

This is working very well, but I've run into another issue.  When an 
error occurs on one of these submitted job steps, the error message is 
sent to the QSYSOPR message queue.  Now, some of our I.T. personnel get 
automatically notified of any error messages on QSYSOPR, and some have a 
habit of responding to them even when they're not familiar with the 
situation.  For this new program I cannot have that happening. 
Therefore, I need to be able to force these error messages to go to a 
message queue other than QSYSOPR.  I've checked the CHGJOB command and 
the SBMJOB command, and neither allows this.  (SBMJOB has the parm MSGQ 
but this applies only to Completion messages.)

This must be done in the new front-end program.  Modifying the 
(existing) job step programs is unrealistic, to put it mildly.

Any ideas would be welcome.

Thanks.

~TA~


On 2/21/2024 4:01 PM, Tim Adair wrote:
> Given the following scenario:
> PROGRAM A calls Program B.  Program B calls Program C.  Program C gets 
> an error (of any kind).
>
> Is there any way to notify Program A that program C had an error, 
> without losing my place in program C.
>
> I'm writing in RPGLE (interactive) Program A, which reads a file where 
> each record contains the name of a (Program B) program.  These B 
> programs are almost all CL programs that call RPGLE programs (which are 
> the C-level programs).  If an error occurs in a C-level program, I want 
> this communicated to program A which will notify the user, _BUT_ I don't 
> want to lose (or automatically respond to) the error in program C.  I 
> want program A to notify the user, but I still want to be able to 
> manually deal with the original error in program C.
>
> Now the kicker...  This must be done without modifying any of the B or 
> C-level programs.  All the hoop-jumping must be done in the new A-level 
> program.
>
> Sorry if this is confusing.  If anyone can decipher the ravings of a 
> lunatic, I would appreciate your thoughts.
>
> Thanks.
>
> ~TA~