Thanks Alan and David, I'll try to work with the Integrated System Console (linemode) since it looks a LOT easier and cleaner than RXLDEV (glad to see that all my old brain cells are not yet totally fried; I did remember part of the solution even if I could not find references during searches).
Prior to the Integrated System Console it would have been nasty. It would have been a lot easier if 3215 support was never dropped in the first place. What a complete pity (ask anyone dealing with a 2nd level VM or OS system). Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not my employer's. "David Boyes" <[EMAIL PROTECTED]> Sent by: "VM/ESA and z/VM Discussions" <[email protected]> 01/13/2006 03:51 PM Please respond to "VM/ESA and z/VM Discussions" <[email protected]> To [email protected] cc Subject Re: Automated OS/340 guest IPL using PROP (or VM:Operator) > 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? Melinda is on vacation -- must be tough being retired. The code is on one of the older VM Workshop tapes (I seem to remember the UKY one). It used RXLDEV to drive a virtual device and a whole lot of magic to determine what had changed in the virtual screen image she maintained from the LDEV, which was then fed to PROP like a proper operating system. It then responded using VINPUT. IBM occasionally wonders why VSE survives. It's because VSE doesn't do half-ass stuff like dropping linemode console support and actually tries to get along nicely with VM. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.
