RE: executing jobs in sequence

From personal experience....I usually just have a controlling CL program

that executes the calls to the processing programs...if needed I add
some minimal restart logic so should something blow up in "step B" I can
fix the problem & resubmit the "driver" program to restart at "step B"
again.  As Charles Wilt stated earlier:
<snip>
Errors are supposed to be the exception rather than the rule.  Plan for
them, but don't expect them as normal.
</snip>
I totally agree..don't expect errors to be the rule...but plan for them
accordingly.  That way when you DO have issues you have a plan in place
for dealing with them. 


Thanks,
Tommy Holden


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, January 08, 2007 8:41 AM
To: Midrange Systems Technical Discussion
Subject: RE: executing jobs in sequence

I am not speaking from personal experience.
However I've heard that some prefer the Advanced Job Scheduler
(5722-JS1) 
from IBM vs the one that IBM provides with the operating system.  And it

is because you can do things like
If job A fails then don't run Job B, etc.
Along with some additional features.
http://www-03.ibm.com/servers/eserver/iseries/jscheduler/

Some people also prefer Robot.

Rob Berendt