...
It appears that the "normal" order is jobA, jobB, jobC, etc.,
but there are times when jobA can be skipped and the process
starts at jobB.  Also, you do not want the existence or not of
certain files to control the job flow.  As previously mentioned
you could write a simple "job checker" script to help:

 PARM jobID
 ANYPARM cmd
 # Verify if 'jobID' is an executing job. Expected jobID is
 # of the form: [#]J|Snnn or [jobname,]user.acct.
 # The 'cmd' parm is a CI command to execute when 'jobID' no
 # longer exists.
 errclear
 continue
 pause ![60*60];job=!jobID
 if cierror = 9032 then
    echo Job "!jobID" still exists one hour later!
 elseif cierror = 0 then
    # execute 'cmd'
    !cmd
 else
    echo PAUSE failed for job "!jobID" with CIERROR=!cierror
 endif


If the script is named "jchk" then it can be used as follows:

  :jchk 'jobA,user.acct' stream joba.group.acct
  :jchk 'jobB,user.acct' stream jobb.group.acct
  etc...

HTH,
 Jeff Vance, CSY

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *