[Bug] [zos_job_query] performance with added column(s)

[ddimatos]

Is there an existing issue for this?

• There are no existing issues.

Are the dependencies a supported version?

• The dependencies are supported.

IBM Z Open Automation Utilities

v1.2.4

IBM Enterprise Python

v3.9.x

IBM z/OS Ansible core Version

v1.7.0-beta.1

ansible-version

v2.15.x

z/OS version

v2.5

Ansible module

zos_job_output, zos_job_query

Bug description

This issue is actually in module_utils/job.py and not particularly a bug as it is a performance issue.

In ZOAU 1.2.3 additional job values were available and those were included in ibm_zos_core 1.7.0-beta.1 (or planned to be) then also program_name which is is in ZOAU 1.2.4 , the team was able to address both where program_name was delivered early.

program_name is known to be an expensive call and likely should be its own option to enable but before going the route of one option to one job value, some performance needs to be done to evaluate if the overhead is acceptable to not have to introduce an option.

This evaluation can not complete until zoau python supports a kwargs -o to allow for ansible to do further testing with and without program_name.

When comparing zoau 1.2.4 to zoau 1.2.2 where ansible did not take into account any additional job values, the performance was 4x slower. While this is generally not an issue for one job via a submit, query or output it can be a problem when wild cards are used that may take more than a minute to respond with a reply.

Thus in this issue, we wait for the kwags support for -o to do some evaluation on if we need to limit the job values and program_name with an option.

Playbook verbosity output.

No response

Ansible configuration.

No response

Contents of the inventory

No response

Contents of group_vars or host_vars

No response

[ddimatos]

ZOAU tracker NAZARE-10018