TQ Tool - RIO Transmit Queue File Viewer

View, analyze, and send records from RIO TQ files with full TLOG and Non-TLOG support

About the TQ Tool

The TQ Tool is a comprehensive viewer and testing utility for RIO Transmit Queue (TQ) files. It allows you to inspect individual records in TQ files, view parsed TLOG transactions, analyze EPSLOG data with field-level details, and send records directly to your RIO Server for testing. Supports all TQ record types: TLOG (999), Non-TLOG (996), EPSLOG (995), and TAX (994).

What are TQ Files?

RIO Transmit Queue (TQ) files contain queued records waiting to be sent to the RIO Server. Each record in a TQ file has a standardized 24-byte header followed by variable-length payload data. TQ files can contain multiple record types:

MsgType Name Description
999 TLOG IBM/Toshiba transaction log records (binary TLOG data)
996 Non-TLOG Generic non-transaction data (configuration files, reports, etc.)
995 EPSLOG EPS (Electronic Payment System) log records with FID-based fields
994 TAX Tax configuration data (alternating key/value pairs)

Choose a TQ Workflow

Open the top-level TQ Tool tab beside Keyed File. Choose the action that fits your task:

ActionUse it to
Browse & Parse / drop a fileLoad a queue into the record viewer, filter it, inspect payloads, and select records.
Scan File IntegrityReview valid segments, corruption gaps, and collection delay without populating the record list.
Export TQ Tlog DataExtract dated TLOG files into a ZIP directly from a queue without loading the viewer.
Compare two TQ filesCompare two independent queues by exact payload occurrences, with PDF and CSV reports.

Key Features

Scan File Integrity and Collection Delay

Scan File Integrity walks a TQ or NTQ file without loading every record into the list. Use it for very large files and for files that contain a corruption gap. The report shows recovered segments, corruption gaps, and collection delay.

Select a file when prompted. When the report is ready, use Export PDF to save it, or Load Scanned File In Viewer to browse the scanned file. A scan reports corruption; it does not repair the queue.

Collection delay is the TQ header collection time minus the clock inside the record. A record is late when that delay is greater than the threshold. The default threshold is 120 seconds. Change the Delay threshold field beside the scan button before the scan, or after a scan to recalculate the same file.

For each compared type the report shows how many records had an event clock, how many did not, the minimum, average, and maximum delay, and how many records exceed the threshold. It then lists the 10 slowest records with TQ record number, file offset, string key, terminal, transaction, source file (tlog) or EPSLOG source record (srcRecNo), collected time, event time, and delay. When more than 10 records exceed the threshold, the report also lists those late records (up to the 250 slowest). Click a heading in that table — Record, Offset, Identity, Collected, Event, or Delay — to sort by it. Click the same heading again to reverse the order.

TQ integrity scan with collection delay summary and slowest records
Integrity scan with synthetic TLOG records and a 120-second delay threshold. Select the image to view it at full size.

File Loading & Parsing

Drag and drop or select RIO TQ files for instant parsing. TLOGic automatically:

Record List View

Browse all records in the TQ file with a comprehensive list showing:

Search & Filter Records

Message-type pills show each type's name, number, and count in the whole file. All types start active; click a pill to hide or show that type. The pills combine with your text filter. Enable all resets the pills; Clear resets both the pills and text. Additional numeric types in the file appear automatically.

Click the question-mark button for the styled search reference, including message types and their counts.

Quickly find specific records using powerful filter syntax:

Combine filters with spaces, for example rec:1..100 mt:995. Record numbers always refer to the original file, even after filtering. No matches shows an empty list and zero counts.

The list displays 100 records per page by default; choose 50, 100, or 250 rows, move between pages, or enter a page number. Filtering searches the entire file. Select All Matches and Invert Matches apply to all matching pages. Checked records stay selected across page and filter changes; Deselect All clears them.

Detailed Record View

Click any record to view comprehensive details in expandable sections:

TQ record list with message-type pills, record-number search and page controls
Record numbers retain their original file positions when filtering. Synthetic queue example. Select the image to view it at full size.

Compare Lab and Prod TQ Files

Open Compare two TQ files in the TQ Tool, select File 1 and File 2, and optionally give each a report label such as Lab or Prod. Click Compare files. Comparison runs locally in your browser and is independent of the file loaded in the viewer and its filters.

For example, File 1 with payloads A, B, A and File 2 with A, A, B has three matched pairs. If File 2 has only A, B, one occurrence of A remains Only in File 1. A changed payload appears as unmatched records, rather than a field-by-field difference between assumed counterparts.

A match requires the same message type and exactly the same payload bytes anywhere in the other file. Record positions, TQ headers, collection timestamps, and subheaders do not affect matching. Dates, terminals, transaction numbers, and other values inside the payload do affect matching. Duplicate payloads are counted separately: each occurrence can match only one occurrence in the other file.

The report shows matched record pairs, records only in File 1, records only in File 2, and totals by message type. Unmatched records are not assumed to be counterparts based on position. Choose Matched pairs or Differences, page through the results, and select Inspect to see full payload bytes and the original record numbers and file offsets. For TLOG (999) records, Inspect also shows the transaction summary and strings; click a string to expand its field names, types, display values, and hex values. Raw payload bytes remain available if parsing fails.

Download PDF and Download CSV include all matched pairs and at most 1,000 unmatched record details combined across both files, with both files represented when possible. Totals cover the entire files even when details are omitted. Payload previews in the reports are limited to 48 bytes; the UI inspection shows the full payload.

