Nonstop Database, HiRDB Version 9 System Definition

[Contents][Index][Back][Next]

2.2.11 Operands related to system monitoring

47) pd_utl_exec_time = utility-execution-monitoring-time
~<unsigned integer>((0-35791394)) (minutes)
Specifies the monitoring time (in minutes) for monitoring the execution time of the following utilities:
  • Database load utility (pdload command)
  • Database reorganization utility (pdrorg command)
  • Free page release utility (pdreclaim command)
  • Global buffer residence utility (pdpgbfon command)
If the execution of a utility is not terminated within the monitoring time specified by this operand, the executing utility is forcibly terminated, and the error information for identifying the cause of no response is output as shown in the following table.
Error information obtained Output destination

  • Core files
  • .deb files
  • .ext.deb files
 These files are output in $PDDIR/spool/save of the server machine on which the utility was running.

  • pdls -d rpc -a command execution result
  • pdls -d lck command execution result
 These results are output to the directory specified by the pd_tmp_directory operand of the server machine from which the utility command was entered. If the pd_tmp_directory operand is omitted, these results are output to the directory specified in the TMPDIR# environment variable. If the TMPDIR# environment variable is also omitted, they are output in /tmp.
However, if the HiRDB administrator executes the command, these results are also output in $PDDIR/spool/save. The file names are as follows:
command-nameYYYYMMDDHHMMSSpid.txt
  • pid is a process ID.
  • If the pdreclaim or pdpgbfon command is executed, HiRDB internally executes the pdrorg command, and therefore pdrorg is used as the command name to be assigned to the file name.
#: This environment variable is set in the process server process (pdprcd) started from init (an OS process).
Advantage
Even if a utility ceases to respond because of an error (communication or disk error, for example) that occurs during utility execution in a nighttime batch job, the succeeding jobs can continue running.
Specification guidelines
  • This operand is designed to deal with no-response errors, and not to monitor for large transactions. Therefore, specify a value for this operand that is somewhat greater than the actual maximum execution time of utilities. For example, if the maximum execution time of the database load utility is approximately 60 minutes, and the maximum execution time of the database reorganization utility is approximately 90 minutes, specify pd_utl_exec_time=120 by leaving some room. In this case, when a process that is normally terminated in 90 minutes does not return a response even after 30 more minutes, it is determined that a no-response error has occurred.
  • If the utility execution time is not monitored and one of the errors below occurs, a utility might go into a no-response state. Therefore, specify a value other than 0.
    [Figure] Communication error (including temporary error) between servers
    [Figure] Process not responding due to a disk error, for example
Operand rules
  • If you omit this operand, the value specified for the pd_cmd_exec_time operand in the system common definition takes effect. If the pd_cmd_exec_time operand is also omitted, 0 is assumed.
  • If 0 is specified for this operand, the utility execution time is not monitored.
  • If monitoring time is specified in the exectime operand of the option control statement of each utility, the specification in the exectime operand takes precedence.
Relationship to other operands
  • This operand is related to the pd_cmd_exec_time operand.

48) pd_cmd_exec_time = period-for-monitoring-the-execution-time-of-operation-commands-and-utilities
~<unsigned integer> ((0-3600))<<0>> (minutes)
An operation command or utility might go into a no-response state if a communication error occurs, if the CPU usage rate becomes high, or if no disk I/O response is returned. To prevent operation commands or utilities from going into an unlimited no-response state, specify this operand.
The table below shows the operation commands and utilities whose execution time can be monitored by this operand. The number of operation commands and utilities targeted by this operand is greater than the number of operation commands and utilities targeted by the pd_utl_exec_time operand in the system common definitions. When the execution time is being monitored, the messages in the table below are output at the start and end of monitoring. In addition, if an operation command or utility does not finish even though the monitoring period elapsed after a monitoring start message was output, a timeout detection message is output and then the running operation command or utility is forcibly terminated.

Table 2-1 TableOperation commands and utilities targeted by the pd_cmd_exec_time operand

