Re: SV: [TSO-REXX] Tuning Question

Thread View: bit.listserv.tsorexx

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by Phil Smith III Fri, 08 Mar 2013 15:32

#253

Author: Phil Smith III
Date: Fri, 08 Mar 2013 15:32

19 lines
2288 bytes

Adrian Stern wrote, re being able to specify a specific EXEC or MODULE,
including filemode:
>That's asking for a big change in the os - maybe too big.

In z/OS, maybe; in CMS, not so much. Long, long ago we had an EXECx command
(part of the CMS nucleus) that would let you invoke the BANANA EXEC on the
Y-disk, overriding the one on the A-disk, as EXECY BANANA.

I've had a MODULE EXEC for 30 years that just does an
ADDRESS COMMAND arg(1)
(OK, it didn't use ADDRESS COMMAND when I first wrote it, since Rexx wasn't
out yet!). A similar MODULEx CMS nucleus facility could do the same.

Extending that further, it's not clear that a JCL extension couldn't
implement EXEC

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to LISTSERV@VM.MARIST.EDU with the message: INFO TSO-REXX

Re: SV: [TSO-REXX] Tuning Question

#255

Author: Paul Gilmartin
Date: Fri, 08 Mar 2013 16:26

43 lines
2861 bytes

On Mar 8, 2013, at 08:31, Phil Smith III wrote:

> Adrian Stern wrote, re being able to specify a specific EXEC or MODULE,
> including filemode:
>> That's asking for a big change in the os - maybe too big.
>
> In z/OS, maybe; in CMS, not so much. Long, long ago we had an EXECx command
> (part of the CMS nucleus) that would let you invoke the BANANA EXEC on the
> Y-disk, overriding the one on the A-disk, as EXECY BANANA.
>
I believe (without referring to the documentation) that the
API to Rexx allows the programmer to specify, independently:
o DDNAME
o MEMBER name
o Default command environment name.

(Why isn't the default command environment for ISPF EDIT
macros ISREDIT rather than TSO?  I suppose the programmers
who (hastily?) ported Rexx to the TSO environment were
alien to the Rexx culture.  Likewise why must one access
the parameter string with ISREDIT MACRO rather than PARSE
ARG?)

Even short of EXEC PGM=DATA.SET.NAME(MEMBER), it would
be useful to be able to code EXEC PGM=DDNAME(MEMBER).

And the CMS Pipelines REXX stage allows the programmer to
code each of FN, FT, and FM.  But the command environment
is always the Pipelines environment.

And z/OS Unix System Services implements the POSIX exec()
syscall that allows the programmer to specify a fully
qualified path, but when exec() recognizes the program as
a Rexx EXEC, it invokes the Rexx interpreter which searches
again for the EXEC, not in the path specified by the programmer,
but in directories mentioned in the PATH enviromment variable;
a drastic design flaw.

-- gil

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to LISTSERV@VM.MARIST.EDU with the message: INFO TSO-REXX

Re: SV: [TSO-REXX] Tuning Question

#256

Author: Steve Thompson
Date: Fri, 08 Mar 2013 16:59

15 lines
1645 bytes

Dumb question (like I don't know the answer).

How is the current topic of name of an exec, and if it is a synomyn etc.
related to a "Tuning Question"?

So, for the sake of future REXX people, could you change the Subject to
"CMS environmental issues of the 3rd level for operating under TSO"  or
some such?

Regards,
Steve Thompson

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to LISTSERV@VM.MARIST.EDU with the message: INFO TSO-REXX

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads