Skip to content

New Project Proposal - Lua/TSO — scripting platform for z/OS (System REXX replacement) #972

@drblez

Description

@drblez

Project description

Lua/TSO — scripting platform for z/OS (System REXX replacement)

Lua/TSO is a scripting platform for z/OS aimed at replacing system REXX for automation. It provides a Lua VM with host APIs for TSO/ISPF/datasets/AXR and TLS via System SSL, designed to work with datasets and core z/OS services.

Statement on alignment with Open Mainframe Project Mission and Vision statements

Lua/TSO aligns with the Open Mainframe Project mission by advancing open‑source tooling for z/OS automation and lowering barriers to mainframe development. It modernizes system scripting by providing a Lua‑based platform that integrates with core z/OS services (TSO/ISPF/AXR) and supports secure connectivity via System SSL. The project encourages community collaboration around reusable automation and modern developer workflows on z/OS.

Are there similar/related projects out there?

Related projects include System REXX (the current standard for z/OS automation), Zowe (modern CLI/REST/UI access to z/OS), and ZOAU utilities used from higher‑level languages. There are also Lua/Python/Perl ports for z/OS USS, but they target the Unix subsystem rather than direct TSO/ISPF/dataset integration.

Sponsor from TAC

To be appointed

Proposed Project Stage

Sandbox

License and contribution guidelines

License: Apache-2.0. Contribution guidelines: see CONTRIBUTING.md (issues + pull requests welcome).

Current or desired source control repository

https://github.com/drblez/luaz

External dependencies (including licenses)

None at the moment (no external dependencies in the repository yet). Target platform dependencies are standard z/OS components (TSO/ISPF/AXR, System SSL), which are part of IBM z/OS.

Initial committers

Initial committers: drblez (Ruslan Stepanenko)
How long: since January 2026
Extent of contributions: 1 initial commit (repo initialization + RFC + licensing)
Diversity of community: currently single‑maintainer, no multi‑org contributor base yet.

Infrastructure requests

No special infrastructure is required at this time. Just only standard MF for my membership level

Communication channels

GH, email [email protected], Telegram @drblez

Communication channels

GH

Website

https://github.com/drblez/luaz

Release methodology and mechanics

No releases yet. Planned methodology: semantic versioning with Git tags, GitHub Releases, and a short changelog per release.

Social media accounts

https://blog.drblez.ru/
https://www.instagram.com/drblez

Community size and any existing sponsorship

Just one )))

Metadata

Metadata

Assignees

No one assigned

    Labels

    mainframe-infra-requestRequest for Mainframe Infrastructure resources

    Type

    No type

    Projects

    Status

    Infrastructure Requests

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions