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

ZEN 1.0.0 documentation #66

Open
jp669844 opened this issue Oct 25, 2023 · 1 comment
Open

ZEN 1.0.0 documentation #66

jp669844 opened this issue Oct 25, 2023 · 1 comment
Labels
documentation Improvements or additions to documentation
Milestone

Comments

@jp669844
Copy link

Document ZEN on the docs.zowe.org/

  • basics,
  • usage,
  • features,
  • troubleshooting
@jp669844 jp669844 added the documentation Improvements or additions to documentation label Oct 25, 2023
@jp669844 jp669844 added this to the ZEN 1.0.0 milestone Oct 25, 2023
@skurnevich
Copy link
Collaborator

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.

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

No branches or pull requests

2 participants