Legacy Text Examples - Error Messages (ER)
This section provides the Legacy format for Nlets generated Error Messages (ER).
Note: The Nlets system (ORI NL0000000) is the only originator of ER messages.
Neither state computer systems nor terminals may generate ER messages.
Nlets Error Message Specifications
Each Nlets error message will contain:
Standard output header.
A numeric and plain English error notification.
The first 100 characters of the input message.
The sending ORI will always be NL0000000.
(This the ORI assigned to the Nlets message-switching computer.)
Message Formats
The detailed message format for error messages is presented below.
Entry
Field Size
Explanation
ER.
2
Message type followed by a period.
Message Header
69-76
Standard output message header, may include
control field.
Error message
Varies
Message explaining the problem with a 2-digit
error number at the beginning.
CR,LF,DEL
3
Control characters
Message text
100
The first 100 characters of the message to which
this error message pertains.
Nlets Error Legacy Examples
Example 1: Error message sent on a Vehicle Registration query.
ER.NL0000000
08:00 01/01/2010 01239
08:00 01/01/2011 01233 AZNLETS20
TXT
.22. INVALID MESSAGE FORMAT - REFER TO RQ MKE OPTIONS BELOW
1. LIC, LIY, LIT
ORIGINAL MESSAGE
RQ.AZNLETS20.AZ.TXT
LIC/123456.LIT/PC
Example 2: Error message sent on a Hit Confirmation query.
ER.NL0000000
08:00 01/01/2010 01231
08:00 01/01/2010 01235 AZNLETS20
TXT
.22. INVALID MESSAGE FORMAT - REFER TO YQ MKE OPTIONS BELOW
1. RTY, RNO, PRI, OCA, NIC, TYP, SER, RNA, RAG
ORIGINAL MESSAGE
YQ.AZNLETS20.AZ0000000.TXT
RTY/SS.PRI/R.OCA/10000000000.NIC/A111110000.
SER/110011001100.DEN/123456789.
RNA/NLETS_ANALYST.RAG/NLETS.PHO/8005284020.
REM/PLS CONFIRM STILL STOLEN.