Since I added alot of entries to the CALLS.CNF file, I thought it was time I wrote a document to explain them in more detail. I will also give you an explanation of the entries that Sam Smith created. Almost all entries have a default value and if there is not an entry or you comment out the entry then the default will be used. The entries may be made in any order you like and if you duplicate one, the last one will be the one to take affect. ON, YES and TRUE are all acceptable states for the below options and any other answer will be considered the same as OFF, NO and FALSE. *--------------------------------------------------------------------------- ;number of nodes to scan (1=single node mode) - Default = 1 NODES 1 This is the number of nodes that you want to scan and will cause a number to be appended to the INFILE name and each file ot be processed in sequence as described under INFILE. If you only run a single node then set this to 1. If you run a single node but have PCBoard set for multiple nodes so that the CALLER file is named CALLER1 then you will need to specify CALLER1 under OUTFILE and set NODE to 1. *--------------------------------------------------------------------------- ;list of nodes (in order of desired scan, NODES should equal the number of ;nodes included in the list. If no list provided then all nodes will be ;scanned from 1 to NODES) ;NODES 3 ;NODELIST 5 3 1 This allows you more control over scanning multi-node setups. You can easily scan only some of your nodes without having to run the program several times using a CALLS.SAV file to collect the data. Try to make sure that NODES matches the number of of entries in the list, although provisions have been made to ensure that CALLS will not care. If there are more entries they will be ignored, and if there are less entries CALLS just ignore the fact, just by being careful, you will save yourself some headaches trying to figure out why some nodes don't show up. *--------------------------------------------------------------------------- ;full name of caller input file (or NUL) - Default = CALLER INFILE C:\PCB\MAIN\CALLER This is the file to be read and processed. If you are running a single node and specify NODE 1 then this will be the complete filename used. If you specify NODE 2 (or higher) then CALLS.EXE will append a '1' to the filename and process that file, then append a '2' and process that, etc.. until it has processed all CALLER files uo to the value you assign to NODE. *--------------------------------------------------------------------------- ;output file to produce - Default = BLT99 OUTFILE C:\PCB\GEN\BLT11 This is the file to send the output to. If you specify BOTH or ANSI for REPORTTYPE then a 'G' will be appended to the filename and an ANSI report generated. If you use a full 8 character filename then when the 'G' gets appended DOS will still interpret the same filename and you will only get 1 report in ASCII if you specified BOTH unless you specify a '.' at the end of the filename in which case CALLS.EXE can properly append a 'G' to it. *--------------------------------------------------------------------------- ;input file of a Header to precede report - Default = NUL ;HEADER C:\PCB\GEN\BLT11.HD This file (if it is found to exist) will be read just prior to outputing the report and will be output to the report. It will be output just after the @CLS@ if you have a '*' as the first character of REPORTS. If you specify ANSI or BOTH then a 'G' will be appended to the filename and be used for the ANSI version of the output (note the same notes regarding the appending as above). If the 'G' version does not exist, then no header will be used for the ANSI version. *--------------------------------------------------------------------------- ;file for saved history information (or NUL) - Default = CALLS.SAV SAVEFILE CALLS.SAV If not set to NUL, then this file will be read before beginning the processing of the INFILE(s) and saved after writing the OUTFILE. This allows reading the CALLERS file each day and then discarding it. The totals will be accumulated in CALLS.SAV each time. Also if you like separate bulletins to be generated for the different reports, you can have multiple .CNF files and in the first specify an INFILE and a SAVEFILE and the first OUTFILE. Then in additional .CNF files set for different REPORTS, you can specify NUL for INFILE to indicate no file processing be done, and reports will be generated from the totals in the SAVEFILE which allows for quick generation of reports. Change the OUTFILE for each report to be generated. *--------------------------------------------------------------------------- ;Don't Update the CALLS.SAV file - Default = NO ;READONLY YES This makes it easier to keep a Year-To-Date CALLS.SAV file that is updated at the end of each month without requiring you to delete the CALLERS file after scanning it with CALLS. Normally when using a CALLS.SAV file the information collected from reading the CALLERS file is added to the CALLS.SAV file and the new totals are written out to the CALLS.SAV file. If you don't delete the CALLERS file at that point and rescan the same CALLERS file, information will be duplicated. I start a new CALLERS file each month and keep a Y-T-D CALLS9x.SAV file that I update only prior to beginning the CALLERS file by running a .CNF file with READONLY set to NO. Then thru the month I run with a .CNF file with READONLY set to YES so I read the Y-T-D CALLS9x.SAV file but I don't update it everytime I read the same months worth of CALLERS file. *--------------------------------------------------------------------------- ;report subtitle (for Report A, Systems Statistics) ;SUBTITLE My BBS Activity Report If defined, this prints after the report title for the Systems Statistics Report (A). *--------------------------------------------------------------------------- ;file for outputting any unknown line for study (or NUL) - Default = NUL UNKNOWNFILE UNKNOWN.TXT New to CALLS 14S23D is the addition of symbols to the end of the data lines written to the UNKNOWN.TXT file. These will identify Unknown, CatchAll and Junk lines (both normal and within Doors) and any lines not marked are known lines being written related to DOORS. (ie. DOORREPORT or UNKNOWNDOORREPORT) This file is for troubleshooting and was used by me in generating data. It allows for sending certain lines read to a file given the following conditions: *----- ;include all unknown lines in unknown file - Default = YES UNKNOWNREPORT YES Any line that is not specifically recognized by CALLS.EXE for processing will be dumped to the file specified in UNKNOWNFILE. This allows recognizing what changes might need to be made to CALLS.EXE for future enhancements. It can also allow you to spot errors in setup. I intentionally do not recognize certain error messages that PCBoard generates, so if they pop up in the UNKNOWNFILE I can see them right away, whereas I might miss them when checking the CALLERS file. *----- ;include all Junk lines in unknown file - Default = NO ;junk lines are those recognized by CALLS and skipped over. JUNKREPORT YES Certain line are recognized by CALLS.EXE but not processed in anyway. They are only recognized to prevent them from being written to UNKNOWNFILE. If you want to see what they are, set this to YES. If there is some data that you feel should be reported in some useful way, let me know. *----- ;include all Door Unknown, Catchall and Junk lines in unknown file ;This refers to only those doors known to CALLS - Default = YES DOORJUNKREPORT NO This is identical to JUNKREPORT, CATCHALLREPORT and UNKNOWNREPORT but controls those type of entries only while in a door and only for the Doors that CALLS has specific reports for. This allows for finding missed or new lines that a door is generating that CALLS does not know yet. *----- ;include all Catchall lines in unknown file - Default = NO ;Catchall lines are those recognized by CALLS in the Catchall routine which ;picks up lines missed by the normal scan (some just have to be done this way) CATCHALLREPORT YES Some lines (like conferences joined) just had to pass thru the catchall routine. Those that had to pass that way will not reported by setting this to YES. Others that were in the routine, that I could not figure out why they were there as they were already trapped for previously, will be reported if this is set to YES and they get caught in the CATCHALL routine. If they don't don't ever show up then I will remove those lines of code. The way processing is done in order to speed up the recognition of the lines is to first process the first (position 7) character of the line and then scan for data in in a CASE statement based on the first character, if the line is not recognized then it passes to the CatchAll routine. This is conferences joined have to be caught in the catchall routine. The conference name is the first thing on the line so the first letter could be anything. *----- ;include all Door lines in unknown file - Default = NO DOORREPORT NO If set to YES then everything from the OPENED DOOR (xxxxx) AT HH:MM to the BACK TO DOS AT HH:MM will be sent to the UNKNOWNFILE (if the line is unrecognized then it will be echoed twice if UNKNOWNREPORT is set to YES). This allows for troubleshooting the door reports or gathering info for building your own report. *----- ;include all Unknown Door lines in unknown file - Default = YES ;This refers to all Doors that are not known to CALLS. UNKNOWNDOORREPORT NO This is identical to DOORREPORT but will send data only on Doors that CALLS does not know (those it does not have a specific report for). It is only active when DOORREPORT is not, as ALL Door lines go to the report when DOORREPORT is set to YES. This will allow for finding more doors that justify a report. *----- ;List of Doors for CALLS to consider known. (separate doors with '/') ; Lines must not exceed 80 characters, use multiple lines which will be ; added together up to 255 characters. (end previous line or begin next ; line with '/') ;KNOWNDOORS REMOTE/LOTTO This allows you to list Doors which you don't want UNKNOWNDOORREPORT to include. The only purpose of including a door here is to stop CALLS from writing lines to UNKNOWN.TXT when UNKNOWNDOORREPORT is set to YES. Any Door that matches one named in the list will not generate lines. Lines must be kept under 80 characters per line, but multiple lines are allowed as long as each additional line starts with the '/' character (or the previous line ends with a '/' character). The total length is 255 characters (about 3 lines full). With 15s1f you may now have two strings of 255 characters. You should try to group them so the first 4 lines add up to as close to 255 characters (including the '/' characters), and then start another section of lines. *--------------------------------------------------------------------------- ;List of Doors for CALLS to consider chat doors. (separate doors with '/') ; Same line restrictions as KNOWNDOORS ;CHATDOORS TALK2ME/CHATDOOR/HELLO! This expands on the new code that counts Doors opened with the text 'CHAT' in them to be counted as Node Chats by allowing a list of doors that are Chat Doors and should be counted as a Node Chat. Time spent in Door will also be counted as Node Chat Time as well as Time Spent in Door. Multiple lines are allowed. *--------------------------------------------------------------------------- ;list of reports to produce from the following list ; Default = A+N#STB~CXO!RPD{E[><]\VU^-F=GY1Y2Y3Y4Y5Y6Y7Y8Y9Y10Y11HIJKL&::1M ; ; A - System Statistics B - Graphic Modes ; C - Baud Rates D - Hourly Usage ; E - Conferences Joined F - Bulletins Read ; G - Doors Opened H - Download Protocols ; I - Download Efficiency J - Upload Protocols ; K - Upload Efficiency L - Batch Sizes ; M - Files Downloaded N - Security Statistics ; O - Security Level Counters P - Connect Type Analysis ; Q - Free Downloads *Not PCB* R - Minutes Used by Security ; S - Sysop Statistics T - User Statistics ; U - User Messages V - Conf Messages ; W - Event Report X - Language Report ; Y#- Door Report (needs a no.) Z - Insert a Blank Line ; @ - Insert a @MORE@ Prompt $ - Insert a @PAUSE@ Prompt ; % - Insert a @WAIT@ Prompt * - Insert a @CLS@ ; | - Insert a FormFeed . - Do Nothing (just a space filler) ; ! - Last Called In Report # - Message Statistics ; = - Time Spent in Doors Report ^ - User Uploads ; - - Callers Hanging Up & - Caller ID Report ; + - File Transfer Statistics ~ - Logoff Statistics ; ( - Voting Issues ) - Voting Comments ; _ - Page Door Reasons / - Short Bulletin ; > - Downloads in Conferences < - Uploads in Conferences ; [ - Time Spent in Conferences ] - File Scan in Conferences ; \ - Conference Reports { - Daily Usage ; :#- PPE Report (takes a no.) ; ; Door Reports are followed by number - ie. Y6 Y11 etc ; 1 - InstaReg 2 - PCBVerify ; 3 - Callback 4 - Depository ; 5 - MailDoor (Generic) 6 - QMail ; 7 - MarkMail 8 - User Definable ; 9 - Voter Plus 10 - Swop ; 11 - PCBPage & Emergency Pager ; ; PPE Reports are followed by number - ie. :1 :2 etc ; 1 - EDSBack PPE alone - Misc PPE Report ; REPORTS *A+ZX#ZBZ~NSZTCD{O!RPE[><]\VU^-F=GY1ZY2Y3ZY4Y5ZY6Y7ZY8Y9Y10Y11HIJKL&::1MW% This controls which reports and in which order they will be issued to the OUTFILE. If a '*' is placed as the first character then a @CLS@ will be sent to the OUTFILE before anything else. Each character controls a single report except for Y which requires two-three characters (Y1 ... Y11) and : which requires one-two characters or (: ... :1). *--------------------------------------------------------------------------- ;Exclude accumulation of Data for graph reports - Default - None ;Allowable entries are CEFGLMOPQRUVWX!=^-&~()_[><] ;REPORTEXCLUDE CPX This allows you to prevent the collection of data which you will not be using which can offer a slight speed improvement and most importantly, reduce the size of the SAVEFILE when accumulating data over long periods of time. Note: If you exclude any report data, then it will not be accumulated and saved in the SAVEFILE and you will not be able to report on it in the future without rescanning old CALLER files. This is also necessary to conserve memory. If you are running out of memory during CALLS and are not using a section of the reports, then excluding it will help reduce memory requirements. *--------------------------------------------------------------------------- ;Action to perform after each section ;Allowable entries are (Z@$%*) REPORTACTION Z%* After every report control character in REPORTS, the string in REPORTACTION will be processed UNLESS the next character in REPORTS is one of the characters (Z@$%*.) in which case REPORTACTION will not be processed for that report. This allows you to perform a @WAIT@ and @CLS@ after EVERY report, yet prevent the action from occurring on certain reports that you want to combine. The '.' is a do nothing character that is used to stop the REPORTACTION without the need to do anything else. The others are described in REPORTS. *--------------------------------------------------------------------------- ;Type of report to output, ASCII, ANSI, BOTH or PCBOARD - Default - BOTH REPORTTYPE PCBOARD This allows you to control what type of report format you output. ASCII is a straight text file. ANSI is a colorized version using ANSI escape sequences, and a 'G" is appended to the OUTFILE and HEADER filenames. BOTH will cause both an ASCII and ANSI report. A setting of PCBOARD will cause a single report (with no 'G' appended to filenames) to be output using @Xnn color codes. In all cases the reports will be generated with @MORE@, @PAUSE@ and @WAIT@ prompts if the are specified. For ASCII and PCBOARD, a @CLS@ will be used but for ANSI a [2J sequence will be issued. *--------------------------------------------------------------------------- ;peak hours to report ; 11111111112222 ; 012345678901234567890123 ;PEAK YNNNNNNNNNNNNNNNNYYYYYYY ;determine peak 6 hours automatically (or number of hours specified) ;PEAK AUTO 8 PEAK AUTO This will be used to control which times are used when calculating the Peak Utilization %... xx.x line. The hours marked with a 'Y' will be included in the peak calculation. If set to AUTO then CALLS will determine the peak 6 hours automatically. You may also specify the number of hours to report as peak after AUTO, ie. AUTO 8 (Note: this does not refer to a consecutive number of hours to be considered as a peak time block. The hours will be sorted by value and the top number of hour specified will be flagged as PEAK hours.) *--------------------------------------------------------------------------- ;shorten graph to just percentage used - Default = no ;NO/YES/or the minimum percent to start at SHORTENGRAPH 50 If set to NO then the full hourly usage chart will be generated. If set to YES then only the portion that is needed (the maximum usage) will be generated. If set to a value (0 to 100 in multiples of 5) then either the maximum usage or the value set will be generate, which ever is higher. This allows you to limit the number of blank lines that are generated by keeping the report to just those lines needed without shrinking the report too small to look good. If EXPANDGRAPH is also set to YES then SHORTENGRAPH will only have an affect if the chart is below 20 in which case CALLS will attempt to retain as many lines as SHORTENGRAPH is attempting to maintain (ie. if set to 80 then 16 will be the minimum number of lines.) *--------------------------------------------------------------------------- ;expand graph to full 20 divisions with variable steps - Default = no ;EXPANDGRAPH YES If set to NO then the chart will step by 5 and depending on SHORTENGRAPH be longer than needed or shortened. If set to YES then the chart will always be 20 lines long but the step value will vary as needed to make it so. Since the step value might be a decimal value but only integers are shown, the chart might skip numbers but should be pretty even. This allows those systems with smaller usage values to get a better resolution rather than waste the chart. The SHORT report format will not be affected. SHORTENGRAPH and EXPANDGRAPH will affect both the Hourly chart and the new WeekDay chart. *--------------------------------------------------------------------------- ;full name of Sysop or SYSOP SYSOPNAME GARY MEEKER This allows CALLS.EXE to recognize you as the SYSOP when reporting local or remote Sysop sessions. If you have PCBoard use your name then place that here or if you have it use SYSOP then specify SYSOP here. *--------------------------------------------------------------------------- ;Conference(s) to include in Conference Report ; up to 50 entries are allowed and are specified by NAME (Case sensitive) ; each entry may only specify one conference CONFERENCE Main Board This allows you to specify which conferences to report activity on. The activity is pulled from the data already collected in the Graph Report sections and REPORTEXCLUDE could cause the values to show zero if you have excluded a report from which this data is pulled (Reports E, >, <, [ & ]) *--------------------------------------------------------------------------- ;PPE Name(s) to ignore (just stops them from showing up in UNKNOWN.TXT) ; up to 50 entries are allowed and are specified by NAME (Case insensitive) ; each entry may only specify one ppe (don't include path) ;PPENAME DIR-L.PPE This is to stop entries from showing up in the UNKNOWN.TXT file or possibly being recognized and mis-counted in other sections of the report. It is designed to work with CALLER LOG entries that start with '!' usually resulting from replacing PCBTEXT entries with PPE's. It will also function with entries that start with 'entered ', 'exited ' or 'out of '. CALLS will also count all encounters with the .PPE's listed here in the new PPE report section. *--------------------------------------------------------------------------- ;First Name to Exclude from stats (RNET.EXE is always excluded) ; up to 10 entries are allowed (this is not for USER names!) ;EXCLUDENAME RNET.EXE This allows you to specify program names that generate logons that look just like a User from being included in the report or prematurely stopping the event timing. RNET.EXE is one such example is is already handled by CALLS.EXE and need not be specified here. You can have up to 10 entries and more will be ignored. *--------------------------------------------------------------------------- ;Full User Name to exclude from stats (User Messages Left, Uploads and ; Caller Hungup Reports). Up to 50 entries are allowed. ; Adding '*' as first character of name will flag User as a NetUser. ;EXCLUDEUSER GARY MEEKER This allows you to exclude Users from being included in the reports mentions above. If you are a HUB then you can include your NODE names from these reports or exclude yourself if you like. Flagging a User as a NetUser will cause messages left by this User to count as Net Mail instead of Mail Door messages. If NetUser is flagged and a message is left via PCBoard instead of a Door then the User Name will NOT be excluded and it will not count as Net Mail. *--------------------------------------------------------------------------- ;Conferences to exclude from stats (Bulletins Read, Conferences Joined and ; Time Spent in Conference, Conferences Uploaded to, Conferences Downloaded ; from, Conference Files Scanned & Conference messages left) ; Up to 50 entries are allowed and are specified by NUMBER ;EXCLUDECONFERENCE 12 This allows you to exclude a conference from showing up in any of the reports. Exclusion is done by conference number though instead of name to simplify the program. The conferences are counted but will not show up in the lists. *--------------------------------------------------------------------------- ;Security Levels to exclude from stats (Number of Calls and Hours Used) ; Up to 50 entries are allowed. ;EXCLUDESECLEVEL 120 This allows you to exclude a security level from showing in any of the reports. *--------------------------------------------------------------------------- ;Door to exclude from stats (Doors Opened and Time Spent in Doors) ; Up to 50 entries are allowed. EXCLUDEDOOR REMOTE This allows you to exclude Doors from being included in the reports. Time spent in the Door and opening of the Door is still counted but the Door Name will not appear in the report lists. *--------------------------------------------------------------------------- ;Label given to the Doors that are excluded. - Default = Unlisted ;NONDOORNAME Unlisted All Excluded Doors are counted and Timed but are reported as a single entry. This variable allows defining that label. If set to a blank then they will not be reported and not added to the SaveFile at all. *--------------------------------------------------------------------------- ;Area Code for CALLER ID Report. If matched then is considered a Local Call. ; multiple Area Codes maybe included and must be seperated by '/' ;AREACODE 404/706 This is used in the Caller ID report. If the Area Code matches the one defined here, then the ID will be listed as a local call. Otherwise, it will be listed as a long distance call. *--------------------------------------------------------------------------- ;Caller ID type or phone number position on log entry - Default = 0 ;1-10 will search for key field as listed below: ;1 = 'NMBR = ' 4 = undefined 7 = undefined 10 = undefined ;2 = 'NUMBER: ' 5 = undefined 8 = undefined ;3 = undefined 6 = undefined 9 = undefined CALLERID 1 CALLERID 1 works with Supra 14.4/Fax #CID=1 format messages: CID: DATE = 0402 TIME = 2234 NMBR = 4049621788 CID: DATE = 0402 TIME = 2236 NMBR = P CID: DATE = 0402 TIME = 2238 NMBR = O The key to this setting is the 'NMBR = ' text and the number is expected to follow this. CALLERID 2 works with ZyXEL modems: CID: TIME: 04-02 22:34 CALLER NUMBER: 4049621788 CID: TIME: 04-02 22:36 REASON FOR NO CALLER NUMBER: PRIVATE CID: TIME: 04-02 22:38 REASON FOR NO CALLER NUMBER: OUT-OF-AREA The key to this setting is the 'NUMBER: ' text and the number is expected to follow this. For other modems (since I don't have them) you can set CALLERID to the position of the phone number on the line. Example: CID: 040222344049621788 CID: 04022236P CID: 04022238O So a setting of CALLERID 20 would be needed. The range would be 12 to 52 in all likelihood. As Sysops with Caller ID supporting modems report to me what the entries look like in the CALLERS file, I'll add support for them to CALLS. *--------------------------------------------------------------------------- ;Save filenames & counts in the history information file YES (default) or NO FILENAMES YES If you don't wish to report files downloaded then you can save alot of file space in the SAVEFILE by setting this to NO. *--------------------------------------------------------------------------- ;File mask of files to be ignored completely, wildcards allowed ; up to 10 entries are allowed (wildcard '#' matches any digit) FILTERFILES *.GIF FILTERFILES *.TIF FILTERFILES *.PIC FILTERFILES #####?.ZIP FILTERFILES #####?.CAP This allows preventing unwanted or sensitive filenames from being included in the files downloaded report. Wildcards are allowed and a special wildcard of '#' allows matching any digit to allow for filtering out .CAP files when using the Caller Number as the filename. They wouldn't show up in the report unless the same file was downloaded more than once (unlikely, unless you reset the Caller Number, but why include them in the total or SAVEFILE). Only 50 are provided for but if more are needed, let me know and I will increase that. *--------------------------------------------------------------------------- ;number of "User Messages Left" to report MAXUSERS 30 ;number of "User Uploads" to report MAXUL 30 ;number of "Callers Hanging Up" to report MAXHANGUP 30 ;number of "Conference Messages Left" to report MAXMSGS 20 ;number of "free downloads" to report MAXFREE 10 ;maximum number of conferences to report MAXCONF 20 ;maximum number of conference time spent to report MAXCONFTIME 20 ;maximum number of conferences downloaded from to report MAXCONFDLS 20 ;maximum number of conferences uploaded from to report MAXCONFULS 20 ;maximum number of conference files scanned to report MAXCONFSCAN 20 ;maximum number of bulletins to report MAXBLT 20 ;maximum number of doors to report MAXDOOR 20 ;maximum number of batch sizes to report MAXBATCH 5 These control how many entries are to be reported in each report. If specified then the report will show Top xx in the report header. If not specified then all entries will be reported. *--------------------------------------------------------------------------- ;minimum d/l's to include a file in report MINDL 2 This will control which filename get reported in the Files downloaded report. Only files downloaded as many or more times as the number specified here will be reported. *--------------------------------------------------------------------------- ;break points for d/l's (1-4) - Default = 2, 6, 12 & 24 ;This is relative to MINDL, ie. MINDL 2 means 0-4, 5-8, 9-14, 15-26 & 27+ ; * ** *** **** ;DL_LEVEL 3 18 DL_LEVEL L NN allows the breakpoint (L) to be set to a new value (NN). The value of L is 1-4 and NN is 1-32767. The Default breakpoints are 2, 6, 12 and 24 and is relative to MINDL. If MINDL is 2 (the default) the breakpoints would be 0-4 (none), 5-8 (*), 9-14 (**), 15-26 (***), and 27+ (****). Issuing DL_LEVEL 3 16 would change it to 9-18 (**) and 19-26 (***). The defaults would be the equivalent of: DL_LEVEL 1 2 DL_LEVEL 2 6 DL_LEVEL 3 12 DL_LEVEL 4 24 *--------------------------------------------------------------------------- ;redefine name of Conference 0 - Default = 'Main Board' ;CONFERENCE0 Main Board This allows defining the name of Conference 0 something other than Main Board in the reports for Downloads, Uploads, Files Scanned & Time Spent in Conferences reports. *--------------------------------------------------------------------------- ;redefine protocol names PROTOCOL A Ascii (Non-Binary) PROTOCOL X Xmodem (Checksum) PROTOCOL C Xmodem (CRC) PROTOCOL O 1K-Xmodem (Ymodem) PROTOCOL F 1K-Xmodem-G(Ymodem/G) PROTOCOL Y Ymodem (PCB Batch) PROTOCOL G Ymodem/G(PCB Batch) PROTOCOL D Ymodem (DSZ Batch) PROTOCOL H Ymodem/G(DSZ Batch) PROTOCOL Z Zmodem (DSZ Batch) PROTOCOL N None This allows you to specify the Text Name used in the report for each PROTOCOL. The letter following the PROTOCOL matches that of the associated Protocol you have defined in PCBoard. *--------------------------------------------------------------------------- ;redefine Door Names - (I,V,C,D,G,Q,M,U,O,S,P) ;corresponds to report - Y(1,2,3,4,5,6,7,8,9,10,11) ; ; A '/' may be used to separate Multiple Door Names for the Same Door ; (Note: No spaces allowed) ie. DOOR I INSTAREG/RENEW ; DOOR I INSTAREG DOOR V VERIFY DOOR C CALLBACK DOOR D DEPOSIT DOOR G MAIL/MAILDOOR DOOR Q QMAIL/QMAIL4 DOOR M MM-2/MM2/MARKMAIL DOOR U REGISTER DOOR O VOTE DOOR S SWOP DOOR P PAGE This controls the processing of doors recognized specially by CALLS.EXE. The default names are shown above and if you run the door under a different name, you must specify that here or it will not be accumulated in the reports. If you run the same door under multiple names, then specify each name here separated by a '/'. *--------------------------------------------------------------------------- ;Text to be added before the Security Level - Default = Level SECLABEL Security Level This allows you to define what text is added to the security level for the report lines. If you want just the Security level with no other text, then just include the line SECLABEL with no text after it. *--------------------------------------------------------------------------- ;Text to be added before the Security Level - Default = '' ;if blank then line will not be printed NOSECLABEL No Security Level This allows you to define what text is used to report caller entries with no security level. If undefined or defined as NOSECLABEL with no text after it, then this line will not be reported at all. *--------------------------------------------------------------------------- ;Maximum item length for variable length items - Default = 20 ; (variable length items are defined by ITEMLEN of -1) ; ;ITEMMAX 25 This controls the maximum length that will be used of a graph item when an ITEMLEN of -1 is specified for a report. *--------------------------------------------------------------------------- ;Item length for graphs, If set to -1 then will be set to longest item ;ITEMLEN C 10 ;ITEMLEN P -1 This controls the length that will be used of a graph item. This allows reducing the wasted space on the shorter reports and increasing the length of the graph bars themselves. It also allows increasing the defaults so the entire User Name would show if one exceeds the 20 character limit normally set in CALLS. The defaults are all 20 except for: 'C' is 8 'G', 'L' and '=' are 10 'E', 'V' and '&' are 15 The length used will actually be 1 less than set as there is 1 space at the front of all items. The parameter after the ITEMLEN is the Report Name as listed in REPORTS and the last parameter is the length to be set. Setting a value of -1 will cause the longest length encountered to be used as long as ITEMMAX is not exceeded. *--------------------------------------------------------------------------- ;Report Title for any Report ; Generic Mail Door - Default = Your Mail Door ;User Definable Door - Default = Any Door ;REPORTTITLE A Here's a Title REPORTTITLE Y5 Cam-Mail Door REPORTTITLE Y8 Register/XferStat/BList Doors This allows you to redefine the Header text of any of the reports you would like to. If you want a more descriptive Header than provided, you can define your own. The parameter after the REPORTTITLE is the Report Name as listed in REPORTS and the last parameter is the title to be set. *--------------------------------------------------------------------------- ;Report Header for any Report ;the file specified will be copied to the report after the Title ;REPORTHEADER U C:\PCB\GEN\USERMSGS This allows you to define a file to be added to the report for each section of the report. It will be added right after the title in place of the blank line and if blank lines are desired they need to be added to the file. The parameter after the REPORTHEADER is the Report Name as listed in REPORTS and the last parameter is the filename. *--------------------------------------------------------------------------- ;Report Text for Reports (ANSU+# and Y1-Y10) items (1-25) ;REPORTTEXT A 2 Number of Calls Rcvd This allows you to change the text on the fixed reports. REPORTTEXT must be followed by a space, then the Code for the report, then a space, then the item number to define, then 'a' space, then the text. Any additional spaces before the text are considered to be part of the text. Using a CALLS.SAV file and NUL for the input file, you can quickly generate a report to see what it looks like. The item numbers start at 1 and count left to right. For the Door reports (Y1-Y11), items 1 & 2 are fixed as are the last 3 items in each report. These items can be changed by using the Code ? for the report code and item numbers are 1 to 6 as follows: 1 Door Executed.......... 2 Time in Door........... 3 ....................... 4 Caller Dropped Carrier. 5 Keyboard Timeouts...... 6 Logged Off in Door..... Changing these will change ALL reports that use them. Likewise, the PCBVerify Report (Y2) and CallBack Report (3) use the same text so changing one changes the other (except for items 7 & 8). Also, the three Mail Doors (Y5, Y6 & Y7) use the same text so changes to any one will change all three. Most text will never need changing but for those who would prefer different wording than is originally coded into CALLS, I have provided this feature. Note: the '.'s shown above will automatically be padded to the end of what ever text you define to fill out the entry, so you don't need to include them. *--------------------------------------------------------------------------- ;redefine User Definable Door Text - (1-20) ;DEFDOOR 1 FIND THIS TEXT ; ; If not defined then the entry will not be scanned for regardless of ; DEFDOORTYPE or DEFREPORT entry. If defined then the text will be ; scanned for anywhere in the line. Order of variables can be important. ; DEFDOOR 1 ADJUSTED DEFDOOR 2 ONLY NEW USERS DEFDOOR 5 SEARCHING FOR ( DEFDOOR 9 FILE READ: DEFDOOR 11 CARRIER LOST DEFDOOR 12 KEYBOARD TIMEOUT This allows you to define the text that is scanned for for a Door defined by yourself. This Door corresponds to the DOOR U DoorName entry (or REPORT Y8). You may define up to text entries to be recognized. Use as much or as little of the text you need to identify a particular line from another. The number corresponds to the 20 variables set aside for the door report. If the text you specify is found then the variable will be incremented. Undefined (unused) text entries will not be scanned for. *--------------------------------------------------------------------------- ;redefine User Definable Door Variable Type - (1-20) ;DEFDOORTYPE 1 1 ; ; When DEFDOOR is defined: ; Bit 2 means Carrier lost, Doesn't count if Door Logged User Off ; Bit 4 means Door Logged User Off ; Bit 8 means Line contains HH:MM entry to stop Door Timing ; ; When DEFREPORT is NOT defined: ; Assigning a 1 means show ' ....................... ' ; Assigning a -1 means show ' ' ; DEFDOORTYPE 1 1 DEFDOORTYPE 2 1 DEFDOORTYPE 3 -1 DEFDOORTYPE 4 -1 DEFDOORTYPE 5 1 DEFDOORTYPE 6 1 DEFDOORTYPE 7 -1 DEFDOORTYPE 8 -1 DEFDOORTYPE 9 1 DEFDOORTYPE 10 1 DEFDOORTYPE 11 2 This controls special aspects of the variables. It is 'bit' controlled and you can include all or none of the bits. The bit meanings are described above. The real use is to recognize a CARRIER LOS entry so it can be counted properly for the report. Also, if there is a line issued by the door that would indicate that the door was dropping carrier or logging the user off, this prevents CALLS from counting a CARRIER LOST against the User. Allowance is also given to tell CALLS to stop timing the door on a given entry. One such line exists in PCBVerify as 'User disconnected at (HH:MM:SS)' so setting an entry to 12 would cause CALLS to recognize that timing of the door can stop and that a subsequent CARRIER LOST should be ignored (until a Minutes Used or a Back From Dos at HH:MM line appears to indicate the door data has ended. If a variable is unused you can use DEFDOORTYPE to cause a blank line to be generated by setting as described above. This allows for flexible report output to be designed. Although only 1 User Definable report is allowed, you can combine multiple doors under it by defining DOOR U Door1/Door2/Door3 and then using the first several variables for Door1, skip 2 variables, use some for Door2, skip 2 and then Use more for Door3. Setting the skipped variables DEFDOORTYPE to -1 will cause a separating blankline. Only a single Number of times Door Opened, Time in Door, etc... report will be generated and represent all doors combined. *--------------------------------------------------------------------------- ;redefine User Definable Door Report Text - (1-20) ;DEFREPORT 1 Found the text ; ; If not defined then the entry will not be Reported, unless DEFDOORTYPE ; is defined in which case a blank entry will be reported. ; DEFREPORT 1 Security Level Adjusted DEFREPORT 2 Not New User in Door DEFREPORT 5 Search performed DEFREPORT 9 File Read DEFREPORT 11 Caller Dropped Carrier DEFREPORT 12 Keyboard Timeouts This allows you to specify the text that appears in the report itself for each variable. Blank (or unused) lines will not be printed (with the noted exception of the 1, -1 DEFDOORTYPE mentioned above) *--------------------------------------------------------------------------- ;Include Refused to Register and Access Denied - Refused Registration REFUSEDREG NO This allows you to have the two figures combined and reported under Refused to Register. The purpose for this is for those of us who allow Users to remain on the BBS at a reduced level if they don't register. PCBoard generates a Refused to Register entry and CALLS uses that to generate a Non-Registered Users report. Only those Users who refuse to give a full name after starting a name entry or refuse to answer the questions after starting registration cause a Access Denied - Refused Registration entry to be generated which CALLS uses to generate a Refused to Register report for. If you have the level set to 0 for these users, then PCBoard will kick them off and you will get a Refused to Register entry in the log for them. Setting REFUSEDREG YES will cause CALLS to report both entries under Refused to Register (although the entries will still be reported under Non-Registered Users also.) *--------------------------------------------------------------------------- ;redefine Language Names - 20 characters max - (1 - 30) ;LANGUAGE 5 Three Stooges (5) LANGUAGE 1 English [Default](1) LANGUAGE 2 Southern Style (2) LANGUAGE 3 Three Stooges (3) This allows you to define the name of the languages reported by CALLS to what you call them in PCBML.DAT file. *--------------------------------------------------------------------------- ;define how event time is reported ; EVENTMODE OFF disables calculation of event duration. ; EVENTMODE BUSY calculates event duration and accounts for it ; as 'busy' time (i.e. the system was in use during this time). ; EVENTMODE IDLE calculates event duration and accounts for it ; as 'idle' time (i.e. the system was NOT in use during this time). EVENTMODE BUSY This allows you to consider the BBS IDLE or BUSY during the time the Event is running. *--------------------------------------------------------------------------- ;define how Sysop chat time is reported ; CHATMODE OFF disables calculation of Sysop chat duration. ; CHATMODE BUSY calculates Sysop chat duration and accounts for it ; as 'busy' time (i.e. the system was in use during this time). ; CHATMODE IDLE calculates Sysop chat duration and accounts for it ; as 'idle' time (i.e. the system was NOT in use during this time). CHATMODE IDLE This was intended to allow you to define the BBS IDLE or BUSY during the time the User was in Chat with the Sysop but it is not correct. It should be set to IDLE or the figures might not be correct. I added it as it is possible not to charge the User for time spent in chat but this really didn't affect the Minutes Used time reported in the Caller log, only how much time he was charged in the User file. I will probably remove this section at a later date or fix it to work by subtracting time if set to IDLE so when time is added at the minutes used line, it will have been cancelled out already. I also left it in as it does allow suppression of the time in chat line if set to OFF *--------------------------------------------------------------------------- ;define how Node chat time is reported ; NODEMODE OFF disables calculation of Node chat duration. ; NODEMODE BUSY calculates Node chat duration and accounts for it ; as 'busy' time (i.e. the system was in use during this time). ; NODEMODE IDLE calculates Node chat duration and accounts for it ; as 'idle' time (i.e. the system was NOT in use during this time). NODEMODE IDLE This should be set to IDLE also for now as it has the same problem as above and was added just to be compatible with CHATMODE. *--------------------------------------------------------------------------- ;Enable filtering of Modem return data RINGFILTER ON Sometimes the Modem returns more that just the baud rate in the way of line noise. This causes unusual reports. Also on some office phone systems it is possible to get a double ring and a RING appears before the resulting in such entries as: Modem: CONNECT 2400 D D C C C Modem: CONNECT 2400 ? ? ? Modem: RING CONNECT 2400 which throws off the report. Setting RINGFILTER ON will cause the word RING to be filtered out of the line and the connect string will be truncated at the first space past the 'CONNECT XXXXX'. *--------------------------------------------------------------------------- ;Enable filtering of CONNECT from Modem return data - Default = OFF ;NEW removes CONNECT & CARRIER identical to 14S24 ;ALL does same as ON but also condenses PROT: & COMP: messages ;HST does same as ON but also condenses HST style messages. ;CONNECTFILTER NEW CONNECTFILTER ON Some modems return much longer Connect strings and CALLS truncates the string making it less readable. Setting CONNECTFILTER to ON causes the word CONNECT to be eliminated from the string, allowing more room for useful text. If the string contains only the word CONNECT then it will not be removed (or else it will cause a problem with the CALLS.SAV file being read back in due to the blank line, which is normally means the end of a list has been reached.) If you have a CALLS.SAV file and do not want to regenerate it, you can edit out the CONNECT portion of the string manually (but don't eliminate it on the string containing only CONNECT as mentioned above, causing a blank line) If the Connect string contains a CARRIER and a CONNECT then if CONNECTFILTER is active, the CARRIER will be filtered out and the entire CONNECT XXXXX will be filtered out. If set to NEW then CONNECT or CARRIER will be stripped from the beginning the same way Sam added to 14s24. Use CONNECTFILTER ALL option to condense PROT: & COMP: messages to '/'. Under PROT: the word NONE is removed and ALT is changed to MNP and LAP-M is changed to V42. Under COMP: the word NONE and CLASS are removed and V.42BIS is changed to 'B'. All Spaces are then stripped from the string. This should help reduce the number of different Connect messages in the report by combining entries from multiple nodes when different brand modems are in use and the report messages are different. Use CONNECTFILTER HST option to condense HST type messages by removing ARQ, V32 and NONE and changing HST/HST to just HST. LAPM is changed to V42 and LAPM/V42BIS is changed to V42B. *--------------------------------------------------------------------------- ;Enable filtering of E from Baud rate - Default = OFF ;BAUDFILTER ON This filters the 'E' off of Baud Rates so all numeric values are counted the same instead of Error Correction connections being counted separately. *--------------------------------------------------------------------------- ;Count all (Local) connect types as SYSOP local sessions. - Default = NO ;ALL_LOCAL YES If set to YES then ALL (Local) sessions will be counted as SYSOP Local sessions regardless of the User Name of the logon. *--------------------------------------------------------------------------- ;Don't count Failed Verification files as Uploads or as a User Upload ; NO means just count it as a failure (Default) ; YES means subtract from the Upload count also ;USER means subtract from the User Uploads count also ;BOTH means subtract from Upload count & User count also FAILEDUPLOAD BOTH This allows you to not count uploads that fail verification. It also allows you to not count such uploads 'credited' to a User. Those Sysops who use CALLS to generate a bulletin showing Top User Uploads will like this. The only known problem with doing this is when a User uploads a file that fails, their name will appear in the bulletin as having uploaded Zero files if they only upload one file and it fails. It was too much trouble to try to figure out how to remove the entry from the chain. I will make a future modification to skip '0' entries on the reporting end of it. As long as there are enough Users uploading to push the Zeros off the report, you won't even see the names. *--------------------------------------------------------------------------- ;Include ' at (hh:mm)' on event times - Default = YES EVENTTIME YES This allows you to control whether the tim is included with the name of the event. If the event slides, there will be multiple entries in the report for each time it ran. If you prefer to have a single entry for the event then set this to NO. -= Average Event Program Times =- 3 - EVENT1 ran at (03:30): 60 Times 16.8 Mins Avg. (Set to YES) 3 - EVENT1 ran at (03:31): 3 Times 16.8 Mins Avg. (Set to YES) 3 - EVENT1 ran: 63 Times 16.8 Mins Avg. (Set to NO) *--------------------------------------------------------------------------- ;Count Batches by batch size count instead of file count - Default = NO COUNTBATCHES YES Normally CALLS counts batches by the number of files in the batch size which is confusing to some Sysops. Setting COUNTBATCHES to YES causes CALLS to count each occurance of a batch size as one instead of the the number of files involved. The example below shows the difference Set to NO: -= Top 10 Batch Transfer Sizes =- Single Files: 1501 (15.8%) 낡같같같같같같같같같같같같같같같같같같같같같같같� 2 Files: 1398 (14.7%) 남께께께께께께께께께께께께께께께께께께께께께께꾼 3 Files: 1137 (12.0%) 낢굇굇굇굇굇굇굇굇굇굇굇굇굇굇굇굇굇굇� 5 Files: 740 ( 7.8%) 낡같같같같같같같같같같같겡 4 Files: 660 ( 7.0%) 남께께께께께께께께께께� 7 Files: 525 ( 5.5%) 낢굇굇굇굇굇굇굇굇� 6 Files: 396 ( 4.2%) 낡같같같같같겡 9 Files: 396 ( 4.2%) 남께께께께께꾼 30 Files: 360 ( 3.8%) 낢굇굇굇굇굇� 8 Files: 352 ( 3.7%) 낡같같같같같� Set to YES: -= Top 10 Batch Transfer Sizes =- Single Files: 1501 (45.6%) 낡같같같같같같같같같같같같같같같같같같같같같같같� 2 Files: 699 (21.2%) 남께께께께께께께께께께꾼 3 Files: 379 (11.5%) 낢굇굇굇굇굇� 4 Files: 165 ( 5.0%) 낡같겡 5 Files: 148 ( 4.5%) 남께꾼 7 Files: 75 ( 2.3%) 낢� 6 Files: 66 ( 2.0%) 낡� 8 Files: 44 ( 1.3%) 넴 9 Files: 44 ( 1.3%) 넴 10 Files: 28 ( 0.9%) 넴 ============================================================================== Of course, despite the fact that the title screen still says support is from Samuel H. Smith, please don't refer questions regarding features added in this version to him. I will field all support questions for the changes I made. Gary Meeker