MIM MOVEJOB errors trying to move Datacom database file : MIM1038, MIM1039, and MIM1040 received.
Article ID: 44967
Updated On:
Products
Issue/Introduction
When trying to run a job to move a database file for Datacom/DB or Datacom/AD, you can receive error messages like this:
10.13.24 JOB52302 *@MIM1040I MOVEJOB WAITING FOR RESOURCES
10.13.25 JOB52302 @MIM1038I MOVEJOB contention with MYOWNMUF OWNS SHR on SYSA
10.13.25 JOB52302 @MIM1039I MOVEJOB needs EXCL SYSDSN SYS3.DATACOM.MYOWNMUF.A01143
Resolution
The utilities used to allocate or move the Datacom files must have exclusive control of the database files, and at the time that the job is submitted, the Multi-User Facility (called MUF) has to have ownership of the files (if the database has been opened during this MUF execution).
Typically, the first step in a job like this will run the DBUTLTY program with these two functions:
- ACCESS . . . OFF – to turn off any further access to the database.
- COMM OPTION=CLOSE,DBID=### – to close the database in the MUF.
These functions should free the database for other work to be done against it, but most utilities like IDCAMS or ADRDSSU or FDR do not know if or how these DBUTLTY functions might free the database file.
Therefore, the recommended approach is to put these two functions into a separate job and run that prior to any work to be done. Once this first job ends with CC zero, the files are no longer owned by the MUF, and your other processes can proceed normally.
Feedback
