Object Code Accelerator Manual

Error and Warning Messages
Object Code Accelerator Manual528144-003
8-3
Warning Messages
16
Cause. OCA assumes that procedures do not reference condition codes (the N and Z
bits of the ENV register) before they perform some work (such as an arithmetic
operation or call to a system procedure) that resets the condition codes. OCA’s static
analysis suggests that the named procedures can inherit the condition codes from their
callers. See Diagnosing Register or Condition Code Inheritance on page 5-6 for more
information.
Effect. The translation continues, but would be incorrect if the procedure were to
reference the condition codes before performing some work that would reset them.
Recovery. If you determine that inherit code condition message occurs when there is
no “inherit a code condition”, you can either:
Eliminate this coding practice from your TAL procedure and then rebuild and
reaccelerate
Reaccelerate your program using the INHERITSCC option on the command line.
For example:
oca [/run-options/] input-file, INHERITSCC proc-name
If you determine that inherit condition code message occurs when there is no inherit
code condition, you can direct OCA to ignore the condition by entering the
IGNORE_CC option on the command line. For example:
oca {/run-options/] input-file, IGNORE_CC proc-name
23
Cause. OCA detects an unsupported TNS opcode in one code path. If you have
specified the Forbid_Obsolete_Ops option, OCA cannot complete processing.
Processing can continue with a warning if Forbid_Obsolete_Ops option is not
specified.
Effect. An illegal instruction failure occurs if this code path is executed with the
Forbid_Obsolete_Ops option specified.
Recovery. Verify that there are not unsupported TNS opcodes in any executable code
paths.
36
Warning 16: Procedure <proc-name> in file <filename> inherits
condition codes.
Warning 23: The priv TNS-opcode <opcode> is not supported.
Warning 36: The OUTPUT_FILE name <filename> could not be opened; output
is in zzzz0000
.