Hello list,
I had the following question in July of this year. I just want add to the
archive the resolution of this problem.
Snip from July 2008
Our system is a 2096 U03 with three LPARs but no sysplex. Two LPARs are
production, one at z/OS 1.4 and a small one at z/OS 1.7. The current IODF
On Mon, 21 Jul 2008 07:06:23 +0200, Barbara Nitz [EMAIL PROTECTED] wrote:
*Obviously* you don't work here :-) Here I am fast with system dump cleanup
to keep the DASD pool empty. If anyone wants a dump longer than it takes me
to take a look at it, they should rename it to a 'keep' qualifier. I
.. I just can't resist...
The data collection for IPLDATA STATUS was just a little thing
I hacked together in OS/390 1.3 to help me find a starting point of
where to look when I got asked to help diagnose why did that IPL
take so long? problems.
Another Jim-Mulder-Special :-) It seems to me
] Subject
.EDU Re: IODF change causes next IPL to
hang
07/17/2008 10:45
On Fri, 18 Jul 2008 01:45:58 -0400, Jim Mulder
[EMAIL PROTECTED] wrote:
...
The data collection for IPLDATA STATUS was just a little thing
I hacked together in OS/390 1.3 to help me find a starting point of
where to look when I got asked to help diagnose why did that IPL
take so long?
On Fri, 2008-07-18 at 15:01 -0500, Patrick O'Keefe wrote:
None of our MVS system programmers knew about
this command. We don't know when our intermittant IPL problem
will strike again, but you can bet this command will be issued
afterwrds.
There are lots of things to see in a dump - I
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Jim Mulder
IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU wrote on
07/16/2008 04:35:28 PM:
Pat, in your situation try running the IPCS VERBEXIT BLSAIPST.
The documented way of invoking that function is
IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU wrote on 07/17/2008
09:00:16 AM:
A colleague asks, When are the 'official' start and end times (events)
that comprise 'IPL'?
From the IPLDATA STATUS output it appears that 'official start' occurs
after the IPLTEXT has been loaded and
Hello List,
Are system is a 2096 U03 with three LPARs but no sysplex. Two LPARs are
production, one at z/OS 1.4 and a small one at z/OS 1.7. The current IODF is
a version 5 level.
This weekend I activated a new IODF on the 1.4 system using the HCD dialogs
which completed successfully. I did
On Wed, 16 Jul 2008 14:33:44 -0500, Stephen Wolf
[EMAIL PROTECTED] wrote:
...
This weekend I activated a new IODF on the 1.4 system using the
HCD dialogs
which completed successfully. I did not do an activate on the 1.7 We
then
IPLed the 1.4 system and it just waited. The NIP console was not
On Wed, 16 Jul 2008 14:33:44 -0500, Stephen Wolf [EMAIL PROTECTED] wrote:
Hello List,
Are system is a 2096 U03 with three LPARs but no sysplex. Two LPARs are
production, one at z/OS 1.4 and a small one at z/OS 1.7. The current IODF is
a version 5 level.
This weekend I activated a new IODF on
Pat, in your situation try running the IPCS VERBEXIT BLSAIPST.
It shows the various phases of NIP and the timing. Maybe you can
pinpoint where the delay has occurred.
I've seen long delays when there are problems when the DASD goes into
some sort of error recovery and retries each device for
[EMAIL PROTECTED] Subject
.EDU IODF change causes next IPL to
hang
IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU wrote on 07/16/2008
04:35:28 PM:
Pat, in your situation try running the IPCS VERBEXIT BLSAIPST.
It shows the various phases of NIP and the timing. Maybe you can
pinpoint where the delay has occurred.
The documented way of invoking that
:-)
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Stephen Wolf
Sent: Wednesday, July 16, 2008 2:34 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: IODF change causes next IPL to hang
Hello List,
Are system is a 2096 U03 with three LPARs but no sysplex
On Wed, 16 Jul 2008 15:24:56 -0500, Mark Zelden [EMAIL PROTECTED]
wrote:
On Wed, 16 Jul 2008 14:33:44 -0500, Stephen Wolf [EMAIL PROTECTED]
wrote:
Hello List,
Are system is a 2096 U03 with three LPARs but no sysplex. Two LPARs are
production, one at z/OS 1.4 and a small one at z/OS 1.7. The
This is a very cool technique for debugging mysterious IPL slowdowns.
You don't even need a dump - if you run this IPCS command on a running
system, the IPLDATA STATUS command will tell you how long each module in
the IPL process took to perform its function when that system was IPLed -
even
17 matches
Mail list logo
