× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Days Used count
  • From: "Leif Svalgaard" <leif@xxxxxxxx>
  • Date: Fri, 22 Dec 2000 09:50:02 -0600

From: Chuck Lewis <clewis@iquest.net>

> I've seen this too Leif and if YOU don't know... :-)
>
> The Change Time on the first file was the time the job was FIRST run on
12/21...
> I then changed the CL and added this second file and reran things and the
Change
> time on the second file was again, the time this job was first RERUN with
this
> second file. It was executed 2 more times and the Change Time still
reflected the
> FIRST time either file was used on 12/21 !!! ???

Chuck,
that is the way it is supposed to work. What is stored is an approximate
timestamp
only. This is all by design (although I can't think of a good reason to do it
that way).

My problem is that programs I wrote (albeit it on another machine) a few
weeks
ago don't get their usage count updated. Neither do any system program, e.g.
QDMCOPN (which is used every day !!).



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.