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

Should we log CEE RUNOPTS? #111

Open
1000TurquoisePogs opened this issue Apr 26, 2024 · 1 comment
Open

Should we log CEE RUNOPTS? #111

1000TurquoisePogs opened this issue Apr 26, 2024 · 1 comment
Assignees

Comments

@1000TurquoisePogs
Copy link
Member

CEE runopts customizations have time and time again caused startup and runtime issues.
We should review them when a user has some error that seems environmental.

zwe support now collects the cee runopts of the user who runs it via tsocmd "OMVS RUNOPTS('RPTOPTS(ON)')"
But, the person who runs that may not be the STC account where the issue occurs.
It'd be better if Zowe prints the runopts at startup, as early as possible.
That would mean the launcher.
Is it a good idea to print the runopts every startup? Or only under ZLDEBUG?

@JoeNemo
Copy link
Contributor

JoeNemo commented May 8, 2024

This can be expensive when done as TSOCMD. Is there anyone to do this programmatically to make this not have a process fork minimum cost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants