Re: Purpose of uppercasing a RUN command ?

In article <1163779444.688194.15890@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>, "AEF" <spamsink2001@xxxxxxxxx> writes:

Larry Kilgallen wrote:
In article <ejkg9o$5aa$1@xxxxxxxxxxxxxxxxx>, david20@xxxxxxxxxxxxxxxx writes:
In article <OF7A40D9CD.6262BD35-ON85257229.004B367E-85257229.004B9753@xxxxxxxxx>, norm.raphael@xxxxxxxxx writes:
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.


SET PROCESS/PARSE=EXTENDED on it's own will preserve case but will access
files in a case insensitive manner.

SET PROCESS/CASE_LOOKUP=SENSITIVE

would be needed to do case sensitive file accesses.

But then they could have just written the commands in
uppercase

But writing the commands in uppercase would not have provided such a good
warning to others who write command procedures (such as those assembled
here).

It's a command procedure, not a tutorial.

You and I have different opinions about how many command procedures
that ship with VMS are created by referring to a manual vs. created
by referring to an example.
--
==============================================================================
DoD Instruction 8500.2 field test sites wanted -
http://www.LJK.com/LJK/8500_2_fieldtest.html
==============================================================================
.