The example illustrated in this appendix is a format definition for decoding a shortened version of EWSD AMA (Automatic Message Accounting).
...
A schematic representation of the example discussed in this section
external
Since the last three optional fields (including RecordOwnerType and RecordOwnerDN) consist of several fields, each one will be is defined as its own type. That is, an external sequential format.
...
An alternative to use the set construct, in the external definition for AMARecord_ext, switched_set could be used. This will impact impacts the syntax for the Package_*_EXT types. Only the syntax differing from the original example is shown. The main reason for using switched_set instead of set is when performance must be increased.
...
| Note | ||
|---|---|---|
| ||
No |
internal
No internal is is used. In this case, the target_internal is is sufficient; all field names and field types are in order and there is only one type of record present in the input, and no additional fields are required.
...
The padding in the records is recognized by the decoder, however it is not actually mapped in to the system due to the use of the discard_output flagflag.
The AMARecord_Map contains sub-automatic specifications (the target_internal specifications within the automatic block), which will give five additional internal formats (other than the AMARecord). This is useful when you want to route them as individual records.
...
| Code Block |
|---|
decoder AMAFile : in_map( AMARecord_Map ),
in_map( FillerRecord_0x00_Map ); |
...