This documentation lists all error messages and codes issued by the Entire Event Management Server.
Expl.: | This message informs the user that the indicated task has been started successfully. It is always displayed on the master console. |
Actn.: | No action required. |
Expl.: | INTERNAL ERROR. This message indicates that an unexpected task name has been passed from another task. Current task terminates abnormally. |
Actn.: | Contact Software AG Support. |
Expl.: | The indicated task was terminated abnormally. The protocol dataset assigned to the task contains detailed information about the possible reason. |
Actn.: | Analyse the related protocol dataset. If you cannot remove the reason for the problem, please contact Software AG Support. |
Expl.: | This message is issued for the Main, Collect, Analysis, Logging and Action Tasks when the online user requests a Server shutdown. |
Actn.: | No action required. |
Expl.: | The Server object identified by its node number was not found in the directory file (System File 2). |
Actn.: | Add the Server object using the Entire Event Management Administration System. |
Expl.: | The Task indicated has been restarted. The reason
can be found in correlated messages:
|
Actn.: | Depends on correlated messages. |
Expl.: | INTERNAL ERROR within inter-task communication. |
Actn.: | Contact Software AG Support. |
Expl.: | This message informs you that a runtime error has occurred during the Server Termination process. |
Actn.: | No action required. |
Expl.: | An internal error was detected in the program indicated. |
Actn.: | Contact Software AG Support. |
Expl.: | The operating system indicated is not yet supported by Entire Event Management. |
Actn.: | Contact your Software AG System Consultant. |
Expl.: | INTERNAL ERROR within inter-task communication. |
Actn.: | Please contact Software AG Support. |
Expl.: | The Node object identified by its Node number was not found in the directory file (System File 2). |
Actn.: | Add the Node object using the Entire Event Management Online Administration System. |
Expl.: | The LFILE assignment for the indicated Logical File Number is wrong. |
Actn.: | Check / change your NATURAL LFILE Environment Settings. |
Expl.: | INTERNAL ERROR occurred in program NAT00009 when accessing the STEPLIB Table. |
Actn.: | Contact Software AG Support. |
Expl.: | INTERNAL ERROR. |
Actn.: | Please contact Software AG Support. |
Expl.: | This message informs you that the Adabas response code :1: was returned during the access indicated by :2:. |
Actn.: | Analyze the situation. If the indicated error cannot be avoided by appropriate environment customization, please contact Software AG support. |
Expl.: | The Entire System Server Node indicated by :2: returned error code when forwarding an Action request to the Execution Server identified by Node number :2:. Correlated message: 5231. |
Actn.: | For detailed explanation of this error code please refer to the Entire System Server Messages and Codes Manual. See also correlated messages in the (Aut...) Console related to the forwarding Server. |
Expl.: | INTERNAL ERROR. The Calendar Table handling routine encountered an unexpected error. |
Actn.: | Please contact Software AG Support. |
Expl.: | The error code :1: was returned from the QHNDLR module when accessing the main storage area identified by :2: using function :3:. For example: "Response 40 using function PUT" means that no free main storage slot could be allocated in the queue indicated by :2: to hold a new element. |
Actn.: | In case of Response 40: increase the Server Parameters 'Initial Size of Active Queues' and RENEW the Server. In all other cases: contact Software AG Support. |
Expl.: | The buffer size reserved for holding variables in keyword/value not is too small. |
Actn.: | Contact Software AG Support. |
Expl.: | The dimension of the array reserved for holding variables as keyword/value table is too small. |
Actn.: | Contact Software AG Support. |
Expl.: | The name of the indicated Symbol is longer than allowed. This is probably a user error. |
Actn.: | Use only Symbol names with allowed length. |
Expl.: | The reference to the indicated Symbol contained in string cannot be replaced by the Symbol value. |
Actn.: | Please contact Software AG support. |
Expl.: | INTERNAL ERROR. |
Actn.: | Please contact Software AG Support. |
Expl.: | This message informs the user that the RENEW process for the object definitions linked to the Server has been started. Correlated messages: 5041 and 5042. |
Actn.: | No action required. |
Expl.: | This message informs the user that the RENEW process for the object definitions linked to the Server has been completed successfully. Correlated messages: 5040 and 5042. |
Actn.: | No action required. |
Expl.: | After a successful RENEW request, this message informs the user that the analysis of the following messages is based on the new definitions. Correlated messages: 5040 and 5041. |
Actn.: | No action required. |
Expl.: | When the Server starts or renews the definitions, the Natural Buffer Pool is automatically refreshed for the user-written Natural programs located in the indicated Action Program Library. |
Actn.: | No action required. |
Expl.: | This message indicates that the Reporting Task has detected that the related task :1: has abended. In consequence, a new subtask will be attached, which performs a forced termination of all Server tasks and asks the operator if the Server should be restarted. |
Actn.: | See correlated messages NCL9998 and NCL9999, which appear on the System Console. |
Expl.: | This message is issued in response to Adabas response code 148. Parameter :1: provides the logical name of the database. The correlated messages, which the error exit writes to the task-specific protocol dataset, contain detailed information about the physical database and file number. The Server temporarily suspends communication to this database and tests availability from time to time. If the database is available again, the Server resumes normal communication. If Response Code 148 is returned by the FNAT where the Server application is located, or by the Definition Database during startup, the Server will terminate abnormally. |
Actn.: | Analyze which database is affected and perform actions necessary to restart the database. |
Expl.: | This message means that the Server identified by its Node number :1 has started. Parameter :2: contains the product version. Parameter :3: contains an intermediate update level which is irrelevant for released versions. |
Actn.: | No action required. |
Expl.: | This message indicates that after 10 access retries of the Server, Backup File is still in use by another user. Most probably an online user is browsing the file. |
Actn.: | Find out who is accessing the file via an online session and unlock file. |
Expl.: | The Backup File used by the Server to download/load its definitions is temporarily blocked by another user. |
Actn.: | No action required. |
Expl.: | INTERNAL ERROR. The first records in the Backup File are expected to have record type 'HD' (header). |
Actn.: | Please contact Software AG Support. |
Expl.: | INTERNAL ERROR. |
Actn.: | Please contact Software AG Support. |
Expl.: | INTERNAL ERROR. Each logical record of a specific type consists of multiple segments identified by a sequence number. The segment currently being processed contains an incorrect sequence number. |
Actn.: | Please contact Software AG Support. |
Expl.: | INTERNAL ERROR. The record currently being processed contains an undefined record type. |
Actn.: | Please contact Software AG Support. |
Expl.: | INTERNAL ERROR. |
Actn.: | Please contact Software AG Support. |
Expl.: | INTERNAL ERROR. The Backup File record currently being processed contains an invalid Action type. |
Actn.: | Please contact Software AG Support. |
Expl.: | This message means that a process has been started which downloads the subset of definitions linked to the Server from the database System File 2 to the Backup File. |
Actn.: | No action required. |
Expl.: | This message informs the user that the Server has successfully copied his working subset of object definitions from the database System File 2 to the sequential Backup File. |
Actn.: | No action required. |
Expl.: | This message indicates that the Server did not copy a working subset of object definitions from the database (System File 2) to the sequential Backup File. As a result, if the Server is starting, it will terminate abnormally. If the Server was RENEWED, it will stay active and resume work as soon as a non-empty working subset is downloaded in response to a second RENEW request. |
Actn.: | Make sure that a non-empty subset of active Logical Consoles is linked to the Server definition before you start or renew the Server. |
Expl.: | This message means that a process has started which loads the working subset of object definitions from the sequential Backup File into main storage queues for faster analysis. |
Actn.: | No action required. |
Expl.: | This message means that the Server has successfully loaded the working subset of object definitions from the sequential Backup File into main storage for faster analysis. |
Actn.: | No action required. |
Expl.: | This message indicates that the Server did not load a working subset of object definitions from the sequential Backup File into main storage. As a result, if the Server is starting, it will terminate abnormally. If the Server was RENEWED, it will stay active and resume work as soon as a non-empty working subset of object definitions is loaded in response to a second RENEW request. |
Actn.: | Make sure that the sequential Backup File used contains a non-empty set of object definitions before you start or renew the Server. |
Expl.: | This message indicates that the Calendar identified by :1: and assigned to Logical Console :2: does not cover the current year. Therefore, the Logical Console indicated is considered active on all days of the current year. See also the correlated messages 5121 and 5124. |
Actn.: | Expand the corresponding Calendar definition to cover the current year and renew the Server. |
Expl.: | This message indicates that the Calendar :1: which is assigned to Logical Console :2: does not cover the next year. Therefore, the Logical Console indicated is considered active on all days of the next year. See also the correlated messages 5120 and 5124. |
Actn.: | Expand the corresponding Calendar definition to cover the next year and renew the Server. |
Expl.: | This message indicates that the Calendar :1: which is assigned to Automation Rule :2: does not cover the current year. Therefore, the Automation Rule indicated is considered active on all days of the current year. See also the correlated messages 5123 and 5124. |
Actn.: | Expand the corresponding Calendar definition to cover the current year and renew the Server. |
Expl.: | This message indicates that the Calendar :1: which is assigned to Automation Rule :2: does not cover the next year. Therefore, the Automation Rule indicated is considered active on all days of the next year. See also the correlated messages 5122 and 5124. |
Actn.: | Expand the corresponding Calendar definition to cover the next year and renew the Server. |
Expl.: | See correlated messages 5120 and 5121 or 5122 and 5123 respectively The message means that all days of the related year are active regarding the activity of the Logical Console indicated in message(s) 5120 and/or 5121 or the activity of the Automation Rule indicated in message(s) 5122 and/or 5123. |
Actn.: | See the correlated messages. |
Expl.: | Informs the user that the Server has loaded :1: Logical Consoles in main storage. |
Actn.: | No action required. |
Expl.: | Informs the user that the Server has loaded :1: Message Ranges into main storage. |
Actn.: | No action required. |
Expl.: | Informs the user that the Server has loaded :1: Root Events into main storage. |
Actn.: | No action required. |
Expl.: | Informs the user that the Server has loaded :1: Dependent Events in main storage. |
Actn.: | No action required. |
Expl.: | Informs the user that the Server has loaded :1: Actions into main storage. |
Actn.: | No action required. |
Expl.: | Informs the user that the Backup Files exist and are correctly formatted. |
Actn.: | No action required. |
Expl.: | Confirms that the user started the Server with parameter NCLREFR = which means that the working subset of object definitions was not refreshed. |
Actn.: | No action required. |
Expl.: | Means that the Events used for inter-task communication have been successfully defined. |
Actn.: | Action: No action required. |
Explanation:
Expl.: | Means that the Server has attached the other subtasks successfully. |
Actn.: | No action required. |
Expl.: | Means that the Logical Console :1: has been loaded into main storage and is available for analysis. |
Actn.: | No action required. |
Expl.: | Means that the Range :1: has been loaded into main storage and is available for analysis. |
Actn.: | No action required. |
Expl.: | Means that the Event with Level :2: identified by :1: has been loaded into main storage and is available for analysis. |
Actn.: | No action required. |
Expl.: | Means that the Action :1: has been loaded into main storage and is available for analysis. |
Actn.: | No action required. |
Expl.: | During the analysis of the current message, the Server detected that too many Ranges were matched. The Ranges which exceeded the maximum are lost. As a result, the message will be available only in those Logical Consoles which have a link to the Ranges received so far. |
Actn.: | Check the Messages Ranges which could be matched by the current message and refine your Message Range definitions where necessary. |
Expl.: | INTERNAL ERROR. Correlated message 5203. |
Actn.: | Contact Software AG Support. |
Expl.: | INTERNAL ERROR. Correlated message 5202. |
Actn.: | Contact Software AG Support. |
Expl.: | INTERNAL ERROR. Correlated messages 5202, 5203 and 5206. |
Actn.: | Contact Software AG Support. |
Expl.: | This message precedes the most recently analyzed Console message, which could not be reprocessed by the Analysis Task after restart. |
Actn.: | Analyze protocol dataset related to the Analysis Task and find out reason for the restart. |
Expl.: | INTERNAL ERROR. Correlated message 5202,5203 and 5204. |
Actn.: | Contact Software AG Support. |
Expl.: | INTERNAL ERROR. |
Actn.: | Contact Software AG Support. |
Expl.: | The current message triggered an Event definition for which the use assigned a Symbol Table containing the keyword variable :1:. However, this keyword could not be found within the current message text. Correlated message 5220. |
Actn.: | Find the correlated Event in the (Aut...) Console related to the Se and check the Event definition. |
Expl.: | This message indicates an overflow of the internal table of user-defined variables which is assigned to the current Automation Rule. Correlated message 5220. |
Actn.: | Find the correlated Event in the (Aut...) Console related to the Server and check the Symbol Tables assigned to the Event(s) of the Automation Rule. |
Expl.: | All deferred Actions are kept in an internal table until the delay has elapsed. This message indicates that all table entries are used. Correlated message 5213. |
Actn.: | Contact Software AG Support. |
Expl.: | See the correlated message 5211. |
Actn.: | See the correlated message 5211. |
Expl.: | INTERNAL ERROR. Correlated messages 5202,5203 and 5216. |
Actn.: | Contact Software AG Support. |
Expl.: | Correlated messages 5202,5203 and 5215. |
Actn.: | Contact Software AG Support. |
Expl.: | This message precedes the most recent frozen message, which could n be reprocessed by the Analysis Task after restart. |
Actn.: | Analyze protocol dataset related to the Analysis Task and find out reason for the restart. |
Expl.: | Because of an error condition, the current Event was not inserted i Active Queue. Correlated messages 5208 or 5210. |
Actn.: | See the correlated messages 5208 or 5210. |
Expl.: | The Server has detected a loop condition in the Automation Rule indicated. This loop occurred when the Rule was repeatedly triggered by an identical message text with identical job number. A loop is assumed if identical message text with identical job number triggers the Rule during the 'Rule Timeout' period more often than indicated by the 'Event Loop Frequency' parameter. Correlated messages 5222 and 5223. |
Actn.: | Find the correlated Event in the (Aut...) Console related to the Server and check the Rule definition. |
Expl.: | Correlated message 5221 (loop in Automation Rule). |
Actn.: | See the correlated message 5221. |
Expl.: | Correlated message 5221 (loop in Automation Rule). |
Actn.: | See the correlated message 5221. |
Expl.: | This message confirms that this Action was forwarded to the Server as requested within the corresponding Action definition (Attribute 'Execution Server'). Correlated message 5403. |
Actn.: | No action required. |
Expl.: | The message means that, because of an ESY error (indicated in correlated message 5020), the Action was not routed to Server :3: as required in the correlated Action specification. |
Actn.: | Find the related Event in the (Aut...) Console related to the Serve and check the corresponding Action definition. |
Expl.: | This message indicates the number of messages which were lost during a restart of a task. |
Actn.: | Analyze the protocol dataset to find the reason for the restart. |
Expl.: | Action was not performed because of an ESY error which precedes this message. |
Actn.: | Analyze the protocol dataset related to the Action Task to find out the reason for the ESY error. You can find the related Action definition by looking for the related Event in the (Aut ..) Console. |
Expl.: | This error message indicates that the program which implements the mentioned standard action, was not found in the internal correlation table. |
Actn.: | Please contact Software AG Support. |
Expl.: | This message confirms that the Server has received the Action forwarded by the Server :3:. Correlated message 5230. |
Actn.: | No Action required. |
Expl.: | This message means that the referred Symbol name was not found in the variable buffer provided and therefore the Symbol reference could not be replaced by the corresponding variable value. This is probably a user error. |
Actn.: | Make sure that the Symbols referred to in Action specifications are available either in user-defined Symbol Tables or as Symbols provided by the system. |
Expl.: | The Collect Task receives the Console messages from a wraparound table This message indicates the number of messages which were overwritten because of a high message volume. |
Actn.: | Under z/OS or z/VSE, increase the Entire System Server parameter 'CONS'. Under BS2000/OSD, increase the 'BUFFER' parameter in the ESYCONS JCL. Restart the NCL Server after having bounced the Entire System Server. |
Expl.: | This means that the Collect Task lost the last message after restart. |
Actn.: | See protocol dataset of the Collect Task to find out the reason for the restart. |
Expl.: | Means that the user indicated has requested to renew the Server. This message appears on the System Console. |
Actn.: | No action required. |
Expl.: | Means that the user indicated has requested to shut down the Server. This message appears on the System Console. |
Actn.: | No action required. |