Re: Near-fatal OOPS waiting to happen in PDM (or THANK GOD for CONFIRMATION SCREENS!)

On 4/18/2011 4:33 PM, CRPence wrote:

On 4/18/11 2:39 PM, Gqcy wrote:

That confirmation screen bit me the other Sunday...

I wondered how come the system hadn't come up an hour after I issued
the PWRDWNSYS.

(I have since added the envvar to suppress it...)

On 4/18/2011 2:28 PM, Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx wrote:

Never happened to me..but i've heard the stories...IBM finally put
a confirmation screen on PWRDWNSYS...wonder what took them so long
LOL

I still recall when Simon had originally, humorously described his views
on a confirmation ever becoming an option for that command. He almost
certainly had implemented the environment variable for *SYS or changed
the command default on any release the CONFIRM parameter had since been
implemented and defaulted to *ENVVAR. Enjoy... :-)
http://archive.midrange.com/midrange-l/200209/msg00229.html

Regards, Chuck

I went back to that job log to see the timing...

I had received my "System ended to restricted condition" prior to typing in my PWRDWNSYS command.

I pressed enter on my PWRDWNSYS option(*IMMED) restart(*YES) at 09:04:26.649749

The next entry in the job log is "Image catalog PTFCATALOG unloaded.." at 09:04:45.386975, 18 seconds later!!!

I seem to remember I sat at the console until the screen went away, maybe about 5 or 6 seconds after I pressed enter...

Has anyone else noticed if the confirm screen lags???


-gerald