Table 1-2 lists the directories and files that the HiRDB administrator creates.

Table 1-2 Organization of directories and files that the HiRDB administrator creates

File or directory name	Description
$PDDIR/conf/pdsys	File for storing system common definitions
$PDDIR/conf/pdutsys	File for storing unit control information definitions
$PDDIR/conf/pdsvrc	File for storing server common definitions
$PDDIR/conf/server-name	File for storing each server definition
$PDDIR/conf/pduapenv	Directory for storing UAP environment definitions
$PDDIR/conf/chgconf	Directory for storing system reconfiguration definition files
$PDDIR/spool/dfc	Directory for storing DF/UX server process' communication error log

Table 1-3 lists the directories and files that HiRDB creates.

Table 1-3 Directories and files that HiRDB creates

File or directory name	Description
$PDDIR/bin	Directory for storing HiRDB commands and utilities
$PDDIR/lib	Directory for storing HiRDB's shared libraries and message text files
$PDDIR/lib/sysconf	Directory for storing a file that is used to analyze HiRDB system definitions
$PDDIR/lib/sysdef
$PDDIR/lib/servers	Directory for storing HiRDB server's executable files and libraries
$PDDIR/lib/save	Directory for storing information when the pdmemsv command is used to share the libraries
$PDDIR/lib/jvm	Directory for storing libraries that are required to execute the POSIX library HiRDB (created for use with the 32-bit mode HP-UX 11.0 version of HiRDB)
$PDDIR/client/lib	Directory for storing HiRDB client's libraries
$PDDIR/client/lib10_20	Directory for storing HP-UX 10.20 HiRDB client's libraries
$PDDIR/client/utl	Directory for storing HiRDB client's commands and utilities
$PDDIR/client/jba	Directory for storing HiRDB Java stored procedure/function distribution wizard (created for use with the 32-bit-mode Solaris or Linux version of HiRDB)
$PDDIR/include	Directory for storing the header information that is used during UAP creation
$PDDIR/spool/save1	Directory for storing saved core files
$PDDIR/spool/pdshmdump1	Directory for storing shared memory dump files
$PDDIR/spool/pdlckinf1	Directory for storing deadlock time-out information files
$PDDIR/spool/pdsysdump1	Directory for storing simple dump files common to the system
$PDDIR/spool/pdsdsdump1	Directory for storing simple dump files for a single server
$PDDIR/spool/pdfesdump1	Directory for storing simple dump files for a front-end server
$PDDIR/spool/pddicdump1	Directory for storing simple dump files for a dictionary server
$PDDIR/spool/pdbesdump1	Directory for storing simple dump files for a back-end server
$PDDIR/spool/pdstj1, pdstj2	Statistics log files
$PDDIR/spool/pdlog1, pdlog2	Message log files
$PDDIR/spool/pdjnlinf	Directory for storing system log information output files
$PDDIR/spool/pdjnlinf/errinf	Directory for storing system log error information output files
$PDDIR/spool/pdscdqi1, pdscdqi2	Files for storing HiRDB's internal schedule queue information
$PDDIR/spool/oslmqid	File for storing message queue IDs
$PDDIR/spool/oslsmid	File for storing semaphore IDs
$PDDIR/spool/pdprcsts	prc status file
$PDDIR/spool/.pdatmode	Status files for startup and termination
$PDDIR/spool/.pdipcid	Files used for managing semaphore IDs
$PDDIR/spool/.pdommenv	Files for storing shared memory information
$PDDIR/spool/cmdlog/cmdlog1, cmdlog2	Files containing the historical information about the executed commands
$PDDIR/spool/errlog/errlog1, errlog2	Files containing the historical information about internal HiRDB operation
$PDDIR/spool/olkfifs	Directory for storing pipe files for use with thread locking8
$PDDIR/spool/olkrsfs	Directory for storing pipe files for use with thread suspend/resume9
$PDDIR/spool/oslcnt1	File for managing the number of pipe files
$PDDIR/spool/cnctusrinf	File for storing the connected user information if there is any user still connected to HiRDB during the execution of normal termination or a planned termination command
$PDDIR/spool/cnctusrdtl	File for storing the execution result of pdls -d act, pdls -d prc, and pdls -d trn commands if there is any user still connected to HiRDB during the execution of normal termination or a planned termination command
$PDDIR/spool/pdsqldump1	Directory for storing access path information files
any name2	RPC trace file
/dev/HiRDB/pth/3	Directory for storing communication information files
$PDDIR/tmp4	HiRDB's internal work directory
$PDDIR/tmp/pdommenv	File for storing shared memory information
$PDDIR/tmp/home/server-name	Current work directory
$PDDIR/conf	Directory for storing HiRDB system definition files
$PDDIR/conf/backconf	Directory for storing the pre-reconfiguration HiRDB system definition when executing the system reconfiguration command
$PDDIR/conf/inittab	/etc/inittab save directory
any name5	Communication error log file for DF/UX server process
$PDDIR/.dbenv	Directory for storing HiRDB database environment information files
$PDCLTPATH/pdsql1.trc, pdsql2.trc6	Files for storing trace information for SQL that is executed by a UAP
$PDCLTPATH/pderr1.trc, pderr2.trc6	Files for storing information about communication errors between a UAP and a server
$PDDIR/plugin	Directory that integrates all HiRDB plug-in directories
$PDDIR/plugin/.sys	HiRDB's internal work directory
$PDDIR/plugin/lib	Directory for storing plug-in libraries
$PDDIR/plugin/plug-in-name	Plug-in directory
$PDDIR/plugin/plug-in-name/.sys	HiRDB's internal work directory
$PDDIR/plugin/plug-in-name/bin	Directory for storing plug-in commands
$PDDIR/plugin/plug-in-name/etc	Directory for storing the common files that are required by all plug-ins
$PDDIR/plugin/plug-in-name/conf	Directory for storing plug-in configuration files
$PDDIR/jre7	JavaTM execution environment
$PDDIR/renew	Directory used during updating to the HiRDB update version
$PDDIR/renew_bak	Directory for backing up the operating HiRDB when updating to the HiRDB update version
$PDDIR/.pdlogprgid	File for managing the syslog program ID
For HP-UX /sbin/init.d/ /sbin/rc1.d/ For Solaris /etc/init.d/ /etc/rc0.d/ /etc/rc1.d/ For Linux /etc/init.d/ /etc/rc0.d/ /etc/rc1.d/ /etc/rc6.d/	Directory for storing script files that run when the operating system starts up or shuts down. File name: For HP-UX or Solaris HiRDB/Single Server is HiRDB_S or K090HiRDB_S HiRDB/Parallel Server is HiRDB_P or K090HiRDB_P For Linux HiRDB/Single Server is HiRDB_S, K09HiRDB_S, or S91HiRDB_S HiRDB/Parallel Server is HiRDB_P, K09HiRDB_P, or S91HiRDB_P

