There are a few requirements to making some of the new reports I added to
CALLS.EXE work.

*---------------------------------------------------------------------------
For Event timing to work properly, you will need to send the following
line to your CALLER log file (you can use CL-PRINT.COM that I wrote to do
this):

       Scheduled Event ended at MM-DD-YY HH:MM:SS

This will cause CALLS to stop timing the event, rather than to continue the
timing until a caller finally logs on.

This is no longer needed with PCBoard 15.x

*---------------------------------------------------------------------------
For the 'Average Event Program Times' report to contain anything to
report on, you will need to send lines such as:

       Event: program name started at MM-DD-YY HH:MM:SS

where 'program name' is the name of any program or function you perform in
your event. The keys here are the EVENT: at the front of the line which
causes CALLS to recognize the line, the word STARTED which causes CALLS to
first end the timing of any previous event and begin timing a new event
which has a name of whatever text is between the 'EVENT: ' and ' STARTED'
keywords, and finally the HH:MM portion of the line is picked up as the
Time the previous event ended and the new event started. If any of these
are not present, then CALLS will not function properly when generating this
report
.
*---------------------------------------------------------------------------
For the 'Languages Selected'  report to function, CALLS need to know
which language was selected at logon. There is no provision in PCBoard to
obtain this info but we can add it easy enough by placing Language Number
in     Modem connect string
        ie. Modem (1): CONNECT 2400
    or Caller Number string
        ie. Caller Number (1): 12345
    or Security Level string
        ie. Caller Security (1): 50

    This is accomplished by using MKTXT145 to modify the record for the
    'Modem: @OPTEXT@' (rec no 590), 'Caller Number: @OPTEXT@' (rec no 591)
    or 'Caller Security: @OPTEXT@' (rec no 592) and adding the text (n) to
    the current text as shown above (where n is the language number, ie.
    for your first language you add (1), for your second language PCBTEXT
    file you add (2), etc...)

You must also setup PCBoard to include whichever entry you use in the CALLER
log by using PCBSETUP and selecting the writing of the proper entry. If you
use the Modem connect string, then local logons will not get counted which
you may or may not desire. My preference would be the Caller Security since
we need it anyways for other reports.

This no longer works with PCboard 15.x as all log entries come from the
same PCBTEXT file regardless of language choice. You will need to add the
(n) language number as the Last On (n): in the line described below.

*---------------------------------------------------------------------------
For the 'Number of Calls by Security Level' or 'Hours Used by Security Level'
reports to work, you MUST have the Caller Security entry written to the log
by PCBoard.
*---------------------------------------------------------------------------
For the 'Last Called In' report to work, you must write entries in the form:

    Last On: MM-DD-YY (HH:MM)
    or
    Last On: MM-DD-YY (HH:MM) for nn Minute(s)
    or
    Last On: MM-DD-YY (HH:MM) for nn Minute(s) - #nnnn

to the CALLER log. CALLS recognizes the LAST ON: at the beginning of the line
and then uses only the MM-DD-YY portion of the line so the rest is just filler.
(I like to see the time, how long and how many calls have they made so I don't
have to go view their USER file data to find out.

*---------------------------------------------------------------------------
For the CALLER ID to work you will need to write that data to the CALLER log.

PCBoard 15.x takes care of this for you.

*---------------------------------------------------------------------------
One special consideration is the timing of the Doors and recognizing what door
the user is in. Normally this is no problem as PCBoard writes entries to the
log when the User opens the door, and returns to the board. CALLS only scans
for particular data on a few doors that is designed to generate a report for.
It only scans for a specific door's data when it sees the Opened Door (name)
entry, rather than to compare every line for the data (which would slow down
the program). The only problem that shows up, is if you go from one Door to
another Door without returning to PCBoard. You can, however, fix this problem
by simply writing an entry to the log such as:

    Opened Door (VERIFY) at HH:MM Via InstaReg

This would cause CALLS to stop timing the InstaReg door and start timing
PCBVerify. Also to start scanning the entries for PCBVerify specific data
rather than to continue scanning for InstaReg specific data.
*---------------------------------------------------------------------------