Hey Skip, I guess documentation is the key for your case. I've worked in an outsource shop that had "no" issues without any operators phisically in the data center for 14+ years (that I'm aware of). IIRC, all customers had a very good documentation of which devices Ops could/should use for consoles and how to logon, etc. I'm also not aware of any way to find which is the NIP console from outside the HCD panels.
Regards, Lucas On Jun 9, 2015 11:18 PM, "J O Skip Robinson" <jo.skip.robin...@sce.com> wrote: > Thank you Radoslaw and others who have suggested that a) we don't need a > NIP console or b) we should be able to promulgate a list and be done with > it. I don't consider it a useful option to c) let people read the IODF and > figure it out for themselves. Really? Would that work in your shop? Your > operators are actually sysprog understudies chomping at the bit to get on > stage? (Pardon mixing of metaphors.) For us, that is so not a realistic > option. > > As for b), I did not burden the list with the reason I'd like to identify > valid NIP consoles externally. We have problems in the current IODF that > some LPARs in fact do not have a viable NIP console. I think I know how to > fix them, but I'd like a way to check my work after dynamic ACTIVATE > without having to actually IPL. A display command would be so much less > disruptive. > > As for a), there is a geographic issue that many on the list do not > experience. We have two data centers in California. Most of the current > operation staff is in Mexico with occasional involvement from India. (A > Google search on 'SCE IT' may be instructive.) There is literally not a > single 'Operator' with physical access to a true HMC. Operations staff can > get to our console application (VCC) over IP, or they can remote into an > HMC. As discussed at some length here in a recent thread, Java is at best > an iffy window into Operating System Messages. > > I'm only concerned about NIP replies. Once MCS has found his brains, we > can get to any LPAR through VCC. Hence the need for NIP consoles. > > . > . > . > 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 > jo.skip.robin...@sce.com > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of R.S. > Sent: Friday, June 05, 2015 2:22 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Identifying a NIP console > > W dniu 2015-06-04 o 16:37, J O Skip Robinson pisze: > > 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. > > Well, > IMHO only few need to know what is the NIP console. Why don't you allow > them to READ the IODF file? Is there any risk related to that? > Last, but not least: since (IMHO) NIP consoles are not changed frequently > the list of them can be simply documented in some way. > > -- > Radoslaw Skorupka > Lodz, Poland > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
