-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to run REXX data set members from the Data Sets view #1784
Comments
Thank you for raising this issue. |
How would I upvote this issue? Sounds like a great idea to me. |
Feel free to leave a 👍🏽 on the issue 😋 |
Thank you for raising this enhancement request. |
👍🏽 |
Hello @Joe-Winchester |
Is your feature request related to a problem? Please describe.
PDS members (as well as sequential data sets) can contain REXX scripts.
These can be run using a Zowe TSO command, e.g.
exec 'PDS.PATH{MEMBER}'
which then echos this to the terminalDescribe the solution you'd like
The ability to do a
Run EXEC
directly against the PDS member.This is similar in concept to
Submit JCL
but a little different as the TSO profile needs to be known (which crosses to the other issue of how to associated a TSO profile with a base profile).Additional context
To avoid cluttering of the
Run EXEC
against every PDS menu, maybe there should be a way to limit this to data sets that have justREXX
in their path, however the same argument goes for submitting JCL that it on every pop-up including COBOL or HLASM (or REXX) or other files that have no valid JCL in them. Maybe there needs to be a way to associate file paths with file types in the settings.json that would allow users to specify which PDS naming rules contain JCL or REXX.By comparison, in ISPF 3.4 a user can type
EX
against a member that runs the TSO exec (and likewise SUB that does a JCL submit).The text was updated successfully, but these errors were encountered: