PM54662: CLI0102E FOR .NET APPLICATIONS THAT CALL A DB2 Z/OS STORED PROCEDURE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2DDF DB2DRDA DB2SP DM1626 defect pm54662 dpm54662
  Remote .NET applications that call a Stored Procedure on a
  DB2 10 for z/OS server may fail with error CLI0102E (Invalid
  conversion). The conversion between the application data type
  and SQL data type is not supported by the remote driver.
  **********************************************************
  Additional Symptoms and Keywords:
    CLI0102E MSGCLI0102E
    DDFCOMPAT
  

Local fix

• The problem can be circumvented by changing the application to
  use an application data type that is supported by the driver.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Distributed Data Facility (DDF) users    *
  *                 using .NET applications to call a stored     *
  *                 procedure on DB2 10 for z/OS.                *
  ****************************************************************
  * PROBLEM DESCRIPTION: After a DB2 for z/OS database server    *
  *                      is migrated to Version 10, a .NET       *
  *                      application using the IBM Data Server   *
  *                      driver calls a stored procedure on the  *
  *                      migrated server.  The CALL fails with   *
  *                      the CLI error message CLI0102E,         *
  *                      indicating the conversion between the   *
  *                      parameter type in the stored procedure  *
  *                      declaration and the argument type       *
  *                      specified in the application's CALL     *
  *                      statement is not supported by the       *
  *                      driver.  The .NET application did not   *
  *                      encounter this error before the DB2     *
  *                      server was migrated to V10.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  DB2 10 for z/OS implemented enhancements to the way in which
  stored procedure parameters are returned to the calling
  application at the remote requester.
  - Before Version 10, DB2 returned stored procedure parameters
    according to the type of the corresponding arguments in
    the stored procedure CALL.
  - Beginning in Version 10, DB2 returns stored procedure
    parameters according to the SQL type of the parameter as
    defined in the stored procedure declaration.
  This change improves performance for the call by eliminating
  server conversions of the parameter data; implements the same
  behavior as used by DB2 for returning other outputs, such as
  cursor or singleton select data; and is the same behavior as is
  implemented on other servers in the DB2 Family.
  .
  However, .NET has strong-typing semantics and this change in
  DB2 server behavior may cause some .NET applications to fail
  with the CLI error message CLI0102E, if they do not specify
  argument types that are compatible with the declared type of
  the corresponding parameter in the stored procedure.  The
  required corrective action is to change the .NET application so
  that it satisfies .NET semantics for strong-typing and, thus,
  conforms to good .NET programming practices.
  

Problem conclusion

• Although changing problematic application CALL statements to
  conform to good .NET programming practices, as described
  above, is the optimal corrective action before migrating or
  upon migrating to DB2 Version 10, another alternative action
  is to use new support added in this PTF to allow migration to
  V10 to complete without first making all application changes.
  .
  This APAR adds an online-changeable subsystem parameter in
  DSN6FAC called DDF_COMPATIBILITY that can be used to specify
  whether DDF returns stored procedure parameters according to
  their declared types (V10 behavior) or according to the types
  of the arguments specified in the CALL statement (pre-V10
  behavior) when a non-Java application is using an IBM Data
  server driver at Version 9.* and below.
  Refer to the PTF COVERLETTER for details.
  

Temporary fix

Comments

APAR Information

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

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

  UK76806

Modules/Macros

• DSN@XAZP DSNDQWPZ DSNLXXSS DSNLZD00 DSNLZS02
  DSNLZVDA DSNTIDXA DSNTIDXB DSNTIJUZ DSNTINST DSNTXAZP DSNWZIFA
  DSN6FAC
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UK76806

     UP12/03/20 P F203

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.