BIF/ICI HealthCheck Licensed Freeware for Db2 11, detects static and dynamic SQL and matches to the relevant collection, packages,…
BIF/ICI HealthCheck overview (Built-in Function & Incompatibility Checker for Db2 z/OS)
BIF/ICI HealthCheck reports the following incompatibilities in Db2 11
- Execution of the Db2 9 for z/OS version of SYSIBM.CHAR(DECIMAL-EXPR)
- Execution of the Db2 9 for z/OS version of SYSIBM.VARCHAR(DECIMAL-EXPR), CAST (DECIMAL AS VARCHAR), OR CAST (DECIMAL AS CHAR)
- Use of an unsupported character string representation of a TIMESTAMP
- Use of the Db2 10 for z/OS default SQL path instead of the V11 path, which has more implicit Schemas
- Execution of a non-Java client that called a Stored Procedure (SP) that is on the Db2 for z/OS Data Server, while subsystem parameter DDF_COMPATIBILITY was set to SP_PARMS_NJV (the Data Server returned output argument values whose data types matched the data types of the call statement arguments).
- Execution of an insert statement that inserts into an XML column without the XMLDOCUMENT function, which generates SQLCODE -20345 on a Db2 release prior to V11, but does not generate an error starting in V11
- V10 XPATH evaluation behavior was in effect, which resulted in an error (e.g. a data type conversion error occurred for a predicate that would otherwise be evaluated to false.). Starting in V11, such errors might be suppressed
- Execution of a SQL statement by a client non-Java, or Java application that included an unsupported conversion from a string type to a numeric type, or from a numeric type to a string type while the Db2 z/OS Data Server environment was one of the following (the Data Server issues SQLCODE -301)
o The Data Server was in version 11 New-Function Mode (NFM)
o APPLICATION COMPATIBILITY was set to V10R1
o Implicit casting was disabled because subsystem parameter DDF_COMPATIBILITY was set to SP_PARMS_NJV, or DISABLE_IMPCAST_NJV
ICI incompatibility Report in Db2 10 (Incompatibility Change Indicator)