3.3.14 Operands related to unit status files (when an error occurs)

For details about the measures to be taken when an error occurs in a status file, see the HiRDB Version 8 System Operation Guide.

38) pd_syssts_initial_error = stop | continue | excontinue
When HiRDB (or a unit) starts, HiRDB performs a process of identifying the current unit status file. This operand specifies the action that HiRDB takes when any of the following errors is detected during this identification process.
  • No real unit status file is found.
  • An error is detected in the unit status file.
Note that the current file identification process is applied to the unit status files specified by the pd_syssts_file_name_1 to 7 operands.
stop:
When an error is detected in the unit status file during the current file identification process, the startup of HiRDB (or the unit) is stopped. In this case, first take a corrective action for the status file in which the error was detected, and then start HiRDB.
continue or excontinue:
Even when an error is detected in the unit status file during the current file identification process, the startup of HiRDB (or the unit) is continued if the current file is normal. However, the startup may be stopped depending on the value specified for the pd_syssts_singleoperation operand (whether operation should continue with a single status file). The following table shows the relationship to the pd_syssts_singleoperation operand.
[Figure]Relationship to the pd_syssts_singleoperation operand
pd_syssts_singleoperation
operand value
Processing by HiRDBHiRDB administrator's action
continueWhen an error is detected in the unit status file, HiRDB cannot identify the current file, and thus the startup of HiRDB (or the unit) is stopped.The HiRDB administrator identifies the current file and specifies the pd_syssts_last_active_file and pd_syssts_last_active_side operands. Afterwards, start HiRDB (or the unit).
stop (default value)When an error is detected in the unit status file, HiRDB identifies the current file, and the startup of HiRDB (or the unit) is continued. However, if File A or B satisfies any of the conditions listed in the following table (cases in which HiRDB cannot identify the current file), the startup of HiRDB is stopped.If HiRDB cannot identify the current file, the HiRDB administrator identifies the current file and specifies the pd_syssts_last_active_file and pd_syssts_last_active_side operands. Afterwards, start HiRDB (or the unit).
[Figure]When HiRDB cannot identify the current file
pd_syssts_initial_error
operand value
File A statusFile B status
continueError shutdownError shutdown
Error shutdownOpen (initial state)
Error shutdownNo real file
Open (initial state)Error shutdown
Open (initial state)No real file
No real fileOpen (initial state)
No real fileError shutdown
No real fileNo real file
excontinueError shutdownError shutdown
Error shutdownNo real file
No real fileError shutdown
No real fileNo real file
Therefore, to minimize actions by the HiRDB administrator (to reduce the number of cases in which both the pd_syssts_last_active_file and pd_syssts_last_active_side operands must be specified), specify the following:
  • pd_syssts_initial_error = excontinue
  • pd_syssts_singleoperation = stop
Specification guidelines
The following table shows the specification guidelines, along with their advantages and disadvantages.
Itempd_syssts_initial_error operand value
stopcontinue or excontinue
Processing by HiRDB during HiRDB or unit startupWhen an error is detected in a unit status file, the startup of HiRDB (or the unit) is stopped.Even when an error is detected in a unit status file, the startup of HiRDB (or the unit) is continued if the current file is normal.
Specification guidelineTo improve system reliability, specify stop.To simplify the error-handling actions during HiRDB startup, specify continue or excontinue.
AdvantageGuarantees that all unit status files are normal when HiRDB starts. Therefore, if an error occurs in the current file after HiRDB has started, it can be swapped to a spare file.Even when an error is detected in a unit status file during HiRDB startup, HiRDB can start with the remaining normal files only. Therefore, HiRDB stop time can be shortened. In this case, because the number of spare files has become small, it is necessary to immediately repair the status files containing errors.
DisadvantagePossibility increases that an error in a unit status file stops the startup of HiRDB.Because HiRDB may be running with only a small number of spare files, system reliability is low. Depending on the number of spare files available, it may not be possible to swap unit status files.
Notes
  • If both current files are abnormal, the startup of HiRDB (or the unit) is stopped regardless of the value specified for this operand.
  • Before starting HiRDB, do not initialize the current file with the pdstsinit command. If the current file is initialized, HiRDB cannot be restarted.
