|
Parameter name |
Value |
Description |
Option |
Default |
|---|---|---|---|---|
|
BQL_GROUPS |
1..9 |
To obtain a higher level of parallel processing in an STC, you can specify a maximum of nine BQL groups. Five groups is recommended. Note: This parameter has no effect on batch jobs. Batch jobs always work with one BQL group. |
optional |
1 |
|
BQL_FUNCTION |
nnn |
Specifies the number of functions that can work in parallel within a group. |
|
999 |
|
BQL_MASTER_SSID |
ssid |
Specifies the master system. In a master-slave system on one LPAR, or in an OCF/ XCF connection, this parameter must always be specified on the slave with the SSID of the master system. This does not apply if you are using a shared database (see "Sharing databases with the BQL share option"). |
optional |
None |
|
BQL_SHARE_OPTION |
NO | SPOOL | ALL |
Enables you to activate or deactivate the BQL share option. |
optional |
NO |
|
BQL_OPEN_FILES |
YES | NO |
This parameter applies to _beta doc|z plus only: If NO is specified, the SPOOL, CACHE, and INDEX files will not be opened until they are needed for the first time, i.e. they will not be automatically allocated and opened when the started task is started. Note: The files concerned must be set to a specific status for this parameter to take effect. Please contact Beta Systems support for details. |
optional |
NO |
|
BQL_INDEX_
|
nnnnn |
You can specify the index files for _beta doc|z plus. nnnnn indicates the number of buffers (in 4K blocks) to be used. If the value specified here is > 30000, and A2G_SUPPORT=YES has not been set, the value will be reset to 30000. |
optional |
0 |
|
BQL_SPEEDMASTER |
YES | NO |
YES specifies that the BQL Speedmaster function is to be used for all DATA and KEY files. You can define the number of buffers for each file in the database definition file. Important: Do not change the value of this parameter to NO. Otherwise serious performance problems could occur. Exception: You have to set this parameter temporarily to NO following the occurrence of message 9502E or 9503W. For more information, see "Operator Response" of message 9502E and 9503W in BSA Messages and Codes. |
optional |
YES |
|
BQL_SPOOLCHECK |
YES | NO |
YES The master STC checks all spool blocks at startup and internal control blocks are built. Unused reader blocks are freed. NO There is no spool check at startup, which reduces the start phase of the master STC considerably. Read-only spool files are always checked at startup, irrespective of the value of this parameter. |
optional |
NO |
|
BQL_STATISTIC |
YES | NO |
The BQL statistics functionality can be switched on and off. When a started task or batch job is stopped, the values found for tables and commands will be written. |
optional |
NO |
|
BQL_QRY_
|
0..2000 |
Central storage (amount in MB) Use this keyword to specify how much central storage is to be used for database queries online (online option D.Q). Specify 0 to use DASD storage instead of central storage. Note: If both BQL_QRY_MAXMEMORY and BQL_QRY_FILESPACE are set to 0, unlimited central storage is used. |
optional |
If VDF: If TSO: |
|
BQL_QRY_FILESPACE |
0..2000 |
DASD storage (amount in cyls) Use this keyword to specify how much file space is to be used on a temporary DASD for database queries online (online option D.Q). Specify 0 to use central storage instead of DASD storage. |
optional |
50 |
|
BQL_DICT_FLAG_
|
YES | NO |
By default, option D.2.3 (FIELDS) includes subfield information (so-called flag fields) in the displayed table. If you don't need this information, you can disable this function to reduce resource consumption if the number of flag fields used by the product is very high (for example _beta access). This parameter can be updated dynamically via the Service Manager. |
optional |
YES |
|
BQL_TRACE |
YES | NO |
YES causes the logging of all BQL and BOF commands |
optional |
NO |
|
BQL_USER |
number of users |
This keyword specifies the number of users allowed in the internal RACF security user table of BQL. 0 means that the internal security table will not be used. When you increase or decrease the number of users, refresh the table with the following MODIFY command for your change to take effect: F stcname,REFRESH RCF[,U=userid] For more information, see "Refreshing the RACF security user table". |
optional |
500 |