× 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.



Steve

Whenever you run SETOBJACC you will get a CPC1140 completion message - the 2nd-level text tells you which pool your object was brought to, as here -

Message ID . . . . . . :   CPC1140       Severity . . . . . . . : 00
Message type . . . . . : Completion
Date sent  . . . . . . :   07/16/21      Time sent  . . . . . . : 20:30:47

Message . . . . :   40K of STAFF brought to pool with 167412K unused.
Cause . . . . . :   STAFF is a member in file STAFF, library CORPDATAVH.  The
  shared pool name or subsystem name and pool identifier within the subsystem
  is *INTERACT. The number of unused K-bytes is a snapshot taken at the start
  of the command.  If the number of K-bytes brought exceeds the number unused,
  some part of this or some other object will be forced out of the pool.
  Depending on how the pool is being used, this member may already exist (in
  part) within the pool.

You could put a watch on that message and record every instance of the command.

Other related messages are CPC1141, CPC1142, CPC1143, and CPC1144.

Regards
Vern

On 7/16/2021 3:02 PM, Steve Pavlichek wrote:
Is there a way to show what objects are pinned to memory with the SETOBJACC command or a way to prove that an object you want pinned is actually pinned to memory?



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.