Gen 8.6 ECI v2 Middleware troubleshooting
Article ID: 188849
Updated On:
Products
Issue/Introduction
With the new support in Gen 8.6 of ECI v2 for C clients (GUI, COM Proxy, and C Proxy), this article was written to cover troubleshooting advice and common errors for using ECI with Gen.
It can be used when implementing Gen C clients connected to Gen CICS servers via ECI v1 or V2.
Environment
Gen 8.6 C clients (GUI, COM Proxy, and C Proxy)
ECI v1 or V2
Resolution
Table of Contents
Where to look when problems arise:
Communications configuration:
- Values set in commcfg.ini (if creating a Gen Support case is ultimately required they can advise on setting debug options in this file)
- Security type used (Enhanced, Standard, None)
- Values before/after user exit
- What type of ECI flow (v1, v2 COMMAREA, v2 CONTAINER)
CICS Log:
- Security errors
- Communication errors
- CICS Command errors (Get/Put Container)
Windows Event Viewer:
- CTG errors
- Application errors
CTG Online Documentation:
Common Errors and possible root causes:
ECI_ERR_SYSTEM_ERROR
- CTG not started – ECI v1
CTG_ERR_CONNECTFAILED
- CTG not started – ECI v2
- PortNumber not correct
ECI_ERR_NO_CICS
- CICS not running
ECI_ERR_UNKNOWN_SERVER
- ECI System Name not known to CTG
- Attempt to send ECI v1 flow on IPIC network protocol
ECI_ERR_INVALID_CALL_TYPE
- ECI System Name not known to CTG – Container
- Attempt to send Container on non-IPIC network protocol
CTG_ERR_BADHOST
- HostName not correct
Additional Information
See related KB article: Gen 8.6 ECI v2 Support
Related documentation:
Release Notes > New Features - see "Enhanced ECI Support for Gen C Clients and Gen Java Clients(SO12045, SO12046, SS12686)"
Distributed Processing Terminology > ECI Terminology
Working With Distributed Processing > Overriding Communications Support at Execution Time
NOTE commcfg.ini syntax for ECI v1 versus v2
v1: <TRANCODE> ECI {ECI System Name}
v2: <TRANCODE> ECI <StorageType> {HostName} {PortNumber} {ECI System Name}
Feedback
