Accelerator Manual (G06.24+, H06.03+)

Accelerator Manual—527303-002

9-1

9 Error, Warning, and Note

Messages

The Accelerator issues an error message when it finds a code construct that it cannot

accelerate, or when it cannot understand input options or input file format. The

Accelerator does not produce an executable object file if it finds error conditions. You

must resolve all error conditions to accelerate your program successfully.

This section defines Accelerator errors, warnings, notes. It also describes recovery

procedures, if appropriate, from problems that the Accelerator finds.

•

Note Messages on page 9-1

•

Warning Messages on page 9-9

•

Error Messages on page 9-15

The Accelerator issues a warning message when it finds a code construct, such as

unexpected inheritance of condition codes, for which it might have produced incorrect

code. Check all warning messages to make sure that they are harmless before

declaring your program successfully accelerated.

The Accelerator issues a note message (if you have used the Notes option) when it

finds a code construct that might cause the program to make a transition into TNS

code. Notes never report a problem with the accuracy of the Accelerator’s optimization;

notes relate to performance only.

Error, warning, and note messages appear in summary form in the Accelerator output

listing. You can direct the Accelerator to suppress specific notes or warnings for a

particular procedure by using the SuppressMsg option.

Refer to Controlling Accelerator Messages on page 4-14 for details on using the Notes

and SuppressMsg options.

Note Messages

The Accelerator issues notes when it finds a code construct that might cause the

program to make a transition into TNS code. Notes never report a problem with the

accuracy of the Accelerator’s optimization; notes relate to performance only. Notes are

numbered 1 through 20.

Cause. The Accelerator was unable to determine the return value size for calls to the

named external procedures. It guessed the values shown, based on the context of the

call.

Note 1: The Accelerator was not able to determine return value size of the

following external procedures: <proc name>; Guessed return size <value>,

<number> times;