z/OS job output problem or normal behavior?

[fabiobncbb]

When using this module, we have the option of filtering the collection of only one DDNAME, however when doing so, the information is not the same if we compare the result of that DDNAME in the mainframe. I have the impression that all the data is repeated and if I am only wanting a DDNAME, some information is not important.

Below, for example, we have the output of a specific DDNAME, after executing a job on the mainframe:

And below, we have the result of the collection by zos_job_output of the same DDNAME:

I only need the information between the red lines, which are the same as the first figure.

Note that the amount of information is much greater and makes possible treatment difficult, such as consulting messages, error codes, etc.

This is my question: Is this behavior normal or am I doing something wrong?
Would it be possible to collect exactly the same as what is on the mainframe?

[ddimatos]

Hello @fabiobncbb ,
If I understand correctly would like to see only the content for a particular DD be returned and not all the DDs such is the case with this example:

    - name: Get job output job by {{sub_job_id}} for JESMSGLG
      zos_job_output:
        job_id: "{{sub_job_id}}"
        ddname: "JESMSGLG"
      register: job_output_result

If my understanding is correct this was fixed in ibm_zos_core version 1.5.0-beta.1. We will also be releasing 1.5.0 by 4/28/23 on Galaxy and Hub.
Please review the git issues, in this case this issue would be #537 where I will highlight there is no intention to back-port a fix to 1.4.x.

This is fixed in our next release of 1.5.0-beta.1, there is no plan to fix it in prior releases as a backport would mean a completely different solution be written since the code between 1.4.x and 1.5.x is completely different in both language and design.

I will wait for a response to ensure I understood correctly, in summary this is a FIN (fixed in next).

[ddimatos]

Closing given it is 30 days now with no activity.