gtpm4m15Messages (System Error and Offline)

0AD000-0ADFFF


0ADB00

Program: CUDX

Error Message: INSUFFICIENT STORAGE TO ALLOCATE UCAB

Explanation: The MALOC macro returned an error condition when requesting storage for the universal debugger common anchor block (UCAB).

System Action: The following occurs:

User Response: See your IBM service representative to report the problem.


0ADB02

Program: CUD2

Error Message: IRRECOVERABLE ERROR IS DETECTED IN VISUALAGE ASSEMBLER DEBUGGER FOR TPF, ERROR CODE: error code

Where:

error code
The error code, which is defined in the i$udbg.hpp C/C++ header file.

Explanation: An unexpected and catastrophic system error was detected in the TPF Assembler Debugger for VisualAge Client subcommand handler.

System Action: The entry control block (ECB) exits.

User Response: See your IBM service representative to report the problem.


0ADB03

Program: CUD1

Error Message: UNSUPPORTED EVENT IS RECEIVED AT VISUALAGE ASSEMBLER DEBUGGER FOR TPF

Explanation: An unsupported event was received by the TPF Assembler Debugger for VisualAge Client event handler.

System Action: The entry control block (ECB) exits.

User Response: See your IBM service representative to report the problem.


0ADB04

Program: CUDA

Error Message: INCORRECT PARAMETER DETECTED IN function FUNCTION

Where:

function
One of the following:

UDUT_EtoA is the EBCDIC-to-ASCII conversion function.

UDUT_AtoE is the ASCII-to-EBCDIC conversion function.

Explanation: The calling function passed an incorrect parameter to the conversion function.

System Action: The entry control block (ECB) exits.

User Response: See your IBM service representative to report the problem.


0ADB05

Program: CUD2

Error Message: THE REQUESTED OPERATION IS NOT SUPPORTED

Explanation: The TPF Assembler Debugger for VisualAge Client front end requested an operation that the back end does not support.

System Action: The TPF Assembler Debugger for VisualAge Client ignores the request.

User Response: None, unless the TPF Assembler Debugger for VisualAge Client front end stops. If this occurs, see your IBM service representative to report the problem.


0ADB0A

Program: CUDR/CCVAGE

Error Message: BAD INPUT TO ASSEMBLER DEBUGGER RESUME CALL

Explanation: The resume at function for the TPF Assembler Debugger for VisualAge Client was called to restart an application that was being debugged, but the control information in the incoming debugger message block was not correct.

System Action: The entry control block (ECB) exits.

User Response: See your IBM service representative to report the problem.


0ADB0B

Program: CUDR/CCVAGE

Error Message: BAD INPUT TO PER LOOKASIDE TABLE COPY

Explanation: The TPF Assembler Debugger for VisualAge Client entry control block (ECB) dispatch time function was called when the CE2CLUE ECB field was not pointing to a valid glue block (storage that joins two ECBs together). The control information in the glue block is required to update the I-stream unique program event recording (PER) lookaside table for the debugger before restarting the application to be debugged.

System Action: The ECB exits.

User Response: See your IBM service representative to report the problem.


0ADB0C

Program: CUDR/CCVAGE

Error Message: BAD INPUT TO VISUALAGE ASSEMBLER DEBUGGER FOR TPF CDBUGPER CALL

Explanation: The TPF Assembler Debugger for VisualAge Client CDBUGPER function was called to update program event recording (PER) bracket settings for the TPF C Debugger for VisualAge Client, but the control information in the incoming debugger message block was not correct.

System Action: The entry control block (ECB) exits.

User Response: See your IBM service representative to report the problem.


0ADB0F

Program: CUDU

Error Message: INSUFFICIENT STORAGE TO ALLOCATE PER EXCLUSION TABLE

Explanation: The GSYSC macro returned an error condition when requesting storage for the program event recording (PER) exclusion table.

System Action: The following occurs:

User Response:

  1. Review the system error dump to determine the cause of the error.
  2. Correct the error.


0ADB10

Program: CHOOKS

Error Message: DEBUGGER IS UNABLE TO ALLOCATE HEAP STORAGE

Explanation: The TPF Assembler Debugger for VisualAge Client tried to allocate heap storage for its internal tables, but the MALOC macro sent an error code indicating that no heap storage is available.

System Action: The entry control block (ECB) exits.

User Response: Do the following:

  1. Increase the size of the ECB heap by entering the ZCTKA ALTER command with the EMPS and MMHS parameters specified.
  2. Perform an initial program load (IPL) of the TPF system again.
  3. Run the function again.

