I have a lot of blog posts on Zowe. Some are ready to make available, some are works in progress. In the link below, if there is an active link it points to the published topic. If there is no link, it is a place holder.
I do not find the Zowe documentation very easy to use. The documentation expects you to go down a certain path. If you do not follow this path, there is not much to help you. I tend to search the web, get to a page, and then get lost!
The start of the official documentation for server installation is here.
- What is Zowe ? This gives a back ground in modern system architecture, and how Zowe fits into this
- Planning. This provides a road map of the set up you will need to do. For example the security changes may take a week to implement system wide, before customising Zowe.
- Installing and configuring z/OS system definitions.
- Create the security definitions
- Set up message. Messages I have encountered setting up a Zowe instance.
- Configuring a run time instance
- Starting Zowe on z/OS. This starts a minimal system, and helps you check out your definitions.
- Message using Zowe. End user messages I have experienced
- Debugging Zowe
- Setting up a web browser to use Zowe
- Configuring end user userids
- Setting up logon with certificates – TBA
- Which messages to automate
- Using VSCODE with Zowe – TBA
- Problem determination
- What are good tools for working with a backend? – HTTPie.
- Specifying Java overrides
- Zowe on the client
- What should I used on my client to talk to z/OS?
- Zowe client start here
- How to save connection parameters: zowe CLI client configuration files
- Messages when using zowe Command Level Interface(CLI)
- The Zowe cli help command is not helpful!
- Colin’s Zowe CLI options
- Secure store aren’t.
- Setting up vscode before you start, so the editors work
- Zowe explorer
- JSON Web Tokens(JWT)
ColinPaice 