I've been looking at the EREP EVENT-reports, and I see the following
entries for every IPL 190 that I did in user MAINT:
SPID
SSYS ID REASON PSW-MCH /PROG-EC
TIME JOBNAME RECTYP CP CUA DEVT CMD CSW SENSE 04 06
* DNO CRW CHP SCSW
17 54 04 71 MAINT MIH 03 B03C 3390 NA START PENDING
I didn't a lot of info about START PENDING in the EREP doc. Anyone know
what it means, what's causing it, or where I could find more info?
Thanks,
Geert.
-----Original Message-----
From: The IBM z/VM Operating System [mailto:[email protected]] On
Behalf Of Alan Altmark
Sent: donderdag 26 maart 2009 4:07
To: [email protected]
Subject: Re: FW: IPL 190 hangs in zVM 5.4
On Wednesday, 03/25/2009 at 02:11 EDT, Dieltiens Geert
<[email protected]> wrote:
> We have been using our current DASD setup for about 5 months now, with
no
> problems, until a couple of days ago. We have 896 (256+256+256+128)
devices on
> the Escon channels, using 4 control units, which PTK shows as 3990-6.
AFAIK
> this should all be nicely within the IBM and EMC limits.
> What puzzles me is that we do millions of IOs to all those devices,
but
the
> problem only occurs with the IPL command in a virtual machine. Is
there
some
> special kind of IO involved with IPL?
For a real (LPAR) IPL, yes, it is a special I/O. For virtual IPL, CP
just
reads the IPL records from the [real or virtual] disk, starts the I/O
and
loads the initial PSW.
Alan Altmark
z/VM Development
IBM Endicott
DISCLAIMER
This email and any files transmitted with it are confidential
and intended solely for the use of the individual or entity
to whom they are addressed. If you have received this email
in error please notify [email protected]
This footnote also confirms that this email has been checked
for the presence of viruses.
Informatica J.Van Breda & Co NV BTW BE 0427 908 174
