This section provides an overview of the installation changes for Adabas Fastpath version 7.4.
The Adabas Fastpath Online Services application, SYSAFP, for Adabas Fastpath version 7.4.2 is distributed in two forms:
a demo version distributed with Adabas version 7.4, and
a fully operable version distributed with Adabas Fastpath version 7.4.2
In previous versions of Adabas Fastpath, there was a requirement to first install the demo version prior to installing the fully operable version. This is no longer the case.
A fully operable SYSAFP application will be available immediately on installing the Natural INPL object supplied on the Adabas Fastpath version 7.4.2 release tape.
Note:
If you install the demo version distributed on the Adabas release
tape after installing the fully operable version, then you must reapply the
fully operable version from the Adabas Fastpath release tape along with any
subsequently applied Adabas Fastpath INPL updates.
The following Adabas Fastpath modules have been retired in order to simplify installation and operation:
AFPDEF
AFPCFG
Adabas Fastpath uses the system file defined in the System Coordinator configuration module.
In previous versions the Command Time When
Optimized parameter was assembled into the Adabas Fastpath
configuration module. This parameter is now defined in Adabas Fastpath job
parameters. The utility F1JPTIME (in batch or online mode) can be used to
update all job parameters with a command time different from the default value
of zero.
If automated operation procedures have been implemented to react to Adabas Fastpath console messages, these should be updated to reflect the change to mixed case.
New job parameters have been added that directly affect the operation of the Adabas System Coordinator:
When defining a job that is part of a clustered application for dynamic transaction routing, you must enter
the name of the Adabas System Coordinator group that is to manage the job; and
an eight-character clustered application service name
You must use the same group name and service name in the job definitions for all jobs or regions that are part of the clustered application.
You can modify job parameters to specify that the Adabas System Coordinator daemon is to manage all client sessions, or just terminal-related client sessions.
Users who run large numbers of background tasks can avoid some overhead by excluding these from SYSCO daemon control because background tasks do not participate in transaction routing.
The UTM startup and shutdown exit ADAUTX introduced with Adabas Fastpath version 7.1 is no longer required for Adabas Fastpath version 7.4 and above.
