Based on your comment I guess either the operator did not specify a loadparm, even when he was instructed to do so, or the loadparm was not
recognized for some reason. Hm, well, I can't guess what is would be. Nex t IPL we can look into it. I did some testing with a guest VM. IPL with known consoles, consoles tha t are not in the system config etc. It is a bit more clear now. I even managed to play with a SYSC console using CP SEND commands from a CMS use r (nice). I agree, during a regular IPL there is no actual need for operator intervention. We do not even need to change parameters when we IPL to activate (CP) serviced components. We always change the CF1 and keep the CF2 as backup/fallback. We only need to use the second parmdisk in case o f some failure. And there came my point in this thread, in case of a proble m we still need a way to select a different parmdisk or to have a way to start VM with noautolog. So it would be interesting to look into a more automated IPL procedure. (and educate the operators that claim an IPLPARM must always be used) Anyway, I have some clues to setup some new IPL procedures. Thanks for your help. Berry.
