Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update release_notes.rst #131

Merged
merged 1 commit into from
May 15, 2024
Merged

Update release_notes.rst #131

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 28 additions & 12 deletions docs/source/release_notes.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,28 @@
.. ...............................................................................
.. © Copyright IBM Corporation 2020,2023 .
.. © Copyright IBM Corporation 2020,2024 .
.. Apache License, Version 2.0 (see https://opensource.org/licenses/Apache-2.0) .
.. ...............................................................................
========
Releases
========

Version 2.0.0
======

What's new
---------------

* **Removed support for Python 2.7.** Python 2.7 is no longer supported as the managed node runtime.


Version 1.0.6
=============
What's New
-------------------
* Bug fix that allows CICSPlex SM Scope and Context to contain special characters '$', '@', and '#'.


Version 1.0.5
=============
What's New
Expand Down Expand Up @@ -48,25 +64,25 @@ Initial release of the **IBM® z/OS® CICS® collection**, also referred to as *

This collection can manage CICS and CICSPlex® SM resources and definitions by calling the `CMCI REST API`_, which can be configured in a CICSplex or in a stand-alone region.

* Modules
**Modules**

* ``cmci_create`` - Create definitional CICS and CICSPlex SM resources in CICS regions, by initiating POST requests via the CMCI REST API.
* ``cmci_delete`` - Remove or discard definitional and installed CICS and CICSPlex SM resources from CICS regions, by initiating DELETE requests via the CMCI REST API.
* ``cmci_get`` - Retrieve information about installed and definitional CICS and CICSPlex SM resources from CICS regions, by initiating GET requests via the CMCI REST API.
* ``cmci_action`` - Install CICS and CICSPlex SM resources into CICS regions from definitions, by initiating PUT requests via the CMCI REST API.
* ``cmci_update`` - Make changes to CICS and CICSPlex SM resources in CICS regions, by initiating PUT requests via the CMCI REST API.
* ``cmci_create`` - Create definitional CICS and CICSPlex SM resources in CICS regions, by initiating POST requests via the CMCI REST API.
* ``cmci_delete`` - Remove or discard definitional and installed CICS and CICSPlex SM resources from CICS regions, by initiating DELETE requests via the CMCI REST API.
* ``cmci_get`` - Retrieve information about installed and definitional CICS and CICSPlex SM resources from CICS regions, by initiating GET requests via the CMCI REST API.
* ``cmci_action`` - Install CICS and CICSPlex SM resources into CICS regions from definitions, by initiating PUT requests via the CMCI REST API.
* ``cmci_update`` - Make changes to CICS and CICSPlex SM resources in CICS regions, by initiating PUT requests via the CMCI REST API.


* Documentation
**Documentation**

* Generic documentation is available at `the documentation site`_, covering guidance on installation, modules, and other reference.
* Generic documentation is available at `the documentation site`_, covering guidance on installation, modules, and other reference.

* Documentation related to playbook configuration is provided with sample playbooks at the `samples repository`_. Each playbook contains a README that explains what configurations must be made to run a sample playbook.
* Documentation related to playbook configuration is provided with sample playbooks at the `samples repository`_. Each playbook contains a README that explains what configurations must be made to run a sample playbook.


* Playbooks
**Playbooks**

* Sample playbooks are available at the `samples repository`_. Each playbook contains a README that explains what configurations must be made to run a sample playbook.
* Sample playbooks are available at the `samples repository`_. Each playbook contains a README that explains what configurations must be made to run a sample playbook.

.. _samples repository:
https://github.com/IBM/z_ansible_collections_samples/tree/main/zos_subsystems/cics
Expand Down
Loading