When a user RDAREA or user LOB RDAREA is specified, the corresponding data dictionary RDAREA must be in one of the following statuses:
Open and shutdown release status
Open and shutdown status placed by the pdhold command
If you specify data dictionary RDAREAs, user RDAREAs, and user LOB RDAREAs at the same time, make sure that the data dictionary RDAREA names are specified last.
(5) Rules
The pdopen command can be executed only while HiRDB is active.
The pdopen command must be executed at the server machine containing the single server or the server machine where the system manager is located.
The pdopen command locks each specified RDAREA in the EX mode. If another transaction is accessing a specified RDAREA, the pdopen command goes onto wait status until the other transaction terminates.
If the pdopen command is executed on a shared RDAREA, all back-end servers are locked. If there can be multiple concurrent accesses to the corresponding RDAREA, global deadlock may occur, resulting in a timeout. If global deadlock has occurred, re-execute the pdopen command.
(6) Notes
The result of the pdopen command can be checked by the pddbls command.
The following shows the pdopen command's return codes: 0: Normal termination 4: Warning termination (some RDAREA processing terminated with an error) 8: Abnormal termination 12: Abnormal termination (an event occurred that prevented output of an error message) If the error code is 12, check the error message in the event log at the host where the single server or dictionary server is located, eliminate the cause of the error, and then re-execute the command. If no error message has been output to the event log, contact the customer engineer.