Create registry key \\HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\EventLog\\Application\\ObjectStar
This message provides the status of the communications services cleanup that the resource cleanup module performed. The resource cleanup module received control from the z/OS Recovery Termination Manager because an address space or task ended unexpectedly.
The first variable holds ASID data if processing is unilateral. The second variable holds TCB data if the cleanup processing is bilateral. Unilateral resource cleanup occurs if a failing address space has insufficient resources or z/OS has terminated it. Bilateral resource cleanup occurs when the terminated task has not been removed from the address. The resource cleanup module can then attempt to coordinate cleanup between the terminated task and other tasks in other address spaces that had active communication with it.
Unilateral resource cleanup processing completed successfully. Unilateral resource cleanup notifies all communications partners that the component is no longer available. It occurs when a z/OS address space containing an Object Service Broker communications environment terminated abnormally or the bilateral resource cleanup failed.
The resource cleanup module was attempting to use bilateral resource cleanup to recover resources from a task that ended abnormally in an Object Service Broker address space. The error, described in a previous message, occurred during this cleanup and unilateral cleanup occurred instead. Unilateral resource cleanup notifies all communications partners that the component is no longer available.
The message includes the Object Service Broker communications identifier of the Object Service Broker environment involved.
This message is issued by the Object Service Broker communications request handler ESTAE routine because of an abend during communications processing. The ESTAE recovery routine will attempt to recovery from the abend. Message S6BCM871E is issued if recovery fails. Other messages may also be issued to indicate success or failure of the recovery. Diagnostic data, consisting of an error record in the system log, is also provided and if possible, an SVC dump is collected.
The first variable contains the system or user abend code. The second variable contains the reason code for the error.
2.
|
Collect any diagnostic information available (System log printout, JES log for the affected Object Service Broker address spaces, and any dumps) and contact TIBCO Support.
|
This message is issued in along with message S6BCM870E. A cleanup attempt during recovery processing for a communications request handler failed. No further communications recovery attempt is to be made for the request handler. The caller of the communications request may still attempt recovery. If this recovery is unsuccessful, the affected Object Service Broker component is abnormally ended and a dump is requested.
The resource cleanup module cannot successfully release task or address space resources allocated to Cross Memory Services. This message is specific to the first failure encountered.
The first variable in the message represents the Object Service Broker communications identifier of the Object Service Broker environment involved. The second variable represents one of the following:
•
|
RESOURCES UNAVAILABLE - the minimal resources required for resource cleanup (e.g., GETMAIN storage, establishing a recovery environment via ESTAE) are unavailable. Resource cleanup failed.
|
•
|
Collect any diagnostic information available (system log printout, JES log for the affected Object Service Broker address spaces, and any dumps) and contact TIBCO Support.
|
Unilateral resource cleanup did successfully notify all communications partners that a communications component is no longer available. Unilateral resource cleanup occurs when a z/OS address space containing an Object Service Broker communications environment terminated abnormally or the bilateral resource cleanup failed.
Verify that the load module libraries have not been damaged. This message should always be paired with the S6BCM999E message providing the return code from the LOAD macro. Record this information and contact TIBCO Support.
This message summarizes the outcome of processing that attempted to build a communications environment. If this processing was not completely successful, then the situations or errors encountered are described in detailed messages issued for each Object Service Broker Communications Implementation, prior to this message. The message provides the following information:
•
|
The completion status (SUCCEEDED | PARTIALLY SUCCEEDED | FAILED), that summarizes the outcome of the processing to build the Object Service Broker communications environment. This is interpreted as follows:
|
•
|
SUCCEEDED - Processing was completely successful. All Object Service Broker Communications Implementations that could be used, after any restrictions of the Execution Environment were taken into account, were successfully initialized. Communication can proceed optimally.
|
•
|
PARTIALLY SUCCEEDED - Processing was not completely successful. Not all Object Service Broker Communications Implementations that could be used, after any restrictions of the Execution Environment were taken into account, were successfully initialized, but at least one was. Additional messages have been issued describing the situations and/or errors that were detected. Communication can proceed, but may not be optimal.
|
•
|
FAILED - Processing was unsuccessful. No Object Service Broker Communications Implementations were successfully initialized. Additional messages have been issued describing the situations and/or errors that were detected. No communication is possible.
|
See the preceding detailed messages issued for each Object Service Broker Communications Implementation to determine what action is required for specific errors or situations encountered by a specific Object Service Broker Communications Implementation.
This message summarizes the outcome of processing that attempted to build a connection between two Object Service Broker communications environments. If this processing was not successful, then the situations or errors encountered are described in detailed messages issued for each Object Service Broker Communications Implementation, prior to this message. The message provides the following information:
•
|
The completion status (SUCCEEDED | FAILED), that summarizes the outcome of the processing to contact the Object Service Broker communications environment. These text data are interpreted as follows:
|
•
|
SUCCEEDED - Processing was completely successful. At least one Object Service Broker Communications Implementation was able to provide resources to support the connection of the two Object Service Broker communications environments. Communication between the two Object Service Broker entities can now proceed.
|
•
|
FAILED - Processing was unsuccessful. No Object Service Broker Communication Implementations were able to provide resources to support the connection of the two Object Service Broker communications environments. Additional messages have been issued describing the situations and/or errors that were detected. No communication is possible.
|
See the preceding detailed messages issued for each Object Service Broker Communications Implementation to determine what action is required for specific errors or situations encountered by a specific Object Service Broker Communications Implementation.
The Object Service Broker Communication Identifier that has been specified or selected for use by the current Object Service Broker communications environment has also been supplied as the Object Service Broker Communication Identifier to be contacted by the current Object Service Broker communications environment. Such a configuration request is pointless, and considered to be an error.
Determine how the Object Service Broker Communication Identifier was supplied to the current Object Service Broker communication environment as a candidate for communication and correct it. For example, examine execution parameter lists and control statements.
While attempting to establish an Object Service Broker communications environment, Object Service Broker was unable to allocate an Object Service Broker Communication Identifier from the pool defined for the z/OS system on which the Object Service Broker communications environment is built. All Object Service Broker Communication Identifiers in the pool were tested and found to be in use by other Object Service Broker communications environments.
•
|
Determine whether the pool is sufficiently sized (defined by the length of the numeric suffix on the Model Object Service Broker Communication Identifier) to support the maximum number of the Object Service Broker Execution Environments that execute on the z/OS System.
|
•
|
If all these Object Service Broker Communication Identifiers are in use, then consider using another pool by following the procedures outlined in the Object Service Broker Installation and Operations for z/OS manual.
|
While attempting to establish an Object Service Broker communications environment, it was determined that the Object Service Broker Communications Identifier specified for use by the Object Service Broker communications environment was already being used by another Object Service Broker communications environment. The name of the z/OS Region (Started Task, Batch Job or TSO User) that is currently using the Object Service Broker Communications Identifier is supplied in the message.
•
|
Ensure that the Object Service Broker Region currently using the Object Service Broker communication identifier is not another execution copy of the Object Service Broker Data Object Broker that received this message.
|
While attempting to establish an Object Service Broker communication environment using a specific Object Service Broker Communications Implementation, a situation or an error was encountered that prohibits the use of that specific Object Service Broker Communications Implementation. The nature of the situation or error is described in detail in other messages issued to this message. This message is usually accompanied by other messages giving specific details about the situation that was detected or the error that occurred. The name of the Object Service Broker Communications Implementation appears as variable data in the message text.
•
|
The second variable is the address of the TCB (Task Control Block) in the current Object Service Broker communications environment address space for which cleanup was being undertaken when the failure occurred.
|
While attempting to initialize a particular Object Service Broker Communications Implementation, an Object Service Broker communications environment determined that the z/OS address space is not APF Authorized. APF Authorization is required to initialize this particular Object Service Broker Communications Implementation. This message indicates that not all the installation procedures, specifically those relating to APF Authorization of load libraries and/or authorization of programs executing under TSO are complete. The name of the Object Service Broker Communications Implementation appears as variable data in the message text.
It is possible that APF Authorization is not available to this particular Object Service Broker component by a decision of the installer. If this is the case, this message can be ignored. If this is not the case, then do the following:
A particular Object Service Broker Communications Implementation has not been initialized because it was explicitly or implicitly specified that the Object Service Broker Communications Implementation be bypassed, using an HCS Options Data Definition Statement. The name of the Object Service Broker Communications Implementation appears as variable data in the message text.
The message is issued during Object Service Broker shutdown to indicate that there were serious processing errors detected in the communications component of Object Service Broker. The variable in the message will indicate the number of errors encountered. This message will be followed by S6BCM995 and S6BCM996.
The message is issued during Object Service Broker shutdown to indicate the extent of diagnostic data gathering performed for serious internal errors in the Communications Component of Object Service Broker. The first variable indicates the number of software symptom records that were successfully written to the LOGREC data set. The second variable indicates the number of system dump requests that were initiated to collect diagnostic data concerning the errors encountered.
This message is issued following messages S6BCM994 and S6BCM995 during the shutdown of an Object Service Broker region, if serious internal errors were recorded in the Communications Component during the life of the Object Service Broker Region.
The full text of the message includes the execution PSW address, as well as the module and control section name if known, where the error was detected. The internal code for the error detected is listed with a reason code for the error in hexadecimal form, followed by the register contents from the detecting module. The address space identifiers (ASIDs) of the Home address space, the Primary address space, and the Secondary Address space are provided.
When the error is detected in an Execution Environment that permits it, an SDUMPX (extended SVC Dump) request is issued. The success or failure of the dump request is indicated in the last line of the message.
The last line shows the status of a system dump request. It can be one of the following:
Note that when the message indicates that the dump was suppressed by DAE (z/OS Dump Analysis and Elimination), this is because it is a duplicate of an earlier dump taken for the same error symptoms.
If it is possible, Object Service Broker attempts to recover from the error and continue processing. However, certain errors can cause the loss of some communications capability and connectivity options.
If the error is of such a severe nature that it is impossible to continue, even in a degraded manner, then Object Service Broker abnormally terminates with a User ABEND code related to the error.
If Object Service Broker is able to continue, examine the joblog for any additional messages indicating the actions taken to recover from the error. The type of actions may include such things as terminating a connection with a user, dropping connectivity to a Peer Object Service Broker, or the loss of a connectivity interface (e.g., VTAM).
If the error was detected in an Data Object Broker, Execution Environment or Database Server region, determine if the degraded communications capability is adequate for the needs of your users and application mix. If not, then recycle the affected region in order to restore full communications capability.
If the normal operation of your Object Service Broker applications is unaffected, you may safely schedule the recycling of the affected regions until a convenient time.
In any case, collect the system log, the JES job log, any system dumps, and the z/OS LOGREC data and contact TIBCO Support for assistance.
A request for a system service failed. A Return Code appears in register 15 describing the reason for the request failure. The request is one of the following:
Refer to the documentation for a description of the service requested and the reason for the failure as described by the Return Code. Determine remedial action by considering the information provided in the manual. If the message persists, contact TIBCO Support.