IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Difference between Successor job and trigger job


IBM Mainframe Forums -> CA Products
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
Rupesh.Kothari

Member of the Month


Joined: 27 Apr 2005
Posts: 463

PostPosted: Tue Jun 14, 2005 8:11 pm
Reply with quote

Hi all,

Can anyone tell me please what id difference between Successor job and trigger job and benefit of each as both are waiting for its predecessor?

Thanks in advance for you help.

Rupesh.Kothari
Back to top
View user's profile Send private message
priyesh.agrawal

Senior Member


Joined: 28 Mar 2005
Posts: 1448
Location: Chicago, IL

PostPosted: Tue Jun 14, 2005 10:55 pm
Reply with quote

Successor & Triggered both are the jobs starts execution only on completion of a specified jobs, the difference lies in Successor jobs dont use any output from its predecessor jobs.

One use of successor jobs is in checking that a predecessor has run within a specified number of hours.

Regards,

Priyesh.
Back to top
View user's profile Send private message
radhakrishnan82

Active User


Joined: 31 Mar 2005
Posts: 435
Location: chennai, India

PostPosted: Wed Jun 15, 2005 11:01 am
Reply with quote

Quote:
Successor & Triggered both are the jobs starts execution only on completion of a specified job


Triggering can be set at the dataset level too.Once the job creates a particular dataset then it will trigger the job.This factor is one of the differentiation that it has with the successor job.
Back to top
View user's profile Send private message
Mohankalyan99

New User


Joined: 06 Apr 2005
Posts: 16

PostPosted: Wed Jun 15, 2005 3:57 pm
Reply with quote

Hi,

Triggered means once Job A is completed Job is going to trigger.
Successor means Before execution of Job B it checks whether Job A is completed or not.

Let me know if you still have any doubts.

Regards
Kalyan.
Back to top
View user's profile Send private message
Rupesh.Kothari

Member of the Month


Joined: 27 Apr 2005
Posts: 463

PostPosted: Wed Jun 15, 2005 4:26 pm
Reply with quote

Hi Kalyan,
Thanks for your response.
But in both the case (Triggering and successor) jobs has to wait to complete the predecessor jobs.

Could you please explain me when we can use triggering and when successor as both are same.

Thanks & regards
Rupesh.Kothari
Back to top
View user's profile Send private message
priyesh.agrawal

Senior Member


Joined: 28 Mar 2005
Posts: 1448
Location: Chicago, IL

PostPosted: Thu Jun 16, 2005 12:15 pm
Reply with quote

A difference b/w Successor & Triggered Jobs is that, Triggered Job gets start immediately after complition of its earlier job. But It is not a compultion to a successor job, It will get start at Its own time.

Quote:
But in both the case (Triggering and successor) jobs has to wait to complete the predecessor jobs.


Yeah, Its correct. In both cases later job waits completion of earlier.

Quote:
Could you please explain me when we can use triggering and when successor as both are same.


Suppose, Job A, runs 11:45 AM, needs two dataset to proceed.
One of it, from Job P, which it gets everyday 11:00 AM, other from Job Q, at 11:30 AM. So Job A can be a successor of Job P, but can't be triggered by Job P.

I hope it'll make U clear.

Regards,

Priyesh.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> CA Products

 


Similar Topics
Topic Forum Replies
No new posts Timestamp difference and its average ... DB2 11
No new posts Difference when accessing dataset in ... JCL & VSAM 7
No new posts What is the difference between Taskty... Compuware & Other Tools 2
No new posts Difference between VALIDPROC and CHEC... DB2 3
No new posts How to define transaction that trigge... CICS 3
Search our Forums:

Back to Top