Re: Purpose of uppercasing a RUN command ?
- From: Kilgallen@xxxxxxxxxxx (Larry Kilgallen)
- Date: 17 Nov 2006 08:43:29 -0600
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).
.
- Follow-Ups:
- Re: Purpose of uppercasing a RUN command ?
- From: Doug Phillips
- Re: Purpose of uppercasing a RUN command ?
- From: AEF
- Re: Purpose of uppercasing a RUN command ?
- References:
- Re: Purpose of uppercasing a RUN command ?
- From: norm . raphael
- Re: Purpose of uppercasing a RUN command ?
- From: david20
- Re: Purpose of uppercasing a RUN command ?
- Prev by Date: Re: What layered products are important for a VAX VMS system?
- Next by Date: Re: Mozilla + Java sanity check (speed tests)
- Previous by thread: Re: Purpose of uppercasing a RUN command ?
- Next by thread: Re: Purpose of uppercasing a RUN command ?
- Index(es):
Relevant Pages
|