Lowercase file/dir names on CD

[Piet Timmers_1]

Hello,

I have a CD mounted, and see the directory:
$1$DQA0:[OpenVMS]

How can I read the files in this directory, and do a set default to it.

We use OpenVMS 7.3
I have tried the command SET PROC/PARSE=EXTEND but I still can not access this directory.

Greetings and many thanks,

Piet Timmers

[Karl Rohwedder]

Piet,

a SET DEFAULT DQA0:[OPENVMS] should work. The default is case-blind, which you may check with SHOW PROCESS/CASE.

Are there any error messages? Is this a VMS structured CD or a ISOxxx CD?

regards Kalle

[Piet Timmers_1]

Karl,

show process/case gives an error. Is this a new command and not available with 7.3

It is a ISO9660 CD.

The error message is that there is no directory on the Cd [OPENVMS], which is correct.

Greetings.

[Volker Halle]

Piet,

can you do DIR $1$DQA0:[*...] and does it show that directory ?

Volker.

[Karl Rohwedder]

Piet,

I created a Cd with 2 directories (one uppercase, one lowercase).If I mount it on VMS with:
$ mount/media=cdrom cd_ /over=id
%MOUNT-I-WRITELOCK, volume is write locked
%MOUNT-I-CDROM_ISO, DISK: (1 of 1) , mounted on _$1$DKC400: (SAP01)
$ dir cd_:<000000>

Directory SAP01$DKC400:<000000>

GROSSERO.DIR;1
KLEINERO.DIR;1

the filesnames a uppercased and truncated.

A SET DEF works:
$ set def cd_:
$ dir

Directory SAP01$DKC400:

RUNDIG.TXT;1
TLVIZ_1_.DOC;1

How did you mount the CD?

regards Kalle

[Piet Timmers_1]

Mayby this can help:

$ mount/over=id /medi=cdrom $2$dqa0:
%MOUNT-I-WRITELOCK, volume is write locked
%MOUNT-I-CDROM_ISO, BEB_10_5_AGENT: (1 of 1) , mounted on _$2$DQA0: (TEST)
$ dir $2$dqa0:[000000]

Directory $2$DQA0:[000000]

AS400.DIR;1 autorun.inf;1 BrightStor.ico;1 Browser.DIR;1
Install.DIR;1 Intel64.DIR;1 IntelNT.DIR;1 NWAgent.DIR;1
OpenVMS.DIR;1 setup.exe;1 setup.ini;1 Unix.DIR;1

Total of 12 files.
$ dir $2$dqa0:[*...]

Directory $2$DQA0:[AS400]

ARCSERVE.;1 CAINSTASO.;1 install.html;1 install.txt;1

Total of 4 files.
$ sh dev $2$dqa0:/full

Disk $2$DQA0: (TEST), device type HL-DT-STDVD-ROM GDR8160B, is online,
allocated, deallocate on dismount, mounted, software write-locked, file-
oriented device, shareable, available to cluster, error logging is enabled.

Error count 0 Operations completed 80
Owner process "Default " Owner UIC [SYSTEM]
Owner process ID 000072ED Dev Prot S:RWPL,O:RWPL,G:R,W
Reference count 2 Default buffer size 512
Total blocks 401740 Sectors per track 8
Total cylinders 12555 Tracks per cylinder 4
Allocation class 2

Volume label "BEB_10_5_AGE" Relative volume number 1
Cluster size 0 Transaction count 1
Free blocks 0 Maximum files allowed 0
Extend quantity 0 Mount count 1
Mount status Process ACP process name "DQA0CACP"

Volume Status: ISO 9660.
Members of this volume set are $2$DQA0: (rvn 1).

$ dir $2$dqa0:[000000]

Directory $2$DQA0:[000000]

AS400.DIR;1 autorun.inf;1 BrightStor.ico;1 Browser.DIR;1
Install.DIR;1 Intel64.DIR;1 IntelNT.DIR;1 NWAgent.DIR;1
OpenVMS.DIR;1 setup.exe;1 setup.ini;1 Unix.DIR;1

Total of 12 files.
$ set def $2$dqa0:[OpenVMS]
$ dir
%DIRECT-E-OPENIN, error opening $2$DQA0:[OPENVMS]*.*;* as input
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file
$

[Dale A. Marcy]

Can you do a:

$ dir/full $2$dqa0:[000000]openvms.dir

[Arch_Muthiah]

