Re: Getting job to use SYSRPYL

On 09-Sep-2014 14:21 -0500, Adam Driver wrote:

<<SNIP>> Job 189213/MBCBU/MBCBUBKP started <<SNIP>> with the
following job attributes: <<SNIP>> INQMSGRPY(*SYSRPYL) <<SNIP>>

However, looking at the job definition attributes for the same job,
I see that it ran with *RQD:

<<SNIP>>
Job: MBCBUBKP User: MBCBU Number: 189213
<<SNIP>>
Inquiry message reply . . . . . . . . . . . . . . : *RQD
<<SNIP>>

Am I missing something stupid here?

That job attribute is not ensured to be static throughout the job. What was assigned as the InqMsgRpy() attribute when the job was created [submitted in this scenario] will not necessarily match the value of that attribute when the job was reviewed later; being temporal, the value seen is merely historical information, relevant only for the snapshot at the moment when the attribute was retrieved from the active job.

The subsystem routing program [per the Routing Entry (RTGE); ADDRTGE] or a program that was run within the routing step, or a request from another job, had effected the change to that attribute of the batch job since submission\inception. Any of Auditing, Debug, or Trace could be used to seek the origin of the [probable] Change Job (CHGJOB) activity; a simple review of the joblog [produced with full logging] may suffice to locate any messages CPC1129, indicating that the job was changed by another job [that message also logs the job name that had effected the change, though what was changed is not included in the messaging].