We've seen cases where powering off a device may not be enough to convince
NIP that a device is not available as long as the controller is functional.
Powering off the controller is a bit risky given the age and increasing
fragility of the hardware. Resorting to different IODFs seems laborious and
error prone.
This technique will work for sure. Identify the chpid that drives the 3174.
Go into the HMC 'Control Chpids' screen or whatever it's called and put
just that one chpid offline. Guaranteed that all your messages will now go
to the HMC Operator Interface. When you're done, go back and put that chpid
online again, even during the current IPL for system messages. Simple and
foolproof.
.
.
JO.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]
John Mattson
<[EMAIL PROTECTED]
EPSON.COM> To
Sent by: IBM [email protected]
Mainframe cc
Discussion List
<[EMAIL PROTECTED] Subject
.EDU> Controlling where first IPL
messages and replies go
05/06/2008 01:37
PM
Please respond to
IBM Mainframe
Discussion List
<[EMAIL PROTECTED]
.EDU>
I am still running 3174's connected by adaptors to Escon channels
for my MVS consoles. Not elegant, but it works. For normal production
work, I want all of the IPL, and other messages to go to the attached
consoles because that is what the operators are used to. But for testing
I would like to see all of this going to the HMC's "Operating System
Messages". I have found that by leaving the consoles out of the IODF
using the "Operating System configuration" "Consoles", that I can
accomplish getting the messages to the HMC. Is there an easier way to
switch between where the messages, especially the early IPL messages go?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
