CleanUpQ for QFront (QSCAN) ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ CleanUpQ does not run without the registration of StatusQ! CleanUpQ was written to reduce the size of the QFront log(s) to speed up the running of StatusQ as well as reducing the size of the QFront log(s) for editing, etc. This program is written to be run in conjunction with my StatusQ program and is not to be run as a separate program. To do so is in violation of my copyright. This archive should contain the following files: CLEANUPQ.EXE.......... QFront log reduction utility CLEANUPQ.DOC.......... Instructions for running CleanUpQ DOORS.TXT............. Current list James Huckabey doors FILE_ID.DIZ........... BBS description file SOFTWARE.TXT.......... Information about shareware HUCKABEY.TXT.......... Current list of all James Huckabey software. READ.ME............... Update/changes information STATUSQ.EXE........... Actual program STATUSQ.DOC........... Instructions for running StatusQ STATUSQ.CFG........... Sample configuration file STATUSQ2.CFG.......... Sample configuration file STATUSQ3.CFG.......... Sample configuration file STATUSQ.LUP........... Sample networks line up file ARCHIVE.TXT........... This list of files ******* WARNING ******* A word of caution: Because garbage can get into any/all logs it is possible to have CleanUpQ chop off your log with an invalid end of file marker. That is the garbage can contain a " " and CleanUpQ believes that this is the end of the file and cuts off the log at this point. There is no way to program around this problem. Once the marker is found the file is set as the end and no way I can work out and over come a premature end of file marker. I am still trying to work this out. ******* o ******* Syntax: CLEANUPQ [path]QSCAN.LOG [path][OTHER.CFG] Where QSCAN.LOG is your QFront log file name. Where [path][OTHER.CFG) is the name of your StatusQ configuration if you are not using 'STATUSQ.CFG' for the name of the configuration file(s). If you do not supply the name you use CleanUpQ aborts if it cannot find the default STATUSQ.CFG file. For best results CleanUpQ should be run before StatusQ. That way on the day of the rollover the LOG(s) are at their smallest possible size. If you run CleanUpQ a second time on a log produced by rollover it does a hasty exit if the first date found is the current date. No harm done! After rollover you can run CleanUpQ on your previous log to remove the last day's activity. To do this you would unarchive the rollover archive, run CleanUpQ on your log(s) and rearchive the logs. This way the log only contains conference names and Import / Export totals with header (start date) and trailer (end date). If you were viewing previous activity this would make it much easier to read and total up. It would be possible to make a "Previous Month's" activity bulletin out of the rolled over log. At least the data would be all there and compacted. CleanUpQ must be in current directory or somewhere in your path statement. You may include a full name and path to your log file. It removes everything but the current activity and writes out the current import and export information for each conference. At the end of activity the program displays the starting and ending log file sizes, starting and ending line count. The process may be lengthy depending on the size of your log. It should be run daily. All that is needed to run CleanUpQ is as much free space on the log file drive as the size of the log or the program does not create a new log. If your BBS system is critical on free space you can run CleanUpQ everyday to reduce the size of your QFront log(s). The program removes unneeded lines and does nothing to the current day's portion of the log. It stops processing data when it finds the log date equal to the system date. If your hard drive space it not at a premium or speed is not critical then you really do not have to run CleanUpQ. Or of course you want all information to remain in the log. The main savings on time, both CleanUpQ and StatusQ, would be gained the most near month's end. It takes StatusQ time to read in and process logs when they are larger. Lines can reach 18,000 or more on a system with a lot of conferences and/or messages. What CleanUpQ does is read in all lines separating out the conference names and number of messages per conference (running total for each conference). When the program finds the date in the log matches the system date, or reaches end of log, it starts writing out the conference names and total messages per conference to a new log. If it has found today's date then it appends the rest of the current data to the new log. When finished it erases the old log. This leaves you with a new log showing only the totals per conference, in sorted order, then the start of the current day's activity (unaltered). CleanUpQ only needs to be run once per day. If you run it additional times nothing is changed in the log although it does keep writing out a new one. Any additional information written to the log will not be processed until the next day. If the month rolls over in the log CleanupQ does nothing and exits immediately. StatusQ then does the rollover during it's own activities. Regardless of what is deleted the current day's activities are not altered in any way (unless premature end of file marker). Special Bulletins Showing Totals Each Conference It is possible to make a "Previous Month's" activity bulletin out of the rolled over log(s). At least the data would be all there and compacted. All you have to do is make a special STATUSQ.CFG file with the name of the bulletins for these special monthly Bulletins. You could do one each month for the previous month. The bulletin for the Last Import could just be written to the current directory and not used. For a full month the Bulletins would have something like 01-01-95 to 01-31-95 for the time period as this would be the dates in a log for January 1995. Of course the above would work even if you did not run CleanUpQ. This Program If you don't like the program please write to me and explain why. Send me any suggestions you might have. If they enhance the overall program I will try to incorporate part, some, all, in the next release. Errors Errors are written to the current directory in a file called CLEANUPQ.ERR. If the file already exists additional errors are appended to the end of the file. It may be deleted after you have made note of any errors. It's existence it not required by the program. Current directory is wherever you call CLEANUPQ.EXE from. CleanUpQ must find a registered copy of STATUSQ.EXE either in the current directory, path or set in the environment according to the StatusQ documentation. CleanUpQ reads in the STATUSQ.CFG file, or optional command line configuration file. I did this because some people might want to run this program on their log file without having StatusQ on their system. This is in violation of my copyrights. This program can only be run in conjunction with STATUSQ.EXE. CLEANUPQ.EXE or any of the other files in the archive may not be distributed in any form other than the original archive and unaltered. Please support my efforts and register StatusQ, which includes making CleanUpQ operational. See STATUSQ.DOC for details. James Huckabey 3621-A Fraser Street Bellingham, Washington 98226-2473 U.S.A. (360) 671-2868 (voice, Pacific)