Section 10: Random Access to Nlets Data (RAND)

From Nlets Wiki
Jump to: navigation, search

Random Access to Nlets Data (RAND) (NLQ/NLR & NFQ/NFR)

Nlets manages a log of message traffic that travels through it. The RAND functionality provides authorized users with access to this traffic log. This section describes the queries (NLQ/NFQ)and the corresponding responses (NLR/NFR).

RAND Query/Response Transactions

Messages are entered in the log as they leave the Nlets switch. Messages intended for Nlets itself such as ORION messages, are recorded on arrival and any generated response messages are also recorded. Embedded images in messages are not recorded into RAND. Receipt and routing of ANSI/NIST messages such as rap sheets or fingerprint sets are logged but no message content is saved in RAND. Additionally, some queries of the RAND log data itself may not be available in a RAND response. For special circumstances requiring that information, please contact the Nlets Help Desk.

Overview

There are two RAND query transactions: NLQ and NFQ. NLQ is used to search the RAND database and produces a hit list in an NLR message format. Information from the NLR message is used to format an NFQ message to retrieve the full text of a message.

Messages can be retrieved by message type, time range, originator, member and by character string within a message.

Note: The messages are recorded in Mountain Standard Time (UTC/GMT -7 hours).

Section10-RAND.jpg

If no messages match the specified search criteria, the response may be "NOT ON FILE".

NLQ Rules

NLQ messages follow these rules:

The type (TYP), beginning (BEG) and end (END) fields are mandatory.
At least one "free text information needed" (FND) or name (NAM) field must be entered.
"Free text information needed" (FND) and name (NAM) fields cannot both be present.
Either "Additional free text" (AND) or "Alternative free text" (ORR) fields may be entered if FND is present.
"Additional free text" (AND) and "Alternative free text" (ORR) fields cannot be used in the same message.
If a type field (TYP) is specified for which the requester is not authorized, then the response message will
include a warning that the user is not authorized to retrieve that message type.
The request must contain at least one authorized message type.

Fields need not be padded to any particular size. They will all be trimmed of leading or trailing spaces before use.

Search Options

When the search string is intended to match the proper names of people rather than general text, the name field (NAM) may be used in place of these combinations:

"Free text information needed" (FND) and "Additional free text" (AND)

OR in place of these combinations:

"Free text information needed" (FND) and "Alternative free text" (ORR)

The RAND query process allows users to leverage certain simple SQL syntax within the FND (n:InquiryText) field in order to make their searches more sophisticated. Below is mere information on the syntax which may be used within the FND field:

Enter a "contains" SQL-style search. Includes words and "phrases in double-quotes" separated by AND,
OR and NEAR. Each word or phrase may include alphanumeric characters, a dash (-), an underscore (_),
apostrophe and the "*" wildcard character. Any words or phrases containing a wildcard should be in
double-quotes, and the wildcard character should be at the end. Parenthesis ( ) are allowed for grouping.

RAND searching is creating one large CONTAINS SQL statement from all of the parameters passed in, and
then adding on the FND field as-is, so it is sensitive to formatting. SQL Server doesn't like it when you
have 2 words without an operator between them, unless they are in quotes. So for example, this would
return an error:

buick phoenix

But this would work, requiring both words to be anywhere in the message to match:

buick and phoenix

This will let you search for an exact phrase:

"buick phoenix"

which would require "buick phoenix" to appear exactly as shown. You can also use OR or NEAR instead of
AND. OR will match either word, and NEAR will require them both to be near each other in the message.
NEAR is what is used for the NAME search, so if you just want to find a series of words that are near
each other, the NAM field would work well for that.

This will require both words to be near each other in the message to match:

buick near phoenix

This will match with either word:

buick or phoenix

You can also do wildcards at the end of words, so if you didn't know how to spell phoenix, you could do this:

buick and "ph*"

Wildcards require quotes, and need to be at the end of a word only.

Parenthesis allow logical grouping, useful when a combination of operators might give confusing results.
For example, if you wanted to search for a buick in either phoenix or tucson, you could search on:

buick and (phoenix or tucson)

Error Messages: If SQL Server doesn't understand the syntax, the user will get a error returned from SQL
Server. For the first buick phoenix example, you'd see something like this:

Syntax error near 'phoenix' in the full-text search condition 'buick phoenix'.

But the message could be anything, depending on what was typed in.

Special rules are used for name based searches compared to general free text searches. These rules are listed below.

Rules for Name Based Searches:

Each name entry (NAM) accepts name components separated by spaces, commas, hyphens or other
non-alphanumeric characters.

Name strings (NAM) may contain the asterisk ("*") in any position after the first character of an
alphanumeric name to indicate a match to any character string following the leading portion.
For example, "JOHN SM*" would indicate a match for a last name beginning with "SM" but ending
with any sequence.

The search process ignores non-alphanumeric characters in each message when comparing for
a match.
If a search was issued for "JOHN SMITH" and a message contained "JOHN@SMITH", a match would be
returned.

Order of name components is not important.
For example, a search on "JOHN SMITH" would match "SMITH JOHN" and also "SMITH, JOHN".

Name (NAM) based searches are not confined to message text beginning with NAM/ but searches for names appearing anywhere in the message.

Authorized users may query criminal history messages. Only header information will be returned to protect the confidentiality of the criminal history data.

NLQ Query Field Requirements

The standard Nlets message header and the fields below are required for NLQ queries.

XML Tag: Legacy
Prefix:
Field
Size:
Data Requirements: Translation:
<n2:RequestCategoryText>
TYP/ 100

2 or 3 character
message type

Message types
of interest.

