I agree that a cleanly shutdown system would be nicer to start with. However, we're using a flash copy-- the source system is quiesced, data is flashed in the V7000 library (which creates a 'thinly provisioned' copy of the source system), then the source system is un-quiesced. This is a ~90 second inter ruption on the source system that no one is supposed to notice. A normal shutdown is not in the cards.

The flash copy is identical to the source system at the instant the copy was created. Which means files are flagged as 'open,' access paths have dangling pointers, etc. When the process IPLs the copy, it looks as if power had dropped and everything just ended. So the IPL has to close the files, end the jobs, and clean up the residue from an abnormal termination. And tell us about everything that was running and had to be put away.


Paul E Musselman

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Wednesday, April 30, 2014 4:29 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Break Messages During IPL - stopping them!


If you can get your shutdown to be normal instead of abnormal, your IPL will be quicker and cleaner. IPLs do more work following an abnormal shutdown.
We found this years back during an upgrade, shutdown wasn't normal.
We also found the shutdowns weren't being done properly, *CNTRLD


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Musselman, Paul
Sent: Wednesday, April 30, 2014 4:21 PM
To: Midrange Systems Technical Discussion
Subject: RE: Break Messages During IPL - stopping them!


Thanks for the idea. We tried changing QSYSOPR profile DLVRY(*NOTIFY) before the flash, but it didn't take. The messages still broke.

I halfway think that the OS knows it was an abnormal termination and wants to make sure you know everything that was running when the system went down. Worst part is that about 2 steps later in the startup process messages start 'stacking up' in the message queue and you can respond to them when you get around to them. ):

--Paul E Musselman

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jack Kingsley

Is it possible to change QSYSOPR profile default message delivery parm.

On Wed, Apr 30, 2014 at 9:19 AM, PaulMmn <PaulMmn@xxxxxxxxxxxxx> wrote (in part):

Is there any way to suppress *INFO messages, or put the [QSYSOPR]
message queue into *NOTIFY mode during an IPL from an Abnormal Termination?

Thanks! Our "ENTER" fingers will be overjoyed!

--Paul E Musselman

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2015 by MIDRANGE dot 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 here. If you have questions about this, please contact