hdsstart (start the target Datareplicator)

Function

The hdsstart command starts the target Datareplicator in accordance with its import system definition. For details about the import system definition, see 5.8 Import system definition.

Format

hdsstart [ -i [ init ][ -D data-linkage-identifier-number ][ -f ][ -q ][ -r ]]
          | -c synchronous-import-group-name

Options

-i

Specify this option to first initialize the target Datareplicator environment, and then start the target Datareplicator (initial start).

An error results if, when the -f option is omitted, there is still an import environment subject to initialization, and the import information queue file for that import environment contains update information that has not yet been imported.

When the -D option is specified, Datareplicator initializes only the import environment for the specified source, and then starts the target Datareplicator. When the -D option is omitted, Datareplicator initializes the following files specified in the import system definition or import environment definition, initializes the entire target Datareplicator environment, and then starts the target Datareplicator (when the -D option is specified, Datareplicator initializes only those files that correspond to the specified source's data linkage identifier):

Import information queue files
Import status files
Import master status file
Import error information files
Import trace files
Unimported information files

init: Specify this option to create all import information queue files and import status files specified in the import environment definitions based on the sizes specified in the queuesize and statssize operands, respectively.; When you execute the hdsstart command with init specified, the initialization processing takes more time than when only the -i option is specified. This amount of time depends on the file sizes and the number of files to be created.; If this option is specified when large files are used, the command might take a long time to execute. For details, see 6.11.2 Estimating the command execution time when large files are used.; When the -D option is specified, the Datareplicator creates only those files that correspond to the specified source's data linkage identifier.

-D data-linkage-identifier-number: Initializes the import environment for the specified source only (partial initialization). Datareplicator executes normal startup on the import environments corresponding to sources that are not specified. If an error occurs during initial start processing, Datareplicator cancels the processing, in which case the target Datareplicator does not start.; Specify the source identifier number, which is the numeric digits in xxx of the data linkage identifier specified in the import system definition (dsidxxx). The specified data linkage identifier number must have been defined when the most recent initial start was executed. You cannot specify a newly added data linkage identifier number. The partial initialization specified in this operand is applicable to import environment definitions specified with dsidxxx and refenvxxx operands in the import system definition and the import definitions specified with reffile in the import environment definitions.; Datareplicator handles any changes to a definition other than partial initialization in the same manner as a normal start.; Datareplicator handles any change to a definition other than partial initialization in the same manner as a normal start.; Do not change a definition other than the data linkage identifier that is subject to partial initialization. To perform partial initialization on multiple data linkage identifiers, first change the definition of a data linkage identifier, and then perform partial initialization; then, repeat this procedure for each additional data linkage identifier.

-f: Executes an initial start forcibly, regardless of whether the import information queue file contains unimported update information. If the import information queue file contains unimported update information, that information will be discarded during the initial start. Therefore, when you specify this option to perform an initial start, check first to determine whether there is any unimported update information that will be needed.; Specify this option if any of the following is true:; Datareplicator was terminated forcibly by the hdsstop -t force command.; Datareplicator is to be initialized for the first time after the import information queue file and the import status file were created using character special files (there is no need to specify this option for a subsequent initialization).; The status file specified in the statsfile operand in the import environment definition is to be renamed and a file with the new status file name already exists.

-q: Terminates the target Datareplicator after initial start or partial initial start without starting it.

-r: Resets the import processing count when the target Datareplicator starts.; This option is applicable when false is specified in the reflect_counter_reset operand in the import system definition.

-c synchronous-import-group-name: Cancels synchronous import of the specified synchronous import group and starts the target Datareplicator normally. You use this option when an import transaction cannot be committed due to failure of the hdeevent command to execute, or due to a shortage of target database resources.; Import processing can be executed later for each of the data linkage identifiers constituting the cancelled synchronous import group. Additionally, the operand that was disabled by specification of the synchronous import group is now enabled.; Once a synchronous import group is cancelled, it cannot be reorganized again until Datareplicator is initialized. If the specified synchronous import group name is undefined or has already been cancelled, the target Datareplicator results in an error during the normal start.

Rules

If the hdsstart command terminates normally, it returns 0. If it terminates abnormally, it returns 1.

The start mode depends on the previous termination mode. The following table shows the relationship between the start mode and the previous termination mode.

Table 7-12 Relationship between the start mode and the previous termination mode

Start mode	Previous termination mode	Action at startup
Initial start	N/A^#¹	Starts the target Datareplicator in accordance with the import system definition without inheriting the settings used at the previous session. At an initial start, the target Datareplicator initializes files, as shown in Table 7-13 Handling of files when the -i option is specified.
Partial initial start	N/A^#²	At partial initial start, the target Datareplicator initializes the import environment only for the specified source and starts operation.
Normal start	Normal termination, event termination, or immediate termination	The target Datareplicator starts in accordance with the import system definition without inheriting the settings used at the previous session.
Restart	Abnormal termination or forced termination	The target Datareplicator ignores some of the operand settings^#³ in the import environment definition and starts operation with the settings used at the previous session in order to guarantee conformity between the source and target databases.

#1: Executing the hdsstart command with the -i option specified starts the target Datareplicator in the initial start mode, regardless of the previous termination mode.
#2: Datareplicator executes initial start on the processing for the data linkage identifier that is specified in the -D option as being subject to initialization. On the processing for any other data linkage identifier, Datareplicator executes either normal start or restart according to the previous termination mode.
#3: In the restart mode, Datareplicator ignores the settings of the startmode, breaktime, breakmode, eventspd, eventtrn, eventtbl, cmtintvl, trncmtintvl, and tblcmtintvl operands in the import environment definition. For the cmtintvl, trncmtintvl, and tblcmtintvl operands, their settings take effect automatically when conformity is guaranteed between the source and target databases.

The following table shows the handling of each file when the -i option is specified.

Table 7-13 Handling of files when the -i option is specified

File type	No existing file	Type of existing file		Datareplicator file system area^#¹
File type	No existing file	OS regular file	Character special file^#¹	In initialized status	Being used
Import information queue file^#²	Created in the OS regular file format	Re-created	Does nothing.^#³	File is allocated.	File is reallocated.
Import status file^#²			Header is initialized.^#³	File is allocated.	File is reallocated.
Import master status file			Header is initialized.^#³	N/A	N/A
Unimported information file			N/A	N/A	N/A
Import error information file			N/A	N/A	N/A
Import trace file			N/A	N/A	N/A

#1: UNIX Datareplicator supports character special files and Datareplicator file system areas.
Windows Datareplicator executes the processing described in the OS regular file column.
#2: If you execute the hdsstart -i command with init specified, the file is created with the specified size.
#3: Use an OS command to re-create this file.

Notes

If an error occurs during partial initial start, you cannot execute normal startup or another partial initial start with a different data linkage identifier number specified while the error remains uncorrected. To correct a partial initial start error, eliminate the cause of the error, re-execute the partial initial start with the same data linkage identifier number specified, and then either terminate Datareplicator normally or execute initial start on the entire extraction environment.
You can specify partial initial start only for data linkage identifier numbers that were defined at the time of the preceding initial start. You cannot specify a new data linkage identifier number that has been added since then. If the number of targets is expected to increase, specify ** for future data linkage identifiers.
The following is a specification example of partial initial start:

Executes partial initial start for data linkage identifier number 001 (data linkage identifier 01).
Executes partial initial start for data linkage identifier number 002 (data linkage identifier A2) after modifying the definition.
Executes partial initial start for data linkage identifier number 003 (data linkage identifier **), which became an absent number after the definition was modified.
Executes partial initial start for data linkage identifier number 004 (data linkage identifier A4), which has been newly defined.
Results in a command error because data linkage identifier number 005 (data linkage identifier A5), which was added by modifying the definition, had not been defined at the time of the initial start.
Results in a command error because data linkage identifier number 004 (data linkage identifier A4) was modified, which is not the specified data linkage identifier number (data linkage identifier A2).
To execute partial initial start for more than one data linkage identifier, modify the definition and specify the -q option for one data linkage identifier at a time, and then execute partial initial start. After all partial initializations have been completed, execute normal start. The following is an example of the execution procedure:

The following is the execution procedure for partial initial start:

Check that the target Datareplicator is stopped.
Use a text editor to modify the definitions.
Specify the data linkage identifier number subject to initialization in the hdsstart -i -D command in order to execute partial initial start.

If you use a system switchover configuration, you must activate the resources that are used by HiRDB Datareplicator (shared disk unit) prior to initialization or startup.