Category : Utilities for DOS and Windows Machines
Archive   : 4LOG05.ZIP
Filename : 4LOG.REF

 
Output of file : 4LOG.REF contained in archive : 4LOG05.ZIP


____________________________________________
| |
| 4 L O G - 4DOS LOG ANALYSIS |
| ----------------------------- |
| Version 0.5 (Beta) |
| May 22, 1991 |
|____________________________________________|

====================================
Parameter Descriptions and Reference
====================================

Copyright (c) 1991 by Mike St. Clair
All Rights Reserved


This file contains information specifying 4LOG Parameters.

Following are definitions of the 4LOG configuration parameters
and options. Upper and lower case are not significant in
specifying parameters. The parameter name may be followed
directly by the parameter value or they may be separated by an
"=" depending on the users preference. You may use whichever
format you are most comfortable with or randomly mix them. Those
parameters which do not use a value may be specified alone or
followed by "=Y" to be turned on. Turn them off by following the
parameter with "=N"

Parameters can be specified on the command line, in the
configuration file 4LOG.CFG or in the DOS environment by setting
variable 4LOG. Parameters from the command line override those
from 4LOG.CFG and from the DOS environment variable 4LOG. Those
in the 4LOG.CFG file override those from the DOS environment.

When these parameters are entered in the 4LOG.CFG file, comments
can be included. Any string starting with " -" or " /" will be
interpreted as a configuration parameter. The rest of the
contents will be assumed to be comments. You can use the program
4LOGCFG (not included in this BETA version) to create or modify
4LOG.CFG or you may use an ASCII text editor. Any leading path
name included in the 4DOS log is automatically stripped so the
actual command name can be properly analyzed and summarized.











May 22, 1991 4LOG.REF (Parameter Descriptions) Page 1 of 7


=================================
Current Configuration Parameters:
=================================

=================================================================
AS Array Size:

Example: -AS=500 (allow for up to 500 unique commands)
Default: -AS=200 if AS is not used or is used with no size

AS allows for this many unique commands to be summarized. If
not enough space is allocated, commands beyond the AS size
are discarded with the number of discards counted.
=================================================================
BD Begin Date:

Example: -BD=04/01/91 (start processing data 4/1/91)
Default: -BD=01/01/00 if BD is not used or is used without
a date

4LOG ignores any data from before the date specified by BD.
=================================================================
BM Batch Mode:

Example: -BM (run in the batch mode)
Default: use interactive mode

When running in batch mode, 4LOG will not ask for any input
at run time.
=================================================================
CF Configuration File:

Example: -SI=C:\4log.cfg (get configuration from this file)
Default: 4dos.cfg in current directory if CF is not used or
if CF is used without a path name.

Note that the CF parameter cannot come from within the CFG
file but must be specified in the environment or on the
command line.
=================================================================
DC Display Count:

Example: -DC=10 (show commands with count of > 10 on screen)
Default: -DC=5 (show commands with count of > 5 on screen)

During 4LOG processing, command counts are displayed on the
screen when they reach this number. If too many commands to
fit on the screen are exceed this count, 4LOG will increase
this number dynamically whenever required. Note that the
summary file and optional printed report both include those
commands which will not fit on the screen.
=================================================================

May 22, 1991 4LOG.REF (Parameter Descriptions) Page 2 of 7



=================================================================
ED End Date:

Example: -ED=04/30/91 (stop processing after 4/30/91)
Default: -ED=12/31/99 if ED is not used or ED is used but no
date is given.

4LOG ignores any data from after the date specified by ED.
=================================================================
LI Internal Command Exclude list:

Example: -LI=C:\4LOG\4LOGICMD.LST (exclude command names
listed in this file)
Default: 4LOGICOM.LST in the current path if LI is used
without a path or if ZI is used without LI.
Internal commands are not excluded if neither LI
nor ZI is specified.

Command names contained in this list will be ignored and not
included in any analysis. It actually works just like LX. A
file with the default name containing a list of 4DOS
internal commands is distributed with 4LOG. The user may
freely modify this list. It contains entries in the
following format with the command starting in column 1:
CDD /* CDD an internal command to be excluded */
Lines beginning with "*" or blank will be skipped.
=================================================================
LX Exclude Command List:

Example: -LX=C:\4LOG\4LOGEXCL.LST (exclude commands listed
in this file)
Default: 4LOGEXCL.LST in the current path, if LX is used
without a path. No exclusions if LX is not used.

Command names contained in this list will be ignored and
not included in any analysis. List contains entries in the
following format with the command starting in column 1:
OPTUNE /* exclude the command OPTUNE */
OPTUNE.EXE /* exclude the command OPTUNE.EXE */
Lines beginning with "*" or blank will be skipped.
=================================================================
MI Main LOG Input File

Example: -MI=C:\4DOSLOG (get 4DOS LOG data from this file)
Default: 4DOSLOG in the current directory

Specifies the name of the 4DOS log to be analyzed.
=================================================================





