Startup of a new MIMplex. Having issues with the control file synchronization not completing.

book

Article ID: 145963

calendar_today

Updated On:

Products

MIM Resource Sharing (MIM) MIM Data Sharing (MII) MIM Tape Sharing (MIA) MIM Message Sharing (MIC)

Issue/Introduction

Trying to startup a new MIMplex. Starting the new MIMplex up with only one system and using the command:

S MIMPROC,FORMAT=CF

We never get the synchronization of the control file to complete.

Here are messages from the startup log.

MIM0073I MIMDRCMN reused at 922DE000
MIM0243I - common area at 122DE000
MIM0073I MIMSVCMN reused at 922CA000
MIM0073I [email protected] loaded at 97422000
MIM0145I MIM tracing initialized; T1AREA (7F569000)
MIM0472I 900 blocks formatted on STS.MIM.CF00
MIM0472I 1350 blocks formatted on SYS.MIM.CF01
MIM0225I Control File Status
 Id Volser Status  Format-Action
 00 MIM201 IN-USE  Formatted On Request
 01 MIM202 USABLE  Formatted On Request
MIM0322W No usable CHECKPOINT files allocated
MIM0030I CA MIM Resource Sharing
Copyright (c) 2016 CA.  All rights reserved.
MIM0073I MIMDRCOM loaded at 94AB8000
MIM0073I LXCFMAIN loaded at 80097FD0
MIM0900I system SYS1 joining XCF group MIMPLEX
MIM0073I MIMCTDIE loaded at 92593000
MIM2001I Global Tape Allocation Facility/GTAF
MIM2004 THE FOLLOWING IS THE LIST OF MANAGED DEVICES -
F9FA       F9FB       F9FC       F9FD       F9FE       F9FF
MIM0049I GTAF R12.5 - initialized
MIM2010I Tape Preferencing and Control Facility/TPCF
Copyright (c) 2016 CA.  All rights reserved.
MIM0049I TPCF R12.5 - initialized
MIM0073I MIMDRGLU reused at 00FC3940
MIM8899I Input from INTERNAL: SETOPT EXIT=(MIMINIXT,LOAD=MIMI
MIM0067I Command SETOPTION
MIM0052I SETOPTION MIM processing complete
MIM0067I Command GLOBALVALUE
MIM0362I GLOBALVALUE command processing complete
MIM0020I MIM  R12.5 INC0 ready - system SYS1
MIM0331I system SYS1 VCF initialization  PENDING
MIM0706I System SYS1 attribute altered: Master Eligible
MIM0113I system SYS1 in file 00 synchronization PENDING
MIM8816I Now recording on file SYSOUT CLASS A for MIMLOG
MIM0335I system SYS1 VCF initialization  UNDERWAY
MIM0336I system SYS1 VCF initialization  COMPLETE


We never get synchronization on the control file. Would expect the following messages:

MIM0022I system SYS1 in file 00 synchronization UNDERWAY
MIM0023I system SYS1 in file 00 synchronization COMPLETE


Despite the missing messages, the started task does not fail.

Cause

Single system running with COMMUNICATION method other than NONE

Environment

Release : 12.5

Component : MIM for z/OS

Resolution

When MIM is started, it looks for another MIM system to synchronize unless the COMMUNICATION method is defined as NONE.

In this case, the MIMINIT member had COMMUNICATION=DASDONLY and only one system was defined on the DEFSYS statement.

To resolve, one of two things is necessary:

1) Specify COMMUNICATION=NONE, and start MIM with a control file format. Here CTC Devices or DASD Control Files will not be used

2) Add a dummy system to the MIM DEFSYS statement. A DUMMY system is a NON-EXISTENT system. You can call this system whatever you like. In essence all you are doing is fooling MIM into thinking it has an external system to synchronize with.

DEFSYS (SYS1,S1,SYS1,INITIAL=FREED),
       (DUMMY,XX,DUMMY,INIT=FREED)