2.75 pdopen (Open RDAREAs)

Organization of this section
(1) Function
(2) Executor
(3) Format
(4) Options
(5) Rules
(6) Notes

(1) Function

The pdopen command opens specified RDAREAs.

(2) Executor

HiRDB administrator

(3) Format

pdopen -r {RDAREA-name[,RDAREA-name]...|ALL}

(4) Options

(a) -r {RDAREA-name[,RDAREA-name]...|ALL}
-r RDAREA-name ~<identifier> ((1-30))
Specifies the name of an RDAREA that is to be opened.
ALL
Specifies that all RDAREAs are to be opened, except for the master directory RDAREA.
Rules
  1. For the rules for specifying RDAREAs, see 1.5.2 Specification of RDAREAs in operation commands and utilities.
  2. An already open RDAREA cannot be opened again.
  3. 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
  4. 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

  1. The pdopen command can be executed only while HiRDB is active.
  2. The pdopen command must be executed at the server machine containing the single server or the server machine where the system manager is located.
  3. 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.
  4. 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

  1. The result of the pdopen command can be checked by the pddbls command.
  2. 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.