Ansible Z Playbook Repository

This repository provides playbooks that can be tailored to automate often repeated Z tasks, links to blogs, and other related media. An Ansible playbook consists of organized instructions that define work for a managed node to be automated with Ansible. The playbooks in this repository are written using the collections from Red Hat® Ansible® Certified Content for IBM Z® offering. For a detailed overview of the playbooks, refer to the documentation.

The collections can be found on Ansible Galaxy and Automation Hub. For additional content, review our community page.

This repository is frequently updated to refresh content. We recommend that you clone the the repository and configure your GitHub notifications and subscriptions to receive ongoing updates about specific activity on GitHub.

Playbooks

Playbooks are organized by topics that align to tasks and use cases that are often repeated and in need of automation.

Z Topics

• Systems Administration
  • zHMC
    • Gather facts for CPC and its adapters and partitions
    • zHMC Concepts

z/OS® Topics

• Administration
  • Set Up Ansible Host Variables for Python and ZOAU
  • Manage z/OS Users Using Ansible - [Playback]
  • Synchronize APF authorized libraries from a configuration cloned from GitHub - [Playback]
• Basic Operations
  • Data Set Basics
  • Copy Directory to PDS, Edit member and Submit Job
  • Operator Basics
  • Convert Encoding
• Concepts
  • Copy and Fetch Data sets
  • Copy, Sort and Fetch Data Sets on z/OS using Ansible- [Playback]
  • Terse Data Set and Fetch
  • Transfer, Dump and Unpack Data Sets
• Integrating Existing Automation
  • Job Control Language (JCL)
    • Submit Batch Jobs, Query and Retrieve Job Output
  • z/OSMF Workflows
  • System Automation
    • Managing Dynamic Resources
• Provisioning
  • IMS
    • Provision a new IMS TMDB subsystem
  • ZCEE
    • Provision a new z/OS Connect EE subsystem
  • z/OSMF Cloud Provisioning and Management
• Application & Service Deployment
  • ZCEE
    • Generate and deploy z/OS Connect EE API, service, and API requester artifacts
• Subsystems
  • CICS
    • Retrieve operational data from running CICS regions
    • Deploy a program to a CICS region
    • Customize when a CMCI module should fail
    • Resource life cycle and CSD
• Software Installation
  • SMP/E Playbooks

Blogs

Don't have time to explore a collection, particular module or a playbook?
Learn all about the offerings from our blogs.
Don't know which one to read first? Well, here is a list of some of our recent blogs:

• Job Submission on z/OS Made Easy with Ansible - [Playbook]
• Running Batch Jobs on z/OS using Ansible - [Playbook]
• Simplified Approach to Copying Data Between z/OS and Local Machine Using Ansible - [Playbook]
• z/OS User Management With Ansible - [Playbook]

Playbacks

Want to experience Z automation with Ansible without rolling up your sleeves? Take a look at some of our playbacks using our own playbooks available in this repository.

• Copy, Sort and Fetch Data Sets on z/OS using Ansible
• Manage z/OS Users Using Ansible
• Synchronize APF authorized libraries from a configuration cloned from GitHub

How playbooks are organized in this repository

All playbooks in this repository can run independently from any other playbook. Each playbook in this repository includes a README with a brief description, licensing and instructions on how to configure the playbook. If configuration is required, a default configuration will be included with the playbook.

The playbooks in the repository is organized as follows:

├── topic/
│  └── use_case/
│      └── playbook_name/
│          ├── host_vars/
│              └── zos_host.yml
│          ├── ansible.cfg
│          ├── inventory
│          ├── playbook_name.yml
│          └── README
├── LICENSE
└── README

Copyright

© Copyright IBM Corporation 2020, 2021

License

Licensed under Apache License, Version 2.0.

Support

Support for all playbooks, roles, and filters are provided by the community and all issues are tracked through a Git issue. The repository admins and content owners will engage directly with users on issues reported on the Git issue.

Playbooks are contributed both by IBM as well as the broader Ansible community including IBM partners and the Z community. Therefore, it may be helpful to review who contributed a sample as well as its requirements. You can view who the contributor was by looking at the playbooks commit history as well as notes in the playbook.