View previous topic :: View next topic |
Author |
Message |
navhin Beginner
Joined: 26 Mar 2007 Posts: 20 Topics: 7 Location: india
|
Posted: Mon Mar 26, 2007 7:49 am Post subject: give me the difference between the following terms in CA7 |
|
|
hi
may i know the difference between the following terms in CA7
triggered jobs and successor jobs
triggered by jobs and dependent jobs _________________ navhin |
|
Back to top |
|
|
kolusu Site Admin
Joined: 26 Nov 2002 Posts: 12375 Topics: 75 Location: San Jose
|
Posted: Mon Mar 26, 2007 8:10 am Post subject: |
|
|
navhin,
Triggered Jobs :
ex: There are 3 jobs in the systems.
Code: |
JOB A >>>triggers >>> JOB B>>>> triggers JOB C
|
Now Job B & JOB C are called triggered jobs as they are being triggered by JOB A and JOB C respectively
Successor JObs :
ex:
Code: |
1. JOB A >>>triggers >>> JOB B>>>> triggers JOB C
2. JOB D >>>triggers >>> JOB E (but E is dependent on completion of JOb B)
|
Now we have 2 job streams JOB A & Job D . Here Job E will be a successor job to JOB B because it has to run only after the successful completion of JOB B even though it is triggered by JOB D. It will wait in the queue untill JOB B completes.
Triggered by jobs:
Same explanation as case 1
Dependent jobs :
Refer example 2. Job E is dependent on Job B
Hope this helps...
Cheers
Kolusu _________________ Kolusu
www.linkedin.com/in/kolusu |
|
Back to top |
|
|
expat Intermediate
Joined: 01 Mar 2007 Posts: 475 Topics: 9 Location: Welsh Wales
|
Posted: Mon Mar 26, 2007 8:29 am Post subject: |
|
|
Using Kolusu's example above,
JOBA may be triggered by either an external event, e.g. the creation of a dataset, or may be triggered by the scheduled start time of the job. _________________ If it's true that we are here to help others,
then what exactly are the others here for ? |
|
Back to top |
|
|
Nic Clouston Advanced
Joined: 01 Feb 2007 Posts: 1075 Topics: 7 Location: At Home
|
Posted: Mon Mar 26, 2007 9:50 am Post subject: |
|
|
Semantics time - To me, a trigger would be one of, but not exclusively, the events mentioned by expat. I would not say that JOBA triggers JOBB. I would take this to mean that JOBA either submits or releases JOBB whereas, in reality (probably), JOBA just finishes and JOBB is then submitted by the Job Scheduler. JOBA is a predecessor to JOBB which is a successor to JOBA.
JOBE would be fully described as dependent on JOBD as well as JOBB. If it is not dependent on JOBD what is it doing in that jobstream? _________________ Utility and Program control cards are NOT, repeat NOT, JCL. |
|
Back to top |
|
|
kolusu Site Admin
Joined: 26 Nov 2002 Posts: 12375 Topics: 75 Location: San Jose
|
Posted: Mon Mar 26, 2007 10:06 am Post subject: |
|
|
Quote: |
JOBE would be fully described as dependent on JOBD as well as JOBB. If it is not dependent on JOBD what is it doing in that jobstream?
|
Nic Clouston,
JOBE is implicitly dependent on JOB D and explicitly dependent on JOB B JOB A & JOB D are 2 different job streams. They can start independently. Ofcourse JOB E is dependent on JOB D as it runs only JOB D stream is activated. However it has to wait until JOB B completes.
Let us say JOB D stream triggered at 6 AM this morning and JOBE was in the queuby 6:30 AM
JOB A stream did not kick off till 10 AM. Once kicked off JOB B completed by 11:30 AM. So Job E will be in wait mode until then and kicks of immediately as soon as JOB B completes.
Kolusu _________________ Kolusu
www.linkedin.com/in/kolusu |
|
Back to top |
|
|
navhin Beginner
Joined: 26 Mar 2007 Posts: 20 Topics: 7 Location: india
|
Posted: Mon Mar 26, 2007 11:46 pm Post subject: |
|
|
i think i am getting an idea......thanks
let me have some more clarification.
if job a triggers job B , then it does'nt imply that the output of job A will be used by job B as input.
but job E is a successor of job B, then the output of job B will be used by job E.
Am i getting it right? _________________ navhin |
|
Back to top |
|
|
Nic Clouston Advanced
Joined: 01 Feb 2007 Posts: 1075 Topics: 7 Location: At Home
|
Posted: Tue Mar 27, 2007 3:22 am Post subject: |
|
|
If a job is dependent on another job (B on A in this case) then there SHOULD be a dependency on some sort of data between the two otherwise why hold up job B?
BUT it is common practice to have a start and/or end job which would be an IEFBR14 - or even a dummy 'job' to provide a convenient 'link' point between applications or 'hold' point if a set of jobs need to be held for some reason. _________________ Utility and Program control cards are NOT, repeat NOT, JCL. |
|
Back to top |
|
|
navhin Beginner
Joined: 26 Mar 2007 Posts: 20 Topics: 7 Location: india
|
Posted: Tue Mar 27, 2007 5:16 am Post subject: |
|
|
nic clouston,
I am actually asking for the difference between trigger and dependency.
if both are same then the value in triggered job , successor job and dependant job fields should be the same jobs.
when viewed in CA7, it is actually not and they have different job names in the respective fields. _________________ navhin |
|
Back to top |
|
|
Nic Clouston Advanced
Joined: 01 Feb 2007 Posts: 1075 Topics: 7 Location: At Home
|
Posted: Tue Mar 27, 2007 5:33 am Post subject: |
|
|
A trigger is something that fires something else off - the completion of JOBA triggers (sets off) JOBB.
A dependency is a 'physical' relationship eg JOB X creates a file which JOB Y needs so JOB Y is dependent on JOB X. This is also known as a predecessor/successor relationship - JOB X is a predecessor to JOB Y. In turn, JOB Y is dependent on JOB X. Also, in this case, when JOB X finishes that completion triggers the submission of JOB Y. _________________ Utility and Program control cards are NOT, repeat NOT, JCL. |
|
Back to top |
|
|
navhin Beginner
Joined: 26 Mar 2007 Posts: 20 Topics: 7 Location: india
|
Posted: Tue Mar 27, 2007 8:00 am Post subject: |
|
|
nic clouston,
so job A need not necessarily give any file to job B.
triggering is upto scheduler level only.
is it? _________________ navhin |
|
Back to top |
|
|
kolusu Site Admin
Joined: 26 Nov 2002 Posts: 12375 Topics: 75 Location: San Jose
|
Posted: Tue Mar 27, 2007 8:06 am Post subject: |
|
|
navhin wrote: | nic clouston,
so job A need not necessarily give any file to job B.
triggering is upto scheduler level only.
is it? |
Just because JOB B gets triggered by JOB A does not mean it will read in the datasets created by JOB A.
JOB A can be directly updating a DB2 table/IMS database. And JOB B reads the same. So you would run JOB after completion of JOB A. 2 ways to do that
1. Trigger the JOb B by JOB A
2. Put a dependency on JOB B for the completion of JOB A
Kolusu _________________ Kolusu
www.linkedin.com/in/kolusu |
|
Back to top |
|
|
|
|