ODS 5 Case sensitive file names

[Tschroeder]

I have a strange issue that I can't seem to diagnose. In a single directory, I have files with identical file names and versions, with the exception that they are different case. Example:

Da_Trans.001;1
DA_TRANS.001;1

This is on a new OpenVMS 7.3-2 installation, and my other machine is the same version but I cannot recreate it there. Is there some setting that I missed on the 2nd machine?

[Volker Halle]

$ HELP SET PROCESS/PARSE_SYTLE

Volker.

[Tschroeder]

I logged into both machines and did

$ show process/all

Parse Style = extended on both machines.

[Robert Gezelter]

Tshroeder,

It may be somewhat simplistic, but I for one would be interested in seeing the output from SHOW DEVICE/FULL for BOTH volumes.

Perhaps one of the volumes is not ODS-5?

- Bob Gezelter, http://www.rlgsc.com

[Hein van den Heuvel]

An of course the disk must be ODS5.


$ write sys$output f$getdvi("sys$disk:","ODS5")

or $SHOW DEV /FULL sys$disk

Hein

[Tschroeder]

Yes, all drives in question are ODS 5

[Hoff]

This can be perfectly normal, and local application software can explicitly request this particular behavior.

First, confirm that you're at current patches for OpenVMS Alpha V7.3-2 on both disks, and then confirm that processes on the second box haven't been set for full case sensitivity.

The application-level commands:

$ SET PROCESS/CASE_LOOKUP=SENSITIVE
$ SET PROCESS/CASE_LOOKUP=BLIND

There are NAM and NAML-level flags for this within RMS, as well.

Some related reading:

http://labs.hoffmanlabs.com/node/650

[Hein van den Heuvel]

There is also CASE sensitivity:


$ init/size=1000 mda1: hein
$ moun mda1: hein
$ set vol/struc=5 mda1:
$ cre/dir mda1:[hein]
$ set proc/parse=exten
$ copy /log nl: mda1:[hein]Test.Txt
%COPY-S-COPIED, NL: copied to MDA1:[hein]Test.Txt;1 (0 records)
$ copy /log nl: mda1:[hein]TEST.TXT
%COPY-S-COPIED, NL: copied to MDA1:[hein]Test.Txt;2 (0 records)
$ set proc /case=sensitive
$ copy /log nl: mda1:[hein]TEST.TXT
%COPY-E-OPENOUT, error opening MDA1:[hein]TEST.TXT; as output
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file
$ copy /log nl: mda1:[HEIN]TEST.TXT
%COPY-S-COPIED, NL: copied to MDA1:[HEIN]TEST.TXT;1 (0 records)
$ dir MDA1:[HEIN]TEST.*

TEST.TXT;1

$ dir MDA1:[HEIN]T*.*

TEST.TXT;1
Test.Txt;2
Test.Txt;1


I really think that HELP SET PROC /PARSE and
HELP SET PROC /CASE chould refernce each other. They don't.

Hein.

[Tschroeder]

I looked at the case on both boxes, it is set to Blind.

Here are some sample commands and what I get:

$ dir DA_TRAN*.001

Directory MUSKIE$DATA1:[TEST]

DA_TRANS.001;2 Da_Trans.001;2


$ dir da_tran*.001

Directory MUSKIE$DATA1:[TEST]

DA_TRANS.001;2 Da_Trans.001;2

Total of 2 files.

[Hoff]

>I looked at the case on both boxes, it is set to Blind

You are aware that the setting is process specific? That the setting that matters here is the setting of the application or of the process that created those files?