Author: sergeyken
Posted: Sat Feb 11, 2017 2:34 am (GMT 5.5)
I am subcontractor, and not supposed to contact the vendor directly.
After some investigation I was able to find the reason. The client's Endevor team provided so called "processor group" to "automatically perform REXX compilation, and link edit the load module". Noone of that support group was able to clarify any minor question.
Further investigation discovered that the "standard processor group" for REXX compilation had internal hardcoded REXX compiler option, the one compatible with... calling REXX from COBOL only! The created object/load modules became incompatible with calls from JCL/TSO/Assembler etc.
The Endevor team has been notified of their own problem. So far I use my own JCL to perform REXX compilation. Now it's working as described.
Thank you
Posted: Sat Feb 11, 2017 2:34 am (GMT 5.5)
| Robert Sample wrote: |
| What did the vendor say when you asked your question there? |
I am subcontractor, and not supposed to contact the vendor directly.
After some investigation I was able to find the reason. The client's Endevor team provided so called "processor group" to "automatically perform REXX compilation, and link edit the load module". Noone of that support group was able to clarify any minor question.
Further investigation discovered that the "standard processor group" for REXX compilation had internal hardcoded REXX compiler option, the one compatible with... calling REXX from COBOL only! The created object/load modules became incompatible with calls from JCL/TSO/Assembler etc.
The Endevor team has been notified of their own problem. So far I use my own JCL to perform REXX compilation. Now it's working as described.
Thank you