Accelerator Manual (G06.27+, H06.04+, J06.03+)
Error, Warning, and Note Messages
Accelerator Manual—527303-003
9-14
Warning Messages
38
Cause. The named procedure contains a SETE instruction that sets the T-bit in a
procedure for which the OvTrap_Off option was specified.
Effect. You probably do not want to use the OvTrap_Off option for this procedure since
the code explicitly turns overflow trapping on. The Accelerator honors the OvTrap_Off
option when generating the accelerated code, which means 16-bit overflow might not
be detected in that procedure. If that procedure requires overflow trapping, then the
expected run-time trap might not occur.
Recovery. Reconsider the option setting. If the procedure runs with traps enabled,
specify the OvTrap_On option for that procedure. Only specify the OvTrap_Off option if
you are positive that 16-bit overflow cannot occur in a procedure.
39
Cause. The Accelerator cannot create an output file with the specified name because
a file with that name was either in use or could not be purged.
Effect. The Accelerator created an output file with a temporary file name of the form
ZZZZnnnn. The Accelerator listing shows the actual output file name.
Recovery. Rename the temporary file created by the Accelerator when the desired file
name becomes available.
40
Cause. The Accelerator processed a TAL program with CODE statements containing
unimplemented opcodes. Unimplemented opcodes are not generated by the TAL
compiler for language statements. This message can be spurious if the Accelerator
mistakes a region of data for code.
Effect. A program traps if it executes an unimplemented opcode on both TNS and
TNS/R systems.
Recovery. If the program contains unimplemented opcodes that can be executed, then
modify the source code to eliminate the unimplemented instructions.
Warning 38: The following SETE instructions set the T bit
while OvTrap_Off was selected:
'<proc name>' at offset(s): <address>
Warning 39: The Accelerator was not able to create an output
file with the requested name.
Warning 40: Unimplemented opcodes appear in the following
procedure(s): <opcode> in procedure '<proc name>'
at offset <address>