ALOHA Grind Process

[DannyZimmerman]

I work for a company that is developing a RealTime monitoring system that for applications such as ALOHA and I need to know more about how the Aloha Grind process works. Also if anyone has the AKBID1016 file this supposly talks about the Grind Process and Errors. I believe it might come with the user manual but not sure.

Thanks

Danny

RealTime Intelligence Solutions

 

[erock123]

When you say real time, are we talking milliseconds or hours?

Grinding is just a process that launched an exe file and crunches the numbers into .DB files which more or less are like CSV files.

 

[IndexRobert]

It all depends on what you are trying to achieve. The gnd**.dbf files can be used for multiple purposes, however we also created programs based on the chit- and checkfiles that can be created by Aloha. Although you have to set it up correctly, it can be a very viable alternative for use in inventory programs (real-time depletion).

 

[JKirland]

Server to initialize the grind process for the dated folder. In this case, the grind files are created in the dated folder. If you are using an RDB, the tables are created in the RDB database.

- You are regrinding a dated folder.

- If you are using a RDB, then grind process is constantly active or standing by. Refer to the Relational Databases and Aloha POS User Manual for more information.



When the grind process completes, it creates a file labeled GNDDBF30.XXX in the dated folder. This file signifies the grind process has successfully completed.

Failure to Automatically Grind
If the grind process does not automatically initialize, verify the following:



Control or Control Server is not active on the file server. Control or Control Server must be active on the file server for the grind process to start following the EOD process because it regularly scans the dated folders created by the EOD process for new folders to grind. If Control or Control Server is not active, the folders are not scanned and the grind process does not automatically start. The following precautions help prevent this:
a) If Control Server is not registered as a Microsoft® Windows® service (in versions 4.2x and higher), place a shortcut to Control or ALOHAMGR.EXE (Aloha Manager) in the Windows StartUp folder and configure Windows to automatically log in (refer to document ID 5975). This ensures that the operating system (OS) logs in and processes the StartUp folder in case of a power failure or unexpected shutdown.

b) If Control Server is not registered as a Windows service, disable the user's option to exit Control or Aloha Manager.

c) Register Control Service as a Windows service.

