Re: [Bulk] Re: QEZSCNEP curiousity

Hi, John:

The object may say "Usage data collected" = YES, but there is a special MI instruction that must be generated into a *PGM for it to update its own "last used" information at runtime. I believe IBM does not include that MI instruction in programs intended to reside in QSYS -- it was likely considered to be "needless overhead."

HTH,

Mark S. Waterbury

> On 8/17/2015 11:11 AM, John McKee wrote:

I like the explanation as to why save/restore is not changed. But, usage
data collected shows as YES - should have included that.

Thanks

John McKee

On Mon, Aug 17, 2015 at 9:18 AM, Mark S Waterbury <
mark.s.waterbury@xxxxxxxxxxxxx> wrote:

John:

AFAIK, no *PGMs in library QSYS have "usage tracking" enabled, so they
always show blank for "Last used date" and 0 for "Days Used Count".

Similarly, objects in QSYS are not normally saved via a SAVLIB or SAVOBJ,
but are saved using the SAVSYS command, and that does not update the "Save
date/time" information (presumably because you should not normally save and
restore individual objects in QSYS using SAVOBJ or SAVLIB. (Use SAVSYS and
restore by IPLing from back-up media, or via PTFs to update those objects
incrementally.)

HTH,

Mark S. Waterbury

On 8/17/2015 9:59 AM, John McKee wrote:
This program is running in our controlling subsystem. I saw a post from
years ago in the archives where it was running in QBATCH and is for
cleanup.

I do Go SAVE 21 every week. I wonderedabout this program before I
searched
the archives. A DSPOBJD shows this program has no information recorded
for
Save/Restore or last used date.

Why would this program not have anything for save date/time?

Again, v5r4 - terminal. Maybe a few months now.

Definitely not an issue. Just curious.

John McKee

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