gtpm4m12Messages (System Error and Offline)

094000-094FFF


094000

Program: CCISOC (CIS0)

Error Message: INVALID ISO-C SHARED LIBRARY CALL

Appended Message: INVALID ISO-C SHARED LIBRARY CALL

Explanation: A call was made to an ISO-C shared library that currently is not loaded in the CRPA.

System Action: The ECB ends.

User Response: Load the required ISO-C shared library.


094001

Program: Displayed on operator console and in dump

Error Message: INVALID ISO-C LIBRARY FUNCTION CALL

Appended Message: INVALID ISO-C LIBRARY FUNCTION CALL

Explanation: A call was made to an ISO-C library function that does not exist in the version of the shared library that is currently loaded.

System Action: The ECB ends.

User Response: Do one of the following:


094002

Program: CCENBK(CCEG)

Error Message: ERROR READING PROGRAM VERSION RECORD

Explanation: A $FINDC attempt on a program version record (PVR) did not complete successfully.

System Action: Processing continues; however, state change is disabled. The program allocation table (PAT) information (version code, linkage type, and size) for some programs is not up to date, which might cause problems when these programs are run.

User Response: Do the following:

  1. Use the SUD value given from the system error dump to determine the cause of the problem.
  2. Correct the problem.
  3. IPL the TPF system again.


094003

Program: CRL0, CRL1

Error Message: ERROR RELEASING ISO-C FILE RESIDENT PROGRAM STORAGE. POLICING WILL CONTINUE.

Appended Message: ERROR RELEASING ISO-C FILE RESIDENT PROGRAM STORAGE. POLICING WILL CONTINUE.

Explanation: An error occurred when the TPF system tried to release a program from the ISO-C file resident program area.

System Action: The program causing the error is removed from the file resident program chain and the address of the program is set to 0.

User Response: Analyze the system dump to determine the cause of the error. See your IBM service representative to report the problem.


094004

Program: CCENBK(CCEF)

Error Message: LOAD MODULE WAS NOT RELOADED AFTER MASTER EXTRA PROGRAM RECORD WAS CLEARED

Appended Message: LOAD MODULE WAS NOT RELOADED AFTER MASTER EXTRA PROGRAM RECORD WAS CLEARED

Explanation: The program was not reloaded after the master extra program record was initialized (by using a LOADER PROG-MOD-BASE CLEARcard in a general file loader load deck or an auxiliary loader load deck). Therefore, the program's ordinals in the #XPRGn record type are not valid.

System Action: The program is not brought into main storage. The entry exits.

User Response: Do one of the following:


094005

Program: CLIB

Error Message: SHARED LIBRARY ORDINAL CONFLICT

Appended Message: SHARED LIBRARY ORDINAL CONFLICT

Explanation: An attempt was made to load a shared library, but a library with the same ordinal was already loaded. This system error dump contains the ordinal number, the name of the library that is loaded, and the name of the library that could not be loaded.

System Action: A RELPC is done to release the library that could not be loaded.

User Response: Assign a unique ordinal number to the library.


094006

Program: CCEG

Error Message: ENTER TO ISO-C TRANSFER VECTOR IS NOT ALLOWED -- ECB EXITED

Explanation: An ECB attempted to enter a transfer vector program, but the base program is defined to be an ISO-C dynamic load module (DLM). Transfer vectors are not supported for ISO-C DLMs.

System Action: The ECB exits.

User Response: Check the program making the call to the transfer vector. Update the program to call the DLM entry point function instead of the transfer vector.

See the TPF Migration Guide: Program Update Tapes for more information about migrating C programs that contain transfer vectors.


094007

Program: CCENBK(CCEB)

Error Message: DIRECT ENTER TO LIBRARY LOAD MODULE NOT ALLOWED -- ECB EXITED

Appended Message: DIRECT ENTER TO LIBRARY LOAD MODULE NOT ALLOWED -- ECB EXITED

Explanation: An attempt was made to do a direct enter to a library. Only function calls for the functions contained in a library are valid. It is not valid to attempt to enter the library load module directly.

System Action: The ECB is exited.

User Response: Correct the program that entered the library load module directly; use a function call for a function in the library.


094008

Program: CCFADC (CEFI)

Error Message: INVALID DECB

Appended Message: INVALID DECB

Explanation: For CP DASD I/O, there are two conditions when this error can occur during:

