> An application does not require you to initialize REXX. > TSO %MYREXX will automatically initialize REXX for all >programs executed from MYREXX exec
No, the application has to have code to recognize that syntax, and ISPF is not the only application to run under TSO. Further, we seem to be talking at cross purposes; the issue is being able to script an application with REXX. > Knowledge of REXX nor knowledge of REXX syntax is needed. > The developer only needs to learn the specific API's needed > and write a very basic test of that functionality. There is no > requirement to even use one REXX API call to be REXX > compatible. FSVO "REXX compatible" that has absolutely no connection to anything I wrote. Write a TSO command processor and the command output is automatically available to REXX using outtrap. That has nothing to do with scripting the application in REXX. > The knowledge is available in the REXX documentation > for using API. Well, duh! How does that contradict "If they don't have knowledge of vthe API then they will have a hard time using it."? They have to actually read the API documentation, after which they have knowledge of it. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Jon Perryman <[email protected]> Sent: Thursday, July 4, 2024 1:32 AM To: [email protected] Subject: Re: As a long-time Rexx programmer On Wed, 3 Jul 2024 19:36:52 +0000, Seymour J Metz <[email protected]> wrote: Sorry, it submitted before I finished. >> Instead, an ADDRESS environment is created but even that is not a >> requirement. >It isiff you want the application to be scriptable. Otherwise, not. An application does not require you to initialize REXX. TSO %MYREXX will automatically initialize REXX for all programs executed from MYREXX exec. No need to create an ADDRESS environment. > >> Again, having a knowledge of REXX would be useful but by no means shouldn't >> stop anyone from using the API to create variables. >You seem to be conflating "knowledge ff REXX" with "knowledge of REXX syntax". >Knowledge of the API is what the developer needs. Knowledge of REXX nor knowledge of REXX syntax is needed. The developer only needs to learn the specific API's needed and write a very basic test of that functionality. There is no requirement to even use one REXX API call to be REXX compatible. Write a TSO command processor and the command output is automatically available to REXX using outtrap. >> Again, having a knolledge of REXX would be useful but by no means shouldn't >> stop anyone from using the API to create variables. >If they don't have knowledge of vthe API then they will have a hard time using >it. That said, some things can be done with the TSO API. The knowledge is available in the REXX documentation for using API. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
