Adabas Fastpath Online Services can be used to display commands excluded from optimization by exclusion category.
| Unsuitable command type | |
| Explanation |
Command code cannot be optimized. |
| Action |
None. |
| Disqualified | |
| Explanation |
Commands ignored because the database/file/command code or descriptor has not been defined for optimization. |
| Action |
None required or define a new database/file parameter, or remove command code/exclusion from file definitions. Define optimization for these if you believe there is sufficient benefit. |
| Optimization was disabled | |
| Explanation |
The most common reason is that a database/file has been disconnected, or a job is in the process of termination. It is also possible that a job has been unable to connect or the buffer is down. |
| Action |
Use SYSAFP to check whether a database or file is not optimizing.
Consider increase to the |
| Multi-fetch was already set | |
| Explanation |
Read-ahead optimization was not possible because the command was already set to perform prefetch or multifetch. |
| Action |
Consider if Fastpaths’ totally dynamic read-ahead is more flexible than specific programming. |
| Command details exceed Set-id limit | |
| Explanation |
Commands were ignored for direct access optimization because the Set ID length exceeded the limit. |
| Action |
Review the buffer and file parameters |
| Record Buffer exceeds the limit | |
| Explanation |
Commands that could not be optimized because the Adabas record buffer length exceeds the limit. |
| Action |
Review the buffer and file parameter |