ibm_zos_core modules and ZOAU compatibility with JES3 enivironment

[ddimatos]

Discussed in #1489

^{Originally posted by bcronefnts April 30, 2024}
I would like to know if the ibm_zos_core modules and IBM ZOAU are compatible with a JES3 environment. I am getting unpredictable results when attempting to submit a JOB, Query a JOB, or list the OUTPUT of the the JOB. When submitting a JOB Ansible never gets a return that the JOB completed successfully. When I attempt to list the OUTPUT of the JOB, the module is successful, but I get no output. Are these tools compatible with a JES3 environment, or do they only work with JES2?

[couckearthur]

We are a JES3 environment, actually a JES3+ (Phoenix) environment. The problems with the job submitting we had in the past was due to the following:
"In the ZOAU coding the programmers are using SSI 54 (the Request Subsystem Version Information Call) to retrieve the literals SSVIFMID/SSVIVERS.
These literals have been changed with JES3Plus. ZOAU has a hard-coded dependency on IBM z/OS JES3 identification literals appearing in the SSI 54 response."

After quite some discussions between us, IBM (and the ZOAU development team) the conclusion was that JES3+ is unsupported. And soon IBM JES3 also becomes unsupported I suppose as IBM will not deliver it anymore...

So in our case Ed Jaffe fixed with introducing a 'bad actor' table in their latest version to catch that SSVIFMID/SSVIVERS mismatch. Personally I try to avoid submitting a job with using the zos_mvs_raw module.

I still have to test how the job submitting is behaving now with our latest JES3+ version and ZOAU 1.3. I will post the outcome here