To use this chapter, start below and follow the steps.

1. Are you receiving one or more of the following messages?
   • USS message 7 ‘LU-name UNABLE TO ESTABLISH SESSION — RU-name FAILED WITH SENSE sense’, or similar USS message
   • USS message 10 (the user-defined logon message)
   • Message IKT029I or IKT028I at the operator's console
   • Message IKJ608I at the operator's console. See Table 1 to determine what document describes message IKJ608I.

   If so, go to Logon problems.

2. Have you encountered one of the following abends?
   • ABEND0AB
   • ABEND0AC
   • ABEND0AD
   • ABEND15D

   If so, go to TSO/VTAM abends.

3. Are you having parameter initialization problems?
   • Message IKT013I or IKT014I at the operator's console.
   • Initialization parameters have not been used.

   If so, go to Parameter initialization problems.

4. Do you have a hung terminal?
   • The terminal does not respond to any keys you press.
   • You must enter data from the terminal before processing will continue (in a situation where output is expected).

   If so, go to Hung terminal problems.

5. Are you having one or more of the following screen management problems?
   • Data is in the wrong place on the screen.
   • Data stream errors occur (such as operation checks, commands are rejected, PROGxxx).
   • Function errors occur (such as incorrect full-screen processing or incorrect line prompting in input mode of TSO EDIT).
   • Data length is incorrect.
   • Data content is incorrect.

   If so, go to Screen management problems.

6. Are you having one or more of the following screen size problems?
   • The terminal does not operate in the expected screen size after logon.
   • The screen is not always the expected size during a TSO session.

   If so, go to Screen size problems.

7. Are you having one or more of the following performance problems?
   • Slow response time
   • An increase in the number of detected waits
   • An increase in the number of swap-outs

   If so, go to Performance problems.

If your problem is not listed in the steps above, it is probably not a TSO/VTAM problem. Go back to Collecting documentation for specific types of problems and look for a more likely problem symptom. If you cannot find a more likely symptom, go to Reporting the problem to IBM.