"these days the IPL process is pretty much an automated cinch that takes less than 5 minutes"
The time depends upon a lot of things... and the outage is longer than the actual IPL, as measured at our shop the outage is from when online systems (TSO, CICS, IMS, Web applications) come down, to when they are available again. That's longer than 5 minutes at our shop, but brings up an interesting (to me) topic: Do any of you "tune" the process of bringing the system down and back up? I'm starting to look at this - we use AF/Operator to bring everything except JES2 up and down. The previous "owner" of the product, instead of making an event-driven automation based on message traps, put in a lot of 15 or 30 second WAITs (i.e. "Start VTAM, wait 30 seconds, Start TSO"). So we have a lot of easy speed-ups due to that - but there are other, perhaps more sublte, things I wonder about: 1. A lot of the automation issues messages like "about to start VTAM".. there's acually quite a flood of messages during our IPL. Are we slowing down waiting for the 2074/emulator to handle all of those? 2. Does VTAM process its start l ist sequentially? If so, would I be better off issuing VARY ACT commands for all of the major nodes to take advantage of VTAM's parallelism? I'm guessing that the 24/7-via-Sysplex crowd doesn't have as much of an issue, since their public face is always up even if one of the members of the plex bounces for maintenance. Tim Hare Senior Systems Programmer Florida Department of Transportation (850) 414-4209 ---------------------------------------------------------------------- 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
