Working with the Delta Process for Translation Tables

This chapter provides an overview of the delta process and discusses how to:

• Set up a database instance.

• Copy the data from a prior release.

• Work with the delta process.

• Work with delta process advanced options.

Understanding the Delta Process

The delta process determines the development changes that have occurred in translation tables. The process compares the translation tables as they are at the time that you run the process with the translation tables as they were when you last ran the process. The process identifies the changes and indicates to translators or developers any new development in the translation tables that they need to edit. You determine the timing of the delta process. You can run the delta process as often as necessary.

You must perform setup tasks at the beginning of each JD Edwards EnterpriseOne software release. After you perform the setup, you can run the delta process as often as necessary. You should establish a schedule for running the delta process so that you can keep current on development changes to JD Edwards EnterpriseOne software.

Prerequisite

You must perform these setup procedures before you run the delta process. These procedures create the appropriate database instances and environments, and populate the data from the previous JD Edwards software release. After you finish these setup procedures, you can run the delta process.

You must complete all of these tasks before you run the delta process for the first time.

Setting Up a Database Instance

This section provides an overview of database instances and discusses how to:

• Set up a database instance.

• Add a new environment.

• Create the environments.

• Use translation tools to create an environment.

• Set up user profiles.

• Add user security.

Understanding Database Instances

Your database administrator must set up a database instance for each compare and language code page set that you use.

This table lists the possible environments or databases:

Work with the database administrator to set up libraries or database instances, or both, that apply to your current system environments, depending on your operating system platform and database server.

Note. Each database has specific setup requirements for each code page. Please follow the database administration guidelines for the current release of the database and Open Database Connectivity (ODBC) setup for code pages.

Forms Used to Set Up a Database Instance

Setting Up a Database Instance

Access the Machine Search & Select form.

1. Click the current machine name and data source for administering environment data sources in the detail area, and then click Select.

2. On the Work With Data Sources form, complete the Data Source Name field in the detail area, and then click Find.

3. In the detail area, click the row for the current data source mapping, and then click Copy.

4. On the Data Source Revisions form, complete the Data Source Name field, and then click OK.

5. Enter the new ODBC information and click OK.

Adding a New Environment

Enter P986110 in the Fast Path to access the Machine Search & Select form.

1. Click the data source mapping environment in the detail area, and then click Select.

2. On the Work With Object Mappings form, click Add.

3. On the Object Mapping Revisions form, complete these fields and click OK:

   • Environment Name

   • Object Type

   • Primary Data Source

   • Data Source Mode

   • Allow QBE

4. Map all the tables listed in this guide to the translation compare environment.

   All other tables can be mapped according to the standard OCM setup.

   Note. You should set up a translation compare environment as a login environment. The code page environment is used only for table mappings and can have one OCM mapping for the DEFAULT TABLE mapping.

Creating the Environments

You must create the environments that are needed to run the delta process. You can complete these tasks manually by using Oracle's JD Edwards EnterpriseOne System Administration tools or Oracle's JD Edwards EnterpriseOne Translation Tools applications.

Access the Work With Environments form.

1. Enter an existing compare environment in the Environment Name query by example line, and click Find.

2. Click the existing compare environment in the detail area.

3. From the Row menu, select Copy Environment to duplicate the environment.

4. Complete the New Environment field, select the Copy *Public Records Only option, and then click OK.

   Use Oracle's JD Edwards EnterpriseOne OCM to modify the mappings of each environment to reflect your enterprise setup and the mapping for the data sources.

Using JD Edwards EnterpriseOne Translation Tools to Create an Environment

Access the Create and Compare and Code Page Environment form.

1. On the Processing Options form, complete these fields:

   • Compare Environment Prefix

   • Release Postfix

2. On the Work With Batch Versions - Available Versions form, select the version that you want to run, and then select Processing Options from the Row menu.

3. On the Processing Options form, complete the Language Environment Path Code field and click OK.

4. On the Work With Batch Versions - Available Versions form, select the version that you want to run, and then click Select.

   On Version Prompting, you can use data selection or data sequencing to further define the version that you are running. The version is set to create all of the environments. You must create the compare environment, but you can use data selection to have the batch process create only those language code page environments that you need.

5. After completing any data selection or sequencing on the Version Prompting form, click Submit.

6. On the Report Output Destination form, select one of these options and click OK:

   • On Screen

   • To Printer

     You have finished creating the base language environments.

