Migration << >>

Extracting Information from IBM PROFS

The IBM PROFS source extractor runs on the host system. It logs on each VM ID automatically and starts a program that extracts information. This program sends the extracted data to a VM ID. The PROFS source extractor copies information from all versions of IBM PROFS to:

Calendar and reminder data are migrated as a special message with an attachment. The user imports the data by opening the message and double-clicking the embedded schedule file. The message is in the same language used in the Migration Wizard dialog boxes. If this language is not the same as the user's, send the user a message with the translated instructions before migration.

Note   To create PAB entries for personal nicknames in chained files, the "NEWFILE" "filename filetype" must be on the 191 "A" mini disk.

How the Source Extractor Works

The IBM PROFS source extractor runs in a specially defined MIGRATOR VM ID. It takes the next VM ID from the list of VM IDs to be migrated and attempts to log on it automatically. If successful, it starts the MIGVIZ EXEC from a common minidisk. This executable file links to the MIGRATOR's 191 minidisk from which it can access the migration parameters and other migration programs. These programs extract the relevant data from notelogs, files, calendars, nickname files, and personal distribution lists. The data is sent to a file transfer VM ID. When a thread completes extracting all of a user's data or the maximum time limit is reached, the MIGRATOR goes on to the next unmigrated VM ID in the list.

To learn more about the internal workings of the source extractor, see "Source Extractor Programs" later in this chapter, and the source files for the source extractor, which are included with Microsoft Exchange Server.

Single-instance Storage

IBM PROFS uses single-instance storage for documents. One document addressed to multiple recipients on a server is stored only once. However, when users' documents are extracted for migration, each user will have a personal copy of each document placed in the migration files. As a result, significantly more disk space may be required on the Microsoft Exchange Server than was used on the IBM PROFS host.

If a document has been referenced in any note, it will be ignored when processing OFSINDEX. Once migrated to Microsoft Exchange Server, the note is imported with the referenced document attached.

There are several options for preventing the volume of migrated materials from overloading Microsoft Exchange Server computers. However, it is important to inform users about which documents are going to be moved.

Option When Advantages
Advise users to clean up their notelogs and maillogs before migration. A few weeks in advance, with additional reminders as time to migrate gets closer. Users control deleted mail, which can make the transition to the new mail system easier.
Limit migration to a recent date range. During the extraction process. Old documents are not migrated.
Migrate accounts only, without migrating notelogs, maillogs, calendars, and PABs. During the extraction process. Users start over with Microsoft Exchange Server.

Command-Line Programs in the Source Extractor

If you would like to run the source extractor from the command line, you need to examine the following source extractor files:

Document Migration

Documents from the document log (OFSINDEX OFSDATA) file and mailed documents are migrated to Microsoft Exchange Server as mail items with attachments. The following algorithm describes the translation which is performed with all documents:

Note   If you are migrating paper documents using the IBM PROFS source extractor, the following error message is migrated as an attachment along with the paper document tracking information: "* * * Unable to process document xxxxxHDCxxxx Nonzero rc from RETRIEVE xxxxxHDCxxxx. rc=2." This error message has a return code of 2 and the characters 'HDC' (hard copy document) in its CRON. You can ignore this error message.