Hotfix/122/update readme (#5)

* update README.md to reflect collection
* hot fix for zos_data_set existence checking and validation
* update README.md version tag links to v.0.0.3
* Updates to README.md that include fixing a malformed link
* Remove dependency list from modules
Dependencies will be stated on the collections README.md

Author: ddimatos

README.md

@@ -1,35 +1,42 @@
+# IBM Z Core Collection
+
+The IBM Z core collection, referred to as `ibm_zos_core`, is part of the broader offering __Red Hat® Ansible Certified Content for IBM Z__. `ibm_zos_core` supports tasks such as creating data sets, submitting jobs, querying jobs, and retrieving job output.  
+
 # Red Hat Ansible Certified Content for IBM Z
-__Red Hat® Ansible Certified Content for IBM Z__ provides the ability to connect IBM Z® to clients' wider enterprise automation strategy through the Ansible Automation Platform ecosystem. The __Red Hat Ansible Certified Content for IBM Z core collection__ (`ibm_zos_core`) enables development and operations to automate on Z by providing Ansible support for tasks such as creating data sets, submitting jobs, querying jobs, and retrieving job output.  
+__Red Hat® Ansible Certified Content for IBM Z__ provides the ability to connect IBM Z® to clients' wider enterprise 
+automation strategy through the Ansible Automation Platform ecosystem. This enables development and operations automation on Z through a seamless, unified workflow orchestration with configuration management, provisioning, and 
+application deployment in one easy-to-use platform.  
 
-# Features
-The __Red Hat Ansible Certified Content for IBM Z core collection__ `ibm_zos_core` includes [connection plugins](https://github.com/ansible-collections/ibm_zos_core/tree/v0.0.2/plugins/connection/), [action plugins](https://github.com/ansible-collections/ibm_zos_core/tree/v0.0.2/plugins/action/), [modules](https://github.com/ansible-collections/ibm_zos_core/tree/v0.0.2/plugins/modules/), [sample playbooks](https://github.com/ansible-collections/ibm_zos_core/tree/v0.0.2/playbooks/), and ansible-doc to automate tasks on Z.  
+Collections, as part of the broader offering __Red Hat® Ansible Certified Content for IBM Z__, will initially be made available
+on Galaxy and later made available as certified content and accessable through Automation Hub. 
 
-These features enable a seamless, unified workflow orchestration with configuration management, provisioning, and application deployment in one easy-to-use platform. 
+# Features
+The The IBM Z core collection includes [connection plugins](https://github.com/ansible-collections/ibm_zos_core/tree/v0.0.3/plugins/connection/), [action plugins](https://github.com/ansible-collections/ibm_zos_core/tree/v0.0.3/plugins/action/), [modules](https://github.com/ansible-collections/ibm_zos_core/tree/v0.0.3/plugins/modules/), [sample playbooks](https://github.com/ansible-collections/ibm_zos_core/tree/v0.0.3/playbooks/), and ansible-doc to automate tasks on Z.  
 
 # Plugins
 
 ## Action
-* [normal](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.2/docs/README-zos-rexx-connection-plugin.md): A fork of [Ansible _normal.py_ action plugin](https://github.com/ansible/ansible/blob/devel/lib/ansible/plugins/action/normal.py) that is modified to allow a conditional shebang line in REXX modules.
-* [zos_job_submit](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.2/docs/README-zos-job-submit.md): Used to submit a job from the controller and optionally monitor for completion.  
+* [normal](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.3/docs/README-zos-rexx-connection-plugin.md): A fork of [Ansible _normal.py_ action plugin](https://github.com/ansible/ansible/blob/devel/lib/ansible/plugins/action/normal.py) that is modified to allow a conditional shebang line in REXX modules.
+* [zos_job_submit](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.3/docs/README-zos-job-submit.md): Used to submit a job from the controller and optionally monitor for job completion.  
 
 ## Connection
-* [zos_ssh](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.2/docs/README-zos-rexx-connection-plugin.md): Enables the Ansible controller to communicate to a Z target machine by using ssh with the added support to transfer ASCII as EBCDIC when transferring REXX modules. The connection plugin was forked from the [Ansible _ssh.py_ connection plugin](https://github.com/ansible/ansible/blob/480b106d6535978ae6ecab68b40942ca4fa914a0/lib/ansible/plugins/connection/ssh.py). 
+* [zos_ssh](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.3/docs/README-zos-rexx-connection-plugin.md): Enables the Ansible controller to communicate to a Z target machine by using ssh, with the added support to transfer ASCII as EBCDIC when transferring REXX modules. This connection plugin was forked from the [Ansible _ssh.py_ connection plugin](https://github.com/ansible/ansible/blob/480b106d6535978ae6ecab68b40942ca4fa914a0/lib/ansible/plugins/connection/ssh.py). 
 
 # Modules 
-*  [zos_data_set](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.2/docs/README-zos-data-set.md): Create, delete, and manage attributes for data sets.
-*  [zos_job_query](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.2/docs/README-zos-job-query.md): Query Z for a list of jobs.
-*  [zos_job_submit](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.2/docs/README-zos-job-submit.md): Submit a job and optionally monitor for completion.
-*  [zos_job_output](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.2/docs/README-zos-job-output.md): Capture the job output for a submitted job.
+*  [zos_data_set](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.3/docs/README-zos-data-set.md): Create, delete, and manage attributes for data sets.
+*  [zos_job_query](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.3/docs/README-zos-job-query.md): Query Z for a list of jobs.
+*  [zos_job_submit](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.3/docs/README-zos-job-submit.md): Submit a job and optionally monitor for its completion.
+*  [zos_job_output](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.3/docs/README-zos-job-output.md): Capture the job output for a submitted job.
 
 # Playbooks
-[Sample playbooks](https://github.com/ansible-collections/ibm_zos_core/tree/v0.0.2/playbooks/) are included that demonstrate how to use the collection content in the `ibm_zos_core` collection.  
-See the [playbooks README](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.2/playbooks/README.md) for detailed instructions and configuration information.
+[Sample playbooks](https://github.com/ansible-collections/ibm_zos_core/tree/v0.0.3/playbooks/) are included that demonstrate how to use the collection content in the `ibm_zos_core` collection.  
+See the [playbooks README](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.3/playbooks/README.md) for detailed instructions and configuration information.
 
 # Requirements
 
 A control node is any machine with Ansible installed. From the control node, you can run commands and playbooks from a laptop, desktop, or server machine. However, you cannot run them on a Windows machine. 
 
-A managed node is often referred as a target node or host and is the node that is managed by Ansible. Ansible does not need not be installed on a managed node, but SSH must be eanabled. 
+A managed node is often referred to as a target node, or host, and is the node that is managed by Ansible. Ansible does not need not need to be installed on a managed node, but SSH must be eanabled.
 
 The following nodes require specific versions of software:
 
@@ -39,9 +46,9 @@ The following nodes require specific versions of software:
 * [OpenSSH](https://www.openssh.com/)
 
 ## Managed node (target)
-* [Python](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.2/docs/README-python-zos.md): 3.6 or later
+* [Python](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.3/docs/README-python-zos.md): 3.6 or later
 * [z/OS](https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2/zos-v2r2-home.html): V02.02.00 or later
-* [IBM Z Open Automation Utilities](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.2/docs/README-ZOAU.md): 1.0.1 (PTF UI66957 or later)
+* [IBM Z Open Automation Utilities](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.3/docs/README-ZOAU.md): 1.0.1 (PTF UI66957 or later)
 * [OpenSSH](https://www.openssh.com/) 
 
 # Installation
@@ -83,10 +90,17 @@ Installed collection content:
 
 You can use the `-p` option with `anasible-galaxy` to specify the installation path such as `ansible-galaxy collection install ibm.ibm_zos_core -p /home/ansible/collections`. For more information on installing collections with Ansible Galaxy, see [Installing collections](https://docs.ansible.com/ansible/latest/user_guide/collections_using.html#installing-collections-with-ansible-galaxy). 
 
-## Automation Hub and private Galaxy server
-You can use the [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) command with option `install` to install a collection on your system (control node) hosted in Hub or a private Galaxy server.  
+## Private Galaxy server
+
+Configuring access to a private Galaxy server follows the same instructions that you would use to configure your client to point to
+Automation Hub. When hosting a private Galaxy server or pointing to Hub, available content is not always consistent with 
+what is avaialable on the community Galaxy server. 
+
+You can use the [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) command with 
+option `install` to install a collection on your system (control node) hosted in Automation Hub or a private Galaxy server.  
 
-By default, the `ansible-galaxy` command uses https://galaxy.ansible.com as the Galaxy server when you install a collection. The `ansible-galaxy` client can be configured to point to _HUB_ or other servers, such as a privately running Galaxy server, by configuring the server list in the `ansible.cfg` file.  
+By default, the `ansible-galaxy` command uses https://galaxy.ansible.com as the Galaxy server when you install a collection. 
+The `ansible-galaxy` client can be configured to point to _HUB_ or other servers, such as a privately running Galaxy server, by configuring the server list in the `ansible.cfg` file.  
 
 Ansible searches for `ansible.cfg` in these locations in this order:
 * ANSIBLE_CONFIG (environment variable if set)
@@ -148,7 +162,7 @@ Created collection for ibm.ibm_zos_core at /Users/user/git/ibm/zos-ansible/ibm_z
 __Note__: If you build the collection with Ansible version 2.9 or earlier, you will see the following warning that you can ignore.
 `[WARNING]: Found unknown keys in collection galaxy.yml at '/Users/user/git/ibm/zos-ansible/ibm_zos_core/galaxy.yml': build_ignore`
 
-You can use the `-p` option with `anasible-galaxy` to specify the installation path, for example, `ansible-galaxy collection install ibm-ibm_zos_core-0.0.2.tar.gz -p /home/ansible/collections`. For more information, see [Installing collections with Ansible Galaxy] (https://docs.ansible.com/ansible/latest/user_guide/collections_using.html#installing-collections-with-ansible-galaxy). 
+You can use the `-p` option with `anasible-galaxy` to specify the installation path, for example, `ansible-galaxy collection install ibm-ibm_zos_core-0.0.2.tar.gz -p /home/ansible/collections`. For more information, see [Installing collections with Ansible Galaxy](https://docs.ansible.com/ansible/latest/user_guide/collections_using.html#installing-collections-with-ansible-galaxy). 
 
 3. Install the locally built collection:
 ```
@@ -188,7 +202,7 @@ In Ansible 2.9, the `collections` keyword was added and reduces the need to refe
 ```
 
 ## ansible-doc
-Modules included in this collection provide additional documentation that is similar to a UNIX or UNIX-like operating system man page (manual page). This documentation an be accessed from the command line by using the `ansible-doc` command.
+Modules included in this collection provide additional documentation that is similar to a UNIX, or UNIX-like, operating system man page (manual page). This documentation can be accessed from the command line by using the `ansible-doc` command.
 
 Here's how to use the Ansible-supplied command after you install the _Red Hat Ansible Certified Content for IBM Z core collection_:
 `ansible-doc ibm.ibm_zos_core.zos_data_set`
@@ -220,13 +234,13 @@ OPTIONS (= is mandatory):
 * [Getting started Ansible guide](https://docs.ansible.com/ansible/latest/user_guide/intro_getting_started.html).
 
 # Contributing
-Currently we are not accepting community contributions. Periodically review this content on when and how contributions could be contributed.   
+Currently we are not accepting community contributions. Though, you may periodically review this content to learn when and how contributions can be made in the future.
 
 # Copyright
 © Copyright IBM Corporation 2020  
 
 # License
-Portions of this collection are licensed under [GNU General Public License, Version 3.0](https://opensource.org/licenses/GPL-3.0), 
-and portions of this collection are licensed under [Apache License, Version 2.0](https://opensource.org/licenses/Apache-2.0).
+Some portions of this collection are licensed under [GNU General Public License, Version 3.0](https://opensource.org/licenses/GPL-3.0), 
+and other portions of this collection are licensed under [Apache License, Version 2.0](https://opensource.org/licenses/Apache-2.0).
 See individual files for applicable licenses.
 

docs/README-ZOAU.md

@@ -9,7 +9,7 @@ See [Installing and configuring ZOA Utilities](https://www.ibm.com/support/knowl
 * See the [fix list](https://www.ibm.com/support/pages/fix-list-ibm-z-open-automation-utilities) for ZOAU.
 * The latest PTF when this document was authored is __UI66957__.
 
-__Note__: [Python 3.6 for z/OS](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.2/docs/README-python-zos.md) is required by ZOAU.
+__Note__: [Python 3.6 for z/OS](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.3/docs/README-python-zos.md) is required by ZOAU.
 
 # Copyright
 © Copyright IBM Corporation 2020  

galaxy.yml

@@ -5,7 +5,7 @@ namespace: ibm
 name: ibm_zos_core 
 
 # The collection version
-version: 0.0.2
+version: 0.0.3
 
 # Collection README file
 readme: README.md

playbooks/README.md

@@ -3,12 +3,12 @@ An [Ansible playbook](https://docs.ansible.com/ansible/latest/user_guide/playboo
 
 Included in __Red Hat Ansible Certified Content for IBM Z core collection__ is a playbooks directory that will contain any number of sample playbooks that with little modification to the __inventory__, __ansible config__ and __group_vars__ can be run with the `ansible-playbook` command. 
 
-You can find the playbook content that is included with the collection where the collection was installed, please refer back to the [installation documentation](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.2/README.md#installation). In the following examples, this documment will refer to the installation path as `~/.ansible/collections/ibm/ibm_zos_core`. 
+You can find the playbook content that is included with the collection where the collection was installed, please refer back to the [installation documentation](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.3/README.md#installation). In the following examples, this documment will refer to the installation path as `~/.ansible/collections/ibm/ibm_zos_core`. 
 
 # Sample Playbook Configuration and Setup
 
 ## Ansible Config
-Ansible config `ansible.cfg` can override nearly all `ansible-playbook` configurations. Also included in the [playbooks/](https://github.com/ansible-collections/ibm_zos_core/tree/v0.0.2/playbooks) directory is a sample `ansible.cfg` that with little modificaton can supplement `ansible-playbook`.
+Ansible config `ansible.cfg` can override nearly all `ansible-playbook` configurations. Also included in the [playbooks/](https://github.com/ansible-collections/ibm_zos_core/tree/v0.0.3/playbooks) directory is a sample `ansible.cfg` that with little modificaton can supplement `ansible-playbook`.
 
 In the sample `ansible.cfg`, the only required configuration is:   
 `pipelining = True`
@@ -18,7 +18,7 @@ For more information about available configurations for `ansible.cfg`, read the
 ## Inventory
 Ansible works with multiple managed nodes (hosts) at the same time, using a list or group of lists know as an [inventory](https://docs.ansible.com/ansible/latest/user_guide/intro_inventory.html). Once the inventory is defined, you can use [patterns](https://docs.ansible.com/ansible/latest/user_guide/intro_patterns.html#intro-patterns) to select the hosts, or groups, you want Ansible to run against.
 
-Included in the  [playbooks/](https://github.com/ansible-collections/ibm_zos_core/tree/v0.0.2/playbooks) directory is a sample [inventory](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.2/playbooks/inventory) file that with little modification can be used to manage your nodes. This inventory file should be included when running the sample playbook. 
+Included in the  [playbooks/](https://github.com/ansible-collections/ibm_zos_core/tree/v0.0.3/playbooks) directory is a sample [inventory](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.3/playbooks/inventory) file that with little modification can be used to manage your nodes. This inventory file should be included when running the sample playbook. 
 
 ```
 zsystem:
@@ -41,7 +41,7 @@ The value for property __ansible_python_interpreter__ is the target host python
 For more information on python configuration requirements on z/OS, refer to [Ansible FAQ: Running on z/OS](https://docs.ansible.com/ansible/latest/reference_appendices/faq.html).
 
 ## Group Vars
-Although you can store variables in the inventory file, storing separate host and group variables files may help you organize your variable values more easily. Included with the sample playbook is a sample variable file located in [./group_vars/all.yml](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.2/playbooks/group_vars/all.yml).
+Although you can store variables in the inventory file, storing separate host and group variables files may help you organize your variable values more easily. Included with the sample playbook is a sample variable file located in [./group_vars/all.yml](https://github.com/ansible-collections/ibm_zos_core/blob/v0.0.3/playbooks/group_vars/all.yml).
 
 The value for property __BPXK_AUTOCVT__ must be configured to `ON`.