Planning Initial Settings › Files Used During Operations

Files Used During Operations

CA MIM uses the following files to establish options, parameters, and other initialization and operation information:

AUTHUSER MIM A (DDNAME=AUTHUSER)

This optional file contains information pertaining to users and their assigned authorization classes. For more information, see Assigning Command Authorization to Users.

CLASS MIM A (DDNAME=MIMCLASS)

This optional file contains definitions for user-defined tape drive classes. For more information, see the CA MIA Tape Sharing for z/VM Programming Guide.

CMNDS MIM A (DDNAME=MIMCMNDS)

This optional file contains commands that are issued during the initialization process. For more information, see Format for CMNDS MIM File.

DDNAMES MIM A (DDNAME=MIMNAMES)

This file defines the location of DASD control files and checkpoint files. For more information, see the installation step for supplying control file and checkpoint file information in "Overview of Concepts and Installation" in the CA MIM Installation Guide.

CALMP KEYS Z (DDNAME=CALMPKEY)

This file contains your product LMP license key, which CA supplies. The file may contain one or more LMP key statements for one or more CA z/VM products. For more information, see the installation step for entering LMP keys in the CA MIM Installation Guide.

EDIMSGS MIM A (EDIMSGS)

This parameter is a placeholder file. This parameter is required to be present, but does not affect product operation.

ICMMSGS MIM A (ICMMSGS)

This parameter is a placeholder file. This parameter is required to be present, but does not affect product operation.

INIT MIM A (DDNAME=MIMINIT)

This file provides product initialization values. Statements in the INIT MIM file let you define names and aliases for systems in your complex, set values for initialization parameters, and disable commands. For more information, see the specific functions that are described throughout this chapter.

LINKAUTH MIM A (DDNAME=MIMLINKA)

This file is used to establish authority for cross-system CP commands that are executed on your system. You can prevent specific commands from being sent to your system from any external user, and you can limit commands to external users with certain authority levels.

MIAMSGS MIM A (MIAMSGS)

This file contains templates that are used by the Allocation component to construct messages. You can alter the text in this file to change the text that is sent to users when the message is invoked.

MICMSGS MIM A (MICMSGS)

This file contains templates that are used by the Console component to construct messages. You can alter the text in this file to change the text that is sent to users when the message is invoked.

MIIMSGS MIM A (MIIMSGS)

This parameter is a placeholder file. This parameter is required to be present, but does not affect product operation.

MIMMSGS MIM A (MIMMSGS)

This file contains templates that are used by the CA MIM driver to construct messages. You can alter the text in this file to change the text that is sent to users when the message is invoked.

SYNCH MIM A (DDNAME=MIMSYNCH)

This optional file contains CP commands and CA MIM commands issued when CA MIM completes its synchronization process. For more information, see Format for SYNCH MIM File.

TRACE MIM A (DDNAME=MIMTRACE)

(Optional) This file stores information about product activities. This file is created when the trace feature is activated. This file is not supplied on the distribution tape.

UNITS MIM A (DDNAME=MIMUNITS)

This file provides device control information. This file is used to accomplish the following tasks:

• Place certain tape devices under CA MIA control.
• Relate different real addresses on several systems to the same tape device.
• Establish global names for tape devices that are controlled by CA MIA .
• Define tape devices as managed by Autopath for z/VM.

For any of the previously listed files, you can change the default file name to another name by issuing a FILEDEF command before starting CA MIM. Associate the given ddname with a fixed-length 80-character-record CMS file in the FILEDEF command.

Example:

To reference a UNITS MIM file on disk C instead of the default file on disk A, include the following statement in your PROFILE GCS file:

FILEDEF MIMUNITS DISK UNITS MIM C