Hitachi MK-90RD011-25 Computer Drive User Manual


 
Hitachi Command Control Interface (CCI) User and Reference Guide 141
(5) Command device.
CCI uses the SCSI class driver for the purpose of accessing the command device on the
9900V/9900, since OpenVMS does not provide the raw I/O device such as UNIX, and is
defining “DG*,DK*,GK*” as the logical name for the device. The SCSI class driver requires the
following privileges: DIAGNOSE and PHY_IO or LOG_IO (for details see the OpenVMS manual).
In CCI version 01-12-03/03 or earlier, you need to define the Physical device as either
DG* or DK* or GK* by using DEFINE/SYSTEM command. For example:
$ show device
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
VMS4$DKB0: Online 0
VMS4$DKB100: Mounted 0 ALPHASYS 30782220 414 1
VMS4$DKB200: Online 0
VMS4$DKB300: Online 0
VMS4$DQA0: Online 0
$1$DGA145: (VMS4) Online 0
$1$DGA146: (VMS4) Online 0
:
:
$1$DGA153: (VMS4) Online 0
$ DEFINE/SYSTEM DKA145 $1$DGA145:
$ DEFINE/SYSTEM DKA146 $1$DGA146:
:
:
$ DEFINE/SYSTEM DKA153 $1$DGA153:
(6) -zx option for Raid Manager commands. ‘-zx option’ for Raid manager commands are
using the select() function to wait a event from STDIN, but OpenVMS select() function does
not support to wait any events from STDIN, and the behavior of select() for terminal(STDIN)
is unable to echo back the terminal input.
Therefore ‘-zx option’ for Raid Manager commands will not be supported, and it will be
deleted a display for ‘-zx option’ on Help & Usage.
(7) Syslog function. The OpenVMS does not support the syslog function like UNIX. Therefore,
CCI does not support the syslog function. You can do an alternative by using HORCM logging
file for HORCM daemon.
(8) Start up log files. In start up of HORCM, CCI does share a start up log file by two process
for start-up, but CRTL does not work correctly to share from two processes.
As workaround, CCI has two start-up log files separated by using PID as follows.
For example, under the SYS$POSIX_ROOT:[HORCM.LOG*.CURLOG] directory:
HORCMLOG_VMS4 HORCM_VMS4_10530.LOG HORCM_VMS4_10531.LOG