RE: Separate asp

Hi Dave

There is some (very) minor advantage from a recovery aspect in separating a
system ASP and user data ASP; however the added complexity probably
outweighs the advantages these days, especially in your scenario where you
also have mirroring.

- If you don't regularly create libraries this might work (have to make sure
they all go to the user ASP).
- To include the IFS you need a UDFS (I think) and that's a pain as well
(has to be mounted at IPL).
- You would need to regularly audit the ASP's to make sure everything is in
it's place
- You have to manage ASP overflows which can make recovery more difficult if
not attended to

Unless you actually plan to save along the ASP lines the advantages are
absolutely negligible as mirroring provides the required protection and you
don't really have to think about it.

I think you'll find it a challenging task to keep the data segregated as
outlined unless the system is completely turnkey and the application
enforces this as well. Any kind of volatile environment and the segregation
will be compromised in a very short space of time.

Just do the mirroring if possible, in my opinion.

Regards
Evan Harris


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of ldwopt@xxxxxxx
Sent: Tuesday, 14 April 2009 9:15 a.m.
To: midrange-l@xxxxxxxxxxxx
Subject: Separate asp

Today has been a day for unique requests. A potential customer would like to
have the system configured with 2 disk mirrored to be used for the OS only
and have a 4 disk mirrored set for data only. Kinda sorta like a windows box
with a C and D drive setup. Data only on the D drive. Since I have never
worked with separate ASPs before, I believe the only way to do this is with
separate ASPs. The system will have V5R4 OS.

Is the another way of accomplishing the results?

What would be the advantage is there in creating the system this way?

Thanks in advance
Dave Willenborg
FNTS