












                                  FPDATA/CMD



                                 Version 01.06



                                Copyright 1989



                                   Karl Mohr








































                            TABLE OF CONTENTS 


          Outline of Procedure . . . . . . . . . . . . . Page  3

          Technical Information  . . . . . . . . . . . . Page  3

          Introduction   . . . . . . . . . . . . . . . . Page  4

          System Requirements  . . . . . . . . . . . . . Page  5

          Correct year Input . . . . . . . . . . . . . . Page  6

          Acknowledgements . . . . . . . . . . . . . . . Page  6

          Reading USERnn/LOG . . . . . . . . . . . . . . Page  7

          Main Sysop Number  . . . . . . . . . . . . . . Page  7

          Drive Output number  . . . . . . . . . . . . . Page  7

          Date Correction  . . . . . . . . . . . . . . . Page  8

          Reading USERnn/LOG files . . . . . . . . . . . Page  8

          Creation of USERnn/DEL . . . . . . . . . . . . Page  8

          Main Menu Options  . . . . . . . . . . . . . . Page  8

          Data Interpretation  . . . . . . . . . . . . . Page  9

          Main Sysop & Sysop Option  . . . . . . . . . . Page 10

          Data tracked Summary . . . . . . . . . . . . . Page 10

          Saving User Information  . . . . . . . . . . . Page 11

          Total USERnn/DAT Files . . . . . . . . . . . . Page 11

          Program Support  . . . . . . . . . . . . . . . Page 11

          Order Form . . . . . . . . . . . . . . . . . . Page 12












          FPDATA/CMD(c)             Page 2              Karl Mohr, 1989











         Outline of Procedures:

         Step 1: Run  FPDATA/CMD and enter USERnn/LOG file, followed by
                 Main Sysop User number, and Output drive number.

         Step 2: USERnn/LOG   file is read,  USERnn/DEL file is created
                 if deleted user is encountered.

         Step 3: Main menu is presented,   inputs on how  you wish data
                 to be displayed, and if Hardcopy is desired.

         Step 4: Data is displayed, and Hardcopy printed (if requested)

         Step 5: USERnn/DAT file created, saves user data.

         Step 6: Total USERnn/DAT files, if desired.

         Step 7: Hardcopy of data in step 6, if desired.

         Step 8: Program terminates.

         To enter specific data, such as USERnn/LOG files, etc. type in
         the information  followed by pressing the  ENTER key.  To step
         through the displayed data,  you must press the SPACE BAR. You
         may  Terminate the  program at any time by  pressing the BREAK
         key instead of pressing the SPACE BAR.
         F1 - moves to next operation, Hardcopy (if set), or loads next
         Overlay (if in /OV1, /OV2, /OV3).

         Technical Information

              FPDATA  uses  integers as much as possible.  You may find
         certain  percentages will not sum up to 100%,   rather it will
         come to 99% or 101%.   Speed was given preference over certain
         data accuracy.   It  was  felt  this  minor  variance could be
         tolerated.

         Keyboard bounce - in the ShareWare release,   a certain factor
         of keyboard bounce occurs.    This is completely eliminated on
         the Registered versions.

         XLR8TER boards -  For some reason,  decimal 0 (.0) is added to
         some  numbers!!   The numbers,  other than  that are perfectly
         normal  and correct.   The Day of the  Week  does NOT come out
         correctly from the 1st to 9th of the Month.   I don't know why
         as yet, but will work on it!    This is fixed in  Version 1.05
         and beyond.







          FPDATA/CMD(c)             Page 3              Karl Mohr, 1989











         Introduction

         FPDATA/CMD and its OVERLAY files will read the USERnn/LOG file
         created by either programs FastPlus or FPII.  The program will
         generate USER data from ONLY these files.  The Sysop will find
         that using this program will give them a better  understanding
         of how the BBS Users are conducting  themselves while on-line.

         FPDATA correlates information such as:
               (1) Main Sysop accesses and time used.
               (2) Number of accesses by Remote Sysops.
               (3) Names and numbers of Deleted Users.
               (4) No. of New, Regular, and Special Users.
               (5) Baud rates used, 300, 1200, 2400.
               (6) Breakdown of individual Users as to:
                   i   Number of accesses.
                   ii  Total time used.
                   iii Total uploads.
                   iv  Total downloads.
                   v   Number of messages left.
               (7) Hardcopy options.

               The  information  gathered  may be viewed in a number of
         selected ways depending on your wishes and input to a number of
         questions.   (More on this later).  All the information may be
         viewed as a quick summary,  or a Hardcopy with full pagination
         may be printed,   or you may wish to view the data  graphicly.

               The  latter is  especially  useful when  summarizing the
         individual users.   It can quickly be seen whether or not each
         User is  doing  their  fair  share in  utilizing the BBS time,
         uploading a  proportion of  programs as compared to downloads.
         The graphic  display  incidentally is a full varying scale de-
         pending  on  the  information  correlated  from the  file that
         you are summarizing.

              It was  quite  interesting as  this program developed and
         was used to correlate the  "Evicted" Users that terminated in-
         correctly.  During a four month period,  it was found that one
         certain  individual  terminated incorrectly 32 times! My guess
         is,  the Sysop of that BBS will be waiting for that person the
         next time that individual signs on!

              The  author of  FPDATA sincerely hopes that you will find
         this program  invaluable in maintaining your BBS, and that you
         support  this  Shareware  release.  Unfortunately, certain in-
         dividuals  would  not  support  Shareware  if an  incentive is
         not used.   I have been  guilty of  this too,   but have  made
         amends!   Therefore,  the options of making any permanent form
         of records has been withheld.   This includes saving the Users
         Data, Deleted Users file, and making a Hardcopy.



          FPDATA/CMD(c)             Page 4              Karl Mohr, 1989











         System Requirements
              FPDATA was developed and fully tested on LS-DOS 6.3 (L+).
         The program can be run on a 64k Model 4,   with a minimum of 1
         floppy disk drive.   A two floppy disk drive system is optimum
         as less  erratic  drive  movement occurs when one drive is the
         input (USERnn/LOG) drive,   and the  other drive is the output
         Ie. USERnn/DEL - created for  deleted users if any.    Model 4
         owners with 128k may invoke  Memdisk to  temporarily store the
         created files.   FPDATA has been tested on systems with a Hard
         Drive as well.

              FPDATA has  five  components with it that must be on-line
         when running.

              FPDATA/CMD
              FPDATA/OV1
              FPDATA/OV2
              FPDATA/OV3
              FPDATA/OV4


         FPDATA/CMD is the  main program.  It may be  renamed but users
         are requested to please not do this.  FPDATA/OV1 to FPDATA/OV4
         are called up from  FPDATA/CMD and may  NOT be renamed.  Doing
         so will result in a file not  found error and the  information
         normally displayed by that Overlay file will be lost.

              FPDATA/CMD asks for the  USERnn/LOG file to be read,  the
         Main Sysop's User number and the output drive number.  It then
         reads all the information from that file in one pass,  reading
         time is  dependent of the file size.   A typical 45k file will
         be read in approximately 1.25 minutes,  this also depends upon
         if the file being read is on a Harddrive or on Floppy disk.

              FPDATA/OV1 - correlates the Hourly functions.
              FPDATA/OV2 - correlates the Weekly functions.
              FPDATA/OV3 - correlates the Monthly functions.
              FPDATA/OV4 - correlates the individual User functions.

         To begin running the program, type in:

              FPDATA     [Press Enter]

         More detail will be  given in  following  documentation on all
         aspects of menu operations, input requirements, etc.










          FPDATA/CMD(c)             Page 5              Karl Mohr, 1989










         Correct Year Input

              The day and date of each User  entry is obtained from the
         USERnn/LOG,  the year however is obtained from the System time
         A number of information readouts use the day  (Mon, Tue, etc.)
         as part of the information,   you may wish to have the correct
         day for the date.   The  only  requirement here is to have the
         correct SYSTEM YEAR for the YEAR  that  the  file was created.
         Other than this,  no further consideration need be given as to
         the correct month or correct date of the System time.

               For example,  if the USERnn/LOG was created in 1988, and
         you are reviewing the file in 1989,   the day of week will not
         be correct for that date.   You must change the system date to
         1988 for the correct day of week to  correspond to the correct
         date.


         Acknowledgements

              FPDATA/CMD and associated  overlay files where written in
         Zbasic,   Version 3.1,   to obtain the necessary speed in file
         reading and processing of data information.

         FPDATA/CMD is Copyrighted by Karl Mohr, 1989.

         FASTPLUS/CMD is Copyrighted by Mel Patrick.

         FPII/CMD is Copyrighted by Mel Patrick.


























          FPDATA/CMD(c)             Page 6              Karl Mohr, 1989










         Reading USERnn/LOG

              You have typed in FPDATA and pressed  Enter.  You are now
         prompted for the USERnn/LOG  you wish to  review.   Enter this
         information and press Enter.   Next you are asked for the Main
         Sysop User number.

         Main Sysop Number

              You have the option of giving the  Main Sysop User number
         or simply pressing  Enter  depending on your choice of how you
         wish the program to compile the data.  If you DO give the Main
         Sysop User number,   the  program  will separately compile the
         information on the Main Sysop.   This information will be kept
         separate from other information and totals,  such as messages,
         uploads, dnloads, total system use,  and so on.   Also, REMOTE
         SYSOP uses will then be  tabulated and kept  separate from the
         Main Sysop.
              If you elect to NOT enter the Main Sysop User number, the
         program will then  tabulate  this  information in with all the
         other information gathered.   The  Main  Sysop will be treated
         the same way as any other user data is displayed.  The program
         will track the number  of  sysop  accesses,   but this will be
         added to any Remote sysop accesses.
              The Main Sysop in my  experience usually accesses and use
         more time in maintaining the BBS,  than any other regular user
         would do.  This may cause the displays,  particularly the user
         graphic display,  by changing the scale of the graphic display
         to be larger than ordinarily so,  thus giving a different view
         of how the BBS Users are performing. As example, the scale may
         be increased by the Main Sysop accesses that the regular Users
         time would appear insignificant on this same scale.  The scale
         is determined by the number of accesses and time  spent on the
         BBS of individual users.

         Drive Output number

              The output drive number is the  drive  that  the  created
         files will be  written to.   A two drive computer system makes
         for smoother and faster operation.   The  output  drive should
         be a different drive than that used for reading the USERnn/LOG
         file.  For example, drive 1 may contain the USERnn/LOG,  while
         drive 0 is  used  as  the  output drive onto which the created
         files are written.   Memdisk  may be used as  output drive for
         128k Model 4. A HardDrive may be used as well.   If the output
         drive is NOT specified,   the files will be written onto first
         available disk or Harddrive.   This may not be to your liking.








          FPDATA/CMD(c)             Page 7              Karl Mohr, 1989










         Date Correction

              The day of the week  routine  in  FPDATA  requires a four
         figure "Year",  ie. 1989,   to arrive at the day.   The system
         date  provides  the last two numbers to which "1900" is added.
         You may have guessed that this program is then date correct to
         December 31, 1999. However, the fix is minor, and if requested
         both programs will be sent. One for pre-2000, and one for post
         2000, date correct then until 2099!



         Reading USERnn/LOG files

              As FPDATA reads the USERnn file,   the first character of
         the data line read will be  flashed on the top right hand side
         of the screen.  If there is no character in the first space of
         the line, then no character will be displayed.  This was first
         used in creating the program to ensure the program was working
         correctly,   and was left in as a visual  indicator to program
         operators.


         Creation of USERnn/DEL file

              The first  time that an  "Evicted" caller is encountered,
         denoted by the E in the  first  character of the line,  FPDATA
         will open a file for USERnn/DEL.   This is fully automatic and
         contains the same USERnn  number  with only the file extension
         changed. Ie. USER01/LOG creates USER01/DEL.
         Further evicted  callers  are  added in sequence to this file.
         If the BBS "Evict"  flag for  evicting first time callers that
         drop carriers is not set,   or no  "Evicted" users are encoun-
         terred, no deleted user file will be created.
              The file will be written to  the  drive that was given as
         the output drive number.   If no drive was specified, then the
         file will be written to the first available drive.  USERnn/DEL
         may be further processed in any word processor if desired.

         Main Menu Options

              After completion of reading the  USERnn/LOG file,  FPDATA
         will present the Main Menu with  which you may decide how each
         section of the data will be displayed.

                   Report options: Detailed Hourly
                                   Detailed Weekly
                                   Detailed Monthly
                                   Detailed User
                 Hardcopy options: BBS Report
                                   Hourly Report
                                   Weekly Report
                                   Monthly Report
                                   User Report

          FPDATA/CMD(c)             Page 8              Karl Mohr, 1989










         Main Menu Options .... continued

              To choose the options wanted  simply press the "Y" or "N"
         to each of the queries.   Irregardless of your replies,  an on
         screen summary will be  given of the BBS  report  and  Deleted
         Users.   If you reply <Y>es to the Report options in the first
         section,   you will be  given a graphic and factual display on
         these reports.   If you reply <N>o,  then a quick summary will
         be given.   If you reply <Y>es to the  Hardcopy  options,  you
         then  get a  Hardcopy  on  these  reports.   The  Hardcopy  is
         presented in the same  outline as a quick summary in the first
         section.
              You may choose any  combination on either first or second
         section that you wish.  Pagination on the Hardcopy report will
         be correct independent of your choices.


         Data Interpretation

              Most of the data presented is self  explanatory,  however
         some of the more  obscure data  information will be  fully ex-
         plained.

         Load Factor
              In the BBS report,  Load Factor is a percentage factor of
         how busy or effective your BBS load is.  It is based on a per-
         centage of the maximum use that your  BBS may encounter during
         a months use.   Also,  it is a quick  indicator to see if User
         traffic is up or down over previous months.

         Sysop Options and Main Sysop
              If the Main Sysop  user  number was given at the start of
         this program,   then Sysop Options will be tracked separately.
         This would indicate any  Remote Sysop functions that were per-
         formed during the target month.  FPDATA states also that these
         functions then "Exclude Main Sysop".
              If the Main Sysop user  number is  NOT given at the start
         of this program,   then  Sysop options and Main Sysop accesses
         will be counted together  under  Sysop Options and FPDATA will
         state then the Sysop Options include Main  Sysop.   Main Sysop
         will not be displayed then.

         Users/Calls above/below Average indicator
              In the detailed reports of hours,  week, month, and User,
         FPDATA compares the  singular  pieces  of  data to the Average
         of that particular data.  For example, if in the detailed user
         display,   the average number of calls per user is 10, and the
         user being  displayed  calls 9 times, the information would be
         displayed as: Calls, 10% below average.






          FPDATA/CMD(c)             Page 9              Karl Mohr, 1989










         User Numbers

              You will notice  that some user numbers are being skipped
         when viewing the user section.   This simply means that no one
         with that user  number  has  called  during the target period.
         This does NOT  necessarily mean that the user number is vacant
         and may very well be in use. Remember, FPDATA only assimilates
         data on Users that frequented the BBS during that period.


         Main Sysop & Sysop Option in detail

              At  some  time  you may elect not to enter the Main Sysop
         number,   or for curiousity,   assign the Main Sysop number to
         someone else - say for example, a remote sysop.   You may then
         notice that the Times On and Time Used  come  out  differently
         than expected.  The main thing to remember is:   That the Main
         Sysop may elect to log  onto the BBS as a Reg user for various
         reasons, rather than as Sysop.   This then does NOT log an "S"
         in the USERnn/LOG file.   FPDATA when scanning for Sysop func-
         tion only looks for the "S" flag.   On the  other  hand,  when
         FPDATA scans for Main  Sysop,   the user number is "looked" at
         only,  independent  of whether the "S" flag is set or not. The
         Main Sysop number  takes  precedence over Sysop Function, both
         being tracked separately.


         Data tracked summary

              Deleted Users - the time used,   messages left,  uploads,
         Dnloads (if allowed),  will be  included in the totals for the
         target period,   even  though the number assigned to that user
         may now be blank or even assigned to another new user.

              Remote Sysop - the  time  used,   messages left, uploads,
         Dnloads, etc,   will be  tracked to the user number(s) of that
         individual and will be included on the  totals.   Only the "S"
         function if used will be kept track of separately.

              Main Sysop - if the Main Sysop number is given,  then all
         entries for that number will NOT be  included in  the  totals.
         Times on,  and time used will be  tracked  separately and dis-
         played with the Main Sysop.   If  the Main Sysop number is not
         given, then this  number  will  be  treated as any other User,
         only the "S" functions will be  separately tracked with Remote
         Sysop functions.









          FPDATA/CMD(c)             Page 10             Karl Mohr, 1989










         Saving User Information

              The file, USERnn/DAT will be created after all viewing and
         Hardcopies are completed. Again, this is completely automatic.
         The /DAT file will have the same USERnn number as the USERnn/LOG
         file read in. Only the extension is changed. This file is further
         used in summarizing information explained in the next chapter.
         This file may also be loaded into a Word Processor for further
         processing if desired.


         Total USERnn/DAT files

              You are given the option of further processing the USERnn/DAT
         files by totalling certain information. Ie. Total Callers, Total
         Time, Total messages, Total uploads, and total dnloads from pre-
         viously processed information. This information can ONLY be ob-
         tained from the USERnn/DAT files, and attempting to read any other
         type of file may result in unexpected results! A maximum of 12
         USERnn/DAT files may be loaded in. The information will be given
         on screen immediately after reading the file. When you wish to
         "Total" the information, simply press ENTER. If you have reached
         the maximum 12 reads,  the information  will  then be totalled
         automaticly.


         Hardcopy of Totals

              You may obtain a hardcopy of the totaled figures if desired
         by pressing "Y" and ENTER.


         Terminating program

              On printing the hardcopy of USERnn/DAT totals, the program
         will terminate to DOS READY. You may also terminate the program
         at anytime by pressing  BREAK instead of pressing the Space Bar
         while stepping through the data readouts.

         Program Support

              Please feel free to offer any suggestions or changes that
         you feel may benefit  program  users.   Actual changes will be
         based on the number of requests for a certain  change,  and of
         course, preference will be given to registered users!

         Queries may be directed through "mail" at the  following BBS.
              Leave messages to: Karl Mohr
                                 FastMaster BBS
                                 (604) 594-7398
                                 8N1, 3/12/24 baud
                                 24 hours (mostly)

         Or drop me a line through the Post Office!

          FPDATA/CMD(c)             Page 11             Karl Mohr, 1989










                                  Order Form




          To: Karl Mohr
              2256-153rd Street
              White Rock, B.C., Canada
              V4A 4R2


          Please forward Registered Version of FPDATA/CMD to:

          Name:______________________________________________

          Address:___________________________________________

                  ___________________________________________

                  ___________________________________________

                  ___________________________________________

          I am enclosing $5.00 to obtain 1 copy of FPDATA and
          associated  overlay files.  (This covers shipping).

          ===================================================

          All effort will be made to mail the registered copy
          out  within 24  hours of  receiving the order form.
          FPDATA/cmd,  Overlays,  and  Documentation  will be
          sent on SS/DD (5inch) floppy diskette of LS-DOS 6.3
          format.
                      Many thanks for your support,   K. Mohr

         ===================================================

          Date Order Received: ______________________________

                               ______________________________

          Serial Number:       ______________________________
