7. Use OCM to modify the mappings of each environment to reflect your enterprise setup.

   Note. You must have all of the OCM mappings modified before you run the delta process.

Setting Up User Profiles

Each translator or developer needs to be set up correctly. The translators have additional setup criteria that indicate the language that they use.

Access the Work With User/Role Profiles form.

1. Complete either of these fields and click Find:

   • User/Role

   • Address Number

2. Select a user and click Select.

3. On the User Profile Revisions form, select Translation Pref from the Form menu.

4. On the Translation Preferences form, complete the Language field and click OK.

   You can enter the translator type, but it is not required.

5. On the User Profile Revisions form, enter the language preference for the translator and click OK.

   Some languages require runtime language processing to edit the data.

6. Set up the user profiles for each translator.

Adding User Security

Each data source might require user security. User security acts like a proxy that transforms the current user into another user when accessing the data. User security is generally required for language setup of user profiles. A user profile often contains language information that you need to convert characters between code pages. The wrong user profile can cause data corruption or data source connection problems. User profiles must be set up correctly on each database server and in JD Edwards software to perform user security.

Access the Work With User Security form.

1. Complete the User ID/Role field and click Find.

2. Add all of the necessary data source connections for each user and click OK.

3. Repeat this task for each user ID that accesses the data source's setup.

Copying the Data from a Prior Release

This section provides overviews of data from a prior release, compare environment tables, and control tables for the code page environment, and discusses how to:

• Copy the data from a prior release

• Edit the language master

Understanding Data from a Prior Release

You must copy data from a prior release to the current release. You can perform this process by using database administration tools or by using a series of batch processes defined as table conversions. JD Edwards EnterpriseOne has a series of batch processes for copying the compare environment, and another series of batch processes to copy to the language code page environments. You need to run all of these batch processes.

Note. The connection of the user profile is critical when copying data between code pages. The code page conversion becomes corrupt when users connect to data sources with the wrong user profile.

See Working with Logs.

Understanding Compare Environment Tables

These tables are from the compare environment, which you can access from the Status (Compare Environment) menu (GH7931):

Understanding the Control Tables for the Code Page Environments

This table lists the Code Page environments:

Note. You can copy the F7910 to preserve existing suggestions or you can generate a new table without any data. You should consider the needs of each translation group when you determine the pre-loading of this data.

This table lists the JD Edwards Content Builder compare environments:

Forms Used to Copy the Data from a Prior Release

Copying Data from a Prior Release

Access the Work With Batch Versions - Available Versions form.

Note. The table mappings in Object Configuration Manager should be based on the standard location, except for the tables in the Content Builder compare environment. The tables in the Content Builder compare environment should always be mapped to the compare environment and the code page environments. The naming convention of the environment and data source should be synonymous.

1. Right-click the compare environment or Code Page environment that you want to copy.

2. Select Prompt For, and then click Version.

3. On the Work With Batch Versions - Available Versions form, select the version that you want to run.

4. From the Row menu, select Processing Options.

5. On Processing Options, complete these fields on the Environments tab:

   • From Environment

     Enter the language environment name from the prior software release.

   • To Environment

     Enter the language environment name of the current software release.

6. Select the Conversion Process tab, complete these fields and then click OK:

   • Conversion Program Name

     The system populates this field, but you can overwrite it with the name of any of the language table conversion batch applications.

   • Program Version

     The system populates this field, but you can overwrite it with any of the language table conversion batch application versions, as long as it applies to the conversion program name.

7. On the Work With Batch Versions - Available Versions form, select the version that you want to run, and then click Select.

8. On the Version Prompting form, click Submit.

9. On the Report Output Destination form, select one of these options and click OK:

   • On Screen

   • To Printer

You have finished copying production data from the prior JD Edwards software release to the current release.

Editing the Language Master

The language master is an integral part of the delta process and translation tools. The delta process uses the language master to define which status records are maintained during the change process. To use all of the necessary tools, you also need code page mapping information and other setup information.

Access the Translation Tools Language Master form.

1. Edit the records for the appropriate languages that match the status records in the compare environment.

   Any languages that are missing status records, or any status record without a language master corrupts the database when you run the delta process.

   During the copy, languages should exist from the data for the previous release.

