IBM Support

How to identify the failing PDSE data set from an ABEND0F4 RC=00000024 RSN=050A0046 SVC DUMP

How To


Summary

Simple to follow steps to identify the failing PDSE data set from an ABEND0F4 RC24 RSN050a0046 SVC Dump

Objective

The PDSE reason code O50A0046 translates to BDS_INVALID_DSCB_EXTENTS. This reason code is an indication that the format-1 DSCB extent list on DASD does not match the view that the SMSPDSE1 or SMSPDSE address space is using to access the data set.
Receipt of this reason code is an indication that the DASD copy of the PDSE data is corrupted.  The only course of action is to restore the data set from a viable back or to re-create the data set from scratch.

Environment

 

Steps

  1. IPCS format the dump and then issue the following command:
    IPCS IEAVDUMP
  2. Find the failing user address space in the IEAVDUMP report listing. Make note of both the PDSE address space and the user address space.
    IEAVDUMP VERSION HBB77A0_OA54868                                                                                  
                                                                                                                      
    -------- GENERAL DUMP INFORMATION FOLLOWS --------                                                                
    DUMP TITLE:      COMPID=DF115,CSECT=IGWBEXT2+05C2,DATE=03/17/19,MAINTID=NONE NON,ABND=0F4,RC=00000024,RSN=050A0046
    DUMP TYPE:       SVC DUMP OF Z/OS HBB77C0, SNAME TST2                                                             
    DUMP TAKEN:      APR 15 2020, 09:16:08 (LOCAL)                                                                    
                                                                                                                      
    DUMP OF ASIDS:                                                                                                    
      X'0009'  JOBNAME: SMSPDSE1                                                                                      
      X'003A'  JOBNAME: SSTOG012                                                                                           
                                                                                      
  3. Issue the following command:
    IP VERBX IGWFPMAN 'F(AS) JOBNAME(PDSEUSER)'
  4. Find the string DSRB@ in the generated report and make note of the address.
     BMF Read Page 2:                                                               
        RPIB@:7F122CA0 LSCB@:7F6BBBC0 LSD@:7F690680 DSRB@:7F66ECC0 ENIB@:7F680660  
  5. Browse the storage for the SMSPDSE1 or SMSPDSE address space that was identified in STEP 1 and locate the DSRB address.  The PDSE data set name can be found in the IGWDSRB+70 for a length of x'2C'
    7F66ECC0: C9C7E6C4 E2D9C240 000000B8 01000000 |IGWDSRB ........|
    7F66ECD0: 7F6625F0 7F662680 D3C40000 00000000 |"..0"...LD......|
    7F66ECE0: 00000000 00000000 D3C40009 008F9E88 |........LD.....h|
    7F66ECF0: 000000A7 01E5D6D3 E2C5D900 052F0000 |...x.VOLSER.....|
    7F66ED00: 00000001 00000000 00010000 00000000 |................|
    7F66ED10: 80000000 00060200 0000052F 00000004 |................|
    7F66ED20: 0000000C 00E73BF8 14A80000 00000000 |.....X.8.y......|
    7F66ED30: E2E8E2F1 4BD7C4E2 C54BD7D9 D6C3D3C9 |SYS1.PDSE.PROCLI|
    7F66ED40: C24BD6D3 C4404040 40404040 40404040 |B.OLD           |
    7F66ED50: 40404040 40404040 40404040 00000000 |            ....|
    7F66ED60: 00000000 00000000 00000000 00000000 |................|
    7F66ED70: 00000000 00000000                   |........        |

Document Location

Worldwide

Operating System

z/OS:All operating systems listed

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG90","label":"z\/OS"},"Component":"5695DF115;PDSE","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB56","label":"Z HW"}}]

Document Information

Modified date:
20 April 2020

UID

ibm16195422

Page Feedback