The pdfmkfs command initializes a specified file as a HiRDB file system area.
HiRDB administrator
pdfmkfs -n HiRDB-file-system-area-size [-l max-files-count] |
Specifies, in megabytes, the space to be allocated as the HiRDB file system area. Specification of this option is mandatory.
pd_large_file_use operand in system definition | File type | Value range |
---|---|---|
N | File (NTFS) | 1-2,047 |
Direct disk access (raw I/O) | 1-2,047 | |
Y (or omitted) | File (NTFS) | 1-1,048,575 |
Direct disk access (raw I/O) | 1-1,048,575 |
If you are using a file (NTFS) with a size greater than 100 gigabytes, specify Y in the pd_ntfs_cache_disable operand in the system definition to avoid a shortage of OS resources. Also make sure that HiRDB files for LOB RDAREAs are not intermixed with HiRDB files for RDAREAs.
If you specify this option together with -k DB -a, -k SDB -a, -k SYS -a, or -k WORK -a, the HiRDB file system area will be extended automatically when the area is used up.
The management area used for management of a HiRDB file system area is also included in the value of the -n option. Therefore, the actual size allocated to the HiRDB file is (value of the -n option) - (size of management area). For details about determining the size of the management area, see (7) Notes. You can use the pdfstatfs command to check the actual size that is allocated to the HiRDB file.
Specifies the maximum number of HiRDB files that can be created in the allocated HiRDB file system area.
The fewer HiRDB files there are in the area, the better the performance will be.
If you omit the -a option, you must specify this option.
Once you execute the pdfmkfs command, you can no longer change this value. Therefore, carefully determine this value taking into account the number of HiRDB files to be used and future expansion plans. For the formula for determining the maximum number of files, see Determining the maximum number of files (pdfmkfs -l command) in the HiRDB Version 9 Installation and Design Guide.
This option cannot be specified together with -k DB -a, -k SDB -a, or -k SYS -a.
Specifies the purpose for which the HiRDB file system area will be used:
Specifies a maximum number of extensions (maximum number of times file extension can be performed). When this option is specified and a shortage of space occurs in a HiRDB file, that file's capacity will be extended automatically.
The specified number of extensions applies cumulatively to all HiRDB files in the HiRDB file system area. For example, if a HiRDB file system area contains two HiRDB files that have been extended 5 times and 3 times, respectively, then the total number of extensions so far is 8.
The maximum number of permissible extensions for one HiRDB file is 23. If the specified value equals or exceeds maximum number of files (value of the -l option) 23, the command ignores the specified value and assumes maximum number of files
23 as the maximum number of extensions. If a file area can contain only one file (1 is specified in the -l option), the limitation to 23 extensions is not applied. When 1 is specified as the maximum number of extensions, file data will not be fragmented by extensions, and the file can be extended up to the size of the HiRDB file system area (value of the -n option). Note that a file cannot exceed the maximum size of an HiRDB file area.
This option cannot be specified together with -k DB -a, -k SDB -a, or -k SYS -a.
-k option | Number of extensions to be specified |
---|---|
DB#1 | Min(60,000, 23 ![]() If you frequently perform deletion, re-initialization (for reduction of allocation size or with with reconstruction specified), or integration of RDAREAs, use the following value: Min(60,000, 23 ![]() |
SDB#1 | |
SYS#1 | 0 |
WORK | Min(60,000, 23 ![]() |
UTL | |
NUTL | |
SVR | Min(60,000, 23 ![]() Extension is applied to work table files and final files in the RDAREA subject to extension.#2 |
If you are using the HiRDB file system area with a device that handles a medium with a physical sector length of 2,048 and 4,096 bytes, such as DVD-RAM device, this option specifies the minimum I/O unit expressed as the sector length. For details about the physical sector length of a medium, see the manual for the medium.
Specifies that the HiRDB file system area specified in the -n option is to be initialized from the beginning. If you specify the -a option to automatically extend the HiRDB file system area, whether the extended area is initialized depends on the file type and the specified -k option value. For details, see the description of the -a option.
When the -i option is omitted, the command creates only the management information for the HiRDB file system area (an area with a maximum size of about 3.5 megabytes is allocated). The HiRDB file system area will be extended up to the size specified with the -n option when it is actually used.
If the HDP facility is not used with direct disk access (raw I/O), a shortage of disk capacity will not occur because an area of the size specified with the -n option is guaranteed.
If you are creating a HiRDB file system area that will be used by the system switchover facility, specify the -i option. If the -i option is omitted and extension of the HiRDB file system area and a power failure on the server machine both occur at the same time, files might become corrupted.
Specifies that no confirmation message is to be displayed when the file is initialized. If this option is omitted and the specified regular file already exists, the command displays a confirmation message asking whether or not to initialize the file. If a letter other than g is entered in response to the confirmation message, the command will not initialize the file.
If you are using direct disk access (raw I/O), you cannot specify the -r option (in which case no confirmation message is displayed).
Specifies that the HiRDB file system area is to be extended automatically when a space shortage occurs due to execution of SQL statements that use automatic extension of RDAREAs and work tables. When this option is specified and the size of a HiRDB file system area reaches the value specified in the -n option, that file system area is extended automatically. You also specify this option in order to create a HiRDB file system area for the system log files to which the system log file automatic extension facility is applied. For details about the facilities for RDAREA automatic extension and system log file automatic extension, see the HiRDB Version 9 System Operation Guide.
The table below shows whether an automatically extended HiRDB file system area is initialized.
Table 2-2 Whether an automatically extended HiRDB file system area is initialized
No. | File type | -k option value | pd_rdarea_expand_format operand value# | Whether extended area is initialized |
---|---|---|---|---|
1 | File (NTFS) | DB or SDB | Y | Y |
2 | N | N | ||
3 | WORK | -- | N | |
4 | SYS | Y | ||
5 | Direct disk access (raw I/O) | DB or SDB | -- | N |
6 | WORK | |||
7 | SYS |
Table 2-3 Maximum sizes of HiRDB file system areas
-k option value | Maximum size of HiRDB file system area (MB) |
---|---|
DB | 65,536 |
SDB | |
SYS | 102,400 |
WORK | Applicable value when Y or nothing is specified in the pd_large_file_use operand in the system definition, as shown in 2.32(4)(a) -n HiRDB-file-system-area-size |
Specifies a name for the file to be initialized. This name is used as the name of the HiRDB file system area.
You can specify a maximum of 30 characters for the name of a HiRDB file that is created in the HiRDB file system area. Note that because HiRDB-file-system-area-name\HiRDB-file-name cannot exceed 167 characters, the maximum length of an HiRDB file name is reduced accordingly if the HiRDB file system area name is greater than 136 characters.
For HiRDB files that are created automatically by HiRDB, make sure that the following maximum lengths for HiRDB file system area names are not exceeded:
HiRDB file created automatically by HiRDB | Maximum length of HiRDB file system area name (in characters) |
---|---|
Work table file (specified with pdwork operand in system definition) | 141 |
Audit trail file (specified with pd_aud_file_name operand in system definition) | 150 |
Index information file for delayed batch creation of plug-in index (specified with pd_plugin_ixmk_dir operand in system definition) | 136 |
Unload log file for system log for the automatic log unloading facility (specified with pd_log_auto_unload_path operand in system definition) | 136 |
A management area is allocated to the HiRDB file system area. The size of the management area to be allocated depends on the type of OS, the -n, -l, -e, and -s options, and the type of files to be used. The formulas for determining the size of a management area are presented below. Note that the sizes of the fixed and variable management sections may increase depending on the process because they are read into memory while the corresponding HiRDB file system area is used.
Management area (bytes)
= Fixed management section + variable management section + HiRDB file management section a
Table 2-4 Size of management area to be allocated (when -k DB, -k SDB, or -k SYS is specified)
File type | Sector length (-s option value) | Size of management area (KB) |
---|---|---|
Regular file | 512 | 5.5 |
Direct disk access (raw I/O) | 1024 | 7 |
2048 | 10 | |
4096 | 16 |
Initialize the following HiRDB file system areas:
pdfmkfs -n 25 .......................1
-l 10 .......................2
-e 5 ........................3
c:\sysarea\rdsys011 .........4