Appendix B.1 Processes started by HiRDB/Single Server

The organization of processes started by HiRDB is shown below.

[Figure]

The following table lists processes started by HiRDB/Single Server.

Table B-1 Processes started by HiRDB/Single Server

Server typeProcess nameDescriptionNumber of processesServer name
Notation in manualProcess name
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_prc
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
_admrsvr
HiRDB start process for server mode system switchoverpdstart2dControls 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
1 (none when online)_pdstrt2
Message log server processpdmlgdControls message output1_mlg
System manager processpdrdmdUnit start/stop control, connected user management
(This might also be notated as a name server or a node manager.)
1_rdm
Status server processpdstsdI/O control of status file for units1_sts0
Scheduler processpdscddAllocates transactions to Single Server processes
(This might also be notated as a lock server.)
1_scd
Transaction server processpdtrndControls transactions1_trn
Transaction recovery processpdtrnrvdControls transaction completion/recoveryFrom 1 to the number of crashed pdsds#1_trnrcv
Audit trail management server processpdauddManages audit trailsIf pd_aud_file_name is specified, 1; otherwise, 0_aud
Audit trail automatic load processpdaudldStart control of pdload for automatic data loadingIf pd_aud_file_name is specified and Y is specified in pd_aud_auto_loading, 1; otherwise 0_audld
XDS log output process#7pdprcteeControls output of XDS logIf the pdxds operand is specified, 1; otherwise, 0--
Command execution processpdcmddControls execution of update log reflection commandIf the pdxds operand is specified, 1; otherwise, 0_cmdd
Cluster synchronization monitoring processpdxclSynchronization monitoring of running XDS and standby XDSIf the pdxds operand is specified, 1; otherwise, 0_xcl
Troubleshooting information acquisition processpdprfdControls the troubleshooting function1--
Log server processpdlogdControls system log acquisition and log-related processes1_logN
Deferred write processpd_buf_dfwBackground writes to DB storage disk11dfwN
Asynchronous READ processpd_ios_ardAsynchronous READ facilityValue of pd_max_ard_process1ardN
Process for parallel writes in deferred write processingpd_buf_awtFacility for parallel writes in deferred write processingValue of pd_dfw_awt_process1awtN
REDO processpd_rcv_rdRoll forward of database 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 Y is specified in pd_rdarea_open_attribute_use, the value of pd_max_recover_process#2
2rrnM
Log swap processpdlogswdManages allocation, release and I/O of system log-related files and acquires syncpoint dump1_logNs
Deadlock monitoring processpdlckmndDetects deadlock when lock processing is distributedIf 2 or more is specified for pd_lck_pool_partition and Y is specified for pd_lck_deadlock_check, 1; otherwise, 0_lckmnN
User serverSingle Server processpdsdsSQL processingValue of pd_max_users#3Server name#4
XDS serverXDS processpdxdsSQL processing, manages memory databaseIf the pdxds operand is specified, 1; otherwise, 0#8Server name#9
Utility server#5pdinit control processpdinitdInitialization utility execution process10minit0
pdcopy backup output processpdcopybBackup file outputDegrees of duplication x number of concurrent command executions0bcpy?0#6
pdcopy database read processpdcopyrDatabase readsNumber of concurrent command executions0rcopy0
pdrstr backup read processpdrstrbBackup file readsNumber of concurrent command executions0brstr0
pdrstr master directory RDAREA read processpdrstrmReads master directory RDAREANumber of concurrent command executions0mrstr0
pdrstr unload log read processpdrstrlReads unload log fileNumber of concurrent command executions0lrstr0
pdrstr database write processpdrstrrDatabase writesNumber of concurrent command executions0brstr0
pdrstr master directory RDAREA write processpdrstrwWrites to master directory RDAREANumber of concurrent command executions0wrstr0
pdload control processpdloadmControls data loadsNumber of concurrent pdload command executions0mload0
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 executions0mrorg0
pdgetcst control processpdgcstmCollects optimization informationNumber of concurrent pdgetcst command executions0mgcst0
pddbst control processpddbst1Controls database condition analysisNumber of concurrent pddbst command executions0mdbst0
pdexp control processpdexpmControls dictionary export/import10mexp0
pdplgexe control processpdplgexmControls plug-in utility executionNumber of concurrent executions of commands provided by plug-ins0mplge0
MIB performance information acquisition processpdmbcdAcquires MIB performance information specified by pdmibcmd command10mbcd0
Legend
--: N/A
Notes

#1
If two or more pdsds have crashed, increases to the number of crashes. As the crashed pdsds 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 value of pd_max_users x 2 + 7.
#2
The REDO process starts when HiRDB starts, and stops when startup is complete.
#3
For utility servers, the number of processes is 0. When it exceeds 2,000 after calculation, everything up to 2,000 is processes that are started. When pd_process_count is specified, the number of startup process is the amount of the specification. When the number of access requests exceeds pd_process_count, concurrent processing occurs, the number of processes that start is the number of concurrent accesses, up to value of pd_max_users.
#4
This is the server name specified by the -s option of the system common definition's pdstart operand.
#5
The process only starts up when the corresponding command is executing. The process stops when the command terminates.
#6
? 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).
#7
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.
#8
If the pdxdsstart command is executed, the process starts; it stops if the pdxdsstop command is executed.
#9
This is the server name specified by the -s option of the system common definition's pdxds operand.