iiX Online Support - ExpressNet

Support Home • ExpressNet • Express for Browsers • Express for Windows • MVR Information • A-Plus™, Credit, UDI/UDV • Criminal History

Search

Understanding the Express for Windows™ Logfile

Understanding the Express for Windows™ Logfile

Interpretations of the Express for Windows™ Logfile:

The first 6 sections covered below are of interest to those who want to view the logfile from a technician's standpoint. The last 6 sections cover what happens after a connection is actually made - such as, our Day Message and what files are uploaded and downloaded.

The beginning section of the logfile shows the time the communication session began. It also indicates on the Modem Toolkit entry whether the Windows® communications driver (V3003) or the DOS communications driver (V2003) is being used.

_{!MT-I, BEGIN
COMM SESSION:}

_{!MT-I, ---->>
Tue Jul 07 08:55:11 AM}

_{!MT-D, DEBUG
LEVEL: 3}

_{!MT-D, No Alt
Config specified.}

_{!MT-D, Using
Default Config file (config.ams).}

_{!MT-D, Config
loaded OK.}

_{!MT-D, Modem
Toolkit: V3003(001)}

_{!MT-D,
CONFIGURATION...}

_DEBUG:[3]

The next section contains the LBUFF information. This information is passed to the iiX system at login. The first 6 digits are the account #. The next 6 are the password. The next 3 are the User ID, etc. Also included in this line are the software version, State Edit version, and Bill Code table version. This information allows iiX customer support to know what software version you have, and it lets our system know whether to download any state edit or billing code updates to your system.

