On Thu, 5 May 2022 12:23:30 +0000, Seymour J Metz <[email protected]> wrote:
>I can parse that sentence two ways:
>
> 1. SUBCOM iis available for the environment name MVS and TSO.
> 2. SUBCOM is available for all of the MVS environment and all of the TSO
> environments
>
>For the second reading, "that is" makes sense; for the first reading it does
>not. In either case, SH should be listed for both TSO and non-TSO.
>
>Na�vely, I would expect that SUBCOM will only work in ATTACH, ATTCHMVS,
>ATTCHPGM, LINK, LINKMVS, LINKPGM, MVS and TSO.
I think they're both right, though very poorly worded.
The "SUBCOM" command is available in TSO and MVS command environments. That
is, you can
Address MVS "SUBCOM whatever"
or
Address TSO "SUBCOM whatever"
At the same time, it's available in all REXX runtime environments because the
exec can explicitly Address MVS to issue it. I am looking at this through the
lens of z/VM which established these concepts in the first place.
I'm curious if you can issue EXECIO or SUBCOM at the TSO command line. In z/VM
these are genuine CMS commands that can be used in environments outside of (and
much older than) REXX, such as the EXEC and EXEC2 languages or even an
assembler program. Still, there is no real requirement for a SUBCOM
environment be exactly the same as the interactive environment it represent.
The SUBCOM handler gets control and decides whether to do something itself or
pass it along.
Alan Altmark
IBM
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
