|
Hello, Andy: This happened once when I was visiting a client site; they had hired a new person, and gave her a manual with all of the commands, and sat her down at a terminal and said, "Here, learn these commands." When she got to the PWRDWNSYS command, she pressed Enter. Suddenly, people were running around, trying to find out what had happened. Luckily this customer had two systems, each a mirror of the other, so things just started to "fall-over" gracefully to the other machine. Meanwhile, there IS one thing you could do. In this case, they had pressed enter with PWRDWNSYS default of OPTION(*CNTRLD) so, we went in and issued: PWRDWNSYS OPTION(*IMMED) RESTART(*YES) This way, at least the system shut down much quicker and then immediately started back up again. So, the whole process of going down and coming back up again was shortened somewhat... Again, in this particular case, the users were able to continue their work, because of the "hot" back-up system. Regards, Mark S. Waterbury ----- Original Message ----- From: "Andy Nolen-Parkhouse" <aparkhouse@attbi.com> To: <midrange-l@midrange.com> Sent: Thursday, September 05, 2002 9:32 AM Subject: RE: PWRDWNSYS - Trivia > Justin, > > You remind me of the time my boss was test-prompting some commands to > check their defaults. For some reason, when he came to PWRDWNSYS, he > hit <enter> instead of <f3>. He ran over to my desk and we tried to > salvage the situation (this was in the middle of a production day), but > there was nothing we could do. > > I don't think there is a way to stop it. > > Thanks for the memories (I think). > > Regards, > Andy Nolen-Parkhouse > > > On Behalf Of Haase, Justin C. > > Subject: PWRDWNSYS - Trivia > > > > If a user were to take the PWRDWNSYS command from a command line, just > > smack > > enter to take defaults (controlled/30 minutes I think) - is there ANY > way > > to > > cancel that, or does it have to do its thing all the way through? > > > > No pending emergency here mind you, just curious. > > > > Thanks. > > > > Justin C. Haase > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.