Hitachi TAGMASTORE MK-90RD011-25 User Manual page 375

The masking feature is to enable the tracing without changing their scripts. And this
feature is available for all RM commands (except inqraid or EX_xxx error code).
For example, if you want to mask pairvolchk (returns 22) and raidqry, you can specify as
below.
pairvolchk=22
raidqry=0
The user will be able to track the performing of their scripts, and then they will decide
to mask by auditing the command logging file as needed.
Relationship between an environment variable and Horcc_HOST.conf
The performing of logging has being depended on $HORCC_LOGSZ environment variable
and/or the HORCC_HOST.conf file as shown below.
$HORCC_LOGSZ HORCC_HOST.conf
=value Don't care
=0
Unspecified HORCC_LOGSZ=value
HORCC_LOGSZ=0
Unspecified or Nonexistent
/HORCM/log* directory
[root@raidmanager log9]# ls -l
total 16
drwxr-xr-x 3 root root
-rw-r--r-- 1 root root
-rw-r--r-- 1 root root 2097452 Oct 27 17:29 horcc_raidmanager.oldlog
-rw-r--r-- 1 root root
drwxr-xr-x 3 root root
/HORCM/log*/horcc_HOST.log file
COMMAND NORMAL : EUserId for HORC : root (0) Tue Nov 1 12:21:53 2005
CMDLINE : pairvolchk -ss -g URA
12:21:54-2d27f-10090- [pairvolchk][exit(32)]
COMMAND NORMAL : EUserId for HORC : root (0) Thu Oct 27 17:36:32 2005
CMDLINE : raidqry -l
17:36:32-3d83c-17539- [raidqry][exit(0)]
COMMAND ERROR : EUserId for HORC : root (0) Thu Oct 27 17:31:28 2005
CMDLINE : pairdisplay -g UR
17:31:28-9a206-17514- ERROR:cm_sndrcv[rc < 0 from HORCM]
17:31:28-9b0a3-17514- [pairdisplay][exit(239)]
[EX_ENOGRP] No such group
[Cause ]:The group name which was designated or the device name doesn't exist in the
configuration file, or the network address for remote communication doesn't exist.
[Action]:Please confirm if the group name exists in the configuration file of the local and
remote host
4096 Oct 27 17:33 curlog
3936 Oct 27 17:36 horcc_raidmanager.log
46 Oct 27 17:19 horcc_raidmanager.conf
4096 Oct 27 17:19 tmplog
Hitachi Command Control Interface (CCI) User and Reference Guide
Performing
Tracing within this APP
NO tracing within this APP
Global Tracing within this RM instance
Global NO tracing within this RM instance
Use the default value (0)
The same as the current logging for only command error
357