2. Verify and edit the correct record or records for these fields, and then click OK:

   • Code Page

     This value comes from user-defined code table H79/CP.

   • L

   • MS Word Language ID

   • Code Page

     This value is the code page data source.

     Note. Complete all of the preceding tasks before you run the delta process for the first time. You should verify the environments and data sources for accuracy, especially code page conversions for all languages. Ensure that users are able to enter the compare environment and edit changes before running the delta process.

Working with the Delta Process

This section provides an overview of the delta process and translation tables, and discusses how to:

• Add translation tables to the delta process.

• Revise translation tables included in the delta process.

• Run the delta process.

• View the progress of the delta process.

• Use jde.log.

• Track the status of each delta process.

• Use preview functionality.

Understanding the Delta Process and Translation Tables

The delta process is a batch application. These tasks explain how to create the batch version for the delta process (which includes selecting translation tables), run that version, and then debug that version, if necessary.

This task explains how to select the translation tables that you want to include in the delta process. The delta process uses batch versions to group the translation tables. You initially define the batch version in the translation tools; this definition indicates the translation tables that you want to include. You also must add the version to the system using the Batch Versions application.

These translation tables are included in the delta process:

• F0004

• F0005

• F00165

• F0083

• RF7920

• F79750

• F79760

• F83100

• F83110

• F9000

• F9005

• F9006

• F9060

• F9061

• F9062

• F9063

• F91100

• F9202

• F9203

• F98306

Forms Used to Work with the Delta Process

Adding Translation Tables to the Delta Process

Access the Work with Delta Table Inclusions form.

1. Click Add to create a new version, or click Select to edit an existing version.

2. On the Delta Table Inclusion form, edit the appropriate tables to be included as part of each version.

3. Complete these fields and then click OK:

   • Version

     Enter the name of a version (for example, XJDE0001).

     Note. When you create this version using the Batch Versions application, you need to use this name.

   • Delta Source Environment

     Enter the name of the environment from which the delta process reads the source files.

   • Delta Destination Environment

     Enter the name of the environment from which the delta process writes or updates the destination files.

   • Delta Include

     Enter 1 to include the table or 0 (zero) to exclude the table when you run the delta process.

   • Delta Table

     Enter the name of a delta table.

4. On the Work with Delta Table Inclusions form, click Find to view the delta tables that you added.

5. Add the version using the Batch Versions application.

   You must use the same version name in the Translation Tools and in the Batch Versions applications.

   Note. All batch applications working with the delta process use the delta inclusion table information. Data selection for every delta batch application works with the version information that is defined in the delta inclusion application. Depending on the administrator requirements, you can enable or disable all tables. To add the version, see Creating a Batch Version in the Foundation Guide.

Revising Translation Tables Included in the Delta Process

Access the Work with Delta Table Inclusions form.

1. Click Find to view any versions for the delta process.

2. Select the delta table that you want to revise, and then click Select.

3. On the Delta Table Inclusion form, complete the Delta Include field to indicate whether you want to include the delta table the next time that you run the delta process.

   If you exclude a delta table, the delta process does not run over the table. This exclusion does not delete the delta table from the delta process version; it merely disables it. Use the options of the Form menu for Yes and No to quickly change all tables.

4. When you finish including and excluding tables, click OK.

5. On the Work with Delta Table Inclusions form, click Find to view the revision that you made.

6. To delete a delta table, click a delta table row in the detail area, and then click Delete.

Running the Delta Process

This task explains how to verify the delta process processing options and run the delta process. You should verify the processing options first, and then run the version.

Note. You should always run the batch application locally. The Form Design Aid (FDA) and Report Design Aid (RDA) contain binary large objects (BLOB) that can be interpreted only on a Windows client computer.

Standard Procedures for Running the Delta Process

You should complete these procedures when you run the delta process:

1. Send an announcement message that includes the scheduled start date and time and the estimated end date and time.

2. Verify the OCM mapping of the source environment and target environment.

   Incorrect mappings cause database corruption.

3. Verify that the delta administrator is signed into the target environment.

   Translators use this same environment.

4. Use the Universal Table Browser to verify each data source and table.

   Data source connection problems might corrupt the database.

5. Begin the delta process at the scheduled time.

   A delta process might take as long as ten hours when the compare environment has multiple languages.

6. Make a backup copy of the compare environment.

   The delta process does not affect any code page data. The delta process compares only source and destination tables, making appropriate source record changes and updating status records in the compare environment.

Running the Delta Process

Access the Work With Batch Versions - Available Versions form.

1. In the detail area, click the version that you want to run, and then select Processing Options from the Row menu.

