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


Using Messages With Identifiers : RE: Communications RELAY

RE: Communications RELAY
S6BRE001I
Command ; processed with return code #
Communications RELAY
An command has been received and processed via operator interface. If the return code is 0 the command has completed successfully. If the return code is not 0 then a previous error message will have been issued describing the problem.
If the return code is 0 then this message is for information only. If the return code is not 0 then the action for the previous error message should be followed.
S6BRE002E
RELAY parameters processing failed due to LE initialization error - R15=;
Communications RELAY
Initialization of the Communications RELAY failed because of an LE failure. TCP/IP support has been disabled.
Refer to the IBM Language Environment Program Guide manual to determine the meaning of the return code from LE initialization. For most errors an LE will produce a formatted dump in the CEEDUMP DDNAME and will provide additional error information in a dynamically allocated print file.
S6BRE003E
RELAY parameter error;; ;
Communications RELAY
During RELAY initialization or as part of a REFRESH command an error was detected in the active relay parameter file.
Correct the error described by this message.
S6BRE004E
RELAY invalid event code #
Communications RELAY
An invalid event code has been received by the RELAY CONTROL TASK.
Contact TIBCO support.
S6BRE005E
RELAY parameter file not allocated to DDNAME ; ;; Communication RELAY disabled.
Communications RELAY
During RELAY initialization or as part of a REFRESH command the RELAY parameter file could not be located.
Correct the allocation of the RELAY parameter file.
S6BRE006E
RELAY parameter file dynamic allocation error;; errcode=# infocode=#
Communications RELAY
Dynamic allocation of the RELAY parameter file at either initialization or as a a result of an operator command.
Look up the errcode and infocode values in the 'z/OS Authorized Assembler Services Guide' manual to determine the cause of this problem.
S6BRE007E
Command ";" not recognized
Communications RELAY
An unsupported command has been received via the operator interface.
Correct the command and re-issue it.
S6BRE008E
Command ";" rejected: ;
Communications RELAY
An operator command was rejected for the reason stated.
Correct the operator command as required and re-issue it.
S6BRE009I
;. The parameter dataset is ;.
Communications RELAY
This message is issued as a result of a CS,STATUS or after the successful processing of a CS,PARMDSN= command. The relay status is displayed as either enabled or disabled. In addition the name of the current relay parameter dataset is displayed.
No action is required.
S6BRE010E
RELAY parameter area storage obtain failed with Return Code #
Communications RELAY
At either initialization or after a CS,REFRESH storage was not available to hold the in store copy of the RELAY parameter file.
Look up the return code in the 'z/OS Assembler Services Reference' under the STORAGE macro. If the return code indicates insufficient storage is available increase the storage available and retry. For any other return code contact TIBCO support.
S6BRE011E
RELAY OPENPORT failed with return code #.
Communications RELAY
An internal Communications Subsystem OPENPORT has failed.
Contact TIBCO support
S6BRE012E
RELAY ; failed for relay number # with return code #.
Communications RELAY
Either initialization or termination of a Communications Subsystem relay processor failed.
Contact TIBCO support
S6BRE875I
CLEANUP FROM ABEND WILL TERMINATE CONNECTION
Communications RELAY
This message is issued by cleanup processing. It is issued during recovery from an intercepted abend that occurred during relay communications send/receive processing. It indicates that the retry processing has reset the relay communications control indicators and will attempt to terminate the communications connection that was active when the abend occurred.
Since this message indicates a successful retry from an abend, no immediate action may be necessary. Consider the following:
If the affected Object Service Broker component (Data Object Broker, Execution Environment, Server, etc.) 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.
S6BRE888E
Communications identifier "%" could not be loacted
Communications RELAY
An attempt by the current Object Service Broker communications environment to contact another Object Service Broker using the Relay Object Service Broker Communications Implementation failed because the target Object Service Broker communications environment could not be located via the relay processes. This may be normal, if the target Object Service Broker is not normally accessible via a relay protocol.
If the target Object Service Broker communications environment is required, ensure that it is executing and has successfully initialized its Object Service Broker Relay communications environment. Ensure that the target Object Service Broker communications environment is defined correctly in the relay parameter file.

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