This section contains information which you should review prior to performing Adabas Fastpath installation.
The Adabas System Coordinator daemon requires an Adabas Fastpath license file in order for Adabas Fastpath to make its services available.
Note
If the Adabas Fastpath license file is not available or is erroneous, client jobs that
require the services of Adabas Fastpath will not be able to connect to the Asynchronous
Buffer Manager and will not be able to benefit from command optimization.
The Adabas Fastpath license file can be transferred to the mainframe in the same way as the Adabas license and made available as a load module with the name AFPLIC. Alternatively, the license file can be referred to by a "DDLAFP" DD statement in the COR daemon’s job/started task. This is a fallback in case the AFPLIC license load module cannot be loaded.
For installation information regarding the Adabas Fastpath license file, refer to the section Installation Procedure Steps.
For general information on Adabas licensing procedures, license check software, and license files, refer to the Mainframe Product Licensing topic in the Adabas for Mainframes documentation.
We recommend that you use a single location (file) for all Adabas Fastpath modules and that you make this file known to the various databases, TP systems, and batch jobs that are to use Adabas Fastpath.
The Adabas Fastpath Online Services service Special Services, Coordinated Newcopy option can be used to simplify the application maintenance. This function can be used to apply maintenance dynamically to all jobs that are using Adabas Fastpath. Again, if there is one location where Adabas Fastpath modules can be maintained, the advantages offered by Coordinated Newcopy are enhanced.
Adabas Fastpath uses a buffer area for storing and maintaining optimization information.
This buffer is managed by the Adabas Fastpath asynchronous buffer manager (ABM) which runs as an optional service within the Adabas System Coordinator daemon.
The buffer is defined and maintained using the Adabas Fastpath online service SYSAFP, with the definitions residing in the Adabas System Coordinator configuration file. Each Adabas Fastpath buffer requires file optimization parameters to be defined, which can be copied among multiple buffers as required.
The Adabas System Coordinator EXPORT and IMPORT tool may also be used to maintain Adabas Fastpath buffer and file definitions. Refer to the Adabas System Coordinator documentation for more information about this tool.
The following recommendations are given in relation to the use of multiple Adabas Fastpath buffers:
Adabas Fastpath buffers that optimize commands issued by clients operating within a CICSplex should have identical buffer and file definitions.
In a multi-LPAR environment, to minimize network traffic and avoid the need for multiple configuration files, the configuration file should reside on an Adabas Cluster Services database with a nucleus instance available on each LPAR.
To enable the Adabas Fastpath Asynchronous Buffer Manager within an Adabas System Coordinator daemon:
make the generated configuration module CORCFG available;
set the Adabas System Coordinator daemon runtime parameter
PRODUCT=AFP; and
make the Adabas Fastpath load library available.
For more information, refer to the Adabas System Coordinator documentation.
Before you start to install Adabas Fastpath, you should identify the following resources which will be required for installation:
a unique Node ID that is to be used by the Adabas System Coordinator daemon which provides the service for the Adabas Fastpath Asynchronous Buffer Manager.
a DBID and FNR for the configuration file that is shared by the Adabas System Coordinator, Adabas Fastpath, and Adabas Vista.
TP system library names.
Adabas library names.
For the requirements regarding the use of an unmodified ADALNK batch link routine refer to the corresponding information in the Before You Install section of the Installation chapter for Adabas System Coordinator.
If you are installing under CICS, the Fastpath modules can be loaded either from the DFHRPL or the STEPLIB libraries. We recommend that you use DFHRPL. If you are not using the CICS program autoinstall feature, you will need to define the Fastpath Client modules (AFPKRN, AFPPXY) and the configuration module (CORCFG) to CICS. All of the modules should be defined with the following characteristics: Language: Assembler ; RELoad :No ; DAtalocation: Any ; EXECKey : User.
Please also refer to the Adabas System Coordinator Installation documentation for similar CICS requirements for that software component.