The “additional parameterization” is dependent on the enterprises represented in the Agency Code field in the Kernel System Parameters file. The kind of behavior is also dependent on sometimes needing to accommodate multiple agencies default behavior as well as being able to “switch” on or off some behaviors. E.g. while the default behavior for VA is to use an MPI, the default for IHS and VOE is to not do so. However, should an enterprise (like IHS) eventually implement an MPI, that behavior will need to be ready to be switched “ON”.
-----Original Message-----
What additional parameterization of this variable is needed over and above what the Kernel already provides? On 1/18/06, James Gray <[EMAIL PROTECTED]> wrote:
|
- RE: [Hardhats-members] Attracting developers Cameron Schlehuber
- Re: [Hardhats-members] Attracting developers Steven McPhelan
- Re: [Hardhats-members] Attracting developers Greg Woodhouse
- RE: [Hardhats-members] Attracting developers Cameron Schlehuber