Cautions

When you cannot update to the HiRDB update version
In the following cases, an operating HiRDB cannot update to the HiRDB update version:
- In the case of a HiRDB/Parallel Server, when not all servers and units have terminated (including reduced mode units) or when network communication between units is blocked
- When a transaction or utility is still operating more than 15 minutes after the pdprgrenew command was executed
- When the HiRDB Datareplicator linkage facility is used, and the setting of the pd_rpl_init_start operand and the actual data extraction mode differ as follows:
  Y is the setting for the pd_rpl_init_start operand, and the pdrplstop command was executed to stop the HiRDB Datareplicator linkage facility
  N is the setting for the pd_rpl_init_start operand, and the pdrplstart command was executed to start the HiRDB Datareplicator linkage facility
UAP response delay
While the pdprgrenew command is executing, UAP response times will be delayed. Thus, we recommend that you execute this command when traffic in the system is relatively low.
Definition reconfiguration
The memory requirements change when you update to the HiRDB update version, which necessitates reconfiguration of the system definition. Thus, the HiRDB system definition must be reconfigured in advance with the pdchgconf system reconfiguration command. For details about the system reconfiguration command, see the manual HiRDB Version 8 System Operation Guide.
Execution of operation commands and utilities
You must not execute operation commands or utilities while the pdprgrenew command is executing. Doing so may result in an error causing HiRDB to terminate or in a failure when HiRDB is updated.
Use of the system switchover facility
You cannot use the system switchover facility while updating to the update version.
Invalid holdable cursor
As the cursor cannot be maintained while updating to the update version, a UAP that uses the holdable cursor cannot be used just before or after updating. Doing so will result in an error at the UAP.
Invalid LOCK statement of the UNTIL DISCONNECT setting
As the UNTIL DISCONNECT setting cannot maintain an exclusive lock while updating to the update version, the LOCK statement cannot use the UNTIL DISCONNECT setting just before or after updating. Doing so will result in an error at the UAP.

1.4.5 Cautions