IBM Support

PM40604: IMS V9 ABENDS0C4 PIC11 IN DFSAOS60 WITH Z/OS 1.12

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The root cause of the 0C4 was identified as being caused by the
    presence of a non-zero value in DEBBINUM. The bin number (BB) in
    DEBBINUM is set to zero starting with a change to macro GETFDAD
    in IMS V10 and beyond. Therefore, this type of 0C4 in DFSAOS60
    is fixed in IMS V10 and higher when operating with z/OS 1.12.
    
    KEYWORDS: ZOS112T/K ZOS112 ZOS113T/K
    

Local fix

  • Usermod LK50474R
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMS V9 Full Function OSAM users who      *
    *                 upgrade to z/OS 1.12.                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: After upgrading to Z/OS 1.12 and still  *
    *                      running IMS V9, ABEND0C4 occurs in      *
    *                      the IMS OSAM interface module DFSAOS60. *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    After upgrading to Z/OS 1.12 and still running IMS V9, an
    ABENDS0C4 occurred in the IMS OSAM interface module DFSAOS60
    when trying to determine if extended architecture devices are
    installed.  The UCB address in R1 is bad, and we attempt to use
    this bad address to load DCEUCBEX (DASD Class Extension table
    address).  The root cause of the problem is due to a non-zero
    value in the high order byte of DEBBINUM.  The 0C4 occurs while
    looping through GETFDAD converting RBN's (Relative Block
    Numbers) to full disk address.  Because of this unexpected non-
    zero value in the high order byte of DEBBINUM, an incorrect UCB
    address is calculated.
    

Problem conclusion

  • The following modules and macro have been modified to fix the
    reported problem:
    
    ************
    * GETFDAD  *
    ************
    Code was modified to zero the bin number in R0 (&RR1) instead of
    loading the bin number from DEBBINUM.
    
    ************
    * DFSDBH30 *
    * DFSAOS60 *
    ************
    CHANGEID line was added to force re-compile to pick up change in
    GETFDAD.
    
    ************
    * DFSAOS10 *
    ************
    Code was modified to set the bin number to zero in DCBWRK1.
    
    ************
    * DFSAOS70 *
    ************
    Code was modified to issue ABENDU0403 if the bin number
    ( DEBBINUM ) is not zero.
    
    ************
    * DFSAOSF0 *
    ************
    Code was modified to set the bin number to zero in DCBFDAD.
    KEYWORDS: ZOS0201T/K ZOS0202T/K
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PM40604

  • Reported component name

    IMS V9

  • Reported component ID

    5655J3800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2011-06-01

  • Closed date

    2011-06-24

  • Last modified date

    2015-01-16

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

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

    UK69141

Modules/Macros

  • DFSAOSF0 DFSAOS10 DFSAOS60 DFSAOS70 DFSDBH30
    GETFDAD
    

Fix information

  • Fixed component name

    IMS V9

  • Fixed component ID

    5655J3800

Applicable component levels

  • R900 PSY UK69141

       UP11/06/30 P F106 Ž

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCVRBJ","label":"System Services"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
16 January 2015