Advanced Topics › Control and Checkpoint File Considerations › How You Migrate to a New Control File › How You Migrate to a DASD Control File

How You Migrate to a DASD Control File

You can migrate to any DASD control file that has been formatted properly for the release of CA MIM that you are running. Migration to a DASD control file occurs in one of several ways:

• From a virtual control file to a DASD control file in the CTCDASD environment
• From one DASD control file to another DASD control file in the DASDONLY or CTCDASD environment
• From a coupling facility structure control file to a DASD control file in the DASDONLY or from a coupling facility structure to a virtual control file in a CTCDASD environment

To migrate from a virtual control file to a backup DASD control file,

1. Issue the following command to view the list of available control file IDs:

   DISPLAY FILES
   

2. Issue the following command

   MIGRATE CONTROLFILE=nn
   

   nn

   Specifies the control file ID of the backup DASD control file

   For example, to switch from the current virtual control file and begin using DASD control file 01, issue this MIGRATE command:

   MIGRATE CONTROLFILE=01
   

To migrate from the current DASD control file to a new DASD control file

1. Issue the following command to view the list of available control file IDs:

   DISPLAY FILES
   

2. Issue the following command

   MIGRATE CONTROLFILE=nn
   

   nn

   Specifies the control file ID of the new DASD control file

You do not have to migrate to the first or next control file identified in your startup procedure. You can migrate to any usable control file that has been formatted properly, even if the ID of the control file is lower than the ID for the current control file.

To migrate CA MIM to the next available control file

Issue the following command:

MIGRATE CF

Note: When you migrate from a virtual control file to a DASD control file, the virtual control file is deactivated automatically.