MIM/MIA DR startup concerns

Products

• MIM Tape Sharing (MIA)

Issue/Introduction

We are planning to bring up MIA on a Disaster Recovery (DR) Lpar with the Same Tape Drives Device ranges(7300-737F) using Flash Copy Volumes that are used in Production Site with 3 Lpars in MIAPlex.

Will this cause any issues with MIA Startup on the DR Lpar?

Production environment consists of LPAR1, LPAR2, and LPAR3.

Production environment will be "flashed".

DR environment will only bring up LPAR1.

Environment

Release : 12.5

MIM - Multi-Image Resource Manager

Resolution

It may be necessary to enter the FREE command when LPAR1 is started if you find it waiting on LPAR2 and LPAR3 to become active. The FREE command can be issued only for a system(s) that is considered possibly inoperative. Systems considered possibly inoperative are those indicated in messages MIM0061W, MIM0062W, or MIM0350W.

Potential messages:

MIM0061W SYSTEM sysid IN FILE type - POSSIBLY INOPERATIVE
         SYSTEM sysid IN FILE type - INOPERATIVE AT STARTUP
         SYSTEM sysid IN FILE type - INOPERATIVE DUE TO SHUTDOWN
MIM0062W SYSTEM sysid in FILE type - CRITICALLY non-responsive ##########
MIM0350W SYSTEM sysid has not responded to {CTC|XCF} communication

As a result you would issue the FREE command for those systems identified on message.

.FREE sysid | (sysid1,sysid2,...)

Where sysid can be the system name, alias, or index number of the system that you are freeing.

The FREE command is documented here.

The alternatives to issuing the FREE command are:

• to be sure you start with FORMAT=BOTH and code INITIAL=FREED on the DEFSYS
• allocate a brand new control file in DR.

Issuing the FREE command is probably the easiest if someone is watching the startup of LPAR1.

If any of the above is neglected and the MIM0061W, MIM0062W, or MIM0350W messages are not addressed, MIA will not synchronize and essentially not process the MIMSYNCH member.