CICS Interface Messages Description

Destination: TIBLOG and SYSLOG.

Destination: TIBLOG and SYSLOG.

User Response: Refer to the preceding messages for clues.

System Action: No interaction with the associated CICS interface is possible. All messages and transactions destined for this CICS interface fail.

Destination: TIBLOG and SYSLOG.

User Response: To reconnect to the CICS region, either specify the connect- operator command or recycle Substation ES.

System Action: Communication between Substation ES and the specified CICS region is no longer possible.

Destination: TIBLOG and SYSLOG.

Destination: TIBLOG and SYSLOG.

User Response: Ensure that the correct parameter, such as the application ID or interface ID, is in the connect-operator command.

User Response: When the CICS region is activated, you must reconnect Substation ES to the CICS region. Do so by either starting or restarting the interface connection or by recycling the Substation ES region.

User Response: Review other informational, error, and warning messages in the log to identify the cause of this condition. If you cannot resolve the issue, contact TIBCO Support with the information on the error from the log and trace files.

System Action: Processing continues.

User Response: Connect to the CICS region with the operator command as soon as CICS becomes available again.

System Action: Communication between Substation ES and the specified CICS region is no longer possible. All messages intended for the CICS region are rejected and returned with a status message to request or reply to applications.

User Response: Start the associated CICS region and reissue the Substation command if it doesn't connect automatically.

User Response: Check for messages in the DMQ and process them. They contain the same information that had been inserted into the trigger queue.

It might also occur when the EMS server unexpectedly goes down. The type provides an indication of the trigger type such as reliable, guaranteed or ordered.

User Response: Check for messages in CICS using the SXTH,ALL command and process them. These entries will contain the same information as when they were initially received by Substation.

User Response: Refer to any other messages in the Substation ES log file that might help determine why the message was sent to the Retransmit Queue or DMQ. Afterwards, look up the EXCI return code to determine why the message could not be placed on the Retransmit Queue or DMQ. Check the CICS BES log for other error messages that are associated with the Substation ES EXCI interface at the same time.

System Action: Substation ES frees up the reliable messages, which are lost. Guaranteed messages roll back the transaction, with the messages remaining in the original queue.

User Response: Determine why the initial message segment was lost. Check the CICS BES and Substation ES log for TDQ- or EXCI-related error messages that would cause a segment loss.

System Action: Substation ES frees up the message segment and all the other related segments. The HVT message associated with the segment is lost.

User Response: Refer to any other messages in the Substation ES log file that might help determine the problem. You might have to cancel Substation ES to shut it down. Report this issue to TIBCO Support with the entire Substation ES job output.

System Action: Processing might continue or go into an idle state. You might have to cancel the job or task.

User Response: Determine why CICS region Applid did not have adequate space. Delete records from TDQ or recycle CICS with a bigger DFHINTRA file.

System Action: Substation ES terminates interface Intf-Id to CICS Applid.The CICS interface will not be available until a reconnect command is issued subsequent to the TDQ “no space” condition.

User Response: Determine why CICS region Applid did not have adequate auxiliary space. Delete records from TSQ or recycle CICS with a bigger DFHTEMP file.

System Action: Substation ES reports the condition and continues to extract messages.

Destination: TIBLOG, TIBTRACE and SYSLOG.

User Response: Determine why the CICS region Applid did not have adequate space. Delete records from TDQ or recycle CICS with a bigger DFHINTRA file.

System Action: Substation ES reports the condition and continues to extract messages.

Destination: TIBLOG, TIBTRACE and SYSLOG.

User Response: Determine if any error has been reported in the log relating to this transaction. What might have happened is that validation had failed in the ESB interface and the coordination back to trigger thread was never sent. The CICS resource awaiting response is taken care of. Report the issue to TIBCO Support with the information from the Substation ES logs.

System Action: The message is added to the DMQ (dead Message Queue) and processing continues.

Destination: TIBLOG, TIBTRACE.

User Response: Determine if any other warnings or errors have been reported in the log related to this transaction. The ESB might have gone down, or a disconnect could have occurred. This error is expected if these conditions occurred.

If the condition persists and you are not able to determine the cause, report the issue to TIBCO Support with the information from the Substation ES log and trace files.

System Action: The message processing has not completed successfully and resources are not committed, but processing continues.

Destination: TIBLOG, TIBTRACE.

User Response: You can increase this value to 250 (maximum allowed by IBM).

User Response: Determine if any errors in the CICS runtime log file can help identify the issue. Report the issue to TIBCO Support with the information from the Substation ES logs.

System Action: Processing continues.

User Response: Review message SXC3072 in TIBLPARM regarding the maximum number of sessions and increase that limit if required or if possible. Contact a Substation ES field representative or TIBCO Support if necessary.

System Action: Substation ES prevents new sessions to start from this region. The existing interfaces and sessions that have been established will operate normally

User Response: Choose the appropriate connection for your installation. In nearly all cases, a SPECIFIC connection is sufficient.

