How does Aloha do EOD ?

[Shatner]

The Aloha install I'm working on tries to do EOD twice and skips the current day.

After I reset it (either via aloha.ini or with GUI/System Date) - and refresh data, it works for the current day, but next morning it goes through the same process again. (As soon as term1, the master, finished booting up - the EOD runs one more time and sets aloha to 'tomororw')

Besides the aloha.ini, where is Aloha getting the idea that it's supposed to be 'tomorrow'

All 4 terminals and BOH times are set properly.

Aloha Version 5.2.4.92

Thanks

 

[posrescue]

Most liekely you have the EOD event set to say 04:00 instead of 28:00. Aloha runs on a 36 hour clock. If you have EOD set to run at 4am EOD will happen before your business day even starts (monday's EOD runs at 4am on monday)

 

[Shatner]

EOD is set for 2800

It may not have been clear in this post, but it's not running at two different points of the day, or the wrong point in the day. EOD runs TWICE at 2800 (4am). Runs yesterdays day.. makes dated dir.... looks happy.. faster terminals come up fine and have right system date and DOB date at bottom...

BUT...Then the terminal 'Term1' (which is the master, and one of the slowest terminals) comes back up after what should be the normal 4 am EOD -- and immediatly goes into processing EOD again - other terminals go into waiting for EOD - if finishes.. quite proud of itself and I know have dated dirs for yesterday, and today (today's of course has no data since nothing was done in that few seconds) Dates in aloha.ini - DOB on screens etc now show tomorrow..system dates on all machines are properly set to today.

I then move everything around.. set system date with either Aloha BOH Gui, or manually editing the aloha.ini in newdata and hit refresh data... everything goes back to normal and is happy (as long as I leave the BAD - now 'blank data' dated dir in the data directory. If I remove it, and refresh data at any point in the day..(they change a specials price for lunch manually for instance) it runs EOD for tomorrow.. orphaning today's 1/2 day...EOD.

If I leave the bad dated dir in there.. it will at least give the error 'dated dir exists' in the EOD log and halt so I don't have to merge days... and I can go through the process again tomorrow. I would just like to stop going through this every morning.

So.. what I am hoping to determine.. is what files/processes trigger EOD.. where on Term1 is some stale old file sitting there... there makes it think it needs to run this second time.. or is there some other file somewhere with a date in it that got set when this screwed up the first time 1.5 weeks ago that keeps getting incremented (Becuase it doesn't ever run a third time... Aloha (and specifically I believe term1) just seem to always think its supposed to be tomorrow.

All timezones/dates are set properly on all 4 terminals and BOH server.

 

[posrescue]

Try going into the ibercfg.bat file on term1 and set master capable and server capable to false. As long as your other terminals are master and server capable that will take term1 out of the mix of the problem. If the problem goes away you then know it was a configuration setting on term1 causing the problem.

EOD is very simple and is all run by the master terminal. The master compares the DOB and system date, (windows date)based on the event time of EOD. If the system refreshes at 2pm the master knows the system date and DOB should be the same and should do nothing. If the DOB is behind the system date then an EOD should start. If EOD is set to 28:00 then the master knows the system date will advance past the DOB untill 4am. When EOD starts the master places a marker file in the data directory on the fileserver, (EOD). It creates a new dated subdirectory in Aloha directory on the fileserver and copies most of the contents of the data directory to the new dated folder. After that completes it removes the trans.log and prt.log files from data. It then changes the date in the aloha.ini in the newdata directory, creates a done30 file in the dated foler, removes the EOD marker and refreshes data. This is all done by the master. The fileserver should recognize the existance of the done30 file with no coresponding grind30xxx file and grind should run.

I am guessing the problem is in the Windows date and time on the master or there may be 2 instances of EOD in events? The events could also be corrupt. See what happens with a different term running as master and go from there...

Cheers

 

[Shatner]

Thank you very much.. Thats exactly the info I was looking for.. I'll give disabling term1 as a master a try, and quadruple check that there are not multiple EOD events, dates, times and report back

Thanks again

 

[Shatner]

Just to report back.. I did finally find the solution.

Even though all the terminals, and the BOH computer were all set to Central Standard Time Zone.. and the correct time, I noticed that the timezone.ini in the data dir had the timezone listed as 'Aloha Standard Time'

The Windows 95 Control panel on terminal1 was showing 'Aloha Standard Time' as the selected timzone, even though central standard is selected in the dropdown box and aloha standard time is not an option in the drop down box.

When Net Time ran on the term server on boot.. it was showing 2 days old time (I guess some wacky offset is set for aloha standard zone?) - even though it actually shows the time to be set to the proper date/time - very confused here ... but nontheless

Deleting the timezone.ini in the Data directory, and doing a stop/start ctlsvr recreated the timzone.ini file and it properly lists 'Central Standard' properly as the timezone..

This appears to have fixed the problems.

Thank you all for all of your help.. it definitely pointed me in the right direction.

 

[Shatner]

Okay.. I was wrong on my previous post.. none of the above has worked.. and it's still going to tomorrow. I've been continuing to rig it everyday... not going to work when I'm out of town next week.

I've made 'term2' master as suggested to no avail, and found/located/tested every timezone/date I can find everywhere. Checked all the old dates for proper files.. reground everything manually...

I clearly am missing something.. probably simple..Getting pretty desparate, Anybody have any insight/ideas ?

 

[bigblok403]

Post the contents of Debout.eod