Skip to content

Commit a732337

Browse files
authored
Update zos_data_set member description created (#816)
* Update zos_data_set module member description Signed-off-by: ddimatos <dimatos@gmail.com> * Adding fix for uncataloged vsam and non-vsam data sets Signed-off-by: ddimatos <dimatos@gmail.com> * Fixes the issue of parts of a vsam cluster remaining behind and allows user to correctly delete DS not in cat Signed-off-by: ddimatos <dimatos@gmail.com> * Update module doc to explain data set deltion for given volume Signed-off-by: ddimatos <dimatos@gmail.com> * Unbound local var fix Signed-off-by: ddimatos <dimatos@gmail.com> * Lint corrections Signed-off-by: ddimatos <dimatos@gmail.com> * remove unused imports Signed-off-by: ddimatos <dimatos@gmail.com> * Added 2.16 ignore since our pipeline supports devel which is at this time 2.16 Signed-off-by: ddimatos <dimatos@gmail.com> * Update module doc to explain data set deltion for given volumegit Signed-off-by: ddimatos <dimatos@gmail.com> * Added changelog fragment Signed-off-by: ddimatos <dimatos@gmail.com> * Update grammar issue Signed-off-by: ddimatos <dimatos@gmail.com> --------- Signed-off-by: ddimatos <dimatos@gmail.com>
1 parent e687a10 commit a732337

File tree

6 files changed

+324
-161
lines changed

6 files changed

+324
-161
lines changed
Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
trivial:
2+
- zos_data_set - when a member is created by the module, the format is type
3+
data which is not suitable for executables. This change describes the
4+
format used when creating member.
5+
(https://github.com/ansible-collections/ibm_zos_core/pull/816)
6+
bugfixes:
7+
- zos_data_set - Reported a failure caused when `present=absent` for a VSAM
8+
data set leaving behind cluster components. Fix introduces a new logical
9+
flow that will evaluate the volumes, compare it to the provided value and
10+
if necessary catalog and delete.
11+
(https://github.com/ansible-collections/ibm_zos_core/pull/816).
12+
- module_utils - data_set.py - Reported a failure caused when cataloging a
13+
VSAM data set. Fix now corrects how VSAM data sets are cataloged.
14+
(https://github.com/ansible-collections/ibm_zos_core/pull/816).

docs/source/modules/zos_data_set.rst

Lines changed: 15 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -56,6 +56,9 @@ state
5656
If *state=absent* and *volumes* is provided, and the data set is not found in the catalog, the module attempts to perform catalog using supplied *name* and *volumes*. If the attempt to catalog the data set catalog fails, then no action is taken. Module completes successfully with *changed=False*.
5757

5858

59+
If *state=absent* and *volumes* is provided, and the data set is found in the catalog, the module compares the catalog volume attributes to the provided *volumes*. If the volume attributes are different, the cataloged data set will be uncataloged temporarily while the requested data set be deleted is cataloged. The module will catalog the original data set on completion, if the attempts to catalog fail, no action is taken. Module completes successfully with *changed=False*.
60+
61+
5962
If *state=present* and the data set does not exist on the managed node, create and catalog the data set, module completes successfully with *changed=True*.
6063

6164

@@ -65,6 +68,9 @@ state
6568
If *state=present* and *replace=False* and the data set is present on the managed node, no action taken, module completes successfully with *changed=False*.
6669

6770

71+
If *state=present* and *type=MEMBER* and the member does not exist in the data set, create a member formatted to store data, module completes successfully with *changed=True*. Note, a PDSE does not allow a mixture of formats such that there is executables (program objects) and data. The member created is formatted to store data, not an executable.
72+
73+
6874
If *state=cataloged* and *volumes* is provided and the data set is already cataloged, no action taken, module completes successfully with *changed=False*.
6975

7076

@@ -74,7 +80,7 @@ state
7480
If *state=cataloged* and *volumes* is provided and the data set is not cataloged, module attempts to perform catalog using supplied *name* and *volumes*. If the attempt to catalog the data set catalog fails, returns failure with *changed=False*.
7581

7682

77-
If *state=uncataloged* and the data set is not found, no action taken , module completes successfully with *changed=False*.
83+
If *state=uncataloged* and the data set is not found, no action taken, module completes successfully with *changed=False*.
7884

7985

8086
If *state=uncataloged* and the data set is found, the data set is uncataloged, module completes successfully with *changed=True*.
@@ -321,6 +327,9 @@ batch
321327
If *state=absent* and *volumes* is provided, and the data set is not found in the catalog, the module attempts to perform catalog using supplied *name* and *volumes*. If the attempt to catalog the data set catalog fails, then no action is taken. Module completes successfully with *changed=False*.
322328

323329

330+
If *state=absent* and *volumes* is provided, and the data set is found in the catalog, the module compares the catalog volume attributes to the provided *volumes*. If they volume attributes are different, the cataloged data set will be uncataloged temporarily while the requested data set be deleted is cataloged. The module will catalog the original data set on completion, if the attempts to catalog fail, no action is taken. Module completes successfully with *changed=False*.
331+
332+
324333
If *state=present* and the data set does not exist on the managed node, create and catalog the data set, module completes successfully with *changed=True*.
325334

326335

@@ -330,6 +339,9 @@ batch
330339
If *state=present* and *replace=False* and the data set is present on the managed node, no action taken, module completes successfully with *changed=False*.
331340

332341

342+
If *state=present* and *type=MEMBER* and the member does not exist in the data set, create a member formatted to store data, module completes successfully with *changed=True*. Note, a PDSE does not allow a mixture of formats such that there is executables (program objects) and data. The member created is formatted to store data, not an executable.
343+
344+
333345
If *state=cataloged* and *volumes* is provided and the data set is already cataloged, no action taken, module completes successfully with *changed=False*.
334346

335347

@@ -339,7 +351,7 @@ batch
339351
If *state=cataloged* and *volumes* is provided and the data set is not cataloged, module attempts to perform catalog using supplied *name* and *volumes*. If the attempt to catalog the data set catalog fails, returns failure with *changed=False*.
340352

341353

342-
If *state=uncataloged* and the data set is not found, no action taken , module completes successfully with *changed=False*.
354+
If *state=uncataloged* and the data set is not found, no action taken, module completes successfully with *changed=False*.
343355

344356

345357
If *state=uncataloged* and the data set is found, the data set is uncataloged, module completes successfully with *changed=True*.
@@ -352,7 +364,7 @@ batch
352364
353365

354366
type
355-
The data set type to be used when creating a data set. (e.g ``pdse``)
367+
The data set type to be used when creating a data set. (e.g ``PDSE``)
356368

357369
``MEMBER`` expects to be used with an existing partitioned data set.
358370

0 commit comments

Comments
 (0)