You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feedback on what could be documented / described better
Space requirements and Permissions for Zowe Convenience builds, though more informative than last year, are still unclear.
- 1300MB is suggested as required space for runtime directory in USS but doesn't seem to suggest recommended values for pax file, product libraries and configuration datasets.
- Documentation doesn't provide any troubleshooting steps to resolve when errors occur.
e.g. One time, my ZFS dataset wasn't big enough for the USS mount I was using. I had to revert to deleting all the datasets created by the zwe until the point of error, recreate ZFS and start over again.
- Even when datasets were created by zwe, zwe stc failed due to access issues when copying procs to JCLLIB etc. Documentation/Help was missing on how to resolve this situation.
- Even when I used my own mainframe id for provisioning zowe, I was unable to delete some datasets created by zwe scripts.
- Information was missing on how I can know which ID holds the permissions or what I need to do so datasets are deleted.
- Documentation is not clear on permissions required for each of the zwe init sections. Like zwe certificate requires permissions of a security administrator on the other hand zwe datasets require MVS access (read/update). On a customer site, tasks may need inputs or permissions involved - System Admin, Security Admin, Network Admin, etc.
Document ZEN on the docs.zowe.org/
The text was updated successfully, but these errors were encountered: