Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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_extswitched_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
titleNote!

No  identified_by  or PackageNumber is present, since this is handled in the containing  switched_set .

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.

...