Normalized Record Formats

Normalized record formats exist for several different ICL record types.
  • File header and control records (types 01 and 99)
  • Cash letter header and control records (types 10 and 90)
  • Bundle header and control records (types 20 and 70)
  • Batch (ICL) records (types 101 and 199)
  • Transaction records (types 102 and 103)
  • Item records (types 25, 31, 61, 112, 113, and 244)
  • Addenda records:
    • Endorsement records (types 26, 27, 28, 32, 33, 35 and 35)
    • Image view records (types 50 and 52)
    • Image test records (types 54, 55, and 56)
    • Other addenda records (type 68)
A nonspecific normalized record format exists for other ICL record types.
  • Other records (types 40, 41, 64, 68, 75, and 85)
The data sent in the transmission file and stored in the FTM database includes the normalized portion and the original record. The normalized portion has four common fields and additional type specific fields.
Table 1. Normalized Records Format
Common fields Additional type specific fields
Length of entire record Record type Data Format Offset of original record Additional type specific fields Original record data

Common Fields

Listed below are the common fields.
Length of entire record
The length of the entire record is specified to facilitate breaking a stream of these records up into individual records. The length value is a 4-byte integer indicating the size in bytes of this entire record, including the length field, in big endian format.
Record type
An 8 character identifier that identifies the type of this record. These ANSI records have a record type of NIFL_0nn, where nn is a two-character record type.
Data format
The data format is a 2-character identifier showing the format of the original record data. It can be one of the following values shown in Table 2.
Table 2. Data format identifiers
Value Description
03 DSTU x9.37-2003
13 SVPCo x9.37-2003 Post Pilot Companion Document
20 ANS x9.100-180-2006
90 CIFF
Offset of original record
The offset of original record is a 4 digit number of bytes into this record where the original record data begins. The field allows reading software to tolerate extensions. The correct way to step past the normalized portion of the record to access the original record data is to use the length field from the record.

The remaining normalized data contains type specific fields with IBM® specified values. The field values are populated based on the original record data. In some cases, such as file header and file control records, a second record is also used to populate the fields.

The original record data is included largely in its original form. Records destined for the Transaction Server are converted to ASCII as needed. Images are stripped from the image view records.