IBM Support

PM62027: POINTER ERROR OCCURRED WHEN RECOVERING DATABASE WITH HPIC AND DBRC=NO

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Pointer error occurred when recovering database with HPIC and
    DBRC=NO.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMS High Performance Image Copy for z/OS *
    *                 Version 4 Release 2 users ( FMID=H1J0420 )   *
    ****************************************************************
    * PROBLEM DESCRIPTION: This APAR includes the forward fit fix  *
    *                      for IMS HP Image Copy APAR PM60811.     *
    *                                                              *
    *                      Recovery function of HP Image Copy      *
    *                      makes a broken OSAM database, if        *
    *                      database data set is allocated by JCL   *
    *                      definition in a JOB step with DISP=NEW  *
    *                      and the inputs are an image copy data   *
    *                      set and SLDS data sets.                 *
    ****************************************************************
    * RECOMMENDATION: Apply the maintenance for this APAR.         *
    ****************************************************************
    This APAR includes the forward fit fix for IMS HP Image Copy
    APAR PM60811.
    
    Recovery function of HP Image Copy makes a broken OSAM database,
    when it runs with following conditions:
    - Input data of the Recovery function is both image copy data
      set and SLDS log data sets.
    - Recovered database data set is allocated by JCL definition
      in a JOB step with DISP=NEW.
    - High Performance I/O (HPIO) is used.
    
    The cause of making the broken OSAM database is that HP Image
    Copy does not change the data set disposition in JFCB to OLD
    when applying log. So that HP image copy can not get the data
    record from the database and merge log data. Then database
    record is overwritten with incorrect record format.
    

Problem conclusion

  • FABJRDBA, FABJRDBB, FABJRDB2 and FABJRDB9 have been modified to
    change to DISP=OLD in JFCB from DISP=NEW before LOG update
    process.
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PM62027

  • Reported component name

    IMS HP IMAGE CO

  • Reported component ID

    5655K9600

  • Reported release

    420

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2012-04-08

  • Closed date

    2012-04-17

  • Last modified date

    2012-05-02

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

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

    UK77881

Modules/Macros

  • FABJRDBA FABJRDBB FABJRDB2 FABJRDB9
    

Fix information

  • Fixed component name

    IMS HP IMAGE CO

  • Fixed component ID

    5655K9600

Applicable component levels

  • R420 PSY UK77881

       UP12/04/18 P F204 Ž

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"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"4.2.0","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
14 December 2020