> I confess that I have not tested this maneuver. Doesn't the OSM screen > close as soon as the operating system stops? Maybe not.
System Reset Normal does not close or clear Operating System Messages. > In any case, I do know this from experience: if the customer has > configured any NIP console to an OSA device, NIP messages will go only to > that device and not to the HMC at all. If a wait state occurs as discussed > here, the OSA device will go blank as previously asserted. The only way to > direct NIP messages to the OSM is to force offline (via HMC) the chpid > that supports the OSA device in the IODF. Afterwards the chpid must be put > back online in order to restore the operational environment. z/OS always selects one and only one NIP console, which is either the first available device in the list that is specified as NIP consoles in your IODF, or Operating System Messages on the HMC. I recommend that you do not define any devices as NIP consoles in your IODF. Then Operating System Messages will always be used as the NIP console. This does not prevent you from defining an OSA device as a console in CONSOLxx, and thus using it as an MCS console. If you really want to use an OSA device as your NIP console most of the time, and OSM only for second-failure data capture, you could maintain 2 IODFs which are identical, except that one has the OSA device specified as a NIP console, and the other does not. Then your operator would only need to change the IODF specification in the Load Parameter in order to use OSM as the NIP console, which might be an easier operational procedure than forcing the OSA chpid (at the expense of the extra system programmer task of keeping 2 almost identical IODFs in synch). Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
