Troubleshooting
Problem
When running a Log Analysis Tool job in DB2 V11 CM, the following error can occur: DSNT408I SQLCODE = -302, ERROR: THE VALUE OF INPUT VARIABLE OR PARAMETER NUMBER 3 IS INVALID OR TOO LARGE FOR THE TARGET COLUMN OR THE TARGET VALUE DSNT418I SQLSTATE = 22001 SQLSTATE RETURN CODE DSNT415I SQLERRP = DSNXRIHB SQL PROCEDURE DETECTING ERROR DSNT416I SQLERRD = -275 0 0 10 0 0 SQL DIAGNOSTIC INFORMATION DSNT416I SQLERRD = X'FFFFFEED' X'00000000' X'00000000' X'0000000A' X'00000000' X'00000000' SQL DIAGNOSTIC INFORMATION SQLIND=084 1
Cause
First, check if APAR PI41594 (v3.4 PTF UI30291 or v3.5 PTF UI30292; see link below) is applied, or the workaround described in that APAR is implemented. If this does not resolve the issue, please continue to review the following possible cause and resolution:
Log Analysis works by reading the log data that DB2 generates for updates, deletes, and inserts. This log data must be formatted in order to be useful in reports, SQL creation, and LOADFILES. In order to do this, Log Analysis needs to know information about the DB2 subsystem that it is reporting on. Log Analysis reads the DSNHDECP to determine the DB2 version, the DB2 mode (NFM, CM), the specified DB2 string delimiter and decimal seperator, the date format, and the encoding format (CCSID). Without this information, Log Analysis cannot properly format the log data.
If the wrong DSNHDECP module is found first in the steplib concatenation of the job, Log Analysis Tool might use incorrect information about the DB2 subsystem and an error might result. In the above example, the -302 occurred because a DB2 V11 NFM DSNHDECP was placed first in the steplib concatenation, when in fact the DB2 subsystem was running in Compatibility Mode.
Resolving The Problem
Log Analysis Tool follows the order of the DB2 loadlibs that are specified on the 'Update DB2 parameters for DB2 Subsystem' panel (accessed via the LAT Main Menu, option 11, 'Setup') for each subsystem:
DB2 libraries:
*Loadlib1
*Loadlib2
*Loadlib3
*Loadlib4
*Loadlib5
The list of libraries here will be the ones that Log Analysis Tool will search in order (1-5) to find module DSNHDECP. The first DSNHDECP module found will need to have the correct DB2 version/mode for this subsystem.
Ensure that the DB2 loadlib that contains the correct DSNHDECP module for the DB2 subsystem is listed first.
Related Information
Was this topic helpful?
Document Information
Modified date:
12 February 2021
UID
swg21988057