× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Joe,

I don't know for sure, but....

It would seem that having "copies" of the object in multiple pools would
violate the whole idea of single level store.  I.E. the object exists only
in one place at a time.

Testing SETOBJACC OBJ(QRPGLESRC) OBJTYPE(*FILE) POOL(*PURGE) 
Message ID . . . . . . :   CPC1142

Date sent  . . . . . . :   11/23/04      Time sent  . . . . . . :   17:06:07

 

Message . . . . :   Member PROOF purged from main storage.

 

Cause . . . . . :   The member is in file QRPGLESRC, library QGPL.  The
member
  was purged from all main storage pools that contained any parts of the

  member.


I think the "any parts" is the key.  

In other words, SETOBJACC can be used to 
1) place a given object into any particular main storage pool.
2) remove all pieces of any given object from all/some pools, no matter how
it got there.

You don't have to use SETOBJACC to place an object into a pool before you
can use SETOBJACC to purge it.  SETOBJACC will purge parts of an object that
reside in main storage as a result of normal I/O.

Charles Wilt
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: Joe Pluta [mailto:joepluta@xxxxxxxxxxxxxxxxx]
> Sent: Tuesday, November 23, 2004 5:17 PM
> To: 'Midrange Systems Technical Discussion'
> Subject: RE: Why separate pools?
> 
> 
> > From: Alexei Pytel
> > 
> > With all respect... This DOES work across memory pools.
> > As soon as page of a vurtual memory is addressable by 
> machine, it does
> not
> > matter, which pool it is in.
> 
> I don't know about that, Alexei.  If you read the documentation on
> SETOBJACC, you specify the pool to bring the object into.  It 
> seems you
> can bring the same object into multiple pools.  *PURGE will purge the
> object "from all pools".
> 
> Why would you bring an object into multiple pools if one pool 
> can access
> the same object loaded in a different pool?
> 
> Maybe an IBMer can help us.
> 
> Joe
> 
> 
> --
> 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-Ups:

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

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