No. Operation command or utility Monitoring start message Monitoring end message Timeout detection message Timeout detection abort code
1 pdacunlck KFPD00041-I KFPD00042-I KFPD00043-E Pd00009
2 pdbufls KFPH27067-I KFPH27068-I KFPH27069-E Phu0009
3 pdbufmod KFPH27067-I KFPH27068-I KFPH27069-E Phu0009
4 pdclose KFPH27067-I KFPH27068-I KFPH27069-E Phu0009
5 pdcopy KFPR26092-I KFPR26093-I KFPR26091-E Pra0001
6 pddbchg KFPH27067-I KFPH27068-I KFPH27069-E Phu0009
7 pddbfrz KFPH27067-I KFPH27068-I KFPH27069-E Phu0009
8 pddbls KFPH27067-I KFPH27068-I KFPH27069-E Phu0009
9 pddbst KFPK10452-I KFPK10453-I KFPK10021-E Pu02004
10 pdexp KFPX28414-I KFPX28415-I KFPX28416-E Pu02004
11 pdgetcst KFPN00500-I KFPN00501-I KFPN00502-E Pu02004
12 pdhold KFPH27067-I KFPH27068-I KFPH27069-E Phu0009
13 pdlistls KFPD00041-I KFPD00042-I KFPD00043-E Pd00009
14 pdload KFPL00901-I KFPL00902-I KFPL24511-E Pu02004
15 pdmemdb KFPH27067-I KFPH27068-I KFPH27069-E Phu0009
16 pdmod KFPS05629-I KFPS05630-I KFPS05631-E Pscm271
17 pdopen KFPH27067-I KFPH27068-I KFPH27069-E Phu0009
18 pdorbegin KFPH27067-I KFPH27068-I KFPH27069-E Phu0009
19 pdorchg KFPH27067-I KFPH27068-I KFPH27069-E Phu0009
20 pdparaload KFPL00901-I KFPL00902-I KFPL24511-E Pu02004
21 pdpgbfon KFPL00901-I KFPL00902-I KFPL24511-E Pu02004
22 pdrbal KFPL00901-I KFPL00902-I KFPL24512-E Pu02004
23 pdreclaim KFPL00901-I KFPL00902-I KFPL24511-E Pu02004
24 pdrels KFPH27067-I KFPH27068-I KFPH27069-E Phu0009
25 pdrorg KFPL00901-I KFPL00902-I KFPL24511-E Pu02004
26 pdrstr KFPR26292-I KFPR26293-I KFPR26291-E Pra0001
If an operation command or utility does not finish within the time specified for this operand, a message indicating the occurrence of a timeout is output, the following error information is obtained, and then the process is forcibly terminated.
No. Obtained information Output destination
1 core file They are output to $PDDIR/spool/save, on the server that has the process used by the utility.
2 .deb files
3 .ext.deb files
Operand rules
  • If you omit this operand or set it to 0, the amount of execution time for operation commands and utilities is not monitored.
  • If the monitoring period is specified for the exectime operand in the option control statement of the utilities below, the specification of the exectime operand takes precedence. If the exectime operand is omitted and the monitoring period is specified for the pd_utl_exec_time operand in the system common definition, the specification of the pd_utl_exec_time operand takes precedence.
    - Database load utility (pdload command)
    - Database reorganization utility (pdrorg command)
    - Free page release utility (pdreclaim command)
    - Global buffer residence utility (pdpgbfon command)
    If you specify the monitoring period in the -W option for operation commands and utilities other than the above utilities, the specification of the -W option takes precedence.
Specification guidelines
This operand is specified to prevent operation commands and utilities from going into the no-response state for a long time. Therefore, specify the amount of execution time for operation commands and utilities, within a range acceptable for operation.
Example 1:
If the maximum amount of execution time for the operation commands and utilities that can be monitored by this operand is about 90 minutes, you can assume a non-response error occurs if no response is returned from processing that normally finishes within 90 minutes even though an additional 30 minutes have passed. Therefore, specify pd_cmd_exec_time to 120 as the time, including a buffer period
Example 2:
This is an example when 5 hours is an acceptable amount of execution time of all nighttime batch jobs comprising multiple operation commands and utilities. If the acceptable amount of execution time for each command is defined as 30 minutes in the overall policy, specify 30 for pd_cmd_exec_time. If you want to monitor operation commands and utilities by changing the acceptable amount of execution time from the definition in the overall policy, you must use the option for each command to specify monitoring of individual execution times. The following figure shows an example:

