General CA MIM Statements and Commands › (MIM) MIGRATE Command-Migrate to New Checkpoint or Control File, or Master System

(MIM) MIGRATE Command-Migrate to New Checkpoint or Control File, or Master System

The MIGRATE command lets you initiate migration to a new checkpoint DASD file, to a new control file, or to a new master system.

Scope: Global

This command has the following format:

MIGRATE {CHKPTFILE[=fileid] | CONTROLFILE[=fileid] | MASTER[=sysid]}

CHKPTFILE

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.

CONTROLFILE

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. This value can also be the two-character XESFILEID associated with a coupling facility structure control file. This value is always numeric.

MASTER

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

• You can issue the DISPLAY FILES command to view the IDs associated with your control files.
• The MIGRATE command should be issued from a console, rather than from the CA MIM parameter data set.
• You must be authorized to issue system control commands to issue the MIGRATE command. TSO users generally are not authorized to issue system control commands.
• You cannot initiate migration to a DASD control file or a coupling facility structure control file unless you have already made that file available to CA MIM. If you have not done this in the startup procedure, you can use the ALLOCATE command for this purpose, but you must allocate the file on all systems before you can migrate.
• The MIGRATE command can be used to migrate to any eligible master system, including those systems not in the VCFMASTER list.
• In a CTCONLY or XCF environment, the MIGRATE command can only be issued after synchronization.
• CA MIM supports migrations to DASD/XES control files in any VCF environment. The migration can automatically allocate the control file on systems that have not previously allocated it.

Examples: MIGRATE Command

• To migrate from control file 00 to control file 01, issue this command:

  MIGRATE CONTROLFILE=01
  

• To migrate from the current master system to a new master system, issue this command:

  MIGRATE MASTER=SYS1
  

• To migrate from the current checkpoint file 01 to a new checkpoint file 02, issue this command:

  MIGRATE CHKPTFILE=02