IBM Support

PI41955: INCORRECT VALUES FOR IMS CONNECTION STATUS AND REGION TYPES IN TEP

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Wrong values for connection status and region type may be shown
    in TEP
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
    *                 users of component                           *
    *                 - Classic Interface                          *
    *                 - CUA Interface                              *
    *                 - TEP                                        *
    *                 - Enhanced 3270 UI                           *
    ****************************************************************
    * PROBLEM DESCRIPTION: INCORRECT VALUES FOR IMS CONNECTION     *
    *                      STATUS AND REGION TYPES IN TEP.         *
    ****************************************************************
    * RECOMMENDATION: Apply this PTF.                              *
    ****************************************************************
    PROBLEM SUMMARY:
    1. IMS regions connection statuses were set incorrectly for
       connected regions in TEP. It caused false firing of IMCN
       situation in TEP.
    2. There was difference in number of connections between TEP
       and Classic.
    3. Control region was counted as dependent region in TEP.
    4. IMCN exception sometimes did not fire in Classic when IMCN
       situation in TEP fired correctly.
    
    PROBLEM CONCLUSION:
    Logic has been changed to set statuses for regions and
    connections numbers correctly.
    Control region has been excluded from dependent regions in TEP.
    IMCN exception has been updated in Classic.
    

Problem conclusion

  • Logic has been changed to set statuses for regions and
    connections numbers correctly.
    Control region has been excluded from dependent regions in TEP.
    IMCN exception has been updated in Classic.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI41955

  • Reported component name

    OM XE DB2PE/PM

  • Reported component ID

    5655OPE00

  • Reported release

    520

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-05-28

  • Closed date

    2015-12-23

  • Last modified date

    2017-02-01

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

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

    UI34052 UI34053 UI34054

Modules/Macros

  • KD2OIMSD KO2APCGA KO2APCGK KO2APCGS KO2APCG2 KO2CIMSA KO2CIMSB
    KO2CIMSC KO2CIMSD KO2CIMSE KO2CIMSF KO2CIMSG KO2CIMSK KO2CISBA
    KO2CISBK KO2CISBS KO2CISB2 KO2IMSTH KO2IMSUH KO2OCONB KO2OZOMB
    KO2XIMSA KO2XIMSB KO2XIMSC KO2XIMSD KO2XIMSE KO2XIMSF KO2XIMSG
    KO2XIMSK
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R511 PSY UI34052

       UP15/12/25 P F512

  • R520 PSY UI34053

       UP15/12/25 P F512

  • R530 PSY UI34054

       UP15/12/25 P F512

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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2.0","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
11 January 2022