Advanced Topics › Product Activation Considerations › How You Start CA MIM on a System New to Your Complex
How You Start CA MIM on a System New to Your Complex
The way you start CA MIM on a system new to your complex depends on which of the following communication methods you selected:
- For DASDONLY, start CA MIM on your new system. CA MIM places the ID of the system in its control files and expects that system to join the complex at startup time. However, the system ID is deleted the next time you reformat the control files. If you want the system ID to remain in the complex long-term, then you should use the DEFSYS statement.
- For CTCDASD or CTCONLY, define system IDs and CTC paths for your new system through the DEFSYS and CTCPATH statements. Then, reformat the control files as you start CA MIM.
- For XCF, define system IDs for your new system using the DEFSYS statement. Then, reformat the control files as you start CA MIM.
Important! Each CTC device used by CA MIM must have an operational path and must be ONLINE before CA MIM attempts to allocate the CTC device. If either of these conditions is not met, the appropriate error message (MIM0464E or MIM0446E) is issued and CTC device allocation is bypassed. The CTC address becomes available to CA MIM after a VARY ONLINE.
More information:
How CA MIM Formats Control and Checkpoint Files
