Parameter Types

Controls whether data in a character encoding other than that used by the database/file to hold the data can be cached.

None
All
Single byte ascii
Single byte ebcdic
Double byte ascii
Double byte ebcdic

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
None
All
Single byte ascii
Single byte ebcdic
Double byte ascii
Double byte ebcdic

Controls whether API runtime overrides may be used.

Refer to the Adabas System Coordinator documentation for more information.

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.

Controls whether or not automated buffer restarts should occur.

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.

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.

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.

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.

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
Suspension Limit: 0-255

Coherence Limit: 32
Suspension Limit: 10

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.

If a command time is specified, then any commands that are successfully optimized by Fastpath will have this command time.

This controls where the Fastpath buffer is allocated. If a name is specified the Fastpath buffer is allocated as a dataspace.

The Fastpath buffer can be allocated as a dataspace to alleviate shortages of shared memory, a critical resource. This feature allows you to run with the z/OS setting of USERCSAKEY=NO as recommended by IBM. For backwards compatibility the default remains shared memory (ECSA). For more information on dataspaces please refer to IBM documentation SA22-7614-00, MVS Programming: Extended Addressability Guide, second edition October 2001, which applies to z/OS.

1-8 characters with no embedded blanks.

First character must be #, @ or J-Z.

All others characters must be letters, numbers, #, @ or $.

The name must not begin with "SYSA" through "SYSI".

Defines the direct access optimization settings at the file level for Adabas commands:

• L1: Get ISN

• L3: Read Logical

• L9: Histogram

• S1: Find

• S2: Find Sorted

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 L3,L9,S1,S2 commands, when optimization is set

• ON, field level overrides indicate that commands using that field are not to be optimized.

• OFF, field level overrides indicate that commands using that field are to be optimized.

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.

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.

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.

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.

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:
The values 00:00 and 24:00 have the same meaning; that is, midnight.

This parameter is used to determine the approximate size of the Adabas System Coordinator user pool where

• type "a" represents batch, TSO, CMS, and TIAM jobs

• type "b" represents Com-plete, CICS, CICSplex, IMS, and UTM jobs

Refer to the Adabas System Coordinator documentation for more information.

type a: 2
type b: 1000

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 L3 or L9 commands for the file are not permitted.

For more information on expanded files, refer to the Adabas documentation.

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.

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.

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.

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.

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.

Determines the initial size of all fixed pools managed by the Adabas System Coordinator.

Refer to the Adabas System Coordinator documentation for more information.

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.

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.

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.

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.

Controls whether the optimization statistics for a job are to be saved or printed.

Possible values are:

• None: No information will be displayed or saved.

• Daemon messages: Fastpath performance information will be sent to the operator console by the Adabas Fastpath asynchronous buffer manager using the AFP-0040 to AFP-0042 messages for the named job(s).

• File history: Statistics will be saved in the configuration file.

Note:
File History is only an option for wholly named jobs (it is not an option offered for *default jobs or jobs that use a wildcard).

None

Daemon messages

File history

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.

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 Keep.

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.

Maximum idle time of a session before session recovery is called.

Refer to the Adabas System Coordinator documentation for more information.

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.

Sets the limit for the amount of memory that may be allocated for a single read-ahead operation.

Warning: Large settings require Adabas ADARUN LU and NAB settings to be reviewed to avoid response code 152.

Sets the limit for the number of records that may be processed in a single read-ahead operation.

Warning: Large settings require Adabas ADARUN LU and NAB settings to be reviewed to avoid response code 152.

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 Size is the only value used.

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.

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.

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.

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.

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.

Limits the amount of memory that can be used for read-ahead optimization for a job.

Defines the read-ahead optimization settings at the file level for Adabas commands:

• L1: Get ISN

• L2: Read Physical

• L3: Read Logical

• L9: Histogram

• S1: Find

• S2: Find Sorted

• S8: Process ISN List

• S9: Sort ISN List

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, field level overrides indicate that commands using that field are not to be optimized.

• OFF, field level overrides indicate that commands using that field are to be optimized.

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.

Note:
Default settings are Batch=BAT and TP Monitor=TP.

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.

Indicates the time at which automated restarts should occur.

Entered as hours and minutes in the 24-hour clock.

The default is midnight.

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.

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.

Adabas Fastpath creates sets of direct access command models. This parameter limits the size (in KB) of data items within each set.

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 Minimum Buffer Size.

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:
The values 00:00 and 24:00 have the same meaning; that is, midnight.

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.

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

R (record level): Remove data held in the Adabas Fastpath buffer when update type commands are found

F (file): Remove data for the file held in the Adabas Fastpath buffer when update type commands are found

D (distributed record level): Use only on advice from Software AG.