Starting Your Product › Configure Your Product › How to Configure Without CA CSM › Allocate Control Files

Allocate Control Files

CA MIM address spaces can communicate with one another through any one of several cross-system communication methods. A shared DASD file or a shared coupling facility structure can be used as a physical control file. Alternatively, CA MIM private storage can be used as a virtual control file (VCF) buffer and be passed between systems using natively allocated CA MIM CTC devices or XCF services.

Most sites use the simplest CA MIM cross-system communication method—a shared DASD control file—when installing CA MIM for the first time. This step describes that approach.

1. To allocate two CA MIM control files, customize and submit the job found in the CAI.CBTDJCL(ALLOCCF) member.
2. To ensure that the new control files are allocated to the CA MIM address spaces during startup, add two CA MIM ALLOCATE commands to the CAI.CBTDPARM(MIMINIT) parmlib member.

Important: CA MIM does not support control files on the high portion of the Extended Address Volume (EAV). If you use EAV, make sure you allocate data sets with EATTR=NO.

Note: For more information, see the comments in the CAI.CBTDJCL(ALLOCCF) member. For more information about other CA MIM control files and other cross-system communication methods, see the CA MIM Programming Guide.