Explanation
VTAM® received
an INOPERATIVE RU for nodename. The code field
gives the INOP reason code.
Note: If the resource that is going
INOP is attached remotely off an NCP, then the NCP, not VTAM, generates the INOP.
If code is
hex 0F, text supplies additional information
about the INOP type.
code (expressed in
hexadecimal) can be:
- 01
- Station INOP: There was a loss of contact, unexpected loss of
connection, or a connection establishment failure.
This error
type normally occurs after a successful connection has been established.
When link-level errors occur, the boundary function will attempt link-level
recovery procedures to recover the session. One of the definitions
that affects this recovery activity is the RETRIES operand on the
GROUP, LINE or PU definition statements. When normal recovery fails,
a higher level of recovery is needed. That recovery is identified
by this message.
This type of failure is normally followed
by message IST619I and later by IST621I or IST129I to report the success
or failure of the recovery actions. A RECMS RU should always accompany
this error. The RECMS is saved as a miscellaneous data record (MDR)
on the system error recording data set or is passed to NPDA. Use Netview/NPDA
or EREP to do the analysis.
- 02
- Link failure.
- 03
- Station INOP: SDLC Disconnect request received. An SNA-PU SDLC
connection has terminated its link manager and is informing the primary
station that it is not available (for example, it is offline).
- 04
- Station INOP: SDLC Request Disconnect response received. During
normal SDLC link activity, a RR poll received a DISC. This usually
means that the secondary station is requesting a DISC from the primary.
- 05
- Station INOP: SDLC Disconnect Mode received. The transmitting
secondary SDLC station is disconnected.
- 06
- Station INOP: IPL or dump in progress.
- 07
- Station INOP: Remote power off (RPO) in progress.
- 08
- Link: Unconditional reset by force deactivate DACTLINK.
- 0A
- X.21 switched link: Outgoing call establishment failed because
the X.21 call-progress signal was received but is not included in
bytes 6-7.
- 0B
- X.21 switched link: Outgoing call establishment failed because
of data circuit-terminating equipment (DCE) signaling DCE clear condition.
- 0C
- X.21 switched link: Outgoing call establishment failed because
of expiration of time-out on changing DCE conditions.
- 0D
- X.21 switched link: There was an unexpected loss of connection
during the X.21 call phase.
- 0E
- X.21 switched link: A failure occurred during the X.21 call-clearing
phase.
- 0F
- X.21 switched link: An outgoing call establishment failed. X.21
call progress signals were received and are included in the INOP.
- FD
- BSC line: BSC cluster PU=YES modem failure occurred. The line
and the PU will be deactivated.
- FE
- Station INOP: Station INOP on S/370 channel-link occurred.
- FF
- Link: S/370 channel-link failure occurred.
text is displayed if code is
hex 0F, and describes the call progress signal (CPS).
text can
be one of the following:
- CPS = UNRECOGNIZED CALL PROGRESS SIGNAL
- CPS = yy - [descr]
The values of
yy (expressed in decimal)
and optionally
descr can be one of the following:
- yy
- descr
- 20
- NO CONNECTION
- 21
- NUMBER BUSY
- 22
- PROCEDURE ERROR
- 23
- TRANSMISSION ERROR
- 41
- ACCESS BARRED
- 42
- CHANGED NUMBER
- 43
- NOT OBTAINABLE
- 44
- OUT OF ORDER
- 45
- CONTROLLED NOT READY
- 46
- UNCONTROLLED NOT READY
- 47
- DCE POWER OFF
- 48
- INVALID FACILITY REQUEST
- 49
- NETWORK FAULT IN LOCAL LOOP
- 51
- CALL INFORMATION SERVICE
- 52
- INCOMPATIBLE USER
- 61
- NETWORK CONGESTION
- 71
- L.T. NETWORK CONGESTION
- 72
- RPOA OUT OF ORDER
- 81
- REGISTRATION/CANCELLATION CONFIRMED
System action
Processing continues.
Notes: - VTAM does not attempt recovery
for error code 02. Link failures are not recoverable.
- If an INOP occurs before processing of an earlier INOP, VTAM does not attempt recovery.
The node is deactivated.
- For switched PUs:
- For peripheral PUs, VTAM does
not attempt recovery for any error codes.
- For subarea PUs, VTAM attempts
recovery only for error code 01.
Operator response
This is probably a hardware error. Save the
system log for problem determination. Run your operating system service
aid program to determine whether MDR/OBR information has been recorded.
See the EREP User's Guide and Reference for more information
on service aid programs.
If you use a network management application
such as NetView®, check to
determine whether an alert was recorded for this INOP code.
See
the z/OS Communications Server: SNA Diagnosis Vol
1, Techniques and Procedures for additional information on non-VTAM subarea
network problems associated with this message and for examples of
IST259I problems and diagnosis.
System programmer response
If you cannot determine the cause
of the problem from the output provided or need additional assistance,
contact the IBM® hardware support
center.
If available, provide the MDR/OBR information from
your operating system service aid program or the alert information
recorded by your network management application.
Routing code
Descriptor code