Getting started with z/OS Cloud Broker and z/OS Package Manager
Installing and configuring IBM z/OS Cloud Broker and z/OS Package Manager is required if you are installing suboperators on z/OS. To get started with z/OS Cloud Broker and z/OS Package Manager rapidly, z/OS system programmers and cloud administrators can refer to the following roadmap. To see the steps as a diagram, see Workflow.
| Step | Action | More information |
|---|---|---|
| 1 | Plan your installation and configuration requirements. | Ensure that you meet the following storage, hardware, and software requirements for both z/OS Cloud Broker and z/OS Package Manager: |
| 2 | Prepare to install IBM Z and Cloud Modernization Stack. | To prepare for installation, refer to one of the following topics depending on whether your cluster is connected to the internet: |
| 3 | Install and configure z/OS Cloud Broker. | To install and configure z/OS Cloud Broker, complete both of the following tasks: |
| 4 | Install z/OS Package Manager. | See Installing z/OS Package Manager |
After you have successfully installed z/OS Cloud Broker and z/OS Package Manager, you can install on z/OS the suboperators that are part of IBM Z and Cloud Modernization Stack. The getting started roadmaps of the suboperators are listed below:
Note: Beginning with z/OS Package Manager suboperator v2.0 and the z/OS Cloud Broker v2.2, individual product suboperators are no longer required. You can directly install z/OS product OCI artifacts by using z/OS Package Manager suboperator v2.0.
- Getting started with C/C++ for Open Enterprise Languages on z/OS
- Getting started with Open Enterprise SDK for Go
- Getting started with Open Enterprise SDK for Node.js
- Getting started with Open Enterprise SDK for Python
- Getting started with Z Open Automation Utilities
For 64-bit SDK for z/OS®, Java™ Technology Edition, use the roadmap for Python as a guide.