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: _sources/ibm_zos_core/docs/source/release_notes.rst.txt
+106-64
Original file line number
Diff line number
Diff line change
@@ -6,75 +6,92 @@
6
6
Releases
7
7
========
8
8
9
-
Version 1.11.0-beta.1
10
-
=====================
9
+
Version 1.11.0
10
+
==============
11
11
12
12
Minor Changes
13
13
-------------
14
14
15
-
- ``zos_apf`` - Added support that auto-escapes 'library' names containing symbols.
16
-
- ``zos_archive`` - Added support for GDG and GDS relative name notation to archive data sets. Added support for data set names with special characters like $, /#, /- and @.
17
-
- ``zos_backup_restore`` - Added support for GDS relative name notation to include or exclude data sets when operation is backup. Added support for data set names with special characters like $, /#, and @.
18
-
- ``zos_blockinfile`` - Added support for GDG and GDS relative name notation to specify a data set. And backup in new generations. Added support for data set names with special characters like $, /#, /- and @.
19
-
- ``zos_copy`` - Added support for copying from and copying to generation data sets (GDS) and generation data groups (GDG) including using a GDS for backup.
20
-
- ``zos_data_set`` - Added support for GDG and GDS relative name notation to create, delete, catalog and uncatalog a data set. Added support for data set names with special characters like $, /#, /- and @.
21
-
- ``zos_encode`` - Added support for converting the encodings of generation data sets (GDS). Also added support to backup into GDS.
22
-
- ``zos_fetch`` - Added support for fetching generation data groups (GDG) and generation data sets (GDS). Added support for specifying data set names with special characters like $, /#, /- and @.
23
-
- ``zos_find`` - Added support for finding generation data groups (GDG) and generation data sets (GDS). Added support for specifying data set names with special characters like $, /#, /- and @.
24
-
- ``zos_job_submit``
15
+
- ``zos_apf`` - Added support for data set names (libraries) with special characters ($, /#, /- and @).
16
+
- ``zos_archive``
25
17
26
-
- Improved the mechanism for copying to remote systems by removing the use of deepcopy, which had previously resulted in the module failing on some systems.
27
-
- Added support for running JCL stored in generation data groups (GDG) and generation data sets (GDS).
18
+
- Added support for GDG and GDS relative name notation to archive data sets.
19
+
- Added support for data set names with special characters ($, /#, /- and @).
28
20
29
-
- ``zos_lineinfile`` - Added support for GDG and GDS relative name notation to specify the target data set and to backup into new generations. Added support for data set names with special characters like $, /#, /- and @.
30
-
- ``zos_mount`` - Added support for data set names with special characters ($, /#, /- and @).
31
-
- ``zos_mvs_raw`` - Added support for GDG and GDS relative name notation to specify data set names. Added support for data set names with special characters like $, /#, /- and @.
32
-
- ``zos_script`` - Improved the mechanism for copying to remote systems by removing the use of deepcopy, which had previously resulted in the module failing on some systems.
33
-
- ``zos_tso_command`` - Added support for using GDG and GDS relative name notation in running TSO commands. Added support for data set names with special characters like $, /#, /- and @.
34
-
- ``zos_unarchive``
21
+
- ``zos_backup_restore``
35
22
36
-
- Added support for data set names with special characters like $, /#, /- and @.
37
-
- Improved the mechanism for copying to remote systems by removing the use of deepcopy, which had previously resulted in the module failing on some systems.
23
+
- Added support for GDS relative name notation to include or exclude data sets when operation is backup.
24
+
- Added support for data set names with special characters ($, /#, /- and @).
38
25
39
-
Bugfixes
40
-
--------
26
+
- ``zos_blockinfile``
27
+
28
+
- Added support for GDG and GDS relative name notation to specify a data set. And backup in new generations.
29
+
- Added support for data set names with special characters ($, /#, /- and @).
41
30
42
31
- ``zos_copy``
43
32
44
-
- a regression in version 1.4.0 made the module stop automatically computing member names when copying a single file into a PDS/E. Fix now lets a user copy a single file into a PDS/E without adding a member in the dest option.
45
-
- module would use opercmd to check if a non existent destination data set is locked. Fix now only checks if the destination is already present.
33
+
- Added support for copying from and to generation data sets (GDS) and generation data groups (GDG) including using a GDS for backup.
34
+
- Added support for data set names with special characters ($, /#, /- and @).
46
35
47
-
- ``zos_data_set`` - When checking if a data set is cataloged, module failed to account for exceptions which occurred during the LISTCAT. The fix now raises an MVSCmdExecError if the return code from LISTCAT is too high.
48
-
- ``zos_job_submit`` - The module was not propagating any error types including UnicodeDecodeError, JSONDecodeError, TypeError, KeyError when encountered. The fix now shares the type error in the error message.
49
-
- ``zos_mvs_raw`` - The first character of each line in dd_output was missing. The fix now includes the first character of each line.
36
+
- ``zos_data_set``
50
37
51
-
Availability
52
-
------------
38
+
- Added support for GDG and GDS relative name notation to create, delete, catalog and uncatalog a data set.
39
+
- Added support for data set names with special characters ($, /#, /- and @).
53
40
54
-
* `Galaxy`_
55
-
* `GitHub`_
41
+
- ``zos_encode``
56
42
57
-
Requirements
58
-
------------
43
+
- Added support for converting the encodings of generation data sets (GDS).
44
+
- Added support for data set names with special characters ($, /#, /- and @).
59
45
60
-
The IBM z/OS core collection has several dependencies, please review the `z/OS core support matrix`_ to understand both the
61
-
controller and z/OS managed node dependencies.
46
+
- ``zos_fetch``
62
47
63
-
Known Issues
64
-
------------
65
-
- ``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.
66
-
- ``zos_job_submit`` - when submitting JCL, the response value returned for **byte_count** is incorrect.
67
-
- ``zos_apf`` - When trying to remove a library that contains the '$' character in the name from APF(authorized program facility), operation will fail.
68
-
- 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.
48
+
- Added support for fetching generation data groups (GDG) and generation data sets (GDS).
49
+
- Added support for data set names with special characters ($, /#, /- and @).
69
50
51
+
- ``zos_find``
70
52
71
-
Version 1.9.2
72
-
=============
53
+
- Added support for finding generation data groups (GDG) and generation data sets (GDS).
54
+
- Added support for data set names with special characters ($, /#, /- and @).
55
+
56
+
- ``zos_job_submit``
57
+
58
+
- Improved the mechanism for copying to remote systems by removing the use of deepcopy, which had previously resulted in the module failing on some systems.
59
+
- Added support for running JCL stored in generation data groups (GDG) and generation data sets (GDS).
60
+
- Added support for data set names with special characters ($, /#, /- and @).
61
+
62
+
- ``zos_lineinfile``
63
+
64
+
- Added support for GDG and GDS relative name notation to specify the target data set and to backup into new generations.
65
+
- Added support for data set names with special characters ($, /#, /- and @).
66
+
67
+
- ``zos_mount`` - Added support for data set names with special characters ($, /#, /- and @).
68
+
- ``zos_mvs_raw``
69
+
70
+
- Added support for GDG and GDS relative name notation to specify data set names.
71
+
- Added support for data set names with special characters ($, /#, /- and @).
72
+
73
+
- ``zos_script`` - Improved the mechanism for copying to remote systems by removing the use of deepcopy, which had previously resulted in the module failing on some systems.
74
+
- ``zos_tso_command``
75
+
76
+
- Added support for using GDG and GDS relative name notation in running TSO commands.
77
+
- Added support for data set names with special characters ($, /#, /- and @).
78
+
79
+
- ``zos_unarchive``
80
+
81
+
- Improved the mechanism for copying to remote systems by removing the use of deepcopy, which had previously resulted in the module failing on some systems.
82
+
- Added support for data set names with special characters ($, /#, /- and @).
73
83
74
84
Bugfixes
75
85
--------
76
86
77
-
- ``zos_copy`` - when creating the destination data set, the module would unnecessarily check if a data set is locked by another process. The module no longer performs this check when it creates the data set.
87
+
- ``zos_copy``
88
+
89
+
- Fixes the issue that prevents the module from automatically computing member names when copying a file into a PDS/E. The module now computes the member name when copying into a PDS/E.
90
+
- Fixes an issue that would perform an unnecessary check if a destination data set is locked for data sets the module created. The module only performs this check for destinations that are present.
91
+
92
+
- ``zos_data_set`` - When checking if a data set is cataloged, module failed to account for exceptions which occurred during the LISTCAT. The module now raises an MVSCmdExecError if the return code from LISTCAT exceeds the determined threshold.
93
+
- ``zos_job_submit`` - Was not propagating any error types including UnicodeDecodeError, JSONDecodeError, TypeError, KeyError when encountered. The module now shares the error type (UnicodeDecodeError, JSONDecodeError, TypeError, KeyError) in the error message.
94
+
- ``zos_mvs_raw`` - The first character of each line in dd_output was missing. The module now includes the first character of each line.
78
95
79
96
Availability
80
97
------------
@@ -87,28 +104,13 @@ Requirements
87
104
------------
88
105
89
106
The IBM z/OS core collection has several dependencies, please review the `z/OS core support matrix`_ to understand both the
90
-
controller and z/OS managed node dependencies.
107
+
control node and z/OS managed node dependencies.
91
108
92
109
Known Issues
93
110
------------
94
-
95
-
- ``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 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.
96
112
- ``zos_job_submit`` - when submitting JCL, the response value returned for **byte_count** is incorrect.
97
-
98
-
- ``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.
99
-
100
-
- If the appropriate level of ZOAU can not be installed, some options are to:
101
-
102
-
- Specify that the ASA assembler option be enabled to instruct the assembler to use ANSI control characters instead of machine code control characters.
103
-
- Ignore module errors by using **ignore_errors:true** for a specific playbook task.
104
-
- 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
105
-
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**.
106
-
- 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.
107
-
108
-
- ``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.
109
-
110
-
- 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.
111
-
113
+
- ``zos_apf`` - When trying to remove a library that contains the '$' character in the name from APF(authorized program facility), operation will fail.
112
114
113
115
Version 1.10.0
114
116
==============
@@ -228,6 +230,46 @@ Known Issues
228
230
- 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.
229
231
- 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.
230
232
233
+
Version 1.9.2
234
+
=============
235
+
236
+
Bugfixes
237
+
--------
238
+
239
+
- ``zos_copy`` - when creating the destination data set, the module would unnecessarily check if a data set is locked by another process. The module no longer performs this check when it creates the data set.
240
+
241
+
Availability
242
+
------------
243
+
244
+
* `Automation Hub`_
245
+
* `Galaxy`_
246
+
* `GitHub`_
247
+
248
+
Requirements
249
+
------------
250
+
251
+
The IBM z/OS core collection has several dependencies, please review the `z/OS core support matrix`_ to understand both the
252
+
controller and z/OS managed node dependencies.
253
+
254
+
Known Issues
255
+
------------
256
+
257
+
- ``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.
258
+
- ``zos_job_submit`` - when submitting JCL, the response value returned for **byte_count** is incorrect.
259
+
260
+
- ``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.
261
+
262
+
- If the appropriate level of ZOAU can not be installed, some options are to:
263
+
264
+
- Specify that the ASA assembler option be enabled to instruct the assembler to use ANSI control characters instead of machine code control characters.
265
+
- Ignore module errors by using **ignore_errors:true** for a specific playbook task.
266
+
- 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
267
+
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**.
268
+
- 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.
269
+
270
+
- ``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.
271
+
272
+
- 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.
<spanclass="p p-Indicator">-</span><spanclass="nt">name</span><spanclass="p">:</span><spanclass="l l-Scalar l-Scalar-Plain">Archive multiple data sets into a new GDS</span>
0 commit comments