I remember back in the days of coax connected real 327x CRTs. Not all consoles were together in one room. Console operators had theirs, print and tape operators had theirs in separate rooms. If a NIPper was not defined explicitly, anyone who pressed <Enter> became king (or queen) of the hill. As in what's wrong with #%@^! system pound pound. Operator had to run around and find the active console. Especially fun in the case of Standalone Dump.
These days most shops like a bit more control. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Staller, Allan Sent: Thursday, June 04, 2015 1:06 PM To: [email protected] Subject: Re: Identifying a NIP console Not to answer your question directly, but ISTR an old article (can't find it at the moment) that suggests NIP consoles are not needed. The system will respond to the first console that presents an interrupt. HTH, <snip> NIP consoles are defined in the NIP Console List in the IODF. Other MCS consoles are defined as 3270-X devices and included in PARMLIB(CONSOLxx). Once a system is IPLed, NIP consoles also function as MCS if they are included in CONSOLxx. My question is whether there is any external way to distinguish the two types without delving into HCD. D C commands seem to display the same info for both types. Lots of folks can issue display commands, while HCD is a realm open to only a few. It would be nice to have a simple, general way to identify a NIP console. </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
