Appendix B.2 Processes started by HiRDB/Parallel Server

The organization of processes started by HiRDB is shown below.

[Figure]

The processes started by HiRDB/Parallel Server are listed in Table B-2 and Table B-3.

Table B-2 Processes started by HiRDB/Parallel Server (1/2)

Server typeProcess nameDescriptionNumber of processesServer nameDoes process start for each server?
Notation in manualProcess name
MGRNon-MGR
System serverHiRDB service processpdserviceControls process server1------
Remote reception processpdrshsrvReceives execution of remote shell/remote copy1 (starts when a remote facility is enabled by the pdntenv command)------
Process server processpdprcdManages HiRDB related processes1_prcYY
Post-processing processpdrsvrePerforms cleanup processing after abnormal termination of a processIf fixed is specified in pd_process_terminator: value of pd_process_terminator_max
If resident is specified in pd_process_terminator: from 3 to the number of processes defined by HiRDB
If nonresident is specified in pd_process_terminator: from 0 to the number of processes that terminated abnormally
_admrsvrYY
HiRDB start process for server mode system switchover 1pdstart2dControls start of HiRDB processes linked to cluster software
  • Standby system switchover that does not perform user server hot standby
  • User server hot standby
  • Rapid system switchover
  • Running system of standby-less system switchover (1:1)
1 (none when online)_pdstrt2YY
HiRDB start process for server mode system switchover 2pdstart2aControls start of HiRDB processes linked to cluster software
  • Standby system of standby-less system switchover (1:1)
1 (none when online)_pdst2a1NY
HiRDB start process for server mode system switchover 3pdsvstartdControls start of HiRDB processes linked to cluster software
  • Standby system of standby-less system switchover (effects distributed)
If activeunits is specified in pd_ha_agent, 1; otherwise, 0_pdsvstdNY
XDS log output process#13pdprcteeControls output of XDS logIf the pdxds operand is specified for a BES within a unit, 1; otherwise, 0--YY
Command execution processpdcmddControls execution of update log reflection commandIf the pdxds operand is specified for a BES within a unit, 1; otherwise, 0_cmddYY
Cluster synchronization monitoring processpdxclSynchronization monitoring of running XDS and standby XDSIf the pdxds operand is specified for a BES within a unit, 1; otherwise, 0_xclYY
Troubleshooting information acquisition processpdprfdControls the troubleshooting function1--YY
Message log server processpdmlgdControls message output
(starts when local is specified for pd_mlg_msg_log_unit)
1_mlgYY
System manager (MGR) processpdrdmdControls unit start/stop and manages connected users
(This might also be notated as a name server or a node manager.)
1_rdmYN
Node manager (non-MGR unit) processpdndmdControls unit start/stop and manages connected users
(This might also be notated as a name server.)
1_ndmNY
Status server processpdstsdControls I/O of status files for units1_sts0YY
Scheduler processpdscddAllocates back-end server, dictionary server, and front-end server processes
(This might also be notated as a lock server.)
1_scdYY
Transaction server processpdtrndControls transactions1_trnYY
Transaction recovery processpdtrnrvdControls transaction completion/recoveryFor an FES:
from 1 to the number of crashed pdfes#1
For a DS:
from 1 to the number of crashed pddic#1
For a BES:
from 1 to the number of crashed pdbes#1
_trnrcvYY
Audit trail management server processpdauddManages audit trailsIf pd_aud_file_name is specified, 1; otherwise, 0_aud
_auz#2
YY
Audit trail automatic load processpdaudldControls start of pdload for automatic data loadIf Y is specified for pd_aud_auto_loading in keeping with the conditions of the audit trail management server process, 1; when N or nothing is specified, 0_audldYN
Unit monitoring processpdrdmaMonitors whether the HiRDB unit is running1 (when the number of units is 1, 0)_rdmckYN

Table B-3 Processes started by HiRDB/Parallel Server (2/2)

