Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful
I've had to deal with a couple of PDSE issues with z/OS 2.1 and Fault Analyzer. 1. Ensure all systems are up to date with PDSE maintenance 2. It's possible that IEBPDSE (the z/OS 2.1 version) against your restored PDSE will still report problems. Reallocate your PDSE and copy (IEBCOPY) the backup data into it. z/OS 2.1 is more robust about reporting some internal PDSE issues than previous z/OS levels. If you don't reallocate you are simply continuing the internal structural problems. 3. Send your diagnostic data and dumps into IBM to be sure you don't have something new . Regards Hank Oerlemans, IBM Fault Analyzer From: Thomas Berg thomas.b...@swedbank.se To: IBM-MAIN@LISTSERV.UA.EDU Date: 26/05/2015 11:48 Subject:Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU BTW, we are on zOS 2.1 in the DEV system and zOS 1.13 in the prod system. Best Regards, Thomas Berg ___ Thomas Berg Specialist zOS/RQM/IT Delivery Swedbank AB (Publ) Interactive is 'manual.' Batch is 'automatic.' -Original Message- From: Thomas Berg Sent: Tuesday, May 26, 2015 3:46 AM To: 'IBM Mainframe Discussion List' Subject: RE: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful 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
Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful
Thanks! Regarding 2: I restored the dataset to another name and then did 2 renames. IEBPDSE did not report any problems. 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 Hank Oerlemans Sent: Tuesday, May 26, 2015 8:14 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful I've had to deal with a couple of PDSE issues with z/OS 2.1 and Fault Analyzer. 1. Ensure all systems are up to date with PDSE maintenance 2. It's possible that IEBPDSE (the z/OS 2.1 version) against your restored PDSE will still report problems. Reallocate your PDSE and copy (IEBCOPY) the backup data into it. z/OS 2.1 is more robust about reporting some internal PDSE issues than previous z/OS levels. If you don't reallocate you are simply continuing the internal structural problems. 3. Send your diagnostic data and dumps into IBM to be sure you don't have something new . Regards Hank Oerlemans, IBM Fault Analyzer From: Thomas Berg thomas.b...@swedbank.se To: IBM-MAIN@LISTSERV.UA.EDU Date: 26/05/2015 11:48 Subject:Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU BTW, we are on zOS 2.1 in the DEV system and zOS 1.13 in the prod system. Best Regards, Thomas Berg ___ Thomas Berg Specialist zOS/RQM/IT Delivery Swedbank AB (Publ) Interactive is 'manual.' Batch is 'automatic.' -Original Message- From: Thomas Berg Sent: Tuesday, May 26, 2015 3:46 AM To: 'IBM Mainframe Discussion List' Subject: RE: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful 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
Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful
Take a look at this APAR: http://www-01.ibm.com/support/docview.wss?uid=isg1OA44607 In the APAR it has: Sparse datasets from release 1.13 or lower and subsequent updated in R2.1 may cause an index corruption. R2.1 collapse sparse indexes and it did not delete an empty page in a particular delete path. Al Nims Systems Admin/Programmer 3 Information Technology University of Florida (352) 273-1298 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mark Jacobs - Listserv Sent: Monday, May 25, 2015 10:04 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful Yea, it looks damaged to me too. I'd still recommend that you validate the integrity of the restored dataset, just to be safe. Mark Jacobs Thomas Berg mailto:thomas.b...@swedbank.se May 25, 2015 at 10:00 PM Tried on another prodsystem. Got this: IGW699I PDSE Directory Validation Unsuccessful IEA995I SYMPTOM DUMP OUTPUT SYSTEM COMPLETION CODE=0F4 REASON CODE=0024 TIME=03.59.10 SEQ=44968 CPU= ASID=01F8 PSW AT TIME OF ERROR 075C1000 88FDA690 ILC 2 INTC 0D NO ACTIVE MODULE FOUND - PRIMARY NOT EQUAL TO HOME NAME=UNKNOWN DATA AT PSW 08FDA68A - 58F05048 0A0DB219 A788 AR/GR 0: 008FF6C8/01188012 1: /040F4000 2: 0001/00FDB9A0 3: /7EC6E268 4: 0002/7703 5: /7EC73400 6: /7EC6E060 7: /00FE0548 8: /00FE05B8 9: 0001/7EC6E268 A: /7EC73868 B: / C: /08FDA012 D: /7EC73778 E: /88FDA682 F: /0024 END OF SYMPTOM DUMP DESC:PDSE structure is corrupted ERROR NUM:103 DSN:SYS6.IDI.PROD5.HIST.FEL 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 ERROR NUM:1 DSN:SYS6.IDI.PROD5.HIST.FEL VOLSER:GEM040 RC:4 RS:01188012 R14:08E8D2A4 RPN:N/A VPTVFN:N/A IEC036I 002-A4,IGC0005E,S000TBE,KAT30,ISP03594,786B,GEM040, SYS6.IDI.PROD5.HIST.FEL IRX0250E System abend code 002, reason code 0164. IRX0255E Abend in host command SELECT or address environment routine ISPEXEC. *** 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:50 PM Three more questions. 1. Do you have all the required toleration maintenance applied on your 1.13 system? 2. Does the hang occur on all systems in the sysplex or just one? 1. If only on one, can you recycle the SMSPDSE1 address space and see if that fixes the problem? Mark Jacobs Thomas Berg mailto:thomas.b...@swedbank.se May 25, 2015 at 9:47 PM BTW, we are on zOS 2.1 in the DEV system and zOS 1.13 in the prod system. 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:27 PM 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
Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful
1: The error is not consistent as it is just hanging when I try to browse it in the prod system. Can cancel the hang with ATTN. 2: It's populated by Fault Analyzer's task IDISS (it is several of those, each in its own system, but still in the same Sysplex). This dataset in particular is populated from several prod systems, and is otherwise accessed by any system in the Sysplex. 3: Is not shared outside of the Sysplex. (AFAIK) 4: It fails in one of the prod systems by hanging when trying to browse. Other similar datasets works fine. 5: Have solved the immediate problem by restoring a backup from yesterday. 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 Lizette Koehler Sent: Tuesday, May 26, 2015 3:33 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful Check the dataset on other systems. See if the error is consistent. How is it populated from other systems? Is it only supposed to be up on DEV? Has it been up on other Plexs if DEV is in a different PLEX. PDS/Es cannot be shared across PLEXs. Only within a given PLEX. If it only fails in DEV, then do not use it in DEV for now until you can action the recovery process as directed by IBM. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Thomas Berg Sent: Monday, May 25, 2015 5:44 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful 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=0024 TIME=02.28.25 SEQ=58662 CPU= 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 A788 AR/GR 0: 007FF6C8/01188012 1: /040F4000 2: 0001/00FDB9A0 3: /7B1A2268 4: 0002/7703 5: /7B1A7400 6: /7B1A2060 7: /00FE0548 8: /00FE05B8 9: 0001/7B1A2268 A: /7B1A7868 B: / C: /088B9012 D: /7B1A7778 E: /888B9682 F: /0024 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 0164. 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 -- 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
Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful
Tried on another prodsystem. Got this: IGW699I PDSE Directory Validation Unsuccessful IEA995I SYMPTOM DUMP OUTPUT SYSTEM COMPLETION CODE=0F4 REASON CODE=0024 TIME=03.59.10 SEQ=44968 CPU= ASID=01F8 PSW AT TIME OF ERROR 075C1000 88FDA690 ILC 2 INTC 0D NO ACTIVE MODULE FOUND - PRIMARY NOT EQUAL TO HOME NAME=UNKNOWN DATA AT PSW 08FDA68A - 58F05048 0A0DB219 A788 AR/GR 0: 008FF6C8/01188012 1: /040F4000 2: 0001/00FDB9A0 3: /7EC6E268 4: 0002/7703 5: /7EC73400 6: /7EC6E060 7: /00FE0548 8: /00FE05B8 9: 0001/7EC6E268 A: /7EC73868 B: / C: /08FDA012 D: /7EC73778 E: /88FDA682 F: /0024 END OF SYMPTOM DUMP DESC:PDSE structure is corrupted ERROR NUM:103 DSN:SYS6.IDI.PROD5.HIST.FEL 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 ERROR NUM:1 DSN:SYS6.IDI.PROD5.HIST.FEL VOLSER:GEM040 RC:4 RS:01188012 R14:08E8D2A4 RPN:N/A VPTVFN:N/A IEC036I 002-A4,IGC0005E,S000TBE,KAT30,ISP03594,786B,GEM040, SYS6.IDI.PROD5.HIST.FEL IRX0250E System abend code 002, reason code 0164. IRX0255E Abend in host command SELECT or address environment routine ISPEXEC. *** 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:50 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful Three more questions. 1. Do you have all the required toleration maintenance applied on your 1.13 system? 2. Does the hang occur on all systems in the sysplex or just one? 1. If only on one, can you recycle the SMSPDSE1 address space and see if that fixes the problem? Mark Jacobs Thomas Berg mailto:thomas.b...@swedbank.se May 25, 2015 at 9:47 PM BTW, we are on zOS 2.1 in the DEV system and zOS 1.13 in the prod system. 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
Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful
Check the dataset on other systems. See if the error is consistent. How is it populated from other systems? Is it only supposed to be up on DEV? Has it been up on other Plexs if DEV is in a different PLEX. PDS/Es cannot be shared across PLEXs. Only within a given PLEX. If it only fails in DEV, then do not use it in DEV for now until you can action the recovery process as directed by IBM. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Thomas Berg Sent: Monday, May 25, 2015 5:44 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful 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=0024 TIME=02.28.25 SEQ=58662 CPU= 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 A788 AR/GR 0: 007FF6C8/01188012 1: /040F4000 2: 0001/00FDB9A0 3: /7B1A2268 4: 0002/7703 5: /7B1A7400 6: /7B1A2060 7: /00FE0548 8: /00FE05B8 9: 0001/7B1A2268 A: /7B1A7868 B: / C: /088B9012 D: /7B1A7778 E: /888B9682 F: /0024 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 0164. 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful
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=0024 TIME=02.28.25 SEQ=58662 CPU= 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 A788 AR/GR 0: 007FF6C8/01188012 1: /040F4000 2: 0001/00FDB9A0 3: /7B1A2268 4: 0002/7703 5: /7B1A7400 6: /7B1A2060 7: /00FE0548 8: /00FE05B8 9: 0001/7B1A2268 A: /7B1A7868 B: / C: /088B9012 D: /7B1A7778 E: /888B9682 F: /0024 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 0164. 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
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=0024 TIME=02.28.25 SEQ=58662 CPU= 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 A788 AR/GR 0: 007FF6C8/01188012 1: /040F4000 2: 0001/00FDB9A0 3: /7B1A2268 4: 0002/7703 5: /7B1A7400 6: /7B1A2060 7: /00FE0548 8: /00FE05B8 9: 0001/7B1A2268 A: /7B1A7868 B: / C: /088B9012 D: /7B1A7778 E: /888B9682 F: /0024 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 0164. 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
Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful
Yea, it looks damaged to me too. I'd still recommend that you validate the integrity of the restored dataset, just to be safe. Mark Jacobs Thomas Berg mailto:thomas.b...@swedbank.se May 25, 2015 at 10:00 PM Tried on another prodsystem. Got this: IGW699I PDSE Directory Validation Unsuccessful IEA995I SYMPTOM DUMP OUTPUT SYSTEM COMPLETION CODE=0F4 REASON CODE=0024 TIME=03.59.10 SEQ=44968 CPU= ASID=01F8 PSW AT TIME OF ERROR 075C1000 88FDA690 ILC 2 INTC 0D NO ACTIVE MODULE FOUND - PRIMARY NOT EQUAL TO HOME NAME=UNKNOWN DATA AT PSW 08FDA68A - 58F05048 0A0DB219 A788 AR/GR 0: 008FF6C8/01188012 1: /040F4000 2: 0001/00FDB9A0 3: /7EC6E268 4: 0002/7703 5: /7EC73400 6: /7EC6E060 7: /00FE0548 8: /00FE05B8 9: 0001/7EC6E268 A: /7EC73868 B: / C: /08FDA012 D: /7EC73778 E: /88FDA682 F: /0024 END OF SYMPTOM DUMP DESC:PDSE structure is corrupted ERROR NUM:103 DSN:SYS6.IDI.PROD5.HIST.FEL 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 ERROR NUM:1 DSN:SYS6.IDI.PROD5.HIST.FEL VOLSER:GEM040 RC:4 RS:01188012 R14:08E8D2A4 RPN:N/A VPTVFN:N/A IEC036I 002-A4,IGC0005E,S000TBE,KAT30,ISP03594,786B,GEM040, SYS6.IDI.PROD5.HIST.FEL IRX0250E System abend code 002, reason code 0164. IRX0255E Abend in host command SELECT or address environment routine ISPEXEC. *** 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:50 PM Three more questions. 1. Do you have all the required toleration maintenance applied on your 1.13 system? 2. Does the hang occur on all systems in the sysplex or just one? 1. If only on one, can you recycle the SMSPDSE1 address space and see if that fixes the problem? Mark Jacobs Thomas Berg mailto:thomas.b...@swedbank.se May 25, 2015 at 9:47 PM BTW, we are on zOS 2.1 in the DEV system and zOS 1.13 in the prod system. 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:27 PM 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 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
Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful
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.' -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:10 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful 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=0024 TIME=02.28.25 SEQ=58662 CPU= 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 A788 AR/GR 0: 007FF6C8/01188012 1: /040F4000 2: 0001/00FDB9A0 3: /7B1A2268 4: 0002/7703 5: /7B1A7400 6: /7B1A2060 7: /00FE0548 8: /00FE05B8 9: 0001/7B1A2268 A: /7B1A7868 B: / C: /088B9012 D: /7B1A7778 E: /888B9682 F: /0024 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 0164. 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
Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful
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=0024 TIME=02.28.25 SEQ=58662 CPU= 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 A788 AR/GR 0: 007FF6C8/01188012 1: /040F4000 2: 0001/00FDB9A0 3: /7B1A2268 4: 0002/7703 5: /7B1A7400 6: /7B1A2060 7: /00FE0548 8: /00FE05B8 9: 0001/7B1A2268 A: /7B1A7868 B: / C: /088B9012 D: /7B1A7778 E: /888B9682 F: /0024 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
Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful
BTW, we are on zOS 2.1 in the DEV system and zOS 1.13 in the prod system. Best Regards, Thomas Berg ___ Thomas Berg Specialist zOS/RQM/IT Delivery Swedbank AB (Publ) Interactive is 'manual.' Batch is 'automatic.' -Original Message- From: Thomas Berg Sent: Tuesday, May 26, 2015 3:46 AM To: 'IBM Mainframe Discussion List' Subject: RE: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful 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=0024 TIME=02.28.25 SEQ=58662 CPU= 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 A788 AR/GR 0: 007FF6C8/01188012 1: /040F4000 2: 0001/00FDB9A0 3: /7B1A2268 4: 0002/7703 5: /7B1A7400 6: /7B1A2060 7: /00FE0548 8: /00FE05B8 9: 0001/7B1A2268 A: /7B1A7868 B: / C: /088B9012 D: /7B1A7778 E: /888B9682 F: /0024 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
Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful
1: I don't know, have to ask the responsible sysprog. But they should have applied those. 2: Have only tested on one of the prod systems. Will try another. 3: I will not dare to try that, would probably be shot in the dawn by the operations manager if I do that. :) (It's not my area of competence.) 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:50 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful Three more questions. 1. Do you have all the required toleration maintenance applied on your 1.13 system? 2. Does the hang occur on all systems in the sysplex or just one? 1. If only on one, can you recycle the SMSPDSE1 address space and see if that fixes the problem? Mark Jacobs Thomas Berg mailto:thomas.b...@swedbank.se May 25, 2015 at 9:47 PM BTW, we are on zOS 2.1 in the DEV system and zOS 1.13 in the prod system. 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:27 PM 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=0024 TIME=02.28.25 SEQ=58662 CPU= 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 A788 AR/GR 0: 007FF6C8/01188012 1: /040F4000 2: 0001/00FDB9A0 3: /7B1A2268 4: 0002/7703 5: /7B1A7400 6: /7B1A2060 7: /00FE0548 8: /00FE05B8 9: 0001/7B1A2268 A: /7B1A7868 B: / C: /088B9012 D: /7B1A7778 E: /888B9682 F: /0024 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
Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful
I checked the restored one. It was ok. I'm currently running IEBPDSE against the failing version, this time in the prod system (where I was just hanging when trying to browse it). When running the same job in the DEV system it took just 4 seconds, but now in the prod system it is still running after 10 minutes. It consumes CPU time but no EXCP (stands still at 4 EXCP). When run in the DEV system it consumed 10213 EXCP. 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 4:04 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful Yea, it looks damaged to me too. I'd still recommend that you validate the integrity of the restored dataset, just to be safe. Mark Jacobs Thomas Berg mailto:thomas.b...@swedbank.se May 25, 2015 at 10:00 PM Tried on another prodsystem. Got this: IGW699I PDSE Directory Validation Unsuccessful IEA995I SYMPTOM DUMP OUTPUT SYSTEM COMPLETION CODE=0F4 REASON CODE=0024 TIME=03.59.10 SEQ=44968 CPU= ASID=01F8 PSW AT TIME OF ERROR 075C1000 88FDA690 ILC 2 INTC 0D NO ACTIVE MODULE FOUND - PRIMARY NOT EQUAL TO HOME NAME=UNKNOWN DATA AT PSW 08FDA68A - 58F05048 0A0DB219 A788 AR/GR 0: 008FF6C8/01188012 1: /040F4000 2: 0001/00FDB9A0 3: /7EC6E268 4: 0002/7703 5: /7EC73400 6: /7EC6E060 7: /00FE0548 8: /00FE05B8 9: 0001/7EC6E268 A: /7EC73868 B: / C: /08FDA012 D: /7EC73778 E: /88FDA682 F: /0024 END OF SYMPTOM DUMP DESC:PDSE structure is corrupted ERROR NUM:103 DSN:SYS6.IDI.PROD5.HIST.FEL 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 ERROR NUM:1 DSN:SYS6.IDI.PROD5.HIST.FEL VOLSER:GEM040 RC:4 RS:01188012 R14:08E8D2A4 RPN:N/A VPTVFN:N/A IEC036I 002-A4,IGC0005E,S000TBE,KAT30,ISP03594,786B,GEM040, SYS6.IDI.PROD5.HIST.FEL IRX0250E System abend code 002, reason code 0164. IRX0255E Abend in host command SELECT or address environment routine ISPEXEC. *** 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:50 PM Three more questions. 1. Do you have all the required toleration maintenance applied on your 1.13 system? 2. Does the hang occur on all systems in the sysplex or just one? 1. If only on one, can you recycle the SMSPDSE1 address space and see if that fixes the problem? Mark Jacobs Thomas Berg mailto:thomas.b...@swedbank.se May 25, 2015 at 9:47 PM BTW, we are on zOS 2.1 in the DEV system and zOS 1.13 in the prod system. 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:27 PM 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
Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful
Three more questions. 1. Do you have all the required toleration maintenance applied on your 1.13 system? 2. Does the hang occur on all systems in the sysplex or just one? 1. If only on one, can you recycle the SMSPDSE1 address space and see if that fixes the problem? Mark Jacobs Thomas Berg mailto:thomas.b...@swedbank.se May 25, 2015 at 9:47 PM BTW, we are on zOS 2.1 in the DEV system and zOS 1.13 in the prod system. 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:27 PM 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=0024 TIME=02.28.25 SEQ=58662 CPU= 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 A788 AR/GR 0: 007FF6C8/01188012 1: /040F4000 2: 0001/00FDB9A0 3: /7B1A2268 4: 0002/7703 5: /7B1A7400 6: /7B1A2060 7: /00FE0548 8: /00FE05B8 9: 0001/7B1A2268 A: /7B1A7868 B: / C: /088B9012 D: /7B1A7778 E: /888B9682 F: /0024 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 0164. 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
Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful
Sounds like oa45027. On Monday, May 25, 2015, Thomas Berg thomas.b...@swedbank.se wrote: I checked the restored one. It was ok. I'm currently running IEBPDSE against the failing version, this time in the prod system (where I was just hanging when trying to browse it). When running the same job in the DEV system it took just 4 seconds, but now in the prod system it is still running after 10 minutes. It consumes CPU time but no EXCP (stands still at 4 EXCP). When run in the DEV system it consumed 10213 EXCP. 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 javascript:;] On Behalf Of Mark Jacobs - Listserv Sent: Tuesday, May 26, 2015 4:04 AM To: IBM-MAIN@LISTSERV.UA.EDU javascript:; Subject: Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful Yea, it looks damaged to me too. I'd still recommend that you validate the integrity of the restored dataset, just to be safe. Mark Jacobs Thomas Berg mailto:thomas.b...@swedbank.se javascript:; May 25, 2015 at 10:00 PM Tried on another prodsystem. Got this: IGW699I PDSE Directory Validation Unsuccessful IEA995I SYMPTOM DUMP OUTPUT SYSTEM COMPLETION CODE=0F4 REASON CODE=0024 TIME=03.59.10 SEQ=44968 CPU= ASID=01F8 PSW AT TIME OF ERROR 075C1000 88FDA690 ILC 2 INTC 0D NO ACTIVE MODULE FOUND - PRIMARY NOT EQUAL TO HOME NAME=UNKNOWN DATA AT PSW 08FDA68A - 58F05048 0A0DB219 A788 AR/GR 0: 008FF6C8/01188012 1: /040F4000 2: 0001/00FDB9A0 3: /7EC6E268 4: 0002/7703 5: /7EC73400 6: /7EC6E060 7: /00FE0548 8: /00FE05B8 9: 0001/7EC6E268 A: /7EC73868 B: / C: /08FDA012 D: /7EC73778 E: /88FDA682 F: /0024 END OF SYMPTOM DUMP DESC:PDSE structure is corrupted ERROR NUM:103 DSN:SYS6.IDI.PROD5.HIST.FEL 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 ERROR NUM:1 DSN:SYS6.IDI.PROD5.HIST.FEL VOLSER:GEM040 RC:4 RS:01188012 R14:08E8D2A4 RPN:N/A VPTVFN:N/A IEC036I 002-A4,IGC0005E,S000TBE,KAT30,ISP03594,786B,GEM040, SYS6.IDI.PROD5.HIST.FEL IRX0250E System abend code 002, reason code 0164. IRX0255E Abend in host command SELECT or address environment routine ISPEXEC. *** 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 javascript:; with the message: INFO IBM-MAIN Mark Jacobs - Listserv mailto:mark.jac...@custserv.com javascript:; May 25, 2015 at 9:50 PM Three more questions. 1. Do you have all the required toleration maintenance applied on your 1.13 system? 2. Does the hang occur on all systems in the sysplex or just one? 1. If only on one, can you recycle the SMSPDSE1 address space and see if that fixes the problem? Mark Jacobs Thomas Berg mailto:thomas.b...@swedbank.se javascript:; May 25, 2015 at 9:47 PM BTW, we are on zOS 2.1 in the DEV system and zOS 1.13 in the prod system. 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 javascript:; with the message: INFO IBM-MAIN Mark Jacobs - Listserv mailto:mark.jac...@custserv.com javascript:; May 25, 2015 at 9:27 PM 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 javascript:; May 25, 2015 at 9:23 PM AFAIK it should have a very low probability. This due
Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful
Is that applicable on zOS 1.13 ? As that is what the prod system is at. (Looked at OA43214 - it said Software version 210.) 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 Dan Little Sent: Tuesday, May 26, 2015 4:40 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful Sounds like oa45027. On Monday, May 25, 2015, Thomas Berg thomas.b...@swedbank.se wrote: I checked the restored one. It was ok. I'm currently running IEBPDSE against the failing version, this time in the prod system (where I was just hanging when trying to browse it). When running the same job in the DEV system it took just 4 seconds, but now in the prod system it is still running after 10 minutes. It consumes CPU time but no EXCP (stands still at 4 EXCP). When run in the DEV system it consumed 10213 EXCP. 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 javascript:;] On Behalf Of Mark Jacobs - Listserv Sent: Tuesday, May 26, 2015 4:04 AM To: IBM-MAIN@LISTSERV.UA.EDU javascript:; Subject: Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful Yea, it looks damaged to me too. I'd still recommend that you validate the integrity of the restored dataset, just to be safe. Mark Jacobs Thomas Berg mailto:thomas.b...@swedbank.se javascript:; May 25, 2015 at 10:00 PM Tried on another prodsystem. Got this: IGW699I PDSE Directory Validation Unsuccessful IEA995I SYMPTOM DUMP OUTPUT SYSTEM COMPLETION CODE=0F4 REASON CODE=0024 TIME=03.59.10 SEQ=44968 CPU= ASID=01F8 PSW AT TIME OF ERROR 075C1000 88FDA690 ILC 2 INTC 0D NO ACTIVE MODULE FOUND - PRIMARY NOT EQUAL TO HOME NAME=UNKNOWN DATA AT PSW 08FDA68A - 58F05048 0A0DB219 A788 AR/GR 0: 008FF6C8/01188012 1: /040F4000 2: 0001/00FDB9A0 3: /7EC6E268 4: 0002/7703 5: /7EC73400 6: /7EC6E060 7: /00FE0548 8: /00FE05B8 9: 0001/7EC6E268 A: /7EC73868 B: / C: /08FDA012 D: /7EC73778 E: /88FDA682 F: /0024 END OF SYMPTOM DUMP DESC:PDSE structure is corrupted ERROR NUM:103 DSN:SYS6.IDI.PROD5.HIST.FEL 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 ERROR NUM:1 DSN:SYS6.IDI.PROD5.HIST.FEL VOLSER:GEM040 RC:4 RS:01188012 R14:08E8D2A4 RPN:N/A VPTVFN:N/A IEC036I 002-A4,IGC0005E,S000TBE,KAT30,ISP03594,786B,GEM040, SYS6.IDI.PROD5.HIST.FEL IRX0250E System abend code 002, reason code 0164. IRX0255E Abend in host command SELECT or address environment routine ISPEXEC. *** 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 javascript:; with the message: INFO IBM-MAIN Mark Jacobs - Listserv mailto:mark.jac...@custserv.com javascript:; May 25, 2015 at 9:50 PM Three more questions. 1. Do you have all the required toleration maintenance applied on your 1.13 system? 2. Does the hang occur on all systems in the sysplex or just one? 1. If only on one, can you recycle the SMSPDSE1 address space and see if that fixes the problem? Mark Jacobs Thomas Berg mailto:thomas.b...@swedbank.se javascript:; May 25, 2015 at 9:47 PM BTW, we are on zOS 2.1 in the DEV system and zOS 1.13 in the prod system. Best Regards, Thomas Berg ___ Thomas Berg Specialist zOS/RQM/IT Delivery Swedbank AB (Publ) Interactive is 'manual.' Batch is 'automatic
Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful
No. It is 2.1. There is a fairly old Apar for the same reason code OA36228. On Monday, May 25, 2015, Thomas Berg thomas.b...@swedbank.se wrote: Is that applicable on zOS 1.13 ? As that is what the prod system is at. (Looked at OA43214 - it said Software version 210.) 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 javascript:;] On Behalf Of Dan Little Sent: Tuesday, May 26, 2015 4:40 AM To: IBM-MAIN@LISTSERV.UA.EDU javascript:; Subject: Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful Sounds like oa45027. On Monday, May 25, 2015, Thomas Berg thomas.b...@swedbank.se javascript:; wrote: I checked the restored one. It was ok. I'm currently running IEBPDSE against the failing version, this time in the prod system (where I was just hanging when trying to browse it). When running the same job in the DEV system it took just 4 seconds, but now in the prod system it is still running after 10 minutes. It consumes CPU time but no EXCP (stands still at 4 EXCP). When run in the DEV system it consumed 10213 EXCP. 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 javascript:; javascript:;] On Behalf Of Mark Jacobs - Listserv Sent: Tuesday, May 26, 2015 4:04 AM To: IBM-MAIN@LISTSERV.UA.EDU javascript:; javascript:; Subject: Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful Yea, it looks damaged to me too. I'd still recommend that you validate the integrity of the restored dataset, just to be safe. Mark Jacobs Thomas Berg mailto:thomas.b...@swedbank.se javascript:; javascript:; May 25, 2015 at 10:00 PM Tried on another prodsystem. Got this: IGW699I PDSE Directory Validation Unsuccessful IEA995I SYMPTOM DUMP OUTPUT SYSTEM COMPLETION CODE=0F4 REASON CODE=0024 TIME=03.59.10 SEQ=44968 CPU= ASID=01F8 PSW AT TIME OF ERROR 075C1000 88FDA690 ILC 2 INTC 0D NO ACTIVE MODULE FOUND - PRIMARY NOT EQUAL TO HOME NAME=UNKNOWN DATA AT PSW 08FDA68A - 58F05048 0A0DB219 A788 AR/GR 0: 008FF6C8/01188012 1: /040F4000 2: 0001/00FDB9A0 3: /7EC6E268 4: 0002/7703 5: /7EC73400 6: /7EC6E060 7: /00FE0548 8: /00FE05B8 9: 0001/7EC6E268 A: /7EC73868 B: / C: /08FDA012 D: /7EC73778 E: /88FDA682 F: /0024 END OF SYMPTOM DUMP DESC:PDSE structure is corrupted ERROR NUM:103 DSN:SYS6.IDI.PROD5.HIST.FEL 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 ERROR NUM:1 DSN:SYS6.IDI.PROD5.HIST.FEL VOLSER:GEM040 RC:4 RS:01188012 R14:08E8D2A4 RPN:N/A VPTVFN:N/A IEC036I 002-A4,IGC0005E,S000TBE,KAT30,ISP03594,786B,GEM040, SYS6.IDI.PROD5.HIST.FEL IRX0250E System abend code 002, reason code 0164. IRX0255E Abend in host command SELECT or address environment routine ISPEXEC. *** 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 javascript:; javascript:; with the message: INFO IBM-MAIN Mark Jacobs - Listserv mailto:mark.jac...@custserv.com javascript:; javascript:; May 25, 2015 at 9:50 PM Three more questions. 1. Do you have all the required toleration maintenance applied on your 1.13 system? 2. Does the hang occur on all systems in the sysplex or just one? 1. If only on one, can you recycle the SMSPDSE1 address space and see if that fixes the problem? Mark Jacobs Thomas Berg mailto:thomas.b
