[Bug] [zos_job_query] Appears to use a wildcard when a job_id is used.

[ddimatos]

Is there an existing issue for this?

• There are no existing issues.

Bug description

Part of Epic: [Enabler] [Epic] [zos_job_query] Performance evaluation and issue related tasks. #1841

This is a slight variation of the issue reported in #1764 , after reading the log it appears that * or just no value is sent to ZOAU causing all jobs to be quarried. At the time of writing this issue it appears this way from the log, I have not reviewed code, or forced an stdout to verify.

In #1764, the task is below.

- name: "STC running check"
  delegate_to: zceeZosLpar
  ibm.ibm_zos_core.zos_job_query:
    job_id: "JOB04719"
  register: bcResult

The log confirmed the task arguments as:

{"module_args": {"job_name": "EDMCARD1", "owner": null, "job_id": null}

Yet ZOAU claimed it ran on the modules behalf:

jls -j -o owner,name,id,status,ccode,jobclass,serviceclass,priority,asid,creationdate,creationtime,queueposition,jobtype,programname --

If ZOAU is correct (else they have a bug) then our module is overly compensating and not only impacting performance, it could trigger SAF violations trying to access jobs that were not intended or instructed to do so.

This issue will be part of a larger epic.

IBM z/OS Ansible core Version

v1.11.0

IBM Z Open Automation Utilities

v1.3.1

IBM Enterprise Python

v3.11.x

ansible-version

v2.14.x

z/OS version

v2.5

Ansible module

No response

Playbook verbosity output.

No response

Ansible configuration.

No response

Contents of the inventory

No response

Contents of group_vars or host_vars

No response