Table 10-3 describes the cause codes that are displayed in messages relating to file duplexing. Table 10-4 describes the cause codes that are displayed in the log input error messages. Table 10-5 describes other cause codes.

Table 10-3 List of cause codes in messages relating to file duplexing

Category	Error No.	Description	User's action
Duplexing definition analysis	-1001	There is an error in the syntax.	Check and, if necessary, revise the syntax of duplexing definition, and then initialize Datareplicator.
	-1002	Logical file name is duplicated.
	-1003	Specified logical file name is invalid.
	-1004	Physical file name is duplicated.
	-1005	Specified physical file name is invalid.
	-1007	Duplexing definition file contains no entry.
	-1008	Row length exceeded 1,024 bytes.
	-1009	Operand name is invalid.
Manipulation of duplexing control file	-1101	Data linkage file contains a syntax error.	To duplex the data linkage file, specify a matching name for both logical and physical files (either primary or secondary file).
	-1102	The duplexing control file is damaged.	Initialize Datareplicator.
	-1104	Attempt was made to access a duplexing control file that is not compatible with the current version.
	-1105	The file_dupenv operand was specified in the system definition during initialization, but the duplexing control file does not exist.
	-1106	The file_dupenv operand was omitted in the system definition during initialization, but there is a duplexing control file.	If you are not using the file duplexing facility, delete the duplexing control file, and then initialize Datareplicator.
	-1107	UNIX files cannot be mixed with character special files for physical files.	For the physical files specified in the duplexing definition, use the same file type for both primary and secondary files.
	-1108	The logical file to be added has already been registered in the duplexing control file.	Check and, if necessary, revise the logical file name in the additional queue duplexing definition file that was specified in the hdemodq command so that the logical file name is different from any existing duplex file.
	-1109	The physical file to be added has already been registered in the duplexing control file.	Check and, if necessary, revise the physical file name in the additional queue duplexing definition file that was specified in the hdemodq command so that the physical file name is different from any existing duplex file.
	-1110	Access to the duplexing control file failed.	See the error message that has been output to the syslog file (to the event log in Windows).
Current file copy command	-1301	The sector sizes do not match between source and target in the RAW device environment.	Use the same sector size as with the source.
	-1302	The source file does not belong to HiRDB Datareplicator or is damaged.	Check the source file.
	-1303	The source file has an invalid file size or is damaged.
	-1304	Target disk space is insufficient.	Check the target disk space.
	-1305	The target disk does not support large files.	Check and, if necessary, revise the maximum file size supported by the target system.
File duplexing facility	-1401	File is damaged.	Execute the current file copy command.
	-1402	Block is damaged.	This error might occur in the situations listed below. If this is the case, you can achieve initial start successfully by specifying the forced initialization option (hdsstart -i -f). An initial start was executed on the target Datareplicator immediately after the target Datareplicator's version was upgraded. Initialization was performed for the first time after the import information queue file and the import status file were created in character special files. A status file specified in the statsfile operand in the import environment definition was to be renamed, but a file with the new status file name already exists. If this error occurs during normal operation, execute the current file copy command.
	-1403	File is empty.	Initialization of Datareplicator failed. Eliminate the cause of the error and re-initialize the Datareplicator.
	-1404	During the previous session, the current file copy command did not terminate normally.	Re-execute the current file copy command.
	-1405	Operation cannot continue even in the single-operation mode.	Restart Datareplicator.
	-1406	During the previous session, an error occurred in the primary file.	Execute the current file copy command.
	-1407	During the previous session, an error occurred in the secondary file.
	-1408	The primary file was placed in HOLD status because its last update time is earlier than that of the secondary file.
	-1409	The secondary file was placed in HOLD status because its last update time is earlier than that of the primary file.
	-1410	No current file is available	Execute Datareplicator's data linkage recovery facility.
	-1411	The logical file names do not match between the primary and secondary systems.	Specify the physical file name that constitutes the logical file.
Internal conflict	-2003	Argument is invalid.	Contact the customer support center.
	-2004	Issuance sequence is invalid.
	-2102	Not found in the FDS management table.
	-2201	Not enough buffer space.
	-2202	File descriptor is invalid.
Other	-2101	Mapped file is damaged.	OS or disk might be unstable. Check for OS or disk errors.
	-2103	Too many files were specified in the Datareplicator definition.	Check and, if necessary, revise the defined value.
Common to all files	-3001	Files are not compatible.	For the source Datareplicator, execute the hdestart -i command; for the target Datareplicator, execute the hdsstart -i -f command.

Table 10-4 List of cause codes that are displayed in the log input error messages

Category	Error No.	Description	User's action
Log input error	-1101	Parameter is invalid.	Contact the customer support center.
	-1105	Protocol is invalid.	Contact the customer support center.
	-1108	Definition is invalid.	Correct the error in the source HiRDB's definition, and then restart the source Datareplicator.
	-1109	Environment variable is invalid.	Correct the error in the environment variable settings, and then restart the source Datareplicator.
	-1113	Memory is insufficient.	Resolve the memory shortage in the environment, and then restart the source Datareplicator.
	-1117	Open error occurred in the log file.	Contact the customer support center.
	-1118	Log start location is invalid.	If the source Datareplicator was initialized while the source HiRDB's linkage was enabled, disable the source HiRDB's linkage, and then initialize Datareplicator. If you are running the facility for recovering the extraction information queue file, this facility cannot be used to restore data because the log file required for recovery has been overwritten. Use another facility, such as the data linkage recovery facility. In all other cases, contact the customer support center.
	-1121	Buffer size is invalid.	Respecify the logiosize operand in the extraction environment definition with a sufficient value, and then restart the source Datareplicator.
	-1143	I/O error occurred.	Contact the customer support center.
	-1144	Log block or data in the log block is invalid.

Table 10-5 List of other cause codes

Category	Error No.	Description	User's action
File access	-3001	Files are not compatible.	For the source Datareplicator, execute the hdestart -i command; for the target Datareplicator, execute the hdsstart -i -f command.