This section describes the preparation for and installation of Adabas Fastpath on VM systems.
The installation tape contains the AFPvrs.TAPE dataset, which contains the AFP installation objects.
Also see the Report of Tape Creation that accompanies the installation tape.
The Adabas System Coordinator must be installed prior to the installation of Adabas Fastpath. See the Adabas System Coordinator documentation for detailed information.
Once the required System Coordinator components have been installed, you can proceed to install Adabas Fastpath. The following checklist identifies the steps necessary to complete the installation:
| Step | Description |
|---|---|
| 1 | Restore the Adabas Fastpath libraries from the installation tape |
| 2 | Prepare SYSAFP |
| 3 | Enable the client process |
| 4 | Enable the Adabas server process |
| 5 | Prepare the asynchronous buffer manager |
| 6 | Verify the installation |
Following is the general Adabas Fastpath installation procedure. The sample EXEC procedures contain specific information about each job. These can be viewed simply by entering the procedure name without parameters.
Use TAPE LOAD to unload the product files.
The Adabas Fastpath Online Services (SYSAFP) objects are delivered on the Adabas Fastpath distribution tape.
Install the INPL objects as standard. If an I001 dataset is supplied, install this as well.
Define SYSAFP and SYSMWvrs to Natural Security, with a start-up program named MENU. Restrict the application to authorized personnel.
Use the following parameter to define the Natural session where SYSAFP is to be used:
LFILE=(152,dbid,fnr<,passw><,ciph>)
where dbid and fnr indicate the location of the Adabas System Coordinator configuration file.
Alternatively, assemble the Natural parameter module with
NTFILE,ID=152,DBID=nnn,FNR=nnn
To enable the Adabas Fastpath client process
for the Adabas System Coordinator:
make the modified Adabas link module available;
make the generated configuration module CORCFG available; and
make the Adabas System Coordinator modules available.
for Adabas Fastpath:
make the Adabas Fastpath modules available.
To enable the Adabas Fastpath database process
for the Adabas System Coordinator:
make the Adabas System Coordinator modules available.
for Adabas Fastpath:
set the Adabas parameter ADARUN
FASTPATH=YES; and
make the Adabas Fastpath modules available.
Note:
An unmodified ADALNK must be available to the database in preference
to the ADALNK created during the installation of the System Coordinator.
The asynchronous buffer manager (ABM) runs as an optional service within the Adabas System Coordinator daemon.
To enable the ABM for the System Coordinator daemon:
make the generated configuration module CORCFG available;
set the daemon service startup parameter
PRODUCT=AFP; and
make the Adabas Fastpath modules available.
For more information, refer to the Adabas System Coordinator documentation.
The Adabas Fastpath global buffer is a shared memory area that is used by all Adabas and CMS user virtual machines that are defined to Adabas Fastpath. For this reason, it must be defined as a shared, read-write saved segment. Use the DEFSEG command to define the name, address, and size of the segment. The address and size are defined as virtual page numbers. Here is an example:
DEFSEG AFPBUF01 2200-25FF SN SAVESYS AFPBUF01
This will define a 4-megabyte buffer (1000*4K pages), starting at virtual address 02200000. The starting page number should locate the area outside the machine size definition for all CMS users and the Adabas virtual machines.
The name selected for the saved segment must be used as the memory pool name when adding the buffer parameter in SYSAFP (see Parameter Maintenance for more information about buffer parameters).
The Adabas Fastpath buffer runs as an optional service within the Adabas System Coordinator daemon (in z/VM, this is currently the only use of the System Coordinator daemon). You must define a CMS virtual machine where the daemon will run.
Adabas Fastpath buffers operate as members of a System Coordinator Group. The member name is the name of the System Coordinator daemon virtual machine under which this Adabas Fastpath buffer operates.
For z/VM, it is a requirement of Adabas Fastpath that the System Coordinator Group name must also be the name of the daemon virtual machine. This name must be at least 6 characters in length. If you wish, you can use the name of the buffer saved segment as the group and member name, but this is not mandatory. For example:
System Coordinator Group Name: AFPBUF01
System Coordinator Member: AFPBUF01 (must be same as Group
name)
Segment (“Memory Pool”): AFPBUF01 (can be a different
name)
System Coordinator Groups are defined with the Online Services SYSCOR application, function Parameter Maintenance.
A sample EXEC for starting the System Coordinator Daemon is supplied with the System Coordinator installation files. The EXEC is called SYSCO EXEC.
The sample SYSCO EXEC assumes a read-write minidisk is available as file mode A. If your A disk is an SFS directory, you should make the following changes to the EXEC:
From:
DATADEF DDCARD,DSN=SYSCO.CONTROL,DISP=OLD,MODE=* DATADEF DDPRINT,DSN=SYSCO.DDPRINT,MODE=A
To:
DATADEF DDCARD,FNAME=SYSCO,FTYPE=CONTROL,DISP=OLD, MODE=*,UNIT=SFS,DSN=your.directory.name DATADEF DDPRINT,FNAME=SYSCO,FTYPE=DDPRINT, MODE=A,UNIT=SFS,DSN=your.directory.name
The DATADEF command is described in the
Adabas Installation documentation (see DATADEF File
Assignments in the VM installation section).
Use the procedure described in section Verifying the Installation to ensure that the installation has been successful.
