On Thursday, 10/29/2009 at 04:08 EDT, "Schuh, Richard" <rsc...@visa.com> wrote: > When the menu is produced on the designated console (which is what the > loadparm does), you can change the name of the module to load, the name of the > CONFIG file, the location of the parm disk, and the OPERATOR console > address. The changes are not permanent, reverting to their old values for the > next IPL.
The request was for a method that does not require the SAPL screen. Kris was right, there is no such method. Only the filename of SYSTEM CONFIG can be specified on the LOADPARM without bringing up the SAPL screen. E.g. LOADPARM FNABC will cause FN=ABC to be added to the SAPL parms, overriding any burned-in specification. > One quirk - if you do specify cons=addr via the menu, it replaces both the > OPERATOR and emergency console lists with that single address for the > duration of that IPL. That's correct for OPERATOR_CONSOLES, but if it's happening for the emergency console list, it's a bug. Here's what the book says: If the CONS=addr or CON=addr parameter was specified on the Stand-Alone Program Loader (SAPL) panel to specify a console address and this console address is not already specified on the EMERGENCY_MESSAGE_CONSOLES statement, it is added to the list of emergency message consoles. When you specify a console on the LOADPARM, SAPL creates a CONS=addr entry and the above rule applies. Alan Altmark z/VM Development IBM Endicott
