Hello Kris,
You and John did hit the problem, at least part of it.
The OPERATOR is logged on to SYSC:
13:53:22 SYSC LOGON AS OPERATOR USERS = 1
The consoledefinitions in the SYSTEM CONFIG are:
Operator_Consoles DE00 DF00 0820 0400 0009 SYSTEM_Console SYSTEM_3270
Emergency_Message_Consoles DE00 DF00 0820 0400 0009
The problem here is the fact that we can't connect to DF00 just now, so
the VM was IPLled on the HMC with loadparm DF01. (DExx and DFxx are ICC
consoles) But DF01 is not in the console statements. 820, 400 and 009 do
not exist in that configuration.
But then the next question. If I specify a loadparm DF01 I would expect t
o
see at least the SA-IPL on DF01. Then I can specify CONS=DF01 to IPL an
d
start OPERATOR on DF01. (Just like a guest VM can be IPLled with loadparm
0009 and then started with CONS=0009) But we've never seen a SA-IPL
screen. Why then is VM started on SYSC? If a consoledefinition was
incorrectly specified I would expect to receive an HCP1010W. Why would th
e
SA-IPL either bypassed or automatically started. AFAIK there is no
operator that has pressed PF10 on a SA-IPL screen. Could is be that VM
(CP?) detects the console and can decide to IPL with it's defaults?
Anyway, we can test this behaviour. We still have one VM to IPL over ther
e
so we can try some different configurations. At least, also specify DF01
in the console statement.
Thanks,
Berry.