In addition, the DECB address itself may be valid, but the DECB contents may not be.

System Action: The TPF system is re-IPLed.

User Response: See your IBM service representative for more information about the DECB.


094009

Program: CCENBK(CCEF)

Error Message: ERROR TRANSLATING LOAD MODULE ORDINAL NUMBER TO A FILE ADDRESS

Appended Message: ERROR TRANSLATING LOAD MODULE ORDINAL NUMBER TO A FILE ADDRESS

Explanation: During load module fetch processing, an attempt to translate an ordinal number in the load module to a file address was unsuccessful.

System Action: The ECB exits.

User Response: Do the following:

  1. Determine the cause of the ordinal number corruption.
  2. Reload all of the ISO-C load modules in the system and include the LOADER PROG-MOD-BASE CLEAR card in the load deck to ensure that all ordinal numbers in use are correct.


09400A

Program: CCENBK(CCEF)

Error Message: UNABLE TO OBTAIN CORE AREA FOR LOAD MODULE

Appended Message: UNABLE TO OBTAIN CORE AREA FOR LOAD MODULE

Explanation: There is not enough space in the system heap storage to hold the ISO-C program or library that the system is attempting to fetch from DASD to main storage.

System Action: The ECB exits.

User Response: Do the following:

  1. Determine if the program is defined as file or core resident.
  2. IPL the TPF system again.


09400B

Program: CCENBK(CCEF, CCEG)

Error Message: NUMBER OF I/O REQUESTS OUTSTANDING IS INVALID

Appended Message: NUMBER OF I/O REQUESTS OUTSTANDING IS INVALID

Explanation: A $FINDC I/O request has completed. The number of I/O requests outstanding is not decremented because the value is not valid, that is, it is not a positive number.

System Action: A catastrophic system error is taken.

User Response: Determine how the number of I/O requests outstanding was corrupted and correct the problem.


09400C

Program: CCSTOR(CLHV)

Error Message: ISO-C STACK OVERFLOW

Appended Message: ISO-C STACK OVERFLOW

Explanation: The size of the ISO-C stack that is required exceeds the maximum allowed for the ECB.

System Action: The ECB exits.

User Response: Do the following:

  1. Make sure that the application is not in an infinite recursive call loop.
  2. Verify that the values set in CTKA for ESPS and MSHS are large enough to accommodate your application. Note that the maximum size of the stack is set to the smaller of these 2 values.
  3. If the application actually requires larger stack storage, increase the allowed stack size for the ECB or for the system.

See the TPF C/C++ Language Support User's Guide for additional information.


09400D

Program: CCSTOR(CLHV)

Error Message: ISO-C STATIC STORAGE OVERFLOW

Appended Message: ISO-C STATIC STORAGE OVERFLOW

Explanation: The storage requested for static data exceeds the maximum allowed for the ECB.

System Action: The ECB exits.

User Response: Do the following:

  1. Static storage is allocated from the TPF heap. Make sure the application is not in an infinite loop acquiring heap storage.
  2. If the application actually requires larger heap storage, increase the maximum allowed heap size for the ECB or for the system. See the TPF C/C++ Language Support User's Guide for more information about how to increase the heap size.


09400E

Program: CCSTOR (CLHV)

Error Message: SYSTEM HEAP IS CORRUPTED. R4 CONTAINS FCT ENTRY.

Appended Message: SYSTEM HEAP IS CORRUPTED. R4 CONTAINS FCT ENTRY.

Explanation: The TPF system detected the double release of a frame thought to be in use by the system heap storage. This condition indicates that the control tables for the system heap storage contain incorrect information.

System Action: The TPF system issues a catastrophic system error to begin another IPL to clear the system heap storage control tables.

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


09400F

Program: CCENBK(CCEG)

Error Message: ERROR TRANSLATING PROGRAM VERSION RECORD ORDINAL NUMBER TO A FILE ADDRESS

Explanation: An attempt to translate the ordinal number for a program version record (PVR) to a file address was unsuccessful for one of the following reasons:

System Action: Processing continues; however, state change is disabled.

User Response: Do the following:

  1. Based on the cause of the problem, take one of the following actions:
  2. IPL the TPF system again after the problem has been corrected.


094010

Program: CCENBK(CCED)

Error Message: CURRENT VERSION OF ISO-C LIBRARY (CISO) NOT LOADED

