A question about Zowe TSO Node SDK

[JWaters02]

Hi everyone,

I want to preface this post by saying that my fundamental understanding of TSO/E is lacking (I simply have not worked in this area of MF before) so please understand if my terminology is wrong and this perhaps seems obvious.

Today I have been working with the Zowe TSO SDK. I can execute simple REXX programs in TSO address space with simple EX "path to rexx program", without even needing to deal with starting a TSO session first (I believe that the SDK just handles it for you?). However, I am super stuck trying to figure out how to deal with the REXX program pointing to other address spaces, namely the ISPEXEC one.

So the REXX program runs in address tso but does some stuff like address "ISPEXEC" "LIBDEF ISPMLIB DATASET ID('"jobLIB"')" and "ISPEXEC FTOPEN TEMP" and address "ISPEXEC" "LIBDEF ISPMLIB". Not sure how to access the different address spaces using the CLI or SDK (or in z/OSMF REST API webview).

I was looking around the z/OSMF REST docs in the TSO/E section, and could get my servletkey for the running session, and wondering if post /zosmf/tsoApp/app/{servletKey}/{appKey} is perhaps the right endpoint to start the ISPEXEC address space before executing the REXX program. But don't know.

For the time being I am just going to submit a batch job to submit the REXX program, but would like to get this TSO method working as its much faster than submitting a job.

Please let me know if I am not making sense and want some more examples 🙂

Thanks,
Joshua

[dkelosky]

In REXX, address isn't exactly referencing an "address space". It's an "environment". For example, see the TSO command environment.

This is not a complete answer but you'll find some more information here #645