On Mon, 23 Jun 2025 20:23:39 +0000, Seymour J Metz <[email protected]> wrote:

>I'm following your example of civility.

Thanks for letting me know.

>How does calling ISPEXEC cause you to lose access to variables and how would 
>that differ 
>between TSO/E REX and ooRexx? The complaint about REXX is that when a REXX 
>script 
>calls an external REXX script, the callee has no access to the caller's 
>variable, 
>but that's less of a problem with ooRexx.

This is true if the callee is called thru an ooRexx compliant method. However, 
is it compliant when the callee is called through various TSO methods (ISPEXEC 
SELECT).

>ooRexx is not a TSO scripting language only because it has not been fully 
>ported to TSO. 
>If you believe that there are other obstacles, feel free to identify them.

Consider a similar known situation. From the recent questionnaire on improving 
Python, we know it will run on z/OS. If it can run in batch, it should be able 
to run in TSO. TSO improvements were eerily missing from the questionnaire. It 
appears to have the same restrictions as Rexx. I can only speculate that ooRexx 
has this same limitation.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to