Codes and Descriptions

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.

Either the DFHCOMMAREA pointer cannot be obtained or the User Area length is invalid.

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

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.

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.

The maximum number of five (5) connections to a single CICS region has been exceeded.

The RED for CICS server program SXCOREDA failed to initialize the system correctly.

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.

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.

An inquiry of a program name specified either on an input parameter or on a queue resource definition has failed.

Error Returned from SXCOINQ.

The CICS Substation ES module SXCOINQ returned an error status to the business application program and ignored the Inquiry request.

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.

The call to a CICS region or a resource within the CICS region making a CICS API call has failed.

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.

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.

Refer to the error message SXC3124E.

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.

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.

A request to obtain storage from a Substation ES CICS program has failed.

An attempt was made to issue a WTO (message to the operator console, syslog) and it failed.

A request from a Substation ES CICS program to read a TSQ has failed.

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.

If you cannot determine the cause of the problem, contact TIBCO Support with the information on the error from the log and trace files.

A request from a Substation ES CICS program to write a TSQ has failed.

A request from a Substation ES CICS program to rewrite a TSQ record has failed.

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.

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.

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.

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.

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.

A request from a Substation CICS program to read a TDQ has failed.

A request from a Substation ES CICS program to write a TDQ has failed.

A request from a Substation ES CICS program to inquire about a TDQ definition has failed.

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.

the situation. Rerun the business program.

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.

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.

Cannot Create Response Container.

The CICS Substation ES module SXCQWRIT or SXCQWTSQ returned the error status when attempting to write back the parameter container.

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 is a length of zero and correct the situation. Rerun the business program.

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.

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.

A request from a Substation ES CICS program to wait on an MVS type ECB has failed.

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.

System Action: CICS processing continues.

Substation ES in CICS attempted to issue a Write-To-Operator (WTO) message, which failed.

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.

A request from a Substation ES CICS program to delay processing for a period of time has failed.

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.

A request from a Substation ES CICS program to obtain the EIB or DFHCOMMAREA address has failed.

A call to SXCOSRVM (Substation ES 3270 support in CICS) did not have the correct version number in the input data.

System Action: The request is not processed. The user application must reschedule or retry the request.

A request from a Substation ES CICS program to start a CICS transaction failed.

A request from a Substation ES CICS program to link to another CICS program has failed.

A request from a Substation ES CICS program to transfer control to another CICS program has failed.

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.

A call to SXCQWRIT (Substation ES HVT program in CICS) asking to use an service (R for reliable, G for guaranteed, O for ordered). The Substation ES interfacing with the CICS is not providing the service.

System Action: The request is not processed. The user application must reschedule or retry the request.

Program attempted a PUT Container and CICS returned an error response.

System Action: The request is not processed. The user application must reschedule or retry the request.

Program attempted a GET Container and CICS returned an error response.

System Action: The request is not processed. The user application must reschedule or retry the request.

Program attempted a DELETE Container and CICS returned an error response.

System Action: The request is not processed. The user application must reschedule or retry the request.

Program attempted a START BROWSE Container and CICS returned an error response.

System Action: The request is not processed. The user application must reschedule or retry the request.

Program attempted an END BROWSE Container and CICS returned an error response.

System Action: The request is not processed. The user application must reschedule or retry the request.

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.

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.

• 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.

If the problem persists or you cannot resolve it, contact TIBCO Support with the information on the error from the log and trace files.

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.

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.

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.

The CICS-initiated request or reply facility has found no active Substation regions in which to process the user application’s request.

If the problem persists, contact TIBCO Support. Before reporting the error, see Prereporting Steps.

Program SXCREPLY could not post the Substation ES interface that a RR event has occurred.

System Action: The request is not processed. The user application must reschedule or retry the request.

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.

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.

Browse the CICS error queue with the SXTH transaction or the view the Substation ES log for additional information on the error condition.

A parameter or value supplied to the program or resource in question is specified incorrectly.

Program output data size is greater than the maximum set in the recipe.

System Action: The request is processed with the user data truncated to the smaller size.

The program has generated response objects that in total are larger than the maximum specified in the Recipe.

System Action: The transaction is failed and an error message is generated in Substation ES and returned to the message "replyTo".

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.

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.

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.

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.

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.

If multiple Substation ES CICS Interfaces connect and use the same CICS region, they must have and use or share the same trigger TDQs.

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 are the same.

The business application has called SXXTRED with a G (guaranteed) attribute, and SXXTRED 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.

System Action: The request is ignored.

The RED send operation has returned a non-zero return code.

System Action: The request is ignored.

When using SXCOTRED to send a Trigger Message, SXCOTRED found that there were no paths available to send the message on.

System Action: Error message is generated to Substation ES and returned to CICS calling program, and the operation is ignored.

The business application has called SXXTRED with a G (guaranteed) attribute, and SXXTRED 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.

System Action: The request is not executed.

System Action: The request is ignored.

The header information passed between Substation ES and CICS SXCO#RED, and SXCOTRED is invalid.

System Action: The request is ignored.