- Where the compiler/library is likely to be selected:
- When a significant REXX automation estate must remain on-platform and there is a need for control over packaging and runtime behavior.
- When distributing compiled REXX programs to other LPARs or customers is required (Alternate Library distribution).
- Where alternatives may be preferred:
- Interpreted REXX: operational simplicity and ubiquity for ops scripts and quick tooling.
- Python/ZOAU: suitability for integration with modern CI/CD, REST APIs, and a larger talent pool.
- Market trend context:
- IBM’s broader messaging has emphasized AI acceleration and modernization for IBM Z. Budget and strategic attention in some organizations may prioritize modernization workstreams; however, existing REXX estates remain operationally important in many enterprises.