Migration << >>

Migrating Data

The process of extracting data for migration is performed by invoking MIGVIZ EXEC at the time the VM ID to be migrated is automatically logged. The VM ID to be migrated cannot be used by the user during the extraction process.

Note   To migrate calendata data, make sure that the IBM PROFS xxxCAL calendar facility is operational prior to running the PROFS source extractor.

   To extract e-mail data

  1. Log on as the MIGRATOR VM ID.
  2. Type MIGWIZRD and press ENTER to start the source extractor. The following is displayed:

    3. Source Extractor for IBM (R) PROFS (R) and OfficeVision (TM) Microsoft Exchange Server Migration Wizard

    The following parameters are specified in MIGPARMS DATA file.

    You can change these parameters using this menu, or by using XEDIT.

    OV/VM (PROFS) Nickname File: File name: File type: Accounts File: File name: File type: PROFS Calendar Migrator vmid (PROFS system only) : Notify VM id : HOWARDS File Transfer VM id : MIGXFER Thread timeout (min) : 30 Spool Console required (TRUE/FALSE) : FALSE Number of migration threads : 05 Replace previously migrated accounts (TRUE/FALSE) : TRUE

    -------------------------------------------------------------------

    << BACK NEXT >> FINISH CANCEL HELP F10/F22 F11/F23 F12/F24 F3/F15 F1/F13

  3. (Optional) In the OV/VM (PROFS) Nickname File field, type the name and file type of the nickname file. If a Nickname file is not specified, the extractor uses OFSUAD FILE.


    4. Tip   If you are migrating only a few accounts, create a nickname file or a OFSUAD FILE with those accounts in it and set the appropriate field to point to the file.
  4. In the Accounts File field, type the name and file type of the accounts file with a list of VM IDs for which you want to extract data. The Accounts file is a temporary working file that must be specified.
  5. (Optional) If you are migrating calendars from a PROFS system, type the corresponding VM ID in the PROFS Calendar Migrator VM ID field.
    6. Skip this step if you are migrating calendars from OfficeVision.
  6. In the Notify VM ID field, type the VM ID to which error messages are sent. This VM ID does not need to have Administrator permissions.
  7. In the File Transfer VM ID field, type the VM ID to which all the extractor data should be sent.
  8. In the Thread Timeout field, type the maximum number of minutes it should take to migrate each VM ID. After this period, the MIGWIZRD EXEC starts the process for the next VM ID regardless of whether the current one has completed extracting data or not.
  9. In the Spool Console Required field, set the value to TRUE to send console updates to the NOTIFY VM ID to monitor progress, or set the value to FALSE so the updates are not sent.
  10. In the Number of Migration Threads field, set the number of VM IDs that will be migrated simultaneously. If you set this number too high, it could affect performance and resources on the host computer.
  11. In the Replace Previously Migrated Accounts field, set the value to TRUE if you want to migrate data for VM IDs that have been migrated previously, or set the value to FALSE if you do not want to migrate previously migrated VM IDs.
  12. Press F11 to continue. The following is displayed:

    13. Source Extractor for IBM (R) PROFS (R) and OfficeVision (TM) Microsoft Exchange Server Migration Wizard

    What information would you like to migrate?

    Type Y to select option, or N to reject it.

    N Remote addresses creation information (REMADDR FILE) N Mailbox creation information (MAILBOX FILE) Y Email messages (Notelogs and In-basket) From: 1994/10/28 to 1995/10/28 Y Schedule information (Calendars and Reminders) From: 1995/10/28 to 1996/10/28 Y Documents from OFSINDEX FILE From: 1994/10/28 to 1995/10/28 Y Personal Address Book (Nicknames and Distribution lists)

    -------------------------------------------------------------------

    << BACK NEXT >> FINISH CANCEL HELP F10/F22 F11/F23 F12/F24 F3/F15 F1/F13

  13. Set the options to Y or N based on what information you need to migrate. Also, update the date range for each type of information that is being migrated.

    14. Caution   The date range does not dynamically update. To avoid not migrating recent items, set the To dates to a future date in case you forget to update them.

  14. Press F11 to continue. The accounts file is displayed.
  15. Edit the accounts file as needed to remove VM IDs that you do not want to migrate.
    16. The status field can have three possible values:  
  16. Press F12 to start extracting data.
  17. When the MIGWIZRD EXEC is finished, it displays zero for both the Number of Not Processed Users and the Number of Migration in Progress:
    18.    * Number of not processed users   = 0
   * Number of migration in progress = 0
    Type SHUT to end the program.

This process creates several items in the reader of the file transfer VM ID, depending on the options selected in the second screen.

Item Description
<VM ID> PKL Packing list for the migration files of the VM ID.
<VM ID> PRI Primary intermediate file for the migration files of the VM ID.
<VM ID> SEC Secondary intermediate file for the migration files of the VM ID.

