Functional Differences Between Version 6.6 Or Later And Versions Earlier Than 6.6; Functional Differences Between Version 6.2 Or Later And Versions Earlier Than 6.2; Functional Differences Between Version 6.0 Or Later And Versions Earlier Than 6.0 - Hitachi XP P9500 User Manual

Hitachi dynamic link manager software user guide for windows (6.6) (hit5201-96006, november 2011)
Hide thumbs Also See for XP P9500:
Table of Contents

Advertisement

Functional Differences Between Version 6.6 or Later and
Versions Earlier Than 6.6
The type of the messages listed below that are output to the event log
has been changed from Error to Warning in HDLM version 6.6. Also, the
level of the message IDs has been changed from E to W.
¢
Drive and Disk Number can be displayed in the Path List view of the
HDLM GUI in HDLM version 6.6.
The values for the storage_emc key and the storage_eva key in the
sample file (sample_installhdlm.ini) of the installation information
settings file used by the HDLM installation utility (installhdlm) have
been changed from n to blank.
If the value of a key is blank, n is assumed for Windows Server 2003, and
y is assumed for Windows Server 2008.
Functional Differences Between Version 6.2 or Later and
Versions Earlier Than 6.2
In HDLM versions earlier than 6.2, the KAPL02087-I message was displayed
and indicated that the Hitachi AMS2000 series, Hitachi SMS storage, and
Universal Storage Platform V/VM storage was not supported in the HDLM GUI
configuration view. However, in HDLM version 6.2, you can now display those
items in the HDLM GUI configuration view.
Functional Differences Between Version 6.0.1 or Later and
Versions Earlier Than 6.0.1
In a new installation of HDLM, the default load balancing algorithm has
been changed from the Round Robin algorithm to the Extended Least I/Os
algorithm.
Functional Differences Between Version 6.0 or Later and
Versions Earlier Than 6.0
The format of the displayed HDLM version has been changed when HDLM
commands or utilities are executed.
The Java execution environment (JRE) bundled with HDLM has been
changed to the Sun Microsystems 5.0_11 (32-bit) JRE. The Java
execution environment no longer needs to be removed as a target of the
Data Execution Prevention (DEP) functionality.
In a new installation of HDLM, the default value for the automatic failback
function has been changed from off to on.
KAPL12150, KAPL12151, and KAPL12152
Functional Differences Between Versions of HDLM
Hitachi Dynamic Link Manager User Guide (for Windows(R))
A-3

Advertisement

Table of Contents
loading

This manual is also suitable for:

Dynamic link manager

Table of Contents