Did run IEBPDSE, but no new info compared to the abend result I posted below:

IGW699I PDSE Directory Validation Unsuccessful 
DESC:PDSE structure is corrupted               
ERROR NUM:103                                  
DSN:SYS6.IDI.PROD5.HIST.FEL                    
VOLSER:GEM040                                  
ADPages:10169 IXRecords:405168                 
ADPagesInCore:3 ADPagesRead:10166              
ADTreeLevels:3                                 
NDPages:21 IXRecords:2460                      
NDPagesInCore:1 NDPagesRead:20                 
NDTreeLevels:2                                 
AD ND Tree Nodes:2430                          
Version:1                                      
Orphan Pages:4682                              
RC:4 RS:01188012                               
IGW702I PDSE Directory Validation Unsuccessful 
DESC:<AD> Structure is corrupted               
LTK:D561C14040404040404040404040404040404040   
ERROR NUM:1                                    
DSN:SYS6.IDI.PROD5.HIST.FEL                    
VOLSER:GEM040                                  
RC:4 RS:01188012 R14:0876C2A4                  
RPN:N/A                                        
VPTVFN:N/A                                     




Best Regards,
Thomas Berg
___________________________________________________________________ 
Thomas Berg   Specialist   zOS/RQM/IT Delivery   Swedbank AB (Publ)

Interactive is 'manual.' Batch is 'automatic.'




> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of
> Mark Jacobs - Listserv
> Sent: Tuesday, May 26, 2015 3:27 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful
> 
> If you take a physical dump of the dataset and send it into IBM for
> analysis they might be able to get to the root cause. Assuming you're on
> zOS 1.13 or higher did you execute IEBPDSE against the restored dataset
> to verify its structure?
> 
> Mark Jacobs
> 
> > Thomas Berg <mailto:thomas.b...@swedbank.se>
> > May 25, 2015 at 9:23 PM
> > AFAIK it should have a very low probability. This due to that those
> > that can access from outside of the Sysplex (special sysprogs) have
> > neither reason or interest of doing that. And this is 3.00 AM here.
> > (At least the operator I spoke to had no knowledge of anyone else that
> > me working at this time.)
> >
> > I have restored a backup from yesterday now so the immediate problem
> > is solved. (And saved the corrupted PDSE in case anyone except me is
> > interested.)
> >
> >
> >
> > Best Regards,
> > Thomas Berg
> > ___________________________________________________________________
> > Thomas Berg Specialist zOS/RQM/IT Delivery Swedbank AB (Publ)
> >
> > Interactive is 'manual.' Batch is 'automatic.'
> >
> >
> >
> > ----------------------------------------------------------------------
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> > Mark Jacobs - Listserv <mailto:mark.jac...@custserv.com>
> > May 25, 2015 at 9:09 PM
> > Could it have been shared(R/W) outside of a sysplex boundary?
> >
> > Mark Jacobs
> >
> >
> > Thomas Berg <mailto:thomas.b...@swedbank.se>
> > May 25, 2015 at 8:43 PM
> > Got a corrupt PDSE. Will throw the problem at some of the responsible
> > sysprogs.
> > But in the meantime I wonder if any of the esteem members of this list
> > can give some hints leading to the cause.
> >
> > Got this when tying a browse from ISPF 3.4 (linecmd B):
> >
> > IGW699I PDSE Directory Validation Unsuccessful
> > DESC:PDSE structure is corrupted
> > ERROR NUM:103
> > DSN:SYS6.IDI.PROD5.HIST
> > VOLSER:GEM040
> > ADPages:10169 IXRecords:405168
> > ADPagesInCore:159 ADPagesRead:10010
> > ADTreeLevels:3
> > NDPages:21 IXRecords:2460
> > NDPagesInCore:7 NDPagesRead:14
> > NDTreeLevels:2
> > AD ND Tree Nodes:2430
> > Version:1
> > Orphan Pages:4682
> > RC:4 RS:01188012
> > IGW702I PDSE Directory Validation Unsuccessful
> > DESC:<AD> Structure is corrupted
> > LTK:D561C14040404040404040404040404040404040
> > IEA995I SYMPTOM DUMP OUTPUT
> > SYSTEM COMPLETION CODE=0F4 REASON CODE=00000024
> > TIME=02.28.25 SEQ=58662 CPU=0000 ASID=0457
> > PSW AT TIME OF ERROR 075C1000 888B9690 ILC 2 INTC 0D
> > NO ACTIVE MODULE FOUND - PRIMARY NOT EQUAL TO HOME
> > NAME=UNKNOWN
> > DATA AT PSW 088B968A - 58F05048 0A0DB219 0000A788
> > AR/GR 0: 007FF6C8/01188012 1: 00000000/040F4000
> > 2: 00000001/00FDB9A0 3: 00000000/7B1A2268
> > 4: 00000002/00007703 5: 00000000/7B1A7400
> > 6: 00000000/7B1A2060 7: 00000000/00FE0548
> > 8: 00000000/00FE05B8 9: 00000001/7B1A2268
> > A: 00000000/7B1A7868 B: 00000000/00000000
> > C: 00000000/088B9012 D: 00000000/7B1A7778
> > E: 00000000/888B9682 F: 00000000/00000024
> > END OF SYMPTOM DUMP
> > ERROR NUM:1
> > DSN:SYS6.IDI.PROD5.HIST
> > VOLSER:GEM040
> > RC:4 RS:01188012 R14:0876C2A4
> > RPN:N/A
> > VPTVFN:N/A
> > IEC036I 002-A4,IGC0005E,S000TBE,KAT30,ISP02264,786B,GEM040,
> > SYS6.IDI.PROD5.HIST
> > ERROR DESCRIPTION: IEC036I
> > Unable to complete the READ against the PDSE directory due to an error
> > return code from the SMS service used to obtain directory information.
> > END ERROR DESCRIPTION: IEC036I
> > IRX0250E System abend code 002, reason code 00000164.
> > IRX0255E Abend in host command SELECT or address environment routine
> > ISPEXEC.
> > ***
> >
> >
> > The dataset is a Fault Analyzer dump pdse. Is populated from
> > productions abends (in another system - same Sysplex).
> > Was browsing from the dev system. We have 7 other similar datasets,
> > all populated from the prod system and mostly viewed from the dev
> > system. First time for me of a corrupt PDSE causing an abend like this.
> >
> >
> >
> > Best Regards,
> > Thomas Berg
> > ___________________________________________________________________
> > Thomas Berg Specialist zOS/RQM/IT Delivery Swedbank AB (Publ)
> >
> > Interactive is 'manual.' Batch is 'automatic.'
> >
> > ----------------------------------------------------------------------
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> >
> >
> > Please be alert for any emails that may ask you for login information
> > or directs you to login via a link. If you believe this message is a
> > phish or aren't sure whether this message is trustworthy, please send
> > the original message as an attachment to 'phish...@timeinc.com'.
> >
> 
> --
> 
> Mark Jacobs
> Time Customer Service
> Technology and Product Engineering
> 
> The standard you walk past is the standard you accept.
> Lt. Gen. David Morrison
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to