IBM Support

PM60956: SUPPORT DB2 DDF LOCATION NAMES UP TO 16 CHARACTERS DURING EXTENDED INSIGHT FEATURE CONFIGURATION

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Currently when customers are configuring a DB2 subsystem for
    monitoring in the Web Console, they are limited to 8 Character
    Location names.
    With this APAR this restriction will be lifted and the maximum
    supported location name length of 16 characters will be
    available.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
    *                 users of component                           *
    *                 - Repository Server (OPM)                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Currently when customers are            *
    *                      configuring a DB2 subsystem for         *
    *                      monitoring in the Web Console,          *
    *                      they are limited to 8 Character         *
    *                      Location names.                         *
    ****************************************************************
    * RECOMMENDATION: Apply this PTF                               *
    ****************************************************************
    Currently when customers are configuring a DB2 subsystem for
    monitoring in the Web Console, they are limited to 8 Character
    Location names.
    

Problem conclusion

  • By downloading and installing the software indicated in the
    TechNote, you will be able to use DB2 DDF location names up
    to 16 Characters when configuring a DB2 subsystem for
    Extended Insight Monitoring.
    
    KEYWORDS:
    Extended Insight, DDF location name, 16 Char
    

Temporary fix

  • Use an 8 Character DDF alias name
    

Comments

APAR Information

  • APAR number

    PM60956

  • Reported component name

    OM XE DB2PE/PM

  • Reported component ID

    5655OPE00

  • Reported release

    510

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-03-22

  • Closed date

    2012-04-05

  • 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:

    UK77720

Modules/Macros

  • FPEO$INF
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R510 PSY UK77720

       UP12/04/06 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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAV2B","label":"IBM Db2 Buffer Pool Analyzer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCT4H5","label":"IBM Tivoli OMEGAMON XE for Db2 PE \/ PM \/ BPA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
02 May 2012