Jr,

Yes I have the dump. I even try to find something interesting with the
symptom macro but I cqn't go far with that; I have no competence to read a
dump.
I could open a PMR but we are z/VM440 ... If you see what I mean. I search
on the IBM site for a ptf. The unique one referenced is for VM 3.1. That's
old

Alain

 



Le 2/02/08 14:39, « Imler, Steven J » <[EMAIL PROTECTED]> a écrit :

> Alain,
> 
> Did you process the DUMPs ... or do you still have them to process
> (likely in OPERATNS RDR)?
> 
> Open a PMR with IBM and they can help you figure out what the problem
> is.
> 
> JR
> 
> JR (Steven) Imler
> CA
> Senior Software Engineer
> Tel:  +1 703 708 3479
> Fax:  +1 703 708 3267
> [EMAIL PROTECTED]
> 
> 
>> -----Original Message-----
>> From: The IBM z/VM Operating System
>> [mailto:[EMAIL PROTECTED] On Behalf Of Alain Benveniste
>> Sent: Saturday, February 02, 2008 08:18 AM
>> To: [email protected]
>> 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
>> 
>> 
> 

Reply via email to