ReadMe.txt  from INETLG75.ZIP 04 Oct 2000 (c) Chuck McKinnis, Jerry Levy
Please pass on comments, suggestions, problems.

Chuck McKinnis, Sandia Park, NM (USA)	mckinnis@attglobal.net
Jerry Levy, Marblehead, MA (USA)
------------------------------------------------

Read the "Installation" Section for install information.

CONTENTS

1.0   What is INetLog?
2.0   Installation
3.0   Defaults and run options
      3.1   Run options
      3.2   Defaults
4.0   Utilities
      4.1   EOF2CRLF
      4.2   INSTALL 
5.0   Copyright notice
6.0   Other things to do or check
7.0   Tips
8.0   Bugs, problems

1.0   What is INetLog?

      INetLog is a REXX Program that extracts and totalizes daily and
      monthly connection times for calls made using the IBM IGN dialer or
      the In-Joy dialer.

2.0   Installation

      After unzipping inetlgxx.zip, open an OS/2 window, navigate to the
      directory you unzipped to, run INSTALL, and you are all ready to go.
      To change INetLog parameters, run INSTALL.  The inetcfg.ini file
      can be changed by editing INSTALL and changing the parameters in
      the Config_sample: subroutine and running INSTALL and resetting
      parameters to the defaults.  Not recommended for the novice and
      pay attention to the comments.  To run INetLog, open its program
      object.

      NOTE - If you run multiple OS/2 sessions from different partitions
      and/or multiple dialers (such as TCPDIAL).  we highly recommend
      you point the log file setting on the logging page of the dialer
      setup to a common log file to assure that you can analyze all
      activity.  You may need to merge the separate existing logs into
      the combined log.

      Read carefully the notes about messing around with the connection
      log. You will need to run EOF2CRLF.CMD with the fully qualified
      names of the input (the one you messed with) and output log files
      as parameters after editing your new connection log.

3.0   Defaults and run options

      3.1   Run options

            The following are acceptable command-line parameters (case
            is ignored.

            QUIET - Run without output to screen, default is to output
               results to the screen

            COMBINED - Produce a combined output summary listing of both
               IGN and InJoy results in addition to other output.

            COMBINEONLY - Produce only a combined summary listing of the
               both the IGN and InJoy results.

      3.2   Defaults

            The defaults are stored in inetcfg.ini, and the major ones
            may be changed by running INetCfg.

            cfg_common - parameters common to all runs

               ibm_dialer - process IBM dialer logs (1 = yes, 0 = no)
                  default is null

               injoy_dialer - process InJoy dialer logs (1 = yes, 0 = no)
                  default is null

               data_path - path to data files - normally x:\inetlog\data

               daily_report - display daily reports (1 = yes, 0 = no)
                  default is no

               warn_pct - warn if the IBM dialer log exceeds this
                  percentage of the size specified for the log
                  default is 85

               sig_x - significant digits for connects/day or conects/month
                  default is 4

               sig_min - ... for minutes/day or minutes/month
                  default is 7

               sig_hr - ... for hours/day or hours/month
                  default is 6

            cfg_inetlog - parameters used for processing IBM dialer logs

               ibm_dialer_ini_file - name of the IBM dialer ini file
                  default is dialer.ini or tcpdial.ini depending upon
                  the dialer you use

               ibm_output_file - output file for IBM dialer detail report
                  default is inetlog.log in data_path

               ibm_summary_file - output file for IBM dialer summary report
                  default is inetsum.log in data_path

               ibm_last_time_stamp - time stamp for last processed record
                  of IBM dialer log - initialized to T00000000000000
                  (yyyymmddhhmmss) and updated by each run

            cfg_ijoylog - parameters used for processing InJoy dialer logs

               injoy_logs - full path(s) to the InJoy dialer log file(s)
                  default is null - for each log there will be a 
                  corresponding entry in injoy_accts, injoy_users, and injoy_times

               injoy_accts - account(s) for the InJoy dialer log file(s)
                  default is null - if an account is not specified, the
                  value will be set to (none)

               injoy_users - users(s) for the InJoy dialer log file(s)
                  default is null

               injoy_times - time stamp(s) for the InJoy dialer log file(s)
                  initialized to T00000000000000 (yyyymmddhhmmss) and
                  updated by each run

               injoy_output_file - output file for InJoy dialer detail
                  report - default is ijoylog.log in data_path

               injoy_summary_file - output file for InJoy dialer summary
                  report - default is ijoysum.log in data_path

4.0   Utilities

   4.1   EOF2CRLF

         If you edit a dialer log with the IBM system editor, it will
         write an eof character at the end of the file.  Subsequent
         executions of INetLog will not read beyond that point.  The
         eof2crlf.cmd can be used copy a file on a character by
         character basis and replace the erroneous eof character with a
         normal carriage return and line feed.

   4.2   INSTALL

         This utility is used to install INetLog and can be run to update
         the INetLog parameters.

5.0   COPYRIGHT NOTICE

      This program is copyright by us (1995 - 2001).  We intend it as
      Freeware, and it may be distributed freely.  We only ask that if
      you build upon it or modify it and distribute a modified version,
      you credit INetLog and us as a source.  Naturally, if we can be of
      help in a modification, we will be pleased to do so.  No warranty
      of merchantability or fitness for any purpose of any kind is
      expressed or implied.

6.0   Other things to do or check

      IBM dialer - You must, of course, have set up your IBM dialer for
      logging.  Upon installation of the TCP/IP stuff supplied with IBM
      Warp, a small connection logfile is enabled for the IBM dialer.

      If you are using the dial other internet providers package, sorry,
      it doesn't provide for any connection logging.

      The Logging Page of the Settings Notebook for the IBM dialer allows
      you to enable or disable logging and to change the size, name and
      location of the logging file.  The logfile can be set anywhere in
      size from 5K to unlimited size.  100K will preserve information on
      about 300 logins.  The summary facilities in INetLog should allow
      you to run with a setting of 10-20K. If your Dialer doesn't have a
      Logging Page in the Settings Notebook, get the latest Dialer
      upgrade (go to the IGN Customer Service folder to go about
      downloading it).

      InJoy dialer - The InJoy dialer maintains connection logs for each
         host.  INetCfg will read the InJoy sub-directory to find the
         default configuration and its log and any logs associated with
         any other hosts found in hosts.dat.  Summary reports are based
         upon account ids and user ids, and you will be asked to furnish a
         account id for any host that does not have one.

7.0   Tips

      Because the summary files contain everything needed to continue to
      accumulate connection information, you can use the IBM tiny system
      system editor (tedit.exe) to clean up your connection logs.  After
      running INetLog, you can delete all of the connection entries in a log
      if you are not interested in daily analysis (turned off by default).  I
      do not recommend that you delete the log.

      You can also edit the summary logs (inetsum.log and ijoysum.log)
      in the IBM tiny system editor (tedit.exe) and eliminate the monthly
      summary records that are no longer of interest.  I usually eliminate
      records that pertain to this year minus 2.  This could be done by the
      INetLog processing, but I chose not to do so.

8.0   Bugs, problems

      None that I'm now aware of.

      If you modify the program, the fact output is saved till the very
      end makes debugging harder, and the error-trapping with the signal
      calls can be problematic as well.  You may want to comment out or
      turn off all of the signal calls until your mod works as planned.
      This may make it easier to spot where a modified program is going
      south. Then when you've made and tested your changes, build
      error-trapping back in with the signal calls re-enabled.

Chuck McKinnis, Sandia Park, NM (mckinnis@attglobal.net)
Jerry Levy, Marblehead, MA
