PM79248: AFTER APPLICATION OF APAR PM52121 / PTF UK78835, AN ABENDS0C4 CAN OCCUR IN MODULE DFSST500 WHEN THE GETSTOR REQUEST FAILS.

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • An ABEND0C4 can occur in module DFSST500, after installation
    of APAR PM52121 / PTF UK78835, because the GETSTOR request
    fails. This request fails because the GETSTOR call was coded
    incorrectly.
    In addition to this problem, a small number of PM52121 related
    issues are being included in this service.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All V11 users that have APAR PM52121 / PTF   *
    *                 UK78835 installed                            *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1.ABEND0C4 in module DFSST500 after     *
    *                      apar PM52121 due to invalid GETSTOR     *
    *                      request fails.                          *
    *                                                              *
    *                      2.DFSRCP10 using SP231 CSA for large    *
    *                      type47 records.                         *
    *                                                              *
    *                      3.DFSRBLB0 attempts to free storage     *
    *                      that was never acquired.                *
    *                                                              *
    *                      4.ABEND0C4 in DFSRBOI0 running Dynamic  *
    *                      Backout in a Batch IMS AUTHORIZED.      *
    *                                                              *
    *                      5.ABEND0C4 in DFSRBOI0, R7 lost         *
    *                      addressability to PSTLOGWA.             *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    1.The original problem reported is an ABEND0C4 in DFSST500
      attempting to use storage from an IMODULE GETSTOR that failed.
      It was also found that the FREESTOR for the same storage was
      attempted when no storage was acquired. These conditions are
      only encountered on RSR Tracking Systems.
    
    2.DFSRCP10 was using SP231 - CSA for large type47 records. SP0
      private storage is more appropriate.
    
    3.DFSRBLB0 attempts to free storage that was never acquired.
    
    4.ABEND0C4 in DFSRBOI0 running Dynamic Backout in a Batch IMS
      AUTHORIZED. The IMS GETSTOR request was using SP231, Key7
      and was allowed for the KEY8 caller due to authorization.
      When the Key7 storage was then being cleared, ABEND0C4
      occurred due to the caller running KEY8.
    
    5.R7 may lose addressability to the PSTLOGWA in DFSRBOI0.
    

Problem conclusion

  • GEN:
    KEYWORDS:
     RSRImpact
    
    *** END IMS KEYWORDS ***
    1.DFSST500 now correctly acquires storage and only attempts to
      free it when it has been successfully acquired.
    
    2.DFSRCP10 now acquires and deletes storage in SP0 instead of
      SP231.
    
    3.DFSRBLB0 now checks for the presence of storage before
      attempting to free it.
    
    4.DFSRBOI0 now determines if the caller is authorised and makes
      the decision to handle GETSTOR requests in the key of the
      caller. SP231 is used for authorized callers while SP0 is now
      used for callers running non-authorized.
    
    5.R7 is reset to point to the PSTLOGWA to correct possible loss
      addressability under label RBOI510.
    

Temporary fix

  • The fix for this APAR is BAD.  If you need to apply
    the fix for this APAR to resolve a problem, you must
    also apply the fix for APAR PM85638.
    AE13/03/26
    *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PM79248

  • Reported component name

    IMS V11

  • Reported component ID

    5635A0200

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-12-14

  • Closed date

    2013-03-20

  • Last modified date

    2013-05-06

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

    PM63331

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

Modules/Macros

  •    DFSRBLB0 DFSRBOI0 DFSRCP10 DFSST500
    

Fix information

  • Fixed component name

    IMS V11

  • Fixed component ID

    5635A0200

Applicable component levels

  • R100 PSY UK92725

       UP13/04/13 P F304 ®

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.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IMS

Software version:

100

Reference #:

PM79248

Modified date:

2013-05-06

Translate my page

Machine Translation

Content navigation