After extensive searching, I could not find a best practice way of delaying the startup of some STCs until JES has completed its startup.
By best practice, I mean, that the solution should be as pure z/OS as possible. Ideally, a command or option that implies 'START xxx' only after JES is started. Maybe an exit of some sort? I'm aware of some automation solutions that can do this based on message id triggers, and some homegrown SLEEP or DELAY commands. And of course there is always the human eye, that watches for the right message before continuing. But my strategy is always to first search for the solution with the least amount of additional software to acquire or maintain. If I cannot find one, then I consider the next best solution. I appreciate any input. Thanks. ---------------------------------------------------------------------- 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
