Re: Object last accessed

["Angus MacQueen" <amacqueen@xxxxxxxxx>]

Hope I don't have to go that route Rob, but thanks anyway.

Angus

On 23/03/07, rob@xxxxxxxxx <rob@xxxxxxxxx> wrote:
> If not, there's always journalling.
>
> Rob Berendt
> --
> Group Dekko Services, LLC
> Dept 01.073
> PO Box 2000
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> "Angus MacQueen" <amacqueen@xxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 03/23/2007 08:34 AM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>
>
> To
> "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> cc
>
> Fax to
>
> Subject
> Re: Object last accessed
>
>
>
>
>
>
> Clare, that looks like it will do the trick.
>
> Many thanks
>
> Angus
>
> On 23/03/07, Clare Holtham <Clare.Holtham@xxxxxxxxxxxxxx> wrote:
> >
> > Hi Angus,
> >
> > If you do DSPFD *Mbr to an outfile, you can look at Last Used Date as
> well
> > as Days used count, and it also shows logical and physical reads, member
> > accesses, and opens and closes....would that do the job?
> >
> > cheers,
> >
> > Clare
> >
> > Clare Holtham
> > Director, Small Blue Ltd
> > www.smallblue.co.uk
> > IBM Certified Systems Professional
> > ----- Original Message -----
> > From: "Angus MacQueen" <amacqueen@xxxxxxxxx>
> > To: <midrange-l@xxxxxxxxxxxx>
> > Sent: Friday, March 23, 2007 11:25 AM
> > Subject: Object last accessed
> >
> >
> > > Is there any way I can identify when an object was last 'used', for
> > > example
> > > in the case of a *FILE when it was last opened regardless of whether
> > there
> > > were any changes? DSPOBJD may not be enough for my requirements.
> > >
> > > Many thanks in advance.
> > >
> > > Angus
> > > --
> > > 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.
> > >
> >
> > --
> > 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.
> >
> >
> --
> 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.
>
>
> --
> 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.