For some DB2 environments there is a requirement that a SET CURRENT SQLID control statement is included. Some jobs in TUNESQLI when modified to include the SET command do not seem to accept it and return the TE0114E error code.
For some DB2 environments, there is a need in the supplied TUNESQLJ job for a SET CURRENT SQLID control statement.
The documentation is TUNESQLJ lists the members used in the job and when the members are modified to include the SET command, the CA MAT utility does not seem to accept this and issues the following messages:
IEF403I TUNESQLJ - STARTED TE0108I TUNSSP=TUNSSP00 DB2=DRB1 PLAN=TRI42DB2 PACKAGE=TRI42 PROCESS=INIT TE0103I CALL ATTACH successful Return Code 00000000 Type=CONNECT DB2=DRB1 TE0103I CALL ATTACH successful Return Code 00000000 Type=OPEN DB2=DRB1 TE0113I Executing GRANT on TRI42DB2 TE0111I Operation successful. TE0109I Reading from TUNSAMP. Member=TRITUNDB TE0114E Expecting CREATE found SET <<<<<< ERROR<<<<<< TE0109I Reading from TUNSAMP. Member=TRITUNTS TE0110I Executing CREATE TABLESPACE TRITUNTS TE0101E TriTune Installation Service (ESQL) DSNT408I SQLCODE = -104, ERROR: ILLEGAL SYMBOL "STOGROUP". SOME SYMBOLS THAT
The utility does not accept the SET parameter. As a workaround one would need to take all the supplied PARMLIB members and built a standalone job that directly executes the DB2 utility to perform the same functions. This is cumbersome, and there should be a more direct way of doing this.
SOLUTION - Please check if RO46777 (TUNESQLI DOES NOT ACCEPT 'SET' STATEMENTS TE0114E) has been applied to the version of CA MAT 8.5 that is receiving the error.
If applied, or you do apply RO46777 and the error is still occurring, please send in the following documentation: