Tom Harper wrote on 10/17/2024 3:18 AM:
Leonard,
This is likely posted to a list you didn’t intend, the assembler list. Since
the question isn’t about assembler but a z/OS macro, you might try posting to
IBM-MAIN.
A distinction without much of a difference. I figured I'd try here
first since everyone here is likely an assembler programmer, which is
far from the situation with IBM-MAIN.
When I look at the doc for ATTACHX, it lists the contents of all registers
under the ETXR parameter.
OK, thanks, I missed that this time around due to the discombobulated
way that IBM presents standard, execute, and list forms completely
separately, along with listing keywords in two different places.
Reviewing it, it seems that ETXR is in the running for the
worst-designed interface in z/OS. No possible way to pass a parm to
the ETXR.
Since you have to change the code anyway, why not use a name/token to pass your
parm then you won’t need a hack?
Because that would require the ETXR to obtain its own workarea and
with the three N/T calls (create/retrieve/delete), we're looking at 5x
as many lines of code. So I'll just have to split it out to another
small dynamic area as I said.
And BTW, N/T has always been primarily a way to circumvent poorly
designed architecture.
Keven Hall wrote on 10/17/2024 5:06 PM:
a Google search probably would have answered this one.
Tried that first. No hits other than discussions of R13 and R14.
Nothing at all regarding a re-entrant ETXR.
/Leonard