<nc:IdentificationID>
SRC/ 2 or 9

Two character
member code or a
full 9 character ORI

Source member or ORI.

<nc:IdentificationID>
DST/ 2 or 9

Two character
member code or a
full 9 character ORI

Destination
member or ORI.

<n2:MessageSendDateTimeMinimumText>
BEG/ 8 or 13

ccyy-mm-dd or
ccyy-mm-dd@hhmm

Beginning date
and optional time
for the query.

<n2:MessageSendDateTimeMaximumText>
END/ 8 or 13

ccyy-mm-dd or
ccyy-mm-dd@hhmm

Ending date and
optional time for
the query.

<n2:InquiryDescriptionText>
FND/ 250

Most characters in
this field represent
themselves. The
field can, however,
contain several
characters with
special meanings:

A character
string containing
text to search for.

<nc:PersonName>
  <nc:PersonFullName>
</nc:PersonName>
NAM/ 250

The format of this
string is the same
as that for the FND
field except that the
field can contain
only alphanumeric
characters or the "*"
wildcard character.

A character
string containing
a name string to
search for.

Responses

Response requirements are described below:

  • Output begins with the date on a line by itself. A series of lines follow, each starting with a time and continuing with the member the message was sent to (or received from), the sequence number of the message, the originator ORI, the message type, the destination ORI, and up to 40 characters of message data beginning with the first point in the message where any term matched.
  • If the results cover more than one date, the next date is then printed and followed by the search hits for that day.
  • There is a limit of 100 hits for a given NLR.
  • If more than 100 hits are necessary, the time and date of the last hit can be used as the beginning field date of a subsequent query where all other fields are as they were in the original NLQ.
  • It is important to remember that RAND contains outgoing messages only (with the exception of transactions processed by Nlets itself).
  • RAND returns only those messages the requesting ORI is authorized to receive. If the requesting ORI is not authorized for criminal history information, for example, those message types are not retrieved. Two ORIs with different authorizations may receive different responses to the same RAND inquiry.
  • If there are no messages in RAND that match the specified search criteria, a response to this effect is returned.

NFQ Query Field Requirements

The standard Nlets message header and all of the fields below are required to retrieve a message. The message sequence field (MSG) may repeat to retrieve more than one message for the given member and date. All retrieved messages in a single NFQ must be for the same date since the date field (DAT) cannot be repeated.

XML Tag: Legacy
Prefix:
Field
Size:
Data
Requirements:
Translation:
<n2:MessageSendDateTimeMinimumText>
DAT/ 100

ccyy-mm-dd

Date of message
or messages to
retrieve.

<nc:IdentificationID>
MEM/ 2

LOC from NLR.

First two
characters of ORI
from NLQ/NLR.

<nc:IdentificationID>
MSG/ 45

Alphanumeric

Message sequence
number as shown
in the NLR message.

Authorized users may query criminal history messages, although only header information will be returned.

RAND Error Messages

Error messages (ER) are returned in response to NLQ or NFQ messages in the following circumstances:

Message
Number:
Message: Explanation:
.60.

"xxx" FIELD INVALID OR MISSING

Indicates one of the RAND inquiry
fields was missing or invalid; where
"xxx" is the field prefix.

.61.

ORI NOT AUTHORIZED TO RETRIEVE MESSAGE

Indicates the ORI attempted to
retrieve a particular message, that the
ORI is not authorized to receive.

Top

GJXDM (DEPRECATED)

GJXDM has been deprecated. Please contact Nlets for additional assistance with GJXDM.

Top

NIEM

Random Access to Nlets Data NIEM Specifications

This section describes the format and provides examples for queries (NLQ/NFQ) to the Nlets message log of traffic that travels through it and the corresponding responses (NLR).

Messages can be retrieved by message type, time range, originator, member and by character string within a message.

Queries to the Nlets message log follow these rules:

  • The type, beginning and end fields are mandatory.
  • At least one free text or name-based string field must be entered.
  • Free text and name-based string fields cannot both be present.
  • Either additional free text or alternative free text fields may be entered if free text is present.
  • Additional free text and alternative free text fields cannot be used in the same message.
  • The name-based string field can repeat in a transaction.
  • If a type field is specified for which the requestor is not authorized, then the response message will include a warning that the user is not authorized to retrieve that message type. The request must contain at least one authorized message type.
  • Fields need not be padded to any particular size. They will all be trimmed of leading or trailing spaces before use.

The name-based string field may be used in place of free text and additional free text combinations or free text and alternative free text combinations when the search string is intended to match the proper names of people rather than general text.

One or more name-based string fields may be entered, and these are considered alternatives (similar to free text and alternative free text combinations).

Special rules are used for name-based searches compared to general free text searches. These rules are listed below.

  • Each name entry (name-based string) accepts name components separated by spaces, commas, hyphens or other non-alphanumeric characters.
  • Name strings may contain the asterisk ("*") in any position after the first character of an alphanumeric name to indicate a match to any character string following the leading portion.
  • The search process ignores non-alphanumeric characters in each message when comparing for a match.
  • Order of name components is not important.
  • Name based searches are not confined to message text beginning with
    <nc:PersonName>
    
    but searches for names appearing anywhere in the message.

An automated response from the Nlets system will be returned advising that the query (NLQ) was successfully received and placed in the queue for processing. Once processing is complete, the response (NLR) will be returned. Within the

<nc:ResponseText>