Appended Message: CURRENT VERSION OF ISO-C LIBRARY (CISO) NOT LOADED

Explanation: The TPF system detected that either the ISO-C library is not loaded or the current version is not loaded.

System Action: The register contents are displayed and the ECB is exited.

User Response: Verify that the correct version of CISO is loaded.


094011

Program: CRL0, CRL1

Error Message: ISO-C FILE RESIDENT PROGRAM POLICING STOPPED DUE TO CORRUPTION IN THE FILE RESIDENT PROGRAM CHAIN

Appended Message: ISO-C FILE RESIDENT PROGRAM POLICING STOPPED DUE TO CORRUPTION IN THE FILE RESIDENT PROGRAM CHAIN

Explanation: The TPF system detected that the file resident program chain pointers are corrupted.

System Action: Policing of ISO-C file resident programs is stopped but the TPF system continues to operate.

User Response: IPL the TPF system again to restart file resident program policing and rebuild the program chain.

Analyze the system dump to determine the cause of the error. See your IBM service representative to report the problem.


094015

Program: CCENBK(CCEB)

Error Message: DIRECT ENTER TO DLL NOT ALLOWED - ECB EXITED

Explanation: The dynamic link library (DLL) cannot be called using TPF enter/back linkage.

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

User Response: Do one of the following:


094016

Program: Dynamic link library (DLL) load functions in CISO.

Error Message: ATTEMPT TO LOAD NON-DLL dll AS A DLL

Where:

dll
The non-DLL load module being loaded or referenced as a DLL.

Explanation: An error occurred while trying to load or reference a non-DLL module as a DLL.

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

User Response: Do one of the following:


094017

Program: TPF_dll_load function in CISO.

Error Message: UNABLE TO LOAD THE DLL dll, GETPC RETURN CODE = d, - ECB EXITED

Where:

dll
The 4-character name of the dynamic link library (DLL).

d
The return code from the GETPC macro.

Explanation: An error occurred with the getpc C function while trying to load a DLL.

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

User Response: Do the following:

  1. See the TPF C/C++ Language Support User's Guide for more information about the return code from the getpc C function.
  2. Correct the problem.


094018

Program: Implicit dynamic link library (DLL) load function in CISO.

Error Message: ERROR DURING DLL IMPLICIT LOAD

Appended Message: IMPLICIT DLL LOAD NOT DONE, CIRCULAR DLL LOAD, RUN CONSTRUCTORS

Explanation: A circular DLL load error occurred, which means DLLA needs DLL B and DLL B needs DLL while running constructors.

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

User Response: Design the DLLs to eliminate a circular DLL oad condition.

Appended Message: IMPLICIT DLL LOAD NOT DONE, CIRCULAR DLL LOAD, RUN DESTRUCTORS

Explanation: A circular DLL load error occurred, which means DLLA needs DLL B and DLL B needs DLL while running constructors.

System Action: The ECB exits.

User Response: Design the DLLs to eliminate a circular DLL load condition.

Appended Message: IMPLICIT DLL LOAD NOT DONE, NOT ENOUGH STORAGE FOR DLL HANDLE

Explanation: The malloc C function was not successful when trying to get storage for a DLL handle.

System Action: The ECB exits.

User Response: Provide more heap storage.

Appended Message: IMPLICIT DLL LOAD NOT DONE, NOT ENOUGH STORAGE FOR DLCB

Explanation: The malloc C function was not successful when trying to get storage for a DLCB.

Note:
DLCB is an IBM internal-use-only control block.

System Action: The ECB exits.

User Response: Provide more heap storage.

Appended Message: DLL dll DOES NOT EXPORT ANY VARIABLES AND FUNCTIONS

Where:

dll
The 4-character name of the DLL.

Explanation: The DLL application referenced an exported variable or called an exported function from the target DLL. However, the DLL in use does not export any variables and functions.

System Action: The ECB exits.

User Response: Do the following:

  1. Build the DLL to export required functions and variables and load the DLL to the system again.
  2. Run the program again.

Appended Message: DLL dll DOES NOT EXPORT ANY VARIABLES, BUT APPLICATION IS EXPECTING

Where:

dll
The 4-character name of the DLL.

Explanation: The DLL application referenced an exported variable from the target DLL; however, the DLL in use does not export any variables.

System Action: The ECB exits.

