At 09:59 PM 10/6/97 -0400, you wrote:
>>At 08:56 AM 9/30/97 -0400, you wrote:
>>>I would bet that if you look at the object description for an object in
>>>QRPLOBJ that used to be in ASP 2 (or 3, 4, etc) you would see the object is
>>>still in that ASP. The machine I'm on right now does not have ASPs (other
>>>than 1) so I can't check.
>>
>>Hi,
>>
>>Well we are testing some new ASP tools for TAATOOL right now, so we happen
>>to have both an 'old' and a 'new' ASP on our system now.  Walden you are
>>absolutely correct.  Replacing a program in a 'new' ASP will put the old
>>program into QRPLOBJ, and it will still be in the old ASP.  Good call.
>>
>
>
>Which makes it just as interesting:  Instead of IBM moving objects between
>ASPs, they're allowing objects from multiple ASPs in a single library!
>
The restrictions as to asp objects in libraries are arbitrary.  When IBM
introduced the notion of the ASP in CPF release 8, it was strictly a
performance thing, and ASP libraries were not made available.

in V1R3, IBM introduced the notion of ASP objects for most types of
objects.  This was fueled by demands from mainframers who didn't understand
single level storage.



Al Barsa, Jr. - Account for Midrange-L
Barsa Consulting, LLC.  
400 > 390

Phone:  914-251-9400
Fax:    914-251-9406





Private mail should be sent to barsa@ibm.net
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2019 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].