We do something similar for other tasks. Set up an MPF exit to trigger on a message, say $HASP492 JES2 ALL-MEMBER WARM START HAS COMPLETED
Have the exit issue a START JESDEP command. Create a procedure called JESDEP (start JES dependant tasks) that uses program COMMAND (from www.cbttape.org) or similar to issue start commands for the tasks you want. Alan -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of SUBSCRIBE IBM-MAIN M. Ioia Sent: Wednesday, December 17, 2008 20:57 To: [email protected] Subject: How to delay until JES2 has finished startup 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 ---------------------------------------------------------------------- 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