2. On Processing Options, verify the information in these fields and then click OK:

   • Delta Source Environment

     Enter the name of the environment to override where the delta process reads the source files.

   • Delta Destination Environment

     Enter the name of the environment to override where the delta process writes or updates the destination files.

   • Maximum Cache Size

     Enter the maximum size, in megabytes, for source and destination caches. If the maximum cache size is reached, the delta process stops.

   • Maximum Consecutive Errors

     Enter the maximum number of consecutive errors that you want the delta process to allow before the process stops. For example, you can have the delta process stop automatically if it processes five errors in a row. However, if five or more errors occur during the process, but they are not consecutive, the delta process continues.

   • Compare Source and Destination records

     If the delta source and destination records reside on different types of computers, enter 1 in this field to disable the caching capability of the delta process. For example, if the source records reside on an AS/400 and the destination records reside on an HP9000, enter 1 in this field. If you do not disable the caching, the respective caches fill to their maximum cache size, and the delta process stops.

     If the source and destination records reside on the same type of computer, such as AS/400s, leave this field blank to enable caching, which results in faster performance of the delta process.

3. On the Work With Batch Versions - Available Versions form, in the detail area, select the version that you want to run, and then click Select.

4. On the Version Prompting form, click Submit.

   If the Processing Options form prompts for editing, click OK; the system displays the Report Output Destination form.

5. On the Report Output Destination form, click one of these options, and then click OK:

   • On Screen

   • To Printer

     The delta process runs, comparing the source and destination files and identifying any differences between them. The report lists these changes.

6. At the end of the delta process, the system runs a secondary synchronized batch process, the System Code Status Record Update program (R79803).

   The System Code Status Record Update program updates product or system code information in the status records. The tables containing this information must be mapped to the correct source environment.

   The system code tables include:

   • F9001

   • F9200

   • F9860

     Note. You can run the System Code Status Record Update program at any time. It is not a task menu item. To run it, the delta administrator must start the Batch Versions program by entering BV in the Fast Path, entering the batch application number (R79803), selecting a version, and launching it. The table selection works with the delta inclusion application information.

Viewing the Progress of the Delta Process

This task explains how to view the progress of the delta process, which includes the status of the process.

Access the Work with Delta Table Inclusions form.

1. Click Find to view any versions for the delta process.

2. Review the Status Description field for these status messages:

   • Unknown Error

     Indicates that the delta process has stopped running.

   • Fatal Error

     Indicates that the delta process has stopped running.

   • Minor Error

     Indicates that the delta process has stopped running because the number of errors that occurred consecutively matches or exceeds the value that you entered in the processing option for the maximum number of consecutive errors.

   • Processing

     Indicates that the delta process is still running. This status message continually updates during the delta process.

   • Complete Success

     Indicates that the delta process completed successfully.

     Note. With a successful backup copy, users can enter the compare environment to continue working. It is better to have no users in the system, and the translation tools application limits access to data based on the current status of the delta process. In the event of data corruption, the data should be restored from the backup copy.

Using jde.log

Use the jde.log file to follow the progress of the delta process and to identify errors that might have occurred. JD Edwards software automatically uses the jde.log file to track the progress and any errors of the delta process; no setup is required. While the delta process is running, you can access the jde.log file to view the progress.

When viewing the jde.log file, locate any delta process information by searching for the word delta or for the B7900022 business function.

The delta keeps a one-to-many relationship between the source records and status records. The language master defines the one-to-many relationship. Any time that a status record is missing, the delta attempts to insert all records. An insert failure might inadvertently result from keeping the one-to-many relationship.

Using jdedebug.log

Use the jdedebug.log file to identify process errors that might occur during the delta process. You need to set up jdedebug.log by using the jde.ini file if you want to use the log file for debugging the delta process.

Tracking the Status of Each Delta Process

This task explains how to report the changes for each delta process. The delta inclusion saves the last historical information by default. You can export this information from the detail area for reporting purposes.

If you need more historical information, you can run the Translation Compare Status report (R79810) for statistics. You should run this report at the completion of every delta process. The report displays the total changes over the compare environment. You can use the report to analyze delta problems and concerns that you might have after you run the Delta Purge and Rebuild Process program (R79801).

Access the Work With Batch Versions - Available Versions form.

1. In the detail area, select the version that matches the table selection for the delta inclusion version, and click Select.

2. On the Version Prompting form, click Submit.

