IST1222I
{WRITE|READ|DATA|TRACE} DEVICE device_address IS INOPERATIVE, NAME IS resource_name

Explanation

VTAM® issues this message when a WRITE, READ, DATA, or TRACE path to or from an adjacent node is no longer active. It provides information about potential problems and may be issued prior to the deactivation of a line.

device_address is the hexadecimal address of the WRITE, READ, DATA, or TRACE subchannel that is displayed.

resource_name is either:
  • The name of a leased line defined for a type 5 physical unit.
  • The name of an element in the active transport resource list, also called a TRLE name.

System action

Processing continues.

Operator response

  • If resource_name is a transport resource list element (TRLE) name, you might want to deactivate the resource that is using this TRLE, and then activate the resource again. If resource_name is a line, you might want to take the line down and restart the line. If resource_name is neither a TRLE name or a line, no action is necessary. Note that the efficiency of data transfer might be affected.
  • If the inoperative subchannel path is critical to your network, save the system log for problem determination.
    • Message IOS000I or other related messages may be issued and can provide additional information.
    • If there are no available paths and the line is deactivated, VTAM issues additional error messages. Also check for messages on the console log of the VTAM on the other side of the multipath channel.
  • Check for any FFST™ probe output. See the z/OS Communications Server: SNA Diagnosis Vol 2, FFST Dumps and the VIT for information about FFST and for a description of FFST probes.
  • 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 using EREP.
  • If you use a network management application such as the NetView® program, check to see whether an alert was recorded for this problem.

System programmer response

If the output does not indicate a hardware problem, and you cannot determine the cause of the problem, take the following actions:
  • If you have access to IBMLink, search for known problems with similar symptoms. If no applicable matches are found, report the problem to IBM® by using the Electronic Technical Report (ETR) option on IBMLink.
  • If you do not have access to IBMLink, report the problem to the IBM software 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

2

Descriptor code

4

Parent topic: IST messages for VTAM network operators IST1200I – IST1599I