element,

  • Output begins with the date on a line by itself.
  • A series of lines follow, each starting with a time and continuing with the member the message was sent to (or received from), the sequence number of the message, the originator ORI, the message type, the destination ORI, and up to 40 characters of message data beginning with the first point in the message where any search term matched.
  • If the results cover more than one date, the next date is printed and followed by the search hits for that day.
  • There is a limit of 100 hits for a given NLR. If more than 100 hits are necessary, the time and date of the last hit can be used as the beginning date field of a subsequent query where all other fields are as they were in the original NLQ.

The full text message query (NFQ) is based on the message log response (NLR) message generated by a message log query (NLQ) transaction.

  • The message sequence field may repeat to retrieve more than one message for the given member and date.
  • All retrieved messages in a single NFQ must be for the same date since the date field cannot be repeated.

All Nlets NIEM messages must be based on the Nlets NIEM Message Structure and include the standard Nlets XML Header as detailed in Message Structure. The NIEM header and hierarchy of the elements in this section have been omitted to avoid redundancy. The associated schemas and instances should be consulted to determine the correct XPaths of the elements.

Element Dictionary

Transaction types detailed below include: RAND Query using Free Text (NLQ), RAND Query using person name (NLQ), RAND Query using sequence number (NFQ) and RAND Response (NLR, NFR)

Query Formats

