Update zos_data_set member description created

[ddimatos]

SUMMARY

Given this change will drive over 700 tests it made sense to collapse all the related zos_data_set into one PR to avoid multiple regression pipelines.

1. Documentation: When a MEMBER is created, the format type of the member was not described, it should be clearly defined so that a user does not try to insert an executable into the data formatted member. Issue [Documentation] [zos_data_set] Update member doc to explain what type of member is created #631

2. Bug: A random issue would occur on the pipeline leaving behind VSAM cluster components be it INDEX or DATA, originally this was thought to be a test case issue and a simple test fix but after reviewing I found it much more complex and took a better part of the week to address. To fix this I had to undo most of what was done in PR 325 for bugfix [Bug] [zos_data_set] should not ignore supplied volumes #140. Although this was a good attempt, the issue was that only one of the cluster components were being deleted here with a DELETE USER.PRIVATE.TESTDS.DATA FILE(DD1) VVR while adding the other for INDEX would have been a suitable fix, the issue such a clean up leaves space unclaimed on the volume and not the correct way to back out a data set from z/OS. Thus introduced a flow of tracking state and uncatalog, catalog, delete to achieve this, see image below for most the flow, the flow has since changed with some added exception actions but mostly the flow is correct for reference. Issue [Enabler] [CI/CD] Failing to clean up environtment causes a failure. #635

3. The catalog commands were failing because of formatting, I might have been happening for a long time because of all this other related issues it might not have been apparent, thus now the commands are formatted correctly and tested. Issue [Bug] zos_data_set data_set.py utils cataloging failures #802

4. Small .ac command issue where some files are left behind were cleaned up as part of this PR because I was using ./ac --ac-test and it was inhibiting my ability to work to not fix it.

Data set deletion flow.

ISSUE TYPE

• Docs Pull Request

[ddimatos]

Jenkins: Job suffix `/job/zosAnsibleAlternate2/41/console` Log: `====================== 760 passed in 33901.51s (9:25:01) =======================` Tests: ``` + ./dependencyfinder.py -p .. -b dev -s functional/modules/test_module_security.py functional/modules/test_zos_apf_func.py -m [Pipeline] echo ../tests/functional/modules/test_zos_lineinfile_func.py ../tests/functional/modules/test_zos_fetch_func.py ../tests/functional/modules/test_zos_mvs_raw_func.py ../tests/functional/modules/test_zos_blockinfile_func.py ../tests/functional/modules/test_zos_find_func.py ../tests/functional/modules/test_zos_copy_func.py ../tests/functional/modules/test_zos_data_set_func.py ../tests/unit/test_zos_mvs_raw_unit.py ../tests/functional/modules/test_zos_backup_restore.py ../tests/functional/modules/test_zos_job_submit_func.py ../tests/functional/modules/test_zos_job_output_func.py ../tests/functional/modules/test_zos_job_query_func.py ../tests/functional/modules/test_zos_volume_init_func.py ../tests/functional/modules/test_zos_mount_func.py ../tests/functional/modules/test_zos_encode_func.py ```

[fernandofloresg]

Changes requested for changelog and unused import.

Questions about 2 rst files apparently not related to this PR and use of run_command for mvs_cmd

[fernandofloresg]

Is ok for me now, I get that having this in our dev branch will benefit us immediately. mvs_cmd can be standarized later and unused imports actually are shown get using the latest ansible 2.15 sanity scan so we will clean it 🙂 .

[ddimatos]

Imports removed from data_sets.py, thought you were referring to the pprint in the test cases, which is referenced by an unused method. Sanity ran clean on 2.15 and 2.16.

[richp405]

lgtm

[ddimatos]

Also includes issue #803 which was left out of the description.