gtpm4m1eMessages (System Error and Offline)

ALDR

ALDR0401TERROR DURING BLDL FOR LOADMOD

Explanation: An error occurred when the offline general file loader (ALDR) attempted to call the BLDL service for the LOADMOD data definition name.

System Action: ALDR processing ends abnormally.

User Response: Do the following:

  1. Determine the cause of the problem associated with the LOADMOD file.
  2. Correct the problem.

See TPF System Installation Support Reference for more information about ALDR.

ALDR0901EPROGRAM LOAD MODULE prognamecode LARGER THAN CLMSIZE

Where:

progname
The program name.

code
The version code.

Explanation: ALDR attempted to load a C load module but not enough memory was allocated to process the C load module.

System Action: The program is not loaded and processing continues.

User Response: Do one of the following:

ALDR0902EPROGRAM LOAD MODULE prognamecode I/O ERROR

Where:

progname
The program name.

code
The version code.

Explanation: ALDR attempted to load a C load module. While attempting to read the C load module into memory, an I/O error occurred.

System Action: The program is not loaded and processing continues.

User Response: Do the following:

  1. Determine why the C load module was not created correctly.
  2. Build the C load module again.
  3. See your IBM service representative if the problem is not corrected; you may have a hardware error.

ALDR0903EBAD RECORD IN PROGRAM LOAD MODULE prognamecode

Where:

progname
The program name.

code
The version code.

Explanation: ALDR attempted to load a C load module. While processing the C load module, an incorrect or unexpected record occurred.

System Action: The program is not loaded and processing continues.

User Response: Do the following:

  1. Determine why the C load module was not created correctly.
  2. Build the C load module again.

ALDR0904ESTARTUP CODE MISSING FROM PROGRAM prognamecode

Where:

progname
The program name.

code
The version code.

Explanation: ALDR attempted to load a C load module, but the C load module did not contain the required startup code (CSTRTD or CSTRTL).

System Action: The C load module is not loaded and processing continues.

User Response: Ensure that the ISO-C program or library was built correctly. One of the startup routines (CSTRTD or CSTRTL) was not linked into the C load module correctly.

ALDR0905EDLM ENTRY POINT NOT FOUND IN PROGRAM prognamecode

Where:

progname
The program name.

code
The version code.

Explanation: ALDR attempted to load a C load module. The C load module contained the DLM startup code CSTRTD but no entry point with the 4-character program name was found. A DLM must contain a function with the 4-character name of the program.

System Action: The program is not loaded and processing continues.

User Response: Ensure that the C load module was built correctly.

ALDR0910WATTENTION - C LOAD MODULE nameversion CONTAINS NO LINK MAP DATA - C LOAD MODULE LOADED ANYWAY

Where:

nameversion
The name and version of the C load module.

Explanation: You ran the offline general file loader (ALDR) and specified a C load module that contains no link map data.

System Action: The C load module is loaded with no link map data.

User Response: If you want a link map for this C load module, do the following:

  1. Rerun the C load module build tool (CBLD).
  2. Rerun the offline general file loader (ALDR) to pick up the updated version of the C load module.

See TPF Application Programming for information about the C load module build tool (CBLD) and TPF System Installation Support Reference for information about the offline general file loader (ALDR).