initialize rdarea RDAREA-name

  [with reconstruction]

  [open attribute {INITIAL|DEFER|SCHEDULE}]

  [page page-length characters]

  [storage control segment segment-size pages]

  [max entries maximum-lists-count-registered]

  [extension {use extension-segments-count segments|nouse}]

  [file name "HiRDB-file-system-area-name/HiRDB-file-name"

    initial HiRDB-file-segments-count segments]

   [file name "HiRDB-file-system-area-name/HiRDB-file-name"

    initial HiRDB-file-segments-count segments]...]

;

Specifies the name of the RDAREA that is to be reinitialized. ALL cannot be specified as an RDAREA name. If the RDAREA name is enclosed in double quotation marks ("), it is treated as being case sensitive; otherwise, it is treated as all uppercase letters. The RDAREA name must be enclosed in double quotation marks if it includes a space.

Specifies that all HiRDB files comprising the RDAREA are to be reconstructed. When this operand is specified, all the HiRDB files comprising the RDAREA to be reconstructed must be specified in file name operands. Any existing HiRDB file definitions that are not specified in file name operand definitions become invalid; HiRDB files that will no longer be used should be deleted. When this operand is omitted, the value in effect before execution of RDAREA reinitialization is inherited. To change a HiRDB file definition without specifying this operand, the name of the applicable HiRDB file must be specified in a file name operand and the new values must be specified in the applicable operands.

Specifies the RDAREA open timing.

Criteria

Normally, specify INITIAL unless a special operation mode is used.

To reduce the HiRDB startup time when there are many RDAREAs, specify DEFER.

Rules

1. This operand takes effect only when Y is specified in the pd_rdarea_open_attribute_use operand in the system common definitions.
2. This operand is applicable to user RDAREAs, user LOB RDAREAs, and list RDAREAs. This operand is ignored if specified for any other type of RDAREA (the RDAREA open timing for all other RDAREA types is INITIAL).
3. When this operand is omitted, the system assumes the value existing before the RDAREA reinitialized.
4. The value of this operand takes effect at the next startup, regardless of the HiRDB startup mode.
5. If the HiRDB file system area assigned to the corresponding RDAREA is shared by other RDAREAs, all such RDAREAs must have the same open timing. Otherwise, an expected result may not be obtained from the RDAREAs sharing the HiRDB file system area.

INITIAL

The RDAREA's HiRDB file system area is to be opened at the time of system startup and the RDAREA information is to be made resident in memory; thus, high-speed operation is available from the first SQL.

Notes

1. The RDAREA's initial status at system startup is open and remains unchanged until an operation command is executed, unless it is placed in error shutdown status due to an error.
2. The INITIAL open attribute does not permit access to a closed RDAREA.

DEFER

The RDAREA's HiRDB file system area is not to be opened at the time of system startup; rather, it is to be opened and its RDAREA information is to be made resident in memory the first time an RDAREA in the HiRDB file system area is accessed. Thus, high-speed operation is available beginning with the second access to the HiRDB file system area.

Notes

1. The RDAREA's initial status at system startup is closed and changes to open the first time an RDAREA in its HiRDB file system area is accessed. The HiRDB file system area's RDAREAs remain in open status thereafter until an operation command is executed, unless they are placed in error shutdown status due to an error.
2. The DEFER open attribute permits access to a closed RDAREA.

SCHEDULE

The RDAREA's HiRDB file system area is not to be opened at the time of system startup; rather, it is to be opened and the RDAREA information is to be made resident in memory the first time an RDAREA in the HiRDB file system area is accessed from within a transaction. When this attribute is used, transaction workload increases because a HiRDB file system area opened by a transaction is closed when the transaction terminates, and open processing must be performed on the HiRDB file system area the first time each transaction accesses one of its RDAREAs.

Notes

1. The RDAREA's initial status at system startup is closed and changes to open when the RDAREA is first accessed by a transaction. When the transaction is terminated, all the RDAREAs opened by it are closed.
   You can use the pdopen command to keep RDAREAs in open status until they are placed in shutdown close status. You can also use other operation commands to change the RDAREA status. However, if an error is detected, RDAREAs are placed in error shutdown status.
   
2. The SCHEDULE open attribute permits access to a closed RDAREA.

Specifies a multiple of 2,048 bytes if the page length for the HiRDB files that are to constitute the RDAREA is to be changed. If you specified a sector length during creation of the HiRDB file system area, specify a multiple of the sector length.

When this operand is omitted, the value in effect before execution of RDAREA reinitialization is inherited.

For a data dictionary LOB RDAREA and user LOB RDAREA, 8192 must be specified; if any other value is specified, 8192 is assumed. For details about the page lengths of other RDAREAs, see the HiRDB Version 9 Installation and Design Guide and specify the appropriate value.

The page length specified in this operand is used as the smallest unit for I/O operations performed by HiRDB on the RDAREA.

Rules

1. If an RDAREA to be reinitialized includes a table, if you reduce the page length, the table row may not fit (in which case an error occurs during data storage).
2. If the RDAREA includes a FIX table, an error results if the following value is smaller than the row length (you can check the row length by retrieving ROW_LENGTH from SQL_TABLES in the data dictionary table):
   (page length after modification 1,000) 1,000
   
3. An error results if the specified page length is greater than the maximum page length for RDAREAs assigned to the global buffer.
4. If the RDAREA to be re-initialized has an index, an error results if the key length of the index obtained from the specified page size is greater than the following value:
   MIN (page size of RDAREA/2 - 1,242, 4,036)
   (bytes)
   

Specifies a new segment size (number of pages) for the RDAREA.

When this operand is omitted, the value in effect before execution of RDAREA reinitialization is inherited.

For a data dictionary LOB RDAREA or user LOB RDAREA, 1 must be specified; if any other value is specified, 1 is assumed. For details about the segment sizes of other RDAREAs, see the HiRDB Version 9 Installation and Design Guide and specify the appropriate value.

Specifies the maximum number of lists that can be created in the list RDAREA, expressed as a multiple of 500. If the specified value is not a multiple of 500, the system rounds it up to the next multiple of 500.

When this operand is omitted, the value in effect before execution of RDAREA reinitialization is inherited.

An error results if you specify this operand for any RDAREA other than the list RDAREA.

Specifies whether or not to apply automatic extension to the RDAREA that is being reinitialized. When this operand is omitted, the value in effect before execution of RDAREA reinitialization is inherited.

For details about RDAREA automatic extension, see the HiRDB Version 9 System Operation Guide.

Prerequisites

You must specify the -e or -a option for the HiRDB file system area containing the RDAREA.

use extension-segments-count segments

Specifies that automatic extension of RDAREA is to be applied.

The automatic extension of RDAREA is applicable to data dictionary RDAREAs, data dictionary LOB RDAREAs, user RDAREAs, and user LOB RDAREAs. For any other type of RDAREA, the system assumes nouse, even if use is specified.

Automatic extension occurs when the number of free segments in an RDAREA reaches the automatic extension timing. You specify the timing value in the pd_rdarea_extension_timing operand.

extension-segments-count ~<unsigned integer> ((1-64000))

Specifies the number of extension segments.

• For a HiRDB file system area for which pdfmkfs -e is specified
  The maximum number of HiRDB file extensions is 24. If this value is exceeded, an error occurs. An error occurs if a shortage of space occurs in the HiRDB file system area or the required area exceeds the maximum size for a HiRDB file.
  The maximum number of extensions per HiRDB file system area is determined by a value specified when the HiRDB file system area was created. Therefore, when you define the maximum number of extensions, you need to take into account the number of files in the HiRDB file system area and the frequency of extension.
  
• For a HiRDB file system area for which pdfmkfs -a is specified
  An error occurs if there is not enough space on the disk containing the HiRDB file to allocate the required HiRDB file system area or the required area exceeds the maximum size for a HiRDB file.
  

nouse

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

Notes

1. New unused segments are added to the last HiRDB file constituting the RDAREA.
2. If allocation of unused segments fails due to a shortage of space in the HiRDB file system area, either extend or re-initialize the RDAREA or use the database reorganization utility to reorganize the table.
3. If the number of extensions exceeds the maximum value, integrate the extensions in the HiRDB file system area containing the RDAREA or add a HiRDB file in another HiRDB file system area to the RDAREA.
   To integrate extensions, 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.
   
4. The last file is locked from the beginning to the end of the automatic extension process.

Specifies a file that is to comprise the reinitialized RDAREA, in terms of a HiRDB file system area name and a HiRDB file name. HiRDB-file-system-area-name/HiRDB-file-name must be enclosed in double quotation marks.

Rules

1. When this operand is omitted, the value in effect before execution of RDAREA reinitialization is inherited.
2. Do not include a linefeed character inside the double quotation marks.
3. You can allocate a maximum of 16 HiRDB files per RDAREA.
4. The database structure modification utility (pdmod) creates the HiRDB file in the specified HiRDB file system area. If the HiRDB file system area already contains a HiRDB file, pdmod deletes it and then creates a new file; therefore, an error results if there are no HiRDB file privileges.
5. HiRDB-file-system-area-name/HiRDB-file-name must be unique in the HiRDB system.
6. For a list RDAREA, use a HiRDB file system area with a purpose of WORK.

HiRDB-file-system-area-name~<pathname>

Specifies the name of the HiRDB file system area.

HiRDB-filename~<HiRDB filename> ((1-30 characters))

Specifies the name of the HiRDB file (which cannot begin with pl).

Specifies the number of segments in this file in the RDAREA.

When this operand is omitted, the value in effect before execution of RDAREA reinitialization is inherited.

To determine the number of segments, use the formula total number of pages in the data page section segment size. For details about the formula for determining the total number of pages in the data page section, see the HiRDB Version 9 Installation and Design Guide. The size of a HiRDB file cannot exceed 2 GB, regardless of the number of segments.