2.3.20 Operands related to RDAREAs

104) pd_max_rdarea_no = maximum-number-of-RDAREAs
[Figure]<unsigned integer>((5-8388592)) <<200>>
Specifies the maximum number of RDAREAs allowed. If the total number of RDAREAs exceeds the value specified for this operand, HiRDB cannot be started normally. Here, RDAREAs also include master directory RDAREAs, data directory RDAREAs, and data dictionary RDAREAs.
Specification guidelines
  • Specify a value that is equal to or greater than the total number of RDAREAs (leave some extra room). You can use the pddbls command to check the total number of RDAREAs. If you plan to add RDAREAs, specify a value by taking the additional RDAREAs into account.
  • For a HiRDB/Parallel Server, the value of this operand is applied to each back-end server. For example, if 100 is specified for this operand, a maximum of 100 RDAREAs can be created in each back-end server. Therefore, use the largest number of RDAREAs among the back-end servers as the guideline when specifying a value for this operand.
  • If you are using shared RDAREAs, also add the number of shared RDAREAs used by reference-only back-end servers.
Notes
  • Do not specify an unnecessarily large value for this operand. Increasing the specification value of this operand increases the size of the shared memory used by HiRDB. If a shortage occurs in the shared memory, HiRDB may not be able to start.
105) pd_max_file_no = maximum-number-of-HiRDB-files-comprising-an-RDAREA
[Figure]<unsigned integer>((5-134217728)) <<400>>
Specifies the maximum number of HiRDB files that comprise an RDAREA. If the total number of HiRDB files exceeds the value specified for this operand, HiRDB cannot be started normally. Here, HiRDB files comprising an RDAREA also include the HiRDB files of master directory RDAREAs, data directory RDAREAs, and data dictionary RDAREAs.
Specification guidelines
  • Specify a value that is equal to or greater than the total number of HiRDB files comprising an RDAREA (leave some extra room). You can use the pdfstatfs command to check the number of HiRDB files inside each HiRDB file system area. If you plan to add HiRDB files, specify a value by taking them into account. HiRDB files are added when RDAREAs are added, reinitialized, or extended.
  • For a HiRDB/Parallel Server, the value of this operand is applied to each back-end server. For example, if 100 is specified for this operand, a maximum of 100 HiRDB files can be created in each back-end server. Therefore, use the largest number of HiRDB files among the back-end servers as the guideline when specifying a value for this operand.
  • If you are using shared RDAREAs, also add the number of HiRDB files comprising the shared RDAREAs used by reference-only back-end servers.
Notes
  • Do not specify an unnecessarily large value for this operand. Increasing the specification value of this operand increases the size of the shared memory used by HiRDB. If a shortage occurs in the shared memory, HiRDB may not be able to start.
106) pd_rdarea_warning_point = segment-usage-ratio-1[,segment-usage-ratio-2[,segment-usage-ratio-3]]
[Figure]<unsigned integer>((0-100))(%)
Specifies as percentages triggers for issuing a warning message (KFPH00211-I or KFPA12300-I) about RDAREA segment usage.
The following table shows the relationship between whether or not this operand is specified and the segment usage ratio warning message for the different types of RDAREAs.
RDAREA typepd_rdarea_warning_point not specifiedpd_rdarea_warning_point specified
  • Master directory RDAREA
  • Data directory RDAREA
No message is output.Segment use has started that makes the segment usage ratio equal to the value specified for all segments of the applicable RDAREA.
  • Data dictionary RDAREA
  • User RDAREA
Segment use has started that makes the segment usage ratio 80%, 90%, or 100% in terms of the relative position of the segment in the last file of the applicable RDAREA.Segment use has started that makes the segment usage ratio equal to the value specified for all segments of the applicable RDAREA.
  • LOB RDAREA
Segment use has started that makes the segment usage ratio 80%, 90%, or 100% in terms of the relative position of the segment in the last file of the applicable RDAREA.Segment use has started that makes the segment usage ratio equal to the value specified for all segments of the applicable RDAREA.
The following table shows specification examples of this operand:
Message output conditionOperand specification value
To output a message when segment use has started that makes the segment usage ratio 80%, 90%, or 100% of all the segments in the applicable RDAREApd_rdarea_warning_point = 80,90,100
To output a message when segment use has started that makes the segment usage ratio 50% or 90% of all the segments in the applicable RDAREApd_rdarea_warning_point = 50,90
To not output a segment usage warning messagepd_rdarea_warning_point = 0
Operand rules
  • Up to three values may be specified.
  • When the same value is specified more than once, only one message will be output for that value.
  • When 0 is specified for all three values, no segment usage warning message is output.
  • When 0 and a non-zero numeric value are both specified, the non-zero numeric value is used as the trigger for message output.
