RE: YAIQ - Yet another ignorant question: multiple LPARs.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dan Kimmel
Sent: Monday, December 08, 2008 10:42 AM
To: Midrange Systems Technical Discussion
Subject: RE: YAIQ - Yet another ignorant question: multiple LPARs.

John,

What you're describing is best handled on i with a single
LPAR, multiple
interactive sub-systems, and multiple library objects.
Workstations are
assigned to sub-systems by id ranges and assigned a job
description and
library list when they are signed on. Programs and data will
be found in
libraries through the library lists. This is the only way you're going
to be able to share your security info (RACF) between the multiple
subsystems. You can use group profiles to secure the libraries to keep
one set of users out of the other set's programs and data. In
fact, you
only need the subsystems to handle allocation of memory and cpu.

Dan Kimmel

Thanks. That is what I was getting from the books, but was unsure. Looks
like we might somehow use LDAP + Kerberos for a type of Single Sign On.
What would be best for the company would be to have this in MS's Active
Directory. If that is the case, then I'm likely out of a job. They would
give the i maintenance to the distributed folks. And there is no way
that I'd be offered a job by that group.

--
John McKown
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)
Administrative Services Group
9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone * (817)-961-6183 cell
john.mckown@xxxxxxxxxxxxxxxxx * www.HealthMarkets.com

Confidentiality Notice: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain
confidential or proprietary information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all
copies of the original message.