On 3/28/07, Alan Altmark <[EMAIL PROTECTED]> wrote:
I should point out that the *RPI service, while defined by CP, is really internal to the ACI. The internal calls CP makes to the ACI don't really care what happens to the data. It doesn't even have to communicate with the *RPI system service. In fact, without changes to the ACI, the *RPI
So how about if you make the calls to the ACI stubs nice CP exits so that we can dynamically load the modules that RACF (or someone else) supplies. We could still have the *RPI as part of CP if an entry point is associated with it to handle defined call-back from CP. Rob ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
