🚀 go-pugleaf

On Mar 7, 2013, at 07:12, Phil Smith III wrote:
> 
> ObAnecdote: A million years ago, I suspected another sysprog was browsing
> others' CMS A-disks, using a hack that let him see mode 0 files ...
>  
And did you have a problem with that, or were you just giving
him quid-pro-quo?

> ... I created an XEDIT EXEC that was mode 0 and would
> examine the invoking userid. If it was not one of mine, ...
>  
Might someone else have had a problem with your doing that?

> ...; it was smart enough to do a PARSE SOURCE to invoke the
> REAL, intended command underneath, as well as to include that command in the
> message it sent). ...
>  
Wouldn't PARSE SOURSE always have returned XEDIT unless the
user had defined a SYNONYM?

-- gil

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

As far as I remember that's exactly how it works - the first found with that
name is the one executed - sorry commands not functions perhaps - it was so
long ago

-----Original Message-----
From: TSO REXX Discussion List [mailto:TSO-REXX@VM.MARIST.EDU] On Behalf Of
Phil Smith III
Sent: den 7 mars 2013 15:13
To: TSO-REXX@VM.MARIST.EDU
Subject: Re: [TSO-REXX] SV: [TSO-REXX] Tuning Question

Adrian Stern wrote:
>After the incident with the rogue Xedit I seem to remember I did quote
>almost every BIF just to make sure I got the BIF and not some sysprog's
>version!
>That was in CMS

Why? That isn't how it works. Having a POS EXEC isn't going to make a POS
function call suddenly invoke that EXEC:

POS EXEC:
/**/ say 'Hi'

From Rexx:
say pos(1, 2)
0
call pos 1, 2
say result
0
'EXEC POS'
Hi

ObAnecdote: A million years ago, I suspected another sysprog was browsing
others' CMS A-disks, using a hack that let him see mode 0 files (this was
well before ACCESSM0). I created an XEDIT EXEC that was mode 0 and would
examine the invoking userid. If it was not one of mine, it would send me a
CP MSG noting that userid x had the disk LINKed and ACCESSed with mode 0
files accessible. Sure enough, I caught him the next day. (I also copied it
as FLIST and BROWSE; it was smart enough to do a PARSE SOURCE to invoke the
REAL, intended command underneath, as well as to include that command in the
message it sent). I still have that EXEC, although it's of no practical use
now.

...phsiii

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

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