# General Reason Codes

The following table describes the general reason codes for Substation ES.

Code | Description
--- | ---
`260` | The number of interfaces to be started by Substation ES has exceeded the maximum allowed number.
User Response: Reduce the number of interfaces in the Substation ES Main SIP member defined by the `INTF-MEMBER` keyword.
`302` | `EVENT_WAIT_INV_COND`
An invalid (failed) event condition was returned for a Substation ES process that should have been successful.
`310` | `EVENT_LIST_FULL`
The number of entries on a Substation ES Event List has exceeded the maximum allowed. The most common reason is that the subtask or thread in error is not processing its list or the process has become disabled. User Response: If this condition persists or disrupts the execution of Substation ES, contact TIBCO Support with the information on the error from the log and trace files.
`400` | `TIMER_EXCEEDED`
The back-end interface tried to publish a response, but the ESB interface has not confirmed the delivery of the response message within its timed period. User Response: Check the status of the ESB and its EMS or RV interface.
`580` | `INTERFACE_INACTIVE`
This message could result from one of the following situations: A request or message is destined for an inactive interface. The BES to which the Substation ES interface is connected is inactive. An invalid interface ID is in the recipe. User Response: Determine the reason why the connection between the Substation ES interface and the BES has terminated and then connect the BES to the Substation ES interface and retry the process. If the problem persists, contact TIBCO Support with the information on the error from the log and trace files.
`888` | `REASON_RED_ERROR`
A Mainframe RED error was encountered. User Response: Refer to other messages or specific RED messages that were issued at the same time as this reason code. These should provide you with sufficient information to determine or resolve an issue.
`1012` | One or more of the libraries specified in the `STEPLIB` DD Name statement of the Substation ES startup procedure has not been authorized by APF.
User Response: Ensure all the libraries specified in the `STEPLIB` statement are APF authorized.
`1901` | `REASON_CONS_ROUTINE_FAIL`
The console routine has failed because of previously encountered errors. User Response: If this condition persists or disrupts the execution of Substation ES, contact TIBCO Support.
`2017` | `REASON_INVALID_MOI`
The back-end process was given a request with a method of invocation that it does not support. User Response: Correct the recipe being used to use a supported method of invocation or a BES that supports the method of invocation specified.
`2018` | `REASON_MSGLEN_GT_MAXLEN`
The response message generated is greater than the maximum length indicated by the service or Substation ES. User Response: Ensure that the response message length is less than recipe and system maximums.
`2029` | `REASON_NOT_CATERED_FOR`
For the Substation function call, there is no reason code returned. User Response: If this condition persists or disrupts the execution of Substation ES, provide whole Substation ES job log and contact TIBCO Support.
`2902` | `REASON_EVT_ADDR_INVALID`
The event address is invalid.
`2909` | `REASON_MSG_TIMEOUT`
The request did not receive the expected response within the timeout value. User Response: Check the other information in the message to determine the cause of the timeout.
`2966` | `REASON_EVENT_MAX_RETRY_LOCK`
While trying to gain access to a locked ECB, the timeout value was exceeded and an error was returned with this value. User Response: If this condition persists or disrupts the execution of Substation ES, contact TIBCO Support with the information on the error from the log and trace files.
`3977` | `REASON_SERVICE_SUSPENDED` Service has been suspended either by the user or because an endpoint has become inactive. For example, if an ESB is disconnected from a Back-end system (BES).
User Response: Issue the operational command SHOW,SUSPENDED to see whether your service is suspended. Other information related to this, such as disconnects, could help determine the reason why the service was suspended.
`3979` | `REASON_SERVICE_NOT_FOUND` Service name could not be found in the configured deployment. This reason is also sometimes used when a general issue to obtain the service name has failed.
User Response: Check that the service request that is in error has been defined correctly in the configuration file. Make sure that the service has not been disabled for some reason. An operational command issued from Mainframe WebUI informs application personnel about the status of all services, recipes and triggers.

Copyright © TIBCO Software Inc. All rights reserved.