Nlynx ETU400 - Manual (Page 101)

ETU400 User Guide 011603 8-7
For example, the table above indicates that a translation table can
contain a maximum of 20 “From” entries with a string length of 6 bytes.
The xxx markers indicate that the length is not supported for that type
of translation. Normally, all translation types will use only the single
character translation.
TO HEX From zero to nine characters (depending again on the type of
file translation) expressed in hexadecimal. Upon finding the
corresponding FROM HEX, the TO HEX characters are written to the output
data.
Translate Before/After
Determines when the translation is performed relative to performing
control action. (This field is labeled XBA on the compiler report.) B
specifies translate before control, and A specifies translate after
control. The default is B. Typically this is used to force padding and
end-of-record processing when a CR/LF sequence is found in a TO3XB
translation. An example of the source statement for this is:
FROM HEX XBA EOR Comment
0D0A B Y If CR/LF then pad and write
Pad Character
Contains the value B for blank (hex 40), or N for null (hex 00), or a
hexadecimal representation of a selected pad character. If a pad
character is not specified, and the utility needs to pad a record, the
character specified in the *TRAIL statement will be used. If that
statement is not used, padding is done with blanks.
End-of-Record Action
Marks the end of the current record being translated upon detection of
the FROM HEX characters (used in FROMPC or TO3XB translation). It can be
either Y or a value encoded *1 through *9.
“Y” specifies that the record currently being translated will be written,
with padding performed as specified. The specifications *1 through *9
allow the concatenation of additional TO HEX characters. For example:
FROM HEX EOR Comment
0D0A Y If CR/LF, write record
Another example, writing AAAB before padding with nulls:
FROM HEX TO HEX EOR Comment
0D0A *1 If CR/LF
*1 C1C1C1C2 Then write AAAB