Troubleshoot object locks in a model

Products

• CA 2E

Issue/Introduction

When users access the CA 2E model, if some objects of the model are locked, users could have issues access the model itself or some objects in the model.

This article gives some tips that administrators could use to figure out which jobs/users lock the objects.

Environment

• CA 2E 8.7 and higher

Cause

There are some unreleased "ghost" hold on some objects.

Resolution

1. Run these commands to identify the jobs that have hold the locks of some objects of the model
   
   DSPRCDLCK FILE(model-lib/YSSNLCKRFP)
DSPRCDLCK FILE(model-lib/YOBJLCKRFP)
   
   
2. If the administrators would like to know more details of the locking jobs, for each job run
   
   DSPJOB JOB(job-number/job-user/job-name) OUTPUT(*PRINT) 
DSPJOBLOG JOB(job-number/job-user/job-name) OUTPUT(*PRINT)
   
   Note: The OUTPUT(*PRINT) is for redirect the outputs to the current joblog so the outputs can be reviewed together. If this option is not present, the output will be seen right away.
   
   
   
3. The administrators could use WRKOBJLCK command to end the jobs that they think should not hold the locks. For example
   WRKOBJLCK OBJ(MYLIB/MYOBJ) OBJTYPE(*FILE)
   then use option 4 to end the job

Additional Information

Work with Object Locks (WRKOBJLCK)