Database Management Solutions Post Install Compare ssid0000 job fails with SC03 abend in COMPRT step and Bad length keyword TS_CLOSE_RULE

Products

• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• Database Management for DB2 for z/OS - Administration Suite
• Database Management for DB2 for z/OS - Performance Suite
• Database Management for DB2 for z/OS - Recovery Suite
• Database Management for DB2 for z/OS - Utilities Suite
• Database Management for DB2 for z/OS - SQL Performance Suite

Issue/Introduction

Executing Database Management Solutions r20 Post Install Compare ssid0000 job.

The COMPRT step abends with the following:

SYSTEM COMPLETION CODE=C03  
 PSW AT TIME OF ERROR  070C0000   86334EBA  ILC 2  INTC 0D   
   NO ACTIVE MODULE FOUND                                    
   NAME=UNKNOWN                                              
   DATA AT PSW  06334EB4 - 80C03000  0A0D58C0  549C9180      
   GR 0: 00000000   1: 80C03000                              
      2: 86334EA0   3: 009BB9B8                              
      4: 0099CE88   5: 7F2EE110                              
      6: 06334C06   7: 00FC24A0                              
      8: 06335CC0   9: 7F597530                              
      A: 7F597530   B: 00FD6CF0                              
      C: 009BB9B8   D: 009BBA24                              
      E: 00DA6278   F: 00000004                              

The following error message is also returned:

RCM00050: Bad length for keyword value in the following parm record:
          TS_CLOSE_RULE            APPLY

Cause

The following new options have been added to the Create JCL for DB2 Object Comparison panel by PTF LU14065: 

UNIT Disk.................> SYSDA              (UNIT)             
UNIT Tape.................> CART               (UNIT)             
Object size threshold.....> 1000000            (number of pages)  

If using a MOD2 terminal emulation the following options appear on the next panel where there is a requirement to scroll down to see these options:

Apply all TS/IX changes to existing objects?..................> N   (Y,N)  
Use the same values for all DB2 Subsystems being processed?...> N   (Y,N)



The first generation of Compare ssid0000 JCL will be correct but any subsequent ssid0000 JCL generated for other Db2 environments will be
missing parameter options within the COMPRT step APRMFILE DD as follows if PF8 is not depressed to scroll down to the above options
on the Create JCL for DB2 Object Comparison panel: 

TRGSSID ssid                        INSTALL SUBSYSTEM                        
BPRULE  Y                             ALWAYS APPLY BP CHANGE TO UTIL OBJS      
TS_MAXPART_RULE  Y        APPLY MAXPARTITIONS FOR TABLESPACE       
TS_TYPE_RULE  Y               APPLY TYPE FOR TABLESPACE                
TS_SEGSIZE_RULE  Y        APPLY SEGSIZE FOR TABLESPACE             
TS_DSSIZE_RULE  Y          APPLY DSSIZE FOR TABLESPACE              
T_PART_RULE  Y                APPLY PART FOR TABLE                     
TS_CLOSE_RULE               APPLY CLOSE FOR TABLESPACE                
TS_COMPRESS_RULE       APPLY COMPRESS FOR TABLESPACE             
TS_PRIQTY_RULE            APPLY PRIQTY FOR TABELSPACE               
TS_SECQTY_RULE           APPLY SECQTY FOR TABELSPACE               
IX_CLOSE_RULE              APPLY CLOSE FOR INDEX                     
IX_PRIQTY_RULE             APPLY PRIQTY FOR INDEX                    
IX_SECQTY_RULE           APPLY SECQTY FOR INDEX

Resolution

If using a MOD2 terminal emulation, note the More:     + option on the Create JCL for DB2 Object Comparison panel and make certain to scroll down (PF8)
each time to view the following options prior to depressing ENTER when generating the Compare ssid0000 JCL:

Apply all TS/IX changes to existing objects?..................> N   (Y,N)  
Use the same values for all DB2 Subsystems being processed?...> N   (Y,N)

Additional Information

Additional circumventions:
1. Use a larger screen emulation such as a MOD4
2. Exit and enter INSMAIN each time to generate the Compare ssid0000 JCL

This problem is resolved by published PTF: LU15378