Client Runtime Controls define which sessions participate in Adabas Fastpath optimization and provide dynamic control for the user.
Fastpath shares some runtime controls with Adabas System Coordinator. When a new runtime control is added a panel appears with a title System Coordinator Runtime Controls. Please refer to Adabas System Coordinator for further information on the controls appearing in this panel.
Client Runtime Controls | Overridable |
---|---|
Command Time |
Y |
Direct
Access |
Y |
Fastpath
On/Off |
Y |
Job
End Statistics |
Y |
Read-Ahead Memory Limit
|
Y |
Read-Ahead Optimization
Control |
Y |
System
Coordinator Group Name |
Y |
Maximum read-ahead unit
size(k) |
Y |
Maximum read-ahead rate
|
Y |
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
Client runtime control |
If a command time is specified, then any commands that are successfully optimized by Fastpath will have this command time. |
0-99999999 | 00000000 |
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
Client runtime control |
Controls direct access optimization at the job level. If this job parameter is set to OFF, direct access optimization is not performed, regardless of the settings in the buffer and file parameters. |
ON | OFF | ON |
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
Client runtime control |
Controls whether any Fastpath optimization should be attempted for this session. If this parameter is set to OFF, Fastpath optimization is not attempted, regardless of the settings in the buffer and file parameters. |
ON | OFF | ON |
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
Client runtime control |
Controls whether the optimization statistics for a job are to be saved or printed. Possible values are:
Note: |
None Daemon messages File history |
None |
Parameter Type | Use | Minimum | Maximum | Default |
---|---|---|---|---|
Client runtime control |
Limits the amount of memory that can be used for read-ahead optimization for a job. |
0 | 0 |
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
Client runtime control |
Controls read-ahead optimization at the job level. If this job parameter is set to OFF, read-ahead optimization is not performed, regardless of the settings in the buffer and file parameters. In addition, you can choose between the batch (BAT) or TP monitor (TP) algorithm for setting the incremental multifetch factor. The batch algorithm accelerates the read-ahead rate more than the TP algorithm. |
OFF | BAT | TP | ON
Note: |
Parameter Type | Use |
---|---|
Client runtime control |
Identifies the Adabas System Coordinator group that is to manage the job. For clustered applications (job types CICS Cluster, IMS, UTM), this name is required to link all the instances of the job in the cluster. If the job is running in a single image (for example, UTM), the name is still required. Refer to the Adabas System Coordinator documentation for more information. |
Parameter Type | Use | Possible Values | Default | ||
---|---|---|---|---|---|
Client runtime control |
Sets the limit for the amount of memory that may be allocated for a single read-ahead operation. If a zero value is input into the online system, the default value will be used.
|
For batch: 0-256 | 64 | ||
For TP: 0-64 | 16 |
Parameter Type | Use | Possible Values | Default | ||
---|---|---|---|---|---|
Client runtime control |
Sets the limit for the number of records that may be processed in a single read-ahead operation. If a zero value is input into the online system, the default value will be used.
|
For batch: 0-8192 | 4096 | ||
For TP: 0-255 | 32 |