After changing the virtual console address from 03E1 (matching the CONSOLE entry in CONSOLxx) to 0009 (matching no z/OS console definition) and reIPLing the guest, the linemode output went to SECUSER without artifacts, as it did on our old hosting environment.
I'm convinced based on the evidence that: * The old environment had the virtual console at 0009 * The old environment had the z/OS CONSOLE definition at 03E1 * The folks who ported our system over for us had logon access to the old environment, but did NOT have access to the VM directory entry for the guest * They thus made the logically correct decision to define the virtual console at 03E1 That was the "right thing to do", except it turned out to change the behavior in an unintuitive way. Now we know. Thanks 10**6 for all the thoughts and advice here! It was a bit of an odyssey but we got there. And this might be due an IBM-MAIN award for the longest thread without significant topic drift, at least in a while. No idea why, but that's rare here! ...phsiii ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
