1
First information about the binary distribution of VMS UnZip 5.4
2
----------------------------------------------------------------
3
This archive comes in different variations:
5
"unz540x-vms-<cpu-compiler>-{obj|exe}.exe",
7
"unz540x-vms-<cpu-compiler>-obj.bck",
9
where <cpu-compiler> is "axp", "vax-decc", or "vax-vaxc", depending on
10
the environment used for creating the binaries.
12
...-obj.exe denotes object library distributions that require
13
a link step on the local machine.
15
...-exe.exe denotes "ready-to-run" executable distributions, that do
16
not require additional work. The caveat of these executable distribution
17
is that they do not run on VMS versions that are older than the system
18
used for building the executables (typical error message: "shareable
21
...-obj.bck are uncompressed VMS backup saveset distributions of the
22
object libraries. They are much larger than the self-extracting Zip
23
archives and are only supplied for people with (old) versions of VMS
24
where the supplied SFX archives do not work. Therefore, if you already
25
have an old version of UnZip for VMS (5.0p1, better: 5.2), the better
26
choice is to fetch the Zip SFX archive and extract it manually, using
27
the older VMS UnZip program.
28
Note that backup savesets are 32256-bytes-fixed-length-record files;
29
when tranfered via binary FTP, the resulting file's record format is
30
usually 512-bytes-fixed-length. Before extracting them with BACKUP, the
31
record size of the saveset has to be restored to 32256 bytes (best done
32
with the public domain "FILE" utility, available from DECUS; or found on
33
ftp.wku.edu.). The contents of these saveset are identically to the
34
corresponding ...-obj.exe archives.
36
Contents of the "vms" executables self extracting archives
39
a) common files (documentation etc.):
40
00binary.vms this file
41
readme.vms general VMS info about using UnZip and zipfiles
42
readme what UnZip is; general information
43
license Info-ZIP copyright and distribution policy
44
where pointer to Zip/UnZip support archives
45
makesfx.com command file to create self-extracting archives
46
unzip.txt UnZip manual page, human-readable format
47
unzipsfx.txt UnZipSFX manual page, human-readable format
48
zipinfo.txt ZipInfo manual page, human-readable format
49
3rdparty.bug known bugs in PK[UN]ZIP, WinZip, etc.
50
unzip.hlp UnZip help module, for default command interface
51
unzip_cli.hlp UnZip help module, for VMSCLI command interface
52
unzipsfx.hlp UnZipSFX pre-formatted help page
54
b) object library distributions:
55
link_unz.com command procedure for the linking step
56
vms/unzip.opt auxiliary files required for linking step
59
unzip.<cpu_compiler>_olb object libraries for UnZip and UnZipSFX
60
unzipsfx.<cpu_compiler>_olb (both command interfaces)
62
unzipcli.<cpu_compiler>_olb additional object libraries for UnZip and
63
unzsfxcli.<cpu_compiler>_olb UnZipSFX, VMSCLI (DCL like) interface
65
c) executable distributions:
66
unzip.exe UnZip executable, default command interface
67
unzipsfx.exe UnZipSFX executable, default command interace
68
unzip_cli.exe UnZip executable, VMSCLI command interface
70
(To save space, unzipsfx_cli.exe has been omitted from the executable
71
distributions. The command interface of the SFX stubs is of minor
72
importance, anyway, since it cannot be used without first defining a
73
"foreign command" to run the SFX archive. In most cases, it is much
74
easier to use "$run <zipsfxarchive>.exe" at the command prompt.)
76
The binary files "*.<...>_olb" and "*.exe" have been stored in the Zip
77
archives with VMS attributes saved! If you extract them using a non-VMS
78
port of UnZip, you may get unusable files.
81
If you decided to fetch the object library distribution, you have to
82
link the executables on your local site. This requires runtime support
83
for the C runtime library to be installed, which may not be present
84
on older VAX VMS systems (prior to VMS 6).
85
To create the executables, just invoke the "link_unz.com" command procedure.
86
This will generate all executables (both unzip with UNIX-style command syntax
87
and with VMSCLI command interface), but note that the executable's
88
extension is ".<cpu_compiler>_exe"!
89
In case your system is a VAX and your current working directory carries
90
both the DEC C and the VAX C object distributions, you have to specify
91
either "VAXC" or "DECC" to tell link_unz.com which binaries you want
94
Additionally, link_unz.com defines foreign commands for the newly linked
95
executables, so you can test them without any further work.
96
In order to use the default (UNIX-like) command interface, you can
97
proceed straight ahead after unpacking the distribution.
98
If you rather prefer to use the VMSCLI interface, you have to specify
99
the option "VMSCLI" (or just "CLI") to the command starting link_unz.com.
101
The executables (object libraries) in this archive have been compiled
102
with the following options enabled:
103
* [decription support]
105
The environment used for compilation was:
107
a) On Alpha AXP : OpenVMS(AXP) 6.2; DEC C V 5.6-003
108
b1) On VAX : OpenVMS(VAX) 6.1; DEC C V 4.0
109
b2) alternatively VAX C V 3.2
112
The binary files of the distribution have been archived with "saving all VMS
113
attributes" enabled. Please do not repack the binary part of the archives on
114
a non-VMS system, to prevent corruption of the files.
116
04 December 1997, Christian Spieler
added
removed
vms/00binary.vms
