- Lien Notification (Part 1)
- Lien Notification (Part 2)
- Response to Lien Notification
- Lienholder Release of Interest - Error
- Confirmation of Release | Release Lien Interest
- Response to Release Lien | Request Paper Title
- Confirmation of Request
- Title Held Removed
- Connectivity Requirements
Lien Notification (Part 1)
LC Message Data Blocks and Required Data Elements
Message Description: The lien notification message is created by DMV as a result of the establishment of a title record on the DMV database with lienholder information that matches a participant. The messages will be grouped together and sent to the lienholder’s mailbox. T
he lienholder responds by formatting and sending the RC-Response to Lien Notification Message to DMV. The RC message contains a count of messages received, processed and in error.
If the lienholder detects an error in the data sent by DMV it can add the 99/2 Edit/Error Description block to the LC message and return it to DMV.
| Block ID | Block Name | DMV-required Data Elements |
|---|---|---|
| 00/0 | Network control block | All elements |
| 02/3 | Message exchange block | All elements |
| 06/2 | Vehicle identification block | Vehicle ID number Vehicle make Vehicle model year |
| 26/2 | Title identification block | Title number Title issue date Title status Title Held Reason Title Held Reason Jurisdiction |
| 30/1 | Lien data block | Lienholder ID number Date of lien |
| 30/2 | Lienholder name block | Lienholder name |
| 30/3 | Lienholder address block | Lienholder address |
| 34/1 | Owner name block | Owner name |
| 34/2 | Owner mailing address block | Owner address |
Lien Notification (Part 2)
LD Message Data Blocks and Required Data Elements
Message Description: The LD message contains additional data elements used in the transmission of data necessary to report that the lien has been perfected.
| Block ID | Block Name | DMV-required Data Elements |
|---|---|---|
| 00/0 | Network control block | All elements |
| 02/3 | Message exchange block | All elements |
| 06/2 | Vehicle identification block | Vehicle ID number Vehicle make Vehicle model year |
| 26/2 | Brand data block | All elements |
Response to Lien Notification
RC Message Data Blocks and Required Data Elements
Message Description: The Response to Lien Notification message is formatted and sent by the lienholder when receiving a group of LC - Lien Notification messages. The response message contains counts of messages received, messages processed and messages in error.
| Block ID | Block Name | DMV-required Data Elements |
|---|---|---|
| 00/0 | Network control block | All elements |
| 02/3 | Message exchange block | All elements |
| 23/C | Response statistics block | Number received Number received with errors Number processed |
Lienholder Release of Interest - Error
LE Message Data Blocks and Required Data Elements
Message Description: The Release of Interest Due to Error transaction is created by the lienholder and sent to DMV when the lienholder determines that they have no interest in the vehicle and an error has occurred. If DMV detects an error in the data contained in the LE message, the 99/2 Edit/Error Description block is added to the LE message and the message is returned to the lienholder.
| Block ID | Block Name | DMV-required Data Elements |
|---|---|---|
| 00/0 | Network control block | All elements |
| 02/3 | Message exchange block | All elements |
| 06/2 | Vehicle identification block | Vehicle ID number Vehicle make Vehicle model year |
| 26/2 | Title identification block | Title number Title issue date |
| 30/1 | Lien data block | Lienholder ID number Date of lien |
Confirmation of Release
CA Message Data Blocks and Required Data Elements
Message Description: DMV responds to the LE message with the CA confirmation message if the lien information is removed from the title record.
| Block ID | Block Name | DMV-required Data Elements |
|---|---|---|
| 00/0 | Network control block | All elements |
| 02/3 | Message exchange block | All elements |
Release Lien Interest
LO Message Data Blocks and Required Data Elements
Message Description: A message originating with the lienholder that notifies DMV that the lienholder no longer has an interest in the vehicle. DMV responds by sending the RO - Release Lien Confirmation message.
The LO message may contain the 99/2 Edit/Error Description block if DMV detects an error condition that prevents the release of lienholder interest.
| Block ID | Block Name | DMV-required Data Elements |
|---|---|---|
| 00/0 | Network control block | All elements |
| 02/3 | Message exchange block | All elements |
| 06/2 | Vehicle identification block | Vehicle ID number Vehicle make Vehicle model year |
| 26/2 | Title identification block | Title number Title issue date |
| 30/1 | Lien data block | Lienholder ID number Lien release date |
| 34/1 | Owner name block | Owner name * |
| 34/2 | Owner mailing address block | Owner address * |
Note: When using Emergency Mailbox for Distributive Printing, the 34/1 field is to contain the name of the entity picking up the title, and the 34/2 field is to contain the Customer Service Center Code and the Customer Service Center Name (a3, a40), eg. 600Alexandria Customer Service Center.
When using the Regular Mailbox for Distributive Mailing, the 34/1 field is to contain the first 30 characters of the name of the entity to which the title is to be mailed on the first occurrence and the second 30 characters of the name of the entity to which the title is to be mailed on the second occurrence (if necessary). The 34/2 field is to contain the address of the entity to which the title is to be mailed in the following fixed format:
- Street address (a35)
- City (a22)
- State (a2)
- Zip (a9)
- Country Cd (a2)
DMV can echo back this information if the LO message was in error, only. Confirmations will not contain echo back.
Response to Release Lien
RO Message Data Blocks and Required Data Elements
Message Description: A message sent by DMV in response to lienholder’s message to release interest in the vehicle.
| Block ID | Block Name | DMV-required Data Elements |
|---|---|---|
| 00/0 | Network control block | All elements |
| 02/3 | Message exchange block | All elements |
| 06/2 | Vehicle identification block | Vehicle ID number Vehicle make Vehicle model year |
Request Paper Title
LG Message Data Block and Required Data Elements
Message Description: A message sent by the lienholder requesting DMV to print a title document for a vehicle in which they have an interest. If an error is detected, the 99/2 Edit/Error description block is added to the LG message and the message is returned to the lienholder.
| Block ID | Block Name | DMV-required Data Elements |
|---|---|---|
| 00/0 | Network control block | All elements |
| 02/3 | Message exchange block | All elements |
| 06/2 | Vehicle identification block | Vehicle ID number Vehicle make Vehicle model year |
| 26/2 | Title identification block | Title number Title issue date |
| 30/1 | Lien data block | Lienholder ID number Date of lien |
| 34/1 | Owner name block | Owner name * |
| 34/2 | Owner mailing address block | Owner address * |
* Note: When using Emergency Mailbox for Distributive Printing, the 34/1 field is to contain the name of the entity picking up the title, and the 34/2 field is to contain the Customer Service Center Code (a3, eg. 600) and the Customer Service Center Name (a40, eg. Alexandria Customer Service Center.
When using the Regular Mailbox for Distributive Mailing, the 34/1 field is to contain the first 30 characters of the name of the entity to which the title is to be mailed on the first line and the second 30 characters of the name of the entity to which the title is to be mailed on the second line (if necessary). The 34/2 field is to contain the address of the entity to which the title is to be mailed in the following fixed format:
- Street address (a35)
- City (a22)
- State (a2)
- Zip (a9)
- Country Cd (a2)
DMV can echo back this information if the LG message was in error, only. Confirmations will not contain echo back.
Confirmation of Request
CA Message Data Blocks and Required Data Elements
Message Description: DMV responds to the print title request with a CA confirmation message if the title document is successfully printed
| Block ID | Block Name | DMV-required Data Elements |
|---|---|---|
| 00/0 | Network control block | All elements |
| 02/3 | Message exchange block | All elements |
Title Held Removed
LV Message Data Block and Required Data Elements
Message Description: The Title Held Removed Notification transaction is created by DMV as a result of the title that was being held by state has now been released. No confirmation is necessary.
| Block ID | Block Name | DMV-required Data Elements |
|---|---|---|
| 00/0 | Network control block | All elements |
| 02/3 | Message exchange block | All elements |
| 06/2 | Vehicle identification block | Vehicle ID number Vehicle make Vehicle model year |
| 26/2 | Title identification block | Title number Title issue date |
| 30/1 | Lien data block | Lienholder ID number Date of lien |
Connectivity Requirements
ADVANTIS Network Access: Lienholders must be able to access the Advantis Information Exchange (IE) service on the Advantis network. Access to the Advantis network can be accomplished via leased line or dial access.
ADVANTIS Information Exchange Access: Lienholders who access the Advantis network directly must be able to interface with the IE service. Advantis provides the EXPEDITE family of software products to accomplish interface with IE. EXPEDITE versions are available for the following systems: DOS, OS/2, Windows, AIX, SCO XENIX, CICS, MVS and VM.
Message Translation Software: The program requires lienholders to format ELP messages using the AAMVAnet AMIE message format. Two programs are available from AAMVAnet to perform the task of encoding and decoding the AMIE format.
- UNI (Unified Network Interface) is the network interface software designed to handle messages between two or more AAMVAnet sites. The program edits inbound and outbound messages, performs message routing and translates messages into the AMIE format. UNI is available for the following systems: CICS/VSAM, OS/2-CICS/IDX, IMS/DL1, Unisys 1100, and Data General. Versions are under development for UNIX
- AMIE/ba (AMIE Batch) is a message translator only. The program currently is available only for the IBM MVS system as well as PC/DOS systems. AAMVAnet has stated that versions of AMIE/ba for other systems could be developed, tested and delivered in three weeks.
Note: UNI and AMIE/ba are proprietary products of AAMVAnet.
- DMV Constraints
- Before testing with AAMVAnet, be sure to use only two (2) Alpha characters as your Origin Code (x7) field. Also ensure that the first two Alpha characters of your lienholder ID number match your Origin Code.
- DMV uses the Batch version of the UNI software and therefore requires the inbound messages to be formatted as follows:
| send field (filename) | class (pctext) | delimit (c) |
| account (vamv) | userid (vamvelt) | for Regular Mailbox |
| 02/3 | (vamvele) | for Emergency Mailbox |
| (vamvtst) | for Testing Mailbox |
- Detailed Specifications and Lienholder Codes: Contact AAMVAnet to obtain a copy of the detailed specifications, and to obtain the two-digit "GAP" code. Patrice Aasmo, Senior Account Representative: (703) 908-5787