Remarks
The following figure shows specification values for this operand, processing by HiRDB, and actions to be taken by the HiRDB administrator.
[Figure]Specification values for this operand and processing by HiRDB
[Figure]
[Figure]Processing by HiRDB and actions by HiRDB administrator
Corresponding No.Processing by HiRDBHiRDB administrator's action
[1]HiRDB startup processing continues.None
[2]HiRDB identifies the latest current file and continues the startup processing.Make the file that is in the error-shutdown state into a spare file.
[3]Using the file specified in the pd_syssts_last_active_file operand as the current status file, HiRDB startup processing continues.Make the file that is in the error-shutdown state into a spare file.
[4]Using the files specified in the pd_syssts_last_active_file and pd_syssts_last_active_side operands as the current status files, HiRDB startup processing continues.Make the file that is in the error-shutdown state into a spare file.
[5]Because stop is specified for the pd_syssts_initial_error operand, HiRDB startup processing is stopped.See the manual HiRDB Version 8 Messages, and take the corrective action indicated by the reason code 0000000010​ in message KFPS01005-E.
[6]Because the current file that was being used during the previous operation cannot be identified, HiRDB startup processing is stopped.See the manual HiRDB Version 8 Messages, and take the corrective action indicated by the reason code 0000000016​ in message KFPS01005-E.
[7]Because the normal current file identified by HiRDB does not match the file specified in the pd_syssts_last_active_side operand, HiRDB startup processing is stopped.See the manual HiRDB Version 8 Messages, and take the corrective action indicated by the reason code 0000000017​ in message KFPS01005-E.
[8]Because the current file name identified by HiRDB does not match the file name specified in the pd_syssts_last_active_file operand, HiRDB startup processing is stopped.See the manual HiRDB Version 8 Messages, and take the corrective action indicated by the reason code 0000000015​ in message KFPS01005-E.
[9]Because the normal current file that was being used during the previous operation cannot be identified, HiRDB startup processing is stopped.See the manual HiRDB Version 8 Messages, and take the corrective action indicated by the reason code 0000000018​ in message KFPS01005-E.
39) pd_syssts_singleoperation = stop | continue
Specifies whether or not processing may continue in the single-operation mode for unit status files.
The status file single-operation mode means that processing is to continue using only the normal file (single file) when an error occurs in the status file and a spare file is not available. For details about the status file single-operation mode, see the HiRDB Version 8 Installation and Design Guide.
If an error occurs in one of the current files and a spare file is available, the status file is swapped and processing continues regardless of the value specified for this operand (operation in the single-operation mode does not occur).
stop:
Do not permit operation in the single-operation mode. If operation in the single-operation mode is necessary, HiRDB (or a unit for a HiRDB/Parallel Server) is abnormally terminated. If HiRDB is abnormally terminated, allocate spare files and then restart HiRDB.
continue:
Enable operation in the single-operation mode. When the single-operation mode goes into effect, the message KFPS01044-I is output. If an error occurs in the normal file during operation in the single-operation mode, or if HiRDB (or a unit for a HiRDB/Parallel Server) is abnormally terminated while the status file is being updated, HiRDB cannot be restarted. Therefore, when the single-operation mode goes into effect, immediately allocate spare files.
Specification guidelines
  • Hitachi recommends that you specify stop to increase system reliability. Hitachi also recommends that you increase the number of spare files to guard against errors in the current files.
  • The following table shows the specification guidelines, along with their advantages and disadvantages.
    Itempd_syssts_singleoperation operand value
    stopcontinue
    Specification guidelineTo improve system reliability, specify stop.Specify continue if it is important not to stop HiRDB.
    AdvantageWhen an error occurs in one of the current files and a spare file is not available, operation in the single-operation mode does not occur, and HiRDB is abnormally terminated. Consequently, the possibility of losing the content of the current files is reduced.Even when an error occurs in one of the current files and a spare file is not available, processing can be continued. Therefore, the possibility that an error in the status file stops HiRDB is reduced.
    DisadvantagePossibility that an error in the status file stops HiRDB increases. However, increasing the number of spare files can reduce this possibility.If an error occurs in the normal status file during operation in the single-operation mode, or if HiRDB is abnormally terminated during updating of the status file, the content of the current file is lost and HiRDB cannot be restarted.
Relationship to other operands
The combination of the values specified for the pd_syssts_singleoperation and pd_syssts_initial_error operands determines the processing by HiRDB when an error occurs in the status file. Therefore, the values to be specified for these operands should be determined together.
40) pd_syssts_last_active_file = "logical-file-name"
[Figure]<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) 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 must be 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
  1. 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.
  2. 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 may have been initialized. In this case, first initialize all status files, then use the method in 1 above to start HiRDB (forced startup will be used, regardless of the previous termination mode).
  3. When one of the current status files has an error:
    Use the method in 2 above, with the following operands specified:
    [Figure]pd_syssts_singleoperation = continue or excontinue
    [Figure] pd_syssts_last_active_side
  4. When both of the current status files have errors:
    Initialize all status files, then execute the method in 1 above (forced startup will be used, regardless of the previous termination mode).
  5. 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.
41) pd_syssts_last_active_side = A | B
Specify this operand if you want to start HiRDB (or a unit for a HiRDB/Parallel Server) 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