Management: TKE verus TSO Panels
W dniu 2013-01-11 15:23, Jousma, David pisze:
> We do use TKE, but I don’t think it matters for this conversation.
> But, correct me if I am wrong. We don’t assign a unique crypto
> domain per lpar. We have unique domains by environment for TECH,
>
W dniu 2013-01-11 15:23, Jousma, David pisze:
We do use TKE, but I don’t think it matters for this conversation.
But, correct me if I am wrong. We don’t assign a unique crypto
domain per lpar. We have unique domains by environment for TECH,
DEV and PROD environments. So the requirement for u
: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Knutson, Sam
Sent: Friday, January 11, 2013 8:56 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ICSF Master Key Management: TKE verus TSO Panels
Yes you have to initialize the keys in each LPAR but using CUT & PASTE in
Operating Principles #1 Be the low-cost provider.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Francis van Zutphen
Sent: Friday, January 11, 2013 2:31 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: ICSF Master Key Management: TKE verus T
Hello Radoslaw,
thanks for your feedback
> QUESTIONS: --
>
> 1. Does ICSF TSO panels method mean that the Key Management guys
> will have to logon to each lpar and load the new Master keys?
Yes. Is it big pain?
The Key management are not too happy, but they will just have to adapt
W dniu 2013-01-11 08:31, Francis van Zutphen pisze:
[...]
QUESTIONS: --
1. Does ICSF TSO panels method mean that the Key Management guys
will have to logon to each lpar and load the new Master keys?
Yes. Is it big pain?
2. Could we alternatively use the “pass phrase initializa
Hello ICSF System Programmers,
Could you please assist/advise me on the following issue/concern.
Due to the fact that we only have a couple of crypto keys to support legacy
applications on our mainframe and because of cost saving exercise, we decided
not to include the optional TKE workstatio
