8.2.1 Explanation of the specification format and options

(1) Specification format

adbchgsqltrc {-d
               |-e
               |-s [-y information-whose-output-is-to-start]
                   [-n information-whose-output-is-to-stop]
                   [-l output-level-after-change]
               |-y information-whose-output-is-to-start
                   [-n information-whose-output-is-to-stop]
                   [-l output-level-after-change]
               |-n information-whose-output-is-to-stop 
                   [-y information-whose-output-is-to-start]
                   [-l output-level-after-change]
               |-l output-level-after-change
                   [-y information-whose-output-is-to-start]
                   [-n information-whose-output-is-to-stop]
               }

To Page Top

(2) Explanation of options

• -d

Displays the output status of the SQL trace information.

For details about the content that is output when this option is specified, see 8.3.1 Checking the output status of the SQL trace information.

• -e

Specify this option to stop outputting the SQL trace information.

• -s

Specify this option to start outputting the SQL trace information.

• -y information-whose-output-is-to-start

~<character string>((1 to 16 bytes))

Specifies the type of information to be output to the SQL trace information.

param: Dynamic parameter information

Outputs dynamic parameter information to the SQL trace information.

accesspath: Access path information and access path statistical information

Outputs access path information and access path statistical information to the SQL trace information.

The following rules apply to specifying this information:

• You can specify multiple information items by separating them with commas (,). You can use only commas as delimiters.

• When you specify multiple information items, the order in which they are specified does not matter.

• The same information item cannot be specified more than once.

• -n information-whose-output-is-to-stop

~<character string>((1 to 16 bytes))

Specifies the type of information whose output to the SQL trace information is to be stopped.

param: Dynamic parameter information

Does not output dynamic parameter information to the SQL trace information.

accesspath: Access path information and access path statistical information

Does not output access path information and access path statistical information to the SQL trace information.

The following rules apply to specifying this information:

• You can specify multiple information items by separating them with commas (,). You can use only commas as delimiters.

• When you specify multiple information items, the order in which they are specified does not matter.

• The same information item cannot be specified more than once.

• -l output-level-after-change

~<character string>((1 to 4 bytes))

Specifies the unit in which to output the SQL trace information.

sql: Each SQL statement

Outputs the SQL trace information for each SQL statement.

call: Each call

Outputs the SQL trace information for each call.

To Page Top

(3) Relationships between command options and server definitions

Some of the options of the adbchgsqltrc command correspond to the server definition operations related to SQL tracing. The following table shows the relationships between the server definition operations related to SQL tracing and the adbchgsqltrc command options.

Table 8‒1: Correspondence between the server definition operations related to SQL tracing and adbchgsqltrc command options

No.	Server definition operand name	Server definition specification value	Corresponding adbchgsqltrc command option
1	adb_sql_trc_out	Y	-s
2		N	-e
3	adb_sql_trc_param	Y	-y param
4		N	-n param
5	adb_sql_trc_accesspath	Y	-y accesspath
6		N	-n accesspath
7	adb_sql_trc_level	SQL	-l sql
8		CALL	-l call

For details about server definitions related to SQL tracing, see the topic Operands related to SQL statements (set format) in Detailed descriptions of the server definition operands in Designing the Server Definition in the HADB Setup and Operation Guide.

To Page Top