The organization of processes started by HiRDB is shown below.

The following table lists processes started by a HiRDB single server configuration.

Table B-1 Processes started by a HiRDB single server configuration (system server)

Process name		Description	Number of processes	Server name
Notation in manual	Process name
Process server process	pdprcd	Manages HiRDB related processes	1	_prc
Post-processing process	pdrsvre	Performs cleanup processing after abnormal termination of a process	If 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 switchover	pdstart2d	Controls 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 process	pdmlgd	Controls message output	1	_mlg
System manager process	pdrdmd	Unit start/stop control, connected user management (This might also be notated as a name server or a node manager.)	1	_rdm
Status server process	pdstsd	I/O control of status file for units	1	_sts0
Scheduler process	pdscdd	Allocates transactions to single server processes (This might also be notated as a lock server.)	1	_scd
Transaction server process	pdtrnd	Controls transactions	1	_trn
Transaction recovery process	pdtrnrvd	Controls transaction completion/recovery	From 1 to the number of crashed pdsds#1	_trnrcv
Audit trail management server process	pdaudd	Manages audit trails	If pd_aud_file_name is specified, 1; otherwise, 0	_aud
Audit trail automatic load process	pdaudld	Start control of pdload for automatic data loading	If pd_aud_file_name is specified and Y is specified in pd_aud_auto_loading, 1; otherwise 0	_audld
XDS log output process#8	pdprctee	Controls output of XDS log	If the pdxds operand is specified, 1; otherwise, 0	--
Command execution process	pdcmdd	Controls execution of update log reflection command	If the pdxds operand is specified, 1; otherwise, 0	_cmdd
Cluster synchronization monitoring process	pdxcl	Synchronization monitoring of running XDS and standby XDS	If the pdxds operand is specified, 1; otherwise, 0	_xcl
Troubleshooting information acquisition process	pdprfd	Controls the troubleshooting function	1	--
Log server process	pdlogd	Controls system log acquisition and log-related processes	1	_logN
Deferred write process	pd_buf_dfw	Background writes to DB storage disk	1	1dfwN
Asynchronous READ process	pd_ios_ard	Asynchronous READ facility	Value of pd_max_ard_process	1ardN
Process for parallel writes in deferred write processing	pd_buf_awt	Facility for parallel writes in deferred write processing	Value of pd_dfw_awt_process	1awtN
REDO process	pd_rcv_rd	Roll forward of database at full rerun	MIN(number of connected disks, value of pd_max_recover_process) Number of connected disks: Number of character special files that define RDAREAs If Y is specified in pd_rdarea_open_attribute_use, the value of pd_max_recover_process#2	2rrnM
Log swap process	pdlogswd	Manages allocation, release and I/O of system log-related files and acquires syncpoint dump	1	_logNs
Deadlock monitoring process	pdlckmnd	Detects deadlock when lock processing is distributed	If 2 or more is specified for pd_lck_pool_partition and Y is specified for pd_lck_deadlock_check, 1; otherwise, 0	_lckmnN

Table B-2 Processes started by a HiRDB single server configuration (user server)

Process name		Explanation	Number of processes	Server name
Notation in manual	Process name
Single server process	pdsds	SQL processing	Value of pd_max_users + value of pd_max_reflect_process_count#3	Server name#4

Table B-3 Processes started by a HiRDB single server configuration (XDS server)

Process name		Explanation	Number of processes	Server name
Notation in manual	Process name
XDS process	pdxds	SQL processing, manages memory database	If the pdxds operand is specified, 1; otherwise, 0#9	Server name#10

Table B-4 Processes started by a HiRDB single server configuration (utility server)

Process name#5		Explanation	Number of processes	Server name
Notation in manual	Process name
pdinit control process	pdinitd	Initialization utility execution process	1	0minit0
pdcopy backup output process	pdcopyb	Backup file output	Degrees of duplication number of concurrent command executions	0bcpy?0#6
pdcopy database read process	pdcopyr	Database reads	Number of concurrent command executions	0rcopy0
pdrstr backup read process	pdrstrb	Backup file reads	Number of concurrent command executions	0brstr0
pdrstr master directory RDAREA read process	pdrstrm	Reads master directory RDAREA	Number of concurrent command executions	0mrstr0
pdrstr unload log read process	pdrstrl	Reads unload log file	Number of concurrent command executions	0lrstr0
pdrstr database write process	pdrstrr	Database writes	Number of concurrent command executions	0brstr0
pdrstr master directory RDAREA write process	pdrstrw	Writes to master directory RDAREA	Number of concurrent command executions	0wrstr0
pdload control process	pdloadm	Controls data loads	Number of concurrent pdload command executions	0mload0
pdrorg control process	pdrorgm	Controls database reorganization (unloading, reloading, index reorganization/re-creation, free page release, and making global buffers resident)	Number of concurrent pdrorg, pdreclaim, and pdpgbfon command executions	0mrorg0
pdgetcst control process	pdgcstm	Collects optimization information	Number of concurrent pdgetcst command executions	0mgcst0
pddbst control process	pddbst1	Controls database condition analysis	Number of concurrent pddbst command executions	0mdbst0
pdexp control process	pdexpm	Controls dictionary export/import	1	0mexp0
pdplgexe control process	pdplgexm	Plug-in utility execution control	Number of concurrent executions of commands provided by plug-ins	0mplge0
pdorend control process	pdorendm	Online reorganization Reflection control	1	0more0
pdorend application process	pdorendl	Online reorganization Reflection processing	Degrees of duplication (number of specifications of the pdorend command's -m option)	0lore?0#7

Legend

--: 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 11 based on the definitions.
• The server name is used in message output, command information output, and so on.

#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. The upper limit value is as follows:

MIN(value of pd_trn_rcvmsg_store_buflen 72, (value of pd_max_users + value of pd_max_reflect_process_count) 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 + value of pd_max_reflect_process_count.

#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

? is increased 1, 2, ..., 8 by the online reorganization reflection processing's degree of duplication (the number of specifications of the pdorend command's -m option).

#8

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.

#9

If the pdxdsstart command is executed, the process starts; it stops if the pdxdsstop command is executed.

#10

This is the server name specified by the -s option of the system common definition's pdxds operand.