Note
Specification of this operand is not applicable to the database initialization utility (pdinit) or the database recovery utility (pdrstr).The message content is the same regardless of whether or not this operand is specified.
107) pd_rdarea_open_attribute_use = Y | N
Specifies whether to use the DEFER or SCHEDULE attribute as the RDAREA opening trigger.
Y: Uses the DEFER or SCHEDULE attribute.
N: Does not use the DEFER or SCHEDULE attribute.
When this operand is omitted or when N is specified, the RDAREA opening trigger attribute is always INITIAL. Therefore, even if the DEFER or SCHEDULE attribute is specified as the RDAREA opening trigger in the operand or utility described as follows, the specification is invalid.
  • pd_rdarea_open_attribute
  • Database initialization utility
  • Database structure modification utility
Notes
  • When Y is specified, HiRDB requires a larger shared memory. Consequently, a shared memory shortage may occur, preventing the HiRDB system from starting.
  • If the rapid system switchover facility, standby-less system switchover (1:1) facility or standby-less system switchover (effects distributed) facility is used, Y is assumed for this operand. Because the size of the shared memory used by the server increases as a result, re-estimate the shared memory size. For the formula for estimating the size of the shared memory used by a server, see the HiRDB Version 8 Installation and Design Guide.
108) pd_rdarea_open_attribute = INITIAL | DEFER | SCHEDULE
Specifies the standard value for the RDAREA opening trigger attribute.
The attribute specified by this operand is assumed for RDAREAs for which open attribute is not specified by the database initialization utility or the database structure modification utility.
For System RDAREAs, INITIAL is always assumed.
Specification guidelines
  • The same attribute should be specified for the RDAREAs in the same HiRDB file system area. If different attributes are specified, the expected result may not be obtained.
  • The following table lists the opening/closing triggers for each attribute and their advantages and disadvantages.
    AttributeInitial statusOpening triggerClosing triggerAdvantageDisadvantage
    INITIALOpen
    • HiRDB startup
    • pdopen command execution
    pdclose command executionFast execution from the first SQL.System startup takes time.
    DEFERClosed
    • Initial access to RDAREA
    • pdopen command execution
    pdclose command execution
    • Fast system startup.
    • Regular SQLs are executed at high-speed, as well as after the initial access.
    First access to each RDAREA takes time.
    SCHEDULEClosed
    • Initial RDAREA access inside transaction
    • pdopen command execution
    • Transaction termination
    • pdclose command execution
    • Fast system startup.
    • Avoids concentrated file opening.
    • Initial access to RDAREA results in high workload for a transaction.
  • The following table shows the operation mode appropriate to each attribute:
    AttributeAppropriate operation mode
    INITIALHiRDB file system area is opened at system startup and keeps the RDAREA information resident in the memory. The HiRDB file system area is opened also during the initial RDAREA access. Because the RDAREA information is not re-created in this case, high-speed operation can be performed from the first SQL.
    The initial status of the RDAREA at system startup is open, and this RDAREA status will not change unless an operation command is entered subsequently, except during shift to an error shutdown.
    This attribute is recommended unless an unusual operation mode is used.
    When this attribute is used, a closed RDAREA cannot be accessed.
    DEFERHiRDB file system area is not opened at system startup. Instead, the HiRDB file system area is opened during the initial RDAREA access and the RDAREA information is kept resident in the memory. In the second and subsequent accesses, the processing beyond opening of the HiRDB file system area is not performed, and thus high-speed operations can be achieved.
    The initial status of the RDAREA at system startup is closed, and each RDAREA is opened during the initial access to that RDAREA. The RDAREA status will not change unless an operation command is entered subsequently, except during a shift to an error shutdown.
    Specify this attribute if you want to avoid cases in which a large number of HiRDB file system areas are opened concurrently or if you want to shorten the time required for starting HiRDB.
    When HiRDB is restarted, the RDAREAs to be recovered are opened during recovery processing.
    When this attribute is used, a closed RDAREA can also be accessed.
    SCHEDULEHiRDB file system area is not opened at system startup. Instead, after HiRDB startup, the HiRDB file system area is opened during the initial RDAREA access in each transaction and the RDAREA information is kept resident in the memory. When a transaction terminates, the HiRDB file system area opened in that transaction is closed. Thereafter, the processing beyond opening will also be performed during the initial access to an RDAREA whenever the transaction is changed, and thus the workload required for transactions will increase.
    The initial status of the RDAREA at system startup is closed, and the RDAREA is kept open only during the transaction for the accessed RDAREA. When a transaction terminates, all RDAREAs that were opened in the transaction are closed.
    If the pdopen command is entered, these RDAREAs can be kept open until they are closed by the next shutdown. It is also possible to use other operation commands to change the status of the RDAREAs. If an error is detected, an error shutdown occurs.
    This attribute should be specified when it is necessary to compensate for many HiRDB file system areas being opened simultaneously or when it is necessary to reduce the HiRDB system startup time.
    When HiRDB is restarted, the RDAREAs to be recovered are opened during recovery processing and closed after the completion of the recovery processing.
    When this attribute is used, a closed RDAREA can also be accessed.
