On Sat, 21 Jun 2025 01:37:29 -0400, Tony Harminc <[email protected]> wrote:

>Integrating a new language (such as has been proposed for OOREXX) is not
>possible with the doc and mappings supplied.

What necessary doc and mapping is missing? I'm guessing you're thinking OUTTRAP 
but everything you need is there. I know because I've implemented it in a 
product and it's not difficult if the product is designed correctly. ISPF is 
not a problem. Calling commands not a problem.

The difficulty comes in with OOREXX implementation which is written in C and 
designed with a Unix mindset. Realize that TSO can be dubbed but that does not 
function fully as a Unix address space (BPXAS). 

>With TSO/E IBM added several new functions that they chose not
>to document the workings of or provide APIs for. Notably, the REXX
>interface to TSO/E is not fully documented. 

Adding new REXX environment is fully documented. TSO/e environment definitions 
are not documented because it's not a user interface. It's not difficult to 
figure out since it uses the documented REXX interfaces. 

>The ability to run APF authorized TSO commands 

AUTHCMD is documented. When environmental issues are encountered, the TSOEXEC 
command can often circumvent those problems. What more do you need?

>or programs is not documented at all.

I suspect the doc exists but buried deep. Using AUTHPGM is extremely dangerous 
because you are passing pointers instead of documented command text. If it's 
not documented, then vendors should be able to get IBM internal doc for it. I 
suspect it's not difficult to figure out. For me, PC routines have been 
sufficient. Realize that the TSO parser can be used without TSO.
 
> (To be clear,
>I mean the ability to write your own TMP that does that is not documented.)
>And there are OCO extensions to several TSO/E control blocks that are not
>documented at all.

With regards to OOREXX, I believe everything needed is documented. For 
resolving other problems, that can only be determined once the problem has been 
defined. OCO is both a hinderance and advantage.

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

Reply via email to