useless message at IPL

I made some changes to by UNIX BPXPRMnn members to test going to a sysplex root. I IPL'ed the system. There were problems. But the message from z/OS is useless. It tells me to refer to the HARDCOPY LOG. Like somebody has a 3287 printer any more? Or any printers? (we don't! All print is outsource

Re: useless message at IPL

On Tue, Jan 5, 2010 at 11:51 AM, McKown, John wrote: > I made some changes to by UNIX BPXPRMnn members to test going to a sysplex > root. I IPL'ed the system. There were problems. But the message from z/OS is > useless. It tells me to refer to the HARDCOPY LOG. Like somebody has a 3287 > printer

Re: useless message at IPL

McKown, John wrote: I made some changes to by UNIX BPXPRMnn members to test going to a sysplex root. I IPL'ed the system. There were problems. But the message from z/OS is useless. It tells me to refer to the HARDCOPY LOG. Like somebody has a 3287 printer any more? Or any printers? (we don't! A

Re: useless message at IPL

IIRC, the NIP messages are saved in memory until JES2 comes up and they can be written to SYSLOG. If you don't get to that point then you should take a stand alone dump, and you should be able to read them there. >>> "McKown, John" 1/5/2010 11:51 AM >>> I made some changes to by UNIX BPXPRMnn

Re: useless message at IPL

> -Original Message- > From: IBM Mainframe Discussion List > [mailto:ibm-m...@bama.ua.edu] On Behalf Of Gabriel Tully > Sent: Tuesday, January 05, 2010 1:30 PM > To: IBM-MAIN@bama.ua.edu > Subject: Re: useless message at IPL > > McKown, John wrote: > >

Re: useless message at IPL

On Tue, 5 Jan 2010 16:26:06 -0500, Scott Rowe wrote: >IIRC, the NIP messages are saved in memory until JES2 comes up and they can be written to SYSLOG. If you don't get to that point then you should take a stand alone dump, and you should be able to read them there. > Scott, You are correc

Re: useless message at IPL

Could you please be more explicit about the message you did see, and possibly about the messages you eventually found in the hardcopy log (SYSLOG)? You wrote >But when NIP was waiting for my reply, I could not see what was wrong so that I could fix it What message was it waiting for you to rep

Re: useless message at IPL

> -Original Message- > From: IBM Mainframe Discussion List > [mailto:ibm-m...@bama.ua.edu] On Behalf Of Peter Relson > Sent: Wednesday, January 06, 2010 6:55 AM > To: IBM-MAIN@bama.ua.edu > Subject: Re: useless message at IPL > > > What message was it

Re: useless message at IPL

> -Original Message- > From: IBM Mainframe Discussion List On Behalf Of McKown, John > > [ snip ] . . . I guess what it really > means is that I should never update an in-use member of PARMLIB, but copy it to a different suffix, > modify it, then point to the modified PARMLIB member. That

Re: useless message at IPL

It should be noted that early IPL messages can be written to the HMC system console in addition to/or instead of the z/OS NIP console. While the HMC system console has a number of usability problems, it does allow scrolling backward to see messages. I'll bite, how do you make NIP/IPL message

Re: useless message at IPL

> -Original Message- > From: IBM Mainframe Discussion List > [mailto:ibm-m...@bama.ua.edu] On Behalf Of John Kelly > Sent: Wednesday, January 06, 2010 9:21 AM > To: IBM-MAIN@bama.ua.edu > Subject: Re: useless message at IPL > > > It should be noted that early

Re: useless message at IPL

: > > -Original Message- > > From: IBM Mainframe Discussion List > > [mailto:ibm-m...@bama.ua.edu] On Behalf Of Peter Relson > > Sent: Wednesday, January 06, 2010 6:55 AM > > To: IBM-MAIN@bama.ua.edu > > Subject: Re: useless message at IPL > > > &

Re: useless message at IPL

In , on 01/05/2010 at 10:51 AM, "McKown, John" said: >Like somebody has a 3287 printer any more? Or any printers? Virtual 1403 under z/VM? -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see We don't care. We don't have

Re: useless message at IPL

> -Original Message- > From: IBM Mainframe Discussion List > [mailto:ibm-m...@bama.ua.edu] On Behalf Of Don Imbriale > Sent: Wednesday, January 06, 2010 10:01 AM > To: IBM-MAIN@bama.ua.edu > Subject: Re: useless message at IPL > > I have found command SETOMV

Re: useless message at IPL

In , on 01/05/2010 at 04:11 PM, "McKown, John" said: >Yes, it did go to HARDCPY in the CONSOLnn member. Which is set to SYSLOG. >Which is a SPOOL dataset. Which really means that these messages are kept >somewhere until JES comes up. If it's in a situation where you took a dump, you can retri

Re: useless message at IPL

In , on 01/06/2010 at 08:04 AM, "McKown, John" said: >I guess what it really means is that I should never update an in-use >member of PARMLIB, but copy it to a different suffix, modify it, then >point to the modified PARMLIB member. Or use the PARMLIB syntax checker. Or both. -- Shmu

Re: useless message at IPL

Back in OS/390 R5 days I was presented a standalone dump where the exact same problem (a syntax error in bpxprm on a test system that nobody cared about but that *was* part of a productive parallel sysplex) had brought down a productive system due to the fact that the message prompting for the n

Re: useless message at IPL

On 6 Jan 2010 22:19:29 -0800, in bit.listserv.ibm-main you wrote: >Back in OS/390 R5 days I was presented a standalone dump where the exact >same problem (a syntax error in bpxprm on a test system that nobody cared >about but that *was* part of a productive parallel sysplex) had brought down >a

Re: useless message at IPL

>Maybe I am off base but if a message is about something that can stop >an IPL, then it should be viewable on the console where the IPL is >taking place. If it isn't and can't be found when IPL quits, I >believe that should be a sev 1 APAR with no FIN. Agreed completely. But believe me, I was VER