I hate IASPs.  If I had my way, the system value QMAXIASP would be set to
*NONE.  For the extra hassle you will go through, LPAR or a separate
smaller development system would be worth it.

If you would like to see the pitch on Intro to IASPs that I am preparing
for COMMON, please send me private mail.


Al Barsa, Jr.
Barsa Consulting Group, LLC


914-251-9406 fax


             vree.com>                                                  To 
             Sent by:                  midrange-l@xxxxxxxxxxxx             
             midrange-l-bounce                                          cc 
                                       IASP, HA and development            
             03/25/2004 05:54                                              
             Please respond to                                             
             Midrange Systems                                              

Hi All,

We want to create a mirrored machine with Vision and we want to develop
on this machine. However, for the development machine we need some
production libraries to compile and test against that are also on the
the production machine.

We want to create the libraries with the same name but in different IASP's.

I have read some of the older threads, but I wonder if there are any new
insights. What needs to be changed the most if we take the IASP approach?

Best regards,

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.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.