As long as you don't specify SUB=MSTR for the other started tasks the tasks won't start until JES2 comes all the way up (after the $S) or if you specified NOREQ on the JES startup, they will start when JES automatically does the $S.
We have a product that allows you this kind of control, and command scripting for very sophisticated system automation as well, and it's licensed at $2,500 for members of IBM-MAIN, but it doesn't appear that you need something like that when all you want is for the started tasks to wait for JES to initialize. Brian Westerman ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
