# Codes and Descriptions

The following table describes the CICS reason codes.

Code | Description
--- | ---
`3005` | A CICS Program Abended The CICS business application program did not return normally; the program was abnormally terminated by CICS or the business program issued its own ABEND call.
User Response: Check with the business program support group as to why the business program terminated abnormally.
`3006` | CA_LEN_INVALID Either the `DFHCOMMAREA` pointer cannot be obtained or the User Area length is invalid.
User Response: Contact TIBCO Support with the information on the error from the log and trace files.
`3010` | SS_NO_STARTUP The Substation ES CICS startup routine `SXCOSTRT` has not been defined or has failed during the startup of the CICS region. Additionally, the primary Substation ES `TSQ SXCTSQES` might have been deleted. The `SXCOSTRT` program outputs the following message after initializing its storage: `@SXC3700I Substation ES CICS initialization complete`
User Response: Ensure that the CICS PLT definitions of Substation ES have been assembled and that they are in a load library concatenated in the `DFHRPL` DD Name of the CICS startup JCL. Also ensure that the Substation ES load module library is in the `DFHRPL` concatenation. You can manually execute the `SXCOSTRT` program from CICS by starting the `SXTS` transaction. View the errors recorded by Substation ES programs in the CICS region with the `SXTH` transaction. Subsequently, delete the old error-queue records.
`3011` | SS_NO_TOKEN The pointer to the Substation ES Anchor Control block is stored in a z/OS token. If this token is not available, then functions of Substation ES will not be able to run properly since they do not have access to the Substation ES control blocks in CICS.
User Response: Make sure program SXCOSTRT was run correctly. This program usually is executed using a PLT at CICS startup. Message `SXC3700I` should be displayed in the CICS JESLOG.
`3012` | SS_MAX_INTF_CONNECT The maximum number of five (5) connections to a single CICS region has been exceeded.
User Response: No more Substation ES instances can connect to this CICS region.
`3013` | REASON_INIT_FAILED The RED for CICS server program `SXCOREDA` failed to initialize the system correctly.
User Response: Inspect the messages that were sent back to Substation ES and the return and reason codes associated with these messages. Rectify the error condition and either recycle Substation ES or manually disconnect and reconnect to the specified CICS region.
`3040` | CICS_DT_ERROR Request for CEE time failed. The CICS Substation ES module `SXCREQR` returned the error status to the business application program and ignored the Request-Reply request.
User Response: Determine why the CEELOCT failed. Correct the situation and rerun the business program.
`3041` | CICS_NO_CONTAINER No Container Passed. The CICS Substation ES module `SXCQWRIT` or `SXCQWTSQ` returned the error status to the business application program and ignored the Trigger request. `SXCQWRIT` or `SXCQWTSQ` was expecting a Container for Parameter Input and did not find one.
User Response: Determine why the container does not exist and correct the situation. Rerun the business program.
`3050` | INV_PGM_NAME An inquiry of a program name specified either on an input parameter or on a queue resource definition has failed.
User Response: View the errors recorded by Substation ES programs in the CICS region with the `SXTH` transaction. Subsequently, delete old error-queue records.
`3051` | INV_EXECUTION Error Returned from `SXCOINQ`. The CICS Substation ES module SXCOINQ returned an error status to the business application program and ignored the Inquiry request.
User Response: Determine why the error occurred. Correct the situation and rerun the business program.
`3060` | SS_INTF_STG_FREE Interface Storage Block missing. The CICS Substation ES module `SXCOSRVA` or `SXCOSRVT` tried to access the Substation ES interface storage area and found it missing. This is a CRITICAL error.
User Response: Determine why the storage area is missing. Correct the situation and rerun the business program.
`3100` | CICS_CALL_FAIL The call to a CICS region or a resource within the CICS region making a CICS API call has failed.
User Response: Review the related error message, correct the error condition, and retry the process. If the problem persists, contact TIBCO Support with the information on the error from the log and trace files.
`3101` | EXCI_CALL_FAIL An `EXCI` call made by the Substation ES interface has failed. This error usually occurs as a result of one or more of the following conditions: Certain CICS resources have been defined incorrectly. One or more Substation ES CICS SIP parameters are incorrect. The CICS region is inactive. The CICS program that is being invoked has abended.
User Response: Review the related error message, correct the error condition, and retry the process. If the problem persists, contact TIBCO Support with the information on the error from the log and trace files.
`3102` | EXCI_DPL_FAIL An `EXCI` DPL call made by the Substation ES interface has failed. This error usually occurs as a result of one or more of the following conditions: A resource that is being invoked has been defined incorrectly. The resource name on the recipe definition is incorrect. The resource is not available in the CICS region.
User Response: Review the related error message, correct the error condition, and retry the process. If the problem persists, contact TIBCO Support with the information on the error from the log and trace files.
`3124` | CA_LEN_EXCEEDED Refer to the error message `SXC3124E`.
`3206` | NO_MORE_CICS The CICS region is or has been terminated and the Substation ES CICS interface can no longer communicate with the CICS region. The Substation ES CICS Interfaces connected to the specified CICS region is disconnected gracefully.
User Response: When the CICS region becomes available, reconnect the Substation ES interface to the CICS region with the operator command.
`3208` | CICS_BES_DISCONNECTED Substation ES was in the process of starting a CICS transaction using EXCI, and EXCI has notified Substation ES that the CICS interface is not available.
System Action: Substation ES returns the response with an error status.
`3404` | GETMAIN_FAIL A request to obtain storage from a Substation ES CICS program has failed.
User Response: Determine if short on storage (SOS) conditions exist in CICS. View the errors recorded by the Substation ES programs in the CICS region with the `SXTH` transaction. If the problem persists, contact TIBCO Support with the information on the error from the log and trace files.
`3405` | WTO_START_FAIL An attempt was made to issue a WTO (message to the operator console, syslog) and it failed.
User Response: None.
`3410` | TSQ_READ_FAIL A request from a Substation ES CICS program to read a TSQ has failed.
User Response: View the errors recorded by the Substation ES programs in the CICS region with the SXTH transaction. If the problem persists, contact TIBCO Support with the information on the error from the log and trace files.
`3411` | TSQ_READ_QIDERR A request from a Substation ES CICS program to read the Substation ES main TSQ (`SXCTSQES`) has failed. Either the Substation ES CICS startup program `SXCOSTRT` has failed or something has deleted the TSQ. In Substation ES, the shutdown program SXCOSHUT is the only one that deletes the main TSQ.
User Response: Substation ES must be disconnected from the CICS region. Execute the program SXCOSTRT with the SXTS transaction. You can then reconnect to the CICS region. If you cannot determine the cause of the problem, contact TIBCO Support with the information on the error from the log and trace files.
`3412` | TSQ_WRITE_FAIL A request from a Substation ES CICS program to write a TSQ has failed.
User Response: View the errors recorded by the Substation ES programs in the CICS region with the SXTH transaction. If the problem persists or you cannot resolve it, contact TIBCO Support with the information on the error from the log and trace files.
`3413` | TSQ_REWRITE_FAIL A request from a Substation ES CICS program to rewrite a TSQ record has failed.
User Response: View the errors recorded by the Substation ES programs in the CICS region with the SXTH transaction. If the problem persists or you cannot resolve it, contact TIBCO Support with the information on the error from the log and trace files.
`3414` | TSQ_DELETE_FAIL A request from a Substation ES CICS program to delete a TSQ record entry has failed. An existing record in the queue cannot be deleted with the key provided.
User Response: Contact TIBCO Support with the information on the error from the log and trace files.
`3415` | TSQ_READ_LENGERR Length Error on READQ TS. The CICS Substation ES module `SXCOSRVT` tried to access the TSQ for a CICS Request-Reply process. However, the maximum Request-Reply size in Substation ES is smaller than the message to be sent. The `SXCREQR` returns an error to the business process.
User Response: Determine why the Request-Reply message is greater than the Substation ES RR-MAXSIZE parameter in the CICS interface definition. Correct the situation and rerun the business program.
`3416` | TSQ_READ_LENGBIG Length Error on READQ TS. While reading a segment of a large message into memory, the CICS Substation ES module `SXCOSRVG` did not have enough buffer area to retrieve the TSQ record.
User Response: Contact TIBCO Support.
`3418` | TSQ_NONEMPTY_INACTIVE HVS TSQ is not empty. While initializing, the CICS Substation ES SXCOSRVA module found HVS TSQ data. However, the parameter HVS-WORKERS is zero. Trigger Messages in HVS TSQ will not be processed.
User Response: Determine why HVS data is present when HVS is turned off and correct the situation. Rerun the business program.
`3419` | TSQ_NOSPACE CICS TSQ is full. The CICS DFHTEMP returned a `FULL` status after attempting a WRITEQ TS. Trigger Messages in HVS TSQ will not be processed.
User Response: Determine why `DFHTEMP` is out of space and correct the situation. Rerun the business program.
`3420` | TDQ_READ_FAIL A request from a Substation CICS program to read a TDQ has failed.
User Response: View the errors recorded by the Substation programs in the CICS region with the SXTH transaction. If the problem persists or you cannot resolve it, contact TIBCO Support with the information on the error from the log and trace files.
`3422` | TDQ_WRITE_FAIL A request from a Substation ES CICS program to write a TDQ has failed.
User Response: View the errors recorded by the Substation programs in the CICS region with the SXTH transaction. If the problem persists or you cannot resolve it, contact TIBCO Support with the information on the error from the log and trace files.
`3423` | TDQ_INQ_FAIL A request from a Substation ES CICS program to inquire about a TDQ definition has failed.
User Response: Contact TIBCO Support with the information on the error from the log and trace files.
`3428` | REASON_TDQ_NONEMPTY_INACTIVE HVT TDQ is not empty. While initializing, the CICS Substation ES `SXCOSRVA` module found HVT TDQ data. However, the parameter HVT-WORKERS is zero. Trigger Messages in HVT TDQ will not be processed.
User Response: Determine why HVT data is present when HVT is turned off and correct the situation. Rerun the business program.
`3429` | REASON_TDQ_NOSPACE CICS TDQ is full. The CICS `DFHINTRA` returned a `FULL` status on trying to do a WRITEQ TD. Trigger Messages in HVT TDQ will not be processed.
User Response: Determine why `DFHINTRA` is out of space and correct the situation. Rerun the business program.
`3432` | REASON_CON_GET_FAIL No User Data Container Passed. The CICS Substation ES module `SXCQWRIT` or `SXCQWTSQ` returned the error status to the business application program and ignored the Trigger request. `SXCQWRIT` or `SXCQWTSQ` was expecting a Container for User Data as Input and did not find one.
User Response: Determine why the container does not exist and correct the situation. Rerun the business program.
`3434` | REASON_CON_PUT_FAIL Cannot Create Response Container. The CICS Substation ES module `SXCQWRIT` or `SXCQWTSQ` returned the error status when attempting to write back the parameter container.
User Response: Determine why the container put got an error and correct the situation. Rerun the business program.
`3438` | REASON_CON_GET_LENERR Container Length is Zero. The CICS Substation ES module `SXCQWRIT` or `SXCQWTSQ` performed a container GET and got a length of zero.
User Response: Determine why the container has a length of zero and correct the situation. Rerun the business program.
`3440` | WAITEXT_TIME_EXP (TIMEOUT) A timeout has occurred, that is, the time specified by the users who requested the application has expired. This condition occurs if the Substation ES CICS request or reply facility has been invoked but an expected response has not been received.
User Response: The application can increase the wait time. Ensure that the recipe definition is correct and invoke the SXCREPLY program. See the TIBCO Substation ES Operations and Administration Guide for information on the CICS-initiated Request or Reply Facility. Also see Prereporting Steps. System Action: A reason code is returned to the user application; all CICS resources are released; and all other processing can continue. However, no data is returned to the requesting application.
`3441` | WAITEXT_FAIL A request from a Substation ES CICS program to wait on a z/OS type ECB has failed.
User Response: View the errors recorded by the Substation ES programs in the CICS region with the SXTH transaction. If the problem persists or you cannot resolve it, contact TIBCO Support with all the related information on the error.
`3445` | REASON_ROLLBACK_FAIL The Syncpoint Rollback failed in an Abend Handle routine. The CICS Substation ES module `SXCOABND` trapped a business process abend. While issuing a `SYNCPOINT` `ROLLBACK`, CICS returned an Error. The changes made by the business process might not have been backed out.
User Response: Determine whether changes made by the business process have been backed out. From the CICS error codes, determine why CICS did not allow a "ROLLBACK". Correct the situation and re-run the transaction. System Action: CICS processing continues.
`3450` | WTO_START_FAIL Substation ES in CICS attempted to issue a Write-To-Operator (WTO) message, which failed.
User Response: Look at the CICS JESLOG and MSGUSR for reasons why the WTO failed. For example, check for security issues. System Action: If the program is `SXCOSTRT`, then the CICS setup did not complete correctly. It's imperative to fix the CICS problem(s) and re-cycle the CICS region. If the program is SXCOEVPA, then CICS error messages might not be processing correctly. Fix the CICS problem and re-cycle the CICS region.
`3460` | DELAY_FAIL A request from a Substation ES CICS program to delay processing for a period of time has failed.
User Response: If the problem persists or you cannot resolve it, contact TIBCO Support with all the related information on the error. System Action: The applications continue processing. However, you must rectify this error as soon as possible because unpredictable results might occur if this condition recurs frequently.
`3464` | ADDRESS_FAIL A request from a Substation ES CICS program to obtain the `EIB` or `DFHCOMMAREA` address has failed.
User Response: View the errors recorded by Substation ES programs in the CICS region with the SXTH transaction. If the problem persists or you cannot resolve it, contact TIBCO Support with the information on the error from the log and trace files.
`3470` | INCOMPAT_VERSION A call to SXCOSRVM (Substation ES 3270 support in CICS) did not have the correct version number in the input data.
User Response: Correct the version number in the input data and make sure the proper structure is being used. System Action: The request is not processed. The user application must reschedule or retry the request.
`3480` | START_TRAN_FAIL A request from a Substation ES CICS program to start a CICS transaction failed.
User Response: View the errors recorded by the Substation ES programs in the CICS region with the SXTH transaction. If the problem persists or you cannot resolve it, contact TIBCO Support with the information on the error from the log and trace files.
`3482` | LINK_FAIL A request from a Substation ES CICS program to link to another CICS program has failed.
User Response: View the errors recorded by Substation ES programs in the CICS region with the SXTH transaction. If the problem persists or you cannot resolve it, contact TIBCO Support with the information on the error from the log and trace files.
`3483` | XCTL_FAIL A request from a Substation ES CICS program to transfer control to another CICS program has failed.
User Response: View the errors recorded by Substation ES programs in the CICS region with the SXTH transaction. If the problem persists or you cannot resolve it, contact TIBCO Support with the information on the error from the log and trace files.
`3500` | ASS_STARTCODE_FAIL Certain programs inquire about how they were initiated, enabling them to perform the correct task. In this case, a request from a Substation ES CICS program to inquire about a CICS `STARTCODE` has failed.
User Response: View the errors recorded by Substation ES programs in the CICS region with the SXTH transaction. If the problem persists or you cannot resolve it, contact TIBCO Support with the information on the error from the log and trace files.
`3520` | SERVICE_NOTFOUND A call to SXCQWRIT (Substation ES HVT program in CICS) is asking to use a service (R for reliable, G for guaranteed, O for ordered). The Substation ES interfacing with the CICS is not providing the service.
User Response: Correct the business program to use a service provided or change Substation ES to add the service. System Action: The request is not processed. The user application must reschedule or retry the request.
`3601` | CTR_PUT_FAIL Program attempted a PUT Container and CICS returned an error response.
User Response: Review the CICS error codes to determine why the CICS API command failed. Correct the situation and re-try. System Action: The request is not processed. The user application must reschedule or retry the request.
`3602` | CTR_GET_FAIL Program attempted a GET Container and CICS returned an error response.
User Response: Review the CICS error codes to determine why the CICS API command failed. Correct the situation and re-try. System Action: The request is not processed. The user application must reschedule or retry the request.
`3603` | CTR_DELETE_FAIL Program attempted a DELETE Container and CICS returned an error response.
User Response: Review the CICS error codes to determine why the CICS API command failed. Correct the situation and re-try. System Action: The request is not processed. The user application must reschedule or retry the request.
`3620` | BROWSE_START Program attempted a START BROWSE Container and CICS returned an error response.
User Response: Review the CICS error codes to determine why the CICS API command failed. Correct the situation and re-try. System Action: The request is not processed. The user application must reschedule or retry the request.
`3621` | BROWSE_END Program attempted an END BROWSE Container and CICS returned an error response.
User Response: : Review the CICS error codes to determine why the CICS API command failed. Correct the situation and re-try. System Action: The request is not processed. The user application must reschedule or retry the request.
`3800` | MAX_RR_SESSIONS A request from a user application to invoke a CICS-initiated Request or Reply facility has been disallowed. The maximum number of allowable concurrent sessions per CICS region has been exceeded.
User Response: Determine why so many request or reply sessions are concurrently active. If a user transaction is being started to invoke the request or reply facility, you might have to define a transaction class to limit the number of active tasks that invoke the request or reply facility. If the problem persists or you cannot resolve it, contact TIBCO Support with the information on the error from the log and trace files. System Action: The request is not processed. The user application must reschedule or retry the request.
`3802` | RR_ENVELOPE_INV The CICS-initiated request or reply facility has received a reply through the program `SXCREPLY`. However, either the data in the envelope is invalid or it contains binary zeros.
User Response: A Hex display of the content in the envelope field is written to the `CEEMSG` in the CICS JES output. Search for the header `RR Envelope` in the CEEMSG file. If the envelope’s content contains binary zeros, one or more of the following conditions exist: The recipe definitions do not specify the tibss-envelope field on the input conversion. The application that sends the reply did not return the tibss-envelope field unchanged. The tibss-envelope field on the reply conversion rule must specify a System field. That is, in the field conversion rule panel, specify `Trunc=S` and `Reqd=Y`. If you cannot decipher the envelope field or the problem persists, contact TIBCO Support. Before reporting the error, see Prereporting Steps.
`3803` | RR_ENVELOPE_TASK_INV The CICS-initiated request or reply facility has received a reply through the program `SXCREPLY`. Either of the following conditions exists: The CICS transaction number in the envelope is invalid. The CICS transaction that is to receive the data has completed or timed out or has been cancelled.
User Response: View the errors recorded by the Substation ES programs in the CICS region with the SXTH transaction. If the problem persists or you cannot resolve it, contact TIBCO Support with the information on the error from the log and trace files.
`3804` | RR_ENVELOPE_DT_INV The CICS-initiated request or reply facility has received a reply through the program `SXCREPLY`. The date-time stamp in the envelope is invalid or does not correspond to an entry in the Substation ES request or reply storage area. This could be an internal error. Another possible cause for this error is that the envelope information was contaminated during the conversation process.
User Response: If you cannot decipher the envelope field or the problem persists, contact TIBCO Support. Before reporting the error, see Prereporting Steps.
`3805` | RR_INV_STATUS The CICS-initiated Request or Reply facility has received a reply through the program `SXCREPLY`. The status of the request or reply storage entry is invalid or the user application has timed out. If the problem persists, it could be caused by an internal storage error.
User Response: View the errors recorded by the Substation ES programs in the CICS region with the SXTH transaction. If the problem persists or you cannot resolve it, contact TIBCO Support.
`3808` | RR_NO_PTR_2_STG The CICS request or reply facility’s timeout program scans for users applications that have exceeded the wait time specified for the call. In this case, the program cannot locate the internal storage area.
User Response: View the errors recorded by the Substation ES programs in the CICS region with the SXTH transaction. If the problem persists or you cannot resolve it, contact TIBCO Support.
`3810` | RR_NO_SS_AVAIL The CICS-initiated request or reply facility has found no active Substation regions in which to process the user application’s request.
User Response: Start a Substation ES region that connects to the CICS region that is attempting to send the request. If the problem persists, contact TIBCO Support. Before reporting the error, see Prereporting Steps.
`3816` | RR_NOT_SENT Program SXCREPLY could not post the Substation ES interface that an RR event has occurred.
User Response: Check that Substation ES is connected properly to CICS and is working correctly. Correct the situation and re-try. System Action: The request is not processed. The user application must reschedule or retry the request.
`3902` | ERR_LOGGED The CICS initiated request or reply facility cannot process the request because of an internal or CICS function error. The error has been logged to the Substation ES CICS error queue SXQE or SXQR.
User Response: View the errors recorded by the Substation ES programs in the CICS region with the `SXTH` or `XTUV` transaction. If too many errors are on the error queue, purge all the error entries with `SXTH` or `XTUV` and rerun the application. If the problem persists or you cannot resolve it, contact TIBCO Support with the information on the error, including the details recorded in the error queue.
`3903` | UNABLE_TO_SET_ENV A module of the Substation ES CICS Interface cannot establish its environment. Following are the possible causes: A system storage address could not be obtained. No communications area was passed. The communications area passed to the module has an incorrect length. Browse the CICS error queue with the SXTH transaction or view the Substation ES log for additional information on the error condition.
User Response: If the problem persists or you cannot resolve it, contact TIBCO Support with the information on the error from the log and trace files.
`3904` | INV_OPTION A parameter or value supplied to the program or resource in question is specified incorrectly.
User Response: Ensure that the parameters supplied to the called or linked program are valid. If the problem persists or you cannot resolve it, contact TIBCO Support with the related information on the error, including the pertinent details recorded in the error queue and the log and trace files.
`3905` | USER_LEN_INVALID During the invocation of the CICS request or reply facility, the data length supplied by the user application was found to be invalid. The valid data lengths are as follows: Zero (0) Larger than 32, 000 bytes Greater than the length of `DFHCOMMAREA` received by the requestor at runtime.
User Response: Correct the value of the data length that is passed to the requestor program by the user application.
`3908` | USER_DATA_TRUNC Program output data size is greater than the maximum set in the recipe.
User Response: Ensure that the program calling Substation ES programs is correctly providing the parameters in CommArea or Container or the Recipe. Correct the situation and retry. System Action: The request is processed with the user data truncated to the smaller size.
`3911` | `REASON_USER_DATA_EXCEEDED` The program has generated response objects that in total are larger than the maximum specified in the Recipe.
User Response: Check if the "max output" in the recipe is too small or why the program is generating more data than expected. System Action: The transaction is failed and an error message is generated in Substation ES and returned to the message "replyTo".
`3913` | TASK_NOT_4_SSQ The Substation ES CICS event post program has been invoked from a TDQ but the TDQ name is not that of the one defined or registered in the Substation CICS SIP members. The event post program terminates without further processing.
User Response: Ensure that you are writing to a queue name specified in the CICS interface parameters: QNAME-TGDQ for guaranteed or QNAME-TRDQ for reliable. Defaults exist for those queue names and you need not specify the parameters. In addition, depending on the service level you desire, set TRIG-GDQ, TRIG-RDQ, or both parameters, to Y. If the problem persists or you cannot resolve it, contact TIBCO Support with the related information on the error, including the pertinent details recorded in the error queue and the log and trace files.
`3914` | REASON_INV_USAGE_OPTION The Substation ES CICS High Volume Trigger (HVT) has been called to write a message. The selected TDQ type (`R` for reliable, `G` for guaranteed, or `O` for ordered) has not been activated in the Substation CICS interface, hence this service is not available.
User Response: Change the calling program to use a different service or activate the required trigger service type in Substation ES. System Action: The request is ignored; an error message is generated and sent to Substation ES; and a reason code is returned to the caller. No message is created.
`3920` | TRAN_START_INVALID The Substation ES CICS program has been invoked through a transaction, which was started with an incorrect method. The transaction could have been entered at a terminal or invoked from another program, but certain Substation ES CICS tasks cannot be started from a terminal or by application programs.
User Response: If the problem persists or you cannot resolve it, contact TIBCO Support with the related information on the error, including the pertinent details recorded in the error queue and the log and trace files.
`3926` | REASON_INTF_NOT_ACTIVE
Description: The RED Interface main control record or the CICS control record could not be found or has been deleted. User Response: Confirm that the SXXOSTRT program has been executed at system startup. Has SXXOSTRT been defined to the CICS PLT? System Action: The SXCOREDA returns to Substation ES without updating the necessary control blocks. The system will not function correctly until this issue has been resolved.
`3928` | REASON_INTF_MAX_EXCEEDED
Description: The CICS system supports only 8 Substation ES interfaces. You are trying to define more than the maximum allowed amount. User Response: Use the "XTUV,RED" CICS command to see number of interfaces already defined to the system. System Action: The interface being added will be rejected by the system administration program.
`3930` | TRG_TDQNAME_NOT_EQUAL If multiple Substation ES CICS Interfaces connect and use the same CICS region, they must have and use or share the same trigger TDQs.
User Response: Ensure that the trigger TDQ name for all Substation ES CICS interfaces that connect to the same CICS region is the same.
`3931` | TRGMIR_TDQNAME_NOT_EQUAL If multiple Substation ES CICS Interfaces connect and use the same CICS region, they must have and use or share the same Request or Reply TDQs.
User Response: Ensure that the Request or Reply TDQ name for all Substation ES CICS interfaces that connect to the same CICS region is the same.
`3940` | REASON_REC_VALUES_NOT_EQUAL If multiple Substation ES RED interfaces connect and use the same CICS region, they must have and use the same RED CICS recipe service listener name.
Description: If multiple Substation ES RED interfaces connect and use the same CICS region, they must have and use the same RED CICS recipe service listener name. It can also be that a previous interface definition already defined a value and a secondary interface definition is different and in this case the secondary interface's value will be ignored. User Response: Ensure that the CICS-LSN-NAME parameter or the parameter's value mentioned in the message specifies the same name/value as the first interface's definition that was registered to this CICS region.
`3977` | REASON_SERVICE_SUSPENDED
Description: The trigger service is suspended or disabled and this could be due to the ESB transport is disconnected or disabled. User Response: Enable the service and also determine why the service has been suspended. System Action: The message is not processed.
`3978` | REASON_SERVICE_INACT
Description: The trigger service that needs to process the request is inactive and not available. User Response: Enable the trigger service and determine why the service is inactive. System Action: The message is not processed.
`3979` | REASON_SERVICE_NOT_FOUND The business application has called SXXOTRED with a `G` (guaranteed) attribute, and SXXOTRED sent the message to Substation ES. Substation ES has looked up the Service ID provided by the business program and could not find an active trigger definition with the Service ID.
User Response: Determine why the Service ID provided does not match an active Substation ES Trigger Service ID. Note that Service ID is case sensitive and that the service (trigger) must be active. Correct the business application or Substation ES trigger definition and retry. System Action: The request is ignored.
`7900` | REASON_RED_SEND_FAIL The RED send operation has returned a non-zero return code.
User Response: Determine why the RED Send operation failed, and the additional information is returned in "RESP" and "RESP2" which are the RED return code and reason code. System Action: The request is ignored.
`7901` | REASON_RED_NO_AVAIL_WORKERS When using SXXOTRED to send a Trigger Message, SXXOTRED found that there were no paths available to send the message on.
User Response: Use the RED CICS control information viewer XTUV,TRG command to check for errors on RED paths to Substation ES. If errors occur, check why the paths are not working. System Action: Error message is generated to Substation ES and returned to CICS calling program, and the operation is ignored.
`7920` | REASON_RED_SERVICE_FAIL The business application has called SXXOTRED with a `G` (guaranteed) attribute, and SXXOTRED sent the message to Substation ES. Substation ES has looked up the Service ID provided by the business program and could not find an active trigger definition with the Service ID. Most likely cases are * ESB interface is inactive *. The name is incorrectly provided or not defined.
User Response: Determine why the Service ID failed execution. Note that Service ID is case sensitive and that the service (trigger) must be active. System Action: The request is not executed.
`7944` | REASON_RED_MSG_NOT_DELIVERED
User Response: Determine why the RED Send operation failed, and the additional information is returned in "RESP" and "RESP2" which are the RED return code and reason code. System Action: The request is ignored.
`7950` | REASON_RED_INV_HEADER_SIZE The header information passed between Substation ES and CICS SXCO#RED, and SXXOTRED is invalid.
User Action: Check that CICS and Substation ES are running on the same software library versions. If the versions are both correct, gather up CICS and Substation ES JES Output and contact TIBCO Support. System Action: The request is ignored.
`44190` | RSN_FAIL_BES_TIMEOUT
Description: The back-end system interface waited for a response from the ESB or TCP interface to complete a delivery and the timed event exceeded its interval. User Response: Refer to the log file to determine the cause of the issue. If there is no information located here, issue the SHOW,UOW operational command and see if there are any active UOW entries. Also look at the ESB connections and ESB server/daemons if there are any messages that can relate to this issue. System Action: The message from a Substation perspective is not processed correctly. If it's a guaranteed message than the BES will be rolled back to its original state. This could happen to both service types, a trigger or request/reply.

Copyright © TIBCO Software Inc. All rights reserved.