Excluded Command Summary

Commands ignored for optimization because job areas were not available.

Increase the buffer parameter maximum jobs.

Only the commands L1, L2, L3, L9, S1, S2, S8, S9, and RC are eligible for optimization.

None required.

Commands ignored because none of the files for the database have been defined for optimization.

Consider using AFPLOOK to sample the database(s) and then create new file parameters.

Commands ignored because the database list area has overflowed.

Indicates a shortage of either local or common storage.

Commands ignored because the file has not been defined for optimization.

None required, or define a new file parameter.

Commands ignored for reasons related to functions that have been temporarily switched off. Most common reason is that a database/file has been disconnected, or a job is in the process of termination.

Use SYSAFP to check whether a database or file is not optimizing.

Commands cannot be processed because a user area is not available.

Indicates a shortage of either local or common storage.

Certain commands are not processed by Adabas Fastpath because of special Adabas control block options; for example, Command IDs set to hex 'FFFFFFFF'.

If the volumes are significant, contact Software AG for assistance.

Commands cannot be processed because a Adabas Fastpath Command ID area is not available.

Indicates a shortage of either local or common storage.

Optimization could not proceed because the command being processed was already set to perform prefetch or multifetch.

None needed, but avoid the conflicting use of read-ahead techniques (Example: ADAPREF and Adabas Fastpath).

Commands were ignored for direct access optimization because the Set ID length exceeded the parameter. A Set ID comprises the Adabas FB+SB+12 bytes.

Review the buffer and file parameters set ID length limit and increase if required.

Although the file is defined for optimization, the descriptor is not included or is explicitly excluded.

None needed, or identify and add the descriptor to the file parameter.

Commands ignored for optimization because Adabas Fastpath does not recognize the syntax in the Adabas format or search buffer.

If the number is significant, contact Software AG for assistance.

Commands ignored for optimization because the status within the command sequence is not known.

None possible.

Count of commands that are not optimized because they are the first in a command sequence and are used for detection of the sequence.

None required.

Count of commands that could not be optimized because the reposition area in the Adabas Fastpath user area was not large enough.

None possible.

Count of commands that could not be optimized because

• other commands were using the direct access file/set; or

• updates were processing data in the set.

If the volume of commands ignored is significant, the buffer parameter set concurrency can be increased by 1.

Count of commands that could not be optimized because

• the start-up process had not completed; or

• a set was switched off or rejected.

None required.

Count of commands not optimized because the direct access set has not yet been created.

The optimization process takes time before sets are created and this count will always show a certain number. If the volumes are significant and continue to increase, the buffer parameter size should be reviewed and increased if necessary.

Count of commands not optimized because, while the set has been found, the required data item is not present.

None required.

Count of commands that could not be optimized because the Adabas record buffer length exceeds the parameter.

Review the buffer and file parameter RB length limit and increase if required.

Count of commands that could not be optimized because no read-ahead memory area was available.

Indicates a shortage of local storage.

Count of commands used to prime the read-ahead memory areas; that is, the commands that Adabas Fastpath sets to multifetch.

None required.

Count of S1,S2,S8,S9 commands that form a command sequence but which Adabas Fastpath cannot optimize.

None required.