Although we have only 'static' LPARs--which I interpret as always running the same SYSNAME in the same LPAR--you can handle virtually any combination of IPL parms by creating unique Load profiles with names suggesting their function. The idea of editing--entering characters on a keyboard--in preparation for a normal IPL strikes me as unacceptably risky. It's not about knowledge transfer. It's the consequences of a simple finger check at the single most crucial point in an IPL. I would not like to have to explain to management why I routinely subjected my operators to that level of jeopardy.
. . JO.Skip Robinson SCE Infrastructure Technology Services Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] From: Mark Zelden <[email protected]> To: [email protected] Date: 06/15/2012 06:19 AM Subject: Re: Change IEASYMxx via operator prompt Sent by: IBM Mainframe Discussion List <[email protected]> On Fri, 15 Jun 2012 09:17:39 +0200, R.S. <[email protected]> wrote: >W dniu 2012-06-15 01:07, Skip Robinson pisze: >> Our operators never 'change IPL address'. They select the appropriate LOAD >> profile on the HMC before IPL. We don't find it necessary on a regular >> basis, but each LOAD profile can contain a unique LOADPARM value where the >> specified LOADxx suffix points to a unique IPLPARM member. That way no one >> has to edit anything on a regular basis. Each LOADxx can specify a unique >> concatenation of IEASYMxx members. All controlled by LOAD profile. > >That's really good approach for "static scenario" - always the same >system is IPLed of given LPAR. However sometimes there is a need to >"dynamically" change the system, for example this week we run MVS123, >next week we will run MVS456 on the same LPAR. In such case you have to >change IPL parameters. Of course there is still possibility to choose >IEASYMxx inplicitly, via LOADyy. > Exactly what I have to do. We have a couple of sandbox sysplexes (2 LPARs per sysplex) that have "static lpars". But I have to share a couple of other monoplex sandbox environments in a single LPAR. One of them is able to share the LOADxx member with the other sandboxes (the one up and running most often). The other one is just IPLed with a different LOADxx member when we need that system active. -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:[email protected] Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
