The DEACTIVATE command terminates operation of a selectable feature on all systems in the CA MIM complex.
Scope: Global
This command has the following format:
DEACTIVATE FEATURE=(featname, [FORCE])
The name of the feature to be deactivated; for a list of the supported features, see the FEATURE parameter on the MIMINIT statement, or issue the DISPLAY FEATURES command to get a list from the active MIMplex.
(Optional) Tells CA MIM to ignore the lack of responses from any inactive or non-existent systems when processing an ACTIVATE command request.
Important! Failure to specify this operand prevents CA MIM from joining the MIMplex on any subsequent CA MIM address space restart until the MIMINIT FEATURE parameter is removed.
Note: For more information including examples, see Advanced Topics in the CA MIM Programming Guide.
The DEFALIAS command lets you define command aliases for CA MIM commands. You can substitute a command alias for the full command specification (including operands) when you want to issue that command.
You can use command aliases for the following purposes:
Use the command name, rather than the alias, when looking up information about the command or when contacting CA Technical Support. Also, because of changes in command format or function, you may need to redefine existing aliases when you upgrade to a new release of CA MIM.
Scope: Local
This command has the following format:
DEFALIAS alias command [operands]
Specifies the one- to eight-character alias that can be substituted for the command.
Specifies the full name of the command that should be executed when this command alias is specified.
(Optional) Specifies the command-specific operands that you want to execute when this command alias is specified.
Usage Notes: DEFALIAS Command
Examples: DEFALIAS Command
DEFALIAS DOPT DISPLAY OPTIONS
The DEFSYS statement lets you define system names and system aliases.
This command has the following format:
DEFSYS (sysname[,alias][,systemid]][,INITIAL={ACTIVE|FREED}])
Specifies the one- to eight-character system name that CA MIM should assign to the system.
Default: If DEFSYS is omitted or a name is not specified, the systemid is used as the system name.
(Optional) Specifies the one- or two-character alias that CA MIM should assign to the system.
Default: The system index number.
Note: System index numbers are discussed under Usage Notes for this statement.
(Optional) Specifies in which state the system starts up. Valid values are:
Specifies that the system starts up and is expected to be active.
Specifies that the system is to start up in the freed state, meaning you will not need to manually issue the FREE command to synchronize without that system.
Important! INITIAL takes effect only when you format the control file.
Specifies the z/VM system identifier for the system represented by this entry. You need not specify a value for systemid if the value for sysname is the same as the z/VM system identifier.
The z/VM system identifier is defined by the SYSID macro in the CP system control file HCPSYS ASSEMBLE or SYSTEM CONFIG in VM/ESA and z/VM.
To display the system identifier of your system, use the CP QUERY USERID command. The z/VM system identifier is also displayed to the right of the running message on many z/VM screens.
Usage Notes: DEFSYS Statement
Examples: DEFSYS Statement
DEFSYS SYS1,SYS2,SYS3
DEFSYS (SYSA,A1) (SYSB,B1)
Note: In the first example, each argument represents a separate system, since no parentheses are used. In the second example, the use of parentheses forces A1 and B1 to become an alias for SYSA and SYSB, respectively.
The DEFSYS command dynamically defines systems to an active MIMplex. This command is only available when using COMPATLEVEL=12.0 or greater.
SCOPE:Global
This command has the following format:
DEFSYS (sysname[[,alias])
Specifies the one-to-eight-character name that CA MIM assigned to the system.
(Optional) Specifies the one-or-two-character alias that CA MIM assigned to the system.
Default: When no alias is specified, CA MIM provides a unique alias.
Note: You can alter system definitions using the ALTERSYS command
The DISABLE statement lets you disable a CA MIM command.
This command has the following format:
DISABLE command
command [facility] operand
Specifies the command that you are disabling.
Disables an operand of the specified command. For example, the command DISABLE DISPLAY GTAF ALL disables the ALL operand on the DISPLAY command for the GTAF facility, but leaves ALL in use as an operand for other CA MIM DISPLAY commands. You do not need to specify facility for unique operands, but it should be used when the same operand is defined for a number of facilities.
Note: When you disable an operand for the SETTRACE command, it is automatically disabled for the SETPRINT, RESETTRACE, and RESETPRINT options.
Usage Notes: DISABLE Statement
Example: DISABLE Statement
To disable the LINK command, specify this statement in the SYNCH MIM file:
MI DISABLE LINK
The DISPLAY MIM command lets you display status and activities information about CA MIM.
This command has the following format:
DISPLAY MIM [{ALL | [COMMANDS]
[CPOOL[,NAME=value][,POOLINFO={YES|NO}]]
[CTCPATH[=RESET]]
[EXIT[=exitid]]
[FACILITIES]
[FEATURES]
[FILES]
[GLOBALVALUE]
[INIT]
[IO[=CF,CHKPT[,RESET]]]
[MODULE[=mask][,CSECT[=mask][,ROUTINES]]
[MSGTABLE]
[OPTIONS]
[OSLEVEL]
[PATH[=RESET]]
[SYSTEMS]}]
[TASK[=mask]]
(Optional) Displays information about commands and command aliases, initialization and operating values, component status, control file activity, and system status.
(Optional) Displays a list of all valid CA MIM commands and command aliases. The display does not show any commands or aliases for commands that have been disabled through the DISABLE command. Also, it shows commands only for active CA MIM facilities. Information about commands is displayed in message MIM0056, and information about command aliases is shown in MIM0053.
Displays information about CA MIM cell pool storage usage. This information is displayed in message MIM0447. Specify one of these values:
Requests information about virtual storage cell pools. Valid values are:
mask--Display any cell pool that matches the name mask provided. You can use the * and # wildcard characters.
The asterisk (*) means that a match occurs for any names containing the characters preceding the asterisk. The pound sign (#) means that a match occurs for the name provided, and names containing any characters located where the # is placed in the name string.
NONZERO--Display those cell pools that currently have cells allocated.
ALL--Display all defined cell pools.
Default: NAME=NONZERO
Requests information about the virtual storage pool areas from which cell pools are allocated. Specify one of these values:
YES-Display information about the virtual storage pool areas.
NO-Omit information about the virtual storage pool areas.
Default: YES
This parameter is currently outdated, but it has been retained for compatibility purposes.
More information:
PATH parameter
(Optional) Displays the exit name, load module name, status, and other information about all active exit routines. However, if you specify a logical name for an exit routine in place of the exitid variable, then CA MIM displays information for only the specified exit routine. If you do not enter a value for exitid, then information is displayed about every routine that has ever been loaded.
(Optional) Displays information about CA MIM facilities that are active on the local system and what service level you are running on each facility. This information is displayed in message MIM0090I.
(Optional) Displays the name and status (active or inactive) of each selectable feature that is supported by the active facilities. This information is displayed in message MIM0670I.
(Optional) Displays information about the status of CA MIM control files and checkpoint files. Control file information is displayed in message MIM0102I, and checkpoint file information is displayed in message MIM0104I.
(Optional) Displays the current values of the CA MIM GLOBALVALUE parameters, which provide details about your virtual control file recovery and master selection options. This information is displayed in message MIM0373.
The display shows the VCFMASTER candidate list in effect. Systems marked with an asterisk (*) are permanently ineligible because they are not connected to one or more other systems through CTC paths. Systems marked with a minus sign (-) are temporarily ineligible because they are currently unable to communicate with one or more systems.
Note: If GLOBALVALUE ANYELIGIBLE=YES was specified on a MIMINIT statement, then the display also includes eligible master systems not in the VCFMASTER candidate list.
(Optional) Displays information about the initialization values that can be set using the MIMINIT statement or as a parameter on the START command that invokes CA MIM. This information is displayed in message MIM0037I.
Displays statistics about CA MIM control file and checkpoint file I/O activity. Control file information is displayed in message MIM0039. Checkpoint file information is displayed in message MIM0107.
Without any operands, CA MIM displays the statistics that have accumulated for both file types since the last time CA MIM was started. To obtain statistics for control files only, specify D IO=CF. To obtain statistics for checkpoint files only, specify D IO=CHKPT.
To reset the counters, issue the command D IO=RESET. When you issue the next D IO command, CA MIM displays an additional line that includes the statistics that have accumulated since you last reset the counters.
It is also possible to perform a reset for each individual file type.
D IO(CF,RESET) or D IO=(CF, RESET).
D IO(CHKPT,RESET) or D IO=(CHKPT,RESET).
(Optional) Tells CA MIM to display information about the CA MIM product in general, rather than about a specific facility.
Specify this operand before the ALL, INIT, OPTIONS, or STATISTICS operands. You also should specify the MIM operand before any other operand that is truncated in such a way that it may be ambiguous with operands for other facilities. Because MIM is a positional operand, you must specify it before any other operand on this command.
Displays information about all modules loaded by CA MIM. Optionally, to tailor the requested display, a module name mask can be supplied with this operand to display specific load modules. Specify one of these values:
Specifies the name for any load module that matches the name mask provided. You can use the * and # wildcard characters.
The asterisk (*) means that a match occurs for any names containing the characters preceding the asterisk. The pound sign (#) means that a match occurs for the name provided, and names containing any characters located where the # is placed in the name string.
Displays information about all CSECTs in the requested module. If this is omitted, then no CSECT information is presented in the module display. The CSECT information display can be limited through the use of a CSECT name mask. It only has meaning for CA MIM load modules.
Note: You must specify CSECT to display routines.
Requests that individual subroutine information be formatted and displayed with CSECT information. It only has meaning when the CSECT operand is requested.
(Optional) Displays information about each message table (original or replacement). The name, language, and number of messages per table/language are displayed for each message table.
(Optional) Displays information about the CA MIM operating values that can be set through the SETOPTION command. These are the operating values that affect more than one CA MIM facility. This information is displayed in message MIM0038. The values displayed can be dynamically changed using the SETOPTION command.
Displays the operating system level, SMF ID, and system name for the z/OS operating system currently running.
Displays information about VCF (CTC) paths and details about cross-system communications paths for virtual control file processing. This information is displayed in message MIM0176. By default, CA MIM displays information that it gathered from the last time you started CA MIM. If you want to reset the counters, issue the command D PATH=RESET. Issuing the next D PATH command displays accumulated statistics from the last counter reset and the counts after the initialization.
(Optional) Displays information about the status of systems. This information is displayed in message MIM0108I.
Displays information about CA MIM service subtasks. Optionally, to tailor the requested display, a subtask name mask can be supplied with this operand to request specific subtasks. You can use the * and # wildcard characters (described previously).
Default: OPTIONS
Usage Notes: DISPLAY MIM Command
Example: DISPLAY Command
To display the current initialization and operating values and other information for all CA MIM facilities, issue this command:
DISPLAY MIM ALL
CA Technical Support uses the DUMP MIM command for diagnostic purposes. This command is to be used only when you are directed by CA Technical Support to do so.
Scope: Local
This command has the following format:
DUMP MIM [ACTAREA]
[ADDRESS=(address[,length])]
[CHANGEMEMORY=(addr,newvalue[,key])]
[C0AREA]
[DFRE]
[DNE]
[FCV]
[GCDAREA[={CHKPT[=00]|CTC|DASD[=00]|VCF}]]
[GMR[={CHKPT|VCF}]]
[GPRMBLK]
[GQ1AREA]
[GQ2AREA]
[GQ8AREA]
[GSIE]
[GVALBLK]
[HYPERSTAR=hyperopt]
[IOSTATS[=CHKPT]]
[LOCKS]
[MLI]
[MODULE=(module[,length] )]
[MSGDIR]
[MSGTBL]
[PATH[=ALL]]
[ROUTINE]
[S1AREA]
[STRNAME=structure]
[T1AREA]
[TRAPS=keywords]
[UCB=(dddd[,length])[,UPDATE=(disp,data)]]
[USERAUTH]
[UXDEF]
[UX0AREA]
[UX1AREA]
[VCFAREA]
[VCFPATHS[=ALL]]
[VCFTRACE]
(Optional) Dumps the ACTAREA control block.
(Optional) Dumps the requested storage beginning at the specified one- to four-byte address and for the specified length. The address is required, while length is optional. Both values are specified in hexadecimal format. For example, the address could be entered as X'1C000' or 1C000. The default length displayed if no value is entered for length is X'D0' bytes.
(Optional) Changes the contents of memory.
(Optional) Dumps the C0AREA control block.
(Optional) Dumps the DFRE control blocks.
(Optional) Dumps the DNE control block Chain.
(Optional) Dumps the FCV control block.
(Optional) Dumps the GCDAREA control block for the active control file. Optionally, you can specify CHKPT (or CKPT) for the current checkpoint file, CTC for CTC information, a DASD file ID for DASD file information, or VCF for virtual control file information.
(Optional) Dumps the GMR control block. Optionally, you can dump the GMR information for the active checkpoint data set (DUMP MIM GMR=CHKPT (or CKPT)), or for the virtual control file (DUMP MIM GMR=VCR).
(Optional) Dumps the GPRMBLK control block.
(Optional) Dumps the GQ1AREA control block.
(Optional) Dumps the GQ2AREA control block.
(Optional) Dumps the GQ8AREA control block.
(Optional) Dumps the GSIE control blocks.
(Optional) Dumps the GVALBLK control block.
(Optional) Sets debugging options for the Hyperstar selectable feature. When
(Optional) Dumps the I/O statistics control block for the active control file. Optionally, you can dump the I/O statistics for the active checkpoint data set if you specify DUMP MIM IOSTATS,CHKPT.
(Optional) Dumps the lock words for the CA MIM internal lock mechanism.
(Optional) Dumps the MLI control block.
(Optional) Dumps the specified module in hexadecimal dump format. The one- to eight-character module name is required. Optionally, you can specify the one- to four-byte length. The default length displayed is X'C0' bytes.
(Optional) Dumps the MSGDIR control block.
(Optional) Dumps the MSGTBL control block.
(Optional) Dumps VCFPATH control blocks for all locally defined paths. If the optional keyword, ALL, is specified, then paths defined for all systems are displayed as well as the locally defined paths.
(Optional) Dumps the storage where the named routine is loaded.
(Optional) Dumps the S1AREA control block.
(Optional) Specifies the name of a coupling facility structure control file that is to be dumped to a system dump data set.
Note: This parameter has no effect on z/VM systems. It is included here only for consistency with CA MIM systems.
(Optional) Dumps the T1AREA control block.
(Optional) Enables and disables the internal CA MIM diagnostic code.
(Optional) Provides display and update of UCB control blocks. If UPDATE is specified, then the UCB is updated. If UPDATE is not specified, then the UCB contents are displayed. These values can be specified as follows:
Specifies the device address of UCB to display or update.
length--(Optional) Specifies the length, in hex, to display.
Default: 30.
(Optional) Specifies that the UCB is to be updated.
disp--Specifies the displacement into UCB to update.
data--Specifies the data to place at displacement disp into UCB. You can specify one or more contiguous bytes.
Note: This parameter has no effect on z/VM systems. It is included here only for consistency with CA MIM systems.
(Optional) Dumps the USERAUTH control block.
(Optional) Dumps the UXDEF control block.
(Optional) Dumps the UX0AREA control block.
(Optional) Dumps the UX1AREA control block.
(Optional) Dumps the VCFAREA control block.
(Optional) Dumps VCFPATHS control blocks for all locally defined paths. If the optional keyword, ALL, is specified, paths defined for all systems are displayed as well as the locally defined paths.
(Optional) Dumps the trace table data associated with virtual control file processing.
Usage Notes: DUMP MIM Command
Example: DUMP MIM Command
To dump the contents of the VCFAREA control block, issue this command:
DUMP MIM VCFAREA
The ENDIF statement marks the end of a block of commands or statements that should be executed on a subset of the systems in your configuration. ENDIF statements are used with IFSYS statements. For more information about the IFSYS/ENDIF statement block, see the IFSYS Statement in this chapter.
This command has the following format:
ENDIF
Usage Notes: IFSYS/ENDIF Statement
Example: IFSYS/ENDIF Statements
Suppose you want to specify alternate DEVCLASS parameter, depending on the system. To make each system use the correct statement, you would specify the following IFSYS/ENDIF statement block:
IFSYS SYS1,SYS2 MIMINIT DEVCLASS=TAPE ENDIF
IFSYS SYS3 MIMINIT DEVCLASS=NONE ENDIF
The FREE command allows you to release devices and resources held by a system that is currently inactive. You should not attempt to free an active system.
Scope: Global
This command has the following format:
FREE sysid | (sysid1,sysid2,...)
Identifies an inactive system that is to be freed. You can use the system name, alias, or index number to identify this system. You can specify multiple system IDs if you want to free more than one system, but multiple IDs must be enclosed in parentheses.
Usage Notes: FREE Command
Important! You should not free a system unless you are sure that CA MIM is not running on that system. If you free a system that is active, the system will ABEND with user code U0322.
Examples: FREE Command
FREE SYSB
FREE (SYSB,SYSC)
The GCS command lets you issue GCS or CP commands that will be executed on the MIMGR service machine. Authorized users can use the GCS command to issue commands (such as SPOOL CONSOLE or PURGE READER) that otherwise could only be done by logging onto the MIMGR console.
This command has the following format:
GCS command text
Specifies the command you wish to be executed on the MIMGR service machine.
Usage Notes: GCS Command
Examples: GCS/CP Command
Q CTC (GCS Command to display status of channel-to-channel adapters)
D 0000000.80 (CP Command to display 80 bytes of low storage.
The GLOBALVALUE command lets you assign global parameters for CA MIM. GLOBALVALUE can be used as a statement in the INIT MIM file or issued as a command after CA MIM is synchronized. When GLOBALVALUE is issued as a command on one system, the values entered are updated on all systems. The global parameters affect the way VCF communication operates.
Scope: Global
This command has the following format:
GLOBALVALUE [ANYELIGIBLE={NO|YES}]
[MOSTPREFERRED={NO|YES}]
[NOMASTER={TERMINATE|WAIT}]
[VCFMASTER={sysids|NONE}]
(Optional) In a recovery situation, determines whether CA MIM initiates migration to any eligible master system when none exists in the VCFMASTER candidate list.
Default: YES
(Optional) Determines whether CA MIM selects the most preferred master system available in the VCFMASTER list or uses the same master that was in control the last time CA MIM was running. It also determines whether CA MIM automatically initiates migration when a more preferred master system joins the complex.
Default: NO
(Optional) Determines how client systems react when the only eligible master system terminates or becomes unresponsive. The value for this operand is only valid in CTCONLY environments.
WAIT
Specifies that the client systems wait for the master to restart. During the waiting period, these systems issue periodic MIM0396 messages.
Specifies that the client systems terminate after issuing MIM0397 message.
Default: WAIT
(Optional) Allows you to create the master system candidate list used to determine the master system in VCF environments. Each master system must be connected to all other systems in the complex by CTCPATH statements. The order of the systems in the candidate list is the order of preference used by CA MIM. You can specify a maximum of 32 systems.
Default: NONE
Note: Although the default is NONE, at least one master system must be specified in a CTCDASD or CTCONLY environment. If you want to start CA MIM in a CTCDASD environment without using CTC devices for initial communication, then specify the following statement in the INIT MIM file:
COMMUNICATION=(CTCDASD,INITIAL=DASD)
Note: Although DASD is specified for the initial control file choice, you must still specify at least one eligible master system in the VCFMASTER list, because the communication method selected is CTCDASD.
Usage Notes:
Example: GLOBALVALUE Command
To indicate that CA MIM should use the most preferred master system from the VCFMASTER list, specify the following:
GLOBALVALUE MOSTPREFERRED=YES
The IFSYS statement marks the beginning of a block of commands or statements that should be executed on a subset of the systems in your complex. It identifies the systems on which these commands or statements should be executed. IFSYS statements, which are used with ENDIF statements, let you conveniently share the same MIM parameter files among systems in a multiple-system configuration.
This statement has the following format:
IFSYS sysid1[,sysid2,sysid3,...,sysidn]
Specifies the IDs of the systems on which the following commands or statements should be executed, to a maximum of 16 IDs. You can use system names, aliases, or index numbers to identify systems.
Usage Notes: IFSYS/ENDIF Statement
Example: IFSYS/ENDIF Statements
Suppose you want to specify alternate DEVCLASS parameter, depending on the system. To make each system use the correct statement, you would specify the following IFSYS/ENDIF statement block:
IFSYS SYS1,SYS2 MIMINIT DEVCLASS=TAPE ENDIF
IFSYS SYS3 MIMINIT DEVCLASS=NONE ENDIF
The INCLUDE statement identifies a file that CA MIM should read during initialization. It is most often used within message facility message files.
This command has the following format:
INCLUDE file
Identifies the file to include.
Usage Notes: INCLUDE Statement
Example: INCLUDE Statement
To include additional commands or statements in the MIMCMNDS file, specify this statement:
INCLUDE MICCMNDS
File MICCMNDS can contain any CA MIM statements or commands that would normally be specified in MIMCMNDS.
The MIGRATE command lets you initiate migration to a new checkpoint file, to a new control file, or to a new master system.
This command has the following format:
MIGRATE {CHKPTFILE[=fileid] | CONTROLFILE[=fileid] | MASTER[=sysid]}
Initiates migration to the specified checkpoint file, if it is usable. If no file ID is specified, migration proceeds to the next available checkpoint file. You can abbreviate this parameter as CHKP.
Initiates migration to the specified control file. Specify the ID of the new control file. If it is usable, CA MIM will migrate to the new control file. If no file ID is specified, the migration will be to the next available control file. This parameter can be abbreviated to CF.
fileid specifies the last two characters of the ddnames used for checkpoint and control files.
Initiates migration from the current master system or DASD control file to the specified master system and abandons the virtual control file managed by the master system. Specify the system ID of the new master system. The target system must be eligible to become the master in order for this process to proceed successfully. If no system ID is specified, then CA MIM migrates to the next available master system. This parameter can be abbreviated VCF.
Usage Notes: MIGRATE Command
Examples: MIGRATE Command
MIGRATE CONTROLFILE=01
MIGRATE MASTER=SYS1
MIGRATE CHKPTFILE=02
The MIMINIT statement lets you set initialization values that affect CA MIM, no matter what components and facilities you are using.
This command has the following format:
MIMINIT [BLKSIZE=size]
[CDEFAULT={YES|NO}]
[CHKPTDSN={NONE|MIMCKP}]
[CMDPREFIX={cmdprefix|NONE}]
[COMMUNICATION=(method [,CTCDASD={NO|YES}[,INITIAL={CTC|DASD}]])]
[,CTCONLY]
[,DASDONLY]
[,NONE]
[COMPATLEVEL=level]
[DEVCLASS={NONE|TAPE}]
[DEVEXCL={name|NONE}]
[FORMAT={BOTH|CF|CHKPT|NONE}]
[GCMF={OFF|ON|EXTERNAL}]
[GTAF={OFF|ON|EXTERNAL}]
[ICMF={OFF|ON|EXTERNAL}]
[INITEXIT={module|NONE}]
[LOGPARAMETERS={NO|YES}]
[MSGTEXT={ASIS|UPPERCASE}]
[SIGNON={NO|YES}]
[SUPPRESSRESP={NO|YES}]
[SYSID=sysid]
[TPCF={OFF|ON}]
[VCFBUFFERSIZE=nn]
[VCFMAXBLOCKS=nn]
(Optional) Determines what block size CA MIM uses to access its control files. Specify a block size in place of the size variable. The lowest possible value is 4096 bytes. The highest possible value is 32767. The initial value 6144 is suitable for most sites.
You can improve system performance in some environments by increasing the block size. This is especially true when you are running CA MIC. Most sites should use the default value for this parameter unless CA MIM issues message MIM0025, which indicates that you should increase the block size.
You need to reformat your DASD control files if you change the value for this parameter.
CA MIM automatically adjusts this value if MIMINIT COMPATLEVEL=11.9 or higher. If CA MIM is using physical control files, the adjustment occurs when a new control file is formatted. If CA MIM is using a virtual control file, the adjustment will occur during CA MIM startup. In most cases, the BLKSIZE will be increased, but in some cases it may be reduced in an effort to maximize the number of usable bytes on the file.
The BLKSIZE value coded on the MIMINIT statement (or defaulted) can be displayed using the DISPLAY MIM INIT command, whereas the automatically adjusted value can be displayed with the DISPLAY IO command.
Default: 6144
(Optional) Controls how CA MIA uses the CLASS MIM file to initialize the identity of tape drives. If set to YES, tape drives are automatically added to a pre-defined class corresponding to their model number, such as 3420, 3480, and so forth, and are also added to any user-defined classes specified for the drive in CLASS MIM. If set to NO, tape devices are added only to the classes specified in CLASS MIM.
When CDEFAULT=YES, IBM tape drive model numbers are reserved, and cannot be specified as a user-defined class in the CLASS MIM file, but when CDEFAULT=NO, you may specify IBM model numbers as a user-defined drive class. This ability can be used to exclude special purpose drives from their model number default class. For example, you may want drives contained within an automatic library to be known by a special name, such as LIB3490, but not to be known by the generic 3490 to prevent inadvertent selection of the drive by model number.
For an explanation of how drive class can be used within the ATTACH command to automatically select an available drive, see the chapter “Configuration Options” in the CA MIA Tape Sharing for z/VM Programming Guide.
Default: CDEFAULT=YES
(Optional) Sets the name by which checkpoint files will be defined in the DDNAMES MIM file. In z/VM systems, the only acceptable settings for CHKPTDSN are NONE or MIMCKP.
If set to NONE, it is not necessary to include a checkpoint file definition in the DDNAMES MIM file.
The CHKPTDSN parameter must be set to MIMCKP if MIMINIT COMMUNICATION=CTCONLY or CTCDASD. CA also recommends the same setting if COMMUNICATIONS=DASDONLY, but it is not required. If this setting is specified and no valid checkpoint file is defined in the DDNAMES MIM file, a non-fatal error message (MIM0334E) is issued, indicating that a checkpoint file must first be defined.
Default: CHKPTDSN=NONE
(Optional) Determines what command prefix is used. You can specify a one- to eight- character prefix in place of the MI prefix in the command text when you direct a CA MIM command to a z/VM system through the CA MIC component. This cannot be used locally to issue CA MIM commands. Specify a prefix in either character or hexadecimal format, or specify NONE.
For details about the content of the command prefix character string, see the appendix, “Valid Characters for CMDPREFIX.”
Default: CMDPREFIX=@
(Optional) Indicates the initial method of multi-system communication the CA MIM Driver control program uses to communicate CA MIM transactions throughout your enterprise. Depending on your environment, you may choose to use DASD, or CTC devices as vehicles for transporting CA MIM transactions.
Provides both methods of communication, DASD and channel-to-channel devices (CTCs). CTCDASD requires a shared DASD control file as well as CTC devices. Optionally, coupling facility structure control files can be used in place of or in conjunction with DASD control files. You can use the MIGRATE command to change the method of communication while CA MIM is running. You can specify a value for the INITIAL keyword when you select this method.
The INITIAL keyword is used to determine which method of communication is used when CA MIM first starts, CTC or DASD. The default is CTC. The following example shows how to specify CTCDASD when you select DASD as the initial control file method:
COMMUNICATION=(CTCDASD,INITIAL=DASD)
Provides virtual control file communication only. CA MIM tasks communicate through CTC devices entirely with no use of shared DASD control files.
Provides storage of control file information on shared DASD only. CA MIM tasks communicate by accessing the shared DASD control files or coupling facility structure control files.
This value is used only if CA MIM is running on a single system (called SOLO mode) where control files are not needed. If CTC devices or DASD control files do exist, they will not be used.
Default: COMMUNICATION=DASDONLY
At COMPATLEVEL=12.0, the COMMUNICATION parameter only specifies the initial communications method. At any time, you may switch communication methods provided you have configured an alternate method.
(Optional) Indicates the format of the CA MIM control file and the associated functionality that is to be activated. The value must be the same across all systems in the CA MIM complex. You can change the value dynamically using the ACTIVATE COMPATLEVEL command. Acceptable values for this operand are 11.81, 11.82, and 12.0.
Note: For more information, see the CA MIM Programming Guide.
(Optional) Allows you to place tape devices under CA MIA management. You can specify one of the following:
Indicates that only devices named in the UNITS MIM file will be placed under CA MIA management.
Places all tape devices under CA MIA management, even if they are not in the UNITS MIM file.
If you specify TAPE, and do not use a UNITS MIM file, then all tape devices in your system will be selected for CA MIA control. In this case, the global name for each device will be the same as its real address. For example, a device at raddr=5C0 will be known globally as 5C0. This will produce unsatisfactory results if the same physical device is known by a different address on another system, unless at least one of the systems defines a UNITS MIM file (or a MIMUNITS member on z/OS).
Note: A physical device can have only one global name.
If 3480 and 3490 tape drives identified during system generation as unsupported devices are to be managed by CA MIA, you must explicitly include those devices in the UNITS MIM file. Simply specifying TAPE will cause CA MIA to manage all tape drives except the 3480s and 3490s genned as unsupported devices.
Default: DEVCLASS=NONE
(Optional) Identifies the file that contains a list of tape devices to exclude from CA MIA management. CA MIM automatically defines the file EXCL MIM A as MIMEXCL during startup. You can issue more FILEDEF commands to provide alternative DDNAMEs.
Represents the DDNAME of the exclude file that CA MIM uses.
Indicates that you are not using the device exclusion functionality.
Default: DEVEXCL=NONE
(Optional) Determines whether the DASD checkpoint files, control files, or both are formatted at startup on the first system started. Specify one of the following values:
Formats both the checkpoint file and control file.
Formats the control file. In a CTC-only environment, it refers to the backup virtual control file residing in a special area on the checkpoint file.
Formats only the checkpoint information in the checkpoint file. You can use the abbreviation CKPT for this operand.
No formatting is done.
We recommend that you set FORMAT=NONE in the INIT MIM file because it is generally not a good idea to format control and checkpoint files each time you start CA MIM. In the unusual instance when it is necessary to format these files, you can specify FORMAT=BOTH (or CF, or CHKPT) on the START command.
(Optional) Determines whether the Global Command and Message Facility (GCMF) of the CA MIC component is activated.
Specify ON to run GCMF on your z/VM system. When you do this, all other systems that share your control file must also specify the values ON or EXTERNAL. Specify OFF if you do not want to run GCMF on your z/VM system. All other systems must also be set to OFF.
Specify EXTERNAL if you do not want to run GCMF on your z/VM system, but other systems that share your control file do run GCMF. This situation occurs if you have a different set of CA MIM components running on your z/VM and z/OS systems.
You need to reformat your control files if you change the value for this parameter.
Default: GCMF=OFF
(Optional) Determines whether the Global Tape Allocation Facility (GTAF) of the CA MIA component is activated.
Specify ON to run GTAF on your z/VM system. When you do this, all other systems that share your control file must also specify the values ON or EXTERNAL. Specify OFF if you do not want to run GTAF on your z/VM system. All other systems must also be set to OFF.
Specify EXTERNAL if you do not want to run GTAF on your z/VM system, but other systems that share your control file do run GTAF. This situation occurs if you have a different set of CA MIM components running on your z/VM and z/OS systems.
You need to reformat your control files if you change the value for this parameter.
Default: GTAF=OFF
(Optional) Determines whether CA MIM should process transactions for the Intersystem Communication Facility (ICMF) of the CA MIC for z/OS component.
Specify OFF for this parameter if the z/OS systems sharing your control file do not run ICMF. Specify ON or EXTERNAL if ICMF is running on the z/OS systems. ON and EXTERNAL are equivalent settings.
Default: ICMF=OFF
Note: Do not specify GCMF=OFF when you specify ON or EXTERNAL for ICMF.
(Optional) Names the CA MIM Initialization Exit module to be called during product startup.
Note: For more information on CA MIM user exit processing, see the chapter “User Exits” in the CA MIM Programming Guide.
Valid values are:
Loads the specified load module and makes one initialization call to it. Error messages are sent to the system log if the module cannot be found.
No call is made to the exit routine.
If no MIMINIT INITEXIT statement is specified, module MIMINIXT will loaded and called.
Default: INITEXIT=NONE
(Optional) Determines whether all of the startup values are recorded in the console log. Specify NO or YES on this parameter. CA recommends that you specify YES if you need diagnostic information about CA MIM.
If you specify LOGPARAMETERS=NO, specify it on the first statement in the initialization file. Unless this parameter is specified on the first statement, CA MIM issues MIM0079I messages to the system log until it reads the parameter LOGPARAMETERS=NO.
Default: LOGPARAMETERS=YES
(Optional) Determines whether CA MIM messages are to be issued in uppercase and lowercase, or in only uppercase. Those messages issued through the CA MIM message facility have message text that contains both uppercase and lowercase letters. If you have console devices that do not properly display EBCDIC lowercase letters, or if you prefer to see message text in uppercase characters, you can control the case of the characters in the messages issued by the CA MIM message facility. Only CA MIM messages under the control of the CA MIM message facility are affected by this parameter.
Note: For more information on the CA MIM message facility, see the CA MIM Programming Guide.
Valid values are:
Issue messages with text containing both uppercase and lowercase characters.
Issue messages with text containing only uppercase characters.
Default: MSGTXT=ASIS
(Optional) Indicates whether CA MIM should display routine sign-on messages when its facilities are initialized. Specify NO or YES.
Routine sign-on messages are sent to the system log no matter what value you specify.
Default: SIGNON=YES
(Optional) Indicates whether CA MIM should suppress routine messages that are issued as it executes commands in the CMNDS MIM and SYNCH MIM files. Specify NO or YES for this parameter.
This parameter does not stop messages from being issued if a command in one of these files cannot be executed (for example, due to a syntax error).
Default: SUPPRESSRESP=YES
(Optional) Overrides the z/VM system identifier specified in HCPSYS ASSEMBLE or SYSTEM CONFIG. It should be used only for testing. SYSID affects the processing of IFSYS and DEFSYS statements in the INIT MIM file, so it must precede these types of statements in order to be effective.
Production systems in your MIMplex definitely should not use a SYSID statement. It is better to use a valid system identifier on IFSYS and DEFSYS statements, because SYSID can create confusion if you add a new system or rename an existing system in your complex.
If two or more systems in your MIMplex specify the same SYSID, control file errors occurs, and CA MIM ABENDs.
Default: SYSID=sysid as specified on the SYSID macro in HCPSYS ASSEMBLE or SYSTEM CONFIG.
(Optional) Specifies whether the TPCF of the CA MIA component is activated. Specify OFF or ON.
Default: TPCF=OFF
(Optional) Specifies the number of bytes in the transfer buffer for the virtual control file. The lowest possible value is seven bytes more than the block size you specify on the BLKSIZE parameter; the highest possible value is 62464 bytes.
If this buffer is too small (less than the average number of bytes read per service cycle), then data is transmitted slowly. If this buffer is too large, then an excessive amount of real storage is used. Note that you can use the DISPLAY IO command to see how many bytes are read per service cycle. We recommend that you use the initial value 32768.
You must specify the same value for the VCFBUFFERSIZE parameter on all systems.
Default: VCFBUFFERSIZE=32768
(Optional) Tells CA MIM how many Virtual Control File blocks to allocate during CA MIM initialization. When CA MIM tasks need more blocks, CA MIM acquires more blocks dynamically.
Notes:
Default: VCFMAXBLOCKS=1200
Usage Notes: MIMINIT Statement
MI START KEYWORD1=value [KEYWORD2=value]
Examples: MIMINIT Statement
MIMINIT SYSID=VMSYS1
MIMINIT GTAF=ON TPCF=ON GCMF=ON
MIMINIT SIGNON=YES
|
Copyright © 2014 CA.
All rights reserved.
|
|