Configuration errors are most often the cause of communications failure. To resolve these errors, you need the following information, which is created when the network is installed and successfully implemented:
CICS table definitions for TCT, PCT, PPT, FCT, and RCT
SNA definitions for the logical unit (LU) and associated Logmode table
SDLC or Token Ring connection charts to the mainframe
Named Pipe and SPX charts to clients
TCP/IP connection charts to clients
For CICS LU 6.2, server SNA configuration
For CICS TCP/IP, server TCP/IP configuration
Sybase interface files for clients and DirectConnect servers
Sybase security definitions, including client logins, connection groups, and transaction groups
Verify that this information has not changed since the error occurred. If there have been changes, determine if a recent change is contributing to or causing the problem. The following subsections explain the causes and actions for common configuration errors.
Any of the following:
Mismatched LU definitions between SNA and server
Mismatched mode names
Incorrect SNA MODETAB and APPLID macros
Incorrect CICS TCT definitions
Correct invalid names and information.
Coordinate with the DirectConnect for z/OS Option Administrator to check connection and modename profiles using the snaping or cicsping utility shipped with the product.
Any of the following:
CICS PCT or PPT entry error
Host security error
Incorrect transaction ID in the DirectConnect for z/OS Option RPC table
Verify definitions.
Coordinate with the DirectConnect for z/OS Option Administrator for correct security and transaction ID setups.
Address incorrectly configured with NCP (assumes correct line or modem setup)
Check both ends of the SDLC station or Token Ring address configuration.
Any of the following:
SNA and DirectConnect server LU definition errors
SSCPID value in the local LU profile set incorrectly
Use the SDLC trace and error log facilities to find the error.
