On Friday, 01/13/2006 at 03:29 CST, Mike Walter <[EMAIL PROTECTED]> wrote: > We have a new itsy-bitsy OS/390 guest (as itsy-bitsy as OS/390 ever gets). I'd > like to automate all prompt responses at its console via PROP or VM:Operator so > that we are free to bring VM up and down with the barest (if any) operator > interaction for this guest. > > But it does not appear that OS/390 wants to come completely up without a 3270 > console (which can't be easily captured and responded to anyway). I have > recollections of Melinda having managed to do this with her MVS guests at > Princeton. After many google, VMESA-L, and VMSHARE searches I was unable to > find anything specific (other than "she did it"). Maybe it relied on LDEVs? > Does anyone remember the technique? > > BTW, even though 01F is not listed as a console in it's gen, or it's > SYS1.PARMLIB(CONSOL00) member, or in the IODEF, OS/390 and even z/OS will begin > to IPL using 01F as a 3215. At some point fairly early it just stops > responding. Still it's terrific when there are IPL errors that display for a > nanosecond on a 3270 before the 3270 screen clears and is replaced with a HCP > Wait State message telling you to read the message that just cleared. The only > other way of capturing the message is probably with a high-speed videocam.
You are seeing z/OS use the linemode integrated console, not the 3215 (MVS doesn't know how to use a 3215 any more). 1. Add a DEVNUM(SYSCONS) entry to CONSOLxx. This enables z/OS to use the integrated linemode console. 2. Add VARY CN(*),ACTIVATE as the first thing in COMMNDxx. This puts MVS in PD mode, forcing him to use SYSCONS. You then use CP SEND CP MVSUSER VINPUT VMSG some-mvs-command Alan Altmark z/VM Development IBM Endicott
