Hi Dan
It's not quite the only way - IASP's will deliver this functionality AND
allow the library names in each environment to be the same. The environments
can also be taken offline by varying off the IASP which is not possible with
your proposal.
The other implementation details would be much the same - different jobd's
etc.
I wouldn't go the route of Workstation entries; I much prefer to use routing
entries to allocate users to subsystems as workstation entries require that
all devices be named - unless a telnet exit program is used to name them and
this wouldn't make sense in the described environment.
An IASP also gives you some isolation of disk performance in the different
environments but this may be of very limited value.
Note - I'm not pushing this as the right answer, just saying that library
lists alone is not the only way. :)
Regards
Evan Harris
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dan Kimmel
Sent: Tuesday, 9 December 2008 5:42 a.m.
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
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of McKown, John
Sent: Monday, December 08, 2008 8:20 AM
To: Midrange Systems Technical Discussion
Subject: RE: YAIQ - Yet another ignorant question: multiple LPARs.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Sunday, December 07, 2008 11:16 PM
To: Midrange Systems Technical Discussion
Subject: Re: YAIQ - Yet another ignorant question: multiple LPARs.
Rob,
I don't think that's the type of sharing John's thinking about.
They way I understand it, he's used to having multiple LPARs being
able to access the same ASP at the same time.
Consider the way the SYSBAS ASP is shared when you have mulitple
IASPs. Except that instead of an IASP, you've got an actual LPAR.
Charles
You've hit it on the head. And, to be honest, if it is not possible, I
will be very glad. I really __hate__ this sharing. As far as I'm
concerned (security/auditor hat on) it is just an easy way to corrupt
data or get the wrong data into an environment. But I'm not allowed to
fix it on the z. So, it is cannot be done on the i, I will get what I
want!
--
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.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
