This message class is returned if an error occurred in the RPC C runtime system layer. Messages of this class have the format:
1000nnnn
where | 1000 | is the message class, and |
nnnn | is the message number in the range 0000 - 9999. |
10000001 | 10000002 | 10000003 | 10000004 | 10000005 | 10000006 | 10000007 | 10000008 | 10000009 | 10000010 | 10000011 | 10000012 | 10000013 | 10000014 | 10000015 | 10000016 | 10000017 | 10000018 | 10000019 | 10000020 | 10000021 | 10000022 | 10000024 | 10000025 | 10000026 | 10000027 | 10000029 | 10000030 | 10000031 | 10000032 | 10000033 | 10000034 | 10000035 | 10000036 | 10000037 | 10000038 | 10000039 | 10000040 | 10000041 | 10000042 | 10000043 | 10000044 | 10000045 | 10000046 | 10000047 | 10000048 | 10000049 | 10000050 | 10000051 | 10000052 | 10000053 | 10000054 | 10000055 | 10000056 | 10000057 | 10000058
10000001 | Error |
Explanation |
System error. |
Action |
Check system log to find out which error occurred. |
10000002 | Service not implemented |
Explanation |
A service call was requested for a platform not implemented. |
Action |
Contact Software AG support. |
10000003 | A non-C file was found |
Explanation |
A LoadLibrary has found a module which is not a shared library. This message is useful in CICS/COBOL environment to distinguish between C (shared) libraries and COBOL native programs. |
Action |
Call as COBOL program. |
10000004 | System Services not initialized |
Explanation |
Initialize some System Services logic: tracing, error boxes. |
Action |
Code |
10000005 | Resource temporarily unavailable |
Explanation |
Indicates system shortage, especially when starting new threads. |
Action |
Try later or terminate some other task(s), if applicable. |
10000006 | Permission denied |
Explanation |
|
Action |
|
10000007 | Not enough memory |
Explanation |
A system request returned with |
Action |
Try to locate the reason for this shortage and remove it from your system. |
10000008 | Thread doesn't exist |
Explanation |
A system request returned with |
Action |
|
10000009 | Deadlock detected |
Explanation |
A system request has been cancelled with |
Action |
Correct your program logic. If the error is caused by an EntireX RPC server operation, contact Software AG support. |
10000010 | Invalid Argument(s) supplied |
Explanation |
A system request has been cancelled with |
Action |
Correct your program logic. If the error is caused by an EntireX RPC server operation, contact Software AG support. |
10000011 | Thread cancelled |
Explanation |
A thread has been cancelled by the operating system. |
Action |
Check system resources. |
10000012 | Interrupted |
Explanation |
One of the |
Action |
Re-issue request. |
10000013 | Timeout |
Explanation |
A wait for an event finished with a timeout. |
Action |
None. |
10000014 | Unknown error |
Explanation |
The RPC Server for CICS returns this code for CICS error codes. |
Action |
Check the system log for the kind of error. |
10000015 | Cannot load shared library |
Explanation |
Loading a shared library failed. The library name can be found in accompanying messages. |
Action |
Check that the shared library is in the server's |
10000016 | Cannot load function |
Explanation |
A shared library has been found but it did not contain the function name. Library name and function name can be found in accompanying messages. |
Action |
Check proper shared library in the server's |
10000017 | CICS length error |
Explanation |
A |
Action |
More detailed information ( |
10000018 | Reserved |
10000019 | Invalid arguments supplied |
Explanation |
This code is returned by the RPC Server for CICS when |
Action |
If part of RPC server errors, contact Software AG support. |
10000020 | File not found |
Explanation |
Loading a file failed. The file name can be found in accompanying messages. This return code will be used by RPC Server for CICS to first test if the file is of type Shared Library or COBOL. |
Action |
Check if the named file is in the server's DFHRPL steplib. |
10000021 | Not authorized |
Explanation |
An RPC Server for CICS has tried to start a (user)task with the user ID
of the client, but CICS rejected with |
Action |
Contact your system administrator. |
10000022 | Thread has abended |
Explanation |
A user server program under CICS has terminated abnormally. The RPC server will continue to process. |
Action |
Correct your server program. |
10000024 | Process could not be started/does not exist |
Explanation |
A request to start a new server process returned with error. This kind of error will occur in environments where a server process can be started from an RPC Online Maintenance Facility tool. |
Action |
Check to see if a process already exists. Otherwise check system messages. |
10000025 | Read from console failed |
Explanation |
Input for RPC Online Maintenance Facility tools is not possible. Note: An RPC Online Maintenance Facility is not supported on every platform. |
Action |
For CICS: Check the |
10000026 | Write to console failed |
Explanation |
Output for the RPC Online Maintenance Facility is not possible. Note: An RPC Online Maintenance Facility is not supported on every platform. |
Action |
For CICS: Check the |
10000027 | Shared memory already exists |
Explanation |
This message is used internally. |
Action |
None. |
10000029 | Error in DISEI - RC : nnnnnnnn |
Explanation |
An error in the RPC Server eventing routines occurred.
|
Action |
Contact Software AG support. |
10000030 | Error in ENAEI - RC : nnnnnnnn |
Explanation |
An error within the RPC Server eventing routines occurred.
|
Action |
Contact Software AG support. |
10000031 | Failed to execute worker task |
Explanation |
An error occurred while establishing an RPC server worker task. This error messages occurs in conjunction with message 10000032, which will contain a reason code. |
Action |
See message 10000032. |
10000032 | Reason Code : n | ||||||||||||
Explanation |
Contains the reason code of a previous 10000031 message. |
||||||||||||
Action |
Action depends on the reason code n:
|
10000033 | Worker task successfully connected to shared memory |
Explanation |
Informational message. |
Action |
None. |
10000034 | SDF variable MAIN-TASK-TSN could not be read - GETVAR RC : nnnnnnnn |
Explanation |
An error in macro |
Action |
Make sure that |
10000035 | Server main task is initializing |
Explanation |
Informational message. |
Action |
None. |
10000036 | Server worker task is initializing |
Explanation |
Informational message. |
Action |
None. |
10000037 | ENAMP failed while initializing the main task - ENAMP RC : nnnnnnnn |
Explanation |
An error within the RPC Server main task initialization routine occurred.
|
Action |
Contact Software AG support. |
10000038 | ENAMP failed while connecting the worker task - ENAMP RC : nnnnnnnn |
Explanation |
An error within the RPC Server worker task initialization routine
occurred. |
Action |
Contact Software AG support. |
10000039 | SDF variable CURRENT-TSN could not be read - GETVAR RC : nnnnnnnn |
Explanation |
An error in macro |
Action |
Make sure that |
10000040 | Request memory failed - REQMP RC : nnnnnnnn |
Explanation |
An error within the RPC Server initialization routine occurred.
|
Action |
Contact Software AG support. |
10000041 | Main task shared memory enabled successfully |
Explanation |
Informational message. |
Action |
None. |
10000042 | ENAMP failed - invalid pool address |
Explanation |
An error within the RPC Server initialization routine occurred. |
Action |
Contact Software AG support. |
10000043 | Error in POSSIG - RC : nnnnnnnn |
Explanation |
An error within the RPC Server eventing routines occurred.
|
Action |
Contact Software AG support. |
10000044 | Error in SOLSIG - RC : nnnnnnnn |
Explanation |
An error within the RPC Server eventing routines occurred.
|
Action |
Contact Software AG support. |
10000045 | Error in DISMP - RC : nnnnnnnn |
Explanation |
An error within the RPC Server termination routine occurred.
|
Action |
Contact Software AG support. |
10000046 | Shared memory disabled |
Explanation |
Informational message. |
Action |
None. |
10000047 | Disconnected from shared memory |
Explanation |
Informational message. |
Action |
None. |
10000048 | RPC Server task ended |
Explanation |
Informational message. |
Action |
None. |
10000049 | Failed to load User Exit |
Explanation |
Either the initialization user exit or the termination user exit, specified in the RPC server configuration file, could not be loaded. |
Action |
Make sure that server parameters |
10000050 | Call Initialization User Exit |
Explanation |
Informational message. |
Action |
None. |
10000051 | Call Termination User Exit |
Explanation |
Informational message. |
Action |
None. |
10000052 | SINF failed while retrieving system information - SINF RC : nnnnnnnn |
Explanation |
An error within the RPC Server initialization routine occurred.
|
Action |
Contact Software AG support. |
10000053 | View already exists |
Explanation |
This message is used internally. |
Action |
None. |
10000054 | Cannot open file |
Explanation |
A request to open a file was not successful. |
Action |
This message is accompanied by other messages. The RPC server could not open a required file, (e.g the server-side mapping container, see Server-side Mapping Files in the RPC server documentation for z/OS (CICS, Batch, IMS) | BS2000 | z/VSE (CICS, Batch). The RPC server might stop. |
10000055 | CICS Container error |
Explanation |
A |
Action |
More detailed information ( |
10000056 | Process stop |
Explanation |
This message is used internally. |
Action |
None. |
10000057 | Trace synchronization table overflow |
Explanation |
Informational message. |
Action |
None. |
10000058 | Fork-child |
Explanation |
This message is used internally. |
Action |
None. |