Defining job dependencies not working

All questions about Control-M jobs definitions
Post Reply
User avatar
gglau
Nouveau
Nouveau
Posts: 317
Joined: 13 Jun 2007 12:00

Post by gglau » 04 Dec 2007 4:23

That should work according to your description. In Desktop, do you see the two jobs connected by a line? If you don't see the connection line, that means the IN and OUT conditions are not defined with the same name. Check your typo. Condition names, and many other Control-M entities, are case-sensitive. Or simply drag JOB1 into JOB2 to let Desktop creates the relationship for you.

User avatar
philmalmaison
Nouveau
Nouveau
Posts: 1148
Joined: 08 Jun 2007 12:00
Location: Ile de France

Post by philmalmaison » 04 Dec 2007 11:19

is your condition really : JOB_1-ENDED-OK ODAT + ?
should be
JOB_1-ENDED-OK in ODATE

User avatar
Darvedd
Nouveau
Nouveau
Posts: 9
Joined: 31 Jul 2007 12:00

Post by Darvedd » 08 Dec 2007 12:54

It sounds like you've only ordered JOB1.

You need to order JOB1 and JOB2.

JOB2 will run once it's in-condition exists, but creating the in-condition doesn't order the job.

User avatar
nehagr
Nouveau
Nouveau
Posts: 1
Joined: 14 Dec 2007 12:00

Post by nehagr » 15 Dec 2007 9:48

That's absolutely right.... for job2 to run run after job1, job 2 must be present in the Active Job file too, only then it would pick the IN condition from the condition log.
So u need to order both Job 1 and Job 2 to the AJF.

User avatar
philmalmaison
Nouveau
Nouveau
Posts: 1148
Joined: 08 Jun 2007 12:00
Location: Ile de France

Post by philmalmaison » 20 Dec 2007 3:05

that the difference between cyclic planing process (like in autosys) or a daily planing process (like in controlm)
regards
Philmalmaison

Post Reply