This section provides an overview of new features for Adabas Fastpath Version 8.2.2
The Fastpath buffer can now be allocated as a dataspace to alleviate shortages of shared memory, a critical resource. This new feature now 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). To use a dataspace set a dataspace name in the Fastpath Buffer Parameters. For more information on dataspaces please refer to the IBM documentation SA22-7614-00, MVS Programming: Extended Addressability Guide, second edition October 2001, which applies to z/OS.
Fastpath Client Runtime Controls are now enhanced to allow end-of-job (job-step) statistics to be saved as history in the configuration file. The existing feature to show end-of-job statistics as messages within the System Coordinator console messages remains as a choice too, and also remains as the default (where used) for compatibility purposes. Statistics for up to the last sixteen executions can be kept on file (see the Job History section in Maintaining Client Runtime Controls for more detail).
Note:
More data stored in the configuration file will affect the space
used. You should increase the space for the file as necessary.
Direct access optimization now also applies to L3
and L9 commands with a from/through
range (“S” operator in the search buffer syntax).
Console messages may be issued by Adabas Fastpath in client jobs, in databases and in System Coordinator daemons. Until now the console has been the only place where you can see them but now you can direct them to an alternate destination. You can accumulate messages as they have been in the past or you can now accumulate them in a file associated with individual client jobs or collect messages for all client jobs into a file in the Coordinator daemon.
The new Adabas System Coordinator Runtime messages client runtime control allows client messages to be routed to:
The console.
This is compatible with previous releases.
A local DDMSG file in the client job.
The JCL for the job must be altered to accommodate this option.
A DDMSG defined by the System Coordinator daemon.
The daemon JCL must be altered.
Both the console and a DDMSG file (either local or defined by the System Coordinator daemon).
The new Adabas System Coordinator daemon group setting Runtime messages – databases allows messages to be routed to:
The console.
This is compatible with previous releases.
A local DDMSG file in the database.
The JCL for the job must be altered to accommodate this option.
Both the console and a local DDMSG file.
The new Adabas System Coordinator daemon group setting Runtime messages – daemon allows messages to be routed to:
The console.
This is compatible with previous releases.
A local DDMSG file in the daemon job.
The JCL for the job must be altered to accommodate this option.
Both the console and a local DDMSG file.
You can now display all Fastpath activities for every job in the system. All you have to do is configure the client runtime controls to make the activity details available to the Adabas System Coordinator group running in your system. Refer to the Adabas System Coordinator documentation for more details on how to set this up and refer to the section Adabas System Coordinator online administration here in Fastpath for the information that is made available.
You can now display all Fastpath activities for every session in the system. All you have to do is configure the client runtime controls to make the activity details available to the Adabas System Coordinator group running in your system. Refer to the Adabas System Coordinator documentation for more details on how to set this up and refer to the section Adabas System Coordinator online administration here in Fastpath for the information that is made available.
Fastpath is fully compliant with the new memory management options introduced with Adabas System Coordinator. These options reduce the amount of memory consumed and also allow advanced crash-recovery capabilities for compliant TP systems such as CICS. Refer to the Adabas System Coordinator documentation for more information on the types of operations you can choose.
Configuration objects can now be exported in XML form. For more information please refer to the Adabas System Coordinator documentation.
Adabas SAF Security sites who also use Fastpath can now secure the use of Fastpath online administration. For more information on how to implement this refer to the Adabas SAF Security documentation.
Adabas System Coordinator 8.2.2 provides a unified trace feature that allows consistent diagnosis of client, database and daemon jobs configured to use Adabas System Coordinator and any of its related products: Adabas Fastpath, Adabas Transaction Manager, Adabas Vista and Adabas SAF Security.
The SYSAFP Natural application has been enhanced:
Better handling of configuration modification. All configuration modification screens now allow PF5 to commit changes and if you make any changes without pressing PF5 you are prompted to commit them with PF5 or exit with PF3.
The Display line command has been removed. Use Modify to view
configuration objects. If you use SAF security to protect
SYSAFP, you will need
READ access to enter the modify screen and
UPDATE access to commit modifications.
PF6 (Top) and
PF9 (Bot) have been removed. Their functionality is
replaced by entering m on the command line and pressing
PF7 or PF8
respectively.
PF9 (More) is now used to access additional configuration screens for those objects such as runtime controls and daemon groups which have more than one configuration screen.
PF11 (Prods) has been enhanced so that it automatically cycles around the available products.
Compliance for running in z/OS zIIP mode is introduced. This also requires use of the base Adabas maintenance ADA824.LX08 (or equivalent for other releases of Adabas).
