HiCommand Dynamic Link Manager User's Guide (for Windows(R))

4.2.1 Notes on operating HDLM GUI windows

This section gives notes on operating HDLM GUI windows. Make sure that you read this section.

• HDLM GUI cannot start when all of the following conditions exist:
  
  • The OS of the host is Windows Server 2003 with SP1 or later applied.
  • Data Execution Prevention (DEP) functionality is enabled on the host.
  • HDLM GUI is started by using the JRE that is bundled with the HDLM product (JRE 1.3.1 provided by Sun Microsystems, Inc.) on the host.
  When all of the following conditions exist and HDLM GUI cannot be started, exclude the Java runtime environment that HDLM GUI is using from being subject to DEP (data execution prevention), by performing the following procedure:
  
  1. Choose Start, Settings, Control Panel, double-click System.
     The System Properties window is displayed.
     
  2. Select the Advanced tab. Click the Settings button under Performance.
     The Performance Option window is displayed.
     
  3. Select the Data Execution Prevention tab.
  4. Select the check box beside java to display a check mark. If java is not displayed, follow the procedure below:
     Add it by clicking the Add button and then specify the following file:
     
     HDLM-installation-folder\jre\bin\java.exe in the File Selection dialog box.
     
     Clicking Open button adds java.
     
  5. Click the [OK] button.
     The Java runtime environment that HDLM GUI is using is excluded from being subject to DEP (data execution prevention).
     
• If you do not install SP1 or later on Windows Server 2003 (IPF), the HDLM GUI might end abnormally when you start or operate the HDLM GUI. If this problem occurs, change the link destination of the shortcut for starting the HDLM GUI as shown below:
  
  • Before changing the link destination
    "HDLM-installation-folder\bin\dlmgui_launcher.exe"
    
  • After changing the link destination
    "HDLM-installation-folder\jre\bin\javaw.exe" -Xint -classpath "system-drive-name:\Program Files(x86)\HITACHI\HNTRLib2\classes\hntrlib2j.jar;HDLM-installation-folder\bin\DLMLocal.jar" dlmgui.DLMGUI
    Note that if you change the link destination of the shortcut, the following phenomena occurs:
    - The HDLM GUI will take 1.5 times longer to start.
    - The JRE that is bundled with the HDLM product (JRE 1.3.1 provided by Sun Microsystems, Inc.) will be used to start the HDLM GUI, even if you install a JRE whose version differs from the one bundled with HDLM.
    
  When the HDLM GUI ends abnormally, the message below is output to the Windows application event log. Note that the value for fault address might differ from 0x0004d87d.
  

   
  Reporting queued error: faulting application java.exe, version 0.0.0.0, faulting module jvm.dll, version 0.0.0.0, faulting address 0x0004d87d.

• If, in HDLM 5.8 or later, you use the HDLM GUI shortcut that was copied when an earlier version of HDLM was being used, the following phenomenon occurs:
  - The HDLM GUI will be started by using the JRE that is bundled with the HDLM product (JRE 1.3.1 provided by Sun Microsystems, Inc.), even if you install a JRE whose version differs from the one bundled with HDLM. In this case, check the following notes contained in HDLM Release Notes for the copy source version:
  
  • Notes when HDLM GUI cannot be started because the Data Execution Prevention (DEP) feature in Windows Server 2003 SP1 or later is enabled.
  • Notes when SP1 or later is not applied to Windows Server 2003 (IPF) and HDLM GUI ends abnormally when it is being started or while it is running.
• When the focus is on an object such as a button, the Enter key does not function as an operation, in the path management window or dialog box. Please use the Space key or click with the mouse to perform an operation in the window or dialog box.
• When the HDLM GUI is running for an extended period of time, response time might increase. In such a case, restart the HDLM GUI.
• When the focus is on the Status check box, the frame indicating the focus is not displayed, but you can perform operations.
• If you reconfigured an HDLM management-target device while the HDLM GUI was displayed, refresh the HDLM GUI.
• If the I/O load on the dynamic disk is heavy, it might take a long time to redisplay the HDLM GUI.
• When an operation to close a window is performed in the window frame of the path management window, the HDLM GUI will terminate even if the Option window remains open.
• If the HDLM GUI screen size is reduced, in some cases, buttons such as the Online and Offline buttons may become hidden. In such cases, please adjust the screen size appropriately, so that the buttons are visible.
• If you open multiple Path Management windows, the only logs output into the HDLM GUI log files (dlmguin.log, where n indicates a file number) will be those pertaining to the first-opened window. The logs pertaining to other Path Management windows are output to the integrated trace information file of the Hitachi Network Objectplaza Trace Library (installation-destination-drive:\Program Files^#\HITACHI\HNTRLib2\spool\Hntr2n.log, where n indicates a file number).
  

  #

  In the Windows Server 2003(IPF and x64), replace this part with Program Files (x86).

• If you are using Universal Storage Platform V, the Configuration view is not displayed. In the view frame, the KAPL02087-I message is displayed. The following buttons and check boxes for the Configuration view are not displayed:
  
  • Online button
  • Offline button
  • Type check box
  • Status check box

[Contents][Back][Next]

All Rights Reserved. Copyright (C) 2003, 2007, Hitachi, Ltd.