Re: Send Scope Message

Hello Beppe,

Here's a new (V5R1) job attribute that might help:

Job end reason. The most recent action that caused the job to end. The
possible values are:
  0
  Job not ending.
  1
  Job ending in normal manner.
  2
  Job ended while it was still on a job queue.
  3
  System ended abnormally.
  4
  Job ending normally after a controlled end was requested.
  5
  Job ending immediately.
  6
  Job ending abnormally.
  7
  Job ended due to the CPU limit being exceeded.
  8
  Job ended due to the storage limit being exceeded.
  9
  Job ended due to the message severity level being exceeded.
  10
  Job ended due to the disconnect time interval being exceeded.
  11
  Job ended due to the inactivity time interval being exceeded.
  12
  Job ended due to a device error.
  13
  Job ended due to a signal.
  14
  Job ended due to an unhandled error.
Best regards,
Carsten Flensburg

----- Original Message -----
From: "Beppe Costagliola" <gcostagliola@asp.it>
To: <midrange-l@midrange.com>
Sent: Wednesday, June 12, 2002 11:52 AM
Subject: Send Scope Message


> I have a problem with Scope Messages:
>
> Pgm A at start calls QMHSNDSM and registers Pgm B.
>
> Pgm B is called at Pgm A termination
> Pgm B calls QUSRJOBI and checks the Active Job Status.
>
> If Pgm A has been cancelled with opt 4 the status is END.
> But if Pgm A went in error it sent a message to QSYSOPR. If operator
replied
> with 'C' Pgm A ended abnormally but Pgm B finds 'RUN' into Active Job
Status
> as if there were no errors.
>
> How can Pgm B see if  Pgm A has been cancelled for any reason ?