Adabas Fastpath optimization and operation is controlled by the following types of parameters:
Buffer parameters control the operation of the Adabas Fastpath buffer.
File parameters control the optimization of specific files. Some file parameters can override buffer parameter settings when applied to a specific file.
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.
Adabas Fastpath parameters can be maintained using Adabas Fastpath Online Services, function Parameter Maintenance.
This section provides a description of each Adabas Fastpath parameter:
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
Buffer |
Controls whether data in a character encoding other than that used by the database/file to hold the data can be cached. |
None |
None |
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
Buffer |
Controls whether data in a character encoding other than that used by the database/file to hold the data can be cached. The Default of this parameter value is defined by the value of the Buffer parameter. |
Default |
Default |
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
Client runtime control |
Controls whether API runtime overrides may be used. Refer to the Adabas System Coordinator documentation for more information. |
Y or N | N |
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
Buffer |
This parameter indicates whether synchronous or asynchronous communication is to be used for retaining cache coherence in remote systems from where the update thread executes. There may be some performance gain by using asynchronous mode but the safest mechanism is synchronous. |
Y | N | Y |
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
Buffer |
Controls whether or not automated buffer restarts should occur. |
Y or N | N |
Parameter Type | Use | Minimum | Maximum | Default |
---|---|---|---|---|
Buffer |
All memory allocations within the Adabas Fastpath buffer are recorded in an index. This parameter is used as a divisor into the buffer size to decide how many items will be expected within the first index block. |
64 | 32768 | 1024 |
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
File |
Records cached by Adabas Fastpath become available to all sessions. Files that are password protected are not normally cached. This field may be set to Y and a password provided in the Password Secure DA-Caching file parameter to allow the caching of such files. Use of this parameter is to be carefully considered and only used where the risk to secure data is acceptable. |
Y or N | N |
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
Buffer |
There is more overhead required by Fastpath to distribute update information across multiple systems (lpars) where distributed caching/optimization for direct-access is used. In periods of intensive update activity this can be counter-productive. These controls allow you to set a threshold where direct-access is suspended for a file if the amount of inter-system update notification breaches a certain level - and then resumed at a later period automatically. This allows Fastpath to react sensibly and dynamically to "floods" of updates. Coherence Limit
The number of distributed update operations to a file per second, as an average over the period of a minute, that will cause the file to temporarily suspend direct access optimization. Suspension Period
The number of minutes that direct-access optimization (etc.) is suspended when the coherence limit is breached. It is automatically resumed after this period. |
Coherence Limit: 0-255 |
Coherence Limit: 32 |
Parameter Type | Use |
---|---|
Client runtime control |
The service name to be used to link together the instances of the application system. For clustered applications (job types CICS Cluster, IMS, UTM), the service name is required to link all the instances of the same application system. If the job is running in a single image (for example, UTM), this name is still required. Refer to the Adabas System Coordinator documentation for more information. |
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 |
---|---|---|---|
File |
Defines the direct access optimization settings at the file level for Adabas commands:
Each command type may have optimization set ON or OFF. In addition, this setting may have up to seven field level overrides which can be achieved by inserting the Adabas two-character field name(s) on the appropriate command line. For
|
ON | OFF | OFF |
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
Buffer |
Expressed as a percentage, this parameter controls the rate at which housekeeping is performed by FASTABM. It is recommended this parameter is only modified when you are instructed to do so by Software AG. |
1-100 | 10 |
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
File |
Expressed as a percentage, this parameter controls the rate at which housekeeping is performed by FASTABM. If a value of 0 is entered, then the Buffer parameter value is assumed. It is recommended this parameter is only modified when you are instructed to do so by Software AG. |
0-100 | 0 |
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
Buffer |
Defines the optimization settings at the buffer level. OFF prevents direct-access optimization altogether. ON enables direct-access optimization according to the file and job parameters that are defined. |
ON | OFF | ON |
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 | Minimum | Maximum | Default |
---|---|---|---|---|
File |
Indicates the time that optimization is to be ended. File start and end times define the period for which the file parameters are to be used for optimization. The start and end times are continuously monitored and the file parameters are switched on/off dynamically. It is also possible to define various file parameters each with a different start and end time period. Note: |
00:00 | 24:00 | none |
Parameter Type | Use | Default |
---|---|---|
Client runtime control |
This parameter is used to determine the approximate size of the Adabas System Coordinator user pool where
Refer to the Adabas System Coordinator documentation for more information. |
type a: 2 |
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
File |
This parameter must be defined (no default) and tells Adabas
Fastpath whether or not the Adabas file is defined as 'expanded'. If this
parameter is set to Y, direct access optimization for
For more information on expanded files, refer to the Adabas documentation. |
Y | N | none |
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
Client runtime control |
Monitor information will be located in shared memory under the control of a COR daemon. A COR group must be specified. Refer to the Adabas System Coordinator documentation for more information. |
Y | N | N |
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
Buffer |
The number of records to be cached in high-speed mode in order to accelerate the learning period of the direct-access algorithm (per set). Once this number is reached the normal asynchronous caching mechanism is used. |
0-255 | 32 |
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
Buffer |
The number of sets to be created in high-speed mode in order to accelerate the learning period of the direct-access algorithm. Once this number is reached the normal asynchronous mechanism is used. |
0-255 | 25 |
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 |
---|---|---|---|
Buffer |
Defines the optimization settings for these commands at the buffer level. OFF prevents optimization altogether. ON enables optimization according to the file and job parameters that are defined. |
ON | OFF | ON |
Parameter Type | Use | Default |
---|---|---|
Client runtime control |
Determines the initial size of all fixed pools managed by the Adabas System Coordinator. Refer to the Adabas System Coordinator documentation for more information. |
256 |
Parameter Type | Use | Minimum | Maximum | Default |
---|---|---|---|---|
Buffer |
All free memory in the Adabas Fastpath buffer is classified into a fixed-size freespace index. This parameter sets the number of different freespace categories (entries) in the index. |
16 | 32768 | 512 |
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
Client runtime control |
If External Monitoring is on, then the COR group must be specified. If the group is not active, then External Monitoring can not occur. Refer to the Adabas System Coordinator documentation for more information. |
Group Name | none |
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
Buffer |
Defines the optimization settings for this command at the buffer level. OFF prevents optimization altogether. ON enables optimization according to the file and job parameters that are defined. |
ON | OFF | ON |
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
File |
Controls the activation of file parameters. If the setting is OFF, the file parameters are inactive. The setting must be changed to ON and SYSAFP must be used to stop/start the file. |
ON | OFF | ON |
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
Client runtime control |
Controls the printing of optimization statistics for a job. If this parameter is set to YES, at the end of a job, optimization statistics are output to the operator console by the Adabas Fastpath asynchronous buffer manager using the AFP-0040 to AFP-0042 messages for the named job(s). |
YES | NO | NO |
Parameter Type | Use | Minimum | Maximum | Default |
---|---|---|---|---|
Buffer |
Determines the number of days that the statistics log is to be retained. When automatic statistic logging is enabled (see the parameter Log), any entries that are younger than n days will be kept for each buffer in the Configuration file. Older entries will be subject to eventual overlay. |
1 | 32768 | 30 |
Parameter Type | Use | Minimum | Maximum | Default |
---|---|---|---|---|
Buffer |
Controls how often the statistics log is to be written (specified in minutes). A statistics log record is written to the Adabas Fastpath
configuration file by the Adabas Fastpath asynchronous buffer manager every
n minutes. A value of 0 implies no automatic logging but does not prevent
logs being requested by using the Adabas Online Special Services function. See
also the parameter |
0 | 32768 | 60 |
The use of these parameters is described in the descriptions of the following parameters:
Parameter Type | Use |
---|---|
Buffer |
Determines type of session management to be used for clustered application sessions. For clustered applications (job types CICS Cluster, IMS, UTM) where dynamic user movement is possible, you can choose to manage only terminal tasks. This is more efficient and is possible when non-terminal tasks do not move between regions in a clustered application. Refer to the Adabas System Coordinator documentation for more information. |
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
Client runtime control |
Maximum idle time of a session before session recovery is called. Refer to the Adabas System Coordinator documentation for more information. |
0- 2147483647 | none |
Parameter Type | Use | Minimum | Maximum | Default |
---|---|---|---|---|
Buffer |
This parameter indicates the maximum number of optimized jobs which are to be run concurrently. The corresponding number of job areas are then reserved. If an area is not available, additional (concurrent) jobs are not optimized. TP Monitors such as CICS, Com-plete, and Shadow require only a single job area. UTM and IMS/DC require a job area for each task being used (plus 1). TSO, TIAM, and CMS require a job area for each user. Batch jobs use one area each. |
1 | 9999 | 12 |
Parameter Type | Use | Minimum | Maximum | Default |
---|---|---|---|---|
Buffer |
Defines the minimum buffer memory size (in k) to be requested from the operating system for the Adabas Fastpath buffer. If the value is 0, the buffer parameter |
0 | value | 0 |
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
File |
Used in combination with the Cache Secure File file parameter, this field allows for specifying the 8-character password required for access to the secured file. |
1-8 char | 0 |
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
Buffer |
Defines the optimization settings for this command at the buffer level. OFF prevents optimization altogether. ON enables optimization according to the file and job parameters that are defined. |
ON | OFF | ON |
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
Buffer |
Defines the optimization settings for this command at the buffer level. OFF prevents optimization altogether. ON enables optimization according to the file and job parameters that are defined. |
ON | OFF | ON |
Parameter Type | Use | Minimum | Maximum | Default |
---|---|---|---|---|
Buffer or File |
Restricts the size of buffer used for evaluating data for direct access optimization. A file parameter value can be used to restrict the buffer parameter setting. A file parameter with a value of zero is ignored. |
16 | 32768 | 1024 |
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
Buffer |
Defines the optimization settings at the buffer level. OFF prevents read-ahead optimization altogether. ON enables read-ahead optimization according to the file and job parameters that are defined. |
ON | OFF | ON |
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 |
---|---|---|---|
File |
Defines the read-ahead optimization settings at the file level for Adabas commands:
Each command type may have optimization set ON or OFF. In addition, this setting may have up to seven field level overrides which can be achieved by inserting the Adabas two-character field name(s) on the appropriate command line. When optimization is set
|
ON | OFF | OFF |
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 | Minimum | Maximum | Default |
---|---|---|---|---|
Buffer |
Indicates frequency of automated buffer restarts. If the value is not zero, it indicates the minimum number of hours that must elapse since the last buffer start/restart before auto-restart may occur. |
0 | 999 | 0 |
Parameter Type | Use | Minimum | Maximum | Default |
---|---|---|---|---|
Buffer |
Indicates the time at which automated restarts should occur. Entered as hours and minutes in the 24-hour clock. The default is midnight. |
0 | 23:59 | 0 |
Parameter Type | Use | Minimum | Maximum | Default |
---|---|---|---|---|
Buffer or File |
This parameter indicates the number of concurrent retrievals which can occur from each set of direct access data created by Adabas Fastpath. A file parameter value can be used to restrict the buffer parameter setting. A file parameter with a value of zero is ignored. |
1 | 16 | 2 |
Parameter Type | Use | Minimum | Maximum | Default |
---|---|---|---|---|
Buffer or File |
Adabas Fastpath uses direct access set identifiers which contain search and format data for direct access command models. This parameter limits the size of data items within each set. A file parameter value can be used to restrict the buffer parameter setting. A file parameter with a value of zero is ignored. |
256 | 16384 | 1024 |
Parameter Type | Use | Minimum | Maximum | Default |
---|---|---|---|---|
File |
Adabas Fastpath creates sets of direct access command models. This parameter limits the size (in KB) of data items within each set. |
0 | 0 |
Parameter Type | Use | Minimum | Maximum | Default |
---|---|---|---|---|
Buffer |
This parameter defines the size (in k) of the memory to be
allocated to the Adabas Fastpath buffer. When requesting the memory from the
operating system, the value actually obtained depends on the setting of the
parameter |
1MB | 4MB |
Parameter Type | Use | Minimum | Maximum | Default |
---|---|---|---|---|
File |
Indicates the time that optimization is to be started. File start and end times define the period for which the file parameters are to be used for optimization. The start and end times are continuously monitored and the file parameters are switched on/off dynamically. It is also possible to define various file parameters each with a different start and end time period. Note: |
00:00 | 24:00 | none |
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. |
The use of these parameters is described in the descriptions of the following parameters:
Parameter Type | Use | Possible Values | Default |
---|---|---|---|
File |
This parameter is used to control how update commands are to be processed for a file. The possible settings are:
N (none): Ignore update type commands for data held in the
Adabas Fastpath buffer |
N | R | F | D | R |