Re: SV: [TSO-REXX] Tuning Question

Thread View: bit.listserv.tsorexx

2 messages

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

2 total messages Started by Phil Smith III Fri, 08 Mar 2013 15:25

#252

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

14 lines
1950 bytes

Paul Gilmartin wrote:
>Wouldn't PARSE SOURSE always have returned XEDIT unless the
>user had defined a SYNONYM?

Your observation is correct, but what I meant is that using PARSE SOURCE let
me determine whether the code was invoked as XEDIT EXEC, FLIST EXEC, et al.
-- that is, which of my traps had sprung. Sorry for being unclear! (as
opposed to "nuclear", which would also be common on the Interwebs...)

...phsiii

----------------------------------------------------------------------
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

#254

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

22 lines
2645 bytes

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

> Paul Gilmartin wrote:
>> Wouldn't PARSE SOURSE always have returned XEDIT unless the
>> user had defined a SYNONYM?
> 
> Your observation is correct, but what I meant is that using PARSE SOURCE let
> me determine whether the code was invoked as XEDIT EXEC, FLIST EXEC, et al.
> -- that is, which of my traps had sprung. Sorry for being unclear! (as
> opposed to "nuclear", which would also be common on the Interwebs...)
>  
An EXEC ought to be able to know its own name without PARSE SOURCE.
But PARSE SOURCE tells you whether it was invoked as a SYNONYM.
And if you needed a dozen EXECs to front-end a dozen commands,
PARSE SOURCE allows you to make a dozen differently named copies
without the need to tailor each to know its own name.

-- gil

----------------------------------------------------------------------
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