Guidelines for Validating the Message Structure

When validating an MT message structure, the following guidelines are used:

  • The fields of all required basic and application headers have the correct length.
  • The basic header and service identifiers are valid.
  • Application input and output indicators are valid.
  • Application input delivery monitoring and obsolescence cannot be displayed in the message unless the priority is displayed.
  • Application input obsolescence cannot be displayed in the message unless the delivery monitoring is displayed.
  • The user header is displayed if required.
  • Message types requiring a user header field validation tag 119 have such a tag.
  • No duplicate user header or trailer tags are found.
  • No invalid user header, trailer, or system acknowledgment tags are found.
  • The lengths of all user header, trailer, and system acknowledgment tag values are correct.
  • Message types requiring user header field validation tags to select correct message metadata (types 102, 103, and 574) have validation tags with valid values.
  • All mandatory text block sequences and fields are displayed in the message.
  • The text block contains no invalid fields.