User Response: Specify the interface ID that corresponds to an ESB interface defined in the Substation ES region. For the valid interface IDs currently in your Substation ES region, run the operational command SHOW,INTF.

System Action: The system does not start SXCOSRVA in the CICS region and cannot extract trigger messages.

Description

RC:RC RSN:RSN

Note: If Description contains an Inter-Region Communication (IRC) code, see the following User Response.

If Description contains "No more pipes available" then the RECEIVECount value defined on CICS session resource definition for the connection of the Netname specified is too low. You have more workers (sessions) defined than there are sessions available. The value of the RECEIVECount should nearly always be greater than 50% more than the worker threads you have defined. Note that this applies to all interfaces going to the same CICS region.

At times message SXC3191E is issued to assist with the reason when EXCI error values are received.

User Response: Determine the resource and interface that caused the error. For details on RSN, see CICS External Interfaces Guide. The following values (Description) are most likely returned to Substation ES by the CICS IRC access method:

• CICS IRC Code:4 X’4’ – Invalid Function Requested. The CICS interface cannot contact the requested CICS region because a valid EXCI Options Module (DFHXCOPT), required by EXCI during initialization with a CICS region, failed to load and execute.
• CICS IRC Code:36 X'24' – Set footprint has failed, which is normally a Substation ES internal error. Substation ES attempted to connect to CICS with an invalid pipe or user token and the call failed. For a quick resolution, issue an explicit disconnect and reconnect to the CICS region with the issue or recycle the Substation ES server. Report this issue to TIBCO Support with the entire Substation ES job output.
• CICS IRC Code:92 X’5c’ – Either the requested CICS region is not available or APPLID defined in the Substation ES CICS Interface parameters is incorrect.
• CICS IRC Code:104 X’68’ – The CICS resource as defined in the message’s resource field does not exist. Either the resource, a node name, is defined incorrectly in the Substation ES CICS Interface parameters or the CICS resource definitions have not been added to the CICS System Definition (CSD) file. Ensure that you have defined the Substation ES list TIBLIST for the CICS GRPLIST startup parameter. Review the MSGUSER data set in the CICS startup and ensure that GROUP TIBCO has been installed.
• CICS IRC Code:124 X'7c' – Primary is in-quiesce. This means CICS is coming down.
• CICS IRC Code:172 X'ac' – The requested CICS connection link is broken or the region is currently not available.

• CICS IRC Code: 414

  SXC3101E CICS EXCI Call Error, TRAN:SXEX, NetName:SXCSSTRG,
  DFHAC2206 time CICSAPPL Transaction trans-id failed with
  abend AITD. Updates to local recoverable resources
  backed out.
  RC:8 RSN:3101
  ID3: 0006 12 414 IICICSX2 SXCOSRVG

This situation is likely caused by the DTIMEOUT happening on the EXCI, because the DTIMEOUT is less than the retry time for the ESB.

RC RSN

ID3: Call type Intf-Id resource

RC is a number that corresponds to the CICS RESP condition that occurred. To determine the error condition, see the EIBRESP values in CICS Application Programming Reference.

User Response: Determine the error by referring to the CICS RESP values. Correct the error and restart the publishing application or trigger process that caused the DPL error.

User Response: Determine if the information is relevant especially when the data length of the user is larger than the CICS CA area.

Resource:server RC:RC SS-Rsn:RSN

ID3: eibfn RC RSN Intf-Id resource

User Response: If this message is displayed with issuing in error and all connections are up , you have to find the reason for this. If this situation persists, contact TIBCO Support with the information on the error from the log and trace files.

System Action: Substation ES continues execution with no delays or side effects.

User Response: Determine which resource and interface caused the error. For details on CIR2, see CICS External Interfaces Guide. The following values (Description) are most likely returned to Substation ES by the CICS IRC access method:

• CICS IRC Code:124 X'7c' - Primary is in-quiesce. This means CICS is coming down.
• CICS IRC Code:172 X'ac' – The requested CICS connection link is broken or the region is currently not available.

System Action: Substation ES continues execution with no delays or side effects.

User Response: Remove the last Substation CICS interface that was added to your configuration. Recycle your CICS region and Substation ES.

System Action: Substation ES issues numerous messages and operates incorrectly

User Response: The message text is self-explanatory. Contact TIBCO Support with the information on the error from the log and trace files.

System Action: Substation ES continues execution with no delays or side effects.

User Response: Check the message at the error destination, which is specified in the definition of the recipe or trigger service recipe.

System Action: Substation continues execution since this error is most likely an application error.

User Response: Ensure that the value of the keyword RR-MAXSIZE is equal to or greater than the maximum outbound data size.

System Action: Substation ES continues execution since this error is most likely an application error or configuration error.

User Response: Reduce the size of the data items configured in the definition of the Substation ES recipe, refresh the recipe, and resubmit the request. Alternatively, increase the size of the IOAREA in the definition of the CICS resource parameter for Substation ES. The default session name for DPL type requests is SXCOSD01.

System Action: Substation ES continues processing all other requests.

Timestamp:CCYY/MM/DD - HH:MM:SS:TTT

