Managed node

The managed z/OS node is the host that is managed by Ansible, as identified in the Ansible inventory. The managed node has dependencies that are specific to each release of the IBM z/OSMF collection. Review the details of the dependencies before you proceed to install the IBM z/OSMF collection.

• z/OS: V2R3 or later

  The target z/OS systems should be configured as the target hosts (managed nodes) in your playbook. The z/OSMF collection drives z/OSMF REST APIs remotely by default. This is done by specifying delegate_to: localhost statement in your playbook or roles in this collection. With this remote approach, it is not necessary to set up SSH and install Python on the target z/OS systems.

• z/OSMF server

  The z/OSMF server must be installed and active on at least one z/OS system in the same sysplex. Information about the z/OSMF server must be configured in the inventory file or in the vars file, such as the hostname, port number, and authentication info. The authentication info to connect to the z/OSMF server is provided when running playbook or it will be prompted during playbook run. You can specify the same z/OSMF server for multiple z/OS managed nodes in the same sysplex.

• z/OSMF Workflow

  z/OSMF Workflow is a plugin of z/OSMF which provides a framework to streamline z/OS tasks. To interact with z/OSMF Workflow in your playbook, it requires you to setup z/OSMF Workflow properly in z/OS managed nodes. Typically, you setup z/OSMF Workflow as a plugin of one z/OSMF server in each sysplex.

  This dependency is only required for using the following roles or modules:

  • module: zmf_workflow

  • role: zmf_workflow_complete

  • role: zmf_cpm_provision_software_service

  • role: zmf_cpm_manage_software_instance

  • role: zmf_cpm_remove_software_instance

• Cloud Provisioning and Management (Optional)

  Cloud Provisioning and Management (CP&M) can be used to provision and Manage z/OS Software Instances. To interact with CP&M in your playbook, it requires you to set up CP&M properly in z/OS managed nodes. Typically, you setup CP&M as a plugin of one z/OSMF server in each sysplex.

  This dependency is only required for using the following roles or modules:

  • role: zmf_cpm_provision_software_service

  • role: zmf_cpm_manage_software_instance

  • role: zmf_cpm_remove_software_instance

  • role: zmf_cpm_list_software_templates

  • role: zmf_cpm_create_software_instance

  • role: zmf_cpm_get_software_instance

• z/OSMF SCA

  z/OSMF SCA is a plugin of z/OSMF which supports json format of security descriptor file. This file can be used to document security requirements by function or product. With the security descriptor file which is easy to create, SCA is able to display and automatically validate or provision security requirements in a flexible granularity, either by individual requirement, by function or by product. SCA is based on SAF interface, therefore, supports all SAF based security products in most cases.

  To interact with z/OSMF SCA in your playbook, it requires you to setup z/OSMF SCA properly in z/OS managed nodes.

  This dependency is only required for using the following module:

  • module: zmf_sca

• z/OSMF Software Management (Optional)

  To interact with the Software Management software instance maintenance reports in your playbook, it requires you to set up Software Management properly in z/OS managed nodes. Typically, you setup Software Management as a plugin of one z/OSMF server in each sysplex.

  This dependency is only required for using the following roles:

  • role: zmf_swmgmt_identify_missing_critical_updates

  • role: zmf_swmgmt_identify_missing_fixcat_updates

  • role: zmf_swmgmt_search_software_updates

• z/OS Management Services Catalog (Optional)

  z/OS Management Services Catalog (zMSC) can be used to create, manage and run z/OS System Management Services. To interact with zMSC in your playbook, it requires you to set up z/OS Management Services Catalog properly in z/OS managed nodes.

  This dependency is only required for using the following roles:

  • role: zmf_zmsc_run_management_service