IBM Support

PM95734: INTERMITTENT ABENDS0C4 IN IROPARS$

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Intermittent ABENDS0C4 in IROPARS$.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All the users who use IMS Database           *
    *                 Recovery Solution Pack V1R1 might            *
    *                 be affected.                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Intermittent S0C4 abend                 *
    *                      with BPE parser.                        *
    *                      There are tow other problems            *
    *                      are fixed in this APAR:                 *
    *                      1. 0C4 in index list area.              *
    *                      2. IB error when empty data             *
    *                      was passed over from DRF.               *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    In the parsing processing, a storage was
    freed after the statement was processed, and
    then a new storage was obtained for the next
    statement. We use two identical storages,
    one for input and one for the output data.
    However, sometimes, we freed the wrong
    data storage, and BPE could not find the
    input storage and so an intermittent S0C4
    occurred.
    
    For the 0C4 in the index list area, the
    problem occurred when we have BLD_SECONDARY
    (select). If a primary index needs to be
    added, we need to have a larger storage to
    hold the data. And because every member in
    the recovery list shares same index list,
    we need to update every DBD with the
    pointer of the new storage, but somehow it
    was updated only for the DBD that has
    the primary index.
    
    For the IB error, the problem occurred when
    an invalid index was selected in BLD_SECONDARY.
    If the wrong index was the only one in the
    selected index list then we passed an empty
    statement to IB and so got rejected.
    

Problem conclusion

  • The parsing module was modified to make
    sure that we re-use two storages that
    contain input/output data to BPE for
    processing. The storges are cleared after
    one statement is processed and get ready
    for the next.
    
    FRXVSTA2 and FRXTAU00 have been modified
    for index list issues.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM95734

  • Reported component name

    IMS RCVR SOLUTN

  • Reported component ID

    5655V8600

  • Reported release

    110

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-08-23

  • Closed date

    2013-10-03

  • Last modified date

    2013-11-04

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

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

    UK98221

Modules/Macros

  • FRXEDRF0 FRXTAU00 FRXVSTA2
    

Fix information

  • Fixed component name

    IMS RCVR SOLUTN

  • Fixed component ID

    5655V8600

Applicable component levels

  • R110 PSY UK98221

       UP13/10/05 P F310

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":"1.1.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 November 2013