[Bug] zos_ping when using ansible-core 2.19

[ddimatos]

Is there an existing issue for this?

• There are no existing issues.

Bug description

This happens when using ansible-core 2.19 which currently is in tech preview, this is an informative but as I understand its in tech preview and an unsupported ansible version but thought it worth noting.

TASK [Test ibm.ibm_zos_core zos_ping.] *****************************************
[ERROR]: Task failed: not enough values to unpack (expected 4, got 2)
Origin: /private/tmp/ibm-zos-ee/test.yml:36:7

34         msg: "{{ result }}"
35
36     - name: Test ibm.ibm_zos_core zos_ping.
         ^ column 7

fatal: [zvm]: FAILED! => {"changed": false, "msg": "Task failed: not enough values to unpack (expected 4, got 2)"}

Changing the ansible-core version to an older version works fine.

Playbook task:

    - name: Test ibm.ibm_zos_core zos_ping.
      ibm.ibm_zos_core.zos_ping:
      register: result

    - name: Print ibm.ibm_zos_core zos_ping result.
      ansible.builtin.debug:
        msg: "{{ result }}"
```

### IBM z/OS Ansible core Version

v1.14.0

### IBM Z Open Automation Utilities

v1.3.3

### IBM Enterprise Python

v3.11.x

### ansible-version

v2.15.x

### z/OS version

v2.5

### Ansible module

_No response_

### Playbook verbosity output.

_No response_

### Ansible configuration.

```YAML

```

### Contents of the inventory

```YAML

```

### Contents of `group_vars` or `host_vars`

```YAML

```