I did some testing and discovered the following for user spaces:
-- If you obtain a space pointer via the QUSPTRUS API or resolve the
system pointer and then set a space pointer from that system pointer and
then directly read data from the user space or write data to the user
space, the usage information is NOT updated.
-- If you use the QUSRTVUS API to read data from the user space, the usage
information IS updated.
-- If you use the QUSCHGUS API to change data in the user space, the usage
information is NOT updated.
So, the last one, changing the user space via the API, behaves just like
the CHGDTAARA command; it doesn't update the usage information.
You should notice that in IBM's usage documentation that user spaces
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Ken Sims
Sent: Thursday, November 01, 2012 07:26
Subject: Re: Object use vs. library use
Hi Robert -
On Thu, 1 Nov 2012 09:29:06 +0000, Robert Houts <rshouts@xxxxxxxxx>
Simply resolving a pointer to an object does not cause the last used dateto be updated. For example, the RTVDTAARA command and QWCRDTAA API both
cause the last used date of a data area to be updated. But, (inexplicably)
the CHGDTAARA command does not. In all three cases the pointer is
resolved. You can resolve pointers all day long to any objects, but the
usage information is only updated when you actually use the object.
activated). As with all objects whose usage information is tracked, it is
The last used date for a program is updated when a program is run (or
only updated the first time it is used in a given day. It has nothing to
do with whether the calling program has been running for several days or
just a few microseconds. If a program that runs for multiple days calls
another program each of those days, the called program's usage information
will be updated each day that it is called.
So for something like a user space that is being read and/or updated by
use of a pointer (rather than the user space APIs), at what point does the
system update the last-used date?
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot 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 here. If you have questions about this, please contact