|
1 | | -IBM z/OS IMS collection |
2 | | -======================== |
| 1 | +# IBM® z/OS® IMS collection |
3 | 2 |
|
4 | | -The **IBM z/OS IMS collection**, also represented as **ibm\_zos\_ims** |
5 | | -in this document, is part of the broader offering **Red Hat® Ansible |
6 | | -Certified Content for IBM Z**. The IBM z/OS IMS collection supports tasks |
7 | | -such as generating IMS Database Descriptors (DBD), Program |
8 | | -Specification Blocks (PSB), Application Control Blocks (ACB), and |
9 | | -running IMS type-1 & type-2 commands. |
| 3 | +The IBM z/OS IMS collection enables Ansible to interact with IBM Information Management System. The collection focuses on system management operations such as generating database descriptors, program specifications, Application Control Blocks (ACB), data definition language (DDL), catalog operations, submitting DBRC commands, and executing commands. |
10 | 4 |
|
11 | | -The **IBM z/OS IMS collection** works closely with offerings such as the |
12 | | -[IBM z/OS core collection](https://github.com/ansible-collections/ibm_zos_core) |
13 | | -to deliver a solution that will enable you to automate tasks on z/OS. |
| 5 | +## Description |
14 | 6 |
|
15 | | -Red Hat Ansible Certified Content for IBM Z |
16 | | -=========================================== |
| 7 | +The IBM z/OS IMS collection is part of the Red Hat® Ansible Certified Content for IBM Z® offering that brings Ansible automation to IBM Z®. This collection enables automation of IMS tasks such as generating IMS Database Descriptors (DBD), Program Specification Blocks (PSB), Application Control Blocks (ACB), managing DDL, catalog operations, submitting DBRC commands, and running IMS type-1 & type-2 commands. |
| 8 | + |
| 9 | +System programmers can automate IMS system management tasks while database administrators can streamline database operations. The collection works seamlessly with other IBM Z collections like IBM z/OS core to deliver comprehensive z/OS automation solutions. |
17 | 10 |
|
18 | | -**Red Hat® Ansible Certified Content for IBM Z** provides the ability to |
19 | | -connect IBM Z® to clients\' wider enterprise automation strategy through |
20 | | -the Ansible Automation Platform ecosystem. This enables development and |
21 | | -operations automation on Z through a seamless, unified workflow |
22 | | -orchestration with configuration management, provisioning, and |
23 | | -application deployment in one easy-to-use platform. |
| 11 | +## Requirements |
24 | 12 |
|
25 | | -**The IBM z/OS IMS collection**, as part of the broader offering |
26 | | -**Red Hat® Ansible Certified Content for IBM Z**, is available on Galaxy as |
27 | | -community supported. |
| 13 | +This collection has been tested against the following Ansible versions: >=2.14.0,<2.17.3. |
28 | 14 |
|
29 | | -For **guides** and **reference**, please visit [the documentation |
30 | | -site](https://ibm.github.io/z_ansible_collections_doc/index.html). |
| 15 | +The collection requires the following on the managed node: |
| 16 | +- IBM z/OS IMS |
| 17 | +- IBM Open Enterprise SDK for Python |
| 18 | +- IBM Z Open Automation Utilities (ZOAU) |
31 | 19 |
|
32 | | -Features |
33 | | -======== |
| 20 | +The control node requires the IBM z/OS core collection to be installed before installing the IMS collection. Please refer to the [IBM z/OS collections support matrix](https://ibm.github.io/z_ansible_collections_doc/ibm_zos_core/docs/source/resources/releases_maintenance.html#support-matrix) for specific version requirements. |
34 | 21 |
|
35 | | -The IBM IMS collection includes |
36 | | -[modules](https://github.com/ansible-collections/ibm_zos_ims/tree/master/plugins/modules/), |
37 | | -and ansible-doc to automate tasks on IMS. |
| 22 | +## Installation |
38 | 23 |
|
| 24 | +Before using this collection, you need to install it with the Ansible Galaxy command-line tool: |
39 | 25 |
|
40 | | -Ansible version compatibility |
41 | | -============================== |
| 26 | +```sh |
| 27 | +ansible-galaxy collection install ibm.ibm_zos_ims |
| 28 | +``` |
42 | 29 |
|
43 | | -This collection has been tested against the following Ansible versions: >=2.14.0,<2.17.0. |
| 30 | +You can also include it in a requirements.yml file and install it with `ansible-galaxy collection install -r requirements.yml`, using the format: |
44 | 31 |
|
| 32 | +```yaml |
| 33 | +collections: |
| 34 | + - name: ibm.ibm_zos_ims |
| 35 | +``` |
45 | 36 |
|
46 | | -Copyright |
47 | | -========= |
| 37 | +Note that if you install the collection from Ansible Galaxy, it will not be upgraded automatically when you upgrade the Ansible package. To upgrade the collection to the latest available version, run the following command: |
48 | 38 |
|
49 | | -© Copyright IBM Corporation 2020 |
| 39 | +```sh |
| 40 | +ansible-galaxy collection install ibm.ibm_zos_ims --upgrade |
| 41 | +``` |
50 | 42 |
|
51 | | -License |
52 | | -======= |
| 43 | +You can also install a specific version of the collection, for example, if you need to downgrade when something is broken in the latest version (please report an issue in this repository). Use the following syntax to install version 1.2.0: |
53 | 44 |
|
54 | | -This collection is licensed under [Apache License, Version 2.0](https://opensource.org/licenses/Apache-2.0). |
| 45 | +```sh |
| 46 | +ansible-galaxy collection install ibm.ibm_zos_ims:1.2.0 |
| 47 | +``` |
| 48 | + |
| 49 | +## Use Cases |
| 50 | + |
| 51 | +* Use Case Name: IMS Database Generation |
| 52 | + * Actors: Database Administrator |
| 53 | + * Description: A database administrator can automate the process of generating and maintaining IMS database definitions |
| 54 | + * Flow: |
| 55 | + * Generate Database Descriptor (DBD) |
| 56 | + * Generate Program Specification Block (PSB) |
| 57 | + * Generate Application Control Block (ACB) |
| 58 | + * Verify generation success |
| 59 | + * Update production libraries |
| 60 | + |
| 61 | +* Use Case Name: IMS Command Automation |
| 62 | + * Actors: System Administrator |
| 63 | + * Description: A system administrator can automate routine IMS commands and health checks |
| 64 | + * Flow: |
| 65 | + * Execute IMS type-1 commands for system monitoring |
| 66 | + * Run IMS type-2 commands for advanced operations |
| 67 | + * Collect command responses |
| 68 | + * Process and analyze results |
| 69 | + * Generate operational reports |
| 70 | + |
| 71 | +* Use Case Name: IMS System Maintenance |
| 72 | + * Actors: System Programmer |
| 73 | + * Description: A system programmer can automate IMS maintenance procedures |
| 74 | + * Flow: |
| 75 | + * Verify system status |
| 76 | + * Back up critical resources |
| 77 | + * Apply maintenance |
| 78 | + * Validate changes |
| 79 | + * Generate maintenance report |
| 80 | + |
| 81 | +* Use Case Name: IMS Catalog Population |
| 82 | + * Actors: Database Administrator |
| 83 | + * Description: A database administrator can automate the population and maintenance of the IMS catalog |
| 84 | + * Flow: |
| 85 | + * Prepare catalog datasets |
| 86 | + * Use DDL to define database structures |
| 87 | + * Populate catalog with database metadata |
| 88 | + * Verify catalog entries |
| 89 | + * Update catalog documentation |
| 90 | + |
| 91 | +* Use Case Name: IMS Database Recovery Control |
| 92 | + * Actors: System Administrator |
| 93 | + * Description: A system administrator can automate DBRC operations for database recovery and backup management |
| 94 | + * Flow: |
| 95 | + * Submit DBRC commands for database registration |
| 96 | + * Monitor backup status through DBRC queries |
| 97 | + * Automate recovery scenarios |
| 98 | + * Manage RECON datasets |
| 99 | + * Generate DBRC reports |
| 100 | + |
| 101 | +## Testing |
| 102 | + |
| 103 | +This release of the collection was tested with the following dependencies. |
| 104 | + |
| 105 | +- ansible-core v2.17.x |
| 106 | +- Python 3.13.x |
| 107 | +- IBM Open Enterprise SDK for Python 3.11.x |
| 108 | +- IBM Z Open Automation Utilities (ZOAU) 1.2.x |
| 109 | +- z/OS V2R5 |
| 110 | + |
| 111 | +## Contributing |
55 | 112 |
|
| 113 | +We are not currently accepting community contributions. However, we encourage you to open git issues for bugs, comments or feature requests. |
| 114 | + |
| 115 | +Review this content periodically to learn when and how to make contributions in the future. For the latest information on open issues, see: [git issues](https://github.com/ansible-collections/ibm_zos_ims/issues). |
| 116 | + |
| 117 | +## Support |
| 118 | + |
| 119 | +As Red Hat Ansible Certified Content, this collection is entitled to support through Ansible Automation Platform (AAP). After creating a Red Hat support case, if it is determined the issue belongs to IBM, Red Hat will instruct you to create an IBM support case and share the case number with Red Hat so that a collaboration can begin between Red Hat and IBM. |
| 120 | + |
| 121 | +## Release Notes and Roadmap |
| 122 | + |
| 123 | +Release notes and changelogs are maintained in the [documentation](https://ibm.github.io/z_ansible_collections_doc/ibm_zos_ims/docs/source/release_notes.html). |
| 124 | + |
| 125 | +## Related Information |
| 126 | + |
| 127 | +For guides and reference information, please visit: |
| 128 | +- [IBM z/OS collections documentation](https://ibm.github.io/z_ansible_collections_doc/index.html) |
| 129 | +- [Ansible sample playbooks using the z/OS IMS collection](https://github.com/IBM/z_ansible_collections_samples/tree/main/zos_subsystems/ims) |
| 130 | + |
| 131 | +## License Information |
| 132 | + |
| 133 | +© Copyright IBM Corporation 2025 |
| 134 | + |
| 135 | +This collection is licensed under [Apache License, Version 2.0](https://opensource.org/licenses/Apache-2.0). |
0 commit comments