16.1.1 Memory allocation

Figure 16-1 shows the memory allocation for a HiRDB/Single Server.

Figure 16-1 Memory allocation for a HiRDB/Single Server

[Figure]

Table 16-1 provides the details of the shared memories for a HiRDB/Single Server.

Table 16-1 HiRDB/Single Server shared memory details

ItemType of shared memory
Unit controller shared memoryGlobal buffer shared memoryUtility shared memorySecurity monitoring information buffer shared memoryInter-process memory communication shared memory
PurposeSystem controlGlobal buffersCommunication between the unit controller and utilitiesSecurity monitoring information bufferClient-server inter-process memory communication
ProcessesAll HiRDB processesSingle ServerUtility processesSingle serverSingle Server, client processes
Number of segments1
  • When the global buffer dynamic update facility is not used: 1-16
  • When the global buffer dynamic update facility is used:
    32-bit mode: 1-516
    64-bit mode: 1-1,016
11Number of clients connected using the PDIPC=MEMORY environment variable (0-2000) [Figure] 2
Maximum value per segmentSee Table 16-2 Size of memory required for a HiRDB/Single Server. Value of the shmmax operating parameter must be equal to or greater than the calculation value.Divide the segment by the SHMMAX operand value. Value of the shmmax operating parameter must be equal to or greater than the SHMMAX operand value.See Table 16-2 Size of memory required for a HiRDB/Single Server. Value of the shmmax operating parameter must be equal to or greater than the calculation value.See Table 16-2 Size of memory required for a HiRDB/Single Server. Value of the shmmax operating parameter must be equal to or greater than the calculation value.See Table 16-2 Size of memory required for a HiRDB/Single Server. Value of the shmmax operating parameter must be equal to or greater than the calculation value.
Allocation conditionsNoneThere must be a global buffer definitionSpecify pd_utl_exec_mode=1Specify 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
Creation timingAt unit activation (including standby unit activation when 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 executedWhen a HiRDB/Single Server starts upWhen client and server are connected
Deletion timingAt next unit activation (including standby unit activation when 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 terminatesWhen a HiRDB Single Server quitsWhen client and server are disconnected
Indication by pdls -d memIndicatedIndicatedIndicatedIndicatedNot indicated
SHM-OWNER of pdls -d memMANAGERServer nameUTILITYAUDDEFNot 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
Remarks[Figure][Figure]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).[Figure][Figure]
Legend:
[Figure]: Not applicable.
#
For details, see the manual HiRDB Version 8 System Definition.