5.3 Status changes of status files

Figure 5-2 and Table 5-3 show the status file status changes during HiRDB operation.

Figure 5-2 Status file status changes during HiRDB operation

[Figure]

Table 5-3 Status file status changes during HiRDB operation

EventStatus of status file
OpenClosed
CurrentSpareReservedHold
ACTIVE*STAND BY*CLOSE*NONE*BLOCK ADE*
12345
Shortage of space for status files occurred[Figure]2[Figure]1[Figure][Figure][Figure]
pdstsswap command was executed[Figure]2[Figure]1[Figure][Figure][Figure]
pdstscls command was executed[Figure][Figure]3[Figure][Figure][Figure]
pdstsopen command was executed[Figure][Figure][Figure]2[Figure][Figure]
Output error occurredSingle system[Figure]5[Figure][Figure][Figure][Figure]
Dual sys- temsSpare files exist[Figure]5[Figure][Figure][Figure][Figure]
No spare files existSingle system opera- tion possi- bleBoth systems opera- ting[Figure][Figure][Figure][Figure][Figure]
Single system opera- ting[Figure]5[Figure][Figure][Figure][Figure]
Single system operation not possible[Figure]5[Figure][Figure][Figure][Figure]
Legend:
[Figure]: Does not apply, or status does not change.
[Figure]n: Status to which status file changes after occurrence of the event.
For example, [Figure]1 indicates that after the event occurs, the status of the status file changes to current (status No. 1).
Note
  • The status transitions listed in this table assume that the relevant events were processed normally.
  • Even if the pdstsinit command or pdstsrm command is executed on reserved or hold files, the status of status files displayed by the pdls command does not change.
* Indicates the execution result (status of the status files) of the pdls -d sts command.