Re: Purpose of uppercasing a RUN command ?

I have no particular insights, but ISTM that since it is possible to
SET PROCESS/PARSE=EXTENDED with ODS5, then this may guarantee a match.

JF Mezei <jfmezei.spamnot@xxxxxxxxxxxx> wrote on 11/17/2006 06:12:44 AM:

Found this jewel in the SYS$SYSTEM directory:

$ run:
$ run 'f$edit("sys$system:tcpip$smtp_receiver.exe","upcase")'


Since this is written supposedly by people part of VMS engineering (or
perhaps "formerly part of" due to downsizing), I have to ask if there is
any justification for the above from a DCL/VMS engineering point of view.

Also found
$ set :=

Is this a strict equivalent to DELETE/SYMBOL/LOCAL SET ?


Another qestion: the same command procedure that has the fancy run
command,
also has this:

$ serv_id = f$edit("tcpip$smtp","upcase")
$ serv_home = f$edit("sys$specific:[''serv_id']","upcase")


(these constructs are used in the TCPIP$*.COM files throughout
SYS$SYSTEM:)

Were these files generated using some DCL generation tool that perhaps
converts the Tru64 scripts ?

I keep wondering why the TCPIP engineers wrote those procedures in those
ways.

.

Relevant Pages

  • Re: Purpose of uppercasing a RUN command ?
    ... files in a case insensitive manner. ... any justification for the above from a DCL/VMS engineering point of view. ... the same command procedure that has the fancy run ...
    (comp.os.vms)
  • Purpose of uppercasing a RUN command ?
    ... Since this is written supposedly by people part of VMS engineering, I have to ask if there is any justification for the above from a DCL/VMS engineering point of view. ... Is this a strict equivalent to DELETE/SYMBOL/LOCAL SET? ... Another qestion: the same command procedure that has the fancy run command, ...
    (comp.os.vms)