3. On Processing Options, enter the language selection to limit the size of the report and click OK.

   When the language selection is blank (the default value), all languages in the compare environment print on the report.

Using Preview Functionality

Many of the translation tools have a preview feature that is built into the application. The preview feature uses local specifications to retrieve current source and target text changes to preview the current delta changes.

You must download specifications to each client machine before processing the preview functionality. The delta process keeps the compare environment synchronized with the objects in a path code, but the delta does not update local machine specifications. Translation Tools has implemented the Advanced Get feature from Object Management Workbench (OMW) to perform previews.

If the items have changed, Translation Tools automatically retrieves the specifications based on untranslated status items.

Access the Work with Delta Table Inclusions form.

1. Select Constants from the Form menu to edit the necessary information for the preview feature.

2. On the Delta Constants form, complete these fields:

   • Path Code

     OMW activity rules must be set up to access the objects in this path code.

   • Release

     Enter the current release that matches your path code.

3. Select any of these options, and then click OK:

   • Forms Design Aid (FDA)

   • Report Design Aid (RDA)

   • Processing Options (PO)

   • Data Dictionary (DD)

     Note. The options are disabled until you enter a path code and release.

Working with Delta Process Advanced Options

This section provides an overview of delta process advanced options, and discusses how to:

• Purge and rebuild delta tables.

• Fix status record problems.

• Use Content Builder batch applications.

• Create non-BLOB FDA specifications.

• Update FDA and RDA tables with translated text.

Understanding Delta Process Advanced Options

The environments and database contain a large set of data that could become corrupt. The delta process includes a suite of batch applications to help keep the compare and code page environments intact.

Forms Used to Work with Delta Process Advanced Options

Purging and Rebuilding Delta Tables

When the compare and code page environments are out of synchronization, use the Delta Purge and Rebuild Process (R79801) to identify and fix problems. You should rebuild at the beginning of the translation lifecycle, but purge before mastering the software.

The purge process deletes these types of records:

• Status and language records that are marked for deletion (status = 99).

• Language records that do not have a corresponding status record.

  This means that the language record is extraneous because, without a corresponding status record, it does not match any of the English records. The translation record has become an orphan.

• All untranslated language records (status = 20).

  This removes bad translations. Untranslated text is a better result than a bad translation.

The rebuild process performs these tasks:

• Checks certain status records for missing translation records or untranslated text.

• Compares all status records that are complete (status = 11) for matching language records.

• Changes the status of the corresponding status record to either untranslated (status = 20) or new item (status = 40) for each language record that meets these conditions:

  • Record does not exist.

  • Record is blank.

  • Record contains English (you need to set a processing option for this function).

Access the Work With Batch Versions - Available Versions form.

1. Select the Purge and Rebuild version in the detail area and then select Processing Options from the Row menu.

2. On the Processing Options form, complete these fields on the Process tab and click OK:

   • Language

     Enter the language code, such as W for Swedish, for the language records that you want to purge and rebuild.

   • Translation Compare Environment

     Enter the compare environment or leave this processing option blank to use the default compare environment. The wrong compare environment can cause corruption in the database.

   • Code Page Environment

     Enter the language code page environment or leave this processing option blank to use the default code page environment. The wrong code page environment can cause corruption in the database.

   • Purge

     Leave this processing option blank to run the purge process. Enter 1 in this processing option to prevent the purge process from running.

   • Rebuild

     Leave this processing option blank to run the rebuild process. Enter 1 in this processing option to prevent the rebuild process from running.

   • Duplicate English

     Enter 1 in this processing option to run a process that checks language records for any source English that also appears in the source English records. Any duplicate source English changes the corresponding status record to untranslated (status = 20). Generally, translation memory problems cause English text to appear in translated software, and this process can reset the status appropriately.

3. On the Work With Batch Versions - Available Versions form, in the detail area, select the version that you want to run, and then click Select.

   The data selection is defined by the delta inclusion application.

   If the Processing Options form prompts for editing, click OK; the system displays the Report Output Destination form.

4. Select one of these options, and then click OK:

   • On Screen

   • To Printer

     The batch process runs.

     Note. The purge and rebuild process also rebuilds information in the code page records. Tables such as F0005D, F7920, and F98306 contain information from the source records. This process fixes translation or mastering issues.

Fixing Status Record Problems

Sometimes, status records are not updated appropriately. These records are often missing the English source and have become orphaned. You can run the Check Status with Text Records program (R79802) to fix these problems. This process runs in the compare environment and works with all language status records that are missing a source record.

Access the Work With Batch Versions - Available Versions form. :

1. Select the version in the detail area and select Processing Options from the Row menu.

2. On the Processing Options form, complete these processing options and click OK:

   • Update Delete Status Records

     The report displays the totals for the records that will be purged from the system.

   • Delete Status

3. On the Work With Batch Versions - Available Versions form, in the detail area select the version that you want to run, and then click Select.

   The data selection is defined by the delta inclusion application.

   If the Processing Options form prompts for editing, click OK; the system displays the Report Output Destination form.

4. Select one of these options and click OK:

   • On Screen

   • To Printer

     The batch process runs.

Using Content Builder Batch Applications

Content Builder uses the delta process to track English source changes. The changes can then be edited by developers into a code page or workspace database. A tool in Content Builder enables developers to access the data dictionary to edit the delta glossary items. These edits eventually need to be synchronized with the pristine database for the purposes of translating and mastering the software.

From the Work With Delta menu (GH7941), select Delta Data Synch.

1. On the Processing Options form, complete these processing options and click OK:

   • Compare Data Source

     This data source contains the status records and the compare source English.

   • Code Page Data Source

     This data source contains the edits that the developers entered, and which need to be updated in the compare and destination data sources.

   • Destination Data Source

     This data source contains the current pristine set of data for the current release of the data dictionary.

   • Synch by Status

     This option selects the status records to update, so that only edited items are replaced.

   • Update Compare Status

     This option updates the status, so that the same records are not continually updated with this process.

2. On the Report Output Destination form, select one of these options and click OK:

   • On Screen

   • To Printer

     The batch process runs.

When Content Builder is not using the delta process to track changes, a set of non-Binary Large Object Form Design Aid (non-BLOB FDA) data is required to use the token integration tool. The non-BLOB data can be generated from the BLOB specifications to enable edits when using token integration in Content Builder.

Creating Non-BLOB FDA specifications

Access the FDA Spec Conversion.

1. On the Processing Options form, complete these processing options and click OK:

   • FDA Spec Source Environment

     This environment contains the path code information of the current FDA BLOB specifications.

   • FDA Data Destination Environment

     This environment contains the mapping to the compare environment.

   • Maximum Consecutive Errors

   • From Range - Interactive Application Name

     To limit the size of the non-BLOB specification data, enter a starting application such as Business Unit Master (P0006).

   • Through Range - Interactive Application Name

     To limit the size of the non-BLOB specification data, enter an ending application such as Purchase Order Entry (P4310).

2. On the Report Output Destination form, select one of these options and click OK:

   • On Screen

   • To Printer

     The batch process runs and creates the data that is necessary to use the token integration tool for Content Builder.

Updating FDA and RDA Tables with Translated Text

This task explains how to update FDA and RDA tables with translated text. JD Edwards software stores FDA and RDA tables in the BLOB format. The delta process converts the FDA and RDA text into Unicode, ASCII, or Extended Binary Coded Decimal Interchange Code (EBCIDIC), depending on your system. After translation is complete and before language mastering, the mastering administrator needs to run the batch processes to convert the translation text back into the BLOB format for use within JD Edwards software.

The UBE for FDA is R798750 and the UBE for RDA is R798760.

Access the Work With Batch Versions - Available Versions form.

1. Select the version in the detail area and then select Processing Options from the Row menu.

2. On the Processing Options form, complete these processing options and click OK:

   • Translation's Code Page Environment

   • Master's Code Page Environment

   • Language Selection

     Enter the language code, such as W for Swedish, for the language records that you want to purge and rebuild.

3. On the Work With Batch Versions - Available Versions form, select the version in the detail area, and then click Select.

4. On the Version Prompting form, click Submit.

   If the Processing Options form prompts for editing, click OK; the system displays the Report Output Destination form.

5. Select one of these options and click OK:

   • On Screen

   • To Printer

     The batch process runs.

6. Return to the Language Mastering Administration menu, and select RDA Blob Update.

Code Page Character Sets

Translation text exists in many forms of character code pages. Some of these code pages include Unicode, ASCII, or EBCIDIC, depending on your system. Unicode has different encoding sets, such as UTF-16, UTF-8, USB-2, and so on. Unicode character code pages are often converted to either ASCII or EBCIDIC code pages for processing on different platforms.

This table displays the character sets for ASCII character code pages: