difference between TSO, ISPEXEC and ISREDIT

rackshit · New User Joined: 19 Dec 2009 Posts: 16 Location: Mumbai

Hi,

i wanted to know the difference between TSO, ISPEXEC and ISREDIT. i came accross this confusion when i was trying to understand the use of ADDRESS instruction of REXX.

while using ADDRESS, the destination can be any of TSO, ISPEXEC or ISREDIT. So wanted to know the difference between them.

PeterHolland · Posted: Tue Mar 15, 2011 7:42 pm

Well there are also constructs like :

ADDRESS MVS
ADDRESS NETVIEW

Want to know those differences too?

superk · Posted: Tue Mar 15, 2011 7:47 pm

Pretty easy, actually.

First of all, all of these would require that your REXX exec run within a TSO/E address space. In addition, for ISPEXEC, you need to also have an ISPF session started. And for ISREDIT, an ISPF Edit or View Session has to be active.

Address TSO is, well, TSO. This would be the default anyway. This allows you to use TSO commands in your exec.

Address ISPEXEC is for ISPF Services. This would be used in any ISPF dialog execs you might create.

Address ISREDIT is for use in an ISPF Edit Macro.

enrico-sorichetti · Posted: Tue Mar 15, 2011 7:49 pm

Everything is explained

for the Address construnct
z/OS V1R2.0-V1R10.0 TSO/E REXX User's Guide
publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IKJ4C310/CCONTENTS?SHELF=IKJ4BK90&DN=SA22-7791-01&DT=20010706113306

and
z/OS V1R8.0-V1R10.0 TSO/E REXX Reference
publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IKJ4A370/CCONTENTS?SHELF=IKJ4BK90&DN=SA22-7790-07&DT=20060626210253

meditate on what is meant by HOST COMMAND ENVIRONMENT and everything will become clear as the light on a sunny day

furthermore
for the TSO environment
publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/Shelves/IKJ4BK90

for the ISPEXEC and ISREDIT environments
publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/Shelves/IKJ4BK90

( not the latest releases but more than enough to understand )

Pedro · Posted: Tue Mar 15, 2011 11:37 pm

The REXX language has powerful grouping and logic constructs, and many built-in functions. But it needs help to do I/O and other system things.

One of the strengths of REXX is that you can extend it (more or less) to invoke functions of other products. One way that you do that is by indicating which command processor will handle particular commands, through the use of the ADDRESS statement.

Depending on the work you want to perform, you will want to route some commands to TSO and others to ISPF. If you route a TSO command to ISPF or an ISPF command to TSO, you will get an error.

In addition to the ones already listed, I think there are also others, including TCPIP, IPCS, DB2, IMS operator, z/OS console, Unix services, etc... Plus you can write your own, or buy vendor products with their own host command environments.

rackshit · New User Joined: 19 Dec 2009 Posts: 16 Location: Mumbai

thnx PeterHolland, Superk, Enrico-sorichetti and Pedro; i got a fair idea about my confusion.

btw nice phrase : clear as the light on a sunny day