[Bug] [zos_job_submit] Jobs with a JCL error which get purged as a result end up with not helpful error #681
Description
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.2
IBM Enterprise Python
v3.11.x
IBM z/OS Ansible core Version
v1.5.0
ansible-version
v2.14.x
z/OS version
v2.5
Ansible module
zos_job_submit
Bug description
When a job which has a JCl error that appends and is immediately purged ends up in an last attempt exception that serves as a basic catchall and is not complete in its msg. This can be managed sooner to avoid the catchall since we can detected it sooner.
Depending if there is a time out or not it will end up here with no timeout
result["msg"] = ("The JCL submitted with job id {0} but "
"there was an error, please review "
"the error for further details: {1}.".format
(str(job_submitted_id), str(err)))
and here with a timeout
"The JCL submitted with job id {0} but appears to be a long "
"running job that exceeded its maximum wait time of {1} "
"second(s). Consider using module zos_job_query to poll for "
"a long running job or increase option 'wait_times_s` to a value "
"greater than {2}."
in both cases there will not be a JOB ID which will not be helpful because the system purged it, but if we do catch this early on we can better provide a message with a job name and explain why it might happen.
Playbook verbosity output.
No response
Ansible configuration.
No response
Contents of the inventory
No response
Contents of group_vars or host_vars
No response