Question & Answer
Question
Why would I receive message IZE0106E Connect failed when using the CICS Interdependency Analyzer for z/OS (CICS IA) Collector with newly installed CICS Explorer V5.3.0.2 and the CICS IA plug-in V5.3.0? I am able to connect using CICS Explorer V5.2.0.6 with the CICS IA plug-in 5.2.4.
This is the message I receive:
IZE0106E Connect failed with error "Couldn't connect. The web service client couldn't be created." (SYSA DEV IA Collector)
We are running CICS IA V5.1 in our CICS Transaction Server for z/OS (CICS TS) V5.1 regions and CICS IA V5.3 in our CICS TS V5.3 regions.
There are no error messages in the CMAS log.
Here is the exception stack trace:
com.ibm.cics.core.comm.EnhancedConnectionException: IZE0106E Connect failed with error "Couldn't connect. The web service client couldn't be created." (SYSA DEV IA Collector) at com.ibm.cics.core.connections.internal.ConnectionService. enhanceExceptionMessage(ConnectionService.java:652) at com.ibm.cics.core.connections.internal.ConnectionService.doConnect (ConnectionService.java:621) at com.ibm.cics.core.connections.internal.ConnectionService.connect (ConnectionService.java:526) at com.ibm.cics.core.connections.internal.ConnectionService$7.runSub (ConnectionService.java:841) at com.ibm.cics.eclipse.common.ui.JobWithCancelingSupport$1.run (JobWithCancelingSupport.java:56) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: com.ibm.cics.core.comm.ConnectionException: Couldn't connect. The web service client couldn't be created. at com.ibm.cics.ia.sm.comm.AtomConnection.connect(AtomConnection.java: 101) at com.ibm.cics.core.connections.internal.ConnectionService.doConnect (ConnectionService.java:605) ... 4 more
I would think that the CICS IA V5.3 plug-in would be downwardly compatible. Maybe there is something that I am missing in the installation, like something new with CICS IA V5.3 security.
Answer
Part of upgrading to CICS IS 5.3 on the host side involves the removal of the ATOMSERVICE RDO definitions from prior versions. The customized job CIUDELGR found in hlq.SCIUSAMP.CICS should be run to remove old CICS resource definitions. This is described in the CICS IA 5.3 documentation in the topic Creating the upgraded collection environment under Step 3 - Updating the IA resources to CICS. You will also need to review and submit the CIUJCWEB job which is described in the same section under To define the web service resources that are required by CICS IA.
Check your CICS IA 5.3 host configuration and the RDO group to see if it still has the ATOMSERVICE and URIMAP RDO definitions from CICS IA V5.1 instead of the new CIUWPIPE PIPELINE definition for the webservice to control the CICS IA collector.
I can reproduce the problem if I try to connect to the ATOMSERVICE. I see... 
If I check my Error log in Explorer for details it shows... 
**Note**IBM CICS IA does intend to provide a future update to provide downward compatibility so the IA Collector can manage pre CICS IA V5.3 collector environments.
The following note has been added to the CICS IA V5.3 documentation topic Configuring a CICS IA Collector Connection
"Note: In the CICS IA Version 5.3 plug-in, the CICS IA Collector connection is not compatible with previous CICS IA Collector versions. To control previous versions of the CICS IA Collector, use the CICS IA Version 5.2 plug-in or the CINT and CINC CICS IA transactions."
Product Synonym
CICSIA CICS IA
Was this topic helpful?
Document Information
Modified date:
07 June 2016
UID
dwa1273758