Validate transaction data against configurable rules to catch missing or invalid fields before they cause processing errors.
TLOGic's TLOG Validation tool checks individual transactions or the entire loaded file against a set of configurable rules. It is designed to catch data quality issues like missing fields, empty values, and invalid data that can cause downstream processing errors such as NullPointerExceptions (NPEs) and incorrect POSLOG output.
The default rules were generated from the ACE Albertsons transaction mapping configuration, covering 30+ string types and 150+ field checks. This provides comprehensive out-of-the-box validation for most IBM TLOG implementations.
In addition to rule-based validation, TLOGic also includes a Scan Structure action for file-wide structural review. Use it when you want to inspect transaction boundaries, malformed data windows, duplicate transactions, or incorrect NumStrings values across the entire loaded file.
TLOG Validation is available to Trial (full access during 14-day trial) and Professional license holders. It is not available with the Standard license.
The rule warn 00:6 num_strings_match compares the header's NumStrings value with the parsed string count, excluding the 00 header and 20 strings (including 20xx types). A mismatch is an error for Trantype 00 (SALE) and a warning for all other transaction types, with both counts shown, for example: declared 21, parsed 7. Missing or unreadable NumStrings values use the same severity; missing or unreadable transaction types receive warnings.
This condition determines severity from the header's Trantype, including for existing saved rules. It runs in both single-transaction and all-transaction validation. Use the num_strings_match issue type and the severity filter to focus on errors or warnings.
Click Validate All in the Transaction List header beside Scan Structure, or Validate All Transactions at the bottom of the validation side panel. Both check every transaction in the loaded TLOG, including records hidden by search, field filters, or the hide-20 option. You do not need to select a transaction first when using the list-header button.
Hiding an issue type or exporting shown results does not change the rules or repair the file. A view with no matching issues may simply have every issue filtered out; use Show all / Reset to check.
Click Scan Structure in the Transaction List header to scan the entire loaded TLOG for structural anomalies. This is different from the normal Validate button: the validation workflow checks string and field rules, while Scan Structure focuses on whether the file layout itself looks correct.
NumStrings mismatches — header string 00 says a transaction should contain more or fewer strings than were actually parsed00 transactions — exact raw duplicates of normal transactions; 0x20 family duplicates are intentionally not flagged00, 20*, and 21. Any other top-level transaction key is shown as Unknown in the scan results and transaction list.
NumberOfMatchingItems must agree with complete ordinal, discount, and price groups across 99:F0:21 and its consecutive 99:F0:22 continuations. Matching ordinals must exist in the same transaction's 01:ORDINAL fields; integer comparison accepts leading zeroes. Orphan continuations are reported. The rule exempts standalone manufacturer coupons when the preceding 01:INDICAT3 equals 65.99:F0:F0:4) and gift-card ApprovalCode (99:F0:96:16) are warnings. The electronic-payment ApprovalCode check (16:19) is disabled in the defaults; an already-enabled legacy check is migrated to warning.Saved rules are migrated when required defaults change. The migration updates these legacy severities without enabling commented ApprovalCode checks or changing unrelated custom rules. Review Edit Validation Rules to see your active rules.
Validation rules use a simple domain-specific language (DSL). Each rule is a single line with the following syntax:
[SEVERITY] STRING_KEY:FIELD_SELECTOR CONDITION [ARGS...]
| Component | Description |
|---|---|
| SEVERITY | error or warn. Defaults to error if omitted. |
| STRING_KEY | The TLOG string key (e.g., 00, 11:BD, 99:10:F5) |
| FIELD_SELECTOR | A schema field name such as ORDINAL, or a 1-based field number for legacy rules. Field names are recommended because they do not depend on fixed positions. |
| CONDITION | The validation condition to apply (see Available Conditions below) |
| ARGS | Optional arguments required by some conditions |
Lines starting with # are comments and are ignored during validation.
| Condition | Args | Description |
|---|---|---|
not_empty |
— | Field must exist and have non-empty data |
not_null |
— | Field index must exist in the string |
numeric |
— | Field display value must be a valid number |
min_length |
N | Field hex must be at least N hex characters |
valid_date |
FORMAT | Field must match date format (e.g., YYMMDDhhmm) |
matches |
REGEX | Field display must match the regex pattern |
in |
V1,V2,... | Field display must be one of the listed values |
range |
MIN MAX | Numeric value must be within [MIN, MAX] |
min_fields |
N | String must have at least N fields |
num_strings_match |
— | On header 00:6, compares NumStrings with the parsed count excluding the 00 header and 20-family strings. Severity depends on Trantype. |
equals |
VALUE | Field display must exactly equal VALUE |
exists_in |
STRING_KEY:FIELD_SELECTOR [options] | Field value must exist in the referenced field of the same transaction. It can validate counted groups spanning a primary string and continuation strings. |
exists_in ArgumentsThe first argument identifies the target field whose values are valid. All remaining arguments are optional unless noted below.
| Argument | Description |
|---|---|
compare=integer |
Compares numeric values after removing leading zeroes. For example, 005 matches 5. The default is exact text comparison. |
count=FIELD_SELECTOR |
Reads the declared number of repeating sets from a field on the primary string. A missing, nonnumeric, or mismatched count produces an error. |
group=FIELD1,FIELD2,... |
Names every field required in one complete repeating set. The validator confirms that each named field occurs exactly the number of times declared by count. |
continuations=STRING_KEY |
Adds consecutive continuation strings immediately following the primary string to the same counted series. A continuation without its primary string is reported as orphaned. This argument requires count and group. |
unless previous(KEY):FIELD equals VALUE |
Skips the entire relationship check when the nearest preceding string with KEY contains VALUE in the selected field. |
every=N |
Applies a numeric source-field selector repeatedly at an interval of N fields. This remains available for simple positional rules; counted named groups should use count, group, and continuations. |
99:F0:21 contains the first matching-item set. Its immediately following 99:F0:22 string contains matching items 2 through N. NumberOfMatchingItems declares the total number of sets across both strings.
# Transaction header: Terminal must exist error 00:2 not_empty # Terminal # Item: ExtendedPrice must be numeric warn 01:3 numeric # ExtendedPrice # Coupon association: ItemCodeForCoupon must not be empty error 11:BD:7 not_empty # ItemCodeForCoupon # EPE item 1 is in 99:F0:21; items 2 through N are in 99:F0:22. # Validate every complete set declared by NumberOfMatchingItems. # Exempt standalone manufacturer coupons whose preceding item type is 65. error 99:F0:21:MatchingItemOrdinalNumber exists_in 01:ORDINAL compare=integer count=NumberOfMatchingItems group=MatchingItemOrdinalNumber,MatchingItemDiscountAmount,MatchingItemPrice continuations=99:F0:22 unless previous(01):INDICAT3 equals 65 # Comment out rules with # #warn 00:11 not_empty # RingTime (disabled)
Click Edit Validation Rules at the bottom of the offcanvas to expand the rule editor. From here you can modify the ruleset to match your specific TLOG format and processing pipeline.
An error means a rule requiring attention failed. Some checks identify missing fields used without null/empty protection in the ACE mapping; others check SALE string counts or EPE item relationships. Investigate the reported field and condition against your mapping before processing the data.
A warning identifies data to review, such as missing AgeDate or ApprovalCode values, or a NumStrings mismatch on a non-SALE transaction. A warning is not proof that downstream processing will succeed; its impact depends on your mapping and transaction type.
| License | TLOG Validation Access |
|---|---|
| Trial | Full access during 14-day trial period |
| Professional | Full access |
| Standard | Not available |