Chuck,
If I confirmed that this LF is not referenced by any program, would it be safe to delete this LF even though the object usage shows it is used once a week.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Monday, May 16, 2016 12:09 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: LF usage
On 16-May-2016 08:23 -0500, Steinmetz, Paul wrote:
1) How would I check for SQL usage you mentioned?
Re Query Engine implementing a query with a keyed Access Path
(ACCPTH) defined by a Logical File (LF) [associated with a Logical File Member (LFM)]
2) I also turned on object auditing for this LF
Not sure what to look for to confirm usage.
If even such AccPth /usage/ is tracked by auditing, which I doubt,
then there would be an object-read-access T-ZR entry for the LF;
presumes also, IIRC, the setting of OBJAUD(*ALL) for the Logical File
*FILE object.
It was used once again this morning by a once a week process.
AFaIK the last-used-date of the LF\LFM, per reference by query for
implementation, is offered only as a means to ensure usage tracking;
i.e. to prevent an appearance of unused\obsolete. That same /usage/ is,
AFaIK, not tracked additionally for auditing purposes; auditing being
satisfied instead, by access to the underlying data [each PFM opened,
over which that Access Path is defined] having been audited.
As an Amazon Associate we earn from qualifying purchases.