The direction is to define the program as OPENAPI which will cause CICS v3.1
to drive it under an OPEN TCB where you are allowed the "MVS freedom of
API", including ICSF.
The problem is that API cannot be APF authorized - so you may end-up issuing
a SVC from the OPENAPI program to get out of CICS - to APF authorized code.
From memory I do not recall if resorting to ICSF software computations
and/or hardware needs to be APF authorized.
Shmuel Koller
Discount Bank
----- Original Message -----
From: "Roger Davis" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To: <[email protected]>
Sent: Friday, May 19, 2006 1:40 PM
Subject: CICS TS v3.1 and ICSF
Hi,
We're running z/OS 1.6 and CICS TS 3.1 and in the midst of PCI/DSS
evaluation work. A question of whether a CICS COBOL transaction is able to
use ICSF has arisen. Can anyone please help in this, as copious
interrogation of CICS manuals has not helped much. We need to see if we
can encrypt and decrypt data from files read by applications.
Kind regards,
Roger Davis
Snr Systems Software Engineer
The Logic Group UK
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
