HDDL line command for a table encounters OFS0001E SQL-206 error for A0.PARSETREE.

Document ID : KB000049215
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

HDDL line command within RC/Query for DB2 for z/OS against a table returns the following:

OFS0001E - defaultPackageProcess Error in Preparing the Cursor

OFS0001E - logSQL -SELECT A0.NAME, A0.CREATOR, A0.TBNAME, -
OFS0001E - logSQL -A0.TBCREATOR, A0.UNIQUERULE, A0.COLCOUNT, -
OFS0001E - logSQL -A0.CLUSTERING, A0.CLUSTERED, A0.DBID, A0.OBID, -
OFS0001E - logSQL -A0.ISOBID, STRIP(A0.DBNAME,TRAILING) AS DBNAME, -
OFS0001E - logSQL -STRIP(A0.INDEXSPACE,TRAILING) AS INDEXSPACE, -
OFS0001E - logSQL -A0.FIRSTKEYCARD, A0.FULLKEYCARD, A0.NLEAF, -
OFS0001E - logSQL -A0.NLEVELS, A0.BPOOL, A0.PGSIZE, A0.ERASERULE, -
OFS0001E - logSQL -A0.DSETPASS, A0.CLOSERULE, A0.SPACE, A0.IBMREQD, -
OFS0001E - logSQL -A0.CLUSTERRATIO, A0.CREATEDBY, A0.IOFACTOR, -
OFS0001E - logSQL -A0.PREFETCHFACTOR, A0.STATSTIME, A0.INDEXTYPE, -
OFS0001E - logSQL -A0.FIRSTKEYCARDF, A0.FULLKEYCARDF, A0.CREATEDTS, -
OFS0001E - logSQL -A0.ALTEREDTS, A0.PIECESIZE, A0.COPY, -
OFS0001E - logSQL -A0.COPYLRSN, A0.CLUSTERRATIOF, A0.SPACEF, -
OFS0001E - logSQL -A0.REMARKS, A0.PADDED, A0.VERSION, -
OFS0001E - logSQL -A0.OLDEST_VERSION, A0.CURRENT_VERSION, -
OFS0001E - logSQL -A0.RELCREATED, A0.AVGKEYLEN, A0.KEYTARGET_COUNT, -
OFS0001E - logSQL -A0.UNIQUE_COUNT, A0.IX_EXTENSION_TYPE, -
OFS0001E - logSQL -A0.COMPRESS, A0.OWNER, A0.OWNERTYPE, -
OFS0001E - logSQL -A0.DATAREPEATFACTORF, A0.ENVID, A0.ROWID, -
OFS0001E - logSQL -A0.HASH, A0.SPARSE, A0.PARSETREE, A0.RTSECTION -
OFS0001E - logSQL -FROM SYSIBM.SYSINDEXES A0 WHERE A0.TBCREATOR = ? -
OFS0001E - logSQL -AND A0.TBNAME = ? -

OFS0001E - logSQLErrorMessage SQLCODE = -206
OFS0001E - logSQLErrorMessage ERROR = A0.PARSETREE

OFS0001E - logSQLErrorMessage SQLERRP = DSNXORSO
OFS0001E - logSQLErrorMessage SQLERRD = -600 0 0 -1 0 0
OFS0001E - ExtractPrimaryKeysNoMTF ProcessOPATH failed

Solution:

The incorrect SSIDMODE setting was specified in the SETUPxx member in highlvl.CDBAPARM for the respective DB2 subsystem.
SSIDMODE (CM ) was specified without the correct conversion mode DB2 version following an upgrade to DB2 10.

In a DB2 10 CM9 environment the SETUPxx member should have the following specifications:
SSIDVER (V10)
SSIDMODE (CM9)

In a DB2 10 CM8 environment the SETUPxx member should have the following specifications:
SSIDVER (V10)
SSIDMODE (CM8)

In a DB2 10 NFM environment the SETUPxx member should have the following specifications:
SSIDVER (V10)
SSIDMODE (NFM)