When a HiRDB system is created by the system generator (g specified on the Master menu), the initialization commands are output to a 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-2 lists the contents of the log file.
Table 4-2 Contents of the log file
Item | Description |
---|
Output destination | $PDDIR/conf |
Type | Regular file (UNIX file) |
Name | pdgen_cmd."name-of-host-where-unit-was-created" |
Access privileges | User who executed pdgen has reference and update privileges. Other users have reference privileges only. |
Output information | - Contents of environment variables during creation (PDDIR, PDCONFPATH, SHLIB_PATH*, 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)
|
- * The environment variable is LD_LIBRARY_PATH for Solaris and Linux and LIBPATH for AIX 5L.
Following is an example of log file output:
PDDIR="/HiRDB"
PDCONFPATH="${PDDIR}/conf"
SHLIB_PATH="${PDDIR}/lib"
PATH="${PDDIR}/bin:${PATH}"
pdfmkfs -r -n 20 -l 100 -k SVR -e 100 -i /sysarea
pdstsinit -u SDSU -f /sysarea/SDSUst1a -c 32
pdstsinit -u SDSU -f /sysarea/SDSUst1b -c 32
pdstsinit -u SDSU -f /sysarea/SDSUst2a -c 32
pdstsinit -u SDSU -f /sysarea/SDSUst2b -c 32
.
.
.
pdloginit -d sys -s sds1 -f /sysarea/sds1jn1a -n 384
pdloginit -d sys -s sds1 -f /sysarea/sds1jn2a -n 384
pdloginit -d sys -s sds1 -f /sysarea/sds1jn3a -n 384
pdfmkfs -r -n 5 -l 100 -k SVR -e 100 -I /dbarea |