This is what I was referring to, relating to NIP and IODF: https://www.ibm.com/docs/en/zos/2.4.0?topic=configuration-working-operating-system-consoles
The topic mentions both MVS and VM, so there may be some useful information. While I mentioned my request to have "...the NIP *device *be removed from IODF", I should have stated to have "... the NIP *CONSOLE* be removed from IODF". Yes, the device should be defined to allow CONSOLxx to make use of it once MVS has been initialized, but an IODF defined NIP CONSOLE is not required, making use of the hardware console in its absence. Maybe you're saying the same thing, just in VM speak?! On Tue, Jul 25, 2023 at 10:43 AM Jon Perryman <[email protected]> wrote: > > On Sunday, July 23, 2023 at 08:25:34 PM PDT, Steve Horein < > [email protected]> wrote: > > The only time I have seen NIP messages (those messages prior to VARY > > > CN(*),ACTIVATE being accepted) on a native MVS LPAR was when the NIP > device > > > Hi Phil, Sorry for the long delay.but I had other things to do. Steve may > have a possible solution. Let me put it into terms you can understand. > > Steve says there is 1 exception to the hardware console requiring V > CN(*),ACT to become the first active console during IPL. He says if you > disable all z/OS DEV(###) consoles, then the hardware console will > automatically activate because there is no other console available. I > believe this to be true but I have never tried this. There may be a couple > caveats that can be discussed later if it solves your problem. > This is simple to test. From the z/OS VM user, detach all devices > specified in PARMLIB(CONSOL##). At the moment, forget he mentions "NIP" > device because this is almost always included in PARMLIB(CONSOL##) which > means you would have detached it. This is so simple it's worth a try. > > > > On Sunday, July 23, 2023 at 08:25:34 PM PDT, Steve Horein < > [email protected]> wrote: > > The only time I have seen NIP messages (those messages prior to VARY > CN(*),ACTIVATE being accepted) on a native MVS LPAR was when the NIP device > defined in the IODF was not available, I believe due to some cabling > issues. In that situation, all NIP messages were routed to the SE/HMC > System Console. I had requested the NIP device be removed from IODF years > before, for that exact purpose, to assist with automation that uses > SYSCONS, and/or for diagnostics, but due to Fear/Uncertainty/Doubt, the > request was flatly denied. > > https://www.ibm.com/docs/en/zos/2.4.0?topic=system-nip-console > "If no NIP console is defined and ready, MVS™ will use the system console > as the NIP-time console." > > I have zero experience with zVM, so I do not know if that NIP message > behavior is the same when MVS is running as a guest. I just figured I would > pass along my anecdotal observations. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
