IBM Support

OA35260: ABEND0C4 PIC04, PIC10, PIC11 IN IGWBLMRD (UA48501) +1148, AND ABEND0F4 RC24 IN IGWDSAAC OR IGWISRCH 11/01/07 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ABEND0C4 pic04, pic10, pic11 in IGWBLMRD (UA48501) +1148, or
    other PDSE CSECTs/modules.  This may be followed by ABEND0F4
    rc24 in IGWDSAAC or IGWISRCH, or other PDSE CSECTs/modules.
    .
    KEYWORD  5695DF115  DF115  ICYBLD64  D/T2817  ZHPF/K
    S0c4 0c4 rc4 rc04 rc10 rc11 0C4-4 0C4-04 0C4-10 0C4-11 s0F4 0F4
    
    Problem is due to Media Manager overlaying various storage areas
    in PDSE address space.
    .
    ADDITIONAL SYMPTOMS:
    Media Manager ICYTRACE logrecs for module ICYBLD64. The MMPB
    control block in these logrecs will show MMPB+64 = 001C1C0C.
    
    ABEND0C4 PIC4 in IGWFHSCN with PDSE HASH Table overlays
    
    ADDITIONAL KEYWORD: PDSE/K
    

Local fix

  • Restart PDSE address spaces.
    Circumvention: do not install OA30025 or remove OA30025 or
      disable zHPF by by use of the SETIOS command or updating the
    IECIOSxx member of parmlib to specify ZHPF=NO.
    
     KEYWORDS:   KEYWORD
    S0c4 0c4 rc4 rc04 rc10 rc11 0C4-4 0C4-04 0C4-10 0C4-11 s0F4 0F4
    5695DF115  DF115 ICYBLD64    D/T2817     ZHPF/K
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: USERS OF PDSES USING HPF CAPABLE             *
    *                 DEVICES WITH MEDIA MANAGER APAR OA30025      *
    *                 OR OA34009 INSTALLED.                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: DUMPING A PDSE WITH MULTIPLE EXTENTS    *
    *                      MAY RESULT IN A RETURN CODE OF ZERO AND *
    *                      A CORRUPTED BACKUP DATA SET.  IN MOST   *
    *                      OF THESE CASES, STORAGE IN THE          *
    *                      PDSE ADDRESS SPACE WILL BE              *
    *                      OVERLAYED CAUSING A SERIES OF S0F4      *
    *                      ABENDS.  THE PDSE1 ADDRESS SPACE MUST   *
    *                      BE RESTARTED OR, IF A RESTARTABLE       *
    *                      PDSE ADDRESS SPACE DOES NOT EXIST,      *
    *                      THE SYSTEM MUST BE RE-IPLED.            *
    *                      A SECOND SYMPTOM IS AN ABEND S0F4       *
    *                      RSN=15050018 WHILE DUMPING A PDSE       *
    *                      CAUSING THE DUMP TO FAIL WITH A         *
    *                      NON-ZERO RETURN CODE AND NO FURTHER     *
    *                      SYMPTOMS.                               *
    ****************************************************************
    * RECOMMENDATION: Dumping a PDSE with multiple extents may     *
    *                 result in a return code of zero and a        *
    *                 corrupted backup data set. In most of these  *
    *                 cases, storage in the PDSE address space     *
    *                 will be overlaid causing a series of S0F4    *
    *                 abends. The application of PTFs for APAR     *
    *                 OA30025 or OA34009 exposed this bug in PDSE  *
    *                 data set backup processing. This bug can     *
    *                 occur under the following conditions:        *
    *                 (1) The fix for OA30025 is installed.        *
    *                 (2) The PDSE to be backed up resides on a    *
    *                  device which supports HPF channel programs. *
    *                 (3) HPF processing is enabled.               *
    *                 (4) The I/O is requesting blocks of data     *
    *                  that are fragmented across multiple DASD    *
    *                  extents (more than appx. 18 extents).       *
    *                 and (5) The blocks which are to be read from *
    *                  any single extent are contiguous.           *
    *                                                              *
    *                 PDSE backups taken after the installation of *
    *                 PTFs for OA30025 or OA34009 should be        *
    *                 considered as suspect.                       *
    *                 Backups taken prior to abends in the PDSE    *
    *                 address space are most suspicious.           *
    *                 A system can be protected from further       *
    *                 exposure by one of the following means:      *
    *                 (1) Installing the corrective maintenance.   *
    *                 (2) Backing off OA30025 and OA34009 until    *
    *                  the corrective maintenance can be           *
    *                  installed.  Note: OA30025 is shipped in the *
    *                  base for z/OS V1R12 (HDZ1C10).              *
    *                 or (3) Disabling zHPF processing.            *
    *                                                              *
    *                 The PTFs for OA30025 and OA34009 have been   *
    *                 marked as PE to prevent additional customers *
    *                 from exposing their systems to this error.   *
    *                 These fixes will be reshipped with a PRE for *
    *                 the PDSE fix which is shipped with APAR      *
    *                 OA35296.                                     *
    ****************************************************************
    USERS WITH ZHPF AND APAR OA30025 OR OA34009 INSTALLED SHOULD
    INSTALL THIS APAR.
    

Problem conclusion

  • OA30025 PTFs and PTFs subsequent have been PE'd because of
    OA35296 for a problem in PDSE. OA35260 reships the media manager
    nucleus modules with new PTFs that PRE the PDSE fix PTFs UA58587
    UA58588 and UA58589. Overlays in PDSE's own address space were
    occurring because PDSE specified I/O termination in its own
    address space but client buffer address resolution in the
    secondary address space under ALET control. When MM I/O
    completion (SRB in the termination address space) recognized
    more channel programs needed to be built to complete the request
    the buffer addresses resolved into PDSE addresses instead of
    into client buffer addresses.
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    OA35260

  • Reported component name

    DFSMS MEDIA MAN

  • Reported component ID

    5695DF126

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-12-29

  • Closed date

    2011-01-11

  • Last modified date

    2014-03-28

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    OA35296 UA58641 UA58642 UA58643

Modules/Macros

  • ICYABN   ICYBLDRE ICYBLD64 ICYBLIST ICYBMFI
    ICYCCHHR ICYCILOC ICYDIE   ICYDUMP  ICYELE   ICYEXIT  ICYEXRBA
    ICYFRR   ICYFW    ICYINIT  ICYMMVT  ICYNRM   ICYPFAPP ICYPFDIE
    ICYPFMT  ICYPF64  ICYPGAD  ICYPIO   ICYPIOPG ICYPIO64 ICYPURG
    ICYRBA   ICYRCD0  ICYRDWR  ICYREP64 ICYSCHED ICYSORT  ICYSTOR
    ICYTRACE ICYVCACH ICYWRITE
    

Fix information

  • Fixed component name

    DFSMS MEDIA MAN

  • Fixed component ID

    5695DF126

Applicable component levels

  • RA10 PSY UA58641

       UP11/02/09 P F102 ®

  • RB10 PSY UA58642

       UP11/02/09 P F102 ®

  • RC10 PSY UA58643

       UP11/02/09 P F102 ®

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A10","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
28 March 2014