Here are some links for obtaining the UNZIP program:
For OpenVMS, re-packaged by DJE Systems (saveset in .ZIP a archive, install using VMSINSTAL):
Self-extract stubs for OpenVMS:
From InfoZip (the authors / maintainers, current and old versions):
Here are some tips on Installing and Using the freeware UNZIP program on OpenVMS.
To unpack the .ZIP archive for UNZIP, first download the appropriate self-extract stub (VAX or Alpha), then download the UNZIP archive (remember to transfer them as binary!). Now, append the two files together, like so:
$ COPY SFX_xxx.EXE,unzip_archive.ZIP unzip_archive.EXE
...where "xxx" is "VAX" for VAX systems or "AXP" for Alpha systems, and "unzip_archive" is the name of the UNZIP archive that you downloaded. Then, to extract the contents of the archive, simply run the .EXE file you just made.
Example: UNZIP V5.32 for VAX:
$ COPY SFX_VAX.EXE,UNZU2053.ZIP UNZU2053.EXE
$ RUN UNZU2053
After this, you can use VMSINSTAL to install the software on your system from the saveset you just unpacked. Be sure to review the README.TXT file for important information. On-line HELP will be installed also to help you use the UNZIP program.
UNZIP works on OpenVMS in a way very similar to the way the PKUNZIP program works on DOS. The command line options are a bit different, however.
As of V5.2x of UNZIP, UNZIP for OpenVMS now supports a more DCL-like command line syntax. You can view the command line syntax options by invoking the program with no parameters, like so:
$ UNZIP :== ddcu:[dir]UNZIP
$ RUN UNZIP
In general, no qualifiers are needed on the command line, unless OpenVMS version numbers were included when the .ZIP archive was created. In that case, use the /VERSION qualifier.
To list the contents of a .ZIP archive, both the "UN*X" and OpenVMS syntaces are supported (ZIP V5.2x and later):
$ UNZIP -V archive_name
$ UNZIP/LIST/FULL archive_name
This display will help you determine whether the files in the archive include version numbers.
To help determine whether the .ZIP archive originated on or is intended for an OpenVMS system:
$ UNZIP -Z archive_name
$ UNZIP/ZIPINFO archive_name
This display will help you determine on which operating system the .ZIP archive originated, or for which operating system it is intended. "VMS" in the second column means VAX/VMS or OpenVMS. "fat" in the second column means DOS or Windows (but does not guarantee that the files were archived in the correct format). "unix" in the second column - well, it explains itself (but again does not guarantee that the files were archived in the correct format).
If the second column shows "fat", you may want to use one of the following qualifiers:
$ UNZIP -A archive_name
$ UNZIP/AUTO archive_name
This will correct the problem of text files having a <CR> (carriage return) as the last byte of each record when the .ZIP archive source is a "fat" volume.
Files are always restored with their original date/time stamps. Files restored are owned by the user unpacking the archive or by the owner of the directory (depending on the OpenVMS privileges of your process).
Like OpenVMS BACKUP or COPY, UNZIP will attempt to match the file allocations to the cluster size of the target disk. As a result, some files may be allocated one more cluster than they actually need. This is a "feature" in OpenVMS (RMS), and is not the fault of either BACKUP, COPY or UNZIP. This usually happens when the source disk cluster size is smaller than that of the target disk.
DJE Systems Links:
Tradenames, trademarks, service marks, etc. appearing on this page are the property of their registered owners.
"DJE Systems" is a service mark of David J.
Dachtera, doing business as DJE Systems.
This page Copyright ©1997 by David J. Dachtera, All Rights Reserved.