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. 

When I look at the doc for ATTACHX, it lists the contents of all registers 
under the ETXR parameter. 

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?

Tom Harper

Phoenix Software International 

Sent from my iPhone

> On Oct 17, 2024, at 4:05 AM, Leonard D Woren <[email protected]> wrote:
> 
> I can't find any doc at all on registers at entry to the ETXR on ATTACH[X], 
> other than R13 and R14.  Can anyone point me to official IBM doc for more 
> registers at entry to ETXR?
> 
> The reason I'm looking for this is that I have a RENT program with an ETXR, 
> and I'm using a half-century old ugly hack, which is to copy a stub to 
> dynamic storage and have a parm pointer in the dynamic area following the 
> stub.
> 
> The problem is that I'm changing the main dynamic area to EXECUTABLE=NO and 
> it would be annoying to have to a obtain and track another tiny bit of 
> storage just for the stub.
> 
> So, the question really boils down to "how do you write a re-entrant ETXR 
> without copying a stub to dynamic storage?"
> 
> 
> /Leonard
> 


--------------------------------------------------------------------------------
This e-mail message, including any attachments, appended messages and the
information contained therein, is for the sole use of the intended
recipient(s). If you are not an intended recipient or have otherwise
received this email message in error, any use, dissemination, distribution,
review, storage or copying of this e-mail message and the information
contained therein is strictly prohibited. If you are not an intended
recipient, please contact the sender by reply e-mail and destroy all copies
of this email message and do not otherwise utilize or retain this email
message or any or all of the information contained therein. Although this
email message and any attachments or appended messages are believed to be
free of any virus or other defect that might affect any computer system into
which it is received and opened, it is the responsibility of the recipient
to ensure that it is virus free and no responsibility is accepted by the
sender for any loss or damage arising in any way from its opening or use.

Reply via email to