|
|
|
|
|
|
|
|
User Response: Check with the business program support group as to why the business program terminated abnormally.
|
|
|
|
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.
|
|
|
|
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:
|
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.
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.
|
|
|
|
|
|
User Response: Make sure program SXCOSTRT was run correctly. This program usually is executed using a PLT at CICS startup. Message SXC3700I should appear in the CICS jeslog.
|
|
|
|
|
|
User Response: No more Substation ES instances can connect to this CICS region.
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
|
|
User Response: View the errors recorded by Substation ES programs in the CICS region with the SXTH transaction. Subsequently, delete old error-queue records.
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
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:
|
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.
|
|
|
|
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:
|
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.
|
|
|
|
|
|
|
|
|
|
|
User Response: When the CICS region becomes available, reconnect the Substation ES interface to the CICS region with the operator command.
|
|
|
|
|
|
System Action: Substation ES returns the response with an error statu.
|
|
|
|
|
|
User Response: Determine if shorts 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.
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
User Response: Contact TIBCO Support with the information on the error from the log and trace files.
|
|
|
|
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.
|
|
|
|
|
|
User Response: Contact TIBCO support.
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
User Response: Contact TIBCO Support with the information on the error from the log and trace files.
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
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 may 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.
|
|
|
|
|
|
User Response: Look at the CICS JESLOG and MSGUSR for reasons why the WTO failed. For example, check for security issues.
|
System Action: : If 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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
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 need to define a transaction class to limit the number of active tasks that invoke the request or reply facility.
|
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.
|
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 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.
|
|
|
|
|
|
|
User Response: View the errors recorded by the Substation ES programs in the CICS region with the SXTH transaction.
|
|
|
|
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.
|
User Response: If you cannot decipher the envelope field or the problem persists, contact TIBCO Support. Before reporting the error, see Prereporting Steps.
|
|
|
|
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 due to 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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
User Response: Start a Substation ES region that connects to the CICS region that is attempting to send the request.
|
|
|
|
|
|
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.
|
|
|
|
|
|
User Response: View the errors recorded by the Substation ES programs in the CICS region with the SXTH transaction. If too many errors are on the error queue, purge all the error entries with SXTH and rerun the application.
|
|
|
|
Browse the CICS error queue with the SXTH transaction or the 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.
|
|
|
|
|
|
User Response: Ensure that the parameters supplied to the called or linked program is 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.
|
|
|
|
|
|
User Response: Correct the value of the data length that is passed to the requestor program by the user application.
|
|
|
|
|
|
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 re-try.
|
System Action: The request is processed with the user data truncated to the smaller size.
|
|
|
|
|
|
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.
|
|
|
|
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 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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
User Response: Ensure that the trigger TDQ name for all Substation ES CICS interfaces that connect to the same CICS region are the same.
|
|
|
|
|
|
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 a active trigger definition with the Service ID.
|
User Response: Determine why the Service ID provided does not match an active Susbstation 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.
|