May 22, 1991 4LOG.REF (Parameter Descriptions) Page 3 of 7


=================================================================
ML Message Level: (0 = minimal messages, 9 = all messages)

Example: -ML=0 (suppress most messages)
Default: -ML=9 if ML is not used

Allows suppression of most screen output to speed
processing and for batch mode operation where the screen
display is not needed.
=================================================================
PR Print Summary Report:

Example: -PR (print a report showing commands executed)
Default: Do not print a summary report. Just list to screen.

Parameter determines whether the command summary is printed.
=================================================================
ZD Ignore Default Disk Switches:

Example: -ZD (ignore disk drive switches e.g. c:)
Default: Summarize the disk switch commands just like all
other commands.

If this switch is not set, disk switches will show up in the
analysis as C:, D:, etc. Specifying ZL as greater than 2
will also suppress disk switch commands.
=================================================================
ZI Suppress Processing of Internal 4DOS Commands:

Example: -ZI (suppress internal commands from IL file)
Default: process internal commands like any other

See the IL parameter for the file name containing the list
of suppressed 4DOS internal commands. This list is included
in the distribution archive file but can be modified by the
user as desired.
=================================================================
ZL Suppress Commands Shorter than the Specified Length:

Example: -ZL=3 (ignore commands of length 3 or shorter)
Default: -ZL=1 if ZL is not used, commands of length one
will be suppressed.

Requests that 4LOG ignore any commands of the specified
length or less when analyzing the input log.
=================================================================







May 22, 1991 4LOG.REF (Parameter Descriptions) Page 4 of 7


=================================================================
ZS Suppress Suffixes on Commands

Example: -ZS (drop the extension from all command names)
Default: do not drop suffixes

If this parameter is given, the period and extension will be
dropped from any command found in the log before
summarization. Therefore LIST.COM, LIST.BAT or LIST.BTM
would all appear as LIST.
=================================================================
Z* Suppress Leading "*" on Commands:

Example: -Z* (drop all leading "*"s)
Default: Do not drop leading "*"s.

Allows dropping the leading * used by 4DOS to bypass alias
lookup. This would cause the command to be summarized
together with the same name without the "*".


































May 22, 1991 4LOG.REF (Parameter Descriptions) Page 5 of 7


===============================
Future Configuration Parameters
===============================

The following options are planned but not fully implemented.

=================================================================
HI History Summary LOG Input File:

Example: -HI=C:\4DOSLOG.SUM
Default: 4DOSLOG.SUM in current directory if HI is used
without a path name. No summary file if HI not
used.

Specifies the name of the 4LOG summary log to be updated
from the data in the 4DOS LOG input file. When summary files
are processed, this file is first renamed with an ".OLD"
extension after deleting any conflicting file name.
=================================================================
HO History Summary LOG Output File:

Example: -HO=C:\4DOSLOG.SUM
Default: 4DOSLOG.SUM in current directory if HO is used
without a path name. No summary file is created if
HO not used.

Specifies the name of the 4LOG summary log to be updated
from the data in the 4DOS LOG input file.
=================================================================
HR Revise the data in the input History Summary LOG file:

Example: -HR
Default: don't revise the history data

If this parameter is used, 4LOG will apply the current
parameters to revise the input history data (e.g. drop short
commands, exclude additional commands) If it is not used,
new data will be added based on the current parameters but
the old data will be carried forward without change with the
exception of applying a higher level of summarization if
this has been requested by SL.
=================================================================
LT Translate List

Example: -LT=C:\4LOG\4LOGXLAT.LST
Default: 4LOGXLAT.LST in current path if LT is used with no
path.

Command names contained in this list will be translated to a
new name. List contains entries in the following format:
OPT=OPTUNE /* OPT commands will summarize as OPTUNE */
=================================================================

May 22, 1991 4LOG.REF (Parameter Descriptions) Page 6 of 7


=================================================================
MF Message File

Example: -MF=C:\4LOG\SPAN.MSG (get messages from this file)
Default: -MF=C:\4LOG\4LOG.MSG if MF is not used

Identifies a file containing the text of the messages and
screen labels used. The 4LOG.MSG file included with the
distribution package has the messages using English text.
This file can be edited by any ASCII text editor or you can
make your own replacement with foreign language
translations. Note that the messages and screen labels
cannot be expanded in size. If they are expanded, only that
portion which is not longer than the original entry will be
displayed.
=================================================================
SL Summary Level (where x is D=daily, W=weekly, M=monthly,
Q=quarterly, Y=yearly)

Example: -SL=W
Default: no summary produced if SL is not specified

Allows specifying the level of summarization desired in the
summary log files. Note that if the input summary file has a
higher level of summarization than the level requested, no
data will be copied from it. (e.g. input = monthly and
output = daily)
=================================================================

























May 22, 1991 4LOG.REF (Parameter Descriptions) Page 7 of 7


  3 Responses to “Category : Utilities for DOS and Windows Machines
Archive   : 4LOG05.ZIP
Filename : 4LOG.REF

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/