Figure 2-1 FigureExample when multiple operation commands and utilities are executed

[Figure]
In this case, because the acceptable amount of execution time for each of the four processes of the pdhold and pdrels commands is 30 minutes, specify 30 for pd_cmd_exec_time. Because the maximum acceptable amount of execution time for pdcopy is 2 hours and 50 minutes, specify 170 for the option for specifying the period for monitoring the execution time for pdcopy. Because the maximum acceptable amount of execution time for pddbls is 10 minutes, specify 10 for the option for specifying the period for monitoring the execution time for pddbls. By setting a monitoring value as shown in the above example (30 + 170 + 10 + 30 = 240 = 4 hours), one hour in five hours of the acceptable amount of execution time for all nighttime batch jobs can be ensured as a buffer period for the period for monitoring the execution time.
Note
If a command goes into the no-response state due to a failure before a monitoring start message is output or after a monitoring end message is output, manually cancel the command process because the command is not automatically terminated.
Relationship to other operands
This operand is related to the pd_utl_exec_time operand.

49) pd_queue_watch_time = message-queue-monitoring-time
~<unsigned integer>((0-3600)) <<600>> (seconds)
This operand is designed to prevent a HiRDB process from not responding. For details about a server process that has stopped responding, see the HiRDB Version 9 System Operation Guide.
Reference note
The number of HiRDB server processes is restricted by the following operands:
  • pd_max_server_process
    If a large number of servers are running within a unit, carefully estimate the value to be specified for this operand. Additionally, if the standby-less system switchover facility is used, the estimated value must also take into account system switchovers.
  • pd_max_bes_process
    If a multiple front-end server or the standby-less system switchover (1:1) facility is used, carefully estimate the value to be specified for this operand.
  • pd_max_dic_process
    If a multiple front-end server is used, carefully estimate the value to be specified for this operand.
  • pd_ha_max_server_process
    If the standby-less system switchover (effects distributed) facility is used, carefully estimate the value to be specified for this operand.
  • pd_max_users
    If the number of concurrent connections is large, an appropriate value must be specified for this operand.
HiRDB uses a message queue for allocating server processes. When a server process stops responding, messages cannot be extracted from the message queue. If messages cannot be extracted from the message queue within the time specified by this operand (message queue monitoring time), a warning message or error message (KFPS00888-W or KFPS00889-E) is output. This facility is called the message queue monitoring facility. If one of these messages is output, the server process might have stopped responding.
If 0 is specified in this operand, the message queue is not monitored.
For details about the message queue monitoring facility, see the HiRDB Version 9 System Operation Guide.
Operand rule
Because message queue monitoring is carried out in 10-second increments, specify for this operand a multiple of 10 seconds (100 or 110 seconds, for example). If the specified value is not a multiple of 10 seconds, the last digit is rounded up. For example, if you specify 105 seconds, 110 seconds is used.
Relationship to other operands
This operand is related to the pd_queue_watch_timeover_action operand.

50) pd_queue_watch_timeover_action = continue | stop
Specifies the processing to be performed by HiRDB when messages cannot be extracted from the message queue within the message queue monitoring time.
continue:
HiRDB outputs the warning message (KFPS00888-W).
stop:
HiRDB outputs the warning and error messages (KFPS00888-W and KFPS00889-E) and abnormally terminates the unit that has the message queue.
Specification guidelines
  • Normally, specify stop (or omit this operand). If messages cannot be extracted from the message queue within the message queue monitoring time, the HiRDB server process might have stopped responding. Restarting the unit containing the server process that has stopped responding can sometimes correct the non-responding server process.
  • If you do not want to stop HiRDB, specify continue. In this case, transactions cannot be executed on the server that has stopped responding. Other servers can still execute transactions. To correct the non-responding server process, use the pdcancel command, for example, to terminate the transactions that were being executed in the server process that stopped responding. Afterwards, identify the cause of the server process no-response and take the necessary action. If there were no transactions, use the OS's kill command to terminate the server that stopped responding. Afterwards, identify the cause of the server process no-response and take the necessary action. For details about server process no-response and corrective measures, see the HiRDB Version 9 System Operation Guide.

