IBM Mainframe Forum

[rickaroo99]

I have dependent job 'B' which has a predecessor 'A' 'with a lead time of 14 for SCHID=2. The predecessor job triggers in and always completes well within 14 hours. Two times a month this dependency doesn't get satisfied. Job 'A' scanned in at 3 AM this morning and predecessor job 'B' ran from 9:30 PM to 10:07 PM last night. On these two nights, I am running special cycles that I don't believe should cause conflicts.

Dependent job runs multiple times a day with different SCHIDs, but only once per day as SCHID=2. Dependent job also has multiple other predecessors for SCHID=2 that get satisfied all the time.

Here is the final wrinkle to this puzzle. Predecessor job 'B' literally runs 365 days a year while dependent job 'A' only runs on business days. I don't believe this would pose a problem though as I believe there are similar days throughout the month when dependent job 'A' would trigger in after midnight and still shave the dependency satisfied.

I am a consultant on a project and as such have limited access to CA/7. Most of my knowledge is gleaned from LJOB commands and such. I do not have access to the actual job screens. My support contacts are of no help here. Perhaps I could live with a LT=99. However, I am just confounded as to why the LT=14 isn't being satisfied on these two days. Any thoughts?

Sorry to be so long-winded but I wanted to toss out as much detail as possible in the event something is being overlooked.

[dick scherrer]

Hello and welcome to the forum,

Please check your PM inbox.

d

[BaghdadMedic]

Did this get fixed? If not I can explain a work around.

[jonnie]

Dont know if you solved this, but it could be a "since the last successfull run" problem.If job B ran it would check for its predecessor, if it sees it in the lead time it will run. If job B comes in again and it's previous run was successfull it won't run again even if still within the 14 hour leadtime. It will wait for another instance of the predecessor.

Hope this helps.

jonnie

[BaghdadMedic]

True,

Change the lead time to all zeros!
(Have you ran since the last time I ran) works with lead times of all zeros...