> -----Original Message-----
> From: IBM Mainframe Discussion List On Behalf Of Patrick O'Keefe
>
> On Sun, 2 Dec 2007 10:24:07 -0600, Chase, John wrote:
>
> >...
> >ICSF cannot be active if CPACF is disabled, according to ICSF doco.
> >I'm also led to believe that CPACF is a prerequisite to
> enabling CEX2.
> >...
>
> John, and Radoslaw,
>
> Thanks for your responses. I recently had someone tell me
> that CEX2 *could not* require CPACF since the CEX2
> co-processor has no access to the z9 CP hardware. But that
> argument is a semantic one.
Well, it's "technically" correct, as you observed:
> If ICSF requires CPACF and CEX2 access requires ICSF, CPACF
> is effectively a requirement for CEX2. (And it's possible
> "they" have built that requirement into CEX2 activation.)
>
> I'll spread the word here.
>
> BTW, expect more bonehead questions from me on this topic.
Please be sure to share any answers you get, especially "correct" ones.
:-)
> I spent a week looking at various (not always consistent) doc
> on encryption hardware and how it relates to TCP/IP security
> features - TLS/SSL & IPSec. I sent out a 1 page summary.
> After reading my summary, some people decided this somehow
> makes me an expert so I'm now getting questions way beyond my
> knowledge.
On the positive side, you're now "qualified" to be a "crypto
consultant". :-D
-jc-
----------------------------------------------------------------------
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
