ClenUpPF for PCBoard-Fido (Caller logs) (Clean Up PCBoard-Fido) ================================================================= ClenUpPF does not run without the registration of StatusPF! ClenUpPF was written to reduce the size of the Caller log(s) to speed up the running of StatusPF as well as reducing the size of the Caller log(s) for editing, etc. This program is written to be run in conjunction with my StatusPF 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: CLENUPPF.EXE.......... PCBoard Caller log reduction utility CLENUPPF.DOC.......... Instructions for running ClenUpPF 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 STATUSPF.EXE.......... Actual program STATUSPF.DOC.......... Instructions for running StatusPF STATUSPF.CFG.......... Sample configuration file STATSPF2.CFG.......... Sample configuration file STATSPF3.CFG.......... Sample configuration file ARCHIVE.TXT........... This list of files E-MAIL.TXT............ Current e-mail address for author ******* WARNING ******* A word of caution: Because garbage can get into any/all logs it is possible to have ClenUpPF chop off your log with an invalid end of file marker. That is the garbage can contain a "R" and ClenUpPF 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: CLENUPPF [path]CALLER [path][OTHER.CFG] Where Caller is your OTHER.CFG) is the name of your StatusPF configuration if you are not using 'STATUSPF.CFG' for the name of the configuration file(s). If you do not supply the name you use ClenUpPF aborts if it cannot find the default STATUSPF.CFG file. For best results ClenUpPF should be run before StatusPF. That way on the day of the rollover the LOG(s) are at their smallest possible size. If you run ClenUpPF 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 ClenUpPF on your previous log to remove the last day's activity. To do this you would unarchive the rollover archive, run ClenUpPF 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. ClenUpPF 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 only the repetitive conference information. It then writes out current data and then import and export information for each conference with running totals. 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 ClenUpPF 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 ClenUpPF everyday to reduce the size of your Caller 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. See below for details. If your hard drive space it not at a premium or speed is not critical then you really do not have to run ClenUpPF or of course you want all information to remain in your Caller log(s). The main savings on time, both ClenUpPF and StatusPF, would be gained the most near month's end. It takes StatusPF time to read in and process logs when they are larger. Lines can reach many thousands of lines more than a Caller log without the Fido information. What ClenUpPF 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 existing Caller log information and then 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 normal activity, then the totals per conference, in sorted order, then the start of the current day's activity (unaltered). ClenUpPF 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 ClenUpPF does nothing and exits immediately. StatusPF then does the rollover during it's own activities. If you have some other procedure that does a rollover on your Caller log(s) it should be performed before you run both ClenUpPF and StatusPF. My program DoCaller is a stand alone program that is run daily and rolls over your Caller log only on the 1st day of month. See HUCKABEY.TXT for details on, or getting a copy of my software. Regardless of what is deleted the current day's activities are not altered in any way (unless premature End Of File marker). What follows is what is removed from the Caller log(s) besides condensing the Fido Exports and Imports: <- At Position 1: ' ' (any line starting with 24 spaces) <- At position 7: Event Exporting Line was busy Packet POLL (POLL) Private Sending netmail <- At Position 18: Removing POLL Adding POLL Beginning FIDO Message Export Ending FIDO Message Export Beginning FIDO mail import Ending message import Beginning NETMAIL export Ending NETMAIL export -> Lines ending with ->: from this packet **** also following list #1 (per sample Caller log) **** <- At position 7: Carried dropped EMSI Sent AKA Sent EMSI Received emsi Connected to In receive In state Incoming connection Sending Emsi send emsi Remote AKA Beginning mail Shelling to End of mail <- At Position 18: Disconnected from Removing Sending EMSI Dialing CONNECT Nothing to send Beginning mail run Beginning incoming mail transfer Ending mail run -> Lines ending with ->: reque received requested duplicate ->Lines containing<-: -> bps <- sent **** end of list #1 (per sample Caller log) **** Consecutive duplicated lines of asterisks are also removed. User information is not altered unless one of the above happens to turn up in their sections, even then no harm done since this is non-vital information. Lines removed may be adjusted from time to time as I receive feedback from users. I do need you input! Hard to know what to remove and what not to remove. I can only base line removal on my sample log(s). I tried not to remove any user information 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 STATUSPF.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 ClenUpPF. 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 CLENUPPF.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 CLENUPPF.EXE from. ClenUpPF must find a valid and registered copy of STATUSPF.EXE either in the current directory, path or set in the environment according to the StatusPF documentation. ClenUpPF reads in the STATUSPF.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 StatusPF on their system. This is in violation of my copyrights. This program can only be run in conjunction with STATUSPF.EXE. CLENUPPF.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 StatusPF, which includes making ClenUpPF operational. See STATUSPF.DOC for details. James Huckabey 3621-A Fraser Street Bellingham, Washington 98226-2473 U.S.A. (360) 671-2868 (voice, Pacific) I do have a US Robotics HST DS 14.4 v32, v42, v42Bis modem!