This section provides an overview of the enhancements for Adabas Fastpath Version 8.2.2
Statistics displays now show much larger numbers so that limits are raised from around 4 billion to around 10 trillion.
Messages issued by the Fastpath Manager now include the node number (in the Adabas network) of the System Coordinator daemon under which it is running. This helps you understand origin of messages more clearly, especially if you run multiple nodes in a large system. The new message format appears as:
AFP-nnnn-ss xxxxx MESSAGE TEXT
where xxxxx is the node number; nnnn is the message number and ss is the severity.
The fix display in SYSAFP has been enhanced to include a short description of each fix that is applied which helps you to get a better understanding of each fix that is in use.
Internal memory management has been improved at Adabas Fastpath 8.2.2 with remedial action added to counter the effects of defragmentation that can be seen in high volume situations in caches that are active for extended periods.
New read-ahead controls have been introduced to improve read-ahead optimization success rates for both very long sequences and when handling very large record views.
For more information see the Adabas Fastpath Client Runtime Controls in Parameter Maintenance.
Maximum read-ahead unit size controls the maximum amount of memory to be used by each concurrent read-ahead operation. The maximum for one operation in batch is 256k, for online the maximum is 64k.
Note:
This can require review of ADARUN LU and NABS settings to avoid
response 152.
Maximum read-ahead rate is used in conjunction with the read-ahead unit size to control the number of records to be processed in one read-ahead operation. The maximum for batch is now increased to be 8192 from the previous 255 and the maximum for TP is now 255 from the previous 16
For more information see the Adabas Fastpath Client Runtime Controls in Parameter Descriptions.
