On Thursday, October 17, 2024 at 05:54:46 PM PDT, Leonard Woren
<[email protected]> wrote:
> 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.
To call this a poor design tells me you need a refresher on multi-tasking
because this is the only possible design for ETXR. Task exit is the last thing
performed by your task and it has no way of knowing if the parm has been freed
or overlayed.
Of the possible designs, the most straight forward is to create a CB for the
attached task (retained for the life of the task) and pass it through the
ATTACH parm. If at the start of your task, you properly saved your registers,
then the task can always access it through TCBFSA (first save area for the TCB)
=> R1 => attach parm.
> And BTW, N/T has always been primarily a way to circumvent poorly> designed
> architecture.
What is the poor design that you are referring to? How does Linux solve this
problem?