¹ Because HiRDB uses this directory to output troubleshooting information, it may keep increasing in size. You should use the pdcspool command periodically to delete the contents.

You use the operands listed below for periodic deletion of troubleshooting information. For details about these operands, see the manual HiRDB Version 8 System Definition:

• pd_spool_cleanup_interval
• pd_spool_cleanup_interval_level
• pd_spool_cleanup
• pd_spool_cleanup_level

² To specify the filename, use the pd_rpc_trace_name operand.

³ The files in this directory can be deleted when all HiRDB servers in this server machine have stopped.

⁴ This directory is used internally by HiRDB. Do not create directories or files in this directory. Do not specify this directory for use by HiRDB to create files (for example, for the pd_rpc_trace_name operand). This directory is deleted and re-created each time the unit starts.

⁵ Use one of the following methods to specify the file name. We recommend that you use $PDDIR/spool/dfc.

• Use the user environment variable PDCLTPATH that starts DF/UX.
• To start DF/UX upon booting the server machine, use the environment variable PDCLTPATH specified before the dfstart command by localrc in the /etc/rc file.

⁶ Two copies of this file are output to the directory specified with PDCLTPATH. If PDCLTPATH is omitted, the files are output to the current directory used to start the UAP (in the case of a UAP started from OpenTP1, $DCDIR/tmp/home/directory-with-server-name-xx).

The names for the files to be created depends on whether or not X/Open-compliance API (TX_ function) was used. When the TX_ function is used, the files are created with the following names:

• pdsqlxxxxx-1.trc, pdsqlxxxxx-2.trc
• pderrxxxxx-1.trc, pderrxxxxx-2.trc

Legend:

xxxxx: Process ID during UAP execution

Because the process ID is used in the file name, note that as many files as there are processes may be output during UAP execution.

⁷ This directory is created when the version is earlier than 07-03. When version 07-03 or later is used, this directory is not created because JRE is not bundled with the package.

⁸ The number of pipe files created in this directory is the value of the pd_max_server_process operand + 100.

⁹ Shown below are the formulas for approximating the number of pipe files to be created in this directory:

• HiRDB/Single Server
  value-of-pd_max_server_process + 127 + value-of-pd_max_users a
  a: 4 if pipe is specified for the pd_lck_release_detect operand, 0 otherwise.
  
• HiRDB/Parallel Server
  value-of-pd_max_server_process + 127 + b
  b: Use one of the following formulas, as applicable, when pipe is specified for the pd_lck_release_detect operand, 0 otherwise:
  Front-end server: value-of-pd_max_users 2
  Dictionary server: value-of-pd_max_dic_process 35
  Back-end server: value-of-pd_max_bes_process 35
  Include in the total the appropriate value for the servers in the unit.