How to modify CA Db2 for z/OS suite indexes on System Catalog to be STORTYPE = I for Implicit?
Article ID: 192283
RC Compare for DB2 for z/OSDatabase Management for DB2 for z/OS - Administration SuiteRC/Extract for DB2 for z/OSRC/Migrator for DB2 for z/OSRC/Merger for DB2 for z/OSRC/Query for DB2 for z/OSRC/Secure for DB2 for z/OSRC/Update for DB2 for z/OS
Have some CA Db2 for z/OS tool indexes defined on User Managed Spaces (STORTYPE = 'E' ).
Attempted to move one of them into DB2 managed space by dropping and recreating it (Index=CAIXP1 on table=SYSPLAN).
During recreation removed (USING VCAT 00000001) and replaced (USING STOGROUP DTSSMS, PRIQTY 2880, SECQTY 720) but it was created again with STORTYPE = 'E' and USING VCAT 00000001.
Have the following list of CA Db2 tool indexes on user defined spaces (STORTYPE = 'E'). Please advise how to move these indexes to Db2 for z/OS managed storage.
Site has created some optional Db2 catalog indexes to improve SQL performance within the CA Db2 tools for z/OS. In the example you provided, creating index DTS.CAIXP2 against SYSIBM.SYSPLAN. As these indexes are defined against the actual Db2 catalog you do not have control over the STORTYPE.
Located the following Db2 for z/OS documentation link that should assist: https://www.ibm.com/support/knowledgecenter/SSEPEK_12.0.0/sqlref/src/tpc/db2z_sql_createindex.html
In the above link it mentions: User-defined indexes on catalog tables: If you issue CREATE INDEX for an index on a catalog table, and you specify the USING clause, Db2 ignores that clause. Instead, Db2 defines and manages the index data sets. The data sets are defined in the same SMS environment that is used for the catalog data sets with default space attributes.
This appears to be working as designed within Db2 for z/OS and not a function of the CA Db2 tools for z/OS.