On Fri, 17 Oct 2014 20:03:13 -0500 Walt Farrell <[email protected]> wrote:
:>On Fri, 17 Oct 2014 12:37:17 -0500, Victor Gil <[email protected]> wrote: :>>Thanks! This would be a totally different ball game as it brings an extra layer of communication between the address spaces. This would also require extra "authorization" which wouldn't fly well with the management :>Yes, it requires extra communication. But it solves your problem in a clean way :) :>I'm not sure in what sense you mean "extra authorization". It does not require any form of system authorization (APF, supervisor state, system key), though it might require that the user ID that the main address space is running under has an OMVS identity (UNIX UID and GID) defined. But the ID may already be set up that way. Is there some kind of USS communication path available? The standard MVS XMEM post requires APF. -- Binyamin Dissen <[email protected]> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
