Bob,
Do you always, **ALWAYS**, faithfully run "CPSYNTAX SYSTEM CONFIG fm" on
the just-changed SYSTEM CONFIG file after each and every change?
If not, start doing it now...
1- Write an EXEC to through which you always make changes to the SYSTEM
CONFIG file, and which runs CPSYNTAX so
you don't forget.
2- Add a comment block to the top of your SYSTEM CONFIG file reminding you
to run CPSYNTAX.
IBM should *JUST DO IT* to the distributed config.
3- Always keep back copies of your previous SYSTEM CONFIG files (maybe as
-1SYSTEM CONFIG, -2SYSTEM CONFIG, etc.)
so you can use them if something goes wrong with the latest change.
After an IPL fails, check the HCP for hardware messages. If you did not
have a console, you should have received a Wait State 1010 - which can be
looked up under CP message: HCP1010W
Precisely what happened depends on what CP saw when reading the SYSTEM
CONFIG file. Everything after the open comment (/*) was ignored. Odds
are that your OPERATOR_CONSOLES and EMERGENCY_CONSOLES statements were
after the open-comment.
Mike Walter
Hewitt Associates
The opinions expressed herein are mine alone, not my employer's.
"Bob Frankovich" <[EMAIL PROTECTED]>
Sent by: "VM/ESA and z/VM Discussions" <[email protected]>
12/21/2005 10:42 AM
Please respond to
"VM/ESA and z/VM Discussions" <[email protected]>
To
[email protected]
cc
Subject
MP3000-H30 IPL problems
We use one of the MP3000 Emulator Sessions for the Z/VM 4.4 console. This
morning, during a scheduled IPL, the operator entered SHUTDOWN REIPL on
this console. VM shutdown but no other messages appeared on the console
which was my 4 AM wakeup call. After several attempts over the phone, I
came to work where I treid several other things : Closed the sessions &
restarted them; entered a LOADPARM of E20 (the console address); did a
POWER ON RESET; even rebooted OS/2. All to no avail. I then entered a
LOADPARM of 01D (an address I had defined to OS/2 TCP/IP as an non-SNA
device to be used for a console). VM started coming up. During the start
up I noticed a message about an invalid comment in the SYSTEM CONFIG at
line xxx. Once VM was up I checked the SYSTEM CONFIG and sure enough,
there was a "/*" on that line without a "*/". I corrected this and IPL'ed
again from 01D - no error. I then IPL'ed without any LOADPARM and VM came
up on Address E20. Has anyone else had a similar problem or was the
errant "/*" really the problem ? I'm really at a loss to explain this so
any help will be appreciated.
The information contained in this e-mail and any accompanying documents may
contain information that is confidential or otherwise protected from
disclosure. If you are not the intended recipient of this message, or if this
message has been addressed to you in error, please immediately alert the sender
by reply e-mail and then delete this message, including any attachments. Any
dissemination, distribution or other use of the contents of this message by
anyone other than the intended recipient is strictly prohibited.