51) pd_cmd_process_conwaittime = period-for-monitoring-process-allocation-at-execution-of-an-operation-command-or-utility
~<unsigned integer>((0, 16-4000))<<60>> (seconds)
Specifies the period for monitoring process allocation after an operation command or utility is executed.
If 0 is specified for this operand, the time taken to allocate a process is not monitored.
If a value from 1 to 15 is specified for this operand, the period for monitoring process allocation is set to 16 seconds.
Specification guidelines
Normally, this operand does not need to be specified.
Specify this operand according to the measure in the KFPS00358-E message only if the KFPS00358-E message was output and an operation command or utility finished abnormally because the number of server processes for extracting messages from the message queue became insufficient during allocation of a server process.
Notes
If a process is not allocated within the monitoring period, the KFPS00358-E message is output and then the operation command or utility ends in an abnormal termination.
Comments
To start an operation command or utility, a user server process or utility server process must be allocated to the operation command or utility. This operand is used to specify the period for monitoring allocation of a user server process or utility server process.
The following figure shows the monitoring scope of this operand.

Figure 2-2 FigureMonitoring scope of this operand

[Figure]
The table below shows the applicable operation commands and utilities.

Table 2-2 TableOperation commands and utilities to which this facility is applied

No. Operation commands and utilities
1 pdacunlck (removes the consecutive certification failure account lock state)
2 pdclose (closes RDAREAs)
3 pdconstck (integrity check utility)
4 pdcopy (database copy utility)
5 pddbchg (switches the replica status for a replica RDAREA)
6 pddbfrz (freezes the update of HiRDB files in user LOB RDAREAs that are filled with data)
7 pddbls (displays RDAREA statuses)
8 pddbst (database condition analysis utility)
9 pddefrev (generates definition SQLs)
10 pdexp (dictionary import/export utility)
11 pdbufls (displays global buffer information)
12 pdbufmod (dynamically updates the global buffer)
13 pdgetcst (optimizing-information collection utility)
14 pdhold (shuts down RDAREAs)
15 pdinit (database initialization utility)
16 pdload (database load utility)
17 pdmod (database structure modification utility)
18 pdopen (opens RDAREAs)
19 pdorbegin (commits a database for online reorganization)
20 pdorchg (switches over the current RDAREA for online reorganization)
21 pdorend (performs reflection processing for online reorganization)
22 pdparaload (performs parallel loading)
23 pdrbal (rebalancing utility)
24 pdrels (releases RDAREAs from shutdown status)
25 pdrorg (database reorganization utility)
26 pdreclaim (free page release utility)
27 pdpgbfon (global buffer residence utility)
28 pdrstr (database recovery utility)
29 pdvrup (upgrades the HiRDB version)
30 pdlistls (displays list definition information)
31 pdmemdb (command related to in-memory data processing)
32 pdreginit (registry facility initialization utility)

52) pd_down_watch_proc = upper-limit-for-server-process-abnormal-terminations[,monitoring-interval]
This operand is used for monitoring the number of abnormal terminations of a HiRDB server process. Processes to be monitored are those that are abnormally terminated by PDCWAITTIME over or aborting.
If abnormal terminations of server processes occur frequently, new services might not be accepted. However, because server process abnormal termination does not cause HiRDB abnormal termination, HiRDB is in an online stopped state, in effect. When this operand is specified, you can pull HiRDB out of this state by restarting it.
upper-limit-for-server-process-abnormal-termination: ~<unsigned integer>((0-65535))<<0>>
If abnormal terminations of server processes exceed the value specified in this operand, HiRDB (applicable unit for a HiRDB parallel server configuration) is abnormally terminated. This is called the facility for monitoring abnormal process terminations. For details about this facility, see the HiRDB Version 9 System Operation Guide.
For a HiRDB single server configuration, abnormal terminations of single server processes are counted. In the case of a HiRDB parallel server configuration, the total of the abnormal terminations in the front-end servers, back-end servers, and dictionary servers inside the unit is counted.
If 0 is specified, abnormal terminations of server processes are not monitored.
monitoring-interval: ~<unsigned integer>((10-3600))<<600>> (seconds)
Specifies the interval (in seconds) for monitoring abnormal terminations of server processes.
For example, if 100 is specified, abnormal terminations of server processes are monitored every 100 seconds.
Advantages
  • Restart of HiRDB refreshes memory and resource statuses, improving the processing efficiency.
  • If abnormal termination of server processes occurs frequently, HiRDB is abnormally terminated, and thus the system can be switched over immediately.
