24.3 Examples

This example executes the adbls -d gbuf command to display information about the global buffers.

Explanation of the output items

BUFF_NAME

Displays a global buffer name specified in the -g option of the adbbuff operand in the server definition or a global buffer name determined automatically by HADB.

Note

If the -o option was specified in the adbbuff operand, the global buffer name determined automatically by HADB is displayed as global-buffer-name#nnnnnnnnnn (n: page size as a 10-digit decimal number).

If the -o option was omitted, the global buffer name determined automatically by HADB is displayed as ##ADBOTHER#nnnnnnnnnn (n: page size as a 10-digit decimal number).

DBAREA_NAME

Displays the DB area name specified in the -n option of the adbbuff operand in the server definition or the DB area name for which HADB allocated the global buffer automatically.

If multiple DB areas are allocated to the global buffer, each of those DB area names is displayed on a separate line.

PAGE_SIZE

Displays in kilobytes the global buffer page size. This is the same value as the page size for the 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 for ADBWRK (global buffer for global work table).

PAGE_NUM

Displays the number of pages in the global buffer specified in the -p option of the adbbuff operand in the server definition.

For ADBWRK (global buffer for global work table), the adb_dbbuff_wrktbl_glb_blk_num operand value specified in the server definition is displayed.

If the -p option was omitted in the adbbuff operand in the server definition or the adb_dbbuff_wrktbl_glb_blk_num operand was omitted in the server definition, the default value is displayed.

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

Table 24‒1: Meanings of the characters displayed following the number of global buffer pages value

No.	Suffixed character	Meaning of the character	Corresponding global buffer	Value that is displayed as the number of global buffer pages
1	S	Value specified in the server definition is used.	Global buffer defined in the adbbuff operand in the server definition	-p option value in the adbbuff operand in the server definition
2			Global buffer for global work table (ADBWRK)	adb_dbbuff_wrktbl_glb_blk_num operand value in the server definition
3	D	Default value is used.	Global buffer defined in the adbbuff operand in the server definition or a global buffer that is defined automatically	-p option value in the adbbuff operand in the server definition
4			Global buffer for global work table (ADBWRK)	Default value for the adb_dbbuff_wrktbl_glb_blk_num operand in the server definition
5			Global buffer for the master directory (ADBMST)	Default value for ADBMST

RANGE_IDX_PAGE_NUM

Displays the number of pages in the global buffer dedicated to the range index specified in the -a option of the adbbuff operand in the server definition.

If the -a option was omitted in the adbbuff operand in the server definition, 0 is displayed.

TABLE_SCAN_BUFFER_SIZE(MB)

Displays the memory size (in megabytes) used for the table scan buffer.

The displayed value varies depending on the specification of the -v or -k option of the adbbuff operand in the server definition. The following table shows the details.

Table 24‒2: Value displayed for TABLE_SCAN_BUFFER_SIZE(MB)

No.	Whether the table scan buffer is specified	Value displayed for TABLE_SCAN_BUFFER_SIZE(MB)
1	The -v option of the adbbuff operand is specified.	Value specified for memory-size-used-for-the-table-scan-buffer in the -v option
2	The -k option of the adbbuff operand is specified.	Value determined from the following formula: Value specified for the -k option × 4
3	Neither the -v nor -k option of the adbbuff operand is specified.	0

TABLE_SCAN_BUFFER_THREAD_MAX_SIZE(MB)

Displays the maximum memory size (in megabytes) that can be used for each real thread of the table scan buffer.

The displayed value varies depending on the specification of the -v or -k option of the adbbuff operand in the server definition. The following table shows the details.

Table 24‒3: Value displayed for TABLE_SCAN_BUFFER_THREAD_MAX_SIZE(MB)

No.	Whether the table scan buffer is specified	Whether maximum-memory-size-that-can-be-used-for-each-real-thread-of-the-table-scan-buffer is specified in the -v option	Value displayed for TABLE_SCAN_BUFFER_THREAD_MAX_SIZE(MB)
1	The -v option of the adbbuff operand is specified.	Specified	Value specified for maximum-memory-size-that-can-be-used-for-each-real-thread-of-the-table-scan-buffer in the -v option
2		Not specified	0
3	The -k option of the adbbuff operand is specified.	--	Value determined from the following formula: Value specified for the -k option × 4 ÷ value of the adb_sys_rthd_num operand in the server definition If the value determined by the preceding calculation is less than 5 megabytes, the value is rounded up to 5 megabytes.
4	Neither the -v nor -k option of the adbbuff operand is specified.	--	0

Legend:

--: Not applicable

Note

For details about the server definition operands, see the topic Detailed descriptions of the server definition operands in Designing the Server Definition in the HADB Setup and Operation Guide.

For details about DB area names, see 20.5.1 Attributes of DB areas that are created.

To Page Top