[Enhancement] [zos_data_set] support force: true with batch option

[adn1107]

Is there an existing issue for this?

• [X] There are no existing issues.

Ansible module

zos_data_set

Enhancement or feature description

force: true is not supported with batch option?

    - name: Clean zCloud PROCLIB
      zos_data_set:
        batch:
          - name: '{{ zCloud_PROCLIB }}({{ DFS_IMS_SSID }}CTL)'
            state: absent
            type: MEMBER
            force: true
          - name: '{{ zCloud_PROCLIB }}({{ DFS_IMS_SSID }}DLI)'
            state: absent
            type: MEMBER
            force: true
          - name: '{{ zCloud_PROCLIB }}({{ DFS_IMS_SSID }}DRC)'
            state: absent
            type: MEMBER
            force: true
          - name: '{{ zCloud_PROCLIB }}({{ DFS_IMS_SSID }}OM)'
            state: absent
            type: MEMBER
            force: true
          - name: '{{ zCloud_PROCLIB }}({{ DFS_IMS_SSID }}SCI)'
            state: absent
            type: MEMBER
            force: true
          - name: '{{ zCloud_PROCLIB }}({{ DFS_IMS_SSID }}RM)'
            state: absent
            type: MEMBER
            force: true
          - name: '{{ zCloud_PROCLIB }}({{ DFS_IMS_SSID }}ODBM)'
            state: absent
            type: MEMBER
            force: true

TASK [ims_proclib : Clean zCloud PROCLIB] **** fatal: [wazi]: FAILED! => {"changed": false, "msg": "Unsupported parameters for (zos_data_set) module: batch.force. Supported parameters include: block_size, directory_blocks, key_length, key_offset, name, record_format, record_length, replace, sms_data_class, sms_management_class, sms_storage_class, space_primary, space_secondary, space_type, state, type, volumes (data_class, format, size, volume)."}

[fernandofloresg]

Using force as an option within batch will need no further change other than changing the validation schema and testing it.

[rexemin]

This issue was fixed by #718.

[rexemin]

@adn1107 Could you try this playbook again with an updated version of ibm_zos_core?