This playbook demonstrates how to create a GDG create copy delete and submit creations of GDS.
This playbook uses:
- collection:
- ibm.ibm_zos_core
- modules:
- zos_copy
- zos_data_set
- zos_job_submit
It is a good practice to review the playbook contents before executing them. It will help you understand the requirements in terms of space, location, names, authority, and the artifacts that will be created and cleaned up.
Important
The release of ibm_zos_core collection version 2.0.0 introduced option
and return value changes to modules. See the migration guide
(here)
to understand the full scope of these changes.
These changes are not compatible with earlier versions of the ibm_zos_core collection,
and since the earlier versions do not reach their end of life until February 2028,
the sample playbooks compatible with the older versions will remain available.
To support both the latest and prior versions of the collection:
- The
mainbranch will reflect playbooks compatible withibm_zos_coreversion 2.0.0 or later.- Find this playbook on the
mainbranch: here.
- Find this playbook on the
- The
ibm_zos_core-v1.16.0-samplesbranch will reflect playbooks compatible withibm_zos_coreversion 1.16.x or earlier.- Find this playbook on the
ibm_zos_core-v1.16.0-samplesbranch: here.
- Find this playbook on the
The ibm_zos_core-v1.16.0-samples branch will remain available until February 2028 but will not receive updates.
This playbook requires:
- Configure the included inventory.yml with the
information from the managed z/OS host.
- Review inventory documentation
- Configure the included host_vars zos_host.yml
with the information from your z/OS system.
- Review host_vars documentation and any additional noted variables in the configuration.
This project has included a site.yml playbook that serves as the primary playbook
that provides additional prerequisite checks then it invokes the create_copy_submit.yml
playbook.
If you want to run the primary playbook site.yml it will check that your environment
has the correct version of Ansible as well as the collection needed to execute
correctly. To run the primary playbook, use command:
ansible-playbook -i inventories site.ymlYou can skip the prerequisite check and run the create_copy_submit.yml with
command:
ansible-playbook -i inventories create_copy_submit.ymlAll changes are maintained chronologically by date found in the changelog.
© Copyright IBM Corporation 2024, 2026
Licensed under Apache License, Version 2.0.
Please refer to the support section for more details.