Dataset requirement not being recognized

[Saul Suarez Del Real]

Hi all,
I have a job that did not recognized its dsn requirement and started running. The job , SCHID=10, was first triggered in at 06:04 and waited for the dsn requirement, which was catalogued at 06:09. No problem here as the job started running after the dsn was catalogued. Then the same job was triggered in at 06:57, SCHID=11 but it started running right away and failed. The dsn did not catalogue until 07:05. The job has MAINT=N. With SCHID=10 the LEADTM is 3 hours. With SCHID=11 the LEADTM is 1 hour. Did the job did not wait for the dsn because it was triggered within the same hour as the previous run?
Thanks

------------------------------
Saul Suarez Del Real
Core Infrastructure Analyst | TSO-Batch CA7
TIAA | Financial Services
------------------------------

[Roderick Woods]

Hi Saul,
 
When you specify LEADTM=3, that mean when JOBA enters the request queue it will look back 3 hours to see has the data set been created or updated within 3 hours. You stated the data set was cataloged at 06:09 and JOBA came in at 06:57. So the requirement is satisfied because it was within the 3 hour LEADTM.

Unlike job requirements, when you specify a LEADTM value of 1 - 99 it does not check to see if the data set was created or updated since the last run of the job and within the LEADTM. It does 1 simple check, has the data set been created/updated within the LEADTM specified.
 
In this case you should consider using LEADTM=0 and this mean, the data set must be crated/updated since the last run of JOBA.

[emckenzi]

Leadtm=99 means the dataset has to be catalogued after the job comes into the queue.

[Roderick Woods]

correction to the following statement I posted:
 
Unlike job requirements, when you specify a LEADTM value of 1 - 98 it does not check to see if the data set was created or updated since the last run of the job and within the LEADTM.
 
should state:  LEADTM value of 1 - 98  .... 
 
thanks Earl for pointing that out...