Administering CA 2E Translator › Using CA 2E Translator Utilities › Translator 4.0 to 8.1 Data Migration

Translator 4.0 to 8.1 Data Migration

Follow the following procedure to migrate data from Translator 4.0 to the current version:

1. Check you have a recent backup of the 4.0 environment.
2. Check that the 8.1 version of trndtalib does not have the same name as the 4.0 version. If necessary, rename the 4.0 library before installing Translator 8.1.
3. If you translated multiple languages at 4.0 by creating multiple copies of trndtalib at 4.0, choose one language to be your base target language.
4. For each language other than base, copy all tgt records from trusm1p & trusm2p in their trndta40s into the base trndta40. Use cpyf, restricting on key of language.
5. For each language, check that aplorglib is still present and contains original language versions of aplpmtmsgf & aplcndfil.

For each language, run Copy Conditions to dictionary and the Copy Conditions file to Target library to update aplcndfil in the 4.0 target library. (It is not necessary to have completed translation of the whole application). Check the conditions files in gen, org & tgt have the same number of records.

For each language, set up an 8.1 target environment. Create a TE library for each, or re-using the 4.0 target library as desired. Be sure to use the 4.0 target language code as the 8.1 TE code.

For each language, if not re-using the 4.0 target libraries, copy the conditions file (aplcndfil), the prompt messages file (aplpmtmsgf), and the prompt messages archive file (called archpmtmsg) into the TE library.

For each language, check that the system values in the 4.0 environment are correct, in particular the original language. If you have changed the original language since starting to translate the application, contact CA technical Support for special instructions.

A problem can occur if user messages have been deleted in the model and the same message number (for example, usr0011) re-used by developers for a different message. If this has happened it will result in orphan entries in the user messages dictionary file. Use Query to check for this.

Check that there are no entries in the Translator user messages files that have been deleted from your model. Use a query, joining ytrndta40/trusm1p & aplmdllib/ymsgdtarfp with join type 3, joining where t01.m3msgx=t02.@@msg. Delete all orphan records found in trusm1p, along with any associated second level text records in trusm2p.

Check the number of records in ytrndta40/trusm1p using dspfd. If more than 10,000 records, chgpf y4usm1p & y4usm2p (size *nomax) accordingly.

If you need to rename a target environment, change the higher level key language id for the relevant records in trusm1p & trusm2p (use SQL or similar).

Change library list to the Translator 8.1 list and run the import option.

If setting up remote sites at 8.1, set them up initially as local for the 4.0 to 8.1 data migration. Once this is complete, follow the instructions in Moving TEs between Local & Remote to move the sites to remote.

If possible, migrate all 4.0 languages together as above. However, if data is not available from some remote sites, do the following:

1. Migrate the available sites first & start translating at 8.1.
2. On arrival of the later 4.0 environments, go through the procedures above, using the previously selected language as base. Be sure to make all checks for orphans and so on For user messages, remove the base language target entries from ytrndta40/trusm1p & 2p, using cpyf.
3. Copy the 8.1 dictionary files and TgtEnv file to another library.
4. Clear the 8.1 dictionary files using clrpfm.
5. Edit the TgtEnv file, deleting the previously-migrated languages and adding the new ones.
6. Run the migration job & check for success.
7. Re-add the deleted entries to the TgtEnv file (trtenvp) using ywrkf or dfu.
8. Copy all dictionary entries for the previously migrated languages back to the dictionary.
9. Check for success.