Notes
  • Do not use this operand in a system that does not allow abnormal termination.
  • When a server process is abnormally terminated, the KFPS01820-E message is output. Although this message is also output when the server process is abnormally terminated by the pdcancel command, this is not counted as an abnormal termination.
  • For a mutual system switchover configuration, multiple HiRDBs are activated on the same server machine when system switchover occurs. As a result, the system traffic might increase, causing an adverse effect instead. Therefore, if you specify this operand, we recommend that you restart HiRDB in the system that terminated abnormally.
  • If a HiRDB server process terminates abnormally repeatedly, a large amount of troubleshooting information will be output, resulting in frequent input to and output from the HiRDB operating directory, possibly leading to a full disk.
Remarks
  • If HiRDB is abnormally terminated by the facility for monitoring abnormal process terminations, the KFPS01821-E and KFPS00729-E messages are output.
  • The following table shows the causes of server process abnormal termination and the server processes that are included in the abnormal termination count.
    Cause of server process abnormal termination Inclusion in abnormal termination count
    Single server process Front-end server process Dictionary server process Back-end server process
    PDCWAITTIME operand value of the client environment definition has been exceeded Y Y N#1 N#1
    pdcancel command N N#2 N N
    Internal forced termination (HiRDB internally issues SIGKILL and terminates a process) Y#3 Y#3 N#1 N#1
    Abort Y Y Y Y
    One of the following:
    • Abnormal termination of server process by transaction recovery processing in an OLTP system
    • Abnormal termination of server process by XDS transaction recovery processing#4
    		 Y Y N N
    Abnormal termination of process other than those described here Y Y Y Y

Legend:
Y: Included in abnormal termination count
N: Not included in abnormal termination count

#1
If an error is detected in a transaction branch, the abnormal terminations of the front-end server process that has occurred in the same transaction branch are counted.

#2
If the pdcancel command is used to forcibly terminate a back-end server process or dictionary server process, the front-end server process is internally and forcibly terminated. In this case, the abnormal termination of the front-end server process might be counted in some cases.

#3
If an error is detected in a global transaction by an OLTP system, the abnormal terminations of the single server process or front-end server process that have occurred in the same global transaction are counted.

#4
If the completion status of a transaction executed from XDS on a server that provides the primary functionality cannot be determined, XDS transaction recovery processing might produce a rollback and the server process might terminate abnormally.

53) pd_host_watch_interval = host-to-host-monitoring-interval
~<unsigned integer>((1-180))<<10>> (seconds)
Specifies in seconds the amount of time between monitoring of the operating status of other hosts (server machines).
Specification guidelines
Normally, this operand is omitted.
Notes
  • This operand is not applicable to a HiRDB single server configuration or to a HiRDB parallel server configuration that has only one unit.
  • If this value is too large, it will be difficult to detect errors at other hosts.
  • If this value is too small, a burden will be placed on the network whenever the system has a large number of units, because of the need to generate a high volume of communications for the purpose of monitoring operating status.
Relationship to other operands
This operand is related to the pd_ipc_conn_nblock_time operand.

54) pd_watch_resource = MANUAL | AUTO | DEFAULT
  • 0904 compatibility mode: <<MANUAL>>