Piet,

After setting the case using
$ SET PROCESS /CASE=BLIND /PARSE=TRADITIONAL

what does it show
$ SHOW PROCESS /CASE /PARSE

Also go thru this VMS - WEBES known issue related with case senstive under
"1.6.5 OpenVMS WEBES Issues"

http://h18023.www1.hp.com/support/svctools/webes/webes_rn.pdf


Archunan

[Steven Schweda]

> show process/case gives an error. Is this
> a new command and not available with 7.3

Apparently. It's not in the on-line docs
for V7.3, but it is for V7.3-2. I don't
know exactly when it appeared.

> After setting the case using
> $ SET PROCESS /CASE=BLIND /PARSE=TRADITIONAL
>
> what does it show
> $ SHOW PROCESS /CASE /PARSE

Typically useful advice, AM.

No bets, but you might look for a
DCL/DIRECTORY and/or MOUNT patch. This sort
of thing may be why V7.3-2 is more popular
than V7.3 on Alpha.

[John Gillings]

Piet,

Your best bet would be to install V7.3-2 - it's basically just a big patch. There shouldn't be any valid reason that you can't install it (bear in mind how long ago it was released!)

If that's not possible, you *may* be able to access files with judicious use of wildcards. For example, try:

$ DIR $2$DQA0:[O*VMS]

If that works, try COPYing the files to a local drive.

[Arch_Muthiah]

Piet,

The "extended file spec" support had been added before 7.3-2 release. I guess as of OpenVMS V7.2 on Alpha systems, RMS supports a larger character set on ODS-5 disk.

In addition, OpenVMS V7.2 on Alpha systems and ODS-5 disks includes support for the use of file spec that include all possible 8-bit characters, excluding values 00 through 1F (hex) and excluding the following chars: < > : / \ | ? * "

Now I don't have 7.3 or 7.3-1 to test it.

But if the directory OpenVMS been created from the Program control, then RMS could have stored it as OpenVMS only on the disk.

From the DCL command interface, file names that are entered at the command prompt with lowercase letters will be translated by default to uppercase before they are passed to RMS. Case may be preserved from the DCL command interface by using the DCL command SET PROCESS/PARSE_STYLE=EXTENDED and also using SYS$SET_PROCESS_PROPERTIESW system service. But file lookups was case blind before 7.3-1, as of OpenVMS Version 7.3-1, an option may be set for file look-ups at either the process or file level to request RMS to either ignore or notice the case sensitivity of file names on ODS--5 disks.

At the process level, the user may request RMS to ignore case by using SET PROCESS/CASE_LOOKUP=BLIND.

At the file level, the NAML$V_CASE_LOOKUP flag can be used to instruct RMS to ignore case for a file on an ODS--5 disk (NAM$L_INPUT_FLAGS field in the NAML structure)

NAML$C_CASE_BLIND is set to tell RMS to ignore case or NAML$C_CASE_LOOKUP_SENSITIVE to notice case when creating, deleting or searching for a file on an ODS--5 disk. If the NAML structure is not used or this flag is zero, the current process setting for
CASE_LOOKUP is used.

Dear Steven Schwede, my answers might have gone wrong many times. But till today I am always trying to concentrate on the questions only. Mistake is common when answering a question. Take it easy friend Steve.

Archunan

[Volker Halle]

Piet and others,

please note, that this CD is not an ODS-5 volume, but an ISO 9660 CD, so there may be different rules !

The DIR DQA0:[*...] output presented shows, that only directories with all uppercase characters have been listed, so there is not much hope for DIR DQA0:[O*VMS] to work - but still worth a try.

If you need the files, you should be able to put this CD into any other operating system capable of reading ISO 9660 CDs and copy the files to your OpenVMS V7.3 system using FTP.

Volker.

[Piet Timmers_1]

Thanks everybody,

I have used the workaround, mount CD on a windows PC and use FTP to copy the files to OpenVMS.

The Cd is provided by Computer Associates (that will tell enough).

Greetings,
Piet Timmers

[Volker Halle]

Piet,

I've found some more information about ISO 9660 and character sets in the 'LJK/CDROM Reference Manual' at:

http://www.ljk.com/ljk/LJK_CDROM_DOCUMENTATION/LJK_CDROM_0100.HTML

It looks like there should be one 'Primary Hierarchy' on a ISO 9660 CD, which consists of uppercase directory names only.

Volker.