Code

Description

C03

Specified program could not be found.

C04

Bad Common file alignment. Common files are specified in the new program that were not specified (in those same positions in the UDA) in the original program.

C05

Incompatible program. Both programs must be compiled with compatible compiler versions.

C06

Invalid program file format. Re-compile the program.

C07

Insufficient memory resources exist to load the program.

C08

Could not create ROLLOUT file. Check rights, space utilization and number of file handles available

C09

Common data misalignment or problem with GLOBAL data variables where data types and size must be the same. The following subcodes are possible:

01: Global data area overflow.

10: Misaligned common. Module and variable address are returned as additional information in the error variable.

11: Invalid data type encountered (Possible data corruption). Module and variable address are returned as additional information in the error variable.

20: Global variable declared size different from already loaded variable. Module and variable address are returned as additional information in the error variable.

21: Global variable defined as different type from already loaded variable. Module and variable address are returned as additional information in the error variable.

22: Global array variable has a different number of variables from currently loaded array variable. Module and variable address are returned as additional information in the error variable.

25: Invalid global file control word for a FILELIST. Global memory has been corrupted for unexplained reasons.

26: Unable to establish a global FILELIST primary file. Insufficient memory.

C11

Null variable used for program name or name too long.

C13

Unable to maintain spooling across program chain, spooling disabled.

C15

LOADMOD module may not be loaded or a procedure is not defined within a specified LOADMOD module. The following subcodes are provided:

00: Unable to locate object file or procedure name.

04: Unable to translate object code file byte order to proper format. One possible cause is corrupted object code file.

09: Insufficient allocated memory available to load the module. Use the '-mNNNNNN' runtime command line option to increase the allocated memory. The value specified is in bytes. If the option is not specified, the runtime default is 1,024,000 bytes.

12: The minimum runtime version specified in the object code file is incompatible with the runtime version executing.

13: The load module forward/reverse order format is invalid for the runtime being used. This error could indicate that the object code file is corrupted.

17: Unable to seek to locations within a load module. The likely cause is an object code file with incorrect information in the header.

18: Unable to read a specified number of bytes from the load module. Possible causes are a module that was compiled with errors or a corrupted module is being used.

21: External name null.

22: Internal name greater than fifty (50) bytes long.

23: User procedure not provided.

24: CALLS name variable null.

25: CALLS procedure not found. Possible causes of the error can be as follows:

a) The routine specified by the user program does not exist in any loaded module.

b) The case for the routine name specified by the user program does not match the intended name of the routine name compiled into the load module. See the ZS compiler option and the runtime PLB_CASE keyword descriptions to help resolve errors caused by case sensitivity differences.

c) The target of the CALL/CALLS target must be a subroutine declared as a ROUTINE, LROUTINE, FUNCTION, LFUNCTION or PROCEDURE instruction.

26: Unable to resolve external procedure.

27: Unable to locate or open load module in read only mode.

28: An invalid or corrupted program data variable was detected as a LOADMOD module was being loaded.

39: When using dynamic load modules, there is insufficient memory available to load the module. (9.7C)

C16

Insufficient memory available to load the Auto Load DIM variables. The Auto Load DIM variables are compiled into a program when the 'DIM ^size' syntax is used explicitly or implicitly in a program.

C17

An invalid or corrupted program data variable was detected as a program module was being loaded.

C18

The data variable translation to reverse the byte order failed. The extended error information give a relative translation data offset to help identify a range where the error occurs. Additional informat is available for subcodes as follows:

30: An error occurred while processing the program data variables in the UDA.

31: An error occurred while processing a program global data variable.