Subtoken Delimiter Sets in Run-Time Error Messages

When an action error occurs at run time, often the original text from the database (as opposed to the generated substitution text) is displayed. This text can contain any of the substitution type and subtext substitution features. Normally, these substitution sequences appear on the console and in the console log exactly as they are specified in the CP-AMS database except for a subtext substitution delimiter set.

A subtext delimiter set is specified within braces ({ }) within a substitution sequence in action text. Braces, however, are not accepted by the host as input characters. Instead, the console automatically converts braces to brackets ([ ]) before sending them to the host.

For example, assume that the following subtext substitution delimiter set, which extracts the second subtoken from the first message token, is specified in a highlight action:

\_TOKEN1 {-} 2\

If the first message token does not contain a hyphen (-), a run-time error occurs because a second subtoken does not exist. The following messages are generated:

LG $AMS-ERR $ SUB-TOKEN SUBSTITUTION OUT OF RANGE
LG $AMS-HILT$ \_TOKEN1 [-] 2\

Note the braces in the second message are automatically converted to brackets. This change occurs only in the LG command sent to the host and does not affect the action in the database.