We use the expedient of a globally defined command file we called "WAITFOR".  The
idiosyncrasy is that one must enclose the parameter in "triple quotes".  (Double
quote + single quote + parm + single quote + double quote.)  We currently use a
pause of 20 seconds, although this has changed over the years.  The result is a
SHOWTIME displayed in the $STDLIST until the job it is waiting for is finished.

This can be used by any kind of PARENT job and nest as deep as you like.  No
message files required.  (In a sense, it treats the job it is waiting for as the
message.)

The only major drawback is that it may wait forever on a runaway job, but THAT's
another kind of problem.  Or you can do something really stupid and have nested
jobs "WAITFOR" each other.

USER DEFINED COMMAND FILE:  WAITFOR.COMMAND.SYS

PARM JOBNAME
SETVAR JSC 1
WHILE JSC>0
   PAUSE 20
   SHOWTIME
   MAIN.PUB.VESOFT;INFO="SETVAR JSC JSCOUNT(!JOBNAME)"
ENDWHILE

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
The end result looks like this in the $STDLIST:

WAITFOR.COMMAND.SYS "'jobname,myuser.myacct'"
SUN, APR 24, 2005, 10:18 PM


SUN, APR 24, 2005, 10:19 PM


SUN, APR 24, 2005, 10:19 PM


SUN, APR 24, 2005, 10:19 PM

...

(Until it starts doing things again.)
--
BT
NNNN



Tracy Johnson
Justin Thyme Productions
http://hp3000.empireclassic.com/

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