Accelerator Manual (G06.27+, H06.04+, J06.03+)

Error, Warning, and Note Messages

Accelerator Manual—527303-003

9-13

Warning Messages

In the case of the C library problem described previously, the accelerated code might

cause a run-time trap or invalidate user variables.

Recovery. For TAL programs with procedures that in fact inherit registers, you have

two options:

1. Modify the source code to eliminate the implicit parameter passing through the

2. Accelerate the program again, supplying a InheritsRn or ReturnsRn option.

C programs that were bound with a C30 version of CLIB released before 01DEC90

must be bound again with the 01DEC90 or later version. You can do either a full or

replacement bind of CLIB^EXTFNAME^TO^INTFNAME. You must then accelerate the

program again.

You can safely ignore this message in all other cases.

Cause. The Accelerator processed a TAL program with CODE statements containing

obsolete opcodes. Obsolete opcodes do not appear in normal high-level programs.

Effect. A programs trap if it executes an obsolete opcode on both TNS and TNS/R

systems. This message can be produced spuriously if the Accelerator mistakes a

region of data for code.

Recovery. If the program contains obsolete opcodes that can be executed, then

modify the source code to eliminate the obsolete instructions.

Cause. The input file has no main procedure, but the Accelerator thinks that it is a user

code program.

Effect. If the accelerated program is actually a user library, then the accelerated code

is incorrect. If the accelerated program is indeed user code without a main procedure

(for example, a system process), then the accelerated code is correct.

Recovery. If the program is not user code, then specify the correct code space option

(UL, SC, SL) and accelerate the program again.

Warning 35: Obsolete opcodes appear in the following

procedure:

<opcode> in procedure '<proc name>' at offset <address>

Warning 37: UC option in effect, but input file has no main

procedure.