Oninit
Talk to an expert →

Informix Error -9063: The user function name, defined by the user in the DEFINE statement of ACE, could not be found in the C function definition table userfuncs in the user's C static data area.

Cause and resolution

The user function name, defined by the user in the DEFINE statement of ACE, could not be found in the C function definition table userfuncs in the user's C static data area.

The DEFINE section of the report contains a FUNCTION statement indicating that an external function name would be linked with the report. (The ESQL/C manual covers the use of external C functions with ACE reports and PERFORM screens.) However, the name and address of each such function must appear in a static array that is named userfuncs. That array, along with the computer code of the external functions, is linked with a custom version of ACEGO. Because name did not appear in the array, ACEGO cannot call it.

Check that you are executing the correct, customized version of ACEGO (the original version of the program has no external functions linked to it). Check to see if name is correctly spelled. Then examine the source of the C functions to make sure that the userfuncs array is defined correctly and that it contains an entry for name.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-9063 fires when a FUNCTION statement in the DEFINE section names an external C function that doesn't appear in the userfuncs static array ACEGO was linked against — per the official guidance.

  1. Running the unmodified/original ACEGO, which has no external functions linked, per the official guidance — the first named cause.
  2. A misspelled function name, per the official guidance — the second named cause.
  3. The userfuncs array not correctly defined, or missing an entry for the function, per the official guidance — the third named cause.
Solutions / Resolution
  1. Check that the correct, customized version of ACEGO is being executed, per the official guidance.
  2. Check that the function name is spelled correctly, per the official guidance.
  3. Examine the C function source to make sure userfuncs is defined correctly and contains an entry for the function, per the official guidance.
Examples
N/A

No specific triggering statement is documented beyond the named function being absent from userfuncs.

Diagnostic Checks
  1. Confirm which ACEGO binary is on the execution path, and check the userfuncs array in the linked C source for a correctly spelled entry.
Related Errors / Related Topics

No closely related error codes are cross-referenced for -9063 in this set yet.

An external C function named in the report's DEFINE section wasn't found in the linked userfuncs array — check the ACEGO binary and the userfuncs source.