HP Storage Library System for OpenVMS

HP Storage Library System SPD 29.67.27
Version 2.9J for OpenVMS
SOFTWARE REQUIREMENTS
Operating System:
SLS is qualified on:
• OpenVMS VAX version, V7.3
• OpenVMS Alpha versions, V7.3-2, V8.2, and V8.3
Note: SLS V2.9J does not utilize ODS5 disk structure.
Layered Products:
• DECnet Phase IV for OpenVMS, or
• DECnet-Plus
Oracle Rdb:
• Oracle Rdb 7.0.3, 7.0.5, 7.0.6, 7.0.6.1, 7.0.9 and 7.1-
02
Optional Software:
Digital Cartridge Server Component (DCSC) is required
for support StorageTek ACSLS silos. Refer to the DCSC
Software Product Description (SPD 33.59.xx). Open-
VMS Disk space required for SLS Server Node:
Server
Without
RDF With RDF
Peak (during
installation):
9,000 blocks
(4.5 MB)
(client and server) 10,200
blocks (5.1 MB)
Net (perma-
nent):
7,800 blocks
(3.9 MB)
8,400 blocks (4.2 MB)
OpenVMS Disk space required for SLS Client Node:
Client
Without
RDF With RDF
Peak (during
installation):
8,700 blocks
(4.4 MB)
(client and server) 9,800
blocks (4 MB)
Net (perma-
nent):
7,100 blocks
(3.6 MB)
7,900 blocks (4.0 MB)
Disk space required by the SLS for OpenVMS media
database and history files:
The SLS media database is present only on nodes exe-
cuting SLS for OpenVMS server software (not on nodes
executing SLS for OpenVMS client software). The disk
space required by the SLS media database depends on
the number of pieces of media to be managed. During
installation, you may designate the disk on which the
SLS media database will be kept. For enhanced data
safety, the SLS media database may be stored on a
shadowed disk.
SLS history files are present on any node executing
either SLS for OpenVMS server software or SLS for
OpenVMS client software. The disk space required for
a SLS history file depends upon the number of files to be
tracked by SLS for OpenVMS software. During installa-
tion, you may designate the disk on which SLS history
files are will be kept. For enhanced data safety, the SLS
history files may be stored on a shadowed disk.
Total Disk Space Requirement for SLS for OpenVMS
Server Software:
Execution of SLS for OpenVMS Server software re-
quires approximately 8,400 blocks (the number of blocks
occupied by SLS for OpenVMS and RDF software) plus
one block for every piece of media it manages plus one
block for every six files it tracks.
Example: Assume that there are 1,500 pieces of media
under management by SLS for OpenVMS software and
that 60,000 files are tracked. The space required is:
Component Required Disk Space
SLS for OpenVMS
Server Software:
8,400 blocks
Media database: 1,500 blocks
History files: 10,000 blocks
TOTAL 19,900 blocks (10.0 MB)
Total Disk Space Requirement for SLS Client software:
Execution of SLS for OpenVMS Client software requires
7,900 blocks (the number of blocks occupied by SLS for
OpenVMS Client and RDF software) plus one block for
every six files it tracks.
Example: Assume that there are 60,000 files known
to SLS for OpenVMS Client software. The disk space
required is:
Component Required Disk Space
SLS for OpenVMS
Client software:
7,900 blocks
History files: 10,000 blocks
TOTAL 17,900 blocks (8.0 MB)
In addition to the disk space specified above, adequate
disk storage must be available on the host system to
accommodate history files if that option is selected.
4