Title File name Command name User
Synchronous waiting $ROOT:[HORCM.usr.bin]pairsyncwait.exe pairsyncwait sys
Configuration file making $ROOT:[HORCM.usr.bin]mkconf.exe - sys
Text filtering $ROOT:[HORCM.usr.bin]rmawk.exe - sys
Database Validator setting $ROOT:[HORCM.usr.bin]raidvchkset.exe raidvchkset sys
DB Validator confirmation $ROOT:[HORCM.usr.bin]raidvchkdsp.exe raidvchkdsp sys
DB Validator confirmation $ROOT:[HORCM.usr.bin]raidvchkscan.exe raidvchkscan sys
Storage Replication Adapter $ROOT:[HORCM.usr.bin]rmsra.exe rmsra sys
Sample file for horcmstart $ROOT:[HORCM]loginhorcm*.com - sys
Sample file for horcmstart $ROOT:[HORCM]runhorcm*.com - sys
Note:
• $ROOT is defined as SYS$POSIX_ROOT. $POSIX_ROOT is necessary when
using C RTL.
• The user name for OpenVMS is "System".
CCI log and trace files
The CCI software (HORCM) maintains internal startup log files, execution log
files, and trace files that can be used to identify the causes of errors and to
keep records of the status transition history of the paired volumes.
•
CCI log files on page 2-40
• CCI trace files on page 2-43
• CCI trace control command on page 2-43
• Command logging for audit on page 2-43
CCI log files
HORCM logs are classified into startup logs and execution logs.
• The startup logs contain data on errors that occur before HORCM
becomes ready to provide services. Thus, if HORCM fails to start up due
to improper environment setting, refer to the startup logs to resolve the
problem.
• The HORCM execution logs (error log, trace, and core files) contain data
on errors that are caused by software or hardware problems. These logs
contain internal error data that does not apply to any user settings,
therefore, you do not need to refer to the HORCM execution logs.
• When an error occurs in execution of a command, data on the error is
collected in the command log file. Refer to the command log file if a
command execution error occurs.
2-40
CCI software environment
Command Control Interface User and Reference Guide