Receiving msg MIM0339E running MVS guest under VM host

Products

MIM Resource Sharing (MIM)

Issue/Introduction

During a Disaster Recovery test, having our z/OS 2.3 running under a VM host system, we are receiving messages:

*19.17.10 SYC MIM *MIM0339E System SYB detected inconsistent TOSYSTEM
* for VCFPATH C442 on system SYC
*19.17.10 SYC MIM *MIM0339E System SYB detected inconsistent TOSYSTEM
* for VCFPATH D44A on system SYC
*19.17.10 SYC MIM *MIM0339E System SYB detected inconsistent TOSYSTEM
* for VCFPATH C44A on system SYC
*19.17.10 SYC MIM *MIM0339E System SYB detected inconsistent TOSYSTEM
* for VCFPATH D442 on system SYC

and also from other systems as well.

These paths are NOT defined in our MIMINIT and our IOGEN matches the MIMINIT statements.
This problem ONLY happens when we run as a z/OS guest under a VM host.
When running native z/OS with same gen and MIMINIT parms we do not have the problem.
Is it possible that VM is somehow messing up the addressing?
Here is our MIMINIT..

DEFSYS (SYB,SB,SYB,INITIAL=FREED), /* PRODUCTION SYSTEM
(SYC,SC,SYC,INITIAL=FREED), /* PRODUCTION SYSTEM
(SYD,SD,SYD,INITIAL=FREED), /* PRODUCTION SYSTEM
(SYF,SF,SYF,INITIAL=FREED), /* PRODUCTION SYSTEM
(SYG,SG,SYG,INITIAL=FREED), /* PRODUCTION SYSTEM
(SYK,SK,SYK,INITIAL=FREED), /* TEST SYSTEM
(SYM,SM,SYM,INITIAL=FREED) /* TEST SYSTEM

*==============================================================*
* DEFINE ASYMETRICAL (FULLY REDUNDANT) CTC CONFIGURATION:
*==============================================================*

*--------------------------------------------------------------*
* SYB TO SYC
*--------------------------------------------------------------*

CTCPATH FROMSYS=SYB ADDR=(D452,C452,D45A,C45A) TOSYS=SYC
CTCPATH FROMSYS=SYC ADDR=(C412,D412,C41A,D41A) TOSYS=SYB

*--------------------------------------------------------------*
* SYB TO SYD
*--------------------------------------------------------------*

CTCPATH FROMSYS=SYB ADDR=(D442,C442,D44A,C44A) TOSYS=SYD
CTCPATH FROMSYS=SYD ADDR=(C412,D412,C41A,D41A) TOSYS=SYB

*--------------------------------------------------------------*
* SYB TO SYG
*--------------------------------------------------------------*

CTCPATH FROMSYS=SYB ADDR=(D422,C422,D42A,C42A) TOSYS=SYG
CTCPATH FROMSYS=SYG ADDR=(C412,D412,C41A,D41A) TOSYS=SYB

*--------------------------------------------------------------*
* SYB TO SYF
*--------------------------------------------------------------*

CTCPATH FROMSYS=SYB ADDR=(D432,C432,D43A,C43A) TOSYS=SYF
CTCPATH FROMSYS=SYF ADDR=(C412,D412,C41A,D41A) TOSYS=SYB

*--------------------------------------------------------------*
* SYB TO SYK
*--------------------------------------------------------------*

CTCPATH FROMSYS=SYB ADDR=(C462,D462,C46A,D46A) TOSYS=SYK
CTCPATH FROMSYS=SYK ADDR=(C412,D412,C41A,D41A) TOSYS=SYB

*--------------------------------------------------------------*
* SYB TO SYM
*--------------------------------------------------------------*

CTCPATH FROMSYS=SYB ADDR=(D472,C472,D47A,C47A) TOSYS=SYM
CTCPATH FROMSYS=SYM ADDR=(C412,D412,C41A,D41A) TOSYS=SYB

*--------------------------------------------------------------*
* SYC TO SYD
*--------------------------------------------------------------*
CTCPATH FROMSYS=SYC ADDR=(D442,C442,D44A,C44A) TOSYS=SYD
CTCPATH FROMSYS=SYD ADDR=(C452,D452,C45A,D45A) TOSYS=SYC

*--------------------------------------------------------------*
* SYC TO SYG
*--------------------------------------------------------------*

CTCPATH FROMSYS=SYC ADDR=(D422,C422,D42A,C42A) TOSYS=SYG
CTCPATH FROMSYS=SYG ADDR=(C452,D452,C45A,D45A) TOSYS=SYC

*--------------------------------------------------------------*
* SYC TO SYF
*--------------------------------------------------------------*

CTCPATH FROMSYS=SYC ADDR=(D432,C432,D43A,C43A) TOSYS=SYF
CTCPATH FROMSYS=SYF ADDR=(C452,D452,C45A,D45A) TOSYS=SYC

*--------------------------------------------------------------*

* SYC TO SYK
*--------------------------------------------------------------*

CTCPATH FROMSYS=SYC ADDR=(D462,C462,D46A,C46A) TOSYS=SYK
CTCPATH FROMSYS=SYK ADDR=(C452,D452,C45A,D45A) TOSYS=SYC

*--------------------------------------------------------------*
* SYC TO SYM
*--------------------------------------------------------------*

CTCPATH FROMSYS=SYC ADDR=(D472,C472,D47A,C47A) TOSYS=SYM
CTCPATH FROMSYS=SYM ADDR=(C452,D452,C45A,D45A) TOSYS=SYC

*--------------------------------------------------------------*
* SYD TO SYG
*--------------------------------------------------------------*

CTCPATH FROMSYS=SYD ADDR=(D42A,C42A,D422,C422) TOSYS=SYG
CTCPATH FROMSYS=SYG ADDR=(C442,D442,C44A,D44A) TOSYS=SYD

Environment

Release : 12.5

Component : MIM

Cause

Resolution

There are three components to Virtual CTC's on an MVS guest where MIM is running.

The MIM CTCPATH definitions
The MVS gen
The VM couple statements

If you have verified that you are using the same MIMINIT CTCPATH statements and the same MVS gen, the next place to check is the VM piece.

On the systems where we have MVS guests running under VM, we have VM COUPLE statements in the PROFILE EXEC which is part of the configuration. They look like this:

'CP COUPLE D20 TO ZM1G D48'
'CP COUPLE D40 TO ZM1G D28'
'CP COUPLE D21 TO ZM2G D48'
'CP COUPLE D41 TO ZM2G D28'
'CP COUPLE D22 TO ZM3G D48'
'CP COUPLE D42 TO ZM3G D28'
'CP COUPLE D23 TO ZM4G D48'
'CP COUPLE D43 TO ZM4G D28'
'CP COUPLE D24 TO ZM5G D48'
'CP COUPLE D44 TO ZM5G D28'

Please verify that the definitions on VM match those on MVS.

IMPORTANT

None of this relates to installing or configuring MIM on VM, which would not help.
This is purely to facilitate access to the correct CTC paths from MIM through MVS and VM to the hardware.

Additional Information

z/VM 7.2 CP Commands and Utilities Reference Guide describes the COUPLE command on page 82

Diagnosis of one of the error messages

The errors indicate mismatched devices.

If we look at one of the errors received

*19.17.10 SYC MIM      *MIM0339E System SYB detected inconsistent TOSYSTEM
* for VCFPATH C442 on system SYC

MIM on SYB was already up. MIM on SYC was started and part of VCF startup is initial handshaking where the two systems compare definitions. System SYB returned the handshake indicating there is an error. Specifically, SYC's VCFPATH C442 has an inconsistent TOSYSTEM parameter.

Looking at the CTCPATH statements for SYC in the MIMINIT member:

CTCPATH FROMSYS=SYC ADDR=(D442,C442,D44A,C44A) TOSYS=SYD

SYC has a VCFPATH definition for CTC address C442 and it is supposed to connect to SYD.

The MIM0339E message description states

If parm=TOSYSTEM, then MIM detected an incorrect TOSYSTEM value on the CTCPATH statement identified by FROMSYSTEM SYC and the ADDRESS C442. The path at that address physically connects SYC with SYB, but the TOSYSTEM parameter indicates a connection to some other system (SYD. This message can also be issued if different DEFSYS statements are specified on systems SYB and SYC.

Possible reasons for this problem:

1. MIMINIT is NOT shared and the CTCPATH statements are different on SYB and SYC.
2. MIMINIT is NOT shared and the DEFSYS statement is different on SYB and SYC.
3. The CTC address physically (or in this case virtually) doesn't connect to the system in the definitions but does connect to another system running MIM.

Given that these exact same definitions work when running regular DR and have only cropped up when running as a guest under VM, items 1 and 2 are already ruled out, which leaves option 3. Since these are virtual CTC's, that points to VM as the problem. The problem has to do with aligning the CTC definitions on VM with what is defined in the MVS MIMINIT. It does not in any way relate to installing or running MIM on the VM system.