Easytrieve Testing Functions

Why Validate Before Process

Batch jobs imply trust: every record matches FILE layout. Reality violates trust daily. Optional fields arrive blank. Interface files pad numeric fields with spaces. Hex low-values mean uninitialized in one system and valid sentinel in another. Testing functions express business rules in one readable IF instead of twenty lines of byte inspection PROC. Fail fast on read—detect bad row before adding GROSS to DEPT-TOTAL. Operations teams prefer exception reports with row keys over ABEND codes requiring restart from top.

Numeric Class Tests

Numeric testing asks whether every byte in a field is a valid digit (and sign nibble for packed types) before ADD or MULTIPLY. Typical pattern: IF NOT NUMERIC-TEST(AMOUNT) PRINT BAD-NUM-RPT—exact function name from your manual. Without builtin, shops compare each byte or MOVE to test field with REDEFINES. Numeric test on display N field differs from packed P—define tests on the type actually read from file. Implied decimal does not affect digit validity; 999.99 storage still must be numeric nibbles throughout.

1
2
3
4
5
6
7
JOB INPUT INFILE
  IF NOT NUMERIC(AMOUNT)
     ERROR-CODE = 10
     PRINT NUM-EXCEPTION
  ELSE
     DEPT-TOTAL = DEPT-TOTAL + AMOUNT
  END-IF

Alphabetic Class Tests

Name, address, and status code fields often require letters only—or alphanumeric without punctuation. Alphabetic test functions return false when digits or special characters appear. Use before concatenating names for mail merge output. Case sensitivity follows collating rules; test documentation for whether lowercase a-z allowed on your code page. Contrasts with numeric test: a field cannot pass both unless test definitions allow alphanumeric subset explicitly documented.

Blank and Empty Detection

Blank test treats spaces as empty—critical for A fields where SPACES fill unused length. IF BLANK(NAME) flags missing employee name on hire record. Distinguish blank from LOW-VALUES: hex 00 may not display as space but still fails business not-empty rule. Some manuals provide separate tests; others require IF NAME EQ SPACES OR NAME EQ LOW-VALUES. Document site convention in program header when both sentinels appear in feeds.

Combining Tests With Relational Operators

Class test first, range second: IF NUMERIC(AMT) AND AMT GT 0 AND AMT LT 999999.99. Short- circuit logic saves CPU when first failure skips expensive table lookup. NOT wraps test: IF NOT BLANK(REMARK) processes only rows with comment text. Avoid double negative without parentheses—IF NOT NOT NUMERIC is confusing in maintenance review.

Exception File Pattern

Define EXCEPTION-FILE in Library mirroring input layout plus ERROR-CODE field. On test failure, MOVE input record to exception buffer, set code, PUT or PRINT to exception. Good records continue main path. Reconciliation job counts ERROR-CODE frequencies for operations dashboard. Testing functions make IF condition readable; ERROR-CODE documents which test failed for support staff.

Testing Versus DEFINE Types

DEFINE type P declares intent that field holds packed decimal; testing verifies runtime content matches intent. Compiler cannot know upstream file corruption. Do not skip tests because FILE definition looks correct—interfaces change without notice. Conversely, passing numeric test does not guarantee business correctness—AMOUNT numeric but negative when policy requires positive still needs IF AMT LT 0 after class test.

Performance on Large Files

Per-record test cost is tiny versus READ. Testing every field on wide copybook records adds up—test only fields participating in math or mandatory output. Hoist invariant tests when field not used in inner loop. Million-row files still I/O bound; readable validation beats bare ADD that ABENDs hour three of batch window.

Procedural Fallbacks Without Builtins

1. IF FIELD EQ SPACES for blank alphabetic detection.
2. DO WHILE loop with INDEX over OCCURS 1 A inspecting each byte.
3. MOVE to numeric work field inside IF NUMERIC-style PROC returning flag.
4. CALL external validation routine when builtins missing on older compile level.

Common Testing Mistakes

• Testing display field while file supplies packed—or reverse.
• Assuming blank test trims trailing spaces on fixed fields automatically.
• Skipping validation on trailer records assumed safe.
• Using edited A field in numeric test after FORMAT corrupts class.
• One ERROR-CODE for all failures—support cannot diagnose without distinct codes.
• Testing after ADD already corrupted accumulator on bad row.

Explain It Like I'm Five

Testing functions are bouncers at a party. Before someone enters the dance floor for math games, the bouncer checks their ticket—is it a real number ticket, a name ticket, or empty? Wrong ticket goes to the help desk line instead of breaking the dance floor. Easytrieve uses bouncers so one bad ticket does not ruin everyone's counting game.

Exercises

1. Write IF pseudocode routing non-numeric AMOUNT to exception before ADD.
2. Explain blank versus LOW-VALUES on A 10 name field.
3. Design ERROR-CODE values for numeric, blank, and range failures.
4. Order tests for IF on AMOUNT: numeric, positive, under ceiling.
5. Describe procedural fallback when NUMERIC builtin unavailable.