We got this feature along with our z14 so wanted to make use of this and am
not sure if PAGENT traffic can be offloaded to zIIP

On Tue, 29 Oct, 2019, 9:26 PM R.S., <r.skoru...@bremultibank.com.pl> wrote:

> Michael,
> It's not so easy.
> You use encrypted communication. That's what you know.
> However you don't know what hardware is used for enciphering/deciphering
> data.
> I'm rather sure that it is NOT CryptoExpress card (let's omit
> handshaking). Note, CPACF is not CryptoExpress. You can have CPACF and
> no CryptoExpress cards. You cannot have CryptoExpress cards without
> CPACF, but this is not interesting in this case.
> However sometimes it is not worth to use crypto hardware for very small
> data blocks. Like in terminal communication. In such case it can be
> software algorithm, which means CPU cycles. Or not, because AFAIK it can
> be offloaded to zIIP.
>
> --
> Radoslaw Skorupka
> Lodz, Poland
>
>
>
>
>
>
> W dniu 2019-10-29 o 10:47, Michael Babcock pisze:
> > I can’t say I’m 100% sure but highly suspect it does.  We don’t have our
> > crypto express cards configured yet so I know it’s not using them.
> >
> > On Tue, Oct 29, 2019 at 4:44 AM Jake Anderson <justmainfra...@gmail.com>
> > wrote:
> >
> >> "We use Rockets’s Bluezone for our 3270 emulator and all 3270 traffic
> uses
> >> TLS 1.2 via IBM’s policy agent"
> >>
> >> All its workload goes to CPACF ?
> >>
> >> On Tue, 29 Oct, 2019, 1:42 PM Michael Babcock, <bigironp...@gmail.com>
> >> wrote:
> >>
> >>> We use Rockets’s Bluezone for our 3270 emulator and all 3270 traffic
> uses
> >>> TLS 1.2 via IBM’s policy agent.
> >>>
> >>> On Tue, Oct 29, 2019 at 4:03 AM Jake Anderson <
> justmainfra...@gmail.com>
> >>> wrote:
> >>>
> >>>> Hi
> >>>>
> >>>> Is it possible to encrypt TN3270 connectivity using CPACF ?
> >>>>
> >>>> Just trying to understand its functionality and has anyone tried this
> >>>> functionality implementated for TN3270 connectivity.
> >>>>
> >>>> Jake
> >>>>
> >>>>
>
>
> ======================================================================
>
> Jeśli nie jesteś adresatem tej wiadomości:
>
> - powiadom nas o tym w mailu zwrotnym (dziękujemy!),
> - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub
> zapisałeś na dysku).
> Wiadomość ta może zawierać chronione prawem informacje, które może
> wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia
> (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania,
> narusza prawo i może podlegać karze.
>
> mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,
> www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy
> XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 0000025237, NIP:
> 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na
> 01.01.2019 r. wynosi 169.347.928 złotych.
>
> If you are not the addressee of this message:
>
> - let us know by replying to this e-mail (thank you!),
> - delete this message permanently (including all the copies which you have
> printed out or saved).
> This message may contain legally protected information, which may be used
> exclusively by the addressee.Please be reminded that anyone who
> disseminates (copies, distributes) this message or takes any similar
> action, violates the law and may be penalised.
>
> mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950
> Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the
> Capital City of Warsaw, 12th Commercial Division of the National Court
> Register, KRS 0000025237, NIP: 526-021-50-88. Fully paid-up share capital
> amounting to PLN 169.347.928 as at 1 January 2019.
>
> ----------------------------------------------------------------------
> 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