Explanation
This message is the first in a group of messages
that VTAM® issues when the request
unit (RU)
runame has been pending on the resource
fornodename for
a period of time without receipt of a corresponding response unit.
A complete description of the message group follows.
IST530I runame PENDING FROM fromnetid TO tonetid FOR fornodename
[IST531I FROM SUBAREA = subarea, ELEMENT = element]
[IST531I TO SUBAREA = subarea, ELEMENT = element]
IST1051I EVENT CODE = code
IST1062I EVENT ID = eventid
Note: If runame remains
outstanding for subsequent intervals, these messages will be repeated
at such intervals until runame is received or until
the request unit is purged.
IST530I - runame is the request unit (RU) that is pending.
See Command and RU types in VTAM messages for a description of runame.
- The origin and destination of runame are identified
by one of the following:
- Network names (fromnetid and tonetid)
as displayed in this message.
- Network addresses (subarea number subarea and
element number element) as displayed in message
IST531I.
IST531I - VTAM will not issue this
message if both FROM network name fromnetid and TO network
name tonetid are displayed in this message.
- VTAM will display this
message once if one of the network names is unknown and twice if both
of the network names are unknown.
- If the subarea and element addresses are unknown, VTAM issues either 0 or *NA* in
place of the address.
System action
Processing continues, awaiting the corresponding
response unit.
Operator response
This message group indicates that a problem
might exist. The longer an RU remains outstanding (that is, the more
often these messages reappear for the same RU), the more probable
it is that a problem exists.
If a particular RU remains outstanding
for an extended period of time, display the node for which the I/O
is pending, and save the system log for problem determination.
If runame is CHAR
CODED, this message group indicates that VTAM sent a USSMSG to the LU and is waiting
for a response. To correct the situation, enter a VARY INACT command
for the resource fornodename and then enter a VARY ACT
for the same resource.
You can use the MODIFY IOPD command
to change the time-out interval controlling the display of this message.
See z/OS Communications Server: SNA Operation for additional information.
System programmer response
See the
z/OS Communications Server: SNA Diagnosis Vol
1, Techniques and Procedures for corrective actions for the common problems.
- If runame is CD DSEARCH, this message
group might indicate one of the following problems:
- A low IOINT value and no ADJSSCP table values were coded.
- The DYNASSCP start option and the ADJSSCP table are not properly
tuned.
- If runame is CHAR CODED, this message
group indicates that VTAM sent
a USSMSG to the LU and is waiting for a response. This is usually
a device problem. A frequent cause of this error is when a user powers
off the terminal without logging off first. To correct the situation,
enter a VARY INACT command for the resource fornodename and
then enter a VARY ACT for the same resource.
- If runame is GUNBIND and the message
is received at log off time in a cross domain environment, this message
group indicates that one of the following probably occurred:
- The application did not issue a CLSDST macro.
- The device sent an incorrect response or no response to the UNBIND
RU.
- If runame is NMVT, this message group
might indicate that the device is not real-time-monitor-capable. This
means that the device did not process the response and return the
requested information properly to the NetView® program for most devices, or to the RS/6000® network management program
for RS/6000 devices. A microcode
change is needed to permanently resolve this problem.
See the z/OS Communications Server: SNA Diagnosis Vol
1, Techniques and Procedures for information on the wait procedure.
Routing code
Descriptor code