HIERARCHY V4.0.6 Release Notes
Copyright © 1992, 1993, 1994, 1995, 1996, 1997, 1999, 2000, 2001, and 2002 Software Partners, Inc. All rights reserved.
Introduction |
These release notes describe the latest release of HIERARCHY. |
Supported Platforms |
With this new release, HIERARCHY has an expanded list of supported platforms. The complete list of supported systems now includes.
OpenVMS for VAX V6.1, V6.2, V7.1, and V7.2 OpenVMS for Alpha V6.1, V6.2, V7.1, V7.2, and V7.2-1. |
In this document |
This document covers the following topics: |
Topic |
See Page |
Upgrade Instructions |
2 |
New Features in V4.0.2 |
4 |
Modifications in V4.0.3 |
5 |
Modifications in V4.0.4 |
6 |
Modifications in V4.0.5 |
7 |
Modifications in V4.0.6 |
8 |
Procedure |
The table below details the upgrade procedure. |
Step |
Action |
1 |
Install the HIERARCHY software from the distribution media using VMSINSTAL.
When prompted for the product name, type in HIERARCHY, and press RETURN. |
2 |
Check the SYSGEN parameter setting by issuing the following:
$ MCR SYSGEN SYSGEN> USE ACTIVE SYSGEN> SHOW CTLPAGES
Has the SYSGEN parameter been added to SYS$SYSTEM:MODPARAMS.DAT as follows? ADD_CTLPAGES = (channelcnt+15)/14+46
where channelcnt is the current setting of the CHANNELCNT parameter.
If Yes, go on to Step 3, If No, - modify the SYSGEN parameters as detailed above, - re-autogen and reboot your system, and - verify the
modification by re-issuing the above MCR
Result: After rebooting, the new version of HIERARCHY will be running.
Caution: Modifying this .DAT file increases the SYSGEN parameter by the integer value of ADD_CTLPAGES. Failure to do this may cause I/O operations to fail with status values of SS$INSFMEM and/or RMS_$DME. |
Continued on next page
Upgrade Instructions, Continued
Procedure
(continued)
Step |
Action |
2 cont'd |
Notes: Consult your system administrator for the proper use of AUTOGEN parameters. To safely modify CTLPAGES, issue the following command:
@SYS$UPDATE:AUTOGEN GETDATA REBOOT CHECK_FEEDBACK
|
3 |
Are there other nodes in the cluster?
If Yes, repeat Step 2 for each node in the cluster. If No, go on to the next step.
|
4 |
For each disk monitored by HIERARCHY, issue the command
$ VSM TERMINATE disk
Note: For cluster mounted disks, issue the command VSM TERMINATE on each node.
Caution: Do NOT access these files on these disks during the upgrade.
|
5 |
Log into the SYSTEM username and start HIERARCHY by issuing
$ @disk:[VSM]VSMSTART
Execute this command on each node in the cluster.
|
New Features in V4.0.2
V4.0.0 - V4.0.1 |
HIERARCHY V4.0.0 - V4.0.1 were in-house releases for testing purposes. |
Modifications |
HIERARCHY V4.0.2 is compatible with OpenVMS V7.1 for Alpha. |
Modifications in V4.0.3
Bug fix |
An access violation occurred when using direct mode for the Optical Interface when running on OpenVMS V7.x Alpha systems.
This has been fixed, and the same change has been made for running on multi-processor Alpha systems. |
Modifications in V4.0.4
Compatibility with OpenVMS V7.2 |
HIERARCHY V4.0.4 is compatible with OpenVMS V7.2 VAX and Alpha platforms, and OpenVMS V7.2-1 on the Alpha platform.
Note: If using the TAPESYS-HIERARCHY interface on OpenVMS V7.2-1, TAPESYS V5.2.17 or higher must be used. |
CREATE/DIR change |
There was a CREATE/DIR behavior change for OpenVMS V7.x which was incompatible with HIERARCHY.
This has been fixed. |
Modifications in V4.0.5
Fix install on VMS 6.x versions |
Made io$v_setdir a weak reference, so that HIERARCHY will install on 6.x versions of VMS. |
Modifications in V4.0.6
Fix Bug in Optical Interface |
During inswap, if writing past EOF, an attempt is made to access the user’s I/O buffer before it has been mapped, causing an access violation. This has been fixed. |