HP XP RAID Manager Software - Manual (Page 23)

$ PRODUCT INSTALL RM /source=Device:[directory]/LOG -
_$ /destination=SYS$POSIX_ROOT:[000000]
Device:[directory] where HITACHI-ARMVMS-RM-V0122-2-1.PCSI exists
:
:
$ PRODUCT SHOW PRODUCT RM
----------------------------------------- ----------- ------------
PRODUCT KIT TYPE STATE
----------------------------------------- ----------- ------------
HITACHI ARMVMS RM V1.22-2 Full LP Installed
----------------------------------------- ----------- ------------
$ raidqry -h
Model : RAID-Manager/OpenVMS
Ver&Rev: 01-22-03/06
:
:
For Installation history:
$ PRODUCT SHOW HISTORY RM /FULL
For removing :
$ PRODUCT REMOVE RM /LOG
(13) About exit code of the command on DCL
RAID Manager return codes are the same for all platforms. However, if the process was invoked
by the DCL, the status is interpreted by DCL and a message appears as below.
---------------------------on DCL of OpenVMS-------------------------
$ pairdisplay jjj
PAIRDISPLAY: requires '-jjj' or '/jjj' as argument
PAIRDISPLAY: [EX_REQARG] Required Arg list
Refer to the command log(SYS$POSIX_ROOT:[HORCM.LOG]HORCC_RMOVMS.LOG (/HORCM/log/horcc_rmovms.log)) for details.
$ sh sym $status
$STATUS == "%X0035A7F1"
$
$ pairdisplay -g aaa
PAIRDISPLAY: [EX_ATTHOR] Can't be attached to HORC manager
Refer to the command log(SYS$POSIX_ROOT:[HORCM.LOG]HORCC_RMOVMS.LOG (/HORCM/log/horcc_rmovms.log)) for details.
$ sh sym $status
$STATUS == "%X0035A7D9"
--------------------------on DCL of OpenVMS--------------------------
You can calculate the RAID Manager “Exit code” from $status of DCL using the formula below.
Exit code of RM command = ( $status % 2048 ) / 8
Known issues
Rebooting on PAIR state (Writing disable)
OpenVMS does not show the volumes of writing disable (for example, S-VOL_PAIR) at startup of
system, therefore the S-VOLs are hidden when rebooting in PAIR state or XP12000 Disk
Array.ND(read only) mode. You are able to verify that the “show device” and “inqraid” command
does not show the S-VOLs after reboot as below (notice that DGA148 and DGA150 devices are
S-VOL_PAIR).
$ sh dev dg
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
$1$DGA145: (VMS4) Online 0
$1$DGA146: (VMS4) Online 0
$1$DGA147: (VMS4) Online 0
$1$DGA149: (VMS4) Online 0
$1$DGA151: (VMS4) Online 0
$1$DGA152: (VMS4) Online 0
$1$DGA153: (VMS4) Online 0
$ inqraid DKA145-153 -cli
DEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_ID
DKA145 CL1-H 30009 145 - - - - OPEN-9-CM
DKA146 CL1-H 30009 146 - s/P/ss 0004 5:01-11 OPEN-9
DKA147 CL1-H 30009 147 - s/S/ss 0004 5:01-11 OPEN-9 DKA148
- - - - - - - -
DKA149 CL1-H 30009 149 - P/s/ss 0004 5:01-11 OPEN-9 DKA150
- - - - - - - -
DKA151 CL1-H 30009 151 - P/s/ss 0004 5:01-11 OPEN-9
DKA152 CL1-H 30009 152 - s/s/ss 0004 5:01-11 OPEN-9
DKA153 CL1-H 30009 153 - s/s/ss 0004 5:01-11 OPEN-9
$ inqraid DKA148
sys$assign : DKA148 -> errcode = 2312
DKA148 -> OPEN: no such device or address
Porting notice for OpenVMS 23