KB Article #178444

COPILOT is started, the UCONFRUN dataset is exclusively held by COPILOT - file contention

Problem

COPILOT is started, the UCONFRUN dataset is exclusively held by COPILOT


UCONFRUN file contention


When COPILOT is started, the UCONFRUN dataset is exclusively held by COPILOT.
CFTMAIN awaits for the dataset to be freed.
CFTUTIL (listparm) job also waits for UCONFRUN dataset (CFTMAIN is not running).

Messages:

IEF861I FOLLOWING RESERVED DATA SET NAMES UNAVAILABLE TO CFTMAIN
IEF863I DSN = CFAUTO.AXWAY.D322.CFT.UCONFRUN CFTMAIN RC = 04
IEF099I JOB CFTMAIN WAITING FOR DATA SETS



When CFTMAIN is started, the UCONFRUN dataset is exclusively held by CFTMAIN.
COPILOT awaits for the dataset to be freed.


Resolution

Such an issue has been identified being related to the use of at least one z/OS storage management tools.


In the reported problem described above, the issue was caused by IBM Tivoli Allocation Optimizer



The easiest way to disable Tivoli Allocation Optimizer is to add the bypass DDNAME in the JCL (COPRUN and CFTMAIN)

It will bypass Tivoli Allocation Optimizer for all the dataset accessed by the step.

The ddname is AOBYPASS and the format of the DD card is:
//AOBYPASS DD DUMMY