Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Using Messages With Identifiers : XC: Cross-Memory Control

XC: Cross-Memory Control
S6BXC200I
CROSS-MEMORY CORRESPONDENT REGIONS MAY HAVE BEEN ABANDONED
Cross-Memory Control
This message is issued by an Object Service Broker communications environment that is being terminated, if it has detected that not all the other Object Service Broker communications environments with which it had engaged in communications exchanges using Cross Memory Services have been allowed to disconnect. Any communication errors experienced by those Object Service Broker communications environments that still had active Cross Memory Services communications paths to the terminating Object Service Broker communications environment can be attributed to the termination of the current Object Service Broker communications environment.
No action is required.
S6BXC875I
CROSS-MEMORY CLEANUP FROM ABEND WILL TERMINATE CONNECTION
Cross-Memory Control
This message is issued by cleanup processing. It is issued during recovery from an intercepted abend that occurred during cross memory communications send/receive processing. It indicates that the cleanup processing has reset the cross memory communications control indicators and will attempt to terminate the communications connection that was active when the abend occurred.
This message is usually accompanied by other messages that provide additional information concerning the error, such as message S6BCM997E. Occasionally, environmental restrictions prevent any other message from being issued. An error record is written to the system log and an SVC dump is attempted.
Since this message indicates a successful cleanup from an abend, no immediate action may be necessary. Consider the following:
If the affected Object Service Broker component (Data Object Broker or Execution Environment) displays no other symptoms of difficulty, the error has successfully been isolated to affect only a single user connection.
If this message is issued repeatedly, it may indicate a severe problem with the communications capability of the affected Object Service Broker component. If normal production work is seriously affected, it may be prudent to recycle the job. In this case, collect any diagnostic information available (system log printout, JES log for the affected Object Service Broker address spaces, and any dumps produced) and contact TIBCO Support.
S6BXC888E
COMMUNICATIONS IDENTIFIER "%" COULD NOT BE LOCATED
Cross-Memory Control
An attempt by the current Object Service Broker communications environment to contact another Object Service Broker communications environment using the Cross Memory Services Object Service Broker Communications Implementation failed because the target Object Service Broker communications environment could not be located in any address space within the current image of z/OS. This may be normal, if the target Object Service Broker communications environment is usually executed on another machine (under another image of z/OS).
If the target Object Service Broker communications environment is required, ensure that it is executing and has successfully initialized its Object Service Broker communications environment.
S6BXC950W
UNABLE TO SERIALIZE CROSS-MEMORY ENVIRONMENT, RESOURCE OWNED BY %, ASID= X'%'
Cross-Memory Control
This message is issued if an Object Service Broker address space is attempting to initiate or terminate the use of a Cross Memory Services environment, but is unable to obtain control of the Object Service Broker Cross Memory Services environment resource needed to ensure the integrity of that environment during the process.
While attempting to gain control of the Object Service Broker Cross Memory Services environment resource, the Object Service Broker address space detected that control of that resource is held by another Object Service Broker address space, and all indications are that the other Object Service Broker address space is not going to release its control of the Object Service Broker Cross Memory Services resource. Something has suspended this "culprit" Object Service Broker address space while it was in transition and owning control of the Object Service Broker Cross Memory Services environment resource.
For example, a user might have pressed the <ATTN>/<PA1> key to interrupt the execution of an Object Service Broker Execution Environment executing under TSO without taking any subsequent action to continue or terminate the execution of the Object Service Broker Execution Environment.
This message provides the following information:
The name of the Object Service Broker address space that currently has control of the Object Service Broker Cross Memory Services environment in question.
The ASID, which is the hexadecimal interpretation of the z/OS Address Space Identifier of the address space that currently has control of the Object Service Broker Cross Memory Services environment in question.
Together these two data items uniquely identify the culprit Object Service Broker address space that is impeding the progress of the Object Service Broker address space that is attempting to initiate or terminate the use of the Object Service Broker Cross Memory Services environment.
This message is always followed by:
Example S6BXC951R REPLY "RETRY" OR "DEFER"
which provides the system operator with a means to direct the Object Service Broker address space on how to proceed.
This message provides the system operator with the identity of the culprit Object Service Broker address space that has control of the Object Service Broker Cross Memory Services environment resource. The operator can use this identity to determine whether the culprit Object Service Broker address space is still legitimate or if it should be purged from the system.
The system operator can make this decision based on the status of the culprit Object Service Broker address space:
If the culprit Object Service Broker address space is swapped out and/or not consuming any CPU resources, it is not going to be able to release control of the Object Service Broker Cross Memory Services environment that it is holding.
If the culprit Object Service Broker address space is consuming processor resources, then it may be about to complete its processing and release its control of the Object Service Broker Cross Memory Services environment.
The system operator can do one of the following:
If the culprit Object Service Broker address space does not appear to be consuming any system resources, the operator could purge it from the system by canceling it. The operator should then reply with "RETRY" to message S6BXC951R (if it has not already been deleted from the system console). Processing by the Object Service Broker address space that issued this message then proceeds. If another Object Service Broker address space also has control of the Object Service Broker Cross Memory Services environment resource and will not release it, this message is reissued and additional assessment and action as described above may be required.
If the culprit Object Service Broker address space is consuming system resources, the operator could decide to allow the culprit Object Service Broker address space more time to release its control of the Object Service Broker Cross Memory Services environment. The operator should reply with "RETRY" to message S6BXC951R; this causes the message issuer to reassess the situation and reissue the message if the assessment does not change.
If the Object Service Broker address space that issued this message is attempting to initiate the use of an Object Service Broker Cross Memory Services environment, the operator could decide to bypass its use of Cross Memory Services, for the time being. The operator should reply with "DEFER" to message S6BXC951R; this causes the Object Service Broker address space to continue without the use of Object Service Broker Cross Memory Services. The operator can use the COMRESTART command to direct the Object Service Broker address space to reattempt initialization of Object Service Broker Cross Memory Services at a later time.
If the Object Service Broker address space that issued this message is attempting to terminate the use of an Object Service Broker Cross Memory Services environment, a reply of "DEFER" to message HRNXC951R is treated the same as a reply of "RETRY". This means that the culprit Object Service Broker address space must release the Object Service Broker Cross Memory Services environment resource or be purged from the system, in either case allowing the Object Service Broker address space that issued the message to proceed with its termination processing.
If no reply to message S6BXC951R is provided within 5 minutes of the time that this message is issued, the issuing Object Service Broker address space simulates a reply of "DEFER" and proceeds with processing accordingly.
S6BXC951R
REPLY "RETRY" OR "DEFER"
Cross-Memory Control
This message is issued in accompaniment with message S6BXC950W, in order to permit the System Operator to provide a reply to message S6BXC950W, and direct subsequent processing of the situation that message S6BXC950W describes.
See the Action description of message S6BXC950W for a complete description of how to deal with this message.
S6BXC992E
CROSS-MEMORY CLEANUP CANNOT CONTINUE - INVALID CSA STRUCTURE DETECTED FOR % (ASID X'%').
Cross-Memory Control
Unilateral resource cleanup processing cannot identify the address space(s) that require cleanup action. The control blocks that identify established cross memory communicants have been corrupted.
The first variable item represents the name of the Object Service Broker environment involved. The second variable represents the address space identifier of the z/OS address space involved.
This message is only significant to Object Service Broker and does not necessarily indicate an error that has impact on z/OS. When issued, the following symptoms may be displayed:
A user may appear to be logged on after the Execution Environment that supported the user has terminated. The user is unable to re-logon to the same Data Object Broker.
Data access requests from other users may be queued indefinitely because of locks still held by the user that appears to be logged on.
If any of these symptoms are displayed, do the following:
Using the Object Service Broker operator interface, terminate the user's session.
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.
S6BXC995W
MVS CROSS-MEMORY SERVICES UNAVAILABLE, NO RESOURCE MANAGER INSTALLED
Cross-Memory Control
The Object Service Broker Cross Memory Services Communications Implementation could not be initialized, because the Object Service Broker MVS Resource Manager Module was not found on the system, and could not be dynamically installed.
Determine why the Object Service Broker MVS Resource Manager Module could not be dynamically installed. This information is obtained from messages that have been issued prior to this one. Correct the situation and restart the Object Service Broker Region.
S6BXC996W
MVS CROSS-MEMORY SERVICES UNUSABLE, SYSTEM AX SET IN ADDRESS SPACE
Cross-Memory Control
During the process of initializing the Object Service Broker Cross Memory Services Communications Implementation, it was found that the z/OS address space had already obtained a System Authority level that permits access to all other address spaces under the same image of z/OS. Initialization of the Object Service Broker Cross Memory Services would rescind this System Authority level, so it cannot be used at this time.
Determine how the Object Service Broker Region's address space was able to obtain the System Authority to access other address spaces (Object Service Broker does not attempt to obtain this authority itself), and assess whether or not it is necessary. Such an authority level may be cause for concern if unscreened User External Routines are being invoked by Object Service Broker Rules.
S6BXC999E
MVS % REQUEST FAILED, R15=X'%'
Cross-Memory Control
A request for a system service provided by z/OS failed. A Return Code was provided by z/OS in register 15 describing the reason for the request failure. The request is one of the following:
Refer to the appropriate z/OS manual 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.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved