IBM Support

IC77623: DB2LICM REPORTS CONNECT SERVER FROM DB2 CLIENT INSTALL

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When installing the IBM Data Server Client from any install
    media which contains a Connect Server license (trial or
    otherwise),  db2licm will display some Server-related fields.
    
    For example:
    
    db2inst1:/home/instance/db2inst1>$ db2licm -l
    Product name:                     "DB2 Connect Enterprise
    Edition"
    License type:                     "User"
    Expiry date:                      "Permanent"
    Product identifier:               "db2consv"
    Version information:              "9.7"
    Concurrent connect user policy:   "Disabled"
    Enforcement policy:               "Soft Stop"
    Number of licensed authorized users: "1"
    
    Attempts to change the license policy or number
    of authorized users will appear to succeed but have
    no effect.
    
    The reason is:
    Although any Connect license can be applied to
    a DB2 installation to unlock some Connect functionality,
    the DB2 client was reporting so in a misleading manner
    as there is no Server/Gateway function there to unlock
    on a DB2 Client installation.   Only client/direct connect
    function is unlocked.
    

Local fix

  • ignore the server-related fields in db2licm output.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL Users                                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When installing the IBM Data Server Client from any install  *
    * media which contains a Connect Server license (trial or      *
    * otherwise),  db2licm will display some Server-related        *
    * fields.                                                      *
    *                                                              *
    * For example:                                                 *
    *                                                              *
    * db2inst1:/home/instance/db2inst1>$ db2licm -l                *
    * Product name:                    "DB2 Connect Enterprise     *
    * Edition"                                                     *
    * License type:                    "User"                      *
    * Expiry date:                      "Permanent"                *
    * Product identifier:              "db2consv"                  *
    * Version information:              "9.7"                      *
    * Concurrent connect user policy:  "Disabled"                  *
    * Enforcement policy:              "Soft Stop"                 *
    * Number of licensed authorized users: "1"                     *
    *                                                              *
    * Attempts to change the license policy or number of           *
    * authorized users will appear to succeed but have no effect.  *
    *                                                              *
    * The reason is:                                               *
    * Although any Connect license can be applied to a DB2         *
    * installation to unlock some Connect functionality, the DB2   *
    * client was reporting so in a misleading manner as there is   *
    * no Server/Gateway function there to unlock on a DB2 Client   *
    * installation.  Only client/direct connect function is        *
    * unlocked.                                                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Ingore the output of db2licm for this case OR upgrade to the *
    * DB2 v9.7 FP6                                                 *
    ****************************************************************
    

Problem conclusion

  • This fix is included in DB2 v9.7 FP6
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC77623

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-07-20

  • Closed date

    2012-06-05

  • Last modified date

    2012-06-05

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

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

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.7","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
05 June 2012