Resource:name RC:RC RSN:RSN

ID3: eibfn RC Rsn_Code Intf-Id resource

RC is a number that corresponds to the CICS RESP condition that occurred. To determine the error condition, see the EIBRESP values in CICS Application Programming Reference.

User Response: Determine the error by referring to the CICS RESP values and the resource that might have caused the error condition.

System Action: Substation ES continues execution since this error is most likely an application error or configuration error.

User Response: Determine the error by referring to other messages in the log or trace files that might have caused the error condition.

System Action: Substation ES continues execution since this error is most likely an application error or configuration error.

User Response: Refer to the CICS reasons for the value and the previous mentioned description and take the appropriate action.

System Action: None for this message.

User Response: Usually, no action is required. If this message is followed by error messages, browse them to determine the reason for the disconnect command from CICS.

User Response: Usually, no action is required. If this message is followed by error messages, browse them to determine the reason for the disconnect command issued from CICS.

User Response: If this is an expected message because of a shutdown or an interface disconnect, no action is required. Otherwise, contact TIBCO Support with the information on the error from the log and trace files.

System Action: Communication between Substation ES and the CICS region Applid is no longer possible.

User Response: Determine the cause by reviewing the related return and reason codes. Fix the error and restart the program or task that failed. If the condition persists, contact TIBCO Support.

User Response: Determine the cause by reviewing the related return and reason codes associated. Fix the error and restart the program or task that failed. If the condition persists, contact TIBCO Support.

User Response: Check the CICS logs or, if the condition persists, determine the error through CEDF.

System Action: The program in use is terminated.

User Response: If RRS is required but is not running, notify your systems or operational department.

User Response: Review the error condition along with other messages in the log. Contact TIBCO Support with the information on the error from the log and trace files.

Destination: JES message log file and SDSF SYSLOG.

Destination: JES message log file and SDSF SYSLOG.

Destination: TIBLOG, TIBTRACE.

User Response: Find out which TDQs might contain records. For a list of the Substation ES records, run the online utility SXTH,ALL. The errors that pertain to this condition are most likely in the Substation log. Attempt to resolve them. We strongly suggest that you shut down CICS at some quiet point and increase the DFHINTRA file size.

System Action: Substation ES attempts to continue processing but might shut down the connection to that CICS region. Contact TIBCO Support.

User Response: Determine if error messages are in the CICS runtime log file and, if so, whether they help identify the issue. Contact TIBCO Support.

System Action: Processing continues.

User Response: Restart CICS in which DFHINTRA has a record length greater than 319.

System Action: The SXCOSTRT program cannot complete its initialization. This CICS region cannot communicate with any Substation ES instance.

User Response: See the CICS logs for a possible explanation or other related messages. If you cannot resolve the issue, contact TIBCO Support with the information on the error from the log and trace files.

System Action: Substation ES operations for this specific CICS region fail to work.

User Response: Refer to the CICS documentation to determine the cause of the error, and then correct and re-run the transaction.

System Action: Processing continues.

User Response: Refer to the CICS documentation to determine the cause of the warning. If required, correct and re-run the transaction.

System Action: Processing continues.

User Response: See the preceding messages to determine why initialization failed. Correct the problem and restart CICS.

System Action: The SXCOSTRT program has not completed initializing its storage in the CICS region, which is not ready to communicate with any Substation ES instance.

This is an information message and is only displayed when the TRCLVL-HVS has been set to 3. A value of 3 is a good choice for testing.

User Response: Usually, no action is required.

Destination: TIBLOG and TIBTRC.

This is an information message and is only displayed when the TRCLVL-HVS has been set to 1 or higher.

User Response: No action is required.

Destination: TIBLOG and TIBTRC.

User Response: See the preceding messages on the log in CICS to determine why the queues are reaching their threshold. Correct the problem and restart Substation ES.

System Action: The SXCOEVPA program is executed by way of Transaction SXPA.

Destination: Substation log and trace and operator's console.

User Response: Ensure you have the correct version of the Substation supplied load library concatenated in your DFHRPL DDName.

System Action: The CICS online system will not function without resolving this error.

Destination: TIBLOG, TIBTRC and SYSLOG (Console).

User Response: Type HELP or ? for a display of the valid parameters.

System Action: The program in use terminates.

User Response: If the condition persists, browse the CICS logs or identify the error with CEDF.

System Action: The program terminates with the appropriate return code.

Loading the token is essential in getting the Substation run-time values that were loaded at CICS startup by PLT program SXCOSTRT.

The most likely cause for this condition is that the PLT program did not execute successfully at CICS start-up or somehow the storage area related to this token was deleted.

User Response: If the problem cannot be identified, contact TIBCO support with the information from this message and any other irregular CICS activities during this time period.

System Action: Substation cannot function without locating and loading the content based on this token. Substation will not connect and server programs executing in the CICS region will not complete successfully.

User Response: Contact TIBCO Support.

System Action: The transaction terminates.

User Response: If the condition persists, browse the CICS logs or identify the error with CEDF.

System Action: The program terminates.