CA-DISK Backups ENQ problem with MIM - MIM1038I and MIM1039I messages

book

Article ID: 195662

calendar_today

Updated On:

Products

CA MIM Resource Sharing (MIM) CA MIM Data Sharing (MII)

Issue/Introduction

We're using CA-Disk to backup datasets, and occasionally get these messages:

Submitted from our MSTRSVW system:

>MIM1038I STGBKP02 JOB12125 A=005D T=7F81A0 contention with MVSZFS A=0081 T=7FED90 OWNS EXCL on SVW
>MIM1039I STGBKP02 JOB12125 A=005D T=7F81A0 needs SHR SYSDSN SHARE.CEM.SVW.INSTALL.OMVS.CONF       

Submitted from our MSTRMIM system:

>MIM1038I STGBKP02 JOB12125 A=005D T=7F81A0 contention with MVSZFS A=006E T=7FED90 OWNS EXCL on MIM
>MIM1039I STGBKP02 JOB12125 A=005D T=7F81A0 needs SHR SYSDSN SHARE.CCS.MIM.INSTANCE.CCSZFSB1       

SVW and MIM in the above are actually the &SMFID symbolic value.

Both datasets are zFS datasets mounted as R/W on the system the job ran on.

The contention clears before we can get a GRS,C but the backup ends up missing datasets.
                                                                                    

MIMEXMPT member contains this:

DEFAULT  RESOURCE=GLOBAL,        /* RESOURCE NAME IS GLOBAL  
         JOB=GLOBAL              /* JOBNAME IS GLOBAL    

LOCAL    QNAME=SYSDSN,RNAME=SHARE.*     

                   

MIMQNAME member contains:

SYSDSN   GDIF=YES,    
         SCOPE=SYSTEM,
         EXEMPT=YES,  
         ECMF=YES,    
         RPTAFTER=30, 
         RPTCYCLE=60  

 

Environment

Release : 12.5

Component : MIM

Resolution

In MIMQNAME the SYSDSN QNAME contains  a typo - SCOPE=SYSTEM is incorrect.

Changing to SCOPE=SYSTEMS corrected the problem.

All other QNAMES were correct.