It depends on what your production LPAR is needed FOR.  If it's 24/7/365 
on-demand global transaction processing, I'd bet any IPL that wasn't 
scheduled at least 2 weeks in advance would cause major headaches to your 
user base.  If it's used for normal 9 to 5 transaction processing and 
nightly batch, and you've got a slow day every couple of weeks (say, a 
Thursday or a Sunday that's not at the end of the month) I don't see too 
much danger.

By the bye, who are "they"? Users? Tech Support? The network guy that's 
slaving World of Warcraft out of one of your zLinux pseudoframes under USS? 

Thing is, you should IPL *sometimes* - such as when you're doing major 
software upgrades, or if you've got an IO contention issue spiraling out 
of control, or if your dwarf is getting totally pwned in the aforementioned 
WoW pseudoframe.

A little more data would probably help.

Many thanks.

Doc Farmer
Senior Security Specialist
InfoSec, Inc.

Website: http://www.InfoSecInc.com
e-Mail: [email protected]
LI: http://www.linkedin.com/in/DocFarmer

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Tommy Tsui
Sent: Wednesday, September 02, 2009 9:09 PM
To: [email protected]
Subject: How often IPL a production LPAR (any good practice)

Hi all,

Is there any concern if we didn't IPL a LPAR over three months. Is there  
any good practise to follow from IBM. They always replied LPAR never needs  
IPL because of 24 x 7.

Any comment will be appreciated

----------------------------------------------------------------------
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

----------------------------------------------------------------------
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

Reply via email to