Hitachi Command Control Interface (Cci) User And Reference Guide; Log And Trace Files; User-Created Files - Hitachi TAGMASTORE MK-90RD011-25 User Manual

2.8.11 Log and Trace Files

The CCI software (HORCM) and Hitachi TrueCopy and ShadowImage commands maintain
start-up log files, execution log files, and trace files which can be used to identify the
causes of errors and keep records of the status transition history of the paired volumes.
Please refer to Appendix A for a complete description of the CCI log and trace files.

2.8.12 User-Created Files

Script Files. CCI supports scripting to provide automated and unattended copy operations. A
CCI script contains a list of CCI commands which describes a series of TrueCopy and/or
ShadowImage operations. The scripted commands for UNIX-based platforms are defined in a
shell script file. The scripted commands for Windows-based platforms are defined in a text
file. The host reads the script file and sends the commands to the command device to
execute the TrueCopy/ShadowImage operations automatically. The CCI scripts are:
HORCM startup script (horcmstart.sh, horcmstart.exe): A script which starts HORCM
(/etc/horcmgr), sets environmental variables as needed (e.g., HORCM_CONF,
HORCM_LOG, HORCM_LOGS), and starts HORCM.
HORCM shutdown script (horcmshutdown.sh, horcmshutdown.exe): A script for stopping
the HORCM (/etc/horcmgr).
HA control script: A script for executing takeover processing automatically when the
cluster manager (CM) detects a server error.
When constructing the HORCM environment, the system administrator should make a copy of
the HORCM_CONF file. The copied file should be set according to the system environment
and registered as the following file (* is the instance number):
UNIX-based systems: /etc/horcm.conf or /etc/horcm*.conf
Windows-based systems: \WINNT\horcm.conf or \WINNT\horcm*.conf

Hitachi Command Control Interface (CCI) User and Reference Guide

75