Preparing space for the migration process

Verify that you have sufficient space on the V7.1.1 system for the migration process.

1. Verify that the system has the amount of space that was estimated in the planning step. Use the planning work sheet that you filled in with your information.
2. If you plan to extract the original server database to media for later insertion into the new database, ensure that you have enough storage space. Storage space is required for the database and the manifest file that the extraction process creates.
   1. Identify the device class to which you will extract the original database. The definition must exist in the server database, not just in the device configuration file.

      The device class must be sequential, and the device class type must be tape. Define a new device class if necessary.

   2. Ensure that space or volumes are available in the selected device class. The amount of space that you need is about the same as the current size of the original database.

      Ensure that the instance user ID that you create for the upgraded server has access permission to the location of the extracted data.

   3. Check that the access permissions are correct for the location that you plan to specify for the manifest file.

      The user ID that will run the database preparation and extraction utilities (DSMUPGRD PREPAREDB and DSMUPGRD EXTRACTDB) must have write access to this file.

      When the data is later inserted into the V7.1.1 database, the instance user ID that you use for the upgraded server must have access permission for the manifest file.

      The manifest file might be less than 1 KB. However, for a complex configuration, it might exceed 1 KB.