create rdarea statement

This section explains the operands of the create rdarea statement. In the following table, each number corresponds to the number assigned to each operand.

No.	Operand
1	create rdarea RDAREA-name
2	[globalbuffer global-buffer-name]
3	for {registry\|LOB used by HiRDB (SQL REGISTRY)}
4	[page page-length characters]
5	[storage control segment segment-size pages]
6	[extension {use extension-segments-count segments\|nouse}]
7	file name "HiRDB file-system-area-name\HiRDB-file-name"
8	initial HiRDB-file-segments-count segments
	[file name "HiRDB file-system-area-name\HiRDB-file-name"
	initial HiRDB-file-segments-count segments]...
	;

Organization of this subsection: (1) RDAREA-name; (2) globalbuffer global-buffer-name; (3) for {registry |LOB used by HiRDB (SQL_REGISTRY)}; (4) page page-length characters; (5) storage control segment segment-size pages; (6) extension {use extension-segments-count segments|nouse}; (7) filename-"HiRDB-file-system-area-name\HiRDB-file-name"; (8) initial HiRDB-file-segments-count segments

(1) RDAREA-name

[Figure] <identifier> ((1-30))

Specify the name of the RDAREA to be used in the HiRDB system. ALL cannot be specified in an RDAREA name. When enclosed in double quotation marks ("), an RDAREA name is case sensitive; otherwise, it is not treated as being all in uppercase.

Examples

create rdarea "pdbuser01" for ...
In this case, the RDAREA name is treated as pdbuser01.
create rdarea pdbuser01 for ...
In this case, the RDAREA name is treated as PDBUSER01.

(2) globalbuffer global-buffer-name

[Figure] <identifier> ((1-16))

Specifies the name of a global buffer in the HiRDB system (or in the dictionary server for a HiRDB/Parallel Server) to temporarily allocate it to the RDAREA to be added. You cannot specify an index global buffer. To check the global buffer, use the pdbufls command.

Rules

This operand is required for the addition of a registry RDAREA.
The specified global buffer must have a buffer length greater than or equal to the page length of the RDAREA to be added. To check the size of global buffer, use the pdbufls command.
The global buffer length is the value specified in the -l operand of the pdbuffer statement in the system common definitions, or the maximum page length for the RDAREA to which the global buffer is assigned at the time of HiRDB startup, whichever is greater.
The specification of this operand loses effect once the HiRDB system starts normally. Therefore, you need to change the global buffer specification in the system common definitions at the next normal startup.
If you specify this operand, but the utility cannot allocate a global buffer, then an RDAREA cannot be added.

(3) for {registry |LOB used by HiRDB (SQL_REGISTRY)}

(4) page page-length characters

[Figure] <unsigned integer> ((4096-30720)) <<4096 or 8192>>

Specifies the page length of the HiRDB file comprising the RDAREA in bytes, in an integral multiple of 2048.

Registry LOB RDAREA: A value of 8192 must be specified. Even if other values are specified, 8192 is assumed.

The page length specified in this operand is used as the smallest unit of data that is input/output by the HiRDB system to or from the RDAREA.

(5) storage control segment segment-size pages

(6) extension {use extension-segments-count segments|nouse}

Specifies whether or not to apply automatic extension of RDAREA.

In the event of a space shortage in an RDAREA, the RDAREA automatic extension facility expands the RDAREA automatically if there is enough space in the HiRDB file system area. If you apply this facility to an RDAREA and a shortage of unused segments occurs, the system allocates new unused segments to the RDAREA. These new unused segments are added at the end of the HiRDB file constituting the RDAREA.

Prerequisites

You need to specify the -e option (specifying the number of extensions) for the HiRDB file system area containing the RDAREA.
There must be enough space in the HiRDB file system area that contains the last HiRDB file constituting the RDAREA.

use extension-segments-count segments

Specifies that automatic extension of RDAREA is to be applied.

In the case of a registry RDAREA, automatic extension occurs when there are no more used free segments or used segments in the RDAREA. In the case of a registry LOB RDAREA, automatic extension occurs when there are no more unused segments.

extension-segments-count <unsigned integer> ((1-64000)): Specifies the number of extension segments.

The maximum number of HiRDB file extensions is 24. If this value is exceeded, an error occurs. The maximum number of extensions per HiRDB file system area is determined by the value specified when the HiRDB file system area is created. Therefore, you need to define the maximum number of extensions, taking into account the number of files in the HiRDB file system area and the frequency of extension.

nouse: Specifies that automatic extension of RDAREA is not to be applied.

Notes

If allocation of unused segments fails due to a shortage of space in the HiRDB file system area, either you must extend or re-initialize the RDAREA or you must use the database reorganization utility to reorganize the data dictionary table.
If the number of extents exceeds the maximum value, integrate the extents in the HiRDB file system area containing the RDAREA or add HiRDB file in another HiRDB file system area to the RDAREA.
To integrate extents, make a backup copy with pdfbkup, initialize the HiRDB file system area with pdfmkfs, then restore the HiRDB file system area from its backup copy using pdfrstr.
The last file is locked from the beginning to the end of the automatic extension process.

(7) filename-"HiRDB-file-system-area-name\HiRDB-file-name"

[Figure] ((up to 167 characters))

Specifies the name of the HiRDB file system area and the name of the HiRDB file to be allocated to the RDAREA.