IBM Support

PI37194: WHEN FALLBACK=Y IS USED, HPIC DOES NOT HANDLE RECON LOSS NOTIFICATION STATUS.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When FALLBACK=Y is used, HPIC does not handle RECON Loss
    Notification status.
    

Local fix

  • Use FALLBACK=N until this APAR can be applied.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMS High Performance Image Copy for z/OS *
    *                 Version 4 Release 2 users ( FMID=H1J0420 )   *
    ****************************************************************
    * PROBLEM DESCRIPTION: IMS High Performance Image Copy breaks  *
    *                      DBRC RECON data sets when the image     *
    *                      copy job and DBRC RECON reorganization  *
    *                      are running at the same time.           *
    ****************************************************************
    * RECOMMENDATION: Apply the maintenance for this APAR.         *
    ****************************************************************
    IMS High Performance Image Copy breaks DBRC RECON data sets when
    the image copy job and DBRC RECON reorganization are running at
    the same time.
    
    IMS HP Image Copy uses DBRC API and IMS modules for accessing
    DBRC RECON. For DBRC API, IMS HP Image Copy allocates RECON data
    sets dynamically by its logic before issuing DBRC API
    FUNC=STARTDBRC. When using IMS module for updating DBRC RECON,
    RECON data sets are allocates in IMS module dynamically.
    
    But if IMS module is called between FUNC=STARTDBRC and
    FUNC=STOPDBRC of DBRC API, IMS module regards RECON data sets
    are allocated in address space by JCL allocation, and can not
    receive DBRC Loss Notification.
    
    The pair of RECON data sets are switched by DBRC RECON
    reorganization, and but IMS module does not know new pair and it
    updates old pair. As the result, the data in DBRC RECON is
    conflict and it can not accessed by other processes.
    
    IMS HP Image Copy does not use IMS module and DBRC API at the
    same time. DBRC access of DBRC API and IMS module in IMS HP
    Image Copy job are serialized.
    

Problem conclusion

  • Following macros and modules have been modified that IMS HP
    Image Copy serializes DBRC RECON access from IMS modules and
    DBRC API for getting DBRC loss notification correctly.
     FABJDMPN FABJDPSN FABJDFCN FABJFCDN FABJOFL1 FABJUIC1 FABJMAP1
     FABDAID  FABDAI20
    
    Following modules have been re-assembled:
     FABDAI00 FABDAI10 FABJDAPI FABJDBCM FABJDBC1 FABJDFCA FABJDFCB
     FABJDFC2 FABJDFC3 FABJDFC4 FABJDFC9 FABJDMPA FABJDMPB FABJDMP2
     FABJDMP3 FABJDMP4 FABJDMP9 FABJDPSA FABJDPSB FABJDPS2 FABJDPS3
     FABJDPS4 FABJDPS9 FABJFCDA FABJFCDB FABJFCD2 FABJFCD3 FABJFCD4
     FABJFCD9 FABJMAIN FABJRPT0
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PI37194

  • 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

    2015-03-17

  • Closed date

    2015-04-19

  • Last modified date

    2015-05-04

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

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

    UI26846

Modules/Macros

  • FABDAI00 FABDAI10 FABDAI20 FABJDAPI FABJDBCM
    FABJDBC1 FABJDFCA FABJDFCB FABJDFC2 FABJDFC3 FABJDFC4 FABJDFC9
    FABJDMPA FABJDMPB FABJDMP2 FABJDMP3 FABJDMP4 FABJDMP9 FABJDPSA
    FABJDPSB FABJDPS2 FABJDPS3 FABJDPS4 FABJDPS9 FABJFCDA FABJFCDB
    FABJFCD2 FABJFCD3 FABJFCD4 FABJFCD9 FABJMAIN FABJOFL1 FABJRPT0
    FABJUIC1
    

Fix information

  • Fixed component name

    IMS HP IMAGE CO

  • Fixed component ID

    5655K9600

Applicable component levels

  • R420 PSY UI26846

       UP15/04/21 P F504 Ž

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