Receiving MIM errors trying to move a CA Datacom database file. Messages MIM1038, MIM1039, and MIM1040 received.

Products

• Datacom
• DATACOM - AD
• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• CA ECOMETER SERVER COMPONENT FOC
• Easytrieve Report Generator for Common Services
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA ON DEMAND PORTAL
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware

Issue/Introduction

Issue:

When trying to run a job to move a database file for CA Datacom/DB or /CA 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

Cause:

The utilities used to allocate or move the CA Datacom files needs to have exclusive control of the database files, and at the time that the job is submitted, the Multi-User Facility (called MUF) has ownership of the files (if the database has been opened during this MUF execution).

Resolution:

Typically, the first step in a job like this will run the DBUTLTY program with these two functions:

1. ACCESS . . . OFF – to turn off any further access to the database.
2. COMM OPTION=CLOSE,DBID=### – to close the database in the MUF.

These functions normally 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.

As always, please contact CA Technologies support for CA Datacom if you have further questions.

***

Environment

Release:
Component: DB