Re: More detail on authority failure

[Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

I would think yes - that parameter is recorded in the early part of the 
job log, IIRC. Because the job is still active, you should have access 
to the job log - sometimes you don't when the job is ended, as would be 
the case with the AF entry, right?

The trick is finding the MSGID that corresponds to the AF event in the 
audit log.

HTH
Vern

On 2/23/2017 8:16 AM, Justin Taylor wrote:
> Would that help identify the CMD() portion of the SBMJOB that's failing?
>
>
>
> -----Original Message-----
> From: Vernon Hamberg [mailto:vhamberg@xxxxxxxxxxxxxxx]
> Sent: Wednesday, February 22, 2017 5:16 PM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> Subject: Re: More detail on authority failure
>
> I wonder if a watch would be useful for the OP - if there is a MSG or PAL event or some other kinds of things associated with the authority failure, then whatever job gets the failure is suspended while a watch program is called.
>
> Watches are marvelous for at-the-time monitoring. One could DSPJOB and get the stack and all manner of things.
>
> STRWCH is one way to start one. There are also API calls to manage them.
>
> HTH
> Vern