Re: Security on multiple LPARs.

[rob@xxxxxxxxx]

Each person is separate, on each machine.
Kerberos and EIM help.  But even in that environment a user on LPAR1 still 
may not exist on LPAR2.  Those items just help keep the "passwords" in 
sync.
Good, bad, or indifferent, a common technique in the i world is that one 
developer may have *ALLOBJ on the development lpar and more restrictive 
authority in the production lpar.
Also, when consolidating machines on to lpars there are strange situations 
where FRED on LPAR1 may be Fred Jones and FRED on LPAR2 may be Fred Smith. 
 Some cleanup work may be involved.  (Think mergers and acquisitions.)

There are security exit points where you can add bolt on's to do what you 
desire.  I wrote simple ones to sync passwords, but not other user 
properties.

Rob Berendt