CA Workload Automation Restart Option for z/OS Schedulers (CA-11) getting a RC 69(071) on DSN table after having upgraded to 11.0

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

CA Workload Automation Restart Option for z/OS Schedulers 3.0 to 11.0 upgrade job AL7ADUP (step 20 of CA Workload Automation Restart Option for z/OS Schedulers 11.0 installation) ran fine, successfully re-defining and re-cataloging CA-11 tables.

But CA-11 STC (CAL7) fails to start due to:

DB00501E - OPEN ERROR - RETURN CODE 69 (071) CXX=cxxname (DSN00601)
U11D-0230-C DATACOM CMD=OPEN TBL=DSN RC=69(071) 

Datacom RC 69(071) means TABLE HAS NO CURRENT INDEX but DSN table had no index problem on 3.0, just before starting the upgrade to 11.0.

Cause:

The problem occurs if AL7DUP migration job has been run AFTER having applied CA Workload Automation Restart Option for z/OS Schedulers 11.0 PTF RO40993. It adds two new keys to DSN table replacing and using the same member (CL7BTG) of CAL7SRC library that is used by upgrade job AL7DUP too.

Resolution:

PTF RO40993 has an HOLD ACTION that requires running a multistep job (T3C6133), the last step of which is an INIT of IXX and a RETIX of the full database:

//SYSIN    DD *                         
 ACCESS STATUS=OFF,DBID=nnn,USERS=WAIT    
 INIT AREA=IXX,DBID=nnn                   
 RETIX DBID=nnn,SORT=9999999999,OPTION1='(I)'
 ACCESS STATUS=WRITE,DBID=nnn     
//

 

AL7ADUP JCL from CAL7SRC library was built when DSN had only one key, like the 3.0 version of the table, so no RETIX was required at that time.

However, if AL7ADUP is executed after RO40993 has been applied, there are two new keys defined on DSN, so the RETIX step from T3C6133 job must be run before starting CAL7.