When a HiRDB system is created by the system generator (g specified on the Master menu), the initialization commands are output to the log file.

Should the system files need to be reviewed for tuning purposes, this log file helps improve the efficiency of the review process. Moreover, if the HiRDB system needs to be reset to its initial status, the contents of this log file can be used to simplify the process.

Table 4-4 lists the contents of the log file.

Table 4-4 Contents of the log file

Item	Description
Output destination	$PDDIR/conf at the server machine where the system manager is defined
Type	Regular file (UNIX file)
Name	pdgen_cmd."name-of-host-where-unit-was-created"
Access privilege	User who executed pdgen has reference and update privileges. Other users have reference privilege only.
Output information1 (when output is to the server machine where the system manager is defined)	Contents of environment variables during creation (PDDIR, PDCONFPATH, SHLIB_PATH2, PATH) Details of creation of HiRDB file system areas for system files (pdfmkfs) Details of creation of HiRDB file system areas for RDAREAs (pdfmkfs) Details of initialization of unit status files (pdstsinit) Details of initialization of server status files (pdstsinit) Details of initialization of synchronization point dump files for server (pdloginit) Details of initialization of system log files for server (pdloginit)
Output information1 (when output is to a server machine other than where the system manager is defined)	Contents of environment variables during creation (PDDIR, PDCONFPATH, SHLIB_PATH2, PATH) Details of creation of HiRDB file system areas for system files (pdfmkfs) Details of creation of HiRDB file system areas for RDAREAs (pdfmkfs)

¹ The command (pdfmkfs) for creating a HiRDB file system area is executed for each server machine (host) in which the HiRDB file system area is to be created, and its log information is output to the file corresponding to each host. On the other hand, the commands for initializing a status file (pdstsinit), a synchronization point dump file (pdloginit), and a system log file (pdloginit) are executed on the server machine where the system manager is located; therefore, their log information is output to the file corresponding to the host where the system manager is located.

² The environment variable is LD_LIBRARY_PATH for Solaris and Linux and LIBPATH for AIX 5L.

• Example of output log file (corresponding to the host where the system manager is located)
  

  PDDIR="/HiRDB" PDCONFPATH="${PDDIR}/conf" SHLIB_PATH="${PDDIR}/lib" PATH="${PDDIR}/bin:${PATH}" pdfmkfs -r -n 56 -l 100 -k SVR -e 100 -i /sysarea pdstsinit -u u001 -f /sysarea/u001st1a -c 32 pdstsinit -u u001 -f /sysarea/u001st1b -c 32 pdstsinit -u u001 -f /sysarea/u001st2a -c 32 pdstsinit -u u001 -f /sysarea/u001st2b -c 32 . . . pdloginit -d sys -s dic -f /sysarea/dicjn1a -n 100 pdloginit -d sys -s dic -f /sysarea/dicjn2a -n 100 pdloginit -d sys -s dic -f /sysarea/dicjn3a -n 100 pdfmkfs -r -n 5 -l 100 -k SVR -e 100 -i /dbarea

• Example of output log file (corresponding to the host where the system manager is not located)
  

  PDDIR="/HiRDB" PDCONFPATH="${PDDIR}/conf" SHLIB_PATH="${PDDIR}/lib" PATH="${PDDIR}/bin:${PATH}" pdfmkfs -r -n 56 -l 100 -k SVR -e 100 -i /sysarea . . . pdfmkfs -r -n 5 -l 100 -k SVR -e 100 -i /dbarea