> http://www.compaq.com/java/faq/ovms.html
Yow, this stuff is lame.
Ignoring the faulty HTML title, and the fact that most of this
"Alpha" stuff applies only to IA64 these days, ...
> [...]
> with ODS-5, do the following:
>
> 1. Make sure you have the latest version of the ZIP utility for
> OpenVMS which can be found at http://h71000.www7.hp.com/.
> [...]
Not the first place I'd look. ("ZIP" or UnZip?)
> [...]
> with ODS-2, do the following:
> [...]
> 3. Extract the contents of the downloaded zip file and then repackage
> it using the jar utility. For example:
>
> UNIX> unzip bdkjul98.zip -d /bdk
>
> UNIX> jar cvf bdk.jar bdk/*
> [...]
I can believe that "jar" on VMS does something special when extracting
onto an ODS2 destination, but can anyone explain what benefit is gained
from using unzip+jar to repackage this kit on a UNIX (or Windows) system
(before hauling the result to the VMS system)?
> [...]
> 4. Move the jar file to your OpenVMS system and extract it in the
> area where you want your JavaBeans development kit to be located.
>
> NOTE: It is CRITICAL that you use the SDK's jar command and not
> some variant of unzip. There will be filenames and directory names in
> the jar file that are not directly representable on an OpenVMS Alpha
> system. When these are encountered, they must be remapped into a name
> that is acceptable. Each un-archiving tool applies its own rules about
> how to do this mapping. Only jar will apply the specific mapping rules
> that will subsequently be used by the rest of the Java system.
>
> $ jar xf bdk.jar
If someone published these "specific mapping rules", then someone
else might be able to implement them in UnZip, potentially saving some
considerable fooling around. (Too radical a concept, I know.)
