Re: [EXTERNAL] Re: Corrupt PDSE dataset
All values are normal :-) -- Lionel B. Dyck (Contractor) Mainframe Systems Programmer Enterprise Infrastructure Support (Station 200) (005OP6.3.10) VA OI Service Delivery & Engineering Office: 512-326-6173 Cell: 925-348-0237 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of David Mingee Sent: Friday, March 11, 2016 5:35 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset Lionel, are all of the DCB values normal or correct, if not they can be changed with PDS86. David Mingee Mainframe Consulting 9206 Aintree Drive Indianapolis, IN 46250 317 288-9588 Home317 903-9455 Cell From: Ted MacNEIL <eamacn...@yahoo.ca> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Friday, March 11, 2016 11:07 AM Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset IBM has always stated that you CANNOT share a PDSE outside SYSPLEX boundaries without a risk of corruption. It sounds like you did just that. That's a big OOPS! -teD Original Message From: R.S. Sent: Friday, March 11, 2016 10:29 To: IBM-MAIN@LISTSERV.UA.EDU Reply To: IBM Mainframe Discussion List Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset W dniu 2016-03-11 o 15:20, Dyck, Lionel B. (TRA) pisze: > We have shared dasd between two different sysplexes and grs is only within > each sysplex. How it broke I've no idea but suspect it was updated on each > side. It's the best method to corrupt PDSE. BTW: GRS won't help, because PDSE use XCF AFAIK. -- Radoslaw Skorupka Lodz, Poland -- Treść tej wiadomości może zawierać informacje prawnie chronione Banku przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorized to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, www.mBank.pl, e-mail: kont...@mbank.pl Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości wpłacony) wynosi 168.955.696 złotych. -- 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 -- 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: [EXTERNAL] Re: Corrupt PDSE dataset
Gil, You are right as usual. I used this utility to repair PDS files(recfm.dsorg,lrecl,blksize,cyl,dir,members) on the fly. It supports PDSe in a limited way. John Kalinich wrote this tool and would know it abilities in detail. I just thought it might be worth a shot. . David Mingee Mainframe Consulting 9206 Aintree Drive Indianapolis, IN 46250 317 288-9588 Home317 903-9455 Cell From: Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Friday, March 11, 2016 7:02 PM Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset On Fri, 11 Mar 2016 23:34:32 +, David Mingee wrote: >Lionel, are all of the DCB values normal or correct, if not they can be >changed with PDS86. > Knowing almost nothing about PDSE internals, I'd hesitate to change DCB attributes with a tool such as PDS86. Those attributes may be reflected internally in the PDSE in OCO-undocumented ways. But if PDS86 has been routinely used to modify PDSE attributes without problems, it's probably safe. Does it just overwrite the DSCB? This is unlikely to be the OP's problem anyway. -- gil -- 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: [EXTERNAL] Re: Corrupt PDSE dataset
On Fri, 11 Mar 2016 23:34:32 +, David Mingee wrote: >Lionel, are all of the DCB values normal or correct, if not they can be >changed with PDS86. > Knowing almost nothing about PDSE internals, I'd hesitate to change DCB attributes with a tool such as PDS86. Those attributes may be reflected internally in the PDSE in OCO-undocumented ways. But if PDS86 has been routinely used to modify PDSE attributes without problems, it's probably safe. Does it just overwrite the DSCB? This is unlikely to be the OP's problem anyway. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: Corrupt PDSE dataset
Lionel, are all of the DCB values normal or correct, if not they can be changed with PDS86. David Mingee Mainframe Consulting 9206 Aintree Drive Indianapolis, IN 46250 317 288-9588 Home317 903-9455 Cell From: Ted MacNEIL <eamacn...@yahoo.ca> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Friday, March 11, 2016 11:07 AM Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset IBM has always stated that you CANNOT share a PDSE outside SYSPLEX boundaries without a risk of corruption. It sounds like you did just that. That's a big OOPS! -teD Original Message From: R.S. Sent: Friday, March 11, 2016 10:29 To: IBM-MAIN@LISTSERV.UA.EDU Reply To: IBM Mainframe Discussion List Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset W dniu 2016-03-11 o 15:20, Dyck, Lionel B. (TRA) pisze: > We have shared dasd between two different sysplexes and grs is only within > each sysplex. How it broke I've no idea but suspect it was updated on each > side. It's the best method to corrupt PDSE. BTW: GRS won't help, because PDSE use XCF AFAIK. -- Radoslaw Skorupka Lodz, Poland -- Treść tej wiadomości może zawierać informacje prawnie chronione Banku przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorized to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, www.mBank.pl, e-mail: kont...@mbank.pl Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości wpłacony) wynosi 168.955.696 złotych. -- 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: Corrupt PDSE dataset
From IEBPDSE: IGW702I PDSE Directory Validation Unsuccessful DESC: Structure is corrupted LTK:0003082510FF ERROR NUM:30 DSN:T311LBD.LIONEL.EXEC.PDSE VOLSER:2INT0B RC:8 RS:011D8404 R14:0804E8B2 RPN:N/A VPTVFN:N/A IGW699I PDSE Directory Validation Unsuccessful DESC:PDSE structure is corrupted ERROR NUM:101 DSN:T311LBD.LIONEL.EXEC.PDSE VOLSER:2INT0B ADPages:0 IXRecords:0 ADPagesInCore:1 ADPagesRead:0 ADTreeLevels:0 NDPages:0 IXRecords:0 NDPagesInCore:1 NDPagesRead:0 NDTreeLevels:0 AD ND Tree Nodes:0 ADRootPercentFree:0 NDRootPercentFree:0 ADMidLevelEmptyPages:0 NDMidLevelEmptyPages:0 Version:1 RC:8 RS:011D8404 And from ISPF Browse: IEA995I SYMPTOM DUMP OUTPUT SYSTEM COMPLETION CODE=0F4 REASON CODE=0024 TIME=10.08.25 SEQ=30236 CPU= ASID=00AD PSW AT TIME OF ERROR 075C0001 881D9FCC ILC 2 INTC 0D NO ACTIVE MODULE FOUND - PRIMARY NOT EQUAL TO HOME NAME=UNKNOWN DATA AT PSW 081D9FC6 - 58F0D750 0A0DD707 D898D898 AR/GR 0: 009FEE88/_1419A084 1: /_040F4000 2: /_00FDA188 3: /_7F627380 4: /0048_0003 5: /_00FD67E0 6: /_00FD6850 7: /_ 8: /_7F627CCF 9: /_081DACB4 A: /_081DAD28 B: /_7F6220C0 C: /_081DAC48 D: /_7F626CD0 E: /_881D9FBC F: /_0024 END OF SYMPTOM DUMP IEC036I 002-A4,IGC0005E,T311LBD,TSD,ISP10073,5107,2INT0B, T311LBD.LIONEL.EXEC.PDSE System abend code 002, reason code 0164. Thanks -- Lionel B. Dyck (Contractor) Mainframe Systems Programmer Enterprise Infrastructure Support (Station 200) (005OP6.3.10) VA OI Service Delivery & Engineering Office: 512-326-6173 Cell: 925-348-0237 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lizette Koehler Sent: Friday, March 11, 2016 10:05 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset If you could provide fuller error messages it might help. Subcode for 0f4. And any ibe-like messages. It might make more sense Lizette -Original Message- >From: "Dyck, Lionel B. (TRA)" <lionel.d...@va.gov> >Sent: Mar 11, 2016 5:09 AM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset > >Liz - good to see you > >How should I do the copy? IEBCOPY fails as does ispf 3.3 as well as >pds copy. I can copy specific members but I don't know all the members >that were added after the backup was taken. Those members that were in >the backup were all good :-) We know of one new member and when trying >to access it the result is an Abend 0F4 :( > >-Original Message- >From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >On Behalf Of Lizette Koehler >Sent: Thursday, March 10, 2016 3:56 PM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset > >copy to new file. See what is broken >Lizette > >-Original Message- >>From: "Dyck, Lionel B. (TRA)" <lionel.d...@va.gov> >>Sent: Mar 10, 2016 11:19 AM >>To: IBM-MAIN@LISTSERV.UA.EDU >>Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset >> >>Tried restore from backup but there isn't one current enough that isn't >>corrupted. >> >> >>-- >>- >>--- >>Lionel B. Dyck (Contractor) >>Mainframe Systems Programmer >>Enterprise Infrastructure Support (Station 200) (005OP6.3.10) VA OI >>Service Delivery & Engineering >>Office: 512-326-6173 >>Cell: 925-348-0237 >> >> >>-----Original Message- >>From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >>On Behalf Of Edward Finnell >>Sent: Thursday, March 10, 2016 12:17 PM >>To: IBM-MAIN@LISTSERV.UA.EDU >>Subject: [EXTERNAL] Re: Corrupt PDSE dataset >> >>Restore from backup? >> >> >>In a message dated 3/10/2016 12:12:29 P.M. Central Standard Time, >>lionel.d...@va.gov writes: >> >>What do y'all recommend when a PDSE goes bad and the IEBPDSE just reports >>that it has a bad directory? >> >> >> >>-- >>For IBM-MAIN subscribe / signoff / archive access instructions, send >>email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> >>
Re: [EXTERNAL] Re: Corrupt PDSE dataset
IBM has always stated that you CANNOT share a PDSE outside SYSPLEX boundaries without a risk of corruption. It sounds like you did just that. That's a big OOPS! -teD Original Message From: R.S. Sent: Friday, March 11, 2016 10:29 To: IBM-MAIN@LISTSERV.UA.EDU Reply To: IBM Mainframe Discussion List Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset W dniu 2016-03-11 o 15:20, Dyck, Lionel B. (TRA) pisze: > We have shared dasd between two different sysplexes and grs is only within > each sysplex. How it broke I've no idea but suspect it was updated on each > side. It's the best method to corrupt PDSE. BTW: GRS won't help, because PDSE use XCF AFAIK. -- Radoslaw Skorupka Lodz, Poland -- Treść tej wiadomości może zawierać informacje prawnie chronione Banku przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorized to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, www.mBank.pl, e-mail: kont...@mbank.pl Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości wpłacony) wynosi 168.955.696 złotych. -- 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: [EXTERNAL] Re: Corrupt PDSE dataset
If you could provide fuller error messages it might help. Subcode for 0f4. And any ibe-like messages. It might make more sense Lizette -Original Message- >From: "Dyck, Lionel B. (TRA)" <lionel.d...@va.gov> >Sent: Mar 11, 2016 5:09 AM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset > >Liz - good to see you > >How should I do the copy? IEBCOPY fails as does ispf 3.3 as well as pds copy. > I can copy specific members but I don't know all the members that were added >after the backup was taken. Those members that were in the backup were all >good :-) We know of one new member and when trying to access it the result is >an Abend 0F4 :( > >-Original Message- >From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On >Behalf Of Lizette Koehler >Sent: Thursday, March 10, 2016 3:56 PM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset > >copy to new file. See what is broken >Lizette > >-Original Message- >>From: "Dyck, Lionel B. (TRA)" <lionel.d...@va.gov> >>Sent: Mar 10, 2016 11:19 AM >>To: IBM-MAIN@LISTSERV.UA.EDU >>Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset >> >>Tried restore from backup but there isn't one current enough that isn't >>corrupted. >> >> >>--- >>--- >>Lionel B. Dyck (Contractor) >>Mainframe Systems Programmer >>Enterprise Infrastructure Support (Station 200) (005OP6.3.10) VA OI >>Service Delivery & Engineering >>Office: 512-326-6173 >>Cell: 925-348-0237 >> >> >>-Original Message- >>From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >>On Behalf Of Edward Finnell >>Sent: Thursday, March 10, 2016 12:17 PM >>To: IBM-MAIN@LISTSERV.UA.EDU >>Subject: [EXTERNAL] Re: Corrupt PDSE dataset >> >>Restore from backup? >> >> >>In a message dated 3/10/2016 12:12:29 P.M. Central Standard Time, >>lionel.d...@va.gov writes: >> >>What do y'all recommend when a PDSE goes bad and the IEBPDSE just reports >>that it has a bad directory? >> >> >> >>-- >>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 > >-- >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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: Corrupt PDSE dataset
On 03/11/2016 07:40 AM, Clark Morris wrote: > On 11 Mar 2016 04:12:49 -0800, in bit.listserv.ibm-main you wrote: > >> Skip - good to see you as well. I suspect the ST FixPDS won't fix this but >> as I don't have ST I can't try it. The PDS on the CBTTape fails as does >> IEBPDSE. Sadly IBM level 2 could not help either. > How does PDSE recognize the beginning and end of a member? does a > member have to occupy contiguous space? > > Clark Morris Since a PDSE doesn't support or require defragmentation to recover and reuse deleted space, the answer is obviously that neither members nor the PDSE directory itself require contiguous space. I don't recall any discussion of the details of how a PDSE links to successor blocks. If there are either links from one data block of a member to the next block, or something external to the data blocks similar in function to a PC file system FAT (File Allocation Table) that contains those pointers, then there might be a chance of partial recovery; but it all depends on that pointer information being intact, reading all pointers for the entire file in order to find a list of unique chains and earliest block for each chain, and eliminating from that list those chains for readable members reached from readable directory information. Unaccounted-for chains would then potentially be pieces of deleted or unreachable members. Obviously any attempt to do that successfully requires a knowledge of PDSE internals beyond the advertised user interfaces. And if the nature of the PDSE damage was such that blocks of interest were erroneously thought to be free and were re-used for other data before the problem was discovered, then you are SOL. Joel C. Ewing >> -Original Message- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On >> Behalf Of Jesse 1 Robinson >> Sent: Thursday, March 10, 2016 7:08 PM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset >> >> I have the Serena program product version StarTool. FIXPDS is there for a >> PDSE, but I don't have a broken data set to experiment with. The options are >> fewer than for PDS largely because you can't muck with the directory in a >> PDSE. >> >> Despite the moniker 'FIX', this function is used mainly to alter attributes >> of a healthy PDS, not to repair a damaged one. >> >> . >> . >> . >> J.O.Skip Robinson >> Southern California Edison Company >> Electric Dragon Team Paddler >> SHARE MVS Program Co-Manager >> 323-715-0595 Mobile >> 626-302-7535 Office >> robin...@sce.com >> >> >> -Original Message- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On >> Behalf Of Edward Finnell >> Sent: Thursday, March 10, 2016 10:58 AM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: (External):Re: [EXTERNAL] Re: Corrupt PDSE dataset >> >> Haven't heard from JK in a while. PDS86 has fixpds command. I've used it on >> 100's of PDS's but not a PDSE. Might try on a unusable restored copy? >> >> >> In a message dated 3/10/2016 12:48:14 P.M. Central Standard Time, >> lionel.d...@va.gov writes: >> >> Are you saying I can back it up with DFDSS and then try to restore it and >> it might work? >> > -- Joel C. Ewing,Bentonville, AR jcew...@acm.org -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: Corrupt PDSE dataset
W dniu 2016-03-11 o 15:20, Dyck, Lionel B. (TRA) pisze: We have shared dasd between two different sysplexes and grs is only within each sysplex. How it broke I've no idea but suspect it was updated on each side. It's the best method to corrupt PDSE. BTW: GRS won't help, because PDSE use XCF AFAIK. -- Radoslaw Skorupka Lodz, Poland -- Treść tej wiadomości może zawierać informacje prawnie chronione Banku przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorized to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, www.mBank.pl, e-mail: kont...@mbank.pl Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości wpłacony) wynosi 168.955.696 złotych. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: Corrupt PDSE dataset
We have shared dasd between two different sysplexes and grs is only within each sysplex. How it broke I've no idea but suspect it was updated on each side. -- Lionel B. Dyck (Contractor) Mainframe Systems Programmer Enterprise Infrastructure Support (Station 200) (005OP6.3.10) VA OI Service Delivery & Engineering Office: 512-326-6173 Cell: 925-348-0237 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tom Marchant Sent: Friday, March 11, 2016 8:09 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: Corrupt PDSE dataset On Thu, 10 Mar 2016 12:12:09 -0600, Dyck, Lionel B. wrote: >What do y'all recommend when a PDSE goes bad and the IEBPDSE just reports that >it has a bad directory? I don't know how to fix it, but I am curious as to what happened to it. Is the broken PDSE shared outside of the sysplex? -- Tom Marchant -- 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 dataset
On Thu, 10 Mar 2016 12:12:09 -0600, Dyck, Lionel B. wrote: >What do y'all recommend when a PDSE goes bad and the IEBPDSE just reports that >it has a bad directory? I don't know how to fix it, but I am curious as to what happened to it. Is the broken PDSE shared outside of the sysplex? -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: Corrupt PDSE dataset
On 11 Mar 2016 04:12:49 -0800, in bit.listserv.ibm-main you wrote: >Skip - good to see you as well. I suspect the ST FixPDS won't fix this but as >I don't have ST I can't try it. The PDS on the CBTTape fails as does IEBPDSE. > Sadly IBM level 2 could not help either. How does PDSE recognize the beginning and end of a member? does a member have to occupy contiguous space? Clark Morris > >-Original Message- >From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On >Behalf Of Jesse 1 Robinson >Sent: Thursday, March 10, 2016 7:08 PM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset > >I have the Serena program product version StarTool. FIXPDS is there for a >PDSE, but I don't have a broken data set to experiment with. The options are >fewer than for PDS largely because you can't muck with the directory in a >PDSE. > >Despite the moniker 'FIX', this function is used mainly to alter attributes of >a healthy PDS, not to repair a damaged one. > >. >. >. >J.O.Skip Robinson >Southern California Edison Company >Electric Dragon Team Paddler >SHARE MVS Program Co-Manager >323-715-0595 Mobile >626-302-7535 Office >robin...@sce.com > > >-Original Message- >From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On >Behalf Of Edward Finnell >Sent: Thursday, March 10, 2016 10:58 AM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: (External):Re: [EXTERNAL] Re: Corrupt PDSE dataset > >Haven't heard from JK in a while. PDS86 has fixpds command. I've used it on >100's of PDS's but not a PDSE. Might try on a unusable restored copy? > > >In a message dated 3/10/2016 12:48:14 P.M. Central Standard Time, >lionel.d...@va.gov writes: > >Are you saying I can back it up with DFDSS and then try to restore it and it >might work? > >-- >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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: Corrupt PDSE dataset
Skip - good to see you as well. I suspect the ST FixPDS won't fix this but as I don't have ST I can't try it. The PDS on the CBTTape fails as does IEBPDSE. Sadly IBM level 2 could not help either. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jesse 1 Robinson Sent: Thursday, March 10, 2016 7:08 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset I have the Serena program product version StarTool. FIXPDS is there for a PDSE, but I don't have a broken data set to experiment with. The options are fewer than for PDS largely because you can't muck with the directory in a PDSE. Despite the moniker 'FIX', this function is used mainly to alter attributes of a healthy PDS, not to repair a damaged one. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Edward Finnell Sent: Thursday, March 10, 2016 10:58 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: [EXTERNAL] Re: Corrupt PDSE dataset Haven't heard from JK in a while. PDS86 has fixpds command. I've used it on 100's of PDS's but not a PDSE. Might try on a unusable restored copy? In a message dated 3/10/2016 12:48:14 P.M. Central Standard Time, lionel.d...@va.gov writes: Are you saying I can back it up with DFDSS and then try to restore it and it might work? -- 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: [EXTERNAL] Re: Corrupt PDSE dataset
Liz - good to see you How should I do the copy? IEBCOPY fails as does ispf 3.3 as well as pds copy. I can copy specific members but I don't know all the members that were added after the backup was taken. Those members that were in the backup were all good :-) We know of one new member and when trying to access it the result is an Abend 0F4 :( -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lizette Koehler Sent: Thursday, March 10, 2016 3:56 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset copy to new file. See what is broken Lizette -Original Message- >From: "Dyck, Lionel B. (TRA)" <lionel.d...@va.gov> >Sent: Mar 10, 2016 11:19 AM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset > >Tried restore from backup but there isn't one current enough that isn't >corrupted. > > >--- >--- >Lionel B. Dyck (Contractor) >Mainframe Systems Programmer >Enterprise Infrastructure Support (Station 200) (005OP6.3.10) VA OI >Service Delivery & Engineering >Office: 512-326-6173 >Cell: 925-348-0237 > > >-Original Message- >From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >On Behalf Of Edward Finnell >Sent: Thursday, March 10, 2016 12:17 PM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: [EXTERNAL] Re: Corrupt PDSE dataset > >Restore from backup? > > >In a message dated 3/10/2016 12:12:29 P.M. Central Standard Time, >lionel.d...@va.gov writes: > >What do y'all recommend when a PDSE goes bad and the IEBPDSE just reports >that it has a bad directory? > > > >-- >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 -- 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: [EXTERNAL] Re: Corrupt PDSE dataset
I have the Serena program product version StarTool. FIXPDS is there for a PDSE, but I don't have a broken data set to experiment with. The options are fewer than for PDS largely because you can't muck with the directory in a PDSE. Despite the moniker 'FIX', this function is used mainly to alter attributes of a healthy PDS, not to repair a damaged one. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Edward Finnell Sent: Thursday, March 10, 2016 10:58 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: [EXTERNAL] Re: Corrupt PDSE dataset Haven't heard from JK in a while. PDS86 has fixpds command. I've used it on 100's of PDS's but not a PDSE. Might try on a unusable restored copy? In a message dated 3/10/2016 12:48:14 P.M. Central Standard Time, lionel.d...@va.gov writes: Are you saying I can back it up with DFDSS and then try to restore it and it might work? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: Corrupt PDSE dataset
copy to new file. See what is broken Lizette -Original Message- >From: "Dyck, Lionel B. (TRA)" <lionel.d...@va.gov> >Sent: Mar 10, 2016 11:19 AM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset > >Tried restore from backup but there isn't one current enough that isn't >corrupted. > > >-- >Lionel B. Dyck (Contractor) >Mainframe Systems Programmer >Enterprise Infrastructure Support (Station 200) (005OP6.3.10) >VA OI Service Delivery & Engineering >Office: 512-326-6173 >Cell: 925-348-0237 > > >-Original Message- >From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On >Behalf Of Edward Finnell >Sent: Thursday, March 10, 2016 12:17 PM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: [EXTERNAL] Re: Corrupt PDSE dataset > >Restore from backup? > > >In a message dated 3/10/2016 12:12:29 P.M. Central Standard Time, >lionel.d...@va.gov writes: > >What do y'all recommend when a PDSE goes bad and the IEBPDSE just reports >that it has a bad directory? > > > >-- >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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: Corrupt PDSE dataset
Haven't heard from JK in a while. PDS86 has fixpds command. I've used it on 100's of PDS's but not a PDSE. Might try on a unusable restored copy? In a message dated 3/10/2016 12:48:14 P.M. Central Standard Time, lionel.d...@va.gov writes: Are you saying I can back it up with DFDSS and then try to restore it and it might work? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: Corrupt PDSE dataset
Tom - how right you are - I've opened a PMR with IBM and am awaiting their response. Are you saying I can back it up with DFDSS and then try to restore it and it might work? -- Lionel B. Dyck (Contractor) Mainframe Systems Programmer Enterprise Infrastructure Support (Station 200) (005OP6.3.10) VA OI Service Delivery & Engineering Office: 512-326-6173 Cell: 925-348-0237 Lionel, Open a PMR with IBM. Tom Reed just presented at SHARE that DFDSS restore should reorg the PDSE and get rid of the corruption. If you have already done that and the PDSE is still corrupted, then you need help, son. Regards, Tom Conley -- 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: [EXTERNAL] Re: Corrupt PDSE dataset
On 3/10/2016 1:19 PM, Dyck, Lionel B. , TRA wrote: Tried restore from backup but there isn't one current enough that isn't corrupted. -- Lionel B. Dyck (Contractor) Mainframe Systems Programmer Enterprise Infrastructure Support (Station 200) (005OP6.3.10) VA OI Service Delivery & Engineering Office: 512-326-6173 Cell: 925-348-0237 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Edward Finnell Sent: Thursday, March 10, 2016 12:17 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: Corrupt PDSE dataset Restore from backup? In a message dated 3/10/2016 12:12:29 P.M. Central Standard Time, lionel.d...@va.gov writes: What do y'all recommend when a PDSE goes bad and the IEBPDSE just reports that it has a bad directory? Lionel, Open a PMR with IBM. Tom Reed just presented at SHARE that DFDSS restore should reorg the PDSE and get rid of the corruption. If you have already done that and the PDSE is still corrupted, then you need help, son. Regards, Tom Conley -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: Corrupt PDSE dataset
Tried restore from backup but there isn't one current enough that isn't corrupted. -- Lionel B. Dyck (Contractor) Mainframe Systems Programmer Enterprise Infrastructure Support (Station 200) (005OP6.3.10) VA OI Service Delivery & Engineering Office: 512-326-6173 Cell: 925-348-0237 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Edward Finnell Sent: Thursday, March 10, 2016 12:17 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: Corrupt PDSE dataset Restore from backup? In a message dated 3/10/2016 12:12:29 P.M. Central Standard Time, lionel.d...@va.gov writes: What do y'all recommend when a PDSE goes bad and the IEBPDSE just reports that it has a bad directory? -- 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 dataset
Try recycling the PDSE address space(s). Doug Fuerst Principal Consultant BK Associates 718.921.2620 (O) 917.572.7364 (C) d...@bkassociates.net -- Original Message -- From: "Dyck, Lionel B. (TRA)" <lionel.d...@va.gov> To: IBM-MAIN@listserv.ua.edu Sent: 10-Mar-16 1:12:09 PM Subject: Corrupt PDSE dataset What do y'all recommend when a PDSE goes bad and the IEBPDSE just reports that it has a bad directory? Thanks -- Lionel B. Dyck (Contractor) Mainframe Systems Programmer Enterprise Infrastructure Support (Station 200) (005OP6.3.10) VA OI Service Delivery & Engineering Office: 512-326-6173 Cell: 925-348-0237 -- 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 dataset
Restore from backup? In a message dated 3/10/2016 12:12:29 P.M. Central Standard Time, lionel.d...@va.gov writes: What do y'all recommend when a PDSE goes bad and the IEBPDSE just reports that it has a bad directory? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Corrupt PDSE dataset
What do y'all recommend when a PDSE goes bad and the IEBPDSE just reports that it has a bad directory? Thanks -- Lionel B. Dyck (Contractor) Mainframe Systems Programmer Enterprise Infrastructure Support (Station 200) (005OP6.3.10) VA OI Service Delivery & Engineering Office: 512-326-6173 Cell: 925-348-0237 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Corrupt PDSE
===start The dataset has a member which has all configuration Parms for a running STC This was updated when STC was up and running So This could be a reason for a possible corruption ? end=== Yes. start=== I get below message when i try to access a PDSE dataset, but when I try to access the same Dataset from a different SYSPLEX it opens up. We do share the Dasd . =end== i've worked in an environment where DASD was SHAREd across several PLEX's, but with the cardinal rule of NO PDSE's. use DSORG=PS or DSORG=PO with IBM's help, determine if there is physical damage to the file, or only an in-memory corruption. if it's the latter, recycling SMSPDSE* may be the answer - again, consult IBM after they have analyzed your SVC dumps. - ravi. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Corrupt PDSE
how about moving the members to a sequential file each ? - ravi. ps: never peek at another SYSPLEX's PDSEs ... -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Corrupt PDSE
At 22:43 +0530 on 07/15/2015, Jake Anderson wrote about Re: Corrupt PDSE: Hi The dataset has a member which has all configuration Parms for a running STC This was updated when STC was up and running So This could be a reason for a possible corruption ? Why not move that member to a PDS (Which is allowed to be shared across LPARs) and either point a DD to that one file or make the DD pointing at the PDSE a concatenation of the PDS and the PDSE? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Corrupt PDSE
IT depends. How do you change the configuration? Do you have to cycle the STC? Do you have to refresh something? Did you do it on all systems that the PDS/E is being used? Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jake Anderson Sent: Wednesday, July 15, 2015 10:13 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Corrupt PDSE Hi The dataset has a member which has all configuration Parms for a running STC This was updated when STC was up and running So This could be a reason for a possible corruption ? On Wednesday 15 July 2015, Lizette Koehler stars...@mindspring.com wrote: And basically if you are only using the PDS/E within the same SYSPLEX. Then you should open a case with IBM for assistance. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM- m...@listserv.ua.edu javascript:;] On Behalf Of Roberto Halais Sent: Wednesday, July 15, 2015 9:40 AM To: IBM-MAIN@LISTSERV.UA.EDU javascript:; Subject: Re: Corrupt PDSE Ibm Info on corrupted PDSEs: http://www-01.ibm.com/support/docview.wss?uid=isg1II14252 On Wed, Jul 15, 2015 at 11:39 AM, Jake Anderson justmainfra...@gmail.com javascript:; wrote: Hello, I get below message when i try to access a PDSE dataset, but when I try to access the same Dataset from a different SYSPLEX it opens up. We do share the Dasd . IGW702I PDSE Directory Validation Unsuccessful DESC:ND Structure is corrupted LTK: 000 0* ERROR NUM:15 DSN:JAKE.PDSE.JCL VOLSER:TCHN011 RC:8 RS:0118800E R14:8A55EDCE RPN:N/A VPTVFN:N/A IGW702I PDSE Directory Validation Unsuccessful DESC:ND Structure is corrupted LTK: 000 0* ERROR NUM:14 DSN:CA.JAKE.PDSE.JCL VOLSER:TCHN011 RC:8 RS:0118800E R14:8A55EDE8 RPN:N/A MEMBER NAME:NETUPQ VPTVFN:N/A IEA995I SYMPTOM DUMP OUTPUT SYSTEM COMPLETION CODE=0F4 REASON CODE=0024 TIME=11.32.41 SEQ=04674 CPU= ASID=01D8 PSW AT TIME OF ERROR 075C1000 8A66C6E0 ILC 2 INTC 0D NO ACTIVE MODULE FOUND - PRIMARY NOT EQUAL TO HOME NAME=UNKNOWN DATA AT PSW 0A66C6DA - 58F05048 0A0DB219 A788 AR/GR 0: 009FF890/_0118800E 1: /_040F4000 2: /0048_00FDB290 3: /_7F2E8268 4: /_7703 5: 0002/_7F2ED0C0 6: /_7F2E8060 7: /_00FD8ED8 8: /_00FD8F48 9: /_7F2E8268 A: /_7F2ED4D8 B: /_ C: /_0A66C062 D: /_7F2ED3E8 E: /_8A66C6D2 F: /_0024 END OF SYMPTOM DUMP IEC036I 002-A4,IGC0005E,JAKE11,TSOPROC,ISP11321,Z09E,TCHN011, JAKE.PDSE.JCL *** Any pointers where I might be looking into ? Jake -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu javascript:; 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Corrupt PDSE
Get a back-up copy from the good SYSPLEX. Stop sharing it across SYSPLEX. (Unless you don't update from anywhere between IPLS :) ) -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jake Anderson Sent: Wednesday, July 15, 2015 8:40 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Corrupt PDSE Hello, I get below message when i try to access a PDSE dataset, but when I try to access the same Dataset from a different SYSPLEX it opens up. We do share the Dasd . IGW702I PDSE Directory Validation Unsuccessful DESC:ND Structure is corrupted LTK: 000 0* ERROR NUM:15 DSN:JAKE.PDSE.JCL VOLSER:TCHN011 RC:8 RS:0118800E R14:8A55EDCE RPN:N/A VPTVFN:N/A IGW702I PDSE Directory Validation Unsuccessful DESC:ND Structure is corrupted LTK: 000 0* ERROR NUM:14 DSN:CA.JAKE.PDSE.JCL VOLSER:TCHN011 RC:8 RS:0118800E R14:8A55EDE8 RPN:N/A MEMBER NAME:NETUPQ VPTVFN:N/A IEA995I SYMPTOM DUMP OUTPUT SYSTEM COMPLETION CODE=0F4 REASON CODE=0024 TIME=11.32.41 SEQ=04674 CPU= ASID=01D8 PSW AT TIME OF ERROR 075C1000 8A66C6E0 ILC 2 INTC 0D NO ACTIVE MODULE FOUND - PRIMARY NOT EQUAL TO HOME NAME=UNKNOWN DATA AT PSW 0A66C6DA - 58F05048 0A0DB219 A788 AR/GR 0: 009FF890/_0118800E 1: /_040F4000 2: /0048_00FDB290 3: /_7F2E8268 4: /_7703 5: 0002/_7F2ED0C0 6: /_7F2E8060 7: /_00FD8ED8 8: /_00FD8F48 9: /_7F2E8268 A: /_7F2ED4D8 B: /_ C: /_0A66C062 D: /_7F2ED3E8 E: /_8A66C6D2 F: /_0024 END OF SYMPTOM DUMP IEC036I 002-A4,IGC0005E,JAKE11,TSOPROC,ISP11321,Z09E,TCHN011, JAKE.PDSE.JCL *** Any pointers where I might be looking into ? Jake -- 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
Hi The dataset has a member which has all configuration Parms for a running STC This was updated when STC was up and running So This could be a reason for a possible corruption ? On Wednesday 15 July 2015, Lizette Koehler stars...@mindspring.com wrote: And basically if you are only using the PDS/E within the same SYSPLEX. Then you should open a case with IBM for assistance. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU javascript:;] On Behalf Of Roberto Halais Sent: Wednesday, July 15, 2015 9:40 AM To: IBM-MAIN@LISTSERV.UA.EDU javascript:; Subject: Re: Corrupt PDSE Ibm Info on corrupted PDSEs: http://www-01.ibm.com/support/docview.wss?uid=isg1II14252 On Wed, Jul 15, 2015 at 11:39 AM, Jake Anderson justmainfra...@gmail.com javascript:; wrote: Hello, I get below message when i try to access a PDSE dataset, but when I try to access the same Dataset from a different SYSPLEX it opens up. We do share the Dasd . IGW702I PDSE Directory Validation Unsuccessful DESC:ND Structure is corrupted LTK: 000 0* ERROR NUM:15 DSN:JAKE.PDSE.JCL VOLSER:TCHN011 RC:8 RS:0118800E R14:8A55EDCE RPN:N/A VPTVFN:N/A IGW702I PDSE Directory Validation Unsuccessful DESC:ND Structure is corrupted LTK: 000 0* ERROR NUM:14 DSN:CA.JAKE.PDSE.JCL VOLSER:TCHN011 RC:8 RS:0118800E R14:8A55EDE8 RPN:N/A MEMBER NAME:NETUPQ VPTVFN:N/A IEA995I SYMPTOM DUMP OUTPUT SYSTEM COMPLETION CODE=0F4 REASON CODE=0024 TIME=11.32.41 SEQ=04674 CPU= ASID=01D8 PSW AT TIME OF ERROR 075C1000 8A66C6E0 ILC 2 INTC 0D NO ACTIVE MODULE FOUND - PRIMARY NOT EQUAL TO HOME NAME=UNKNOWN DATA AT PSW 0A66C6DA - 58F05048 0A0DB219 A788 AR/GR 0: 009FF890/_0118800E 1: /_040F4000 2: /0048_00FDB290 3: /_7F2E8268 4: /_7703 5: 0002/_7F2ED0C0 6: /_7F2E8060 7: /_00FD8ED8 8: /_00FD8F48 9: /_7F2E8268 A: /_7F2ED4D8 B: /_ C: /_0A66C062 D: /_7F2ED3E8 E: /_8A66C6D2 F: /_0024 END OF SYMPTOM DUMP IEC036I 002-A4,IGC0005E,JAKE11,TSOPROC,ISP11321,Z09E,TCHN011, JAKE.PDSE.JCL *** Any pointers where I might be looking into ? Jake -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu javascript:; 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
Look into the fact that you can't share PDSE's across SYSPLEX's. - -teD - Original Message From: Jake Anderson Sent: Wednesday, July 15, 2015 17:31 To: IBM-MAIN@LISTSERV.UA.EDU Reply To: IBM Mainframe Discussion List Subject: Corrupt PDSE Hello, I get below message when i try to access a PDSE dataset, but when I try to access the same Dataset from a different SYSPLEX it opens up. We do share the Dasd . IGW702I PDSE Directory Validation Unsuccessful DESC:ND Structure is corrupted LTK: * ERROR NUM:15 DSN:JAKE.PDSE.JCL VOLSER:TCHN011 RC:8 RS:0118800E R14:8A55EDCE RPN:N/A VPTVFN:N/A IGW702I PDSE Directory Validation Unsuccessful DESC:ND Structure is corrupted LTK: * ERROR NUM:14 DSN:CA.JAKE.PDSE.JCL VOLSER:TCHN011 RC:8 RS:0118800E R14:8A55EDE8 RPN:N/A MEMBER NAME:NETUPQ VPTVFN:N/A IEA995I SYMPTOM DUMP OUTPUT SYSTEM COMPLETION CODE=0F4 REASON CODE=0024 TIME=11.32.41 SEQ=04674 CPU= ASID=01D8 PSW AT TIME OF ERROR 075C1000 8A66C6E0 ILC 2 INTC 0D NO ACTIVE MODULE FOUND - PRIMARY NOT EQUAL TO HOME NAME=UNKNOWN DATA AT PSW 0A66C6DA - 58F05048 0A0DB219 A788 AR/GR 0: 009FF890/_0118800E 1: /_040F4000 2: /0048_00FDB290 3: /_7F2E8268 4: /_7703 5: 0002/_7F2ED0C0 6: /_7F2E8060 7: /_00FD8ED8 8: /_00FD8F48 9: /_7F2E8268 A: /_7F2ED4D8 B: /_ C: /_0A66C062 D: /_7F2ED3E8 E: /_8A66C6D2 F: /_0024 END OF SYMPTOM DUMP IEC036I 002-A4,IGC0005E,JAKE11,TSOPROC,ISP11321,Z09E,TCHN011, JAKE.PDSE.JCL *** Any pointers where I might be looking into ? Jake -- 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
It's possible to get away with inter-sysplex PDSE sharing for such a long time that people forget that it's verboten. I'm told that ISV serialization products like MIM do not solve this problem. BTW this is a common inhibitor to COBOL V5, which requires PDSE for load modules. Many shops have historically shared load libraries across GRS-plex boundaries. This may work (indefinitely) for traditional PO. It's deadly for PDSE. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Staller, Allan Sent: Wednesday, July 15, 2015 8:46 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Corrupt PDSE PDSE's *CANNOT* be shared across SYSPLEX Boundaries. PDSE's *CAN* be shared within a SYSPLEX if the SMSPDSE* address spaces are running... HTH, snip I get below message when i try to access a PDSE dataset, but when I try to access the same Dataset from a different SYSPLEX it opens up. We do share the Dasd . IGW702I PDSE Directory Validation Unsuccessful DESC:ND Structure is corrupted LTK: * ERROR NUM:15 ..remainder deleted /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Corrupt PDSE
Hello, I get below message when i try to access a PDSE dataset, but when I try to access the same Dataset from a different SYSPLEX it opens up. We do share the Dasd . IGW702I PDSE Directory Validation Unsuccessful DESC:ND Structure is corrupted LTK: * ERROR NUM:15 DSN:JAKE.PDSE.JCL VOLSER:TCHN011 RC:8 RS:0118800E R14:8A55EDCE RPN:N/A VPTVFN:N/A IGW702I PDSE Directory Validation Unsuccessful DESC:ND Structure is corrupted LTK: * ERROR NUM:14 DSN:CA.JAKE.PDSE.JCL VOLSER:TCHN011 RC:8 RS:0118800E R14:8A55EDE8 RPN:N/A MEMBER NAME:NETUPQ VPTVFN:N/A IEA995I SYMPTOM DUMP OUTPUT SYSTEM COMPLETION CODE=0F4 REASON CODE=0024 TIME=11.32.41 SEQ=04674 CPU= ASID=01D8 PSW AT TIME OF ERROR 075C1000 8A66C6E0 ILC 2 INTC 0D NO ACTIVE MODULE FOUND - PRIMARY NOT EQUAL TO HOME NAME=UNKNOWN DATA AT PSW 0A66C6DA - 58F05048 0A0DB219 A788 AR/GR 0: 009FF890/_0118800E 1: /_040F4000 2: /0048_00FDB290 3: /_7F2E8268 4: /_7703 5: 0002/_7F2ED0C0 6: /_7F2E8060 7: /_00FD8ED8 8: /_00FD8F48 9: /_7F2E8268 A: /_7F2ED4D8 B: /_ C: /_0A66C062 D: /_7F2ED3E8 E: /_8A66C6D2 F: /_0024 END OF SYMPTOM DUMP IEC036I 002-A4,IGC0005E,JAKE11,TSOPROC,ISP11321,Z09E,TCHN011, JAKE.PDSE.JCL *** Any pointers where I might be looking into ? Jake -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Corrupt PDSE
PDSE's *CANNOT* be shared across SYSPLEX Boundaries. PDSE's *CAN* be shared within a SYSPLEX if the SMSPDSE* address spaces are running... HTH, snip I get below message when i try to access a PDSE dataset, but when I try to access the same Dataset from a different SYSPLEX it opens up. We do share the Dasd . IGW702I PDSE Directory Validation Unsuccessful DESC:ND Structure is corrupted LTK: * ERROR NUM:15 ..remainder deleted /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Corrupt PDSE
Ibm Info on corrupted PDSEs: http://www-01.ibm.com/support/docview.wss?uid=isg1II14252 On Wed, Jul 15, 2015 at 11:39 AM, Jake Anderson justmainfra...@gmail.com wrote: Hello, I get below message when i try to access a PDSE dataset, but when I try to access the same Dataset from a different SYSPLEX it opens up. We do share the Dasd . IGW702I PDSE Directory Validation Unsuccessful DESC:ND Structure is corrupted LTK: * ERROR NUM:15 DSN:JAKE.PDSE.JCL VOLSER:TCHN011 RC:8 RS:0118800E R14:8A55EDCE RPN:N/A VPTVFN:N/A IGW702I PDSE Directory Validation Unsuccessful DESC:ND Structure is corrupted LTK: * ERROR NUM:14 DSN:CA.JAKE.PDSE.JCL VOLSER:TCHN011 RC:8 RS:0118800E R14:8A55EDE8 RPN:N/A MEMBER NAME:NETUPQ VPTVFN:N/A IEA995I SYMPTOM DUMP OUTPUT SYSTEM COMPLETION CODE=0F4 REASON CODE=0024 TIME=11.32.41 SEQ=04674 CPU= ASID=01D8 PSW AT TIME OF ERROR 075C1000 8A66C6E0 ILC 2 INTC 0D NO ACTIVE MODULE FOUND - PRIMARY NOT EQUAL TO HOME NAME=UNKNOWN DATA AT PSW 0A66C6DA - 58F05048 0A0DB219 A788 AR/GR 0: 009FF890/_0118800E 1: /_040F4000 2: /0048_00FDB290 3: /_7F2E8268 4: /_7703 5: 0002/_7F2ED0C0 6: /_7F2E8060 7: /_00FD8ED8 8: /_00FD8F48 9: /_7F2E8268 A: /_7F2ED4D8 B: /_ C: /_0A66C062 D: /_7F2ED3E8 E: /_8A66C6D2 F: /_0024 END OF SYMPTOM DUMP IEC036I 002-A4,IGC0005E,JAKE11,TSOPROC,ISP11321,Z09E,TCHN011, JAKE.PDSE.JCL *** Any pointers where I might be looking into ? Jake -- 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
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
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 ___ 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
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