Note
The following table describes the notes related to the use of the rapid system switchover facility, standby-less system switchover (1:1) facility, and standby-less system switchover (effects distributed) facility.
Facility usedNotes
Rapid system switchover facilityA standby unit that is targeted by the rapid system switchover facility has not opened RDAREAs while it is in a standby state. Furthermore, to minimize the time required for system switchover, the standby unit opens only those RDAREAs that are necessary for full recovery when system switchover occurs, and does not open other RDAREAs. Therefore, the RDAREA opening trigger for the standby system cannot be INITIAL. The INITIAL attribute of RDAREAs is changed to DEFER.
Standby-less system switchover (1:1) facilityTo minimize the time required for system switchover, the standby-less system switchover (1:1) facility opens only those RDAREAs that are necessary for full recovery when system switchover occurs, and does not open other RDAREAs. Therefore, the opening trigger for the RDAREAs in the normal BES or alternate portion is as follows:
  • When system switchover occurs, the opening trigger for the RDAREAs in the alternate portion is SCHEDULE.
  • When the error is corrected and the system switches back to the normal BES, the opening trigger for RDAREAs with the INITIAL or DEFER attribute under the normal BES is changed to DEFER. RDAREAs with the SCHEDULE attribute retain this attribute.
Standby-less system switchover (effects distributed) facilityTo minimize the time required for system switchover, the standby-less system switchover (effects distributed) facility opens only those RDAREAs that are necessary for full recovery when system switchover occurs, and does not open other RDAREAs. Therefore, when system switchover occurs, the opening trigger for RDAREAs with the INITIAL attribute under the guest BES is changed to DEFER.
The following table shows the relationships between the opening trigger for RDAREAs and the rapid system switchover facility, standby-less system switchover (1:1) facility, and standby-less system switchover (effects distributed) facility.
Conditionpd_rdarea_open_attribute_use specification value
NY
RDAREA opening trigger
INITIALDEFERSCHEDULE
System switchover facility not used1INITIALINITIALDEFERSCHEDULE
Standby system switchover facility1Rapid system switchover facility not used
Rapid system switchover facilityRunning system
Standby systemDEFER2DEFERDEFERSCHEDULE
Standby-less system switchover (1:1) facility1Accepting portion (other than the alternate portion of the alternate BES unit)Running systemINITIAL2, 3INITIAL3DEFERSCHEDULE
Standby systemDEFER2DEFERDEFERSCHEDULE
Alternate portionRunning systemSCHEDULE2SCHEDULESCHEDULESCHEDULE
Standby system
Standby-less system switchover (effects distributed) facility1Normal start or restartINITIALINITIALDEFERSCHEDULE
Restart due to system switchoverDEFER2DEFERDEFERSCHEDULE
1 The opening trigger for the System RDAREA is INITIAL.
2 It is assumed that pd_rdarea_open_attribute_use = Y is specified.
3 Changed to DEFER after a restart.
109) pd_shared_rdarea_use = Y | N
This operand applies only to a HiRDB/Parallel Server.
Specifies whether to use a shared RDAREA.
Y:
A shared RDAREA is used.
N:
A shared RDAREA is not used.
Notes
  • If you omit this operand (or specify N for it) even though a shared RDAREA has been defined, HiRDB cannot be normally started.
  • Specifying Y for this operand allocates the same shared memory block as that allocated when commit is specified for the pd_dbsync_point operand.