During the migration of an EAE 3.3 application to AB Suite, any embedded MCP control characters present in the model will be eliminated. These control characters are eliminated because, the control characters can cause issues in the migrated application and can result in the failure of the AB Suite build.
The following table lists the characters that are removed from the model by migration:
| ASCII Control Character Name | Description |
|---|---|
| 0F SI | Underline |
| 17 ETB | Stop (terminator) |
| OE SO | Reverse |
| 1A SUB | Bright |
| 18 CAN | Blink |
| 1E RS | Right delimiter |
| 7F DEL | Delete |
If your application is dependent on the presence of these control characters, you must replace them before you migrate from EAE to AB Suite. You can replace the control character using one of two methods:
If the control character precedes a single label or field, or a series of labels and fields on a single line, remove the control character, and for all the labels and fields that follow the control character, set a display attribute that matches the effect of that control character. For example, if the control character causes the following labels and fields to be reversed, remove the control character and set the 'Reverse' display attribute on them.
If the control character does not precede any specific label or field, or is included in an insertable global logic, remove the control character and replace it with a data item that has a length of 1 and is edit A. In logic, move the appropriate hex string to the data item.
For example, use the following syntax to move the Reverse control character to a data item.
Move; (@0E@) SD-CC
Refer to the following table for EBCDIC hex strings:
| EBCDIC Control Character Name | Description |
|---|---|
| 0F SI | Underline |
| 26 ETB | Stop (terminator) |
| 0E SO | Reverse |
| 3F SUB | Bright |
| 18 CAN | Blink |