Unresolved LOCK functions when making SEQ=PHYSICAL backups with DBUTLTY for CA 7

Products

• CA 7 Workload Automation

Issue/Introduction

CA 7 is hanging and users are not able to logon.

Environment

Release r12.0 and r12.1

Cause

The AL2DBHOT - CA 7 back up job was cancelled after the LOCK function occurred.  

Resolution

Review of the CA 7 MUF showed that the UNLOCK was not done after the LOCK functions were performed.

Run the UNLOCK step from CAL2JCL(AL2DBHOT).

//UNLOCK   EXEC PGM=DBUTLTY,REGION=4M        
//STEPLIB  DD DISP=SHR,DSN=datacomhlq.CUSLIB 
//                 DD DISP=SHR,DSN=datacomhlq.CAAXLOAD
//SYSPRINT DD SYSOUT=*                                   
//SYSIN    DD *                                          
 UNLOCK OPTION=MOVER,DBID=770,AREA=MIN                   
 UNLOCK OPTION=MOVER,DBID=770,AREA=DFS                   
 UNLOCK OPTION=MOVER,DBID=770,AREA=JOB                   
 UNLOCK OPTION=MOVER,DBID=770,AREA=AWS                   
 UNLOCK OPTION=MOVER,DBID=770,AREA=AWL                   
 UNLOCK OPTION=MOVER,DBID=770,AREA=AWH                   
 UNLOCK OPTION=MOVER,DBID=770,AREA=HIS                   
 UNLOCK OPTION=MOVER,DBID=770,AREA=HIL                   
/*          

NOTE:   If the LOCK was repeatedly performed, for example,  3 times.  Then you will need to run the UNLOCK functions 3 times.