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?
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 viatsocmd "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?