Partial TQ records are compared individually, not reassembled. Different fragmentation can therefore produce unmatched records. Incomplete records or invalid record/subheader lengths stop comparison with a file and byte-offset error; use Scan File Integrity to investigate.

TQ comparison summary and unmatched records for Lab and Prod example queues
Order-independent comparison of synthetic queues. The report separates matched pairs from records with no exact counterpart. Select the image to view it at full size.
Comparison Inspect view with an expanded StoreClose string showing field names, types, display values and hex
Inspect a TLOG payload and expand a string to see its fields. This synthetic example is a store-close record, so terminal and transaction are N/A. Select the image to view it at full size.

Cancel stops a running comparison. Clear comparison resets its file selections and results. Changing either input file or report label invalidates the old report; click Compare files again. Comparison does not replace the file in the record viewer.

Record Type Parsing

TLOG Records (MsgType 999)

TLOG records contain binary IBM/Toshiba transaction data. The TQ Tool:

Tip: A complete TLOG payload can be inspected as transaction strings and expanded into fields. Queues can also contain partial records (F/M/L); these are displayed separately and are not automatically reassembled, so parsing may fall back to raw hex.

Non-TLOG Records (MsgType 996)

Non-TLOG records contain generic data like configuration files, reports, or custom data. The TQ Tool:

EPSLOG Records (MsgType 995)

EPSLOG (Electronic Payment System Log) records use a sophisticated FID-based format with 204 defined fields. The TQ Tool provides comprehensive parsing:

EPSLOG Header Parsing

The TQ Tool parses the complete EPSLOG structure:

EPSLOG FID Table Display

Each FID (Field ID) is displayed in a comprehensive table with:

Column Description
FID Field ID in hex format (e.g., 0x42)
Field Name Human-readable name (e.g., "TotalAmount", "Track2", "XMLUserDataRequest")
Type Data type badge: A (ASCII), H (Hex), P (BCD), I (Integer), C (Character)
Value Type-specific formatted value (see formatting below)
Raw Hex Complete hex representation of field data

Type-Specific Field Formatting

Type Description Example
A ASCII - Printable text, null-terminated, XML preserved <HighRiskItemsPresent>true</HighRiskItemsPresent>
H Hex - Binary data as hex string A1 B2 C3 D4
P BCD - Binary Coded Decimal to numeric string 12345 from 12 34 50
I Integer - Little Endian 1/2/4-byte integer, amounts formatted as currency $46.60 from raw value 4660
C Character - Single character with hex value or just hex for non-printable 'X' (0x58) or 0x00
Supported EPSLOG Fields: The TQ Tool recognizes all 204 standard EPSLOG fields including MessageType, Terminal, TransactionNumber, TotalAmount, Track2, EMVTagData, XMLUserDataRequest, and many more. Unknown FIDs are displayed as "Unknown" with best-effort interpretation.

TAX Records (MsgType 994)

TAX records contain tax configuration data stored as alternating key/value pairs. The TQ Tool:

Sending Records to RIO Server

Testing Feature: The TQ Tool allows you to send individual records or batches directly to your RIO Server for testing. This is useful for validating server behavior with specific TQ file data.

Sending Options

The TQ Tool provides multiple ways to send records:

RIO Configuration

Click the Config button to set up your RIO Server connection:

Setting Description
Service URL Your RIO Server endpoint (e.g., https://rio.example.com/trickle/file)
Store Number Store number to use in RioRequest messages
Division Division code for RioRequest
Format Format identifier (defaults to 'GENERIC' if not in SubHeader)
UTC Offset Timezone offset (e.g., -05:00)
Basic Auth Optional username/password for HTTP Basic Authentication

Send Results & Tracking

After sending records, the TQ Tool displays detailed results:

Export Features

Export Options

Extract Dated TLOG Files

  1. For the loaded queue, set the desired message-type and text filters, then click Extract TLOG. To process a separate file in full, click Export TQ Tlog Data on the landing card and choose that file.
  2. Review the preview's filenames, date sources, record counts, and sizes. A repeated TLOG name after another name starts a separate run; dates alone do not split a run.
  3. Download the ZIP and unzip it. Load an individual .tlog file in TLOGic for transaction analysis or validation.

Selection matters: Raw Binary exports checked records (including checks retained on other pages or hidden by filters). Extract TLOG uses matching TLOG records from the active viewer filters, regardless of checkboxes. The direct Export TQ Tlog Data action processes the selected queue in full.

TLOG ZIP export preview listing dated EAMTRANA and EAMTRANB files, date sources, record counts and sizes
Review each dated TLOG file before selecting Export. Synthetic queue example. Select the image to view it at full size.

Common Use Cases

Debugging RIO Integration

  • Inspect exact record structure sent to RIO Server
  • Validate CRC checksums
  • View SubHeader properties (ftype, fname, totrecs)
  • Send problematic records individually to isolate issues

Testing Specific Scenarios

  • Filter to specific MsgTypes for targeted testing
  • Test EPSLOG payment records with XMLUserDataRequest
  • Validate TLOG transaction parsing
  • Test partial record handling

Data Validation

  • Verify all records have valid CRC checksums
  • Check for missing or corrupted SubHeaders
  • Validate EPSLOG FID data formatting
  • Ensure proper timestamp formatting

Analysis & Exploration

  • View distribution of MsgTypes in TQ files
  • Analyze payload size statistics
  • Explore EPSLOG field usage (which FIDs are present)
  • Examine date ranges and collection patterns

Best Practices

Tips for Success
Important Notes