On Thu, 22 Apr 2010 19:19:29 +0100, Sam Siegel <[email protected]> wrote:
>The requirements exists because I'm trying to write something that will be >Ziip enabled and leased as a product. > >Prior to passing the buffer to a work queue for the SRB, there is the >possibility that the user (which can be a normal programmer) will need to >modify the data in the buffer or provide additional data once the data >source has been drained. > >I don't want the to impose a requirement of authorized code for the exit as >most shop will not allow application programmers to put code in an >authorized library. > >Having systems staff write the code creates a bottleneck on the application >rate of change. > Given that explanation (thanks, Sam) my first choice would be providing a way for an unauthorized application to communicate with your authorized application and pass it a work request + data. Some such approaches have come up already. TCP/IP, sockets, or UNIX sockets, or UNIX named pipes, or a cross-memory PC routine you would establish, are probably all worthy of investigation and will prove (I believe) much safer to use, and in the long run simpler to program and maintain. -- Walt Farrell, CISSP IBM STSM, z/OS Security Desgn ---------------------------------------------------------------------- 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
