The following figure shows the memory allocation for a HiRDB single server configuration.

Figure 15-1 Memory allocation for a HiRDB single server configuration

The following table lists details for HiRDB single server configuration shared memory.

Table 15-1 HiRDB single server configuration shared memory details

Item	Type of shared memory
	Unit controller shared memory	Global buffer shared memory	Utility shared memory	Security monitoring information buffer shared memory	Inter-process memory communication shared memory	Troubleshooting information acquisition shared memory
Purpose	System control	Global buffers	Communication between the unit controller and utilities	Security monitoring information buffer	Client-server inter-process memory communication	Acquisition of troubleshooting information
Processes	All HiRDB processes	Single server	Utility processes	Single server	Single server, client processes	All HiRDB processes
Number of segments	1	If the facility for dynamic updating of global buffers is not used: 1 to 512 If the facility for dynamic updating of global buffers is used: 32-bit mode: 1 to 1,012 64-bit mode: 1 to 1,512	1	1	Number of clients connected using the PDIPC=MEMORY environment variable (0-2,000) 2	1
Maximum value per segment	See Table 15-2 Size of memory required for a HiRDB single server configuration. Value of the shmmax operating system parameter must be equal to or greater than the calculation value.	Divide the segment by the SHMMAX operand value. Value of the shmmax operating system parameter must be equal to or greater than the SHMMAX operand value.	See Table 15-2 Size of memory required for a HiRDB single server configuration. Value of the shmmax operating system parameter must be equal to or greater than the calculation value.	See Table 15-2 Size of memory required for a HiRDB single server configuration. Value of the shmmax operating system parameter must be equal to or greater than the calculation value.	See Table 15-2 Size of memory required for a HiRDB single server configuration. Value of the shmmax operating system parameter must be equal to or greater than the calculation value.	10 MB
Allocation conditions	None	There must be a global buffer definition	Specify pd_utl_exec_mode=1	Specify the pd_aud_file_name operand as the HiRDB file system area name for the audit trail file.	There are clients connected using the PDIPC=MEMORY environment variable	None
Creation timing	At unit activation (including standby unit activation when user server hot standby or the rapid system switchover facility is used)	At server activation (including standby unit activation when the rapid system switchover facility is used) When pdbufmod -k {add|upd} is executed	When utilities are executed	When a HiRDB single server configuration starts up	When client and server are connected	At unit activation (including standby unit activation when user server hot standby or the rapid system switchover facility is used)
Deletion timing	At next unit activation (including standby unit activation when user server hot standby or the rapid system switchover facility is used)	When pdbufmod -k del is executed For normal termination or planned termination: When the server is terminated For forced termination, abnormal termination, or termination of standby unit when the rapid system switchover facility is used: When the unit is next activated	10 minutes after the utility terminates	When a HiRDB Single server quits	When client and server are disconnected	At unit termination
Indication by pdls -d mem	Indicated	Indicated	Indicated	Indicated	Not indicated	Not indicated
SHM-OWNER of pdls -d mem	MANAGER	Server name	UTILITY	AUDDEF	Not indicated	Not indicated
Related operands	pd_shmpool_attribute pd_sds_shmpool_size	pd_dbbuff_attribute pd_dbbuff_modify pdbuffer SHMMAX	pd_utl_exec_mode	Operands related to the security audit facility#	PDIPC PDSENDMEMSIZE PDRECVMEMSIZE	None
Remarks	--	--	Can be created only when pd_utl_exec_mode=1 (when pd_utl_exec_mode=0, the relevant space is allocated in the unit controller shared memory).	--	--	--

Legend:

--: Not applicable.

#

For details, see the manual HiRDB Version 9 System Definition.