Start of change

QUERY_ACCEL_OPTIONS in macro DSN6SPRM

The QUERY_ACCEL_OPTIONS subsystem parameter specifies additional types of SQL queries that are eligible for acceleration.

Acceptable values: NONE, YES
Default: NONE
DSNZPxxx: DSN6SPRM.QUERY_ACCEL_OPTIONS (option NONE)

NONE specifies that no additional types of SQL queries are eligible. Therefore, the types of queries that are described in the other available values for this parameter are not eligible for acceleration. This is the default value.

You can specify a combination of query accelerator options other than NONE in a comma-separated list that is enclosed in parentheses. For example, (1,2).

Possible values are:

1
Specifies that queries that include data that is encoded with the EBCDIC mixed or graphic encoding schemes are eligible for acceleration.

If the accelerator server encodes data in another encoding scheme, such as Unicode UTF-8, the collating sequence for the data on the accelerator server is different from the collating sequence for the data in DB2®. This difference affects data ordering and the results from range predicates. Therefore, if table columns include any mixture of uppercase characters, lowercase characters, numeric characters, or national language characters, and the SQL statements that query those tables include range predicates or ordering on those columns, the results of executing a query in DB2 might be different from the results of executing the same query on an accelerator server.

Start of change2End of change
Start of changeSpecifies that an INSERT with SELECT statement is eligible for acceleration. However, only the SELECT operation of the query is processed by the accelerator server.

If the SELECT operation runs on the accelerator server, the data that is operated on by the SELECT operation might not be current in the accelerator server.

End of change
Start of change3End of change
Start of changeSpecifies that queries that contain built-in functions for which DB2 processes each byte of the input string, rather than each character of the input string, can run on an accelerator server.

For an accelerator server that supports only functions that operate on the characters in an input string, if the input data on which the function operates contains only single-byte characters, the function returns the same result when it runs on the accelerator server and when it runs on DB2. However, if the input data contains multi-byte characters, the function returns different results when it runs on the accelerator server and when it runs on DB2.

End of change
Start of change4End of change
Start of changeSpecifies that queries that reference an expression with a DATE data type that uses a LOCAL format are not blocked from running on an accelerator server. The accelerator server uses the format 'dd/mm/yyyy' to interpret the input and output date value.

Specify option 4 only when the DATE FORMAT field of the DSNTIP4 panel specifies LOCAL, or when application programs that process SQL on DB2 are precompiled with the DATE(LOCAL) option. In both of these cases, the LOCAL date exit routine must define the specific 'dd/mm/yyyy' date format. If the LOCAL format is not defined as 'dd/mm/yyyy', the query might return unpredictable results.

End of change
End of change