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


Using Messages With Identifiers : NC: Network Control

NC: Network Control
S6BNC100I
"SRBEXIT=NO" CODED/DEFAULTED ON VTAM APPLID='%', BUT ADDRESS SPACE IS AUTHORIZED
Network Control
The VTAM Application Identifier assigned for the use of an Object Service Broker communications environment is defined with a VTAM APPL statement that specifies or defaults the SRBEXIT keyword operand to the value of NO, but the Object Service Broker communications environment is executing in an APF Authorized address space.
This message is issued to bring attention to the fact that, since the address space is APF Authorized, the SRBEXIT keyword operand could be coded with a value of YES. This would allow VTAM to schedule the Object Service Broker VTAM ACB and NIB exits using z/OS SRBs, which reduces CPU utilization and increase multiprocessing concurrency.
The APPLID is the VTAM Application Identifier that is used by the Object Service Broker Region, and which has SRBEXIT=NO coded in its definition.
If you do not expect the APF Authorization of the Object Service Broker Region using this VTAM Application Identifier to be downgraded to Unauthorized at some time in the future, you can change the SRBEXIT keyword operand on the VTAM APPL statement (in SYS1.VTAMLST, in a VTAM Major Node Definition for Object Service Broker Network Resources) for the VTAM Application Identifier used by the Object Service Broker Region. Change it to specify SRBEXIT=YES to achieve a performance improvement in CPU utilization and multiprocessing concurrency. If the APF Authorization of the Object Service Broker Region is at some later time rescinded, the SRBEXIT keyword operand must again be changed. Specify SRBEXIT=NO; otherwise, message S6BNC998E will be issued (indicating an OPEN request failed with ACBERFLG=X'F4'), and the Object Service Broker Region will fail during initialization.
S6BNC870W
"UNBIND" REQUEST UNIT RECEIVED, APPLID='%', LU='%', TYPE=X'%'
Network Control
An SNA UNBIND Request Unit was received by the Object Service Broker Region for one of its sessions, indicating the loss of the session for an exceptional reason. This message is issued if session termination was not solicited.
The message provides the following information:
The APPLID is the VTAM Application Identifier that is used by the Object Service Broker Region.
The LU is the VTAM Logical Unit name of the session partner network resource that has (directly or indirectly) caused the SNA UNBIND Request Unit to be generated.
The TYPE is the hexadecimal UNBIND TYPE code from the SNA UNBIND Request Unit. Interpretations of this code can be found in the IBM manual Systems Network Architecture Formats.
The VTAM session is lost. To resume communications, request a new session.
S6BNC871E
"CINIT" REQUEST UNIT REJECTED, APPLID='%', LU='%', IMPROPER SESSION PARAMETERS ARE INDICATED:
Network Control
An SNA CINIT Request Unit was received by the Object Service Broker Region, representing a pending logon from some network resource. The Object Service Broker Region rejected the SNA CINIT Request Unit, due to unacceptable values in the session parameters. The SNA CINIT Request Unit is rejected with an SNA Sense Code X'08210000', which will be conveyed by the network in an SNA UNBIND Request Unit to the rejected session's session partner Logical Unit.
The message provides the following information:
The APPLID is the VTAM Application Identifier that is used by the Object Service Broker Region.
The LU is the VTAM Logical Unit name of the session partner Logical Unit that had its request for a session rejected.
This message is usually followed by messages S6BNC872I and S6BNC873I, which convey additional information about the unacceptable session parameters.
The request for a session was rejected. The session parameters associated with the Logical Unit must be corrected before further attempts to establish a session are made.
S6BNC872I
%
Network Control
An SNA CINIT Request Unit was received by the Object Service Broker Region, representing a pending logon from some network resource. The Object Service Broker Region has rejected the SNA CINIT Request Unit, due to unacceptable values in the session parameters. The session parameters from the SNA CINIT Request Unit are displayed in this message as a string of hexadecimal digits.
This message is usually preceded by message S6BNC871E and followed by message S6BNC873I.
The request for a session has been rejected. The session parameters associated with the LU must be corrected before further attempts to establish a session are made.
S6BNC873I
%
Network Control
An SNA CINIT Request Unit was received by the Object Service Broker Region, representing a pending logon from some network resource. The Object Service Broker Region has rejected the SNA CINIT Request Unit, due to unacceptable values in the session parameters. This message contains a cursor that indicates the particular session parameter(s) that is (are) the reason for rejecting the SNA CINIT Request Unit.
This message is preceded by message S6BNC872I. The cursor in this message is aligned with the hexadecimal digits in the session parameters in message S6BNC872I that are the reason for rejecting the SNA CINIT Request Unit.
The request for a session has been rejected. The session parameters associated with the LU must be corrected before further attempts to establish a session are made.
S6BNC874E
"LOGON" CONVERSATION REJECTED, APPLID='%', LU='%', RETURN CODE: X'%'
Network Control
An SNA APPC Conversation that will Logon a new Object Service Broker user to the Object Service Broker Data Object Broker has arrived from another Object Service Broker Region in the network. Due to conditions apparent at the time of the arrival of the new Conversation, the Logon has been rejected by the Data Object Broker. The message provides the following information:
The APPLID is the character encoded name of the Object Service Broker Data Object Broker that was the target of the SNA APPC Conversation.
The LU is the character encoded name of the SNA Session Partner Logical Unit that originated the SNA APPC Conversation.
The RETURN CODE is the hexadecimal encoded value of the Return Code that the Data Object Broker generated to describe the situation that caused it to reject the SNA APPC Conversation. The four digits display a two-digit return code followed by a two-digit reason code.
The request for a Conversation was rejected. The originating Conversation Partner will act on the information contained in the Return Code made available to it. Refer to message S6BKC036I for an explanation of the return code and reason code.
S6BNC875E
VTAM ATTN(FMH5) LOGIC ERROR, APPLID='%', LU='%', MODENAME='%': ATTEMPTING SDUMP
Network Control
An SNA APPC Conversation intended to logon a new Object Service Broker user to the Data Object Broker arrived from another Object Service Broker region in the network. Due to timing conditions, Object Service Broker is unable to uniquely identify the SNA session that the conversation has been allocated to. The Object Service Broker APPC LU 6.2 implementation is unable to continue processing data on this conversation, and will reject the Logon. Also, if system authority is sufficient, an SDUMP will be scheduled to aid in diagnosing the error condition. The message provides the following information:
The APPLID is the character-encoded name of the Object Service Broker Data Object Broker that was the target of the SNA APPC Conversation.
The LU is the character-encoded name of the SNA Session Partner Logical Unit that originated the SNA APPC Conversation.
The MODENAME is the character-encoded name of the VTAM Logmode Table entry that was used for the Conversation.
The request for a Conversation was rejected. The originating Conversation Partner may retry the request, as the error condition is probably temporary. If the error reoccurs, it may be necessary to shut down the originating partner's VTAM LU in order to terminate all the VTAM sessions between it and the Data Object Broker.
In any case, if this message is issued, collect any diagnostic information available (System Log printout, JES Log for the affected Object Service Broker regions, and any dumps produced) and contact TIBCO Support.
S6BNC880W
"NOTIFY" REQUEST UNIT RECEIVED, PLU='%', SLU='%', STATUS=X'%', REASON=X'%', SENSE=X'%'
Network Control
A VTAM session cannot be established.
The Object Service Broker region received an SNA NOTIFY Request Unit for one of its sessions. Currently, an SNA NOTIFY Request Unit is generated only by the failure of session establishment initiated by a VTAM REQSESS RPL Request. This message is issued if session establishment was refused after the VTAM REQSESS Request was successfully completed. This message contains significant data from fields in the SNA NOTIFY Request Unit received.
The message provides the following information:
The PLU is the character encoded name of the SNA Primary Logical Unit that had been engaged in the session.
The SLU is the character encoded name of the SNA Secondary Logical Unit that had been engaged in the session.
The hexadecimal values provided by the message are as follows:
Although it is not shown in this message (because the SNA NOTIFY Request Unit is generated as the result of a failure during session establishment), the NOTIFY CONTROL VECTOR KEY field contains a value of x'03'.
Interpretations of these codes can be found in the IBM manual Systems Network Architecture - Formats, and as described below.
Additional messages will have been issued based on the interpretation of the SENSE data receive in the SNA NOTIFY Request Unit.
If an Object Service Broker region refused the connection, then the STATUS and REASON codes are x'03' and x'80' respectively, and the sense code has the format x'0000eerr', where "ee" is the error code and "rr" is the reason code for the refusal, both reported in hexadecimal. If the target of the connection is a Data Object Broker, refer to the Explanation for message S6BKC036 for the interpretation of these codes.
Examine the reported status, reason, and sense codes, as well as the additional messages issued, to determine what action is required for the specific situation or error.
S6BNC881W
"CLEANUP" REQUEST UNIT RECEIVED, PLU='%', SLU='%'
Network Control
An SNA CLEANUP Request Unit was received by the Object Service Broker Region for one of its sessions. This Request Unit notifies the Object Service Broker Region of the loss of the VTAM session, so that the resources allocated to support the session can be released. This message contains significant data from fields in the SNA CLEANUP Request Unit received.
The message provides the following information:
The PLU is the character encoded name of the SNA Primary Logical Unit that had been engaged in the lost session.
The SLU is the character encoded name of the SNA Secondary Logical Unit that had been engaged in the lost session. Additional messages are issued in response to the activity of releasing the VTAM session's resources.
The VTAM session is lost. To resume communications, request a new session.
S6BNC882W
VTAM ATTN(LOSS) EXIT ENTERED, APPLID='%', LU='%', MODENAME='%', RPL6FLG3=X'%'
Network Control
An SNA Session that was initiated to support APPC Conversations has been terminated, and VTAM has driven the Object Service Broker ATTN Exit with a LOSS event. The message names the Object Service Broker APPLID, the name of the Conversation Partner LU and the SNA Modename (these two items define the LM Table entry), and the significant indicators from the RPL6FLG3 field.
The message provides the following information:
The APPLID is the character encoded name of the Object Service Broker application to which VTAM has reported the ATTN(LOSS) event.
The LU is the character encoded name of the SNA Session Partner Logical Unit that had been engaged in the lost session.
The MODENAME is the character encoded name of the VTAM Logmode Table entry that was used for the lost session.
The RPL6FLG3 is the hexadecimal interpretation of the RPL6DERC and RPL6LAST indicators from the VTAM Read-Only RPL that was made available by VTAM to the Object Service Broker ATTN(LOSS) exit.
The VTAM session is lost. This is probably the result of a coordinated deactivation of one of the Logical Units involved. This message is issued for documentation purposes only.
S6BNC883E
PROTOCOL OR STATE ERROR ON SESSION, APPLID ='%', LU='%' - SESSION TERMINATED
Network Control
An unexpected situation has occurred on an SNA session in an Object Service Broker Region for one of its sessions. Either the defined protocol rules have been violated or an invalid state has been reached. An example of a protocol error is the transmission of an unsupported Data Flow Control request unit. An example of a state error is the arrival of data on a session that is in the "send" state.
The APPLID is the VTAM Application Identifier that is used by the Object Service Broker Region.
The LU is the VTAM Logical Unit name of the session partner network resource that has caused the SNA Response Unit to be generated.
The VTAM session in error is lost. To resume communications, request a new session. You should determine the reason the unexpected event occurred and correct the problem. A VTAM buffer trace will assist in this determination.
If the session was with another Object Service Broker region, contact TIBCO Support.
S6BNC888E
COMMUNICATIONS IDENTIFIER "%" IS NOT ACCEPTING SESSIONS
Network Control
An attempt by the current Object Service Broker communications environment to contact another Object Service Broker communications environment using the Network Communication (SNA) Object Service Broker Communications Implementation has failed because the target Object Service Broker communications environment has not yet initialized itself as a VTAM Application.
If the target Object Service Broker Region is required, ensure that it is executing, and has successfully initialized its Object Service Broker communications environment.
S6BNC889E
VTAM VERSION Vv.r.l INSUFFICIENT FOR OBJECT SERVICE BROKER'S APPC<LU 6.2> IMPLEMENTATION
Network Control
While attempting to connect the current Object Service Broker communications environment with another Object Service Broker communications environment, it was determined that the appropriate Object Service Broker Communications Implementation to support the communication was SNA APPC (LU 6.2). The version/release level of VTAM that is installed is insufficient for use by Object Service Broker, however, and so SNA APPC cannot be used.
This message is likely to be issued only if the version/release level of the VTAM in use at the installation is very old.
If the version/release level of the installed VTAM is very old, upgrade to a more current VTAM.
S6BNC890W
LOSTERM EXIT ENTERED, APPLID='%', LU='%', REASON CODE=X'%'
Network Control
The VTAM LOSTERM Exit supplied by the Object Service Broker Region was driven by VTAM. This exit is entered when a VTAM session is being deactivated or lost.
The message provides the following information:
The APPLID is the VTAM Application Identifier that is used by the Object Service Broker Region.
The LU is the VTAM Logical Unit name of the session partner network resource whose session with the Object Service Broker Region has been lost.
The REASON CODE is the hexadecimal value of the Reason Code passed by VTAM to the VTAM LOSTERM Exit. The Reason Code supplies details about the disposition of the topic VTAM session. Interpretations of the Reason Codes can be found in the IBM manual VTAM Programming.
Additional messages may have been issued in response to the activity of releasing the VTAM session's resources.
The VTAM session is lost. Loss of the VTAM session may be the result of deactivating Network Resources by a VTAM Console Operator. To resume communications, request a new session.
S6BNC900W
TPEND EXIT ENTERED, APPLID='%', REASON CODE=X'%'
Network Control
The VTAM TPEND Exit supplied by the Object Service Broker Region is driven by VTAM. This exit is entered when a VTAM Application Definition is being deactivated by the system operator, or when VTAM is abnormally terminating.
The message provides the following information:
The APPLID is the VTAM Application Identifier that is used by the Object Service Broker Region.
The REASON CODE is the hexadecimal value of the Reason Code passed by VTAM to the VTAM TPEND Exit. The Reason Code supplies details about the disposition of the Object Service Broker Region's status as a VTAM Application. Interpretations of the Reason Codes can be found in the IBM manual VTAM Programming.
Additional messages may have been issued in response to the activity of relinquishing the Object Service Broker Region's VTAM Application Program status.
The Object Service Broker Region's status as a VTAM Application Program either has been lost, or is being relinquished gracefully. Loss of the VTAM Application Program status may be the result of a VTAM console operator deactivating Network Resources. Refer to the accompanying messages to determine what action is required for the specific situation or error.
S6BNC991E
VTAM RESP EXIT ENTERED WITH UNSOLICITED "%" %RSP, APPLID='*UNKNWN*', LU='*UNKNWN*' - SESSION TERMINATED
Network Control
An unexpected SNA Response Unit was received by the Object Service Broker Region for one of its sessions. It is either an unsolicited positive response to normal flow data, or else it is an unsupported response type.
The message provides the following information:
The APPLID is the VTAM Application Identifier that is used by the Object Service Broker Region.
The LU is the VTAM Logical Unit name of the session partner network resource that has caused the SNA Response Unit to be generated.
The VTAM session in error is lost. To resume communications, request a new session. You should determine the reason the unexpected response unit was generated and correct the problem.
If the session was with another Object Service Broker region, contact TIBCO Support.
S6BNC992E
APPC ERROR LOG DATA RECEIVED -> %
Network Control
While engaged in an SNA APPC (LU 6.2) Conversation, an error was detected by the conversation partner Logical Unit, and an APPC Error Log string was sent to the current Object Service Broker communications environment. The text from the APPC Error Log string is contained in the message. The conversation will have been terminated.
The text of the APPC Error Log string provides an explanation of the error that occurred in the conversation partner Logical Unit. Any specific action to be taken depends on the content of this text.
S6BNC993E
VTAM APPCCMD RPL REQUEST ERROR DETECTED, APPLID='%', LU='%' CONTROL=%, QUALIFY=%, RCPRI='%', RCSEC='%'
Network Control
A physical error related to an LU 6.2 API request issued to VTAM was detected by VTAM and passed to Object Service Broker. Such an error can disrupt communication on the APPC Conversation for which the request was issued. This message contains significant data from fields in the VTAM RPL (Request Parameter List) that conveyed the failed request to VTAM. This message is in two parts, due to the length of the text that it contains.
The message provides the following information:
The APPLID is the character encoded name of the Object Service Broker Application to which VTAM has reported the LU 6.2 Request failure.
The LU is the character encoded name of the SNA Session Partner Logical Unit that is engaged in the SNA session for which the LU 6.2 Request failure has occurred.
The CONTROL and QUALIFY are the character encoded names that together describe the VTAM LU 6.2 API Request type that has failed. The purpose of these VTAM RPL requests can be found in the IBM manual Macro Instructions.
The RCPRI and RCSEC are the hexadecimal interpretations of the VTAM LU 6.2 API's Primary and Secondary Return Codes made available in the VTAM RPL Extension of the VTAM RPL used to issue the failed VTAM LU 6.2 Request. Interpretations of these codes can be found in the IBM manuals VTAM Programming for LU 6.2.
If the error is accompanied by nonzero Sense data, this message will be followed by:
Example S6BNC994E SENSE DATA PRESENT, RPL6SN SI=X' %'
This message is issued to provide documentation about the error that has been detected. The affected Object Service Broker component is advised of the error and takes subsequent action to remedy or recover from the error.
S6BNC994E
SENSE DATA PRESENT, RPL6SNSI=X'%'
Network Control
A physical error related to an LU 6.2 API request issued to VTAM was detected by VTAM and passed to Object Service Broker. Such an error can disrupt communication on the session for which the request was issued. This message is always preceded by:
Example S6BNC993E VTAM APPCCMD RPL REQUEST ERROR DETECTED, APPLID='%', LU='%', CONTROL=%, QUALIFY=%, RCPRI=X'%', RCSEC='%'
which describes the VTAM RPL Request that was issued, and the exceptional or abnormal condition that was encountered. The S6BNC994E message contains additional significant data from fields in the VTAM RPL (Request Parameter List) that conveyed the request in error to VTAM.
The RPL6SNSI is the hexadecimal representation of the System Sense Code data stored in the VTAM RPL Extension to describe the physical error encountered. Interpretations of this code can be found in the IBM manual VTAM Messages and Codes.
Since this message augments the message that precedes it, refer to the preceding message to determine the proper action to take.
S6BNC995E
VTAM % EXIT ENTERED, APPLID='%', { LU='%',} RPLREQ=%, RPLRTNCD/RPLFDB2=X'%'
Network Control
A physical error or logical error related to a request issued to VTAM was detected by VTAM and passed to Object Service Broker. Such an error can disrupt communication on the session for which the request was issued. This message contains significant data from fields in the VTAM RPL (Request Parameter List) that conveyed the failed request to VTAM.
The message provides the following information:
The first variable data item is substituted with either "SYNAD" or "LERAD", signifying either a physical or a logical error, respectively.
The APPLID is the VTAM Application Identifier that is used by the Object Service Broker Region.
The LU is the VTAM Logical Unit name of the session partner network resource for the session that has experienced the problem. This item may be omitted from the message if it cannot be determined, such as in the case of a logical error.
The RPLREQ is the type of VTAM RPL Request that was issued. The purpose of these VTAM RPL requests can be found in the IBM manual instructions.
The RPLRTNCD/RPLFDB2 data is the hexadecimal return and feedback codes from VTAM that describe the physical or logical error encountered.
Interpretations of these codes can be found in the IBM manuals VTAM Programming and VTAM Messages and Codes.
If the first variable item is replaced by "SYNAD" (indicating a physical error), this message may be followed by:
Example S6BNC996E SENSE DATA PRESENT, SSENSEI/SSENSMI=X'%', USENSEI=X'%'
Action depends on the interpretation of the data extracted from the RPL for the failed request. In the case of a physical error ("SYNAD" specified), the problem can usually be identified and corrected if information in the message and relevant manuals is interpreted by personnel familiar with VTAM networks. If remedial action cannot be determined, contact TIBCO Support. In the case of a logical error ("LERAD" specified), although corrective action can be taken for some logic errors, a programming fix is usually required. If this is the case, contact TIBCO Support.
S6BNC996E
SENSE DATA PRESENT, SSENSEI/SSENSMI=X'%', USENSEI=X'%'
Network Control
A physical error related to a request issued to VTAM was detected by VTAM and passed to Object Service Broker. Such an error can disrupt communication on the session for which the request was issued. This message is always preceded by:
Example S6BNC995E VTAM SYNAD EXIT ENTERED, RPLREQ=%, RPLRTNCD/RPLFDB2=X' %'
which describes the VTAM RPL Request that was issued, and the exceptional or abnormal condition that was encountered. The S6BNC996E message contains additional significant data from fields in the VTAM RPL (Request Parameter List) that conveyed the request in error to VTAM.
The SSENSEI/SSENSMI data is the hexadecimal System Sense Code and System Sense Modifier data stored in the VTAM RPL to describe the physical error encountered. Interpretations of this code can be found in the IBM manual VTAM Messages and Codes.
The USENSEI is the hexadecimal User Sense Code data stored in the VTAM RPL to describe the physical error encountered. If the SSENSEI/SSENSMI data is nonzero, then interpretations of the USENSEI code can be found in the IBM manual VTAM Messages and Codes.
Since this message augments the message that precedes it, refer to the preceding message to determine the proper action to take.
S6BNC997E
VTAM % % REQUEST FAILED, R15=X'%', R0=X'%'
Network Control
A VTAM Manipulative Macro Instruction request has failed. A Return Code and possibly a Reason Code were provided by VTAM in registers 15 and 0 respectively, describing the reason for the request failure. Interpretations of the Return and Reason Codes can be found in the IBM manual VTAM Programming. The VTAM Manipulative Macro Instruction is one of the following:
The VTAM Control Block being manipulated is one of the following:
Action depends on the interpretation of the Return and Reason Codes provided by VTAM. This message usually indicates that a programming fix is required. If this is the case, contact TIBCO Support.
S6BNC998E
UNABLE TO % VTAM ACB, APPLID='%', R15=X'%', ACBERFLG=X'%'
Network Control
A VTAM ACB-Based Macro Instruction failed. The message provides the following information:
The first variable item is the name of the VTAM ACB-based Macro Instruction that was issued, either OPEN or CLOSE.
The APPLID is the VTAM Application Identifier that is used by the Object Service Broker Region.
A Return Code is provided by VTAM in register 15 describing the reason for the request failure.
The contents of the ERROR field (ACBERFLG) from the VTAM ACB is also provided in the message.
Interpretations of the Return Code and ERROR field can be found in the IBM manual VTAM Programming, in the section for the appropriate VTAM ACB-Based Macro Instruction.
Contact the person who supports the VTAM Network to interpret the ERROR field extracted from the VTAM ACB and determine remedial action. If remedial action cannot be determined, contact TIBCO Support.
S6BNC999E
MVS % REQUEST FAILED, R15=X'%'
Network Control
A request for a system service provided by z/OS has 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 problem persists, contact TIBCO Support.

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