These files are stored in ASCII format and should not be edited. For each VM ID, there can be multiple primary intermediate files in the MIGXFER reader. Files are created on the MIGRATOR minidisk for each VM ID. The files that are created depend on the types of data that were extracted. The types are LOG, PAB, CAL, and ERROR.

   To move the migration files to Microsoft Exchange Server

  1. Log on as the MIGXFER VM ID.
  2. Type MIGXFER and press ENTER to start the transfer tool. The following is displayed:

    3. Source Extractor for IBM (R) PROFS (R) and OfficeVision (TM). Ver 4.0

    There are 5292 K bytes available on A disk. Total size of selected files is 157 K. The actual space required to store all files may be greater due to blocking factors. Select a subset of files that can be transferred by editing this file.

    User ID File Size 00000 * * * Top of File * * * 00001 HOWARDS 121.313 K 00002 BILLLEE 35.672 K 00003 * * * End of File * * *

    ------------------------------------------------------------------- FINISH RECALCULATE CANCEL F12/F24 F10/F22 F3/F15 ====>

  3. (Optional) Select a subset of files to be transferred by editing this list. If there is limited space on the minidisk, press F10 to recalculate the total size of the selected files.
    4. The transfer tool modifies the files to the migration file format and transfers them from the reader to the minidisk. The MIGXFER EXEC also creates MIGXFER BAT, MIGXFER PKL, and MIGPURGE EXEC on the minidisk.

  4. Download the MIGXFER BAT file to the personal computer.
  5. At the personal computer, type:
    6. MIGXFER <path to your terminal emulation software>to transfer the migration files to the personal computer as *.PRI, *.SEC, and MIGXFER.PKL. This step consolidates multiple PRI files per VM ID into one PRI file and all packing list files (PKLs) into one file.

    Note   The minidisk with read and write access and the most available free space is used to store the intermediate files. Therefore, make sure that the minidisk with read and write access and the most free space is the one you want to use for the intermediate files.

  6. On the host, type MIGPURGE to remove the files from the reader.
  7. If you wish, edit the MAILBOX.PRI file to modify information, such as directory names, or to add additional directory import fields and data.
    8. For example, if you want to migrate department information with each mailbox, you can add the field "Department" to the end of the first line of the directory header and then add department names to the end of each line of data.

Important    If you need to change directory (common-name) names, you must do it before importing the migration files. After creating mailboxes, the directory name can only be changed by deleting the mailbox and creating a new one.

Migrating User Accounts in Multiple Account Files

You can merge the user accounts in several migration account files into one migration accounts file.

   To merge user accounts into one migration accounts file

  1. Start the PROFS Migration Wizard.
  2. In the Accounts File field, change the default accounts file name by typing a new file name.
  3. In the "Select VM ids which should be migrated" screen, XEDIT displays all entries in the file. Delete all entries in the file, if necessary.
  4. At the command prompt, type GET accounts file to retrieve the list of accounts you want to migrate.
  5. Press PF12. The user accounts from the different files can be migrated in one migration accounts file.

Data Character Translation from EBCDIC to ASCII

You can change how a character is translated from EBCDIC to ASCII by editing the MIGASCII DATA lookup table. The following procedure describes how to edit the MIGASCII DATA lookup table.

Note   All intermediate files are converted using the MIGASCII DATA lookup table.

   To edit the MIGASCII DATA lookup table

  1. Determine the EBCDIC character's hex value.
  2. Use the MIGASCII DATA lookup table to determine the position in the table that corresponds to the character.
  3. Change the value at that location to the hex value of the ASCII character to which you want this EBCDIC character translated.

Extracting PROFS Calendar Data

The following procedure is required for calendar extraction from an IBM PROFS system.

Note   You will need a CALENDAR_MIGRATOR id, which can be an existing user or a new user you create. This PROFS account must have a 191 minidisk large enough to contain one months calendar data for any one user. It should have permission to access all calendars including private calendars. This id must be specified in the MIGPARMS DATA file CALENDAR_MIGRATOR field, either by editing this file or specifying this id in the MIGWIZRD.

  1. From your Calendar Migrator id, link and access MIGRATOR's 191 minidisk.
  2. From your Calendar Migrator id, link and access the PROFS/OV calendar data (usually on xxxCAL's 59C-59F).
  3. Invoke MIGCALX EXEC Accounts_File for extraction of calendars.
  4. After extraction, log on to the MIGRATOR vm account and start MIGRATOR EXEC. This will update the MIGRATOR STATUS file and process calendar files.
  5. If you haven't already, you can now extract the rest of the users' data.

Note   The Calendar Migrator account and the Schedule information date range must be specified in the MIGPARMS DATA file. You can use the MIGWIZRD to set up this data or set it up manually by editing the MIGPARMS DATA file. This process will not migrate reminders. Reminders should be extracted using the calendar extraction of MIGWIZRD.