Mainframe Application Tuner 11.0 DB2 customizations receiving a "DSNT408I SQLCODE = -874" error

Products

• Mainframe Application Tuner

Issue/Introduction

Got an error message while doing the DB2 customization which is required for migration of MAT from 9.0 to 11.0.

Reading member TRITPT10 from TUNSAMP

Executing CREATE TABLE CAMAT.PLAN_TABLE

DSNT408I SQLCODE = -874, ERROR: THE ENCODING SCHEME SPECIFIED FOR THE TABLE

MUST BE THE SAME AS THE CONTAINING TABLE SPACE OR OTHER PARAMETERS

DSNT418I SQLSTATE = 53091 SQLSTATE RETURN CODE

DSNT415I SQLERRP = DSNXICTB SQL PROCEDURE DETECTING ERROR

DSNT416I SQLERRD = 65 0 0 -1 0 0 SQL DIAGNOSTIC INFORMATION

DSNT416I SQLERRD = X'00000041' X'00000000' X'00000000' X'FFFFFFFF'

X'00000000' X'00000000' SQL DIAGNOSTIC INFORMATION

--------------------------------------------------------------------------------

Reading member TRITST10 from TUNSAMP

Executing CREATE TABLE CAMAT.DSN_STATEMNT_TABLE

DSNT408I SQLCODE = -874, ERROR: THE ENCODING SCHEME SPECIFIED FOR THE TABLE

MUST BE THE SAME AS THE CONTAINING TABLE SPACE OR OTHER PARAMETERS

DSNT418I SQLSTATE = 53091 SQLSTATE RETURN CODE

DSNT415I SQLERRP = DSNXICTB SQL PROCEDURE DETECTING ERROR

DSNT416I SQLERRD = 65 0 0 -1 0 0 SQL DIAGNOSTIC INFORMATION

DSNT416I SQLERRD = X'00000041' X'00000000' X'00000000' X'FFFFFFFF'

X'00000000' X'00000000' SQL DIAGNOSTIC INFORMATION

--------------------------------------------------------------------------------

Reading member TRITFT10 from TUNSAMP

Executing CREATE TABLE CAMAT.DSN_FUNCTION_TABLE

DSNT408I SQLCODE = -874, ERROR: THE ENCODING SCHEME SPECIFIED FOR THE TABLE

MUST BE THE SAME AS THE CONTAINING TABLE SPACE OR OTHER PARAMETERS

DSNT418I SQLSTATE = 53091 SQLSTATE RETURN CODE

DSNT415I SQLERRP = DSNXICTB SQL PROCEDURE DETECTING ERROR

DSNT416I SQLERRD = 65 0 0 -1 0 0 SQL DIAGNOSTIC INFORMATION

DSNT416I SQLERRD = X'00000041' X'00000000' X'00000000' X'FFFFFFFF'

X'00000000' X'00000000' SQL DIAGNOSTIC INFORMATION

Environment

Release:
Component: MATUNE

Resolution

TUNESQLJ runs a program called TUNESQLI which calls another program to do the table creates you are seeing that are failing.  The default table creates are done in EBCDIC.  There is a test in that program that tries to determine what release of DB2 you are running and then sets EBCDIC or UNICODE based on the releases of DB2, in your case you are DB2 V10 and we want to create tables using CCSID of UNICODE. 

The issue here is TRCUST is creating TNBINDJ with EBCDIC.  In step 9 of TRCUST we ask you what release of DB2 you are running, I am assuming you are specifying 10.1?  If that is true then the TNBINDJ job should be being built with ENCODING(UNICODE) and yours is being built with EBCDIC which is where the SQLCODE -874 is coming from.

You can change the TNBINDJ to specify ENCODING(UNICODE), rerun the bind then rerun TUNESQLJ.