We have NSD Jobtime and JobRescue for production, but our project
manager is reluctant to spend $25G for the development environment. So,
we are charged with coming up with some way to daisy chain the job
streams, and preferably a good way to know what the last successful job
in the chain was. The latter should be easy enough with a ECHO
!HPJOBNAME>LASTJOB.PUB.

But I would like a nice clean and easy way to setup some sort of a
linked list or other mechanism using nothing but native HP 3000 MPE
capabilities, and maybe SuprTool if that helps with the linked list. I
expect that we will want set an HP var for jobs in the system logon UDC
that indicates whether we are running JobTime or not (so we can change
our minds without changing all these batches), and then test for that in
jobs to keep them in sync on both 3Ks. We would want to add code at the
end of each job stream to test for this var, and if we are not running
JobTime on that box, stream the next job in the chain. The ideal level
of abstraction would be an individual command file (so we only have to
paste a single command into each job stream), which in turn check the
JCW or CIERROR, and if that is OK, might use the current jobname as the
key to get the next jobname, and stream the appropriate job. We are not
yet sure how we want to handle errors, since this is development. Or, if
I knew a good way to test for when a job is running, we could write a
single job stream to stream each job in turn, wait for it to finish,
then check for errors, testing whether to stream the next job or not.

Although if anyone has any better approaches, please let me know. But
what I am looking for is good ways to make the above happen. Thanks.