Executor: HiRDB administrator

The following table lists the operands that can be specified for use of the security audit facility.

Table 24-11 Operands specified for using the security audit facility

Operand	Explanation
pd_audit	Specifies whether collection of an audit trail is to start from the time HiRDB starts: Y: Collect an audit trail from the time of HiRDB startup. N: Do not start collecting an audit trail at the time HiRDB starts. Even if N is specified in this operand, an audit trail can be collected by executing the pdaudbegin command. If Y is specified in the pd_audit operand, or if the pdaudbegin command is executed, audit trails for the following events are collected unconditionally: System administrator security events Auditor security events For other events, use CREATE AUDIT to specify whether an audit trail is to be collected. For details, see 24.4.4 Audit event definition.
pd_aud_file_name	Specifies the HiRDB file system area to be used for the audit trail files. HiRDB creates the audit trail files in this HiRDB file system area. This operand must be specified when the security audit facility is used. If it is not specified, the security audit facility cannot be used. When this operand is specified, HiRDB will not start if an access error occurs in the HiRDB file system area for the audit trail files during startup of HiRDB (or unit for a HiRDB parallel server configuration). When you are using the security audit facility in a HiRDB parallel server configuration, we recommend that you acquire audit trails from the entire system. To acquire audit trails from the entire system, specify one of the following: Specify the pd_aud_file_name operand in the system common definition. Specify the pd_aud_file_name operand in all unit control information definitions. However, in a system configuration in which multiple units run on the same server machine, you must specify the pd_aud_file_name operand in all unit control information definitions.
pd_aud_max_generation_size	Specifies the maximum size of an audit trail file.
pd_aud_max_generation_num#	Specifies the maximum number of audit trail file generations to be created in the HiRDB file system area for audit trail files.
pd_aud_no_standby_file_opr	Specifies the processing when there are no available swappable audit trail files, or when all sectors of the asynchronous output buffer are placed in flush-wait status. forcewrite (default): When there are no swappable audit trail files available, a data load waiting audit trail file (excluding files in shutdown status) is to be forcibly made the swap target so that audit trail output will continue. For details about the status of audit trail files, see 24.6 Operation of audit trail files. When 180 seconds have passed since all sectors of the asynchronous output buffer were placed in flush-wait status, audit trail output is continued by forcibly overwriting and reusing the first asynchronous output buffer that was placed in flush-wait status. The audit trail in the overwritten asynchronous output buffer is discarded. down: When the remaining number of swappable audit trail files falls to 1, or when 180 seconds have passed since all sectors of the asynchronous output buffer were placed in flush-wait status, HiRDB (a unit in the case of a HiRDB parallel server configuration) is forcibly terminated.
pd_aud_async_buff_size	Specifies the buffer length to be used when the audit trail is output asynchronously.
pd_aud_async_buff_count	Specifies the number of buffers to be used when the audit trail is output asynchronously.
pd_aud_async_buff_retry_intvl	Specifies the interval at which buffer monitoring is to be retried until an unused buffer is allocated when all the buffers used for asynchronous output of an audit trail are in use.
pd_aud_file_wrn_pnt	Specifies that a warning message is to be output when the number of unswappable audit trail files reaches a warning level. Specify for the warning value a value that is less than the maximum number of audit trail file generations specified in the pd_aud_max_generation_num operand.
pd_aud_auto_loading	Specifies whether to use the facility for automatically loading audit trail table data. Y: Uses the facility for automatically loading audit trail table data. In this case, data is automatically loaded to the audit trail table when the audit trail file is swapped (except when swapping occurs because of an error). N: Does not use the facility for automatically loading audit trail table data. In this case, data is not automatically loaded to the audit trail table. The auditor must manually load data. When you specify Y for this operand in a HiRDB parallel server configuration, you need to create a HiRDB file system area for audit trail files in the unit in which the system manager is located, and you must specify the pd_aud_file_name operand. If this operand is not specified, the facility for automatically loading audit trail table data cannot be used.
pdaudload	If the operating method satisfies one of the conditions listed below when you use the facility for automatically loading audit trail table data, you must change the pdload option in the pdaudload command. For details about the pdaudload command, see the manual HiRDB Version 9 System Definition. Real Time SAN Replication in the log-only synchronous method is applied. Change the log acquisition method to the log acquisition mode. The RDAREA storing the audit trail table is not to be backed up. Change the log acquisition method to the log acquisition mode. Indexes are defined in the audit trail table and data is loaded in the batch index creation mode. Change the index creation method to the batch index creation mode. Data is loaded using a local buffer. Specify a local buffer sector count.

#: Specify the value of the pd_aud_max_generation_num operand so that it satisfies the following condition:

• Value of pd_aud_max_generation_num < value of pdfmkfs command's -l option

The -l option specifies the maximum number of files to be created in the HiRDB file system area used for the audit trail files, which is discussed later. If the value of the operand is specified so that this condition is satisfied, then if swappable files cannot be prepared immediately, you will be able to increase the value of the pd_aud_max_generation_num operand. The following figure shows the recommended specification.

Figure 24-4 Recommended relationship between the value of pd_aud_max_generation_num and the -l option