View previous topic :: View next topic
|
Author |
Message |
arunn
New User
Joined: 03 Sep 2010 Posts: 15 Location: Bengaluru
|
|
|
|
Hi,
I have a query regarding the usage of web open command.
This command is used to open connection to a specified host in the internet.
Here is a snippet of the command that i am using.
EXEC CICS WEB OPEN
HOST(HOSTNAME)
HOSTLENGTH(LENGTH OF HOSTNAME)
PORTNUMBER(PORTNUM)
HTTP or HTTPS
SESSTOKEN(TOKEN)
RESP(CICSRESP)
RESP2(CICSRESP2)
END-EXEC.
Web open can done either using the HTTP or HTTPS.
First the URL used was with the scheme HTTP, defualt port number for HTTP is 80 and that is what i have used. The connection established flawlessly and everthying else went according to plan.
Now, upon changing the scheme name to HTTPS is the URL( Had to change to HTTPS as that would be the requirement down the line) and the port number was changed to 443 - Default port number for HTTPS requests. Now when a call is made i am getting back the
CICSRESP = 16: Invalid Request and CICSRESP2 = 96 : SSL not supported. Can somebody please explain to me what exactly this error means. Is there something that needs to be done from the code perspective or anything else to avoid this.
Another query is that in the reference manual from publib boulder for web open i saw that " If HTTPS is used, the CICS address space must be enabled for SSL" . I think that this is what would be required but not entirely sure as to who and how this could be achieved. I will consult the CICS admin folks regarding this , but before i did wanted to be sure that there is nothing that would be required from a developers perspective to acheive this.
Thanks in advance,
Arun. |
|
Back to top |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009 Posts: 2481 Location: Netherlands, Amstelveen
|
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
Quote: |
Is there something that needs to be done from the code perspective or anything else to avoid this. |
No -- from the code perspective things are fine. The system either does not have SSL set up, or the specific CICS region does not have SSL set up. Neither problem is code related, but something the system support group needs to address. |
|
Back to top |
|
|
|