User Response: Do the following:

  1. Build the DLL to export required variables and load the DLL to the system again.
  2. Run the program again.

Appended Message: DLL dll DOES NOT EXPORT ANY FUNCTIONS, BUT APPLICATION IS EXPECTING

Where:

dll
The 4-character name of the DLL.

Explanation: The DLL application called an exported function from the target DLL; however, the DLL in use does not call any function.

System Action: The ECB exits.

User Response: Do the following:

  1. Build the DLL to export required functions and load the DLL to the system again.
  2. Run the program again.

Appended Message: REFERENCED VARIABLE name NOT FOUND IN DLL dll

Where:

name
The name of the referenced variable.

Explanation: The DLL application referenced the variable shown in the message but the variable was not found in the target DLL.

System Action: The ECB exits.

User Response: Do the following:

  1. Build the DLL to export the referenced variable and load the DLL to the system again.
  2. Run the program again.

Appended Message: REFERENCED FUNCTION name NOT FOUND IN DLL dll

Where:

name
The name of the referenced function.

Explanation: The DLL application referenced the function name but it is not found in the target DLL.

System Action: The ECB exits.

User Response: Do the following:

  1. Build the DLL to export the referenced function and load the DLL to the system again.
  2. Run the program again.


094101

Program: CLIB, CPRE

Error Message: DLL CODE IN RUN-TIME LIBRARY

Explanation: An attempt was made to load a run-time library, but the run-time library contains a dynamic link library (DLL) object file. This system error contains the ordinal number and the name of the run-time library that contains the DLL object file.

System Action: An RELPC macro is issued to release the library that could not be loaded.

User Response: Do the following:

  1. Determine if the member should be a DLL object file or a run-time library member.
  2. If the member should be a DLL object file, remove it from the run-time library and go to step 2a. If the member should be a run-time library member, change the DLL object file to be a non-DLL object file and go to step 2b.
    1. After you remove the DLL object file:
      1. Remove the associated library function ordinal number from the library interface script.
      2. Run the library interface tool (LIBI).
      3. Continue to steps 3 and 4.
    2. After you change the DLL object file to be a non-DLL object file:
      1. Do not remove the library ordinal number from the library interface script.
      2. Recompile the source code.
      3. Continue to steps 3 and 4.
  3. Run the C load module build tool (CBLD) to rebuild the run-time library.
  4. Reload the corrected run-time library to the TPF system.


094202

Program: C++ exception handling routine in CPP1.

Error Message: PROGRAM NESTING LEVEL AND DLM MISMATCH OCCURRED IN EXCEPTION HANDLING

Explanation: A catch clause is identified to receive control to handle an exception, but the TPF system cannot find the program nesting level (PNL) of the dynamic load module (DLM) that is associated with the catch clause.

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

User Response: See your IBM service representative.


094203

Program: C++ exception handling routine in CPP1.

Error Message: EXCEPTION IS CAUGHT ACROSS TARGET(TPF) PROGRAM

Explanation: An exception is thrown and the TPF system needs to drop a TARGET(TPF) program to reach the catch clause. Continuing to run the program may cause unpredictable results because the exception cannot restore the pointer of the writable stack of a TARGET(TPF) program.

System Action: Control is returned to the catch clause.

User Response: Modify the application to avoid throw exceptions across TARGET(TPF) programs.


094204

Program: C++ exception handling routine in CPP1.

Error Message: AN UNCAUGHT EXCEPTION OR A BAD RE-THROW IS DETECTED, EXCEPTION HANDLING IS TERMINATED

Explanation: One of the following occurred:

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

User Response: Do the following:

  1. Examine the system error and application programs to determine where the incorrect re-throw or the uncaught exception was thrown.
  2. Correct the application.

See TPF Application Programming for more information about C++ exception handling.


094320

Program: CCENBK (CCEG)

Error Message: ERROR READING MASTER APRG RECORD

Explanation: A $FINDC macro attempt on the master APRG record was not completed successfully.

System Action: Processing continues; however, ADATA file information will not be moved from the program version record (PVR) entries to the program allocation table (PAT) entries. As a result, the TPF Assembler Debugger for VisualAge Client will not be able to use ADATA files that were loaded to the program base.

User Response: Do the following:

  1. Use the CE1SUD indicator in the entry control block (ECB) value that was provided in the system error dump to determine the cause of the problem.
  2. Correct the problem.
  3. IPL the TPF system again.