CMOD 10.1 changes to DB2 tables

[hsoares]

When I upgraded CMOD from 8.5 to 9.5, I asked IBM to provide 1 page with the DDL that was going to be executed by arsdb because DB2 for z/OS requires more than a simple back-up when a table is being dropped. Now, I'm close to executing the V10.1 arsdb and again I have no idea what it is going to do to Db2. Do you know?
Thank you,
Heloisa

[Justin Derrick]

On the multiplatforms systems, the arsdb utility that upgrades the CMOD database is a compiled binary, so it's not easy to find out what it's doing.  Your best move would be to request that information from IBM again.  Don't hesitate to post that DDL here for other z/OS users to benefit from it. 

-JD.

[Nancy Irgens]

It would be best for you to confirm the expected DDL changes for CMOD V10 with IBM. 

We found ARSDB performed the following Alters during our CMOD V9.5 to CMOD V10.1 upgrade:

  ALTER TABLE ARSSERVR.ARSHOLDMAP                           
                 ADD COLUMN DOC_UUID AFTER RES_ID                     
                                   (CHAR(36)            FOR SBCS DATA 
                 NOT NULL WITH DEFAULT)                               
                                                                       
  ALTER TABLE ARSSERVR.ARSRES                               
                 ADD COLUMN CRYPT_STATUS AFTER EXP_DT                 
                                   (SMALLINT)                         
                 ADD COLUMN HASH_VAL AFTER EXP_DT                     
                                   (CHAR(32)            FOR BIT DATA) 
                                                                       
  ALTER TABLE ARSSERVR.ARSSYS                               
                 ADD COLUMN KEYSTORE_TYPE AFTER <LAST>                 
                                   (VARCHAR(16)         FOR SBCS DATA)
                 ADD COLUMN KEYSTORE_LOCATION AFTER <LAST>             
                                   (VARCHAR(254)        FOR SBCS DATA)
                 ADD COLUMN KEYSTORE_MKL AFTER <LAST>                 
                                   (VARCHAR(128)        FOR SBCS DATA)
                 ADD COLUMN KEYSTORE_MKL_DT AFTER <LAST>               
                                   (TIMESTAMP)                         
                 ADD COLUMN DATA_EKEY AFTER <LAST>                     
                                   (VARCHAR(254)        FOR BIT DATA) 
                                                                       
  ALTER INDEX ARSSERVR.ARSHOLDMAP_IDX                       
                 KEYCOLUMNS (HID ASC, AGID ASC, AID ASC, "NAME" ASC,   
 DOC_OFF ASC, DOC_LEN ASC, COMP_OFF ASC, COMP_LEN ASC, DOC_UUID ASC)   

[hsoares]

Thank you very much. At least now I have an idea of how many tables will be affected and how they'll be affected.