This describes the header and trailer records used to route nonstandard data.
Header Syntax
#‹format-id› FROM ‹orig-id› TO ‹dest-id› ‹date› ‹time› ‹ctrl-number›
Where:
‹format-id › is an optional 4 to 20 character alphanumeric string identifying the data format being transmitted.
‹orig-id› is a mandatory 4 to 20 character alphanumeric string identifying the sender of the data.
‹dest-id› is a mandatory 4 to 20 character alphanumeric string identifying the receiver of the data.
‹date› is an optional date of transmission of the data (YYMMDD).
‹time› is an optional time of transmission of the data (HHMM).
‹ctrl-number› is an optional 1 to 9 digit number (incremented each transmission) used as a control for tracking transmissions.
Note:
If ‹date› and ‹time› are excluded then the date and time of receipt are assumed.
If ‹ctrl-number› is excluded then a sequential number is assigned upon receipt. This number is kept on file and incremented on each incoming transmission.
Trailer Syntax
#EOT ‹ctrl-number› ‹record-count›
Where:
‹ctrl-number› — is an optional 1 to 9 digit number matching the control number in the header record. It is used to match headers to trailers.
‹record-count› — is an optional 1 to 5 digit count of the data records between the header and trailer. This count does not include the header and trailer.
Header and Trailer Examples
#MY-FORMAT FROM COMPANY‑A TO COMPANY‑B 980923 1800 1
‹data record 1›
‹data record 2›
#EOT 1 2
#SHIPMENTS FROM 8005551212 TO 9996661313
‹data record 1›
‹data record 2›
‹data record 3›
#EOT
#PODATA FROM WIDGET TO 88123456333 981030 1234 00123
‹data record 1›
‹data record 2›
‹data record 3›
#EOT 00123 00003