Networking on z/OS
Previous topic | Next topic | Contents | Glossary | Contact z/OS | PDF


VTAM problem determination

Networking on z/OS

Each type of VTAM problem has a corresponding set of actions to take.

Table 1 lists sample problems that may occur in VTAM. The appropriate actions are explained in Table 2.

VTAM problem types

Table 1. VTAM problem types and appropriate actions
Symptom Problem type Action
abend message abend Perform A
Activating network nodes takes too long Performance Perform B
Application program reports an unexpected return or sense code Incorrect output or message Perform C
Deactivating network nodes takes too long Performance Perform B
Error message Message Perform C
Hung session, LU, or terminal Incorrect output Perform D
Hung system Wait Perform E
IST error message Message Perform C
LOGON takes too long to complete Performance Perform B
Performance is degraded after a network outage Performance Perform B
Response time is slow Performance Perform B
Storage message IST154I or IST561I-IST566I Storage Perform F

Actions

Table 2 lists and describes the appropriate actions to perform for further diagnostic information.

Table 2. Appropriate actions
Action Description
A Collect the following documentation:
  • Dump output
  • LOGREC
  • Symptom string
  • Abend or system completion code
  • Contents of the general registers (at the time of the abend)
  • PSW (at the time of the abend)
  • VTAM internal trace (at the time of the abend)
Note: LOGREC is the log recording data set used by z/OS. Any abend that occurs is recorded here. In addition, hardware failures are reported in LOGREC.
B Collect the following documentation:
  • System console log
  • Error file output in LOGREC
  • SMS (buffer use) trace output
C Collect the following documentation:
  • Issuing module
  • Message number
  • System console log
  • VTAM internal trace output
D Collect the following documentation:
  • VTAM internal trace output (all except LOCK)
  • Generalized trace facility CCWTRACE output
E Collect the following documentation:
  • I/O trace output
  • Buffer contents trace output
  • Dump of the VTAM primary address space including the common service area (CSA)
  • Output from the VTAM internal trace (all options except LOCK)
F Collect the following documentation:
  • Full VTAM dump




Copyright IBM Corporation 1990, 2010