See TPF Operations for more information about the ZCTKA ALTER command.


0ADB11

Program: CHOOKS

Error Message: INTERNAL DEBUGGER ERROR

Explanation: An internal error occurred with the TPF Assembler Debugger for VisualAge Client.

System Action: The entry control block (ECB) exits.

User Response: See your IBM service representative to report the problem.


0ADB12

Program: UCST

Error Message: UCST CANNOT BE ENTERED

Explanation: An error occurred because the common symbol table (UCST) program was entered by a user-defined program. A user-defined program should not be coded to enter the UCST program because it is a program record for the common symbol table.

System Action: The entry control block (ECB) exits.

User Response: Do the following:

  1. Review the system error dump to find the name of the calling program and determine the cause of the error.
  2. Correct the error.


0ADB13

Program: CUDA

Error Message: ASSEMBLER DEBUGGER IS UNABLE TO ALLOCATE HEAP STORAGE

Explanation: The TPF Assembler Debugger for VisualAge Client tried to allocate heap storage for internal use but was not successful. An error message is also displayed in the TPF Assembler Debugger for VisualAge Client user interface.

System Action: The entry control block (ECB) continues.

User Response: Do the following:

  1. Increase the size of the ECB heap by entering the ZCTKA ALTER command with the EMPS and MMHS parameters specified.
  2. Perform an IPL of the TPF system.
  3. Run the function again.

See TPF Operations for more information about the ZCTKA ALTER command.


0ADB14

Program: CUDA

Error Message: ASM DEBUGGER: IVALINKEDLIST METHOD RECEIVED A NULL POINTER

Explanation: An internal error occurred with the TPF Assembler Debugger for VisualAge Client.

System Action: The entry control block (ECB) ends.

User Response: Do the following:

  1. Use the dump to locate which code called the IVALinkedList method.
  2. Determine why a null pointer was passed.


0ADB15

Program: CUDA

Error Message: ERROR IN DWARF_API: (FILE:LINE): Error_String

Where:

DWARF_API
One of the following API calls made by the TPF Assembler Debugger for VisualAge Client:

FILE
The name of the file from which the error occurred.

LINE
The line on which the error occurred.

Error_String
The error string returned by the DWARF API call.

Explanation: An error occurred while using a DWARF API call.

System Action: Processing continues.

User Response: See your IBM service representative to report the problem.


0ADB16

Program: CEXP

Error Message: MALLOC FAILED FOR GLOBAL SYMBOL SUPPORT

Explanation: An error occurred because there was not enough heap storage allocated to accomodate the processing of global symbols.

System Action: The entry control block (ECB) ends.

Program: CDB3

Error Message: MALLOC FAILED FOR GLOBAL SYMBOL SUPPORT: yyyy SYMBOL TABLE REQUIRES xxxx BYTES

Where:

yyyy
One of the following:

xxxx
The amount of memory needed for the specified table.

Explanation: Large sections of memory must be allocated to create the symbol information for the global symbols in TPF C Debugger for VisualAge Client. This includes user override symbols, user global symbols, and IBM global symbols. The amount of memory that must be allocated is proportional to the complexity of the symbol definitions in the user symbol override table, the user global symbol table, or the IBM-defined global symbol table, for example, a struct any * variable requires more memory than a void * variable. This error occurs when the amount of memory to allocate exceeds the limit of 4KB frames.

System Action: The following occurs:

User Response: Modify keypoint A by doing one of the following:

See TPF Operations for more information about the ZCTKA ALTER command.


0ADB17

Program: CEXP

Error Message: DYNAMIC SYMBOL LIMIT REACHED: DELETE A USER OVERRIDE SYMBOL WITH PARAMETER

DYNAMIC SYMBOL LIMIT REACHED: DELETE A USER GLOBAL SYMBOL WITH PARAMETER

DYNAMIC SYMBOL LIMIT REACHED: DELETE A TPF GLOBAL SYMBOL WITH PARAMETER

Explanation: Global variables that include a parameter require special processing. As a result, there is a limit to the number of global symbols that can be displayed at one time. The current limit is 50 global symbols for each table: user global symbol table, user symbol override table, and IBM-defined global symbol table.

System Action: A SNAP dump is issued that displays the message that corresponds to the table, as well as the variables that are currently displayed in the expression monitor. Processing continues.

User Response: Do the following: