Re: Last Used Date

Al,

Al Barsa, Jr. wrote:

> At 01:24 PM 4/2/98 -0500, you wrote:
>
> Pete,
>
> With all due respect, I disagree.  Although I am unable to find a program
> created before V2R1 that I still use, I have found several files created on
> a System/38.

Just out of curiosity, does the AS/400 that this file lives a RISC machine?  I
could believe that the re-encapsulation process would reset the bit that causes
object usage to be counted.

Heck, it may even be the restore process itself that causes this bit to get
toggled.  Easy enough to test, maybe the original questioner could save and
restore one of these objects.

jte



>
>
> I am currently looking at a file created 12/31/84 (It happens to be a
> Federal Withholding Tax Rate file, so the date seems logical - despite the
> fact that the file is physical).  It was created on System/38 Release 6.0.
>
> It clearly shows that the date last used is 3/30/98, which is the last day
> that I ran payroll.
>
> Do I not understand something about your response??
>
> Al
>
> >Al Barsa, Jr. wrote:
> >>
> >> At 09:24 AM 3/31/98 -0500, you wrote:
> >> >Can someone confirm/deny the following hypothesis?
> >> >
> >> >Our system was converted over from a System/38 & there are still many
> >> >objects out there that have not been recompiled on the AS/400.  An
> >> >object that was removed from the system because the Last Used Date on
> >> >it was zero but the program has indeed been used many times since it
> >> >was tranferred over from the System/38 (several years ago).  After
> >> >recovering the source & recompiling it (at which time the last used
> >> >date is blank) then running the option, the last used date & days
> >> >last used are filled in correctly.
> >> >
> >> "Date last used" was added in the V2R1 timeframe.  It is related to the
> >> object, and has nothing to do with the compiler.  I firmly believe that an
> >> object created on a System/38 should be able to use this function.
> >>
> >> At the moment, I am unable to check, as my system is down loading PTFs.
> >>
> >> Al
> >>
> >
> >  If the object was created prior to V2R1, then it doesnt track the
> >info.  If you recreate the object on a later release it will track it
> >(Except for anything in QDOC, which does not track this at all).
> >
> >--
> >Pete Massiello
> >OS Solutions International
> >Phone: (203)-744-7854  Ext 11.
> >http://www.os-solutions.com
> >mailto:pmassiello@os-solutions.com
> >
> >+---
> >| This is the Midrange System Mailing List!
> >| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> >| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
> >| Questions should be directed to the list owner/operator: david@midrange.com
> >+---
> >
> >
>
> Al Barsa, Jr. - Account for Midrange-L
> Barsa Consulting, LLC.
> 400 > 390
>
> Phone:  914-251-9400
> Fax:    914-251-9406
>
> Private mail should be sent to barsa@ibm.net
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: david@midrange.com
> +---



--
John Earl Lighthouse Software Inc.
8514 71st NW Gig Harbor, WA 98335
253-858-7388 johnearl@lns400.com

Without Lighthouse Network Security/400, your AS/400 is wide open.
--


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---