RE: A CL program that runs several batch jobs, one after the other

I don't remember all the details and I don't know if this counts as "an
easy way" but this is basically how we did it years and years ago before
Advanced Job Scheduler.

The "master" clp submitted all the other jobs in reverse order, loading
all the jobs into the jobq's. As they were submitted, the job name, user
id, and job number from the completion message of the SBMJOB command was
captured and passed as parameters to the next submitted job. The last
step in the submitted job that received those parameters was to do a
RLSJOB with the passed parameters. So, a dependent job wouldn't run
unless the predecessor completed normally. And a predecessor that failed
could be resubmitted with the original dependent job information so that
when the new predecessor job completed normally the original dependent
job was released.

from: Booth Martin <booth@xxxxxxxxxxxx>
subject: A CL program that runs several batch jobs, one after the
other

A CL program that runs several batch jobs, one after the other

A CL program is calling several other CLs, many of which
have SBMJOB
commands in them. The next CL can not be run until the
previous CL is
completed.

It is entirely possible that I am making too big a deal out
of this. Is
there an easy way to make it run one step at a time?