Skip to content
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

Run Edit Macros from Zowe Explorer #2415

Open
CexyChris opened this issue Aug 9, 2023 · 1 comment
Open

Run Edit Macros from Zowe Explorer #2415

CexyChris opened this issue Aug 9, 2023 · 1 comment
Labels
community-upvoted enhancement New feature or request priority-low Legit issue but cosmetic or nice-to-have Research Needed

Comments

@CexyChris
Copy link

When I am editing a member in VS Code I still need to switch to ISPF whenever I want to run an Edit Macro. These context switches are very unfortunate and for me personally they are a major showstopper for adoption of Zowe Explorer, since I will just continue editing in ISPF afterwards.

I'd like to run an Edit Macro on the Data Set or Member I am currently editing. A possible solution would be an additional option in the context menu of the DATA SETS List "Run Edit Macro...", which then prompts you for the name of the macro to be run. The resulting changes should then of course be instantly visible in the editor without further user interaction.
One would need to allocate a macro library, so either the person editing needs a TSO session and the library has to be part of a fitting concatenation or maybe configuration of Zowe could be extended to provide a concatenation of macro libraries to be allocated as needed.
The alternatives to enabling Edit Macros in Zowe Explorer are to either stick to ISPF Edit or throw away about 50 years worth of well tested, proven-to-work macros.

@CexyChris CexyChris added the enhancement New feature or request label Aug 9, 2023
@github-actions
Copy link

github-actions bot commented Aug 9, 2023

Thank you for raising this enhancement request.
The community has 90 days to vote on it.
If the enhancement receives at least 10 upvotes, it is added to our development backlog.
If it receives fewer votes, the issue is closed.

@JTonda JTonda added community-upvoted priority-low Legit issue but cosmetic or nice-to-have Research Needed labels Jan 9, 2024
@JTonda JTonda moved this from New Issues to Low Priority in Zowe Explorer for VS Code Jan 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community-upvoted enhancement New feature or request priority-low Legit issue but cosmetic or nice-to-have Research Needed
Projects
Status: Low Priority
Development

No branches or pull requests

2 participants