VisualAge Generator to Enterprise Generation Language Migration Guide

Fill characters for shared data items

VisualAge Generator: The default fill character for map edits is null for character, mixed or DBCS; blank for numerics; and 0 for hex. The default fill character for UI edits is blank for character, mixed, DBCS, unicode, and numerics; and 0 for hex. Null is not a valid fill character for UI records. A different fill character can be specified for map edits and UI edits.

EGL: There is only one default fillCharacter property for a data item. Even though UI records are not supported in this release of EGL, the migration tool merges the map and UI fillCharacter properties for the data items. This preserves as much of your data item information as possible.

Associated part needed for migration: Not applicable.

Figure 12. Fill characters for shared data items

Migrating with the associated part Migrating without the associated part

The first time the shared data item is migrated, the migration tool does the first of the following that applies:

  • If the UI edits specify a fill character, the migration tool migrates the character to the EGL fillCharacter property.
  • If the map edits specify a fill character, the migration tool migrates the character to the EGL fillCharacter property.
  • If neither the UI edits nor the map edits specify a fill character, the migration tool does not set the EGL fillCharacter property.

The migration tool does the same thing as mentioned in the Migrating with the associated part column.

Potential Problem: A problem only arises if you add a data item that was migrated using one type of edits to a different type of user interface (form or user interface record).

Possible Solution: Always review the fill character when adding a new item to a form or user interface record.

The same problem listed under the Migrating with the associated part column can occur. You can use the same solution.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]