The following figure and the table below show the status file status changes that occur during operation of HiRDB.

Figure 5-2 Status file status changes during HiRDB operation

Table 5-3 Status file status changes during HiRDB operation

Event					Status of status file
					Open		Closed
					Current	Spare	Reserved		Hold
					ACTIVE#	STAND BY#	CLOSE#	NONE#	BLOCK ADE#
					1	2	3	4	5
Shortage of space for status files occurred					2	1	--	--	--
pdstsswap command was executed					2	1	--	--	--
pdstscls command was executed					--	3	--	--	--
pdstsopen command was executed					--	--	2	--	--
Output error occurred	Single system				5	--	--	--	--
	Dual sys- tems	Spare files exist			5	--	--	--	--
		No spare files exist	Single system opera- tion possi- ble	Both systems opera- ting	--	--	--	--	--
				Single system opera- ting	5	--	--	--	--
			Single system operation not possible		5	--	--	--	--

Legend:

--: Does not apply, or status does not change.

n: Status to which status file changes after occurrence of the event.

For example, 1 indicates that after the event occurs, the status of the status file changes to current (status No. 1).

Notes

• 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.