MIM0355W during IPL with DASDONLY

Products

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

Issue/Introduction

Received MIM0355W during IPL.

MIM0355W Initialization cannot continue until an eligible MASTER becomes available.

Why does MIM issue the message when MIM is runnning with no VCF master by MIMINIT COMMUNICATION=DASDONLY?
 

Environment

Release:
Component: MIM

Resolution

The MIM0355 can be safely ignored - it had no impact on the synchronization of MIM. The message is related to the fact that MIM automatically builds XCF paths in a sysplex even if COMM=DASDONLY. There are timers that are used to determine master eligibility - the message is probably timing related.