REXX EXIT Exit‑Code Propagation Inconsistency

REXX EXIT statement exit‑code propagation inconsistency after schema change rollback

0 reputation · 26 Dec 2023, 10:26 UTC

122.3K views0

REXX EXIT statement exit‑code propagation inconsistency after schema change rollback

The language specification allows EXIT to return a numeric status, yet each REXX interpreter treats the argument differently, causing inconsistent exit codes when scripts are used for rollback verification.

What is the actual behavior of EXIT 5 on IBM z/OS, OpenRexx and OS/2 REXX, and which configuration changes are required for OpenRexx to propagate the status when invoked indirectly?

Developers can reliably test exit‑code propagation across interpreters before depending on it for rollback operations?

3,650 following

Keep exploring this topic

Rexx LOCK command: unspecified wait duration when NOWAIT omitted

The Rexx LOCK command blocks indefinitely when NOWAIT is not used, but documentation does not define a timeout or retry policy, creating uncertainty for backup and restore scripts.

REXX SIGNAL ON ERROR Deployment Log Triage Failure Policy

REXX SIGNAL ON ERROR deployment-log triage: abort on first trapped error or continue for a complete failure summary?

Schema validation failed after downgrade – can broker auto‑rollback topic schema version?

Can the broker automatically revert a topic’s schema version after a downgrade to avoid DeserializationException?

REXX and DB2: Intermittent Connection Pool Exhaustion Diagnosis

Diagnosing intermittent DB2 thread exhaustion in REXX programs that use DSNREXX or RRSAF. The question focuses on the role of WITH HOLD cursors, explicit COMMIT/ROLLBACK, and DSNREXX thread‑reuse policies.

REXX EXIT statement exit‑code propagation inconsistency after schema change rollback

REXX EXIT statement exit‑code propagation inconsistency after schema change rollback

0 answers

Your perspective belongs here.

0 question comments