I am installing a new release of CA Mainframe Application Tuner (CA MAT). I am getting "DSNT408I SQLCODE = -204, ERROR: BURMAT.SYSIBM.SYSTABLES" in TUNESQLT job.
The JES2 output is in the held output queue job name like BUR2*
10.54.05 JOB51166 ---- FRIDAY, 05 MAY 2017 ----
10.54.05 JOB51166 $HASP373 BUR2SQLJ STARTED - WLM INIT - SRVCLASS BATPRDLO - SYS GS1E
10.54.05 JOB51166 ACF9CCCD USERID BURMAT IS ASSIGNED TO THIS JOB - BUR2SQLJ
10.54.05 JOB51166 IEF196I ACF9CCCD USERID BURMAT IS ASSIGNED TO THIS JOB - BUR2SQLJ
10.54.05 JOB51166 IEFUJI00 LOGONID: BURMAT SOURCE: TN070001 NAME: BURMAN,TOM
10.54.05 JOB51166 IEF196I IEFUJI00 LOGONID: BURMAT SOURCE: TN070001 NAME: BURMAN,TOM
10.54.05 JOB51166 IEF403I BUR2SQLJ - STARTED - TIME=10.54.05
10.54.05 JOB51166 TE0108I TUNSSP=TUNSSP00 DB2=DB2P PLAN=MATB0DB2 PACKAGE=MATB0 PROCESS=INIT
10.54.05 JOB51166 TE0103I CALL ATTACH successful Return Code 00000000 Type=CONNECT DB2=DB2P Release=10.10
10.54.05 JOB51166 TE0103I CALL ATTACH successful Return Code 00000000 Type=OPEN DB2=DB2P Release=10.10
10.54.05 JOB51166 TE0101E CA MAT Installation Service (ESQL)
10.54.05 JOB51166 DSNT408I SQLCODE = -204, ERROR: BURMAT.SYSIBM.SYSTABLES IS AN UNDEFINED NAME
10.54.05 JOB51166 DSNT418I SQLSTATE = 42704 SQLSTATE RETURN CODE
10.54.05 JOB51166 DSNT415I SQLERRP = DSNXEDST SQL PROCEDURE DETECTING ERROR
10.54.05 JOB51166 DSNT416I SQLERRD = 50 0 0 -1 0 0 SQL DIAGNOSTIC INFORMATION
10.54.05 JOB51166 DSNT416I SQLERRD = X'00000032' X'00000000' X'00000000' X'FFFFFFFF'
10.54.05 JOB51166 X'00000000' X'00000000' SQL DIAGNOSTIC INFORMATION
10.54.05 JOB51166 TE0103I CALL ATTACH successful Return Code 00000000 Type=CLOSE DB2=DB2P Release=10.10
10.54.05 JOB51166 TE0103I CALL ATTACH successful Return Code 00000000 Type=DISCONNECT DB2=DB2P Release=10.10
Panel input for DB2 Release:
CA MAT -------------------- CREATE DB2 DEFINITIONS ------------ TUNSSP00 SAVED
This step specifies DB2 subsystem information that will be used during
the generation of JCL for BINDing the CA MAT Plan and Package.
DB2 Subsystem Information:
Target DB2 ssid ===> DB2P (for example, DSN)
DB2 Release ===> 10.1 (for example, 8.1)
DSNLOAD DSNAME ===> PDB2P.SDSNLOAD
DSN Exit Lib ===> PDB2P.SDSNEXIT
OWNERID of Plan ===> BURMAT
Press ENTER to continue, HELP for more information, or END to exit step.
These are the finding from our L2:
I ran the bind job against a shared subsystem and got the same messages as you received.
I then ran the TUNESQLJ job against a different subsystem on a different LPAR which was part of the data sharing group. The job ended without any problems.
I then moved the SYSIBM.SYSTABLES table out of shared DASD and ran the job again. This time I got exactly the same error as you did, my authid prefixed the table name in the message.
I spoke with one of our field engineers who informed me that most of our customers are running the TUNESQLJ job against subsystems in data sharing groups without any issues.
This leads me to believe that there may be a setup problem with your DB2 susbsystem.
Is this subsystem a member of a data sharing group? And if so, could there be a problem with the data sharing group configuration?