I just made a test with a secondlevel z/VM system (it has 600-605, SYSG and SYSC as consoles in SYSTEM CONFIG) - #CP TERM CONMODE 3270#IPL xxxx LOADPARM CONS0009 - I DIAL to the secondlevel as 601, and logon to MAINT there - on the firstlevel system, I issue #CP DEF 9 1F - in the secondlevel's MAINT: SHUTDOWN REIPL ==> wait 1010 This proves that at SHUTDOWN REIPL CP did no longer look at the list of consoles in its SYSTEM CONFIG, it wanted 0009 and nothing else.
2011/6/22 Alan Altmark <alan_altm...@us.ibm.com> > On Tuesday, 06/21/2011 at 02:40 EDT, gclo...@br.ibm.com wrote: > > Is SYSC the unique restriction? > > Another legacy of the last millennium? > > "Restriction" against what? It is the one unifying console interface. It > works for all the OSes. If you know how to use it for one OS, you know > how to use it for the others, both on the HMC and via #CP VINPUT VMSG. And > it operates whether the guest is running in 3270 mode or 3215. > > Ideally, you shouldn't even have to code it in SYSTEM CONFIG. System_3270 > (SYSG) and System_Console (SYSC) should be the consoles of last resort. If > you don't specify any operator or emergency consoles, SYSG and SYSC are > what you get. If the 3270 session is started, you get that. If not, you > get the linemode console. Easy. > > The only time a 1010 would be given would be if an explicitly specified > console at IPL wasn't available for use. And I have to think about > whether I believe that SAPL parms or LOADPARM that are re-used on SHUTDOWN > REIPL constitute "explicitly specified" -- I don't think so. IMO, for the > purposes of abend restart and SHUTDOWN REIPL, that stored value is simply > prepended to the operator and emergency console lists. Just come up on > the next available operator console with a message that says "PREVIOUS > CONSOLE DEVICE 01F IS NO LONGER AVAILABLE". > > While we're Wishing, I would also wish that CP would accompany all IPL > wait states with a message to the integrated console, including "SPECIFIED > CONSOLE DEVICE 009 IS NOT A 3270". (Natch, the system has to be able to > come up far enough to allow CP to connect to SYSC!) The one wait state > with no message would be the one for "I can't establish a connection with > the integrated console - something is seriously wrong." (If SYSC doesn't > exist at all, that's a horse of a different color.) > > An always-on, always-there console changes the nature of traditional CP > error reporting. > > Alan Altmark > > z/VM and Linux on System z Consultant > IBM System Lab Services and Training > ibm.com/systems/services/labservices > office: 607.429.3323 > mobile; 607.321.7556 > alan_altm...@us.ibm.com > IBM Endicott > -- Kris Buelens, IBM Belgium, VM customer support
