To migrate data languages

In Infor Enterprise Server 8.4.1 and later, the coding of data languages is based on the ISO 639-1/ISO 3166-1 standard. In earlier versions, the coding was based on the ISO 639-2 standard. For details, see Multilanguage application data (OP).

Infor Enterprise Server still works with the old ISO 639-2 data languages. To use the new data language coding standards, a migration of the existing data languages might be required.

To find out whether a migration is required, start the Data Languages (ttaad1111m000) session and view the data language properties. A migration is required if ISO 639-2 data languages with status "Available" or "Base Language" are present. Migrate these languages according to the procedure described later.

If no ISO 639-2 data languages with status "Available" or "Base Language" are present, a migration is not required. However, you must remove all data languages with status "Pending for Addition" and/or "Pending for Deletion", otherwise you cannot convert new data languages to runtime.

Step 1. Define new ISO 639-1/ISO 3166 data languages
  1. Start the ISO 639 Languages (ttaad1512m000) session and check whether the ISO 639-1-based languages codes are present; if not, on the appropriate menu, click Import to import the missing languages.
  2. Start the ISO 3166-1 Countries (ttaad1513m000) session and check whether the ISO 3166-based country codes are present; if not, on the appropriate menu, click Import to import the missing countries.
  3. Start the Data Languages (ttaad1111m000) session. For each ISO 639-2 data language with status "Available" or "Base Language", define a new data language based on the new ISO 639-1/ISO 3166 standard. The new data languages have status "Pending for Addition".
Step 2. Define data language mapping

To define a mapping between the old ISO 639-2-based language codes and the new ISO 639-1/ISO 3166-based language codes:

  1. Start the ISO Data Language Migration (ttaad1211m000) session.
  2. Click Mapping. The ISO Data Language Mapping (migration) (ttaad1114m000) session starts. The session displays the old ISO 639-2 data languages with status "Available" or "Base Language" in the Data Language (from) field.
  3. Define the mapping between the old and new data languages: for each old data language displayed, specify the corresponding new ISO 639-1/ISO 3166 data language in the Data Language (to) field. For an example, refer to the session help. Note: all old data languages with status "Available" or "Base Language" MUST be mapped.
  4. To store the mapping and return to the ISO Data Language Migration (ttaad1211m000) session, click Save and Close.
Step 3. Migrate data languages
  1. In the Basic name for dump file field in the ISO Data Language Migration (ttaad1211m000) session, enter the basic name, including the path, of the sequential dump files the session will generate. For example: /home/ISOdump.
    • The session generates a separate dump file for each package combination. The package combination code is automatically added as a prefix to the basic filename.
    • The sequential dump files contain the records and data dictionary of all tables with enabled registered multilanguage fields.
  2. In the Basic name for error file field, enter the basic name, including the path, of the error files the session will generate. For example: /home/ISOerr.
    • The session generates a separate error file for each package combination. The package combination code is automatically added as a prefix to the basic error filename.
    • The error files contain error messages and statistics.
  3. To start the migration process, click Migrate.

Note Do not interrupt this process.

During the migration process, the following steps are automatically executed and indicated by a progress bar:

  • The sequential dump(s), mentioned above, are generated.
  • From the sequential dumps the data is imported again, using the data language mapping scheme as defined in step 2. This step links the existing translations to the new data language.

  • Based on the data language mapping scheme, users and software languages linked to old ISO 639-2 data languages are linked to the corresponding new data languages.

    If the user who executes the migration is not linked to a data language, the migration process links this user to the base language. You can change this manually after the migration.

  • If the process executed successfully, the following message is displayed: Migration data languages completed successfully.
  • If the process did NOT execute successfully, the following error message is displayed: Migration data languages NOT completed successfully. Check the logfile "log.mle_conv" in the $BSE/log folder for the possible cause, solve the issue(s) and restart the migration process.
  • The original ISO 639-2 data languages get the status "Migrated". The new ISO 639-1/ISO 3166-1 data languages get the status "Available", and the mapped base language gets the status "Base Language".

For example, after a successful migration, these data languages are present:

Data LanguageStatus
dutDutch; FlemishMigrated
enUSEnglish_UNITED STATESBase Language
engEnglishMigrated
frBEFrench_BELGIUMAvailable
freFrenchMigrated
gerGermanMigrated
nlNLDutch; Flemish_NETHERLANDSAvailable

 

In the example earlier, the $BSE/lib/data_langs file has this content:

en_US:b
fr_BE:a
nl_NL:a
Step 4. Finalize migration
  1. Log off and log on again.
  2. Start the Convert Changes to Runtime DD (ttams2200m000) session and convert all user data to runtime.

Note

  • After a successful migration, do not remove the specified data language mapping; this mapping is used by the Audit Management facility.
  • After a successful migration, you can add new data languages based on the new ISO 639-1/ISO 3166 standard. For details, see Multilanguage application data (OP).