Question: zos_submit It is possible submit more than 1 element?

[JCzOS]

Hi all,

I am creating some JCLs using a loop, this JCL is located on USS and I submit them using:

    - name: Submit de JCLS
      ibm.ibm_zos_core.zos_job_submit:
        src: "/u/ibmuser/jcls/{{ item }}"
        wait_time_s: 86400
        location: USS  
        max_rc: 8
      loop: "{{ file_list.stdout_lines }}" 

I dont know (and didnt found doc.) about if it is possible to submit all Jcls in paralell.

At this time, jcls are submitted approximately 10 minutes apart from one to the next. And Any job is around 2 minutes.

I am also not able to use wait_time_s in rigth way, I am always facing this issue:

failed: [lrdtts02] (item=bindpla1.jcl) => {"ansible_loop_var": "item", "changed": false, "duration": 46, "item": "bindpla1.jcl", "job_id": null, "msg": "The job /u/ibmuser/jcls/bindpla1.jcl has been submitted and no job id was returned within the allocated time of 86400 seconds. Without the job id, the error can not be determined, consider using module zos_job_query to poll for the job by name or review the system log for purged jobs resulting from an abend."}

failed: [lrdtts02] (item=bindpla2.jcl) => {"ansible_loop_var": "item", "changed": false, "duration": 56, "item": "bindpla2.jcl", "job_id": null, "msg": "The job /u/ibmuser/jcls/bindpla2.jcl has been submitted and no job id was returned within the allocated time of 86400 seconds. Without the job id, the error can not be determined, consider using module zos_job_query to poll for the job by name or review the system log for purged jobs resulting from an abend."}

Thanks in advance.

[fernandofloresg]

Hi @JCzOS.

Ansible does support asynchronous playbook tasks unfortunately, the zos_job_submit module does not support this mode, we have an issue to enable this functionality #1249. For now, you can use different playbooks to enable do stuff in parallel.

Now for the wait_time_s error you are getting, I assume that the job works correctly without this option? Just tested it and appears to be working fine in the latest version.
Did you check with zos_job_query by name or owner to check the job status?

If you continue to have this problem I encourage you to open a new issue so we can a look into this.

[fernandofloresg]

Hi @JCzOS, the we have added async support for zos_job_submit in #1786 in v1.13.0-beta.1, which should be released next quarter around January/February.

I'm closing this discussion after 60 days of inactivity.