HP DECram for OpenVMS
HP DECram for OpenVMS SPD 34.26.12
INITIALIZE command is then used to write the Open-
VMS cluster file system to the RAM disk.
With DECram Version 2.5, the user interface to a
DECram device is the same as other disk class devices.
Management Interface
A DECram device is managed by the same tools as any
other OpenVMS disk device. For example, the INITIAL-
IZE, MOUNT, and DIRECTORY commands will work the
same on both hard disk and DECram devices. How-
ever, the standard utilities are used differently to set up
a DECram device.
System Analysis
Before creating a DECram device, the OpenVMS sys-
tem manager must determine its size. Each disk block
allocated to a DECram device will mean one less disk
block of available memory. The system manager should
also assess the need for multiple DECram units. See
Restrictions listed below.
System Generation
When adding a DECram device, the OpenVMS system
manager must reassess the values for the SYSGEN pa-
rameters that control paging and swapping behavior.
Restrictions
DECram for OpenVMS currently has the following re-
strictions:
• Data in a DECram device is volatile unless shadowed
with a physical disk.
• DECram Version 3.2 or higher cannot be installed on
a VAX system.
• With DECram Version 3.2, the maximum size of a
single DECram device on OpenVMS Alpha systems
running OpenVMS V7.2-2 or higher is 2048 Giga-
bytes (GB).
• In DECram Version 2.5, a single DECram device size
on OpenVMS Alpha systems running OpenVMS Ver-
sion 7.2-2 or higher is limited to 32 GB.
• In DECram Version 2.5, a single DECram device size
on OpenVMS VAX systems running OpenVMS Ver-
sion 6.2 or higher is limited to 256 Megabytes (MB).
• DECram V3.2-3HP is the minimum version for Open-
VMS V7.3-1 or higher.
Note: For disk volumes larger than 256 MB on VAX or
2048 GB on Alpha, multiple DECram disk devices can
be created and bound into a volume set.
DECram for OpenVMS is not designed to support long-
term data storage. If a system or hardware failure oc-
curs, data stored in the DECram device is lost and must
be recreated. This restriction does not apply if the de-
vice is shadowed to a real physical device, using a sup-
ported version of OpenVMS Volume Shadowing.
HARDWARE REQUIREMENTS
There are no special hardware requirements to install
DECram for OpenVMS.
Processor and hardware configurations must conform
to specifications in the HP OpenVMS Operating Sys-
tem for Alpha Version 7.3-1 and 7.3-2, and VAX Version
7.3 Software Product Description (SPD 25.01.xx) or the
HP OpenVMS for Alpha and Integrity Servers Version
8.3 Software Product Description (SPD 82.35.xx), or the
appropriate operating system documentation set.
SOFTWARE REQUIREMENTS
DECram for OpenVMS Version 8.3 supports OpenVMS
Alpha and OpenVMS for Integrity servers Version 8.3.
DECram for OpenVMS Version 3.2 supports OpenVMS
Alpha Version 7.2-2 or higher.
DECram for OpenVMS Version 2.5 supports OpenVMS
Alpha Versions 7.2-2, and 7.3. A minimum of DECram
Version 2.3 or higher is required for any OpenVMS Clus-
ter systems running any version of OpenVMS Alpha or
VAX.
DECram for OpenVMS Version 2.5 supports OpenVMS
VAX Version 6.2 or higher.
ORDERING INFORMATION
OpenVMS for Integrity servers
Software License: BA407AC
For HP OpenVMS for Integrity server customers, a soft-
ware license for HP DECram may be purchased ei-
ther as a separate per-processor core license (PCL):
BA407AC or as part of the OpenVMS Enterprise Op-
erating Environment (EOE) license bundle. Please re-
fer to the HP Operating Environments for OpenVMS
for Integrity servers Software Product Description (SPD
82.34.xx) for ordering information.
Software Media:
Foundation Operating Environment Media, BA322AA
or
Enterprise Operating Environment Media, BA323AA
or
Mission Critical Operating Environment Media, BA324AA
3