IBM Support

PH39098: Miscellaneous Fixes

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • 1) Optim makes use of DB2 tables referred to as the "directory
    tables" for storing objects and definitions related to the
    various processes associated with the product.  There has never
    been a mechanism by which users can identify the names of the
    tables in use by a particular plan.  This enhancement provides a
    new primary command, DIRTBLS, that will result in the display of
    the directory table names and the plan using them.
    
    2) A system error such as the one below may ensue if an
    incorrect name is entered for the Optim plan during product
    installation/upgrade.
    
    ------ Optim's System Error Panel 11.7.0 DB2: 81(CM)  -------
    Command ===>
    
    An Internal System Error has Occurred on yyyy/mm/dd hh:mm
    
    CCSIDInfo failed for plan CCSID
    DB2Rel=81(CM), Rel=11.7.0
    Code=-1, AuxInfo=
    01  FOPQADMN 20210406 PH35775  (001124) DS_Open
    02  FOPHS3   20180619 COPYSENT (000189) extractDB2Relationships
    03  FOPHSM   20210406 PH35775  (000561) (FOPHSM)main
    3) The FOPINS2 clist introduced with PTF UI76359 may
    display an incorrect list of available buffer pools when the
    information needed to generate the 'create tablespace'
    commands are generated.  It may also generate duplicate
    statements.
    
    3) The FOPINS2 clist introduced with PTF UI76359 may
    display an incorrect list of available buffer pools when the
    information needed to generate the 'create tablespace'
    commands are generated.  It may also generate duplicate
    statements.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Optim users and those performing product     *
    *                 installation.                                *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1) There was no way to IDENTIFY OPTIM   *
    *                      DIRECTORY TABLES IN USE within an optim *
    *                      session.                                *
    *                                                              *
    *                      2) DB2 "plan not found" errors in       *
    *                      installation/upgrade processes result   *
    *                      in system errors.                       *
    *                                                              *
    *                      3) An incorrect Buffer Pool list may be *
    *                      presented and duplicate "create         *
    *                      tablespace" statements may be generated *
    *                      by the FOPINS2 clist.                   *
    ****************************************************************
    * RECOMMENDATION: Apply the fix provided.                      *
    ****************************************************************
    1) There was no method to display the names of the Optim
    tables in use other than querying DB2 itself.
    
    2) Errors caused when DB2 cannot find the Optim plan specified
    during installation or upgrade were not being properly
    identified.
    
    3) Due to a set of logic errors an incorrect list
    of acceptable values for the DB2 Buffer Pools was
    being displayed in the FOPINS2 clist.
    

Problem conclusion

  • 1) Code has been added to enable the user to idenfity the Optim
    directory tables in use via the DIRTBLS primary command.
    
    2) Errors caused by an incorrect Optim plan name being entered
    by the user are now caught and a message issued.
    
    3) The list of valid Buffer Pools is now correct when displayed.
    Duplicate "CREATE TABLESPACE" statements are no longer
    generated.
    
    The Optim DB2 DBRMs were modified by this fix.  Therefore
    the packages must be re-bound following its application.
    Note that this APAR removes support for DB2 V9 COMPATIBILITY
    mode and lower DB2 releases.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH39098

  • Reported component name

    OPTIM MOVE FOR

  • Reported component ID

    5655V0700

  • Reported release

    B70

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function / Xsystem

  • Submitted date

    2021-07-19

  • Closed date

    2021-09-03

  • Last modified date

    2021-10-01

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

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

Modules/Macros

  • FOP0HMNP FOP1OSFN FOP9APIM FOPAM003 FOPAM004 FOPAM005 FOPAR000
    FOPAR001 FOPCFPMN FOPCXLIB FOPD2    FOPD2V85 FOPD2V91 FOPD2VA5
    FOPD2VC5 FOPD2VNN FOPDC000 FOPE0004 FOPHSTM  FOPINS0  FOPINS2
    FOPITSNM FOPMAIN  FOPMCMAI FOPMCOLA FOPMCOLP FOPMDMAI FOPMDPRC
    FOPMDXTR FOPMECMN FOPMEMAI FOPMIXMM FOPMMCMR FOPMMJBS FOPMMUNU
    FOPMMUTL FOPOMN   FOPRM000 FOPRS7   FOPRS9   FOPXM001 FOPXMC01
    FOPXMD01 FOPZFMMN FOPZMAIN
    

Fix information

  • Fixed component name

    OPTIM MOVE FOR

  • Fixed component ID

    5655V0700

Applicable component levels

  • RB70 PSY UI77016

       UP21/09/08 P F109  

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"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"B70"}]

Document Information

Modified date:
02 October 2021