General Messages

The following table describes the general messages.

For the invalid keywords or values specified, refer to TIBCO Substation ES Installation for a list of console commands.

Code	Description
`SXG1010E`	Substation ES error occurred during initialization Date:`ccyymmdd` Time:`hhmmsshh` Function:`function` Line:`lineno` `ERROR CODE`:`RC` `REASON`:`RSN` `Progname` - `Msg-Id` - `Description`
`SXG1010E`	Explanation: An invalid parameter has been specified that has caused the Substation ES initialization routines to fail. The message is routed to the `SYSPRINT` DD Name, as the LTA Agents have not yet been started. User Response: Refer to `Msg-Id` and `Description` in the message for help in determining the problem. System Action: Refer to `Msg-Id` and `Description` in the message for help in determining the problem. Destination: `SYSPRINT`.
`SXG1011E`	Additional Important error information `Pgm`:`Progname` `Error Msg`:`Msg-Id` `Description`
`SXG1011E`	Explanation: This message is written when an agent of Substation ES has been started and can not be initialized successfully. This message is a supplement to message SXS1010E supplying additional information of the Agent error condition. User Response: Refer to `Msg-Id` and `Description` in the message for help in determining the problem. System Action: Substation ES is terminated. Destination: `SYSPRINT` and log file.
`SXG1012E`	Shutdown Error for Agent `Description`
`SXG1012E`	Explanation: While trying to close an LTA Agent file, an error was encountered. User Response: Contact TIBCO Support and report the error. Destination: Logs and trace files that are still available have the message written to it.
`SXG1021E`	Priority could not be set for IId: `Intf-Id`
`SXG1021E`	Explanation: An internal request to set an interface priority failed. User Response: Contact TIBCO Support and report the error.
`SXG1032C`	TIBCO Substation ES Library not APF Authorized
`SXG1032C`	Explanation: One or more of the libraries specified in the `STEPLIB DD Name` statement of the Substation ES startup procedure has been not APF authorized. User Response: Ensure all the libraries specified on the `STEPLIB` statement of the Substation ES startup procedure are APF authorized. System Action: Substation ES is terminated.
`SXG1117E`	RED UoW:`UoW` RC:`RC` Rsn:`RSN` RC:`RC2` Rsn:`RSN2`
`SXG1117E`	Explanation: This error is produced when a request process with `UoW` is sent to the RED interface, but the processes fails with a return code of `RC` and reason code `Rsn` from the RED interface. `RC2` and `RSN2` are return code and reason code from ESB interface. User Response: Refer to the RED messages and codes documentation for an explanation of the error condition. For `RSN2`, refer to the section Reason Codes for an explanation about the error condition. Contact TIBCO support if the condition persists. Provide the Substation ES job log details to help identify the error encountered. System Action: The interface attempts to continue processing after the error condition has occurred. Destination: Service request error message and `TIBTRC`.
`SXG1129E`	Maximum number of `Number` interfaces exceeded
`SXG1129E`	Explanation: The administrator has defined more than the allowable number of Interfaces per Substation ES. User Response: Remove the Interfaces to cater for allowable `Number` of Interfaces. Split Interfaces between Substation ES instances. System Action: Substation ES terminates abnormally.
`SXG1135W`	Task has already Enqueued Resource: `value`
`SXG1135W`	Explanation: The value specified on the message is the result of a resource that has already been Enqueued. User Response: Contact TIBCO Support and report the error. System Action: Substation ES tries to recover normally.
`SXG1149I`	Shutdown Completed - Routine: `PGM`
`SXG1149I`	Explanation: Substation ES reports that a subtask program has completed its shutdown process successfully. This message is normally followed by message `SXG2805I` identifying the interface.
`SXG1400I`	starting Thd Id: `thread-id` Type: `type` IId: `Intf-Id` Evt: `event_addr`
`SXG1400I`	Explanation: Substation ES reports that a thread is being started for `Intf-Id`. Additional information is supplied for reference purposes only.
`SXG1402E`	Thread (`Name`) Event allocation failed
`SXG1402E`	Explanation: Substation ES could not allocate a requested thread's event control block (ECB). The `Name` of the thread has been identified. User Response: Try restarting Substation ES. Contact TIBCO Support to report the error. Supply the information on the error from the log and trace files. System Action: The thread that can be critical to Substation ES, does not start.
`SXG1405I`	Posting generic Thread(s) - Thd@: `address` Type: `type` Event@:`event_addr` Cond: `event_cond`
`SXG1405I`	Explanation: Substation ES or one of its Interfaces is posting events to a group of threads identified by `type`. The event condition that is received by this post is identified by `event_cond`. Other event and thread information is also recorded.
`SXG1406E`	Thread (`Name`) Allocation failed
`SXG1406E`	Explanation: Substation ES could not allocate a requested thread of `Name`. User Response: Try restarting Substation ES. Contact TIBCO Support with the information on the error from the log and trace files. System Action: The thread that can be critical to Substation ES does not start.
`SXG1407E`	Thread (Type:`Type`) Allocation failed
`SXG1407E`	Explanation: Substation ES could not allocate a requested thread of `Type.` User Response: Try restarting Substation ES. Contact TIBCO Support to report the error. Supply the information on the error from the log and trace files. System Action: The thread that can be critical to Substation ES does not start.
`SXG1410I`	Terminating Thd: `thread-id` Type:`type` TCB@:`address` IId: `Intf-Id` CPU Time:`cpu-total` Start: `cpu-start` End: `cpu-end`
`SXG1410I`	Explanation: A TIBCO Substation ES thread in an interface identified by `Intf-Id` is being terminated. A message is recorded with thread-specific information and CPU timings for this thread.
`SXG1414I`	Main Task reporting a thread is exiting
`SXG1414I`	Explanation: The Substation ES main task has detected that a thread or subtask has been terminated.
`SXG1416I`	Thread starting - Id: `Id-No` Type: `type`
`SXG1416I`	Explanation: A Substation ES subtask or thread has started. The `Id-No` and `type` are added for reference purposes.
`SXG1417I`	Thread terminating - Id: `Id-No` Type: `type`
`SXG1417I`	Explanation: A Substation ES subtask or thread has been terminated. The `Id-No` and `type` are added for reference purposes.
`SXG1419E`	`Description`
`SXG1419E`	Explanation: Substation ES received a `Description` of the error that occurred when trying to cancel a thread. User Response: Contact TIBCO Support to report the error. Supply the information on the error from the log and trace files. System Action: If the thread could not be cancelled repetitively, Substation ES can enter into a loop or infinite wait state.
`SXG1420E`	Thread (`Name`) Creation Error
`SXG1420E`	Explanation: Substation ES could not create a requested thread of `Name.` User Response: Contact TIBCO Support with the information on the error from the log and trace files. System Action: The thread that can be critical to Substation ES does not start.
`SXG1421E`	`Description`
`SXG1421E`	Explanation: Substation ES received `Description` of the error, which occurred during the creation of a thread. This message is normally preceded by message `SXG1420E`. User Response: Contact TIBCO Support to report the error. Supply the information on the error from the log and trace files. System Action: The thread that can be critical to Substation ES does not start.
`SXG1421W`	`Description`
`SXG1421W`	Explanation: Substation ES received `Description` of the error, which occurred when Substation ES was trying to obtain the stack size of a thread. User Response: Contact TIBCO Support to report the error. System Action: Processing continues normally.
`SXG1422E`	Thread Set Specific Error - `Description`
`SXG1422E`	Explanation: Substation ES received `Description` of the error, which occurred when Substation ES was trying to set specific attributes of a thread. User Response: Contact TIBCO Support to report the error. System Action: Processing continues normally.
`SXG1425E`	Master Ctrl Thread Never Started Up
`SXG1425E`	Explanation: The Substation ES master task never received a signal from its control thread that it was ready to start processing. User Response: Contact TIBCO Support with the information on the error from the log and trace files. System Action: Substation ES terminates abnormally.
`SXG1450E`	Thread attribute error. `text`
`SXG1450E`	Explanation: A `pthread_attr` call has failed. The error suggests a language environmental runtime error. User Response: This error condition is rare. Contact TIBCO Support with the information on the error from the log and trace files. System Action: System operations might still be able to proceed with no side effects.
`SXG1451E`	Thread control create error. `text`
`SXG1451E`	Explanation: A `pthread_attr` call has failed. The error suggests a language environmental runtime error. User Response: This error condition is rare. Contact TIBCO Support with the information on the error from the log and trace files. System Action: System operations might still be able to proceed with no side effects.
`SXG1491E`	Bad Thread address: `address`
`SXG1491E`	Explanation: Storage has most likely been overwritten and the software has detected an invalid thread address. User Response: Contact TIBCO Support with the information on the entire Substation JES2 job log. System Action: A dump has been taken. Operations might still be able to proceed but with throughput degradation.
`SXG1495F`	Thread ptr(s) bad or Max Thd count: `value`
`SXG1495F`	Explanation: Storage has most likely been overwritten along with the detection of an invalid thread address or counter that relates to the Substation ES internals. User Response: Contact TIBCO Support with the information on the entire Substation JES2 job log. System Action: A dump has been taken. Operations might still be able to proceed. This phenomenon usually occurs only at system shutdown time.
`SXG1600I`	Log Agent Starting - Logging to DD `Name`
`SXG1600I`	Explanation: The Log Agent has been initialized and started successfully. Log entries are being recorded to a data set referenced on the DD `Name` statement.
`SXG1601I`	Log Agent terminating & file closed
`SXG1601I`	Explanation: The Log Agent is about to be closed and the Logging Agent is terminated.
`SXG1610E`	Log Agent Error Review Error lines following
`SXG1610E`	Explanation: The Log Agent has detected an error condition. User Response: Review the additional error messages and reason codes to determine the cause of the Agent’s error condition. System Action: Substation ES terminates with `RC=16`.
`SXG1611C`	Logging Agent write Error, Cond: `Cond`
`SXG1611C`	Explanation: The target interface identified by `Intf-Id` is not active or available in the Substation ES active configuration. User Response: Ensure that the correct Substation ES interface ID has been specified or review the log file for error conditions that can have caused the interface to become unavailable. If this problem persists, contact TIBCO Support with the information on the error from the log and trace files. System Action: Substation ES does not process the request.
`SXG1700I`	Trace Agent Starting - Tracing to `DD Name`
`SXG1700I`	Explanation: The Trace Agent has been initialized and started. Trace entries are being recorded to a data set referenced on the `DD Name` statement.
`SXG1701I`	Trace Agent terminating
`SXG1701I`	Explanation: The Trace file is about to be closed and the Tracing Agent terminates.
`SXG1709W`	Tracing Agent under stress
`SXG1709W`	Explanation: The Tracing Agent is currently too busy to handle additional work. All tasks requesting data to be written to the trace file are slowed down until the stress condition has been relieved. Normally, this condition is caused by heavy usage on the disk or channel on which the disk is located. User Response: Determine the cause of the stress. Verify that Substation ES `TRC-LVL` is not set to higher than 3. If the problem still persists, contact TIBCO Support. System Action: When the stress condition is relieved, the system functions normally again.
`SXG1710E`	Trace Agent Error
`SXG1710E`	Explanation: The Trace Agent has detected an error condition. User Response: Review the additional error messages and reason codes to determine the cause of the Agent’s error condition. System Action: Substation ES terminates with RC=16.
`SXG1711C`	Trace Agent write Error - RC: `RC`
`SXG1711C`	Explanation: A write to the specified LTA agent has been unsuccessful. The RC determines the severity of the error. User Response: Review the message with reference to its environment, System Initialization Parameters (SIPs) and the operator command issued. Contact TIBCO Support with the information on the error from the log and trace files. System Action: This is a critical error in which the specified LTA agent can not be operational any longer. Substation ES attempts to operate without the specified LTA agent.
`SXG1800I`	Parameter Log Agent Starting - Logging to `DD Name`
`SXG1800I`	Explanation: The Parameter or Audit Agent has been initialized and started successfully. Entries are being recorded to a data set referenced on the `DD Name` statement.
`SXG1801I`	Parameter log closed
`SXG1801I`	Explanation: The Parameter or Audit file is about to be closed and the associated Agent is terminated.
`SXG1803I`	`Agent` destination changing to `medium`
`SXG1803I`	Explanation: An operator request has been issued directing Substation ES to change the `Agent's` recording `medium`. `Medium` can either be Print or Disk. System Action: If the request was successful, the output is recorded on the medium specified. Otherwise, no change occurs.
`SXG1805E`	Already initialized `Agent`
`SXG1805E`	Explanation: The LTA `Agent` is to be initialized, but already has been. User Response: Contact TIBCO Support to report the error. System Action: Substation ES must continue to operate normally.
`SXG1811E`	LTA Agent write Error, Cond: `Cond`
`SXG1811E`	Explanation: The LTA parameter Agent received an error whilst trying to write to its output medium. User Response: Contact TIBCO Support to report the error.
`SXG1813C`	LTA Agent unable to continue - `Agent`
`SXG1813C`	Explanation: One of the Substation ES LTA Agents named `Agent` has had a critical error and could not be restarted. Normally, Substation ES tries to restart `Agent` and switches the output medium. If all else fails, this message is displayed. User Response: Contact TIBCO Support with the information on the error from the log and trace files. System Action: Substation ES continues operating normally. However, it is advisable to restart Substation ES as soon as convenient. Destination: Medium that is available.
`SXG1815E`	LTA Admin call `Func` Failed with RC:`RC`
`SXG1815E`	Explanation: The administration command specified has failed to execute. The RC shown might not be very useful as it's a code returned on a program call. User Response: See if there are other messages in the Substation log files that might clarify the issue. If the problem persists, contact TIBCO Support with the information on the error from the log and trace files. System Action: Substation ES continues operating normally.
`SXG1821I`	LTA Version: `Description`
`SXG1821I`	Explanation: This message is displayed when an operator command, SHOW,LTAVERS is entered. This message shows the version number with the date and time of the LTA agent’s kernel.
`SXG1824I`	Force Write set to `nnn` (1/100) of a second for LTA Agent
`SXG1824I`	Explanation: This message is displayed if a LOGFWRITE or TRCGFWRITE operator command is issued to force a write interval for an Agent (Log or Trace). This is only valid if the output medium is a DASD. System Action: The LTA Agent’s buffers are flushed to disk every centi seconds (1/100 of a second).
`SXG1830I`	Logging to Syslog. Severity set to value
`SXG1830I`	Explanation: This message is displayed when the parameter LOG2-SYSLOG has been specified with any value other than the default. The default value will not send any Substation ES log messages to the MVS Syslog. Refer to the parameter LOG2-SYSLOG for the usage and valid value values.
`SXG1880I`	IId: `Intf-Id` U-Trc(T) - UoW: `UoW`
`SXG1880I`	Explanation: The Substation ES Interface’s trigger trace level has been set and the Substation ES Interface reported that a buffer has been received from the BES. User Response: This message is useful when tracing data that moves through Substation ES. `Uow` is referenced on all user trace messages and can be used to follow the trace of a user's message or data.
`SXG1885I`	IId: `Intf-Id` U-Trc(I) - UoW: `UoW`
`SXG1885I`	Explanation: Substation ES is reporting that input data has been received from the Transformer interface. The trace level of the recipe definition has been set and the input of the specific occurrence of the data is traced. If the trace level is set to 2, message `SXG1886I` is logged to the trace file, displaying the contents of the buffer. User Response: This message is useful for tracing data that moves through Substation ES. `Uow` is referenced on all user trace messages and can be used to follow the trace of a user’s message or data.
`SXG1887I`	IId: `Intf-Id` U-Trc(O) - UoW: `UoW`
`SXG1887I`	Explanation: Substation ES is reporting that output data has been received from the BES. Data previously sent to the BES would have been reported by message `SXG1885I`. The trace level of the recipe definition has been set and the output from a BES of the specific occurrence of the data is traced. If the trace level is set to 2, message SXG1888I is logged to the trace file, displaying the contents of the buffer. User Response: This message is useful for tracing data that moves through Substation ES. `Uow` is referenced on all user trace messages and can be used to follow the trace of a user’s message or data.
`SXG1889I`	IId:`Intf-Id` U-Trc(`Type`) UoW:`Uow` Service:`RID`
`SXG1889I`	Explanation: The message execution is one of the following two `Type` conditions: (`N`) a negative acknowledgment (NAK) was sent to IMS for this request. (`C`) the request been committed to IMS. User Response: This message is useful for tracing data that moves through Substation ES. UoW is referenced on all user trace messages and can be used to follow the trace of a message or data. `RID` is the service request that has reported condition.
`SXG2001E`	Address failed validation `info`
`SXG2001E`	Explanation: A memory address used internally by Substation ES failed validation. Information regarding the error is suffixed to the end of the message in field `info.` User Response: Contact TIBCO Support with the information on the error from the log and trace files. System Action: The system tries to recover from the error. If that attempt fails, a critical error follows and Substation ES can be terminated abnormally.
`SXG2001W`	Address valid but storage compare failed `info`
`SXG2001W`	Explanation: A memory address must point to a Substation ES internal control block that contains valid information, but failed validation when accessed. The information on the error is at the end of the message in field `info.` User Response: Contact TIBCO Support with the information on the error from the log and trace files. System Action: The system tries to recover from the error. If that attempt fails, a critical error follows and Substation ES can be terminated abnormally.
`SXG2005C`	* System Internal Error. Contact Customer Support
`SXG2005C`	Explanation: Substation ES has reported that a critical error has been detected. Substation ES messages that precede this message normally contain information on the error condition. User Response: Contact TIBCO Support with the information on the error from the log and trace files. System Action: Substation ES tries to shut down normally but usually terminates abnormally.
`SXG2006E`	Memory allocation request unsuccessful
`SXG2006E`	Explanation: Storage allocation has failed for a particular request. Substation ES could have exceeded its storage allocation requirements. User Response: Contact TIBCO Support with the information on the error from the log and trace files. System Action: Substation ES tries to shut down normally and, in most cases, it terminates as normally as possible.
`SXG2007E`	Invalid pointer - refer to object
`SXG2007E`	Explanation: The storage has most likely been overwritten and the software has detected that an invalid address has been supplied to the Substation ES internal processing routines. User Response: Contact TIBCO Support with the information on the entire Substation JES2 job log. System Action: The system reports the error and attempts to continue with the operations.
`SXG2008W`	IId: `Intf-Id` Terminating. Unable to process Cond: `Cond`
`SXG2008W`	Explanation: A Substation ES interface has failed to process a request with the condition `Cond.` User Response: Contact TIBCO Support to report the error.
`SXG2017E`	Invalid MOI detected, Value: `value`
`SXG2017E`	Explanation: An invalid Method of Invocation was detected by one of the Substation ES Interfaces. This condition could be because of an incorrect definition for the Unit of Work (UOW) or an incorrect update of the invocation method by a Substation ES internal process. User Response: Ensure that the recipe definition is correctly specified. If the problem persists, contact TIBCO Support. System Action: The message is not processed by a back-end system. An error response is generated for the user.
`SXG2018E`	Msg Length (`MsgLen`) GT than Max Length (`MaxLen`)
`SXG2018E`	Explanation: The input message length exceed the specified allowable maximum message length. User Response: Correct the message length or increase the RED interface maximum message length value. System Action: The message is not processed by a back-end system. An error response is generated for the user.
`SXG2020E`	Execution of request Failed, IId:`Intf-Id - Description`.
`SXG2020E`	Explanation: The Substation ES dispatcher could not send a request to an interface(s), signaling that a UoW was ready for processing. The possible reasons are mentioned in the description of the message. Either the interface that Substation was trying to reach could be not found, stopped, or might have been disconnected from the back-end (CICS or IMS), or the internal queues were not available for processing requests. Refer to the description for why the dispatching could not occur. User Response: Refer to the trace for additional information following the line at which this error was logged. 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 continues processing other requests normally. Substation sends the issuing user a response indicating that the transaction execution had failed.
`SXG2021E`	Dispatch of request Failed
`SXG2021E`	Explanation: The Substation ES UoW dispatcher could not post an interface, signaling that a UoW was ready for processing. The interface was not found, stopped, or could have been disconnected from the back-end, or the internal queues were not available for processing requests. Refer to the reason for why the dispatch could not take place. User Response: Refer to the trace for additional information following the line at which this error was logged. 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 continues processing other requests.
`SXG2021C`	* Dispatch of request Failed
`SXG2021C`	Explanation: A Substation ES Interface reported that a dispatch for a UoW has failed. Normally, other messages that precede this message determine the cause of the error that occurred. User Response: Contact TIBCO Support to report the error. Supply information about the error from the log and trace files. System Action: Substation ES continues processing other requests normally.
`SXG2022C`	* Max retries of Number exceeded - desc
`SXG2022C`	Explanation: A retry exceeded its limit in trying to lock or send an alert internally; desc describes the error and its condition. User Response: Contact TIBCO Support with the information on the error from the log and trace files. System Action: The system can still function normally and operations should not be affected.
`SXG2029C`	* Critical condition not catered for - `value`
`SXG2029C`	Explanation: Substation ES reported that an undetermined critical error has occurred and that it might have problems processing in an interface or agent related to this request. A description is suffixed to this message with more details on the error condition. User Response: Contact TIBCO Support, supplying information on the error from the log and trace files. System Action: Substation ES continues processing other requests.
`SXG2040I`	IId: `Intf-Id`, ESB state changed to `Description`
`SXG2040I`	Explanation: A Substation ES interface has detected that the ESB interface has changed its status. Other actions might follow this message depending on the state shown in the description. User Response: None. Processing continues. System Action: Substation ES continues processing normally unless this event occurs frequently.
`SXG2040E`	IId: `Intf-Id`, ESB state request failed
`SXG2040E`	Explanation: A Substation ES interface requested the latest state of an ESB but the request failed. User Response: If the condition persists, contact TIBCO Support with the information on the error from the log and trace files. System Action: Substation ES continues processing normally.
`SXG2044E`	Waiting on Event has failed. Reason:`RSN`
`SXG2044E`	Explanation: During the wait for an event to be posted, an abnormal condition was detected and shown as `RSN`. Normally, a timeout occurs if an event is not posted in time. Not posting in time can be because of resource contention or if the function that should post the event has had some processing error of its own. User Response: Contact TIBCO Support with the information on the error from the log and trace files. System Action: If `RSN` is not serious, Substation ES continues to process other requests.
`SXG2049W`	Field `field` truncated in Function `func`
`SXG2049W`	Explanation: A description was truncated for `field` by a Substation ES function (`func`) because it exceeded the length into which to place the value. User Response: Contact TIBCO Support to report the error. System Action: Substation ES continues processing normally.
`SXG2050E`	Error during UOW/ReqBlk List increase
`SXG2050E`	Explanation: Substation ES could not increase the UoW table dynamically. A condition explaining the error is suffixed to the message. User Response: It is advisable to recycle Substation ES at the earliest convenient time. Contact TIBCO Support with the information on the error from the log and trace files. System Action: Processing continues normally but possibly with a limited capacity for concurrent processing.
`SXG2052E`	UOW/ReqBlk Allocation Failed, EvtC: `value`
`SXG2052E`	Explanation: Substation ES could not allocate a UoW for a process that requested a new UoW. The condition `value` explains the reason for the failure. The requesting subtask, thread, or processes can be terminated as a result. User Response: Contact TIBCO Support with the information on the error from the log and trace files. System Action: Substation ES continues processing normally.
`SXG2053F`	ReqBlk Release Failed. UoW: `Uow` Idx: `Index` Cond: `Cond`
`SXG2053F`	Explanation: Substation ES could not release a UoW for a process that requested the release. Additional information is attached to the message to identify the cause of problem. The result is that a UoW entry could not be released and cannot be reused. User Response: It is advisable to recycle Substation ES at the earliest convenient time. Contact TIBCO Support with the information on the error from the log and trace files. System Action: Substation ES continues processing normally.
`SXG2054F`	IId: `Intf-Id` Cond: `Condition` Failed to release UoW:`Uow`
`SXG2054F`	Explanation: A Substation ES request control block (`reqblk`) failed to be released. Increased storage usage occurs. User Response: Contact TIBCO Support. System Action: Substation ES continues processing normally unless this event occurs frequently.
`SXS2059W`	UOW List Release of Storage has started
`SXS2059W`	Explanation: This message signals that the user has chosen to free communications storage and not to reuse these areas. User Response: Verify that you intended to have storage release setting (free) active. System Action: `TIBLOG` and `TIBTRC.`
`SXG2060W`	Not catered for Dead Message record Released
`SXG2060W`	Explanation: A message targeted for the Dead Message Queue (DMQ) cannot be stored because no facility is currently available to store the message. User Response: Review the service recipe or trigger definition that specifies the service level. This condition should only occur for IMS transactions. Contact TIBCO Support to report the condition after consulting the appropriate product guides. System Action: The system drops the message and continues processing.
`SXG2065E`	IId:`Intf-Id`, IPC-M, Ops Event unsupported Evt:`Num`
`SXG2065E`	Explanation: An internal operational command was sent to an interface or a thread to perform an action but the operation is currently not supported. IPC stands for Internal Process Communication and the `Num` reflects the command event the receiving interface was supposed to execute. User Response: Contact TIBCO Support with the information on the error from the log and trace files. System Action: Substation ES continues operating normally.
`SXG2070W`	IId: `Intf-Id` not found
`SXG2070W`	Explanation: An interface noted by `Intf-Id` could not be found in Substation ES. This warning is usually displayed if a command Substation ES is processing has received an invalid interface ID caused by user input. User Response: Correct `Intf-Id`, which was sent or supplied to Substation ES, and resubmit the command. System Action: Substation ES rejects the request.
`SXG2070E`	IId: `Intf-Id` not reachable. Systems Alert
`SXG2070E`	Explanation: A Substation ES process tried to contact this interface but could not reach it, or the interface did not respond. User Response: Review the Substation ES log for any error conditions and recycle Substation ES at your earliest convenience. Contact TIBCO Support with the information on the error from the log and trace files. System Action: Substation ES should continue to execute normally without disruptions.
`SXA2675I`	Requesting Auto Recovery for BES: `Intf-Id`
`SXA2675I`	Explanation: Substation ES issues this message when auto recovery is in progress for an interface. If this value applies to all interfaces, then an asterisk () is displayed. User Response:* None. System Action: After a reconnect to an IMS or CICS system is completed, Substation ES schedules an auto recover command to ensure that all services using this interface and that have a service level of guaranteed will obtain their messages from the EMS queues, and process them.
`SXG2077I`	Operational Request Feedback for IId:`Intf-Id`
`SXG2077I`	Explanation: The administration interface displays this message after an operational command has been issued and information from the target interface needs to be displayed.
`SXG2080E`	No Interface Message slots available
`SXG2080E`	Explanation: Internally used Substation ES messages have filled up the table that stores message entries. These messages are used for commands passed internally between Substation ES interfaces and other Substation ES regions. User Response: Recycle Substation ES at the earliest convenient time. Contact TIBCO Support with the information on the error from the log and trace files. System Action: The system does not process any more internal messages. Substation ES processing continues normally.
`SXG2081E`	Invalid message number: `Num` supplied
`SXG2081E`	Explanation: A reply to an internal Substation ES message is invalid. Either the message has been replied to already or the initiating process has supplied an invalid message number. User Response: Contact TIBCO Support with the information on the error from the log and trace files.
`SXG2082E`	Not sent Internal message: `Description`
`SXG2082E`	Explanation: Substation ES could not send an internal message to one of its interfaces. User Response: Contact TIBCO Support with the information on the error from the log and trace files.
`SXG2083W`	Invalid message status: `value`
`SXG2083W`	Explanation: An internal invalid message status has been detected. The message is only used for inter-TCB communications. User Response: Contact TIBCO Support with the information on the error from the log and trace files. System Action: The system can still function normally and operations should not be affected.
`SXG2084E`	Invalid IM Reply Method: `value`
`SXG2084E`	Explanation: An internal invalid message reply method wait status has been detected. The message is only used for inter-TCB communications. User Response: Contact TIBCO Support with the information on the error from the log and trace files. System Action: The system can still function normally and operations should not be affected.
`SXG2085E`	Internal Message Reply timeout for `text` RC:`rc` EvtC:`condition`
`SXG2085E`	Explanation: An internal message has received a timeout. `text` describes the error. User Response: Contact TIBCO Support with the information on the error from the log and trace files. System Action: The system can still function normally and operations should not be affected.
`SXG2086E`	Invalid message pointer
`SXG2086E`	Explanation: An internal message has received a timeout. `text` describes the error. User Response: Contact TIBCO Support with the information on the error from the log and trace files. System Action: The system can still function normally and operations should not be affected.
`SXG2090I`	Termination Status `Description`
`SXG2090I`	Explanation: This message displays the status of the active threads during Substation ES shutdown or termination. Destination: This message is displayed only if the trace and or log route level is set to 5.
`SXG2091E`	IId:`Intf-Id` IPC Failed (RC:`RC`) Unable to perform auto recovery
`SXG2091E`	Explanation: Substation ES failed to deliver an internal command through its inter-process communications mechanism. Auto recovery for guaranteed transactions can not be started. User Response: Manual recovery can be performed. Contact TIBCO Support with the log and trace files for Substation ES. System Action: Substation ES should continue to execute normally without disruptions. Destination: `TIBLOG` and `SYSLOG.`
`SXG2095F`	* User message has been lost
`SXG2095F`	Explanation: This message is issued by Substation ES if a dead message cannot be routed to its destination or written to DASD. User Response: Contact TIBCO Support with the information on the error from the log and trace files. System Action: Substation ES continues to process other messages normally.
`SXG2096F`	* Critical Address found to be NULL
`SXG2096F`	Explanation: Substation ES detected that a memory location required to execute successfully is not available. This normally denotes an operational failure. User Response: Recycle your Substation region as quickly as possible and contact TIBCO Support with the log and trace files for Substation ES. System Action: Substation ES might not continue to execute normally without failure to one or more processes. Destination: `TIBLOG` and `SYSLOG.`
`SXG2100E`	Failed to obtain Request Block
`SXG2100E`	Explanation: Substation ES has failed to obtain a request block for a Uow. Normally, this condition occurs if the entries in the UoW table have been exhausted or resource contention on the UoW table exists because of the large number of requests that Substation ES is processing. This condition might also occur if the Uow entries in the Substation ES SIP have not been correctly defined or there are too many requests for processing by Substation ES. User Response: If value of the MAXUOW parameter is not set at its maximum, increase the defined value. If that value is set to its maximum, you might have to start an additional Substation ES region and split the workload among the active Substation ES regions. If you are not sure about the steps to take, contact TIBCO Support with the information on the error from the log and trace files. System Action: Substation ES repeatedly attempts to satisfy the request. After a permitted number of retries, the request fails and the TIBCO messaging application receives an error message.
`SXG2133W`	Stress Level Caution. Impacting throughput
`SXG2133W`	Explanation: There are tasks waiting on the input queues that cannot be processed. The input queues can now be temporarily suspended internally to enable the Substation to manage the current workload. The input queues are restarted when the current workload has decreased. User Response: Increase the value of `MAXUOW`, the Substation ES configuration parameter that determines the maximum number of concurrent tasks. Subsequently, if the problem persists, contact TIBCO Support. System Action: Substation ES continues processing but at a slower rate. Destination: `TIBLOG.`
`SXG2134I`	Stress
`SXG2134I`	Explanation: This message indicates there is currently a stress condition. Other messages normally provide a realistic prognosis. Run the operational commands to help determine the effect: SHOW,INTF and SHOW,SYS,DEBUG. User Response: None. System Action: Substation ES continues processing but at a slower rate. Destination: `TIBLOG` and `TIBTRC.`
`SXG2135I`	Stress IId:`Intf-Id` Cond:STOP `Type`
`SXG2135I`	Explanation: The maximum UoW has been reached and the input threads for this interface have stopped receiving input. User Response: Increasing the MAXUOW might not always be the correct resolution, especially if the number is already at 800. Contact TIBCO Support with the information on the error from the log and trace files. System Action: Substation ES continues operating normally. However, it is advisable to determine the cause of this issue as quickly as possible. Destination: Mediums that are available.
`SXG2140I`	TAKE NOTE!! Retrying UoW list for `Num` time
`SXG2140I`	Explanation: Substation ES is retrying the UoW table to find a free UoW entry to satisfy a request from a Substation ES interface.
`SXG2202E`	IId:`Intf-Id`, not available, State:`value`
`SXG2202E`	Explanation: The target interface identified by `Intf-Id` is not active or available in the Substation ES active configuration. User Response: Ensure that the correct Substation ES interface ID has been specified or review the log file for error conditions that might have caused the interface to become unavailable. If this problem persists, contact TIBCO Support with the information on the error from the log and trace files. System Action: Substation ES does not process the request.
`SXG2310W`	IPC Get - No message found
`SXG2310W`	Explanation: The internal message communication failed to find a message that was sent to it. This is most likely an internal error where some resource access might not be catered for. User Response: Contact TIBCO Support with the information on the error from the log and trace files. System Action: Substation ES continues operating normally. However, it is advisable to restart Substation ES as soon as convenient. Destination: Mediums that are available.
`SXG2388W`	IId:`Intf-Id`, Partner IId:`Intf-Id2` not active, State:`value`
`SXG2388W`	Explanation: The Partner interface identified by `Intf-Id2` is not active or available in the Substation ES active configuration. User Response: Ensure that the correct Substation ES interface ID has been specified, or review the log file for error conditions that might have caused the interface to become unavailable. If this problem persists, contact TIBCO Support with the information on the error from the log and trace files. System Action: Substation ES does not complete processing the request.
`SXG2800I`	Starting ~ `Description`
`SXG2800I`	Explanation: This message identifies that a Substation ES interface is being started. `Description` originates from the Interface SIP on the `DESCR` keyword. If you must change the `Description` value, edit and change the value of the `DESCR` keyword for the appropriate interface.
`SXG2801I`	Initialized ~ `Description`
`SXG2801I`	Explanation: A Substation ES interface has been initialized. All work related to the interface’s own processing has completed and now the interface is waiting for Substation ES to give the signal to start processing. `Description` originates from the Interface SIP on the `DESCR` keyword. If you must change the `Description` value, edit and change the value of the `DESCR` keyword for the appropriate interface.
`SXG2802I`	Stopping ~ `Description`
`SXG2802I`	Explanation: A Substation ES interface is being stopped or terminated. All work related to the interface’s own processing has completed and now the interface continues to stop all subtasks and events and release all the storage.
`SXG2803W`	Terminating `Description`
`SXG2803W`	Explanation: The Substation ES region or a Substation ES Interface is being terminated. `Description` is the value specified on the SIP `DESCR` keyword. User Response: The operator has chosen to terminate Substation ES rather than shutting it down normally. If there are active resources or subtasks, they can be terminated because of the nature of the Substation ES shutdown request. It is advisable to issue the stop or SHUT operator command and let Substation ES quiesce normally.
`SXG2805I`	Shutdown Completed ~`Description`
`SXG2805I`	Explanation: The Substation ES region or a Substation ES Interface has been terminated successfully. `Description` is the value specified on the SIP `DESCR` keyword.
`SXG2806I`	Activated ~ `Description`
`SXG2806I`	Explanation: Substation ES or one of its Interfaces has been notified that processing can continue. Communication to and from external users are now accepted. `Description` is the value specified on the SPI `DESCR` keyword.
`SXG2810E`	Sub-Task Arguments received are invalid
`SXG2810E`	Explanation: The arguments passed to a subtask creation are invalid; this message indicates that storage has most likely been overwritten and that the software has detected the invalid memory address. User Response: Contact TIBCO Support and supply the information on the entire Substation JES2 job log. System Action: The system reports the error and attempts to continue with operations.
`SXG2811E`	Sub-Task FATAL initialization Error `function`
`SXG2811E`	Explanation: The attached subtask could not identify the storage location passed to it. User Response: Notify TIBCO Support and supply the log and trace files for Substation ES. System Action: The Substation ES Interface terminates and is not initialized.
`SXG2920I`	`Information`
`SXG2920I`	Explanation: An event control block has been posted. `Information` supplies details on the posted event. System Action: Substation ES continues normally.
`SXG2921I`	Event_Wait_List, Evtc: `value` Evt@: `address`
`SXG2921I`	Explanation: This is information on a posted event on the Substation ES wait list. System Action: Substation ES continues normally.
`SXG2931E`	Unexpected Event condition: `value` Event: `address` IId: `Intf-Id`
`SXG2931E`	Explanation: A thread or subtask within Substation ES has received an event condition that is identified by a value that has not been catered for. The event’s control block address and, optionally, the Interface ID, which reported the error, has also been recorded. User Response: Notify TIBCO Support and supply the log and trace files for Substation ES. Do not ignore this condition because processing that should have occurred has not happened. System Action: The subtask or thread ignores the condition and continues with processing as normal.
`SXG2931F`	Invalid Event Wait Condition: `Cond`
`SXG2931F`	Explanation: A Substation ES request control block (`reqblk`) failed to be released. Increased storage usage occurs. User Response: Contact TIBCO Support. System Action: Substation ES continues processing normally unless this event occurs frequently.
`SXG2936W`	Unexpected Post condition: `value`
`SXG2936W`	Explanation: An unexpected post condition was received by an event. User Response: Notify TIBCO Support and supply the log and trace files for Substation ES. System Action: Substation ES continues normally.
`SXG2940F`	* Post failed, Cond: `value`
`SXG2940F`	Explanation: A fatal error occurred during the posting of an event. User Response: Notify TIBCO Support and supply the log and trace files for Substation ES. Recycle Substation ES as soon as possible. System Action: Substation ES tries to continue normally.
`SXG2940W`	Post List failed. Cond: `value` Evt@: `address`
`SXG2940W`	Explanation: A post of an event failed with a condition value. This is a warning, but if the message is displayed continually, take the steps under User Response below. User Response: Notify TIBCO Support and supply the log and trace files for Substation ES. Recycle Substation ES as soon as possible. System Action: Substation ES tries to correct the condition. If that is not possible, this message reappears and an error condition follows.
`SXG2941W`	Post List failed. Cond: `number` Evt@: `address` EvtC: `cond` Desc: `text`
`SXG2941W`	Explanation: The arguments passed to a subtask dispatching routine failed; this message indicates that storage has most likely been overwritten and the software detected the invalid memory address. User Response: Contact TIBCO Support reporting the error with the information about the entire Substation JES2 job log. System Action: The system reports the error and attempts to continue with the operations.

Contents

Index

Search Results

General Messages