It was reported that when using job_query with a started task unexpected results were occurring. It should be known that the collection does not currently support started tasks, the reason is because a started task although like a batch job will yield different behaviors and for that should be specifically handled, thus it is not recommended to use the current module for started tasks.
This would be a validation enabler item to ensure the fix from the dependency is working.
While not supported, the team did notice that the underlying dependency had a bug that would eventually need to be addressed so that start tasks could be supported so its worth noting and tracking that work now.
The issue is that ZOAU returns different results for started tasks with status execution, for instance:
Started task IRRDPTAB who's execution status is awaiting ,
But then another started task DHCPCLNT where its status is execution
JOB(DHCPCLNT) STATUS=(EXECUTING/STL1)
gets no result from pjdd:
pjdd STC00069 EVENTLOG
It appears the parsing of the eventlog might be the source of the issue for the dependency:
The EVENTLOG data set is allocated automatically for every batch job, started task, and TSO user. It contains machine readable records and is intended to be processed by applications
This was all reported on zoau 1.2.5.6 but also on 1.3 i ran with the -j to see the JSON results and had similar experience, notice the content responses differ:
Is there an existing issue for this?
Bug description
It was reported that when using job_query with a started task unexpected results were occurring. It should be known that the collection does not currently support started tasks, the reason is because a started task although like a batch job will yield different behaviors and for that should be specifically handled, thus it is not recommended to use the current module for started tasks.
This would be a validation enabler item to ensure the fix from the dependency is working.
While not supported, the team did notice that the underlying dependency had a bug that would eventually need to be addressed so that start tasks could be supported so its worth noting and tracking that work now.
The issue is that ZOAU returns different results for started tasks with status execution, for instance: Started task
IRRDPTAB
who's execution status isawaiting
,gets the program name
IKJEFT01
For started tasks
TCPIP
where its status isexecution
gets the program name
ARTSRPLY
But then another started task
DHCPCLNT
where its status isexecution
gets no result from pjdd:
It appears the parsing of the eventlog might be the source of the issue for the dependency:
This was all reported on zoau 1.2.5.6 but also on 1.3 i ran with the
-j
to see the JSON results and had similar experience, notice the content responses differ:IBM z/OS Ansible core Version
v1.9.0
IBM Z Open Automation Utilities
v1.2.5 (default)
IBM Enterprise Python
v3.11.x (default)
ansible-version
v2.16.x (default)
z/OS version
v2.5 (default)
Ansible module
zos_job_query
Playbook verbosity output.
No response
Ansible configuration.
No response
Contents of the inventory
No response
Contents of
group_vars
orhost_vars
No response