![[Contents]](FIGURE/CONTENT.GIF)
Nonstop Database, HiRDB Version 9 System Operation Guide
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
If a server process is terminated by a forced termination request due to an interrupt at the client during transaction execution, or if a server process connected to a UAP is terminated by the pdcancel command, HiRDB displays the KFPS01820-E and KFPO00105-E messages, which indicate termination of the server process. These messages are also displayed when a server process is terminated due to some abnormality in the server's processing. To determine the cause of such a termination, you must also check other messages, such as KFPS00993-I, that are displayed by HiRDB.
Use of the facility for changing the process-down message when a transaction is canceled enables you to change the IDs of the KFPS01820-E and KFPO00105-E messages that are displayed in the case of client-related operations and errors. When you do this, you can easily identify a termination of server processing that was caused by a client-related operation or error simply by checking the message IDs (thus eliminating the need to check other messages).
This facility changes only the message IDs; it does not change the message text or output information (the original message text and output information are still displayed as is even after the message ID has been changed).
The following table lists the messages that can be changed by this facility.
Table 20-5 Messages whose message IDs can be changed
| Message ID that can be changed | Description of the message | Message ID after change |
|---|---|---|
| KFPS01820-E | Server process was terminated. | KFPS01852-W |
| KFPO00105-E | Server process was terminated because an error occurred (abort message). | KFPO00115-W |
For details about these messages, see the manual HiRDB Version 9 Messages.
The table below shows whether message IDs are changed, depending on the process-down event that takes place.
Table 20-6 Whether message IDs are changed depending on the process-down event
| No. | Event | Cause of process-down | Msg ID chgd | Remarks | |||||
|---|---|---|---|---|---|---|---|---|---|
| User op | Env set'g | Client error | Client comm err | Svr error | S-to-S comm error | ||||
| 1 | Forced termination request due to an interrupt at the client | C | -- | -- | -- | -- | -- | Yes | HiRDB server process was terminated during execution of a transaction due to a forced termination request caused by an interrupt at the client.#1 |
| 2 | Server process killed due to a client process-down | -- | -- | C | C | -- | -- | Yes | For a client process using XA, see No. 11. |
| 3 | HiRDB server process killed because PDCWAITTIME was exceeded | -- | C#2 | -- | C | C | -- | No | HiRDB cannot identify the cause.#3 |
| 4 | Process-down (exit) at HiRDB server because PDSWAITTIME was exceeded | -- | C | C | C | -- | -- | Yes | -- |
| 5 | Process-down (exit) at HiRDB server because PDSWATCHTIME was exceeded | -- | C | C | C | -- | -- | Yes | -- |
| 6 | HiRDB server process killed due to forced termination of unit, unit down, or transaction recovery during system switchover | C | -- | -- | -- | --#4 | --#4 | Yes | Applicable to another unit's branch recovery. This is applicable only to a HiRDB parallel server configuration. |
| 7 | HiRDB server process killed due to forced termination of unit, unit down, or utility branch recovery during system switchover | C | -- | -- | -- | --#4 | --#4 | Yes | Applicable not only to recovery in the local unit but also to another unit's branch recovery. |
| 8 | HiRDB server killed by pdcancel command (including a killed utility) | C | -- | --#4 | -- | --#4 | --#4 | Yes | -- |
| 9 | HiRDB server process killed due to forced termination of transaction by pdfgt command (transaction branch recovery) | C | -- | --#4 | -- | --#4 | --#4 | Yes | -- |
| 10 | HiRDB server process killed by the facility for monitoring free area for system log file | C#5 | C#6 | -- | -- | -- | -- | Yes | KFPS01160-E message is displayed. |
| 11 | HiRDB server process killed by XA completion instruction issued by the transaction manager in an extension of transaction recovery | C | -- | -- | -- | C | C | No | HiRDB cannot identify the cause.#7 |
| 12 | HiRDB server process killed due to recovery when the synchronization skip count exceeded the boundary value | C#8 | C#6 | -- | -- | C | -- | No | HiRDB cannot determine the cause. |
| 13 | Process-down (exit) at HiRDB server due to timeout during communication between HiRDB server processes | -- | -- | -- | -- | C | C | No | -- |
| 14 | Communication request processing from a shutdown unit when recovery- unnecessary front-end server is used | -- | -- | -- | -- | C | C | No | -- |
| 15 | Process-down (exit) at server due to transaction completion error when recovery- unnecessary front-end server is used | -- | -- | -- | -- | C | C | No | -- |
| 16 | Process-down at HiRDB server when automatic log unloading facility was terminated due to a server failure | -- | -- | -- | -- | C | C | No | -- |
| 17 | Server process failure shutdown (such as internal processing failure, process failure, or transaction start error) | -- | -- | -- | -- | C | C | No | -- |
| 18 | HiRDB server process killed during transaction and utility branch recovery due to HiRDB server process failure shutdown | -- | -- | -- | -- | --#4 | --#4 | Yes | Recovery processing caused by No. 17. |
To use this facility, either omit the pd_cancel_down_msgchange operand or specify Y.
All Rights Reserved. Copyright (C) 2011, 2015, Hitachi, Ltd.