Specifies whether to output a warning message when the resource usage reaches or exceeds 80%.
MANUAL: Do not issue the warning message.
AUTO or DEFAULT: Output the warning message.
The following table lists the resources that are monitored.
Monitored resource Message that is output
Maximum number of concurrent connections specified by the pd_max_users operand# KFPS05123-W
Concurrently accessible base tables count specified by the pd_max_access_tables operand
Maximum number of RDAREAs specified by the pd_max_rdarea_no operand
Maximum number of HiRDB files comprising an RDAREA specified by the pd_max_file_no operand
Usage of HiRDB file system area for work table files, as specified by the pdwork operand
Maximum number of users who can own lists concurrently, as specified by pd_max_list_users
Maximum number of lists that a user can create, as specified by pd_max_list_count
Number of audit trail files that cannot be specified as swappable targets
Number of lists created within a server KFPH22023-W
#: If DEFAULT is specified, a warning message is not output.
Relationship to other operands
When AUTO or DEFAULT is specified, 80 is set as the default value for the operands listed below, which eliminates the need to specify these operands (however, if it is necessary to specify a value other than 80 for any of the listed operands, the appropriate value can be specified):
  • pd_max_users_wrn_pnt#1, #2
  • pd_max_access_tables_wrn_pnt
  • pd_max_rdarea_no_wrn_pnt
  • pd_max_file_no_wrn_pnt
  • pdwork_wrn_pnt
  • pd_max_list_users_wrn_pnt
  • pd_max_list_count_wrn_pnt
  • pd_aud_file_wrn_pnt#1
  • pd_rdarea_list_no_wrn_pnt#1
#1: 50 is set as the trigger for resetting the warning output status.
#2: Except when DEFAULT is set.
Note
After a version upgrade, the number of resources to be monitored might increase (meaning that other operands in addition to those listed above might be included).Therefore, to keep the monitoring statuses up to date, specify the operands listed above in order to monitor the individual resources, rather than specifying this operand.

55) pd_max_users_wrn_pnt = trigger-for-outputting-warning-message-related-to-number-of-connections-to-HiRDB-server[,trigger-for-resetting-warning-message-output-status]
trigger-for-outputting-warning-message-related-to-number-of-connections-to-HiRDB-server ~<unsigned integer>((0-100))<<0 or 80>>(%)
Specifies when to output the warning message when the number of connections to the HiRDB server reaches or exceeds a predetermined percentage (percentage of the maximum number of concurrent connections specified by the pd_max_users operand). For example, if 200 and 90 are specified for the pd_max_users and pd_max_user_wrn_pnt operands, respectively, the KFPS05123-W warning message is output when the number of connections to the HiRDB server reaches or exceeds 180.
Notes
  • When 0 is specified, no warning message is issued.
  • Specification of this operand is invalid when 9 or less is specified for the pd_max_users operand.
Relationship to other operands
  • If you omit this operand and MANUAL or DEFAULT is specified for the pd_watch_resource operand, the value of this operand is assumed to be 0 (no warning message is issued).
  • If you omit this operand and AUTO is specified for the pd_watch_resource operand, the value of this operand is assumed to be 80 (a warning message is issued when the usage reaches 80%).
trigger-for-resetting-warning-message-output-status: ~<unsigned integer>((0-99) ) (%)
Specifies the trigger for resetting the warning message output status. When the warning message (KFPS05123-W) is output, HiRDB goes into the warning message output status. Once HiRDB goes into this status, the warning message is not output again, even if the number of connections to the HiRDB server exceeds the warning message output trigger level again. However, when the number of connections to the HiRDB server falls below the trigger for resetting the warning message output status specified here, the warning message output status is reset.
For example, if pd_max_users_wrn_pnt=90,70 is specified, the warning message is output when the number of connections to the HiRDB server reaches or exceeds 90% of the maximum number of concurrent connections. Afterwards, no warning message is output until the number of connections to the HiRDB server falls below 70% of the maximum number of concurrent connections. After the percentage falls below 70%, and when it subsequently reaches or exceeds 90% again, the warning message is output.
Notes
  • When this specification is omitted, warning-message-output-trigger - 30 is assumed as the default (if the result is a negative number, 0 is used).
  • If a value greater than the warning message output trigger is specified, the warning message output trigger value is used.

