Using ODS-5 disks

[Malleka Ramachandran]

I have a question regarding the ODS 5. I tried to download the JDK on OpenVMS 8.2 and I read that the installation requires the disk to be ODS 5 formatted. Since we only have one system disk, I was planning on backing up the existing ODS 2 disk on a tape, initializing the disk to ODS 5 and restoring from the tape.
From other posts in this forum, I understand that it is wise to stay with ODS 2 unless there is a compelling reason. Since JDK is my only reason for moving to ODS 5, I would like to get feedback from other members on this.
I was even thinking of ignoring that part about ODS 5 and going ahead and installing JDK on the ODS 2 to see if it works. Has anyone tried this before?

Thanks,
Malleka

[Ian Miller.]

Malleka,
java needs ODS5 and won't work without it.

(BTW Its best to start your own thread for new questions)

[Karl Rohwedder]

Shael,

a backup is allways o.k., but you can boot an OS CD and issue a 'set volume /Structure' command to convert to ODS-5.

You could also use the LD (Logical Disk) facility to create an ODS-5 disk in a container file on your ODS-2 disk (Since 8.2 LD is part of VMS, else see freeware CD's). So you are able to experiment with ODS-5 without changing your systemdisk.

regards Kalle

[Steven Schweda]

I also recommend adding an experimental ODS5
disk (real or LD), and testing _everything_
before converting. MMS, for example, still
does not deal well with lower-case file
names. The TCPIP V5.4 FTP server provides
but does not accept ^-escaped characters in
file names. I assume that there are other
problems still lying in wait for the
careless.

Conversion _to_ ODS5 is much easier than
conversion back _from_ ODS5.


> Also I seem to remember that older versions
> of Zip had problems creating archives using
> [...] syntax for the input files on ODS-5
> disks.

The latest released Info-ZIP programs (Zip
2.31, UnZip 5.52) are not as good with ODS5
as the unreleased beta Zip 3.0e and UnZip
6.00c, but specific complaints are always
welcome. (Versions even older could easily
be even worse.)

[Cass Witkowski]

Has CSWING ever been updated to work with ODS-5?

[Karl Rohwedder]

As far as I know, CSWING has NOT been updated.

regards Kalle

[Rinkens]

Hi

One off the things what happened to us when did go from ODS2 to ODS5 was the following.

When you ftp from unix to vms (or form vms to unix) using ODS2 then the file name you see on your vms is for example:


$ ftp open unix node
get TestFile.txt
exit
$ dir testfile.txt

TESTFILE.TXT (file upper case characters)

On a vms system with ODS5 you get the following

$ ftp open unix node
get TestFile.txt
exit

$dir testfile.txt

TestFile.txt (file with upper and lower characters)

So if you have some scripts with for example f$search in it where you are looking for
TESTFILE.TXT, then you will not find anything.

You have to check your application and command files, before you decide to go to ODS5.

Regards Kor

[Steven Schweda]

> $dir testfile.txt
>
> TestFile.txt (file with upper and lower characters)

> So if you have some scripts with for
> example f$search in it where you are
> looking for TESTFILE.TXT, then you will
> not find anything.

Well, no, not always:

ALP $ dire /date /prot /size ALP$DKA100:[TEST]

Directory ALP$DKA100:[TEST]

TestFile.txt;1 0 5-JAN-2006 01:05:00.82 (RWED,RWED,RE,)

Total of 1 file, 0 blocks.

ALP $ set process /case_lookup = sensitive
ALP $ write sys$output f$search( "D5:[TEST]TESTFILE.TXT")

ALP $

But:

ALP $ set proc /case_lookup = blind
ALP $ write sys$output f$search( "D5:[TEST]TESTFILE.TXT")
ALP$DKA100:[TEST]TestFile.txt;1

As the HELP (SET PROCESS /CASE_LOOKUP) says:

HP strongly recommends that you use caution
when enabling case sensitivity in your
processes.