Good idea. I'll try that tomorrow since I don't have access to the
server from home. The *.dat file has today's timestamp. So if I
check it tomorrow and it doesn't have 25th in it, then something
unusual is going on. The error log has no errors whatsoever. just a
couple of overlap log files, nothing to scream about.
Bassam
At 04:44 PM 7/25/2005, you wrote:
Well, check the contents of the .dat file too. If it really was run on the
25th, it should have a line within the top ten that looks something like
this:
x PS 2005 07 25 11 25
If it does have that line, then Report Magic is reading a different file
(it reported Program Starts {PS} date of 2005-07-18). If it does not have
that line, then try deleting the file and running Analog again to make
sure Analog is the one touching the file and not something in your script.
--
Jeremy Wadsack
Seven Simple Machines
On Mon, July 25, 2005 1:05 pm, Bassam Abdul-Baki said:
> Analog's *.dat output file had today's timestamp. I know because I
> manually ran it today after the scheduler failed to produce the
> correct results. If I had run Analog last week, the time period that
> it generated would have been correct. However, my expected time
> period was supposed to be run on 25th from 17th to 23rd. This is
> definitely not what I got. It just occurred to me to check the date
> on the server machine. I'm wondering if somebody (too many admins)
> was playing around with it. The DATE call that I made in my script
> should in no way have affected that, so it must have been a manual change.
>
> Bassam
>
> At 02:53 PM 7/25/2005, you wrote:
>>On Monday, July 25, 2005 12:34 PM [EDT],
>>[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>>
>> >> Not true. Analog ran at 1:00 AM today.
>>
>>The report that you posted excerpts from was run last week, on July 18th.
>>It's written there, in black and white. Analog just timestamps the output
>>with "now", no matter what subset of logs it is told to report on.
>>
>> >> The Report Magic files all have today's timestamp.
>>
>>So Report Magic ran this morning, on the output from last weeks Analog
>> run.
>>
>> >> The Analog error log had nothing unusual ad
>> >> had today's date.
>>
>>What's the timestamp of the output file that Analog produced?
>>
>>Aengus
+------------------------------------------------------------------------
| TO UNSUBSCRIBE from this list:
| http://lists.meer.net/mailman/listinfo/analog-help
|
| Analog Documentation: http://analog.cx/docs/Readme.html
| List archives: http://www.analog.cx/docs/mailing.html#listarchives
| Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
+------------------------------------------------------------------------
+------------------------------------------------------------------------
| TO UNSUBSCRIBE from this list:
| http://lists.meer.net/mailman/listinfo/analog-help
|
| Analog Documentation: http://analog.cx/docs/Readme.html
| List archives: http://www.analog.cx/docs/mailing.html#listarchives
| Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
+------------------------------------------------------------------------
