If your https target has a determinable ip address port combination, then you 
can let the z/os networking guys onfigure SSL for you by using AT-TLS. Then you 
don't need to change anything on your program, the encryption will be 
transparent to your application and from the z/os tcpip stack to the endpoint. 
There will be no encryption internal to z/os from your application to the z/os 
tcpip stack.
So ask for an AT-TLS configuration.
Hope it helps,Denis.


-----Original Message-----
From: Bernd Oppolzer <bernd.oppol...@t-online.de>
To: IBM-MAIN <IBM-MAIN@LISTSERV.UA.EDU>
Sent: Sun, Mar 10, 2019 05:55 PM
Subject: calling a webservice using HTTPS from batch (and CICS)


Hello all,

some months ago, I wrote a program which allows to call webservices 
(HTTP POST or HTTP GET)
from batch programs, written in C or PL/1. The program (subroutine) is 
written in C
and uses the standard TCP/IP socket interface, available in the 
classical z/OS environment.
I am doing all the conversion work myself, and I build the necessary 
HTTP headers, and
analyze them on return. This works without problems.

When running under CICS, I provide the same interface to the callers, 
but I use the
EXEC CICS WEB CONVERSE calls instead (because CICS does not allow me to do
standard socket calls, when under CICS control).

Now the problem is: I am limited to HTTP at the moment, but customer's 
politics
requires me to do HTTPS in the middle and long term.

I have no idea what I need to do to provide HTTPS communication in the 
batch and
in the CICS case; what are my options and what is the easiest migration 
path?

Thank you all,
kind regards

Bernd

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to