The 'Auto Grind and Summarize' flag is cleared in Control (versions 4.4x and lower). The 'Auto Grind and Summarize' setting in Control enables or disables the grind process from automatically activating when needed. This setting, located in Control/System/Auto Grind and Summarize, is very easy to inadvertently clear. The ability to clear this setting is controlled by the user's abilities as defined in the Aloha Back of House (BOH) security configuration. Refer to the Aloha QuickService or TableService User Manual for more information. All users, regardless of standing, should be disabled from clearing this flag.
In versions 5.0x and higher, ensure that Aloha Manager/Maintenance/Store Settings/System/Aloha Settings/Disable Auto-Grind is not enabled. If it is, disable it, refresh the system, and restart Control Server. In versions 4.4.x and lower, ensure that Maintenance/System/'Auto Grind and Summarize' is disabled.
The Summary file creation is interfering with automatic grinding of the new dated folder's data. This usually becomes an issue when Summary files are enabled after multiple dated folders already exist and the Summary process cannot catch up to the current date before another new dated folder is created. If you do not need the Summary files, disable them by setting the RUNSUM variable in the ALOHA.INI to FALSE. Refer to document ID 6075 for more information on the Summary process.
A Winhook file is defined in the configuration files, but the batch file does not exist in the BIN folder. The Grind process may not automatically start following the EOD process if a Winhook batch file is defined in the BOH, but the batch file does not actually exist in the BIN folder. Clear the Winhook file definition to rectify this problem. Refer to document ID 5998 for more information on Winhook.
The hard drive has run out of available space (refer to document ID 5984).
The shortcut for Control or Aloha Manager includes the REMOTE variable or the command line variables for Control Server include the REMOTE variable. Among other functions, the REMOTE variable (refer to document ID 6318) instructs Control or Control Server to not automatically search for new dated folder to grind. Verify the REMOTE command line variable does not exists in the command line for any shortcuts to Control (versions 4.4x and lower), any shortcuts to Aloha Manager (versions 5.0x and higher) or in the Windows registry command line for Control Server (refer to document ID 6217).
The transaction log or a database file (DBF or RDB) is corrupted. If the transaction log appears to be the corrupted, use the fixlog utility (refer to document ID 5982) to repair the log. If a corrupt .DBF file (in non-RDB systems only) appears to be the root of the problem, try using the same .DBF file from a previous day's folder. Backup the possibly .DBF file and copy the same .DBF file from the previous day's folder and retry the grind process. Ensure the .DBF file in the NEWDATA and DATA folders is not also corrupt. If the system is using an RDB and the RDB is corrupt, consult your database engine's user manual for help repairing a corrupt database.
A NOGRIND file exists in the Store's folder (RDB systems only). The most common reason for the grind process to fail in an RDB system is the existence of a NOGRIND file in the store's folder (STR00001). The grind process does not initialize if a NOGRIND file exists. The NOGRIND file may exist because of human intervention or Control or Control Server may have created it because of problems in the grind process. Either way, remove the flag and see if the grind process performs properly. If the grind process errors out three times, it will recreate the NOGRIND file. The Debugging-Output-Files (debouts) created by the grind process should provide an adequate explanation of the problem. Refer to document ID 6104 for more information on debouts.
'Disable Auto-Grind and Summarize' is enabled in Maintenance/Options/BOH Controls or Aloha Manager/Maintenance/Store Settings/System/Aloha Settings. You should always leave this option disabled.
Control or Control Server is hung up waiting for a Winhook batch file to complete. Although Control and Control Server do not monitor the success of the commands included in the Winhook batch file, they do wait for the batch file to complete. Control and Control Server do not continue with other tasks (such as grinding dated folders or initializing the Winhook batch file for other dated folders) until the current Winhook batch file completes. If the batch file from the previous Date-of-Business (DOB) pauses or hangs indefinitely, then Control or Control Server will not initialize other tasks. If you have registered Control Server using a specific user login rather than the built-in Windows system account, then the batch file does not interact with the desktop, and you cannot verify the Winhook batch file's completion or see any errors (including errors while printing reports). In this case, you can view the current processes in Windows Task Manager and close the CMD.EXE process if it is active (ensure that the CMD.EXE process does not represent another task besides Winhook).
If you have Control Server configured to log in with a specific user rather than the built-in Windows System account, ensure that the login has administrative privileges.
Ensure that you do not have a file or folder in the Aloha Bin folder that is labeled Grind or Grindq (no file extension).


If, for whatever reason, the site is ready to open for business but the FOH terminals are still waiting for the previous day to grind, you can 'trick' the Aloha application software into thinking it has successfully completed the grind process for the dated folder by manually creating the GNDDBF30.XXX file using the DOS ECHO command. The following line is an example of this:



ECHO 1 > %IBERDIR%\20000112\GNDDBF30.XXX



This is a temporary fix for use in an emergency and does not replace the actual grind process. After you have fixed the problem, delete the GNDDBF30.XXX and WINHOOK files from the dated folder.

SuperSites not Grinding Dated Folders
If a SuperSite successfully grinds a store's data folder during the current day but does not grind the dated folder following the EOD process, then verify that the TERMSTR is configured properly in store maintenance. The grind debouts will show how the TERMSTR that is currently configured.

Debugging Variables
Variable DEBUG

Description
Generates extra debugging information in the Debout files.

System Variable Example
N/A

Command Line Example
GRIND.EXE /DEBUG




Variable DEBUGCONVERTLOG

Description
Generates additional debug information in the debout files when converting a transaction log, and it is used with the CONVERTTRANSLOG function. Has the same effect as the DEBUGCONVERTTRANSLOG variable.

System Variable Example
N/A

Command Line Example
GRIND.EXE /DEBUGCONVERTLOG /CONVERTTRANS.LOG





Variable DEBUGCONVERTTRANSLOG

Description
Generates additional debug information in the debout files when converting a transaction log. This variable is considered true regardless of the assigned value. If this variable is not desired, completely remove it.

System Variable Example
SET DEBUGCONVERTTRANSLOG=TRUE

Command Line Example
N/A





Variable DEBUGGRINDMANAGER

Description
Generates additional Grind Manager debugging information in the debout files. Existence of the variable is all that matters. This variable is considered true regardless of the assigned value. If this variable is not desired, completely remove it.

System Variable Example
SET DEBUGGRINDMANAGER=TRUE

