Connection value using Link Service value failed
Qualifier = value
SUBCODE INFORMATION:
X'1152'
A link service reported a connection failure to the node.
When this error continues to occur during connection establishment, it is due to a mismatch between the parameters specified in SNA Server Manager and either the local hardware, the physical connection, or the remote system configuration.
If the problem occurs during data transfer, it can be due to an unreliable physical connection (such as noise on an SDLC line) or faulty hardware.
Return codes for different link service types are shown in the following sections.
The following are return codes for SDLC connections.
X'10'
All the link services configured for use by the connection were inactive.
X'16'
The link service has been terminated, either by a failure or by an operator action. If the termination is due to a failure, there should be other messages logged giving reasons for the failure. Check the actions for these messages.
X'87'
An invalid SDLC frame was received. This is a protocol error generated by the remote system.
X'89'
RD received. The remote system requested disconnection.
The next three codes indicate that the modem is disconnected or the remote system dropped the line.
X'11'
Data Set Ready (DSR) failure.
X'12'
Clear To Send (CTS) failure.
X'14'
Data Carrier Detect (DCD) failure.
The next three codes indicate that the remote end is inactive but has not broken the modem connection or that there is a very poor-quality line.
X'24'
Non-productive receive retry exceeded.
X'25'
Idle time-out retry exceeded.
X'29'
Connection problem.
The next two codes indicate a local hardware problem. Check the modem and adapter.
X'2D'
Abnormal response.
X'2E'
Write time-out retry exceeded.
The next three codes indicate that the remote end returned to initialization state.
X'15'
Connection terminated by host.
X'80'
DM received in Information Transfer state.
X'88'
RIM received.
The next four codes indicate that the remote end did not reply during a contact or disconnect attempt.
X'81'
Disconnect retry limit.
X'82'
Contact retry limit.
X'84'
No response retry limit. The remote end is not answering polls.
X'85'
Remote busy retry limit. The remote end failed to come out of "receiver not ready" (RNR) state.
The following are return codes for X.25 connections.
X'37'
Loss of a virtual circuit.
X'60'
The switched virtual circuit to the host has been cleared down (broken) either by the host or by the X.25 network itself.
X'61'
The permanent virtual circuit to the host has been reset (broken) either by the host or by the X.25 network itself.
X'62'
An attempt to connect to the host through a switched virtual circuit has failed.
The next three codes indicate a problem with the remote node (contact support personnel for your network).
X'29'
Remote node not active.
X'AE'
DISC/DM received.
X'AF'
Link lost.
The next three codes indicate a protocol violation on the LAN.
X'AB'
SABME received while connection active.
X'AC'
FRMR sent.
X'AD'
FRMR received.
The DFT outage codes are derived from the line check codes generated by the 3X74 control unit. The line check code will have been logged on a previous #261 message. Take the outage code from the message, convert it to decimal, and add 484 to it. The result is the line check code. Here is an example: an outage code of 11 converts to 17 in decimal. 484 + 17 = 501, which is the line check code. Look up the line check code in the maintenance information manual for your control unit and follow the actions indicated there.
X'11'
Data Set Ready (DSR) failure.
X'14'
Data Carrier Detect (DCD) failure.
X'15'
Connection terminated by host.
ACTION: Check the return code shown, any events logged by the link service, and the local configuration and hardware to determine what the problem is. If the frequency of the problem is unacceptable, contact network support personnel.