Re: SMBJOB - with delay

On 12-Nov-2014 15:03 -0600, rob@xxxxxxxxx wrote:

On 12-Nov-2014 14:48 -0600, Steinmetz, Paul wrote:

On 12-Nov-2014 14:37 -0600, Steinmetz, Paul wrote:

I’ve run into multiple case where I’m doing a SBMJOB, with either
a CMD or PGM.
But, for this process to be successful (job I’m submitting from
needs to end to rid record locks), I need to have a 5 second delay.

SBMJOB does not have a built in delay option.

Any thoughts from the group?

<<SNIP>>
I should have clarified, I'm actually doing a HLDJOBJS, which is
changing the status of the AJS (advanced job scheduler) from *READY
to *HOLD

SBMJOB CMD(HLDJOBJS JOB(&JOBNAME)) JOB(HLDJOBJS)

The intermittent problem is that HLDJOBJS failed because the AJS
record was still in use QUSRIJS/QAIJSMST
Record 40 in use by job 545328/CPASFTPC/BRCSFTBCS

<<SNIP>>
Or, one other idea, when you SBMJOB the HLDJOBJS make sure that it
uses a job description with a special class (see WRKCLS)
Default wait time . . . . . . . *nomax

Awaiting a record lock [as identified by the apparent CPF5027 "Record &6 in use by job &9."] is timed according to the Maximum Record Wait Rime (WAITRCD) attribute applied to the Open Data Path (ODP), not according to the Default Wait Time (DFTWAIT) for the job. And the WaitRcd() setting offers no *CLS special value [to suggest redirection to the "default wait time specified in the class description"] like is available for both the Wait Time (WAIT) parameter of the Allocate Object (ALCOBJ) command and the Maximum File Wait Time (WAITFILE) [aka Wait File Timeout] parameter of the commands: Change Logical File (CHGLF), Change Physical File (CHGPF), and Override With Database File (OVRDBF).