I just looked at my code. There is no basic difference between the logic for a 
gskkyman key database name or RACF keyring name. If a product will accept one 
it should accept the other. You just need to be able to tell it "no stash file" 
-- and hopefully it is not doing something stupid like making sure the first 
character of the name is a slash.

Charles

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Charles Mills
Sent: Tuesday, September 20, 2016 1:12 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: How do I see the end date for a certificate or key on z/OS 1.13 
Tectia 6.4?


    
I apologize - I have not been following this thread. From a programming point 
of view, USS and RACF managed certificates are pretty compatible. I am 
travelling but can get you more info if you need when I land.


CharlesSent from a mobile; please excuse the brevity

-------- Original message --------
From: "Roach, Dennis" <dennis.ro...@aig.com>
Date: 9/20/16  9:13 AM  (GMT-08:00)
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: How do I see the end date for a certificate or key on z/OS 1.13 
Tectia 6.4? 

Thanks for the replies. 
Unfortunately, the product was installed to use USS hostkeys files, with the 
user keys under the user's home directory, not RACF.
Since the product was ported from the UNIX/Linex/Windows environment, I have 
seen no documentation of it being able to use RACF.

----------------------------------------------------------------------
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