CICS Service requester-receiving 'Hostname is not resolved'

urampilla · Posted: Sat Mar 05, 2016 1:25 am

Am trying to test my CICS web service requester to consume a java API which is hosted on my local machine. When I try to execute the program, it fails during the Http connection open with the below CICS response codes.

RESP1 value:
13 NOTFND
RESP2 values:
20 - Host name is not resolved by name server or the format of the host option is incorrect.

Below is the information provided relevant to these RESP codes by IBM in one of their web page:
If a CICS region operating in a dual-mode environment issues a WEB OPEN command, specifying an IPv6 address (or a hostname that resolves to an IPv6 address) to a listening CICS region that is operating in a single-mode environment, the CICS region issuing the command might receive a NOTFND error code with a RESP2 value of 20 (host name is not resolved by name server or the format of the host option is incorrect). This message can be issued because the dual-mode environment has attempted to connect using IPv6 and the single-mode region does not have IPv6 capability.

I checked that my Internet connection on local machine is both IPv4 and IPv6 enabled.

Below is my HTTP connection statement:
EXEC CICS WEB OPEN
Host('my machine host name')
Hostlength(12)
Portnumber(portnumber on which API is up)
HTTP
SESSTOKEN(TOKEN)
RESP(CICS-RESP)
RESP2(CICS-RESP2)
END-EXEC.

Any help on this is much appreciated.

Robert Sample · Posted: Sat Mar 05, 2016 3:14 am

So your local PC is running HTTP server software?

urampilla · Posted: Sat Mar 05, 2016 4:01 am

Robert Sample · Posted: Sat Mar 05, 2016 7:17 am

In that case, you MUST contact your site support group and work with them to find out why the mainframe's name server is not resolving your host name of the Tomcat server. There is nothing anyone on this -- or any -- forum can do to help you as the assistance must come from someone working at your site who can investigate the issues.

urampilla · Posted: Tue Mar 08, 2016 10:54 am

I could have the issue resolved by configuring tomcat server to use my machine IP address from default IP address, 127.0.0.1. Then opening the Web connection to IP address instead of hostname.