ansible-collections
diff --git a/‎README.md
Lines changed: 4 additions & 6 deletions b/‎README.md
Lines changed: 4 additions & 6 deletions
diff --git a/‎bindep.txt
Lines changed: 8 additions & 0 deletions b/‎bindep.txt
Lines changed: 8 additions & 0 deletions
diff --git a/‎docs/source/modules/zos_copy.rst
Lines changed: 13 additions & 5 deletions b/‎docs/source/modules/zos_copy.rst
Lines changed: 13 additions & 5 deletions
@@ -1,14 +1,14 @@
 IBM z/OS core collection
 ========================
 
-The **IBM z/OS core collection**, also represented as
+The **IBM® z/OS® core collection**, also represented as
 **ibm_zos_core** in this document, is  part of the broader
 initiative to bring Ansible Automation to IBM Z® through the offering
 **Red Hat® Ansible Certified Content for IBM Z®**. The
 **IBM z/OS core collection** supports automation tasks such as
-creating data sets, submitting jobs, querying jobs,
-retrieving job output, encoding data sets, fetching data sets, copying data
-sets, executing operator commands, executing TSO commands, ping,
+creating data sets, submitting jobs, querying jobs, retrieving job output,
+encoding data, fetching data sets, copying data sets,
+executing operator commands, executing TSO commands, ping,
 querying operator actions, APF authorizing libraries,
 editing textual data in data sets or Unix System Services files,
 finding data sets, backing up and restoring data sets and
@@ -36,7 +36,6 @@ released to [Ansible Automation Hub](https://www.ansible.com/products/automation
 as **certified** and **IBM supported** for
 **Red Hat® Ansible Automation Platform subscribers**.
 
-
 For guides and reference, please review the [documentation](https://ibm.github.io/z_ansible_collections_doc/index.html).
 
 Features
@@ -46,7 +45,6 @@ The **IBM z/OS core collection**, includes
 [action plugins](https://ibm.github.io/z_ansible_collections_doc/ibm_zos_core/docs/source/plugins.html#action),
 [modules](https://ibm.github.io/z_ansible_collections_doc/ibm_zos_core/docs/source/modules.html),
 [filters](https://ibm.github.io/z_ansible_collections_doc/ibm_zos_core/docs/source/filters.html),
-[sample playbooks](https://ibm.github.io/z_ansible_collections_doc/playbooks/playbooks.html)
 and ansible-doc to automate tasks on z/OS.
 
 Copyright
 
@@ -0,0 +1,8 @@
+################################################################################
+# © Copyright IBM Corporation 2021
+################################################################################
+# This file maintains a list of any binary dependencies needed by this
+# Collection. At this time there are no binary dependencies.
+# For more information on Bindep,
+# see https://docs.opendev.org/opendev/bindep/latest/readme.html
+################################################################################
@@ -75,15 +75,17 @@ dest
 
   If ``dest`` is a nonexistent USS file, it will be created.
 
-  If ``dest`` is a nonexistent data set, it will be allocated.
+  If ``dest`` is a nonexistent data set, storage management rules will be used to determine the volume where ``dest`` will be allocated.
 
   If ``src`` and ``dest`` are files and if the parent directory of ``dest`` does not exist, then the task will fail.
 
-  When the ``dest`` is an existing VSA:ref:`KSDS <KSDS_module>` or VSA:ref:`ESDS <ESDS_module>`, then source can be ESDS, KSDS or RRDS.
+  When the ``dest`` is an existing VSA:ref:`KSDS <KSDS_module>` or VSA:ref:`ESDS <ESDS_module>`, then source can be ESDS, KSDS or RRDS. The ``dest`` will be deleted and storage management rules will be used to determine the volume where ``dest`` will be allocated.
 
-  When the ``dest`` is an existing VSA:ref:`RRDS <RRDS_module>`, then the source must be RRDS.
+  When the ``dest`` is an existing VSA:ref:`RRDS <RRDS_module>`, then the source must be RRDS. The ``dest`` will be deleted and storage management rules will be used to determine the volume where ``dest`` will be allocated.
 
-  When ``dest`` is and existing VSA:ref:`LDS <LDS_module>`, then source must be LDS.
+  When ``dest`` is and existing VSA:ref:`LDS <LDS_module>`, then source must be LDS. The ``dest`` will be deleted and storage management rules will be used to determine the volume where ``dest`` will be allocated.
+
+  When ``dest`` is a data set, you can override storage management rules by specifying both ``volume`` and ``model_ds``.
 
   | **required**: True
   | **type**: str
@@ -229,11 +231,15 @@ validate
 volume
   If ``dest`` does not exist, specify which volume ``dest`` should be allocated to.
 
+  ``volume`` must be used with ``model_ds``, otherwise the ``volume`` value is ignored.
+
   Only valid when the destination is an MVS data set.
 
   The volume must already be present on the device.
 
-  If no volume is specified, an appropriate volume will be chosen to allocate ``dest``.
+  If no volume is specified, storage management rules will be used to determine the volume where ``dest`` will be allocated.
+
+  If the storage administrator has specified a system default unit name and you do not set a ``volume`` name for non-system-managed data sets, then the system uses the volumes associated with the default unit name. Check with your storage administrator to determine whether a default unit name has been specified.
 
   | **required**: False
   | **type**: str
@@ -410,6 +416,8 @@ Notes
 
    For supported character sets used to encode data, refer to https://ansible-collections.github.io/ibm_zos_core/supplementary.html#encode
 
+   :ref:`zos_copy <zos_copy_module>` uses SFTP (Secure File Transfer Protocol) for the underlying transfer protocol; Co:Z SFTP is not supported. In the case of Co:z SFTP, you can exempt the Ansible userid on ZOS from using Co:Z thus falling back to using standard SFTP.
+
 
 
 See Also