Is it possible that a different system (even a second level guest) wrote 
to that DASD, or that there's a minidisk allocated on that DASD and 
something wrote to the minidisk?

Since you're 100% certain (right?) that the CP_Owned slot numbers were not 
changed, the only other thing I can think of is that maybe the disk was 
never FULLY formatted.  E.g. it's easy to think of a 3390-3 disk as 3,338 
cylinders, and format 0-3,337  (forgetting that it is actually 3,339 
cylinders - thus leaving the true last cylinder not CP-formatted).  You'll 
run along just fine until one day when the system finally writes to that 
slot on cylinder 3,339 and crashes.  It won't be obvious why you crashed, 
and you will continue to run just fine until the system once again tries 
to write to that slot.  But the dump will probably have some breadcrumbs 
showing which slot was being written.

Why not open a PMR?  Get your money's worth from your support contract!

Mike Walter 
Hewitt Associates 
Any opinions expressed herein are mine alone and do not necessarily 
represent the opinions or policies of Hewitt Associates.



Alain Benveniste <[EMAIL PROTECTED]> 

Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>
02/02/2008 07:17 AM
Please respond to
"The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>



To
IBMVM@LISTSERV.UARK.EDU
cc

Subject
Abend PGT003






Hi,

PGT003 Explanation: The DASD page slot being released was not previously
allocated, or the slot address is incorrect. 

User response: By means of the caller?s return address and base registe
r
stored in SAVER14 and SAVER12 in the SAVBK located by R13, identify the
module attempting to release the page. Locate the source (control block o
r
ASATE) of the address of the DASD being released to verify that it has no
t
been destroyed. If the DASD page is in a spool file, it is possible that 
the
file has been incorrectly checkpointed and warm-started after a system
shutdown or a system crash.


I got 2 PGT003 abends in 2 weeks. And I don't find the reason.
All my DASD pages are always allocated with a %>0 and I never changed a s
lot
address since the install. So I suppose that 'a DASD page is in a spool
file' but I don't understand what that means. How to konw that ?
And if I do a FORCE start, would it be enough or should I do a COLD start
 to
definitely remove my problem ?

Alain Benveniste




 
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. All messages 
sent to and from this e-mail address may be monitored as permitted by 
applicable law and regulations to ensure compliance with our internal policies 
and to protect our business. Emails are not secure and cannot be guaranteed to 
be error free as they can be intercepted, amended, lost or destroyed, or 
contain viruses. You are deemed to have accepted these risks if you communicate 
with us by email. 

Reply via email to