For details about the measures to be taken when an error occurs in a status file, see the HiRDB Version 9 System Operation Guide.
- 42) pd_syssts_last_active_file = "logical-file-name"
- ~<identifier>((1-8 characters))
- Specifies the name of the logical file name of the status file to be used as the current file at the time of HiRDB (or a unit for a HiRDB parallel server configuration) startup.
- HiRDB compares the file specified in this operand with the file selected by HiRDB to be the current file. If they match, HiRDB is started; otherwise, HiRDB is not started.
- Conditions
- The following conditions must be satisfied:
- continue or excontinue is specified for the pd_syssts_initial_error operand.
- It cannot be determined if the current file selected by the HiRDB system was the most recent current file during the previous session.
- Specification guidelines
- To start HiRDB immediately after initializing all status files:
From among the operable logical files specified in the pd_syssts_file_name_1-7 operands, specify the one that has the smallest number. Forced startup will be used in this case, regardless of the previous termination mode.
- When both of the current status files are normal:
Specify the name of the current file#.
If HiRDB cannot be started even though the name of the current file is specified, the current file might have been initialized. In this case, first initialize all status files, and then use the method in step 1 above to start HiRDB (forced startup will be used, regardless of the previous termination mode).
- When one of the current status files has an error:
Use the method in step 2 above, with the following operands specified:
pd_syssts_singleoperation = continue or excontinue
pd_syssts_last_active_side
- When both of the current status files have errors:
Initialize all status files, then execute the method in step 1 above (forced startup will be used, regardless of the previous termination mode).
- When a virtual status file is specified:
Specify the name of the current file#.
- #: The names of the current files (that were active at the end of the previous operation) can be determined from the following messages:
- KFPS01001-I
- KFPS01010-E
- KFPS01011-I
- KFPS01063-I
- Of the status files displayed by these messages, the one that is reported in the message that was output most recently is the current file.
- Notes
- If Real Time SAN Replication based on the log-only synchronous method is used, the unit status files for transaction processing are used at the transaction execution site. At the log application site, this operand is ignored, if specified.
- 43) pd_syssts_last_active_side = A | B
- Specify this operand if you want to start HiRDB (or a unit for a HiRDB parallel server configuration) when one of the current files is in an error state. Specify the normal status file for this operand. HiRDB compares the file specified in this operand with the file selected by HiRDB. If they match, HiRDB copies the contents of the normal status file to secondary File A and File B. Afterwards, the secondary file is switched to the current file and HiRDB is started. If the files do not match, HiRDB is not started.
- Conditions
- The following operands must be specified:
- pd_syssts_initial_error = continue or excontinue
- pd_syssts_last_active_file
- Notes
- If Real Time SAN Replication based on the log-only synchronous method is used, the status files for transaction processing are used at the transaction execution site. At the log application site, this operand is ignored, if specified.
- 44) pd_syssts_last_active_subfile = "logical-file-name"
- ~ <identifier> ((1-8 characters))
- When Real Time SAN Replication based on the log-only synchronous method is used, this operand specifies the logical file name of the status file for log application processing that is to be used as the current file when HiRDB (or the unit in the case of a HiRDB parallel server configuration) starts. HiRDB compares the file specified in this operand with the current file selected by HiRDB. If the file names match, HiRDB starts; if not, HiRDB does not start.
- Conditions
- For details about the supported platforms, see the HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide.
- The following conditions must be satisfied:
- Y is specified in the pd_rise_use operand, and also syssync is specified in the pd_rise_pairvolume_combination operand.
- continue or excontinue is specified in the pd_syssts_initial_error operand.
- It cannot be determined if the current file selected by the HiRDB system was the most recent current file during the previous session.
- Specification guidelines
- When starting HiRDB immediately after initializing all status files for log application processing
Perform the preparations for log application. Once the preparations for log application have been completed successfully, start HiRDB without specifying this operand.
- When both of the current files are normal
Specify the name of the current file.# If HiRDB cannot be started even though the name of the current file is specified, the current file might have been initialized. In such a case, first initialize all status files for log application processing, and then use the method in step 1 above to start HiRDB. Note that in this case, forced startup will be used, regardless of the previous termination mode.
- When one of the current files has an error
Use the method in step 2 above and specify the following operands:
Specify continue in the pd_syssts_singleoperation operand
Specify the pd_syssts_last_active_side_sub operand
- When both of the current files have errors
Perform the preparations for log application. Once the preparations for log application have been completed successfully, start HiRDB without specifying this operand.
- When a virtual status file for log application processing is specified
Specify the name of the current file.#
- #: The names of the current files (that were active at the end of the previous session) can be determined from the following messages:
- KFPS01001-I
- KFPS01010-E
- KFPS01011-I
- KFPS01063-I
- Of the status files for log application processing that are displayed in these messages, the one that is reported in the message that was output most recently is the current file.
- Notes
- If Real Time SAN Replication based on the log-only synchronous method is used, the unit status files for log application processing are used at the log application site. At the transaction execution site, this operand is ignored, if specified.
- 45) pd_syssts_last_active_side_sub = A | B
- When Real Time SAN Replication based on the log-only synchronous method is used, specify this operand if you wish to start HiRDB (or the unit in the case of a HiRDB parallel server configuration) while one of the current files is in error status. In such a case, you specify the normal file in this operand. HiRDB compares the file specified in this operand with the file selected by HiRDB. If their names match, HiRDB copies the contents of the normal file into the secondary file. HiRDB then designates the secondary file as the current file and starts itself. If the file names do not match, HiRDB does not start.
- Conditions
- For details about the supported platforms, see the HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide.
- The following conditions must be satisfied:
- Y is specified in the pd_rise_use operand, and also syssync is specified in the pd_rise_pairvolume_combination operand.
- continue or excontinue is specified in the pd_syssts_initial_error operand.
- The pd_syssts_last_active_subfile operand is specified.
- Notes
- If Real Time SAN Replication based on the log-only synchronous method is used, the unit status files for log application processing are used at the log application site. At the transaction execution site, this operand is ignored, if specified.