IBM Support

PH11103: ODBC WORKAROUND TO RETAIN TRAILING PERIOD IN THE CHAR REPRESENTATION OF DECIMAL COLUMNS

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • To maintain platform consistency, the trailing period in the
    char representation of decimal columns is removed
    by PTF UI60551.  For applications, such as LDAP, that have a
    dependency on this trailing point, a workaround
    will be provided.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of Db2 12 for z/OS ODBC/CLI                        *
    * driver when fetching from a DECIMAL                          *
    * or NUMERIC column of scale 0 into                            *
    * SQL_C_CHAR with PH05953/UI60551 applied.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * ODBC/CLI workaround to modify the                            *
    * default behavior of the ODBC driver                          *
    * involving DECIMAL or NUMERIC data.                           *
    * LDAP may receive ABEND0C7 without                            *
    * the workaround                                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply corrective PTF when available                          *
    ****************************************************************
    This apar adds a new workaround that allows selected ODBC
    applications to modify the ODBC driver's default behavior.
    This default behavior was introduced by PH05953/UI60551 to
    resolve a cross-platform inconsistency by removing the trailing
    decimal point when fetching from a DECIMAL or NUMERIC column of
    scale 0 into SQL_C_CHAR. However, when the LDAP server fetches
    a DECIMAL or NUMERIC column of a scale 0 into SQL_C_CHAR, it
    expects the resulting character string from ODBC to contain a
    trailing decimal point. Because this decimal point is absent,
    the server received an ABEND0C7.
    

Problem conclusion

  • A new workaround has been added with this apar which allows
    the applications to modify the default behavior of the ODBC
    driver for fetching from a DECIMAL or NUMERIC column of
    scale 0 into SQL_C_CHAR .  The workaround can be enabled
    through the PATCH2 configuration keyword in the
    initialization file. Use of this workaround is limited to
    selected ODBC applications and should only be used under the
    direction of IBM Software Support.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH11103

  • Reported component name

    DB2 ODBC/JDBC/S

  • Reported component ID

    5740XYR02

  • Reported release

    C17

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-04-16

  • Closed date

    2019-05-20

  • Last modified date

    2019-06-04

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

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

    UI63117

Modules/Macros

  • DSNAOG17 DSNAOG28 DSNAOC28 DSNAOC08 DSNAOC17 DSNAOG08 DSNAOC06
    DSNAOG06 DSNAOC05 DSNAOC03 DSNAOC02 DSNAOG02 DSNAOG03 DSNAOG05
    DSNAOSDK DSNAOCLI
    

Fix information

  • Fixed component name

    DB2 ODBC/JDBC/S

  • Fixed component ID

    5740XYR02

Applicable component levels

  • RC17 PSY UI63117

       UP19/06/04 I 1000

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.



Document information

More support for: DB2 for z/OS
SQLJ/JDBC

Software version: C17

Reference #: PH11103

Modified date: 04 June 2019