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.
Job parameters define which jobs participate in Adabas Fastpath optimization. Some job parameters can override buffer parameter settings when applied to a specific job.
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 | 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 |
---|---|
Job |
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 |
---|---|---|---|
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 |
---|---|---|---|
Job |
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 or Job |
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. Job start and end times are only checked when a job starts. If the current time is between the limits, the job's optimization parameters will be used. No additional checks are made. Note: |
00:00 | 24:00 | none |
Parameter Type | Use | Default |
---|---|---|
Job |
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 | Default |
---|---|---|
Buffer |
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 |
---|---|---|---|
Buffer |
Defines the optimization settings at the buffer level. The following optimization settings can be defined:
If OFF is specified, no optimization will be in effect regardless of any file or job settings. |
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 |
---|---|---|---|
Job |
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
|
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 | 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 | 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 | Minimum | Maximum | Default |
---|---|---|---|---|
job |
Limits the amount of memory that can be used for read-ahead optimization for a job. |
0 | 0 |
Parameter Type | Use | Minimum | Maximum | Default |
---|---|---|---|---|
Job |
This parameter defines the sizes of areas (in k) to be allocated by individual jobs to perform read-ahead optimization using the Adabas multifetch function. The sizes (4 categories) must be defined in ascending order. |
1 | 32 | 4, 8, 16, 32 |
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 |
---|---|---|---|
Job |
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 after how many hours a buffer is to restarted automatically after the last buffer start or restart. If the value is not zero, the buffer is restarted n hours after the last buffer start or restart time. |
0 | 999 | 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 |
This parameter defines the number of free areas to be allocated by the Adabas Fastpath asynchronous buffer manager when a direct access set is expanded. This is also referred to as the growth rate for direct access sets. A file parameter value can be used to restrict the buffer parameter setting. A file parameter with a value of zero is ignored. Note: |
1 | 256 | 8 |
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 or Job |
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. Job start and end times are only checked when a job starts. If the current time is between the limits, the job's optimization parameters will be used. No additional checks are made. Note: |
00:00 | 24:00 | none |
Parameter Type | Use | Possible Values | Default | ||
---|---|---|---|---|---|
Buffer |
This parameter indicates whether synchronous or asynchronous update communication is to be used for remote databases and for remote cluster services instances. When a database is remotely located from an Adabas Fastpath asynchronous buffer manager, it communicates update information by waiting in the nucleus thread for the reply before allowing the update transaction to complete (this mode is called synchronous mode; which is the default). If this parameter is set to N, update communication does not wait for the reply before allowing the update transaction to complete (asynchronous mode).
If this parameter is set to Y for any file in a database, the database defaults to synchronous mode updates. In order to change to asynchronous mode, all files for the database must be set to N. |
Y | N | Y |
Parameter Type | Use |
---|---|
Job |
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 |