Hitachi

Hitachi Advanced Database Command Reference


25.3 Examples

This example executes the adbls -d lbuf command to display information about the local work table buffer.

adbls -d lbuf
 
CNUMBER    PAGE_SIZE PAGE_NUM
0          256       256 D
1          256       128 C
3          256       10 C
4          256       256 D
5          256       256 D

Explanation of the output items

CNUMBER

Displays the connection sequence number since the HADB server started.

To check the application identifier or command that corresponds to a displayed connection sequence number, use the adbls -d cnct command.

In the execution results of the adbls -d cnct command, check the PROGRAM column for the same connection sequence number.

If 0 is displayed under CNUMBER, one of the following values is displayed under PAGE_NUM:

  • The value specified for the adb_dbbuff_wrktbl_clt_blk_num operand in the server definition or the default value

  • The value specified for the adb_dbbuff_wrktbl_clt_blk_num buffer-modifying option

For details about the adbls -d cnct command, see 23. adbls -d cnct (Display the Connection Status).

PAGE_SIZE

Displays in kilobytes the page size for the local work table buffer used for application program or command processing. This is the same value as the page size for the work table DB area.

If the page size of the work table DB area was changed by specifying the adb_dbarea_wrk_page_size operand in the server definition when the HADB server started, the page size after the change is displayed.

PAGE_NUM

Displays the number of local work table buffer pages used for application program or command processing.

One of the following values is displayed:

  • The value specified for the adb_dbbuff_wrktbl_clt_blk_num operand in the server definition, or the default value for this operand

  • The value specified for the adb_dbbuff_wrktbl_clt_blk_num operand in the client definition

  • The value specified for the adb_export_wrktbl_blk_num export option

  • The value specified for the adb_dbbuff_wrktbl_clt_blk_num buffer-modifying option

You can determine which value applies to the number of local work table buffer pages by checking the character that follows the number of pages value. The following table explains the meanings of the suffixed characters.

Table 25‒1: Meaning of the characters displayed following the value displayed for the number of local work table buffer pages

No.

Suffixed character

Meaning of the character

Value that is displayed as the number of local work table buffer pages

1

S

Value specified in the server definition is used.

Value specified for the adb_dbbuff_wrktbl_clt_blk_num operand in the server definition

2

S*

Value specified in the buffer-modifying option is used.

Value specified for the adb_dbbuff_wrktbl_clt_blk_num buffer-modifying option

3

C

Value specified in the client definition or the export option is used.

Value specified for the adb_dbbuff_wrktbl_clt_blk_num operand in the client definition

4

Value specified for the adb_export_wrktbl_blk_num export option

5

D

Default value is used.

Default value for the adb_dbbuff_wrktbl_clt_blk_num operand in the server definition

The number of local work table buffer pages that is displayed by this command depends on the settings in the server definition and the client definition and whether the adbmodbuff command has been executed. The following examples explain these variations in detail.

Example 1: When the adb_dbbuff_wrktbl_clt_blk_num operand is omitted in the server definition
adbls -d lbuf
 
CNUMBER    PAGE_SIZE PAGE_NUM
0          256       256 D
1          256       128 C
3          256       10 C
4          256       256 D
5          256       256 D
  • On the row where CNUMBER is 0, the default value of the adb_dbbuff_wrktbl_clt_blk_num operand in the server definition is displayed.

  • For connection sequence numbers 1 and 3, the adb_dbbuff_wrktbl_clt_blk_num operand is specified in the client definition. Therefore, on the rows where CNUMBER is 1 and 3, the value specified for the adb_dbbuff_wrktbl_clt_blk_num operand in the client definition is displayed under PAGE_NUM.

  • For connection sequence numbers 4 and 5, the adb_dbbuff_wrktbl_clt_blk_num operand is omitted in the client definition. Therefore, on the rows where CNUMBER is 4 and 5, the default value of the adb_dbbuff_wrktbl_clt_blk_num operand in the server definition is displayed under PAGE_NUM.

Example 2: When the adb_dbbuff_wrktbl_clt_blk_num operand is specified in the server definition
adbls -d lbuf
 
CNUMBER    PAGE_SIZE PAGE_NUM
0          256       128 S
1          256       128 C
3          256       10 C
4          256       128 S
5          256       128 S
  • On the row where CNUMBER is 0, the value specified for the adb_dbbuff_wrktbl_clt_blk_num operand in the server definition is displayed.

  • For connection sequence numbers 1 and 3, the adb_dbbuff_wrktbl_clt_blk_num operand is specified in the client definition. Therefore, on the rows where CNUMBER is 1 and 3, the value specified for the adb_dbbuff_wrktbl_clt_blk_num operand in the client definition is displayed under PAGE_NUM.

  • For connection sequence numbers 4 and 5, the adb_dbbuff_wrktbl_clt_blk_num operand is omitted in the client definition. Therefore, on the rows where CNUMBER is 4 and 5, the value specified for the adb_dbbuff_wrktbl_clt_blk_num operand in the server definition is displayed under PAGE_NUM.

Example 3: When the adbmodbuff command was executed
adbls -d lbuf
 
CNUMBER    PAGE_SIZE PAGE_NUM
0          256       128 S*
1          256       128 C
3          256       10 C
4          256       128 S*
5          256       128 S*
  • On the row where CNUMBER is 0, the value specified for the adb_dbbuff_wrktbl_clt_blk_num buffer-modifying option is displayed.

  • For connection sequence numbers 1 and 3, the adb_dbbuff_wrktbl_clt_blk_num operand is specified in the client definition. Therefore, on the rows where CNUMBER is 1 and 3, the value specified for the adb_dbbuff_wrktbl_clt_blk_num operand in the client definition is displayed under PAGE_NUM.

  • For connection sequence numbers 4 and 5, the adb_dbbuff_wrktbl_clt_blk_num operand is omitted in the client definition. Therefore, on the rows where CNUMBER is 4 and 5, the value specified for the adb_dbbuff_wrktbl_clt_blk_num buffer-modifying option is displayed under PAGE_NUM.

Note
  • For details about the adb_dbbuff_wrktbl_clt_blk_num operand in the server definition, see the topic Operands related to performance (set format) in Detailed descriptions of the server definition operands in Designing the Server Definition in the HADB Setup and Operation Guide.

  • For details about the adb_dbbuff_wrktbl_clt_blk_num operand in the client definition, see the topic Operands related to performance in Contents of operands in the client definition in Designing Client Definitions in the HADB Application Development Guide.

  • For details about the adb_export_wrktbl_blk_num export option, see 14.2.2 Format of export options.

  • For details about the adb_dbbuff_wrktbl_clt_blk_num buffer-modifying option, see 35.2.2 Format of the buffer-modifying option.