> Next it will be MESSAGE, SMSG and IUCV traffic that will need to be > encrypted. Better not let them know about those.
Yeah, better not. It's stupid (and not exactly non-disruptive), but I suppose you *could* pull message buffer content out of a CP SNAPDUMP file if you were motivated enough. Hipersockets would be a lot harder -- getting inter-LPAR traffic would probably require a SADUMP -- at least a POR, which someone might notice...8-)
