Ques: There is a Job XYZ which has got a Pred ABC, ABC is not in the current scheule at XYZ is wating for its dependancy (on ABC) and its unable to run.
Now, if a user request to run the Job ABC as a adhoc run with no dependancy on any job, after the ABC completes with RC=00, is it going to trigger Job XYZ ???
Just to repharase: XYZ is not running because its dependancy is not fulfilled (as XYZ is dependant on its pred ABC), If we run job ABC from outside schedule ( i.e- as a adhoc run with no succ and pred), Is it going to trigger Job XYZ once ABC is completed ???
As i understood from your statement,
XYZ is dependent on ABC, where ABC is not in the current scheduler and it lies outside the scheduler as an adhoc job and also ABC is not listed under any scheduler.
I'm considering OPC application as the scheduler.
See if ABC is not in the current application atleast it should be listed under a separate application which can be inside or outside the system. But XYZ job should contain the some correlation(dependency) details corresponding to ABC inside it.
So ABC job should be listed as separate OPC application. and dependency has to be set in the XYZ saying it is depending on ABC job.
And one more when u do an adhoc run, it no way triggers the JOB XYZ listed under any OPC application.
Hi Sriram, Thanks for taking such pain to understand my question.
Well, Im so sorry, I've not used right kind of words (termonologies)...
ABC job is not in the current plan of today and ABC is defined as a Pred of XYZ in the database. ABC might be in different application which is not loaded today in the current plan.
My 1st question here is:
For instance suppose ABC is not loaded today in the current plan, so is it going to affect XYZ : i.e- Is XYZ going to run today???, because its pred ABC is not in the current plan and it is not completed also.
My 2nd question considering the same senario mentioned above:
If the user request to run ABC (which is not in the current plan) as a adhoc run with no dependancy (no pred and no successor). So running ABC with no dependancy going to affect XYZ.
i.e- Is it going to trigger XYZ, even though we have ran ABC with no dependancy???
(Because I think Job XYZ is waiting for the completion of ABC, so as soon as ABC completes XYZ would be triggered)...but Im not sure...
Dependency you will set only when the pred job o/p is used as input to the successor program or for some validation purpose we have set this ABC as a predecessor job based on the business requirement.
Let us consider your example.
ABC is not loaded in the current plan or if it didnt run today or if it didnt get completed. then its for sure XYZ won't run as we have set the dependency for this.
One more case is, say ABC job failed due to some reasons, support team or some other team fixed the defect and run it is an ADHOC run, then XYZ can be trigerred by informing the operator to mark 'C' against the job ABC which you set as dependency for the job XYZ and Running the application that contains the XYZ will trigger the XYZ job.
XYZ W (waiting)
ABC E (error)
XYZ W (waiting)
ABC C (mark as completed inside the XYZ application)
XYZ R (ready) and then S(started) and finally C (completed)
When you mark "C" in the first job saying ABC job is completed, because you have done an adhoc run, so and so fields or files are updated properly, OPC will automatically turn the status of the job to 'R' when you come out of the application, the job will running in the spool area and once it is completed the entire application status will be marked as 'C'
Application name status
XYZ application C
Answer for the second question is also explained in the scenario.