56) pd_max_access_tables_wrn_pnt = trigger-for-issuing-concurrently-accessible-base-tables-count-warning
~<unsigned integer>((0-100))<<0 or 80>> (%)
Specifies the number of base tables being accessed concurrently that is to trigger issuance of a warning message. The value that is specified is a percentage of the total number of concurrently accessible base tables and sequence generators combined, as specified in the pd_max_access_tables operand. For example, if 90 is specified in this operand and 200 in specified in pd_max_access_tables, the KFPS05123-W warning message will be issued when the total number of base tables and sequence generators being accessed concurrently reaches 180 (90% of 200).
Note
When 0 is specified, no warning message is issued.
Relationship to other operands
  • If you omit this operand and MANUAL is specified for the pd_watch_resource operand, the value of this operand is assumed to be 0 (no warning message is issued).
  • If you omit this operand and AUTO or DEFAULT is specified for the pd_watch_resource operand, the value of this operand is assumed to be 80 (a warning message is issued when the usage reaches 80%).

57) pd_max_rdarea_no_wrn_pnt = trigger-for-issuing-RDAREAs-count-warning
~<unsigned integer>((0-100))<<0 or 80>> (%)
Specifies as a percentage of the maximum number of RDAREAs (as specified by the pd_max_rdarea_no operand) the actual number of RDAREAs at which a warning message is to be issued. For example, if 90 is specified for this operand and 200 has been specified for the pd_max_rdarea_no operand, a warning message will be issued when the number of RDAREAs reaches 180 (90% of 200). KFPS05123-W is issued as the warning message.
Note
When 0 is specified, no warning message is issued.
Relationship to other operands
  • If you omit this operand and MANUAL is specified for the pd_watch_resource operand, the value of this operand is assumed to be 0 (no warning message is issued).
  • If you omit this operand and AUTO or DEFAULT is specified for the pd_watch_resource operand, the value of this operand is assumed to be 80 (a warning message is issued when the usage reaches 80%).

58) pd_max_file_no_wrn_pnt = trigger-for-issuing-HiRDB-files-count-warning
~<unsigned integer>((0-100))<<0 or 80>> (%)
Specifies as a percentage of the maximum number of files comprising an RDAREA (as specified by the pd_max_file_no operand) the number of files actually comprising an RDAREA at which a warning message is to be issued. For example, if 90 is specified for this operand and 200 has been specified for the pd_max_file_no operand, a warning message will be issued when the number of files comprising an RDAREA reaches 180 (90% of 200). KFPS05123-W is issued as the warning message.
Note
When 0 is specified, no warning message is issued.
Relationship to other operands
  • If you omit this operand and MANUAL is specified for the pd_watch_resource operand, the value of this operand is assumed to be 0 (no warning message is issued).
  • If you omit this operand and AUTO or DEFAULT is specified for the pd_watch_resource operand, the value of this operand is assumed to be 80 (a warning message is issued when the usage reaches 80%).

59) pdwork_wrn_pnt = trigger-for-issuing-work-table-files-warning
~<unsigned integer>((0-100))<<0 or 80>> (%)
Specifies as a percentage of the applicable usage# of a HiRDB file system area for work table files (as specified by the pdwork operand) the point at which a warning message is to be issued. For example, if 90 is specified for this operand, a warning message will be issued when the applicable usage rate of a HiRDB file system area for work table files reaches 90%. KFPS05123-W is issued as the warning message.
#: This operand specifies a percentage of usage in terms of the items listed below, which are specified with the pdfmkfs command when the HiRDB file system areas are created; the warning message can be issued for each of these items:
  • Usage relative to capacity
  • Usage relative to the maximum number of files
  • Usage relative to the maximum number of increments
Note
When 0 is specified, no warning message is issued.
Relationship to other operands
  • If you omit this operand and MANUAL is specified for the pd_watch_resource operand, the value of this operand is assumed to be 0 (no warning message is issued).
  • If you omit this operand and AUTO or DEFAULT is specified for the pd_watch_resource operand, the value of this operand is assumed to be 80 (a warning message is issued when the usage reaches 80%).