Server typeProcess nameDescriptionNumber of processesServer nameDoes process start for each server?
Notation in manualProcess name
BESDSFES
System serverLog server processpdlogdControls system log acquisition and log-related processes1_logN
_lozN#2
YYY
Deferred write processpd_buf_dfwBackground write to DB storage disk11dfwNYYN
Asynchronous READ processpd_ios_ardAsynchronous READ facilityValue of pd_max_ard_process1ardNYYN
Parallel WRITE process for deferred write processingpd_buf_awtFacility for parallel writes in deferred write processingValue of pd_dfw_awt_process1awtNYYN
REDO processpd_rcv_rdDB roll forward at full rerunMIN(number of connected disks, value of pd_max_recover_process)
Number of connected disks: Number of logical volumes that define RDAREAs
If the value of pd_rdarea_open_attribute_use is Y, the value of pd_max_recover_process#3
2rrnMYYN
Log swap processpdlogswdManages allocation, release and I/O of system log-related files and acquires syncpoint dump1_logsN
_lozsN#2
YYY
Deadlock monitoring processpdlckmndDetects deadlock when lock processing is distributedIf 2 or more is specified for pd_lck_pool_partition and if Y is specified for pd_lck_deadlock_check 1; otherwise, 0_lckmnN
_lckmzN#2
YYY
User serverBack-end server processpdbesAccess to databaseMAX(value of pd_max_users, value of pd_max_bes_process)Server name#4YNN
Dictionary server processpddicBatch management of dictionary tableMAX(value of pd_max_users, value of pd_max_dic_process)Server name#4NYN
Front-end server processpdfesSQL processing, instructions to back-end serverValue of pd_max_users,Server name#4NNY
XDS serverXDS processpdxdsSQL processing, manages memory databaseFor each pdxds operand specification, 1#11Server name#12YNN
Utility serverpdinit control processpdinitdInitialization utility execution process10minit0NYN
pdinit execution processpdinitbInitialization utility BES side execution process1 to 20sinit0YNN
pdcopy backup output processpdcopybBackup file output
(starts at the backup output destination specified in pdcopy (-b option))
Degree of duplication x number of concurrent pdcopy command executions0bcpy?0#5NNN
pdcopy database read processpdcopyrDatabase readNumber of servers subject to copy#60rcopyNYYN
pdrstr backup read processpdrstrbBackup file read
(starts at the backup read destination specified in pdrstr (-b option))
Number of concurrent pdrstr command executions0brstr0NNN
pdrstr master directory RDAREA read processpdrstrmReads master directory RDAREA#7Number of concurrent pdrstr command executions0mrstr0NYN
pdrstr unload log read processpdrstrlReads unload log file#8Number of concurrent pdrstr command executions0lrstr0NNN
pdrstr database write processpdrstrrDatabase writesNumber of servers subject to recovery#90brstrNYYN
pdrstr master directory RDAREA write processpdrstrwWrites to master directory RDAREA#1010wrstr0NYN
pdload control processpdloadmControls data loadsNumber of concurrent pdload command executions0mload0YYY
pdrorg control processpdrorgmControls database reorganization (unloading, reloading, index reorganization/re-creation, free page release, and making global buffer resident)Number of concurrent pdrorg, pdreclaim, and pdpgbfon command executions0mrorg0YYY
pdrbal control processpdrbalmControls rebalancingNumber of concurrent pdrbal command executions0mrbal0NYN
pdgetcst control processpdgcstmCollects optimization informationNumber of concurrent pdgetcst command executions0mgcst0NYN
pddbst control processpddbst1Controls database condition analysis (starts at MGR unit)Number of concurrent pddbst command executions0mdbst0NNN
pdexp control processpdexpmControls dictionary export/import
(starts in unit that has export file)
10mexp0NNN
pdplgexe control processpdplgexmPlug-in utility execution controlNumber of concurrent executions of commands provided by plug-ins0mplge0NYN
MIB performance information acquisition processpdmbcdAcquires MIB performance information specified by pdmibcmd command
(starts at MGR unit)
10mbcd0NNN
Legend
Y: Process starts.
N: Process does not start.
--: N/A

Notes
  • The xxxN in the server name increases by 1, 2, ..., up to the maximum number of servers in the unit, based on the number of user servers.
  • The xxxM in the server name increases by 2 to (maximum number of units x 11) based on the definitions.
#1
When two or more pdbes, pdfes, or pddic have crashed, this value increases to the number of crashes. As the crashed pdbes, pdfes, or pddic transactions complete, the number of processes decreases, returning to 1 when there are no more transactions subject to recovery. Note that the upper limit value is the following:
For an FES: value of pd_max_users x 2 + 7
For a DS: value of pd_max_dic_process x 2 + 7)
For a BES: value of pd_max_bes_process x 2 + 7)
#2
For a standby-less system switchover (1:1) configuration, this is the name used when an alternate BES unit is started.
#3
The REDO process starts when HiRDB starts, and stops when startup is complete.
#4
This is the server name specified by the -s option of the system common definition's pdstart operand.
#5
? is increased 0, 1, ..., f by the backup output process's degree of duplication (the number of specifications of the -b option in the control statement file specified by the pdcopy -f option).
#6
The process starts the same number of processes as there are servers that have RDAREAs subject to copying, as specified in pdcopy (-r, -s, -u, and -a options), as members.
#7
The process starts when the host that has the backup file specified in pdrstr (-b option) differs from the host that has the dictionary server. It also starts when the output destination host of the backup file specified in pdrstr (-b option) differs from the host that has the dictionary server.
#8
When pdrstr has specified an unload log file (-l option) or directory (-d option), the process starts if there are two or more servers to recover, or if the host that stores the unload log file is different from the host that has the server that RDAREAs subject to recovery are members of.
#9
The process starts the same number of processes as there are servers that have RDAREAs subject to recovery, as specified in pdrstr (-r, -s, -u, -c, and -a options), as members.
#10
The process starts if the host that specifies the master directory RDAREA as subject to recovery, and that has the backup file, is different from the host that has the dictionary server.
#11
If the pdxdsstart command is executed, the process starts; it stops when the pdxdsstop command is executed.
#12
This is the server name specified by the -s option of the system common definition's pdxds operand.
#13
The XDS log output process starts if the pdstart command executes and then becomes resident. It does not stop even if the pdstop command is executed.