Re: Tips for user ASP

["Al Barsa" <barsa@xxxxxxxxxxxxxxxxxxx>]

Oliver,

A separate user ASP for this purpose would buy you little.  Traditional
User ASP's (2 to 32) exist in the same named space as the System ASP, so
you would still be subject to library name collisions (e.g.: QGPL).  I have
two suggestions:

1).   Consider the V5R2 implementation of Independent ASPs.  I have not had
the chance to play with them extensively, but there does appear to be some
backup problems, but I will report when I check this out.  I have the
appropriate hardware coming for this later this summer.

2).   Just give them their own library names in the system ASP, and your
company get's the benefit of more disk arms.  With the system moving from
proprietary DASD to PC commodity DASD, DASD densities will grow through the
roof, and I predict that the next bottleneck for many ships will be DASD
arm contention.

Al

Al Barsa, Jr.
Barsa Consulting Group, LLC

400>390

914-251-1234
914-251-9406 fax

http://www.barsaconsulting.com
http://www.taatool.com






                      oliver.wenzel@cibavision.n
                      ovartis.com                       To:       
MIDRANGE-L@midrange.com
                      Sent by:                          cc:
                      midrange-l-admin@midrange.        Subject:  Tips for user 
ASP
                      com


                      06/28/2002 02:32 AM
                      Please respond to
                      midrange-l






Hello,

we have a sales company that also has an 820. These people want to use our
820 as a backup machine. In case
of a disaster they want to restore their main application (from the last
backup) onto our machine and do emergency
operations.

We already have an additional pair of disks (6718) and I wonder if we
should
create an User ASP for this backup
procedure.

We would like to seperate their stuff from ours, but I know there are some
gotchas involved with user ASPs.

Any suggestions,

Thanx,

Oliver
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.