This page explains the Console Messages, which have the format
XCOnnnns
| where | XCO | is the error code |
| nnnn | is the message number, and | |
| s | indicates the severity of the error: E: error; function cannot be performed I: information W: warning; potential problem exists |
XCO0003E | XCO0005E | XCO0007E | XCO0008E | XCO0009I | XCO0010W | XCO0011E | XCO0012E | XCO0013E | XCO0014E | XCO0015E | XCO0016I | XCO0019E | XCO0020I | XCO0021W | XCO0022I | XCO0023I | XCO0024I | XCO0025I | XCO0026E | XCO0027E | XCO0028I | XCO0029I | XCO0030I | XCO0031I | XCO0032I | XCO0033I | XCO0034I | XCO0035I | XCO0036I | XCO0037I | XCO0039I | XCO0041E | XCO0043E | XCO0044E | XCO0045E | XCO0046E | XCO0047E | XCO0048E | XCO0050E | XCO0051W | XCO0052W | XCO0053W | XCO0054W | XCO0055I | XCO0057I | XCO0061W | XCO0062W | XCO0063E | XCO0077I | XCO0078E | XCO0080E | XCO0081E | XCO0082I | XCO0083W | XCO0084W | XCO0085W | XCO0086I | XCO0087E | XCO0088I | XCO0089E | XCO0091I | XCO0095E | XCO2001E | XCO2002E | XCO2003E | XCO2004E | XCO2005E | XCO2006E | XCO2007E | XCO2008E | XCO2009E | XCO2010E | XCO2011E | XCO2012E | XCO2013E | XCO2014E | XCO2015E| XCO0003E | ERROR DURING READ OF STARTUP PARMS. |
| Explanation |
Error occurred while attempting to open the file designated by the PARMS DD. |
| Action |
Correct and verify that the PARMS DD is pointing to the file containing the startup parameters. Restart Broker. |
| XCO0005E | LOAD FOR MODULE :1: FAILED - ABEND. |
| Explanation |
The loading of module :1: failed. |
| Action |
Check and verify whether the module :1: is in the library concatenation. If not, add the appropriate library containing the module :1:. Restart Broker. |
| XCO0007E | WRONG X-COM PARAMETER :1:. |
| Explanation |
The X-COM parameter :1: is incorrect or not specified. |
| Action |
Add or correct the value for the parameter :1:. Restart Broker. |
| XCO0008E | ADAMPM - WRONG VERSION FOUND. |
| Explanation |
The verification of ADAMPM failed. |
| Action |
Ensure that the correct version of ADAMPM is contained in the library concatenation. Restart Broker. |
| XCO0009I | X-COM node is initialized. |
| Explanation |
X-COM has initialized the target and is ready for work. |
| Action |
No action required. |
| XCO0010W | Wrong ECB found. |
| Explanation |
The type of returned event indicator is not valid and will be ignored. X-COM nucleus continues to wait for requests. |
| Action |
Contact Software AG support. |
| XCO0011E | X-COM data error. |
| Explanation |
The routine to check X-COM data has detected an inconsistency. X-COM nucleus terminates abnormally. |
| Action |
Contact Software AG support. |
| XCO0012E | USER RET (R15) error. |
| Explanation |
One of the routines called by X-COM nucleus has returned an error. X-COM nucleus terminates abnormally. |
| Action |
Contact Software AG support. |
| XCO0013E | Delete ECB error. |
| Explanation |
An ECB cannot be removed from the wait list. X-COM nucleus terminates abnormally. |
| Action |
Contact Software AG support. |
| XCO0014E | No ANSWER entry point. |
| Explanation |
The entry point for the reply handler could not be found. X-COM nucleus cannot process any user replies and terminates abnormally. |
| Action |
Contact Software AG support. |
| XCO0015E | APPL ECB throw away. |
| Explanation |
The X-COM nucleus was posted to send the reply to the user but could find the related X-COM data. X-COM nucleus ignores the post and continues to wait for requests. |
| Action |
No action required. |
| XCO0016I | Operator typed in: :1:. |
| Explanation |
Message confirming operator input. |
| Action |
No action required. |
| XCO0019E | X-COM parm list wrong. |
| Explanation |
The request or reply handler has returned inconsistent data. X-COM nucleus terminates abnormally. |
| Action |
Contact Software AG support. |
| XCO0020I | X-COM stopped |
| Explanation |
X-COM nucleus is calling the termination handler for shutdown |
| Action |
No action required |
| XCO0021W | This X-COM is no longer active |
| Explanation |
X-COM nucleus has successfully executed the termination handler |
| Action |
No action required |
| XCO0022I | X-COM cancel will proceed |
| Explanation |
The operator command XCANCEL to cancel Entire System Server was entered |
| Action |
No action required |
| XCO0023I | X-COM halted |
| Explanation |
The operator command XHALT was entered. This means that no more calls are possible, but the Entire System Server task is still available and can be restarted with the XSTART command |
| Action |
No action required |
| XCO0024I | X-COM started |
| Explanation |
The operator command XSTART was entered. This means that calls are now processed again |
| Action |
No action required |
| XCO0025I | X-COM end will proceed |
| Explanation |
The operator command XEND to end Entire System Server was entered |
| Action |
No action required |
| XCO0026E | APPL stop error |
| Explanation |
The shutdown handler has returned an error |
| Action |
Contact Software AG support. |
| XCO0027E | Timer error |
| Explanation |
Setup of timer services has failed. X-COM nucleus terminates abnormally |
| Action |
Contact Software AG support. |
| XCO0028I | Number of active users = :1: |
| Explanation |
Output of command XUSER reporting the current number of user requests |
| Action |
No action required |
| XCO0029I | Highest number of active users = :1: |
| Explanation |
Output of command XUSER reporting the highest number of user requests |
| Action |
No action required |
| XCO0030I | Number of active CQE-S = :1:. |
| Explanation |
Output of command XCQES reporting the current number of user requests. |
| Action |
No action required. |
| XCO0031I | Highest number of active CQE-S = :1:. |
| Explanation |
Output of command XCQES reporting the highest number of user requests. |
| Action |
No action required. |
| XCO0032I | Parameters for this session:. |
| Explanation |
Output of command XPARM. |
| Action |
No action required. |
| XCO0033I | SVC number = :1:. |
| Explanation |
Output of command XPARM reporting the used SVC number on z/OS or z/VSE. |
| Action |
No action required. |
| XCO0034I | Node number = :1:. |
| Explanation |
Output of command XPARM reporting the ESY node number. |
| Action |
No action required. |
| XCO0035I | CQE number = :1:. |
| Explanation |
Output of command XPARM reporting the startup parameter NCQE. |
| Action |
No action required. |
| XCO0036I | NAB number = :1:. |
| Explanation |
Output of command XPARM reporting the startup parameter NABS. |
| Action |
No action required. |
| XCO0037I | User-application = :1:. |
| Explanation |
Output of command XPARM reporting the name of MAIN function. |
| Action |
No action required. |
| XCO0039I | Total number of commands = :1:. |
| Explanation |
Output of command XSTAT reporting the accumulated number of received user requests. |
| Action |
No action required. |
| XCO0041E | Invalid operator command. |
| Explanation |
An invalid operator command was entered. |
| Action |
Correct it. |
| XCO0043E | Error during request of memory. |
| Explanation |
Not enough memory available. X-COM nucleus terminates abnormally. |
| Action |
Please check your environment for available memory. |
| XCO0044E | Error during release of memory. |
| Explanation |
Error in FREEMAIN/FREEVIS/RELM. |
| Action |
Contact Software AG support. |
| XCO0045E | OPER command init error. |
| Explanation |
Adabas operator command interface could not be established. X-COM nucleus terminates abnormally. |
| Action |
Contact Software AG support. |
| XCO0046E | Add CQHAECB error. |
| Explanation |
Adabas could not add the command queue to the ECB wait list. X-COM nucleus terminates abnormally. |
| Action |
Contact Software AG support. |
| XCO0047E | Add user ECB error. |
| Explanation |
Adabas could not add the user ECB to the ECB wait list. X-COM nucleus terminates abnormally. |
| Action |
Contact Software AG support. |
| XCO0048E | WAIT error. |
| Explanation |
The central wait routine has returned an unrecoverable error. X-COM nucleus terminates abnormally. |
| Action |
Contact Software AG support. |
| XCO0050E | MPM20-error. |
| Explanation |
The Terminate-Target call was unsuccessful. Shutdown will continue. |
| Action |
Contact Software AG support. |
| XCO0051W | MPM08-error, user gone. |
| Explanation |
The Get-User-Buffer call was unsuccessful. The user is probably not active any longer. Entire System Server purged this request from the queue. |
| Action |
No action required. |
| XCO0052W | MPM12-error, user gone. |
| Explanation |
The Post-User call was unsuccessful. The user is probably not active anymore. Entire System Server has purged this reply from the queue. |
| Action |
No action required. |
| XCO0053W | MPM36-OK, user gone. |
| Explanation |
The timeout call (TIME elapsed) for a user was successful. The user is probably not active anymore. Entire System Server has purged this reply from the queue. |
| Action |
No action required. |
| XCO0054W | MPM36-error, user not gone. |
| Explanation |
The timeout call (TIME elapsed) for a user was unsuccessful. Entire System Server has tried to purge the user, but the user fetched data back at the last moment. |
| Action |
No action required. |
| XCO0055I | Node currently :1:. |
| Explanation |
Output of command XSTAT. Possible value for :1: are ACTIVE (normal state) or HALTED (node is halted due to operator command XHALT). |
| Action |
No action required. |
| XCO0057I | OPERATOR ENTRY :1:. |
| Explanation |
Display operator entry status: active or inactive. |
| Action |
No action required. |
| XCO0061W | CANNOT LOCATE SUBSYSTEM MODULE :1:. |
| Explanation |
The loading of module :1: failed. |
| Action |
Check and verify whether the module :1: is in the library concatenation. If not, add the appropriate library containing the module :1:. Restart Broker. |
| XCO0062W | Request for active user found, delete old user. |
| Explanation |
There is already an active request for the user requesting a new call. The old session is queued for logoff and the new request has been assigned to a new session. The X-COM nucleus has removed the old resources used on the transport level. |
| Action |
No action required. |
| XCO0063E | BAD PARM CARD: :1:. |
| Explanation |
The parameter line :1: being currently processed is invalid. |
| Action |
Correct the parameter line :1:. Restart Broker. |
| XCO0077I | Attached buffers above 16M line. |
| Explanation |
Adabas Attached Buffers are allocated above the 16 MBytes line. |
| Action |
No action required. |
| XCO0078E | No space for new user X-COM block. |
| Explanation |
The number of free user X-COM blocks has been exceeded. This number depends on the NCQE parameter. Usually a command queue overflow will occur if the number of parallel user requests is exceeded. X-COM nucleus terminates abnormally due to data inconsistencies. |
| Action |
Contact Software AG support. |
| XCO0080E | MPM24-error, environment not established. |
| Explanation |
The Establish-Adabas-Environment call has failed. The Entire System Server terminates abnormally. |
| Action |
Contact Software AG support. |
| XCO0081E | MPM00-error, target not initialized. |
| Explanation |
The Initialize-Adabas-Target call has failed. The Entire System Server terminates abnormally. |
| Action |
Contact Software AG support. |
| XCO0082I | :1:. |
| Explanation |
TRACE data output. |
| Action |
No action required. |
| XCO0083W | Duplicate WAIT ECB. User cleaned up. |
| Explanation |
After successful return from request handler: The user was already waiting. The new request is accepted and the old command queue entry is purged. The old ECB is reused for the new request. |
| Action |
No action required. |
| XCO0084W | Multiple active requests. Delete old. |
| Explanation |
After successful return from reply handler: The command queue element of the user is not unique. Another element has been found with the same cross memory post information (z/OS only). The old request has been purged and the reply for the new request has been initiated. This occurs only if a task has been cancelled and immediately restarted and if the same ASCB has been reused. |
| Action |
No action required. |
| XCO0085W | Reply handling cancelled. Illegal ECB. |
| Explanation |
After successful return from reply handler: the reply cannot be delivered. The command queue element of the user is not unique. Another element has been found with the same cross-memory post information (z/OS only). The reply currently processed is obsolete and has been purged. This occurs only if a task has been cancelled and immediately restarted and if the same ASCB has been reused. |
| Action |
No action required. |
| XCO0086I | APPL ECB: :1:. |
| Explanation |
This message informs about the address of an Event Control Block. It will be issued only in conjunction with other messages. |
| Action |
No action required. |
| XCO0087E | MPM12-ERROR, CQE is not active. |
| Explanation |
Attempt to perform MPM12 function, but the command queue element (CQE) is not active. |
| Action |
No action required. |
| XCO0088I | Dead XCOM block killed. |
| Explanation |
XCOM user has gone away; so skip reply processing. |
| Action |
No action required. |
| XCO0089E | MPM36 impossible because CQE not active. |
| Explanation |
The MPM36 timeout function is skipped, since the command queue element (CQE) is not active. |
| Action |
No action required. |
| XCO0091I | SVC NOT SPECIFIED, SO THIS XCOM COMMAND IS NOT ALLOWED. |
| Explanation |
This informational message indicates that the XCOM operator command issued to the Broker is not allowed, since the Adabas SVC number for EntireX Broker access was set to zero in the startup parameters. |
| Action |
No action required. |
| XCO0095E | NCQE IS LOWER THAN NUM-WQE |
| Explanation |
The number of command queue entries (NCQE) specified is less than the number of work queue entries (NUM-WQE) requested. NCQE defines the number of requests active at one time using the NET transport. NUM-WQE defines the number of requests active at one time for all transports. |
| Action |
Ensure that the value for the number of command queue entries (NCQE) is equal to or greater than the number of work queue entries (NUM-WQE). Restart Broker |
| XCO2001E | Error during READ of startup parms. |
| Explanation |
Bad file format or I/O error during read of startup parameter file. |
| Action |
Parameter file must be a SAM or an ISAM file with variable or fixed record length. |
| XCO2002E | More than :1: parameter cards not possible. |
| Explanation |
The maximum number :1: of startup parms is exceeded. |
| Action |
Reduce the number of startup parm cards in your parameter file. Check the default values of the parameters to avoid setting the values explicitly. |
| XCO2003E | LOAD for module :1: failed - abend. |
| Explanation |
Module :1: could not be found. You need Entire System Server or Adabas libraries with module :1: to start the Entire System Server. |
| Action |
Copy the missing module into your library and start the Entire System Server again. Do not rename modules in the load libraries, e.g. from NAME to NAME.OLD. It could create problems during load. |
| XCO2004E | X-COM abended. |
| Explanation |
An unrecoverable error has occurred. X-COM terminates abnormally. |
| Action |
Look at the previous error messages of X-COM. |
| XCO2005E | Wrong X-COM parameter :1:. |
| Explanation |
An invalid value for :1: was specified in startup parameters. |
| Action |
Verify Entire System Server startup parameter :1: and set a proper value. |
| XCO2006E | ADAMPM - wrong version found. |
| Explanation |
The loaded module ADAMPM has a wrong version. |
| Action |
Check your Adabas library or contact Software AG. |
| XCO2007E | BS2000/OSD V.2 or above is required. |
| Explanation |
The Entire System Server is compiled for BS2000/OSD Version 2 or above. It cannot run on OSD Version 1 or below. |
| Action |
Upgrade of BS2000/OSD is required. |
| XCO2008E | MPM12-error, CQE is not active. |
| Explanation |
The Post-User call has been rejected due to bad status of command queue element. The reply cannot be delivered. |
| Action |
No action required. |
| XCO2009E | MPM36 impossible because CQE not active. |
| Explanation |
The timeout call (TIME elapsed) has been rejected due to bad status of command queue element. |
| Action |
No action required. |
| XCO2010E | Macro :1: RC :2:. |
| Explanation |
The BS2000/OSD macro :1: has returned an error. :2: contains the return code. X-COM nucleus terminates abnormally. |
| Action |
Contact Software AG support if return code does not explain the problem. |
| XCO2011E | MAIN MP - Macro :1: RC :2:. |
| Explanation |
The ESY MAIN memory pool creation has been aborted. The BS2000/OSD macro :1: has returned an error. :2: contains the return code. X-COM nucleus terminates abnormally. |
| Action |
Contact Software AG support if return code does not explain the problem. |
| XCO2012E | STACK FAILURE in function :1:. |
| Explanation |
The internal stack is corrupted. :1: identifies the failed function. X-COM nucleus terminates abnormally. |
| Action |
Contact Software AG support. |
| XCO2013E | Incompatible Adabas version detected. |
| Explanation |
This version of Adabas is no longer supported. An XS-enabled library is required to run with Entire System Server. X-COM nucleus terminates abnormally. |
| Action |
Upgrade of Adabas is required. |
| XCO2014E | MAIN MP - Requested space exceeded. |
| Explanation |
The allocated memory size is not sufficient to contain all required data structures of Entire System Server. X-COM nucleus terminates abnormally. |
| Action |
Contact Software AG support. |
| XCO2015E | Unrecoverable error in function :1:. |
| Explanation |
A function called by the X-COM nucleus has returned an error response. :1: identifies the called function. X-COM nucleus terminates abnormally. |
| Action |
Contact Software AG support. |