60) pd_max_list_users_wrn_pnt = trigger-for-issuing-warning-about-number-of-users-who-have-created-lists
~<unsigned integer>((0-100)) <<0 or 80>> (%)
Specifies as a percentage of the number of users who can create lists (as specified by the pd_max_list_users operand) the point at which the number of users actually using lists is to cause a warning message to be issued. For example, if 90 is specified for this operand and 200 was specified for the pd_max_list_users operand, a warning message will be issued whenever the number of users using lists reaches 180. KFPS05123-W is issued as the warning message.
Notes
  • When 0 is specified, no warning message is issued.
  • The warning message is output only once. However, if the applicable server is restarted after the warning message has been output, a check of list usage is executed again, and the warning message will be output again.
Relationship to other operands
  • If you omit this operand and MANUAL is specified for the pd_watch_resource operand, the value of this operand is assumed to be 0 (no warning message is issued).
  • If you omit this operand and AUTO or DEFAULT is specified for the pd_watch_resource operand, the value of this operand is assumed to be 80 (a warning message is issued when the usage reaches 80%).

61) pd_max_list_count_wrn_pnt = trigger-for-issuing-warning-about-number-of-lists-created-by-a-user
~<unsigned integer>((0-100)) <<0 or 80>> (%)
Specifies as a percentage of the number of lists that can be created per user (as specified by the pd_max_list_count operand) the point at which the number of lists created by a user is to cause a warning message to be issued. For example, if 90 is specified for this operand and 200 was specified for the pd_max_list_count operand, a warning message will be issued when a user creates 180 lists. KFPS05123-W is issued as the warning message.
Notes
  • When 0 is specified, no warning message is issued.
  • The warning message is output only once. However, if the applicable server is restarted after the warning message has been output, a check of list usage is executed again, and the warning message will be output again.
  • If multiple users are creating lists simultaneously, the warning message might be output at the server multiple times, depending on the timing.
Relationship to other operands
  • If you omit this operand and MANUAL is specified for the pd_watch_resource operand, the value of this operand is assumed to be 0 (no warning message is issued).
  • If you omit this operand and AUTO or DEFAULT is specified for the pd_watch_resource operand, the value of this operand is assumed to be 80 (a warning message is issued when the usage reaches 80%).

62) pd_rdarea_list_no_wrn_pnt = trigger-for-issuing-warning-about-number-of-lists-created-at-server[,trigger-for-resetting-warning-output-status]
trigger-for-issuing-warning-about-number-of-lists-created-at-server ~<unsigned integer>((0-100)) <<0 or 80>> (%)
Specifies as a percentage of the number of lists that can be created at a server the point at which a warning message is to be issued. For example, if 90 is specified for this operand and the maximum number of lists that can be created at the server is 1,000, a warning message will be issued whenever 900 lists have been created. KFPH22023-W is issued as the warning message.
Note
When 0 is specified, no warning message is issued.
Relationship to other operands
  • If you omit this operand and MANUAL is specified for the pd_watch_resource operand, the value of this operand is assumed to be 0 (no warning message is issued).
  • If you omit this operand and AUTO or DEFAULT is specified for the pd_watch_resource operand, the value of this operand is assumed to be 80 (a warning message is issued when the usage reaches 80%).
trigger-for-resetting-warning-output-status: ~<unsigned integer>((0-99)) (%)
Specifies the trigger for resetting the warning message output status.
Whenever the KFPH22023-W warning message is issued, HiRDB goes into warning message output status. Once HiRDB is in this status, the warning message will not be issued again even when the number of created lists again reaches the trigger value. However, when the number of created lists falls below the trigger for resetting the warning message output status specified here, the warning message output status is reset.
For example, if pd_rdarea_list_no_wrn_pnt=90,70 is specified, the warning message will be issued when the number of created lists reaches 90% of the maximum permissible number of lists. Once this occurs, the warning message will not be eligible to be issued again until the number of created lists falls below 70% of the maximum number of permissible lists allowed. Thereafter, the warning message will be issued if the number of lists again reaches the 90% trigger value.
Notes
  • If no value is specified for the trigger for resetting the warning output status, 30 is assumed. If a negative is specified, 0 is assumed.
  • If the value specified here is greater than the value specified for the trigger for issuing warning, the value specified here is ignored and the same value as was specified for the trigger for issuing warning is assumed as the trigger for resetting the warning output status.

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2011, 2015, Hitachi, Ltd.