Command Line Example
N/A





Variable DEBUGGRINDSTORE

Description
Provides additional Store grinding debugging information in the debout files. Used only with SuperSites. This variable is considered true regardless of the assigned value. If this variable is not desired, completely remove it.

System Variable Example
SET DEBUGGRINDSTORE=TRUE

Command Line Example
N/A





Variable DEBUGGRINDTHREAD

Description
Provides additional grind thread initiation debugging information in the debout files. This variable is considered true regardless of the assigned value. If this variable is not desired, completely remove it.

System Variable Example
SET DEBUGGRINDTHREAD=TRUE

Command Line Example
N/A





Variable DEBUGMERGETRANSLOGS

Applications
GRIND.EXE, GRINDQ.EXE

Description
Generates additional debugging information in the debout files when merging transaction logs.

Command Line Example
GRIND.EXE /DEBUGMERGETRANSLOGS



Regrinding Dated Folders
If you need to regrind a dated folder, you can use either use the Regrind Subdirectories utility in Aloha Manager or you can manually grind each dated folder from a command line.



If you are using the Regrind Subdirectories utility, all database and transaction log conversions are performed automatically without any user input. Open Aloha Manager, select Utilities/Regrind Dated Subdirectories, select the dates to regrind, set Active to 'On', set Num Grinds to '1' and click Done. Refer to the Aloha QuickService or TableService User Manual for more information on the Regrind Subdirectories utility.



The Aloha application software stores the Regrind Subdirectories utility configuration data in the \SQL\SQL.INI and the list of dated folders to regrind in REGRIND.DBF.



In versions, 5.2.7.165 through 5.2.7.x, and 5.2.8.57 and higher, the Regrind Subdirectories utility creates a NOREGRIND flag in the dated folder if it is unable to regrind it. The enables the Regrind Subdirectories utility to move on to the next dated folder in the list. When this occurs, the dated folder is noted as 'Noregrind' in the Regrind Subdirectories utility, and you can reselect the dated folder in order to attempt to regrind it again.



If you are regrinding the dated folders in a site using an RDB, you can place a REGRIND flag in the Store folder in order to override the NOGRIND file (if it exists). If you are performing an upgrade, this enables you to upgrade and regrind dated folders, even if you do not yet want to upgrade and grind current data.

Manually Grinding Dated Folders
To manually grind a dated folder from a command line, open a command line and navigate to the BIN folder. The command line is GRIND.EXE followed by /DATE, and the name of the dated folder to grind. For example, use the following command line:



GRIND.EXE /DATE 20000112



Use DATA as the date to manually grind the current day's transactions. You can also use this command line in batch files. Refer to document ID 6613 for more information on command line variables.

Repair a Log Using Grind in Aloha Versions 5.3.12 and Higher
Grind will automatically detect the log version and repair any transaction log from Aloha version 4.0x and higher. If the transaction log is from an older version than the grind, grind will upgrade the transaction log prior to repairing it. Unlike Fixlog.exe (refer to document ID 5982), which requires a different application file for each version of transaction log, the single grind application will work for all versions of transaction logs from 4.0x through the version of grind.



To repair a corrupt log for the current day's business, stop the FOH on all terminals, rename the Trans.log to BadTrans.log, open a command prompt and navigate to the Data folder on the file server. Use Grind.exe or GrindQ.exe to repair the transaction log on the file server using the following command line:



..\BIN\GRIND.EXE /FIXLOG BADTRANS.LOG



Grind does not alter the original transaction log (renamed BadTrans.log), but, instead, creates a new transaction log labeled Fixed.log. Once you repair the log, you must rename Fixed.log to Trans.log and restart the FOH terminals.



To repair a corrupt log for previous days business, open a command prompt and navigate to the dated folder on the file server, repair the transaction log in the dated folder using the following command line, and then manually regrind the dated folder:



..\BIN\GRIND.EXE /FIXLOG TRANS.LOG



Grind does not alter the original transaction log, but, instead, creates a new transaction log labeled Fixed.log. Create a backup copy of the original transaction log and rename Fixed.log to Trans.log.

Extended Information
Remote copies of the non-RDB BOH use the RUNGRIND folder to start the Grind process for the current day's data. Refer to document ID 6338. This does not apply to systems with a RDB database.