This is a very cool technique for debugging "mysterious" IPL slowdowns.
You don't even need a dump - if you run this IPCS command on a running system, the IPLDATA STATUS command will tell you how long each module in the IPL process took to perform its function when that system was IPLed - even days later. Brian On Wed, 16 Jul 2008 16:54:29 -0400, Jim Mulder wrote: >IBM Mainframe Discussion List <[email protected]> wrote on 07/16/2008 >04:35:28 PM: > >> Pat, in your situation try running the IPCS VERBEXIT BLSAIPST. >> >> It shows the various phases of NIP and the timing. Maybe you can >> pinpoint where the delay has occurred. > > The documented way of invoking that function is > > IPLDATA STATUS > >Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY > ---------------------------------------------------------------------- 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
