Debugging Rexx: Resolving Undefined Variables and Parsing Logic Failures

The Problem: Silent Logic Failures

In many languages, referencing an uninitialized variable triggers an immediate crash or a "null pointer" exception. Rexx behaves differently: it treats any uninitialized variable as an empty string. While this prevents immediate crashes, it often masks critical logic failures, leading to scripts that run to completion but produce incorrect results or fail only when an empty string is passed to a mathematical operator.

Diagnostic Matrix: Common Failure States

Symptom	Likely Cause	Diagnostic Indicator
Unexpected "Syntax Error"	Unmatched quotes or missing commas	Interpreter stops before execution begins
Arithmetic Error	Uninitialized variable used in calculation	Variable was treated as "" (empty string)
Truncated Data	Incorrect PARSE logic	Last variable in PARSE list is empty or partial
Erratic Variable Values	Global scope collision	Variable changes value after calling a subroutine

Step-by-Step Diagnostic Workflow

Follow these checks in order to isolate where the data flow is breaking.

1. Enable Runtime Tracing

Before adding manual print statements, use the built-in trace facility. This reveals exactly how the interpreter evaluates expressions and assigns variables.

/* Run this command at the start of your script or in the interpreter console */
TRACE R

Expected Result: The interpreter will output every instruction executed and the resulting value of every variable assignment to the standard output. If a variable is unexpectedly empty, the trace will show it as variable = "".

2. Inspect Parsing Boundaries

The PARSE instruction is the most common source of "missing" data. If you are parsing a string and the final variable is empty, you likely have a trailing delimiter issue.

Example Scenario: Parsing a comma-separated string "John,Doe,Engineer".

/* Potential Bug: Using a fixed number of variables without checking the remainder */
input = "John,Doe,Engineer"
PARSE VAR input name surname job
/* If 'input' was "John,Doe,", 'job' becomes an empty string without warning */

The Fix: Always verify the contents of the final parsed variable using SAY or check the length of the input string before parsing.

3. Detect Variable Collisions

Because Rexx variables are global by default, a subroutine that uses a common variable name like i or line will overwrite that variable in the calling routine.

Diagnostic Check:

1. Place a SAY "Before: " i before a subroutine call.
2. Place a SAY "After: " i immediately after the call.
3. If the values differ and you did not explicitly change i, you have a scope collision.

Corrective Actions

Fixing Syntax Errors

If the interpreter reports a syntax error, check for these specific patterns:

• Argument Lists: Ensure all arguments in a function call are separated by commas.
• String Literals: Ensure every opening quote has a matching closing quote on the same line (unless using continuation characters).

Preventing Undefined Variable Math Errors

To prevent a script from failing during a calculation, initialize your numeric variables explicitly or use a validation check.

/* Safe initialization */
count = 0

/* Validation check before math */
IF VALUE(count) = "" THEN DO
  SAY "Error: count is not initialized"
  EXIT
END

Verification and Limitations

To verify the fix, run the script with TRACE R enabled and confirm that the variable assignments match your expected logic. Use SAY statements immediately following PARSE or PULL instructions to ensure data is captured correctly.

Limitations:

• Case Sensitivity: Rexx is case-insensitive. If your script passes variables to an external shell command (e.g., via ADDRESS SYSTOOLS or ADDRESS CMD), the external system may treat "Variable" and "variable" as different entities, leading to "File Not Found" errors that Rexx cannot detect.
• Performance: In older interpreters, excessive use of the concatenation operator (||) in large loops can degrade performance. Consider using QUEUE PUSH and QUEUE PULL for building large strings.

Rollback Procedure

If the TRACE R command produces too much output for your logs, disable it by running:

TRACE OFF