_{LBUFF:[999999AMSMVRIIX#00003003SYYYYYY***AMSVBWINVERS0230001STATEDIT040DBILCODE021]}

This section indicates the Access type - ACCES: [ D ] = Direct Dial ( one of iiX's 800 numbers ). The line labelled DIAL [ 9,18007096802 ] T: [ 50 ] means that the system is dialing 9, for an outside line, then 18007096802 to reach iiX Data Center, allowing 50 seconds for the connection to be made.

_ACCES:[D]

_{GUARDTIME:[40]}

_NOHUP:[0]

_{DIAL:
[9,18007096802] T:[50]}

_{T1:[1], T2:[10]}

_NOISE:[450]

The next section includes the following:

DRIVER = [ I ] indicates how the software is talking to the modem. I = Interrupt mode (direct hardware), P = Polled mode (indirect via buffering), B = Bios/INT14 ( software interrupt 14 ), or X = Xbios/INT14 ( software interrupt 14 ). B and X are usually used when modems are pooled through communications servers.

PORTINFO = (COM2:, 9600,N,8,1) indicates how the software was configured to access the modem and initialize the com port. COM2 = Com 2 ( can be 1,2,3,or 4), 9600 = 9600 bits per second - i.e. the modem speed, N81 indicate the parity = 8 data bits, 1 stop bit, No parity.

FLOW = [ R ] means that RTS/CTS (hardware) flow control is being used. Other possible values are N - no flow control, and X - XON/XOFF (software) flow control.

ODDINT = [ 0 ] , [0x00] indicates whether the software has been configured for a modem using a non-standard interrupt. The first bracket indicates the IRQ being used and the second bracket shows the Base Address of the Com Port. When the values are set to 0, the default IRQ and base addresses for the selected com port are being used.

_{DRIVER: [ I ]}

_{NASISESSION:[,,,]}

_{PORTINFO:[
COM2:,9600,N,8,1 ]}

_{AUTOCONNECT:[ 1 ]}

_{ZRECOVER:[
1014 ]}

_{ZBLOCK:[
1015 ]}

_{DTERATE:[
F ]}

_{FLOW:[ R ]}

_{ODDINT:[ 0
] [ 0x0 ]}

This next section shows the command being issued to initialize (configure) the modem.

RESET : [ AT&F ] This is the first command issued to the modem. AT&F is a factory reset command - telling the modem is configure itself using the manufacturer's factory default profile.

INIT: The lines that follow that are additional configuration strings issued to the modem after the initial RESET is issued. Line [ 0 ] generally issues the AT&F string again. This line is sent to the modem after the communications session is ended. Line [ 1 ] is issued after the RESET command line. This is done before the modem dials iiX.

_{RESET:[ AT&F ]}
_INIT:
	_{[0] AT&F}
	_{[1] ATV1E1Q0X4S0=0S7=60S10=50&B1&A0&H1&R2}
	_[2]
	_[3]
	_[4]

The following are the modem responses that the software looks for after dialing. Those in the CONNECT section are the ones issued when the modem makes contact with the iiX modems. The NOCONNECT messages are the possible modem responses that can appear when some type of failure has occured. If the modem returns ones of the NO CONNECT messages, the software will redial.

_CONNECT:
	_{[0] CONNECT 19200 =(19200)}
	_{[1] CONNECT 14400 =(19200)}
	_{[2] CONNECT 12000 =(19200)}
	_{[3] CONNECT 9600 =(9600)}
	_{[4] CONNECT 7200 =(7200)}
	_{[5] CONNECT 4800 =(4800)}
	_{[6] CONNECT 2400 =(2400)}
	_{[7] CONNECT 1200 =(1200)}
	_{[8] CONNECT =(300)}
	_{[9] =(0)}
_NOCONNECT:
	_{[0] BUSY}
	_{[1] ERROR}
	_{[2] NO CARRIER}
	_{[3] NO ANSWER}
	_{[4] NO DIAL TONE}

The communications session actually begins here in the next section. The AT commands are issued to the modem and then the dial string is issued with the iiX phone number. The session timer then begins to count 50… 49… 48 etc until one of the CONNECT or NOCONNECT messages from the above list is received.

_{MT-I, Acctid:[999999]}

_{!MT-I, Default
Windows driver.}

_AT&F

_{ATV1E1Q0X4S0=0S7=60S10=50&B1&A0&H1&R2}

_{!MT-I, Dialing:
[9,18007096802]}

_50...

_{|
ATDT9,18007096802 |}

_{49...48...47...46...45...44...43...42...41...40...39...38...37...36...35...34...33...32...31...30...29...28...27...26...25...24...23...22...21...20...}

_{| CONNECT 9600 |}

_{!MT-I, Connected
at 9600}

_{!MT-I, OK.}

_{!MT-D, SEND?0...}

_{!MT-D,
SENT{32}[_]}

_{!MT-D, EXPECT?}

_{!MT-I, Script
Successful.}

At this point, if login is successful, the Welcome Message and the Day Message are displayed. The Welcome identifies the account by name and shows the date and time ( iiX system time ) of the session. The Day Message displays information regarding state MVR delays, service problems, fee changes, and other pertinent information.

_{!MT-I, Login:}

_{iiX DEMO ACCOUNT
LOGGED INTO iiX (036N) AT 08:53:26 07/07/98}

_{WELCOME TO THE
iiX MVR SERVICE}

_{This message was
last changed on 07/07/98 at 08:49:06.}

_{******************************************************}

_{STATE DELAYS}

_{DC--STATE
PROBLEM. MVRS DELAYED UNTIL NOON.}

_{OH,ME--QUICKTIME
SERVICES TEMPORARILY UNAVAILABLE.}

_{RI--STATE
HOLIDAY. MVRS FROM 7/6 DELAYED UNTIL 7/8.}

_{******************************************************}

_{RATE CHANGES
EFFECTIVE 7/1}

_{UT--REGULAR MVRS
4.25}

_{FL--INTERACTIVES:
3 YEAR MVRS 2.16 7 YEAR MVRS 3.16}

_{******************************************************}

This next section shows examples of messages generated when requests are uploaded from the user's system to the iiX Data Center. Make sure to read the Editor's Notes in red!

Each type of request ( MVR, UDI, or A-PLUS ) uploads using a different file name. The files names are:

MVRZRQST.TXT - Standard (not quicktime) MVR requests
MVRZRQQT.TXT - Quicktime MVR requests
UDIZRQST.TXT - Undisclosed Driver (UDI) requests
APLZRQST.TXT - A-PLUS® Property requests

_{1... 0...!MT-I,
Upload: .\OUTBOUND\*.*}

_{!MT-I, Open outfile.}

_{!MT-D, Reset MtOpenoutfile.}

_{!MT-I, Open outfile.}

_{!MT-I, Sending .\outbound\mvrzrqst.txt,rb
(0).}

_{!MT-I, Open outfile.}

_{!MT-I, Sent .\outbound\mvrzrqst.txt
(0).}

_{.\outbound\mvrzrqst.txt
deleted.}

_{Editors note: The lines
!MT-I Sending and !MT-I Sent must be present. If not, an Upload did
not successfully occur.}

_{!MT-I, SZ sent 1
files.}

_{The system
indicates how many request files were sent. This does not indicate how
many requests were in those files!!}

The following message appears in the log and on the user's communications screen if they have requested either Quicktime MVRs, UDI, or A-PLUS.

_{** HOLDING FOR
QUICKTIME REPORTS **}

When the user chooses the option to Send and Receive or the Receive Only option, the software uses a Download process to tranfer information from iiX to the client's PC.

Files that may be downloaded are:

MISCEDIT.TXT - This file downloads each time one of the Receive options is chosen. It does not contain any reports. It updates items like company billing codes, service authorizations, and the company name and address that appears on each report.
STATEDIT.TXT - This file downloads only when iiX updates the downloaded state edit table. This occurs whenever a state makes a change to a license format or other MVR request requirement.
MVRxxxxx.RDC - (where xxxxx represents a series of random letters or numbers). This file contains MVR reports. It is possible for more than one MVRxxxxx.TXT file to download in a single session if standard and quicktime reports are received back at the same time.
UDIZRPTS.RDC - This file contains any Undisclosed Driver Reports.
APLZRPTS.RDC - This file contains any A-PLUS® reports.

The following is an example of the logfile messages that accompany the download process. This particular session downloaded the MISCEDIT.TXT file and an MVR data file (MVR11111.RDC):

_{!MT-I, Download:}
_{!MT-D, Reset MtOpeninfile.}
	_{!MT-I, Receiving mvr11111.rdc,ab (0).}
	_{!MT-I, Received .\INBOUND\TMP\mvr11111.rdc (0).}
_{.\INBOUND\TMP\mvr11111.rdc renamed.}
	_{!MT-I, Receiving miscedit.txt,ab (0).}
	_{!MT-I, Renaming .\INBOUND\TMP\miscedit.txt ().}
_{.\INBOUND\TMP\miscedit.txt renamed.}

_{!MT-I, RZ received 2 files.}

The communications session ends with the following messages.

_{!MT-I, Hangup.}

_{!MT-D, SEND?}

_{!MT-I, Linkstats
Successful.}

_{Communications
Session ended at 8:57:54 AM}

This page has been viewed 13291 times | Document Rating is 2.00 / 5.00 | Last Updated on 4/28/2004 7:08:45 AM