You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/modules/zos_copy.rst
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -815,6 +815,10 @@ Notes
815
815
816
816
Beginning in version 1.8.x, zos_copy will no longer attempt to correct a copy of a data type member into a PDSE that contains program objects. You can control this behavior using module option ``executable`` that will signify an executable is being copied into a PDSE with other executables. Mixing data type members with program objects will result in a (FSUM8976,./zos_copy.html) error.
817
817
818
+
It is the playbook author or user's responsibility to ensure they have appropriate authority to the RACF FACILITY resource class. A user is described as the remote user, configured either for the playbook or playbook tasks, who can also obtain escalated privileges to execute as root or another user.
819
+
820
+
To use this module, you must define the RACF FACILITY class profile and allow READ access to RACF FACILITY profile MVS.MCSOPER.ZOAU. If your system uses a different security product, consult that product's documentation to configure the required security classes.
Copy file name to clipboardExpand all lines: docs/source/release_notes.rst
+65-2Lines changed: 65 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,8 +6,8 @@
6
6
Releases
7
7
========
8
8
9
-
Version 1.10.0-beta.1
10
-
=====================
9
+
Version 1.10.0
10
+
==============
11
11
12
12
Major Changes
13
13
-------------
@@ -95,6 +95,7 @@ It is intended to assist in updating your playbooks so this collection will cont
95
95
Availability
96
96
------------
97
97
98
+
* `Automation Hub`_
98
99
* `Galaxy`_
99
100
* `GitHub`_
100
101
@@ -104,6 +105,68 @@ Requirements
104
105
The IBM z/OS core collection has several dependencies, please review the `z/OS core support matrix`_ to understand both the
105
106
controller and z/OS managed node dependencies.
106
107
108
+
Known Issues
109
+
------------
110
+
- ``zos_job_submit`` - when setting 'location' to 'local' and not specifying the from and to encoding, the modules defaults are not read leaving the file in its original encoding; explicitly set the encodings instead of relying on the default.
111
+
- ``zos_job_submit`` - when submitting JCL, the response value returned for **byte_count** is incorrect.
112
+
- ``zos_data_set`` - When data set creation fails, exception can throw a bad import error instead of data set creation error.
113
+
- ``zos_copy`` - To use this module, you must define the RACF FACILITY class profile and allow READ access to RACF FACILITY profile MVS.MCSOPER.ZOAU. If your system uses a different security product, consult that product's documentation to configure the required security classes.
114
+
- ``zos_job_submit``, ``zos_job_output``, ``zos_operator_action_query`` - encounters JSON decoding (DecodeError, TypeError, KeyError) errors when interacting with results that contain non-printable UTF-8 characters in the response. This will be addressed in **ZOAU version 1.3.2** and later.
115
+
116
+
- Some options to work around this known issue are:
117
+
118
+
- Specify that the ASA assembler option be enabled to instruct the assembler to use ANSI control characters instead of machine code control characters.
119
+
- Ignore module errors by using **ignore_errors:true** for a specific playbook task.
120
+
- If the error is resulting from a batch job, add **ignore_errors:true** to the task and capture the output into a registered variable to extract the
121
+
job ID with a regular expression. Then use ``zos_job_output`` to display the DD without the non-printable character such as the DD **JESMSGLG**.
122
+
- If the error is the result of a batch job, set option **return_output** to false so that no DDs are read which could contain the non-printable UTF-8 characters.
123
+
124
+
- In the past, choices could be defined in either lower or upper case. Now, only the case that is identified in the docs can be set, this is so that the collection can continue to maintain certified status.
125
+
- Use of special characters (#, @, $, \- ) in different options like data set names and commands is not fully supported, some modules support them but is the user responsibility to escape them. Read each module documentation for further details.
126
+
127
+
128
+
Version 1.9.1
129
+
=============
130
+
131
+
Bugfixes
132
+
--------
133
+
134
+
- ``zos_find`` - Option size failed if a PDS/E matched the pattern, now filtering on utilized size for a PDS/E is supported.
135
+
- ``zos_mvs_raw`` - Option **tmp_hlq** when creating temporary data sets was previously ignored, now the option honors the High Level Qualifier for temporary data sets created during the module execution.
136
+
137
+
Availability
138
+
------------
139
+
140
+
* `Automation Hub`_
141
+
* `Galaxy`_
142
+
* `GitHub`_
143
+
144
+
Requirements
145
+
------------
146
+
147
+
The IBM z/OS core collection has several dependencies, please review the `z/OS core support matrix`_ to understand both the
148
+
controller and z/OS managed node dependencies.
149
+
150
+
Known Issues
151
+
------------
152
+
153
+
- ``zos_job_submit`` - when setting 'location' to 'local' and not specifying the from and to encoding, the modules defaults are not read leaving the file in its original encoding; explicitly set the encodings instead of relying on the default.
154
+
- ``zos_job_submit`` - when submitting JCL, the response value returned for **byte_count** is incorrect.
155
+
156
+
- ``zos_job_submit``, ``zos_job_output``, ``zos_operator_action_query`` - encounters UTF-8 decoding errors when interacting with results that contain non-printable UTF-8 characters in the response. This has been addressed in this release and corrected with **ZOAU version 1.2.5.6** or later.
157
+
158
+
- If the appropriate level of ZOAU can not be installed, some options are to:
159
+
160
+
- Specify that the ASA assembler option be enabled to instruct the assembler to use ANSI control characters instead of machine code control characters.
161
+
- Ignore module errors by using **ignore_errors:true** for a specific playbook task.
162
+
- If the error is resulting from a batch job, add **ignore_errors:true** to the task and capture the output into a registered variable to extract the
163
+
job ID with a regular expression. Then use ``zos_job_output`` to display the DD without the non-printable character such as the DD **JESMSGLG**.
164
+
- If the error is the result of a batch job, set option **return_output** to false so that no DDs are read which could contain the non-printable UTF-8 characters.
165
+
166
+
- ``zos_data_set`` - An undocumented option **size** was defined in module **zos_data_set**, this has been removed to satisfy collection certification, use the intended and documented **space_primary** option.
167
+
168
+
- In the past, choices could be defined in either lower or upper case. Now, only the case that is identified in the docs can be set, this is so that the collection can continue to maintain certified status.
0 commit comments