RAND Query using Free Text (NLQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  n2:RANDQuery
  This element encapsulates information about a random access query to Nlets data XML specifications

    n2:MessageSendDateTimeMinimumText
    The beginning date and optional time for the query. The format is ccyy-mm-dd or
    ccyy-mm-dd@hhmm.
    The beginning date and optional time for the query. The format is ccyy-mm-dd or
    ccyy-mm-dd@hhmm.

    n2:MessageSendDateTimeMaximumText
    The ending date and optional time for the query. The format is ccyy-mm-dd or
    ccyy-mm-dd@hhmm.
    The ending date and optional time for the query. The format is ccyy-mm-dd or
    ccyy-mm-dd@hhmm.

    n2:InquiryDescriptionText
    This element contains free text. Include personal descriptors (name, sex) with other relevant data
    (case number, booking number, state ID, miscellaneous number) followed by any additional free text.
    A character string containing text to search for. This string need not be padded and will be
    stored with leading and trailing spaces and carriage return-line feed sequences removed. The
    string is terminated by the end of message or by a period. Most characters in this field
    represent themselves. The field can, however, contain several characters with special meanings:
    described in the text below.

    n2:MessageSourceORIIdentification
    This optional element will contain the source of message either in the form of a two character
    member code or a full nine character ORI.

      nc:IdentificationID
      A value that identifies something.
      This element will contain the source ORI of the message being searched for.

    n2:MessageDestinationORIIdentification
    This optional element will contain the destination of messages either in the form of a two character
    member code or a full nine character ORI.

      nc:IdentificationID
      A value that identifies something.
      This optional element will contain the destination of messages either in the form of a two
      character member code or a full nine character ORI.

    n2:RequestCategoryText
    Identify message types of interest. Enter one or more message types, separated by commas and
    optional spaces. A value of ALL indicates searching all message types.
    Identify message types of interest. Enter one or more message types, separated by commas
    and optional spaces. A value of ALL indicates searching all message types.

RAND Query using Person Name (NLQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  n2:RANDQuery
  This element encapsulates information about a random access query to Nlets data XML specifications.

    n2:MessageSendDateTimeMinimumText
    The beginning date and optional time for the query. The format is ccyy-mm-dd or
    ccyy-mm-dd@hhmm.
    The beginning date and optional time for the query. The format is ccyy-mm-dd or
    ccyy-mm-dd@hhmm.

    n2:MessageSendDateTimeMaximumText
    The ending date and optional time for the query. The format is ccyy-mm-dd or
    ccyy-mm-dd@hhmm.
    The ending date and optional time for the query. The format is ccyy-mm-dd or
    ccyy-mm-dd@hhmm.

    n2:MessageSourceORIIdentification
    This optional element will contain the source of message either in the form of a two character
    member code or a full nine character ORI.

      nc:IdentificationID
      A value that identifies something.
      This element will contain the source ORI of the message being searched for.

    n2:MessageDestinationORIIdentification
    This optional element will contain the destination of messages either in the form of a two character
    member code or a full nine character ORI.

      nc:IdentificationID
      A value that identifies something.
      This optional element will contain the destination of messages either in the form of a two
      character member code or a full nine character ORI.

    n2:RequestCategoryText
    Identify message types of interest. Enter one or more message types, separated by commas and
    optional spaces. A value of ALL indicates searching all message types.
    Identify message types of interest. Enter one or more message types, separated by commas
    and optional spaces. A value of ALL indicates searching all message types.

    nc:Person
    A human being.

      nc:PersonName
      A combination of names and/or titles by which a person is known.

        nc:PersonFullName
        A complete name of a person.
        This required element must contain the full name of the person in the format LAST,
        FIRST MIDDLE.

RAND Query on Message Sequence Number (NFQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  n2:RANDQuery
  This element encapsulates information about a random access query to Nlets data XML specifications.

    n2:MessageSequenceIdentification
    This element will contain the message sequence number as shown in the NLR message.

      nc:IdentificationID
      A value that identifies something.
      This element will contain the message sequence number as shown in the NLR message.

Response Formats

RAND Response in Free Text (NLR,NFR)

n2:NLETSResponseData

n2:ResponseText

This element will contain the free text response. Nlets recommends the use of

<nh2:DocumentControlFieldText><![CDATA[CR055F1R53]]></nh2:DocumentControlFieldText>

tags to ensure that the response does not contain any characters illegal in XML.

Random Access to Nlets Data NIEM Examples

Example 1: A RAND Message querying by free text.

<n2:NLETS version="" xsi:schemaLocation="http://www.nlets.org/niem/1.0 ../xsd/NLQ.xsd" 
xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0" 
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NLQ</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS47</nh2:OriginatingORIID>
    <nh2:DestinationORIID>NL</nh2:DestinationORIID>
	<nh2:DocumentControlFieldText><![CDATA[RAND023456]]></nh2:DocumentControlFieldText>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="NLQ">
    <n2:RANDQuery>
      <n2:MessageSendDateTimeMinimumText>2019-08-01</n2:MessageSendDateTimeMinimumText>
      <n2:MessageSendDateTimeMaximumText>2019-08-01</n2:MessageSendDateTimeMaximumText>
      <n2:InquiryDescriptionText>SUPRA</n2:InquiryDescriptionText>
      <n2:RequestCategoryText>RQ,RR</n2:RequestCategoryText>
    </n2:RANDQuery>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 2: A response from RAND by free text.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NLR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>NL0000000</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[RAND023456]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>10/22/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>13:15</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>10/22/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>13:15</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>01097</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData>
    <n2:ResponseText>TYP/RQ,RR.BEG/20190801.END/20190801.FND/SUPRA

DATETIME       SEQ                ORI        TYPE  DEST       CONTROL     SAMPLE
20190801@0141  AZ0100000000000558103794201908010141257070OR0DMVR00  RR    ID0380300  MRI9765754    RR.OR0DMVR00  01:41 08/01/2019 00659  XX:XX XX/XX/XXXX 00391 ID0380300  *M
20190801@0142  AZ0100000000000558105039201908010142308900OR0DMVR00  RR    ID0380000  MRI9765833    RR.OR0DMVR00  01:42 08/01/2019 00668  XX:XX XX/XX/XXXX 00393 ID0380000  *M
20190801@0725  AZ0100000000000558802945201908010725457270MNVIN0000  RR    MN0070100  10D400B724  &lt;n:NLETS version="3.00" xmlns:j="http://www.it.ojp.gov/jxdm/3.0" xmlns:n="http:/
20190801@0725  AZ0100000000000558802986201908010725463600WIDOT0000  RR    MN0070100  10D400B724  &lt;n:NLETS version="3.00" xmlns:j="http://www.it.ojp.gov/jxdm/3.0" xmlns:n="http:/
20190801@0727  AZ0100000000000558808739201908010727221330OR0DMVR00  RR    VAUSC6199  NN07480172    RR.OR0DMVR00  07:27 08/01/2019 02378  XX:XX XX/XX/XXXX 26386 VAUSC6199  *N
20190801@1013  AZ0100000000000559469445201908011013071370OR0DMVR00  RR    VAUSC6199  NN08708552    RR.OR0DMVR00  10:13 08/01/2019 04666  XX:XX XX/XX/XXXX 45126 VAUSC6199  *N
20190801@1123  AZ0100000000000559746773201908011123354000AZMVD0000  RR    VAUSC6199  NN09262445    RR.AZMVD0000  11:23 08/01/2019 09602  XX:XX XX/XX/XXXX 53160 VAUSC6199  *N
20190801@1502  AZ0100000000000560616881201908011502238770GA0601501  RR    MAMSP0077  RQ71264985  &lt;n:NLETS version="3.00" xmlns:j="http://www.it.ojp.gov/jxdm/3.0" xmlns:n="http:/
20190801@1907  AZ0100000000000561244982201908011907099500OR0DMVR00  RR    UT0250200  00002483BR  &lt;n:NLETS version="3.00" xmlns:j="http://www.it.ojp.gov/jxdm/3.0" xmlns:n="http:/

TOTAL MATCHES LISTED: 9
</n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Example 3: A RAND Message querying by name.

<n2:NLETS version="" xsi:schemaLocation="http://www.nlets.org/niem/1.0 ../xsd/NLQ.xsd" 
xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0" 
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NLQ</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS47</nh2:OriginatingORIID>
    <nh2:DestinationORIID>NL</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[RAND323456]]></nh2:DocumentControlFieldText>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="NLQ">
    <n2:RANDQuery>
      <n2:MessageSendDateTimeMinimumText>2019-08-01</n2:MessageSendDateTimeMinimumText>
      <n2:MessageSendDateTimeMaximumText>2019-08-01</n2:MessageSendDateTimeMaximumText>
      <n2:RequestCategoryText>RQ,RR</n2:RequestCategoryText>
      <nc:Person>
        <nc:PersonName>
          <nc:PersonFullName>SMITH,JOHN</nc:PersonFullName>
        </nc:PersonName>
      </nc:Person>
    </n2:RANDQuery>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 4: A response from RAND by name.

<?xml version="1.0" encoding="utf-16"?>
<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NLR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>NL0000000</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>10/22/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>13:47</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>10/22/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>13:47</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>01159</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData>
    <n2:ResponseText>TYP/AM.SRC/AZNLETS47.BEG/20191021@1346.END/20191022@1346.FND/'PLANO AND MAINTENANCE'

DATETIME       SEQ                ORI        TYPE  DEST       CONTROL     SAMPLE
20191022@1123  AZ0100000000000832024864201910221123465000AZNLETS47  AM    AK         CUT102219O    AM.AZNLETS47  11:23 10/22/2019 00165  XX:XX XX/XX/XXXX 02008 AK  *CUT10221
20191022@1123  AZ0100000000000832024866201910221123465200AZNLETS47  AM    AL         CUT102219O  &lt;n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/n
20191022@1123  AZ0100000000000832024871201910221123465370AZNLETS47  AM    AR         CUT102219O  &lt;n:NLETS version="3.00" xmlns:j="http://www.it.ojp.gov/jxdm/3.0" xmlns:n="http:/
20191022@1123  AZ0100000000000832024872201910221123465530AZNLETS47  AM    AX         CUT102219O    AM.AZNLETS47  11:23 10/22/2019 00165  XX:XX XX/XX/XXXX 09983 AX  *CUT10221
20191022@1123  AZ0100000000000832024875201910221123465700AZNLETS47  AM    AZ         CUT102219O    AM.AZNLETS47  11:23 10/22/2019 00165  XX:XX XX/XX/XXXX 08508 AZ  *CUT10221
20191022@1123  AZ0100000000000832024876201910221123465800AZNLETS47  AM    CA         CUT102219O    AM.AZNLETS47  11:23 10/22/2019 00165  XX:XX XX/XX/XXXX 13604 CA  *CUT10221
20191022@1123  AZ0100000000000832024878201910221123465970AZNLETS47  AM    CO         CUT102219O    AM.AZNLETS47  11:23 10/22/2019 00165  XX:XX XX/XX/XXXX 08949 CO  *CUT10221
20191022@1123  AZ0100000000000832024880201910221123466200AZNLETS47  AM    CT         CUT102219O    AM.AZNLETS47  11:23 10/22/2019 00165  XX:XX XX/XX/XXXX 05040 CT  *CUT10221
20191022@1123  AZ0100000000000832024882201910221123466600AZNLETS47  AM    DE         CUT102219O  &lt;n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/n
20191022@1123  AZ0100000000000832024887201910221123466800AZNLETS47  AM    DJ         CUT102219O    AM.AZNLETS47  11:23 10/22/2019 00165  XX:XX XX/XX/XXXX 04041 DJ  *CUT10221
20191022@1123  AZ0100000000000832024890201910221123466930AZNLETS47  AM    DN         CUT102219O    AM.AZNLETS47  11:23 10/22/2019 00165  XX:XX XX/XX/XXXX 00304 DN  *CUT10221
20191022@1123  AZ0100000000000832024892201910221123467200AZNLETS47  AM    FB         CUT102219O    AM.AZNLETS47  11:23 10/22/2019 00165  XX:XX XX/XX/XXXX 03298 FB  *CUT10221
20191022@1123  AZ0100000000000832024893201910221123467400AZNLETS47  AM    FL         CUT102219O  &lt;n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/n
20191022@1123  AZ0100000000000832024894201910221123467500AZNLETS47  AM    GA         CUT102219O  &lt;n:NLETS version="3.00" xmlns:j="http://www.it.ojp.gov/jxdm/3.0" xmlns:n="http:/
20191022@1123  AZ0100000000000832024896201910221123467630AZNLETS47  AM    HI         CUT102219O    AM.AZNLETS47  11:23 10/22/2019 00165  XX:XX XX/XX/XXXX 01754 HI  *CUT10221
20191022@1123  AZ0100000000000832024899201910221123467800AZNLETS47  AM    IA         CUT102219O  &lt;n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/n
20191022@1123  AZ0100000000000832024903201910221123468000AZNLETS47  AM    ID         CUT102219O  &lt;n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/n
20191022@1123  AZ0100000000000832024905201910221123468170AZNLETS47  AM    IL         CUT102219O    AM.AZNLETS47  11:23 10/22/2019 00165  XX:XX XX/XX/XXXX 12432 IL  *CUT10221
20191022@1123  AZ0100000000000832024906201910221123468370AZNLETS47  AM    IN         CUT102219O  &lt;n:NLETS version="3.00" xmlns:j="http://www.it.ojp.gov/jxdm/3.0" xmlns:n="http:/
20191022@1123  AZ0100000000000832024911201910221123468570AZNLETS47  AM    KS         CUT102219O  &lt;n:NLETS version="3.00" xmlns:j="http://www.it.ojp.gov/jxdm/3.0" xmlns:n="http:/
20191022@1123  AZ0100000000000832024912201910221123468900AZNLETS47  AM    KY         CUT102219O  &lt;n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/n
20191022@1123  AZ0100000000000832024917201910221123469170AZNLETS47  AM    LA         CUT102219O  AM.AZNLETS47  11:23 10/22/2019 00165  XX:XX XX/XX/XXXX 06064 LA  *CUT102219O  TX
20191022@1123  AZ0100000000000832024920201910221123469430AZNLETS47  AM    MA         CUT102219O  &lt;n:NLETS version="3.00" xmlns:j="http://www.it.ojp.gov/jxdm/3.0" xmlns:n="http:/
20191022@1123  AZ0100000000000832024922201910221123469600AZNLETS47  AM    MD         CUT102219O  &lt;n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/n
20191022@1123  AZ0100000000000832024923201910221123469700AZNLETS47  AM    ME         CUT102219O    AM.AZNLETS47  11:23 10/22/2019 00165  XX:XX XX/XX/XXXX 03421 ME  *CUT10221
20191022@1123  AZ0100000000000832024928201910221123469870AZNLETS47  AM    MI         CUT102219O  &lt;n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/n
20191022@1123  AZ0100000000000832024929201910221123477000AZNLETS47  AM    MN         CUT102219O  &lt;n:NLETS version="3.00" xmlns:j="http://www.it.ojp.gov/jxdm/3.0" xmlns:n="http:/
20191022@1123  AZ0100000000000832024931201910221123471700AZNLETS47  AM    MS         CUT102219O    AM.AZNLETS47  11:23 10/22/2019 00165  XX:XX XX/XX/XXXX 04760 MS  *CUT10221
20191022@1123  AZ0100000000000832024933201910221123472700AZNLETS47  AM    MT         CUT102219O  &lt;n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/n
20191022@1123  AZ0100000000000832024934201910221123474000AZNLETS47  AM    NB         CUT102219O  &lt;n:NLETS version="3.00" xmlns:j="http://www.it.ojp.gov/jxdm/3.0" xmlns:n="http:/
20191022@1123  AZ0100000000000832024936201910221123475700AZNLETS47  AM    NC         CUT102219O    AM.AZNLETS47  11:23 10/22/2019 00165  XX:XX XX/XX/XXXX 09704 NC  *CUT10221
20191022@1123  AZ0100000000000832024940201910221123477000AZNLETS47  AM    NH         CUT102219O  &lt;n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/n
20191022@1123  AZ0100000000000832024942201910221123478000AZNLETS47  AM    NJ         CUT102219O  &lt;n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/n
20191022@1123  AZ0100000000000832024944201910221123479000AZNLETS47  AM    NM         CUT102219O  &lt;n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/n
20191022@1123  AZ0100000000000832024945201910221123471030AZNLETS47  AM    NV         CUT102219O    AM.AZNLETS47  11:23 10/22/2019 00165  XX:XX XX/XX/XXXX 04999 NV  *CUT10221
20191022@1123  AZ0100000000000832024947201910221123471230AZNLETS47  AM    NY         CUT102219O  &lt;n:NLETS version="3.00" xmlns:j="http://www.it.ojp.gov/jxdm/3.0" xmlns:n="http:/
20191022@1123  AZ0100000000000832024953201910221123471600AZNLETS47  AM    OH         CUT102219O  &lt;n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/n
20191022@1123  AZ0100000000000832024954201910221123471700AZNLETS47  AM    OK         CUT102219O  &lt;n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/n
20191022@1123  AZ0100000000000832024958201910221123471900AZNLETS47  AM    OR         CUT102219O  &lt;n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/n
20191022@1123  AZ0100000000000832024960201910221123472130AZNLETS47  AM    PA         CUT102219O  &lt;n:NLETS version="3.00" xmlns:j="http://www.it.ojp.gov/jxdm/3.0" xmlns:n="http:/
20191022@1123  AZ0100000000000832024963201910221123472300AZNLETS47  AM    PS         CUT102219O    AM.AZNLETS47  11:23 10/22/2019 00165  XX:XX XX/XX/XXXX 00088 PS  *CUT10221
20191022@1123  AZ0100000000000832024965201910221123472470AZNLETS47  AM    RI         CUT102219O  &lt;n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/n
20191022@1123  AZ0100000000000832024966201910221123472600AZNLETS47  AM    SC         CUT102219O  AM.AZNLETS47  11:23 10/22/2019 00165  XX:XX XX/XX/XXXX 05993 SC  *CUT102219O  TX
20191022@1123  AZ0100000000000832024967201910221123472700AZNLETS47  AM    SD         CUT102219O  &lt;n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/n
20191022@1123  AZ0100000000000832024968201910221123472800AZNLETS47  AM    SS         CUT102219O    AM.AZNLETS47  11:23 10/22/2019 00165  XX:XX XX/XX/XXXX 00554 SS  *CUT10221
20191022@1123  AZ0100000000000832024969201910221123472900AZNLETS47  AM    TC         CUT102219O    AM.AZNLETS47  11:23 10/22/2019 00165  XX:XX XX/XX/XXXX 75151 TC  *CUT10221
20191022@1123  AZ0100000000000832024970201910221123473000AZNLETS47  AM    TN         CUT102219O  &lt;n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/n
20191022@1123  AZ0100000000000832024971201910221123473100AZNLETS47  AM    TX         CUT102219O  &lt;n:NLETS version="3.00" xmlns:j="http://www.it.ojp.gov/jxdm/3.0" xmlns:n="http:/
20191022@1123  AZ0100000000000832024973201910221123473200AZNLETS47  AM    UT         CUT102219O  &lt;n:NLETS version="3.00" xmlns:j="http://www.it.ojp.gov/jxdm/3.0" xmlns:n="http:/
20191022@1123  AZ0100000000000832024978201910221123473330AZNLETS47  AM    VA         CUT102219O  &lt;n:NLETS version="3.00" xmlns:j="http://www.it.ojp.gov/jxdm/3.0" xmlns:n="http:/
20191022@1123  AZ0100000000000832024983201910221123473500AZNLETS47  AM    VT         CUT102219O    AM.AZNLETS47  11:23 10/22/2019 00165  XX:XX XX/XX/XXXX 01944 VT  *CUT10221
20191022@1123  AZ0100000000000832024985201910221123473800AZNLETS47  AM    WA         CUT102219O  &lt;n:NLETS version="3.00" xmlns:j="http://www.it.ojp.gov/jxdm/3.0" xmlns:n="http:/
20191022@1123  AZ0100000000000832024990201910221123474200AZNLETS47  AM    WI         CUT102219O    AM.AZNLETS47  11:23 10/22/2019 00165  XX:XX XX/XX/XXXX 04784 WI  *CUT10221
20191022@1123  AZ0100000000000832024995201910221123474470AZNLETS47  AM    WV         CUT102219O  &lt;n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/n
20191022@1123  AZ0100000000000832024998201910221123474800AZNLETS47  AM    WY         CUT102219O  &lt;n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/n
20191022@1123  AZ0100000000000832025004201910221123475330AZNLETS47  AM    PR         CUT102219O  &lt;n:NLETS version="3.00" xmlns:j="http://www.it.ojp.gov/jxdm/3.0" xmlns:n="http:/
20191022@1123  AZ0100000000000832025009201910221123475600AZNLETS47  AM    DC         CUT102219O  &lt;n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/n
20191022@1123  AZ0100000000000832025014201910221123476030AZNLETS47  AM    MO         CUT102219O  &lt;n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/n
20191022@1123  AZ0100000000000832025016201910221123476170AZNLETS47  AM    TS         CUT102219O  &lt;n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/n
20191022@1123  AZ0100000000000832025018201910221123476300AZNLETS47  AM    PY         CUT102219O  &lt;n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/n
20191022@1123  AZ0100000000000832025020201910221123476400AZNLETS47  AM    P4         CUT102219O  &lt;n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/n
20191022@1123  AZ0100000000000832025021201910221123476500AZNLETS47  AM    DA         CUT102219O    AM.AZNLETS47  11:23 10/22/2019 00165  XX:XX XX/XX/XXXX 00035 DA  *CUT10221
20191022@1123  AZ0100000000000832025025201910221123476600AZNLETS47  AM    P1         CUT102219O  &lt;n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/n
20191022@1123  AZ0100000000000832025026201910221123476800AZNLETS47  AM    GM         CUT102219O  &lt;n:NLETS version="3.00" xmlns:j="http://www.it.ojp.gov/jxdm/3.0" xmlns:n="http:/
20191022@1123  AZ0100000000000832025028201910221123476970AZNLETS47  AM    IP         CUT102219O    AM.AZNLETS47  11:23 10/22/2019 00165  XX:XX XX/XX/XXXX 49127 IP  *CUT10221
20191022@1123  AZ0100000000000832025029201910221123477200AZNLETS47  AM    JW         CUT102219O  &lt;n:NLETS version="3.00" xmlns:j="http://www.it.ojp.gov/jxdm/3.0" xmlns:n="http:/
20191022@1123  AZ0100000000000832025034201910221123477470AZNLETS47  AM    P6         CUT102219O    AM.AZNLETS47  11:23 10/22/2019 00165  XX:XX XX/XX/XXXX 01693 P6  *CUT10221
20191022@1123  AZ0100000000000832025035201910221123477600AZNLETS47  AM    P3         CUT102219O    AM.AZNLETS47  11:23 10/22/2019 00165  XX:XX XX/XX/XXXX 00072 P3  *CUT10221
20191022@1123  AZ0100000000000832025039201910221123477800AZNLETS47  AM    AZNLETS47  CUT102219O  &lt;n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/n

TOTAL MATCHES LISTED: 69
</n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Example 5: A RAND Message querying by sequence number.

<n2:NLETS xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0" 
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">  
   <n2:NLETSMessageHeader>
            <nh2:MessageKeyCodeText>NFQ</nh2:MessageKeyCodeText>
            <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
            <nh2:DestinationORIID>NL</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[RAND979859]]></nh2:DocumentControlFieldText>
   </n2:NLETSMessageHeader>
   <n2:NLETSInquiryData n2:key="NFQ">
           <n2:RANDQuery>
                   <n2:MessageSendDateTimeMinimumText>2019-10-22</n2:MessageSendDateTimeMinimumText>
                   <n2:MessageSendDateTimeMaximumText>2019-10-22</n2:MessageSendDateTimeMaximumText>
               <n2:MessageSequenceIdentification>
                   <nc:IdentificationID>AZ0100000000000832</nc:IdentificationID>
               </n2:MessageSequenceIdentification>
           </n2:RANDQuery>
    </n2:NLETSInquiryData>
</n2:NLETS>

Example 6: A response from RAND by sequence number.

Top

Legacy (DEPRECATED)

Random Access to Nlets Data Legacy Specifications

This section describes the format and provides examples for queries (NLQ/NFQ) to the Nlets message log of traffic that travels through it and the corresponding responses (NLR/NFR).

Messages can be retrieved by message type, time range, originator, member, and by character string within a message.

All messages will be preceded by a standard input header.

All data elements are preceded by a prefix and terminated by a period with the exception of the last character of the message.

Query Formats

Queries to the Nlets message log follow these rules:

The TYP, BEG and END fields are mandatory.
At least one FND or NAM field must be entered.
FND and NAM fields cannot both be present.
Either AND or ORR fields may be entered if FND is present.
AND and ORR fields cannot be used in the same message

If a TYP field is specified for which the requestor is not authorized, then the response
message will include a warning that the user is not authorized to retrieve that message type.
The request must contain at least one authorized message type.

Fields need not be padded to any particular size. They will all be trimmed of leading or trailing
spaces before use.

Name Based Search

The NAM field may be used in place of FND and AND combinations or FND and ORR combinations when the search string is intended to match the proper names of people rather than general text.

Special rules are used for name based searches compared to general free text searches. These four rules are listed below.

Each name entry (NAM) accepts name components separated by spaces, commas, hyphens
or other non-alphanumeric characters.
Name strings (NAM) may contain the asterisk ("*") in any position after the first character of an
alphanumeric name to indicate a match to any character string following the leading portion.
The search process ignores non-alphanumeric characters in each message when comparing
for a match.
Order of name components is not important.

Name (NAM) based searches are not confined to message text beginning with NAM/ but searches for names appearing anywhere in the message.

The table below shows the fields for an NLQ message.

Entry: Size: Explanation:
NLQ. 3 Message type for searching the RAND message
database.
Sender ORI 9 Sender ORI followed by a period.
Destination ORI 2 Must always be NL followed by a period.
TXT 3 Field prefix denoting beginning of message.
TYP/ 4 Prefix to identify message types of interest.
Message Types 100

One or more message types, separated by commas
and optional spaces, ending with a period. A value of
ALL indicates searching all message types.

SRC/ 4 Prefix to identify source member or ORI followed
by a period.
Source ORI or Member 2 or 9

Source of messages either in the form of a two
character member code or a full 9 character ORI
followed by a period.

DST/ 4 Prefix to identify destination member or ORI
followed by a period.
Destination ORI or
Member
2 or 9

Destination of messages either in the form of a two
character member code or a full 9 character ORI
followed by a period.

BEG/ 4 Prefix to identify the beginning date and optional time
for the query.
Beginning Date and
Optional Time
8 or 13

The beginning date and optional time for the query,
followed by period. The format is ccyymmdd or
ccyymmdd@hhmm.

END/ 4 Prefix to identify the ending date and optional time for
the query.
Ending Date and
Optional Time
8 or 13

The ending date and optional time for the query,
followed by period. The format is ccyymmdd or
ccyymmdd@hhmm.

FND/ 4 Prefix to identify the free text information needed.
Free Text 250

A character string containing text to search for. This
string need not be padded and will be stored with
leading and trailing spaces and carriage return-line
feed sequences removed. The string is terminated by
the end of message or by a period. Most characters in
this field represent themselves. The field can,
however, contain several characters with special
meanings: described in the text below.

An automated response from the Nlets system will be returned advising that the query (NLQ) was successfully received and placed in the queue for processing.

Once processing is complete, the response (NLR) will be returned.

  • Output begins with the date on a line by itself.
  • A series of lines follow, each starting with a time and continuing with the member the message was sent to (or received from), the sequence number of the message, the originator ORI, the message type, the destination ORI, and up to 40 characters of message data beginning with the first point in the message where any search term matched.
  • If the results cover more than one date, the next date is printed and followed by the search hits for that day.
  • There is a limit of 100 hits for a given NLR. If more than 100 hits are necessary, the time and date of the last hit can be used as the BEG field date of a subsequent query where all other fields are as they were in the original NLQ.

The NFQ transaction is based on the NLR message generated by an NLQ transaction.

  • The standard Nlets message header and all of the fields listed in the table below are required to retrieve a full text message.
  • The message sequence field (MSG) may repeat to retrieve more than one message for the given member and date.
  • All retrieved messages in a single NFQ must be for the same date since the date field (DAT) cannot be repeated.
Entry: Size: Explanation:
NFQ. 3 Message type for RAND full text retrieval followed by
period.
DAT/ 8 Date of the transaction.
MSG/ 45 45 digit message sequence number as shown in the
NLR message.
Random Access to Nlets Data Legacy Examples

Example 1: A RAND Message querying by free text.

NLQ.AZNLETS20.NL.TXT
TYP/RQ,RR.BEG/20110801.END/20110801.FND/BUICK

Example 2: A response from RAND by free text.

NLR.NL0000000
08:21 08/31/2011 17345
08:21 08/31/2011 09138 AZNLETS20
TXT
TYP/RQ,RR.BEG/20110801.END/20110801.FND/BUICK
DATETIME SEQ ORI TYPE DEST CONTROL
SAMPLE 20110801@0000 2011081085772095 PADPS0000 RR VA007163N VAMDT00RX7
RR.PADPS0000
00:00 08/01/2011 46154
XX:XX XX/XX/XXXX 40791 VA007163N
*V
20110801@0000 2011081085772127 MI230015V RR VAUSC6199 CQCL349835
RR.MI230015V
00:00 08/01/2011 47944
XX:XX XX/XX/XXXX 06693 VAUSC6199
*C
20110801@0001 2011081085772227 MI230015V RR VAUSC6199 CQCLB19654
TOTAL MATCHES LISTED: 2

Example 3: A RAND Message querying by name.

NLQ.AZNLETS20.NL.TXT
TYP/RQ,RR.SRC/AZ.BEG/20110801.END/20110801.FND/NAME,FULL

Example 4: A response from RAND by name.

NLR.NL0000000
08:56 08/31/2011 17698
08:56 08/31/2011 09142 AZNLETS20
TXT
TYP/RR,RQ.SRC/AZ.BEG/20110801.END/20110801.NAM/NAME,FULL
NO DATA FOUND MATCHING THE SEARCH CRITERIA

Example 5: A RAND message by sequence number.

NFQ.AZNLETS20.NL.TXT
DAT/20110801.MSG/2011221087250119

Example 6: A response from RAND by sequence number.

NFR.NL0000000
08:21 08/31/2011 17346
08:21 08/31/2011 09139 AZNLETS20
TXT
DAT/20110801.MEM/AZ.MSG/2011081087270169
TEXT OF RETRIEVED MESSAGE FOLLOWS FOR SEQUENCE: 2011221087250119
RR.AZMVDPX00
18:24 08/01/2011 15954
XX:XX XX/XX/XXXX 41220 MA0094800
*RLT2C20CB0
TXT
LIC/AAA1111.LIY/2011.LIT/PC.
LIC:AAA1111 EXPIRE: 01/20/2010
NAM:SMITH,JOHN CUST#:D00000001
NAM:SMITH,JANE CUST#:D00000002
ADR:1234 W ANYSTREET RD
CTY:PHOENIX ST:AZ ZIP:850100000
MSGS: PLATES NOT VALID FOR HIGHWAY USE
MSGS: PLATE IS FOR CREDIT ONLY PREVIOUS VEH INFO BELOW
VIN:1A1AA11A1AA1111111 VYR:1990 VMA:BUICK VST:4DSD

Top

Downloads

Download NLQ Schema

Download NLQ Stylesheet

Download NLR Schema

Download NLR Stylesheet

Download NFQ Schema

Download NFQ Stylesheet

Download NFR Schema

Download NFR Stylesheet

Top