Where to start troubleshooting

System administrators at the client, DirectConnect server, and mainframe must check components systematically to locate the source of a problem. Check for problems in this sequence:

1. Major outage, such as a CICS crash or power outage

2. Client application

3. Client LAN

4. Client network setup

5. DirectConnect server

6. Connection from the client application to the DirectConnect server

7. Connection from the DirectConnect server to the mainframe

8. Configuration between the transaction processor and the Server Option or the DB2 UDB Option for CICS

For any of these problems, the appropriate system administrator should:

• Record specific error message information, including:

  • Error message number

  • Associated SNA sense codes, SNA Services error codes, or TCP/IP error codes

  • The time the error occurred

  • The client or user affected

• See the appropriate documentation, as needed. For example, if you need information about the DB2 UDB Option for CICS errors, see Appendix A, “Error Messages.”

• Perform the recommended action.

• Continue the process until the problem is resolved.

Copyright © 2005. Sybase Inc. All rights reserved.

View this book as PDF