home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
DP Tool Club 8
/
CDASC08.ISO
/
VRAC
/
STATSC11.ZIP
/
STATUSC.DOC
< prev
next >
Wrap
Text File
|
1993-07-08
|
21KB
|
459 lines
Network Mail Status - Cam-Mail Version
=================================================================
First off I would like to thank those users who have offered
suggestions and made comments to this and the original Status
program (Postlink version). Some functions and displays are the
direct result of this input.
Works with Cam DeBuck's Cam-Mail (copyright Cam DeBuck
Software) door which imports and exports .QWK mail packets
received from your Network Hub(s). It uses the log(s) produced
by EXPORT.EXE and IMPORT.EXE log options.
(1) Generates a network Export mail status bulletin showing
each conference (full 24 characters in conference names), 1000
maximum, and the total number of messages exported for current
date and total to date for each conferences, total conferences
and the total messages to date for the specified network.
(2) Generates a network Import mail status bulletin with the
same format as the Export bulletin. Since the export routine
contains all conference names it is run first to get those names
so that conferences with zero imports are still displayed in the
import bulletin. I could not find another way to get all
conference names.
(3) Generates last import bulletin showing last import
information: date, time, total messages import in last import and
total messages imported to date.
(4) Generates, or appends to the end of, a monthly totals
bulletin called network.TOT with each rollover. This bulletin
contains the total lines from previous Export and Import
bulletins.
Supports multiple networks. This program uses Cam-Mail's
export/import log(s). Single log file or separate Import and
Export logs. It does a monthly rollover of the LOG(s) using
PKZIP.EXE.
This archive should contain the following files:
DOORS.TXT.............. Current list of James Huckabey doors
FILE_ID.DIZ............ BBS description file
READ.ME................ Update/changes information
STATUSC.EXE............ Actual StatusC program
STATUSC.DOC............ Instructions for running StatusC
STATUSC.CFG............ Sample configuration file
STATUSC2.CFG........... Sample configuration file
STATUSC3.CFG........... Sample configuration file
STATUSC.BAT............ Sample batch file
SUPPORT.TXT............ Location of Support BBS
ARCHIVE.TXT............ This list of files
Syntax is pretty straight forward:
STATUSC STATUSC.CFG
Full path to STATUSC.EXE may be used if not in path or in
current directory. If you do use a path statement in your
execution of StatusC (not in current dir or in path) you need to
set the environment variable "SET STATUSC=path to STATUSC.EXE"
(SET STATUSC=C:\UTILITY\OTHER, etc. no ending slash is needed).
It is not necessary to add a path statement to the
configuration file since the program finds itself. Of course the
file must be in location of STATUSC.EXE. If the configuration
file is not in the same location then use the path statement to
it's location.
"STATUSC.CFG" and can have any file name with the following
format. You can use up to 8 characters of your network name for
the name of your .CFG file if that helps keep multi-network
configurations clearer. This would be the easiest way to do it.
Each line must be populated with a valid entry. Paths to
bulletins or logs are not needed if they are in or written to the
current directory:
(1) Unregistered BBS
(2) 0000
(3) Network
(4) CAM-MAIL.LOG
(5) C:\BBS\BLT7
(6) CAM-MAIL.LOG
(7) C:\BBS\BLT77
(8) C:\BBS\BLT777
(9) PCB
CFG line #1
"Unregistered BBS", system name if registered
CFG line #2
"0000", valid serial number if registered.
CFG line #3
"Network" should be the name of the actual network you are
using, one word and case sensitive (Intelec, UNINET, etc.). 18
characters max, longer names are truncated. Say you are making
two different network mail runs with the same software, you would
use those names here, each in it's own configuration file.
CFG line #4
"CAM-MAIL.LOG" is the path and name of your Cam-Mail Export
log. Lines #4 and #6 can contain the same file name if your
Export and Import logs are in one file. I believe this is normal
for the Cam-Mail generated log. (At this time I have no details
on how Cam-Mail does logs or multiple logs)
CFG line #5
"C:\BBS\BLT7" is the path and name for your Export bulletin.
CFG line #6
"CAM-MAIL.LOG" is the path and name of your Cam-Mail Import
log. Lines #4 and #6 can contain the same file name if your
Export and Import logs are in one file. I believe this is normal
for the Cam-Mail generated log, but have maintained the format
used in the Postlink version of Status.
CFG line #7
"C:\BBS\BLT77" is the path and name for your Import
bulletin.
CFG line #8
"C:\BBS\BLT777" is the path and name for your Last Import
bulletin.
CFG line #9
Color and characters used are setup to give you as much
control over the output as possible. Not all users can read and
handle IBM extended graphic characters (like sight impaired users
and voice hardware). Program can use either "=/-" or IBM's
extended graphic characters "═/─". Line #9 must contain one of
the following options:
"PCB" use IBM extended graphic characters and PCBoard's @X0
colorizing codes.
"PCB0" use no IBM extended graphic characters and PCBoard's
@X0 colorizing codes.
"ANSI" use colorizing and no IBM extended graphic
characters.
"ANSI2" use colorizing and IBM extended graphic characters.
"ASCII" use no colorizing and no IBM extended graphic
characters.
"ASCII2" use no colorizing, but use IBM extended graphic
characters.
STATUSC TOTALS FILE(s)
This file, StatusC Totals, is written to the current
directory only. Current directory is the directory where you call
STATUSC.EXE from. The file name is the first eight alphabetical
characters of your network name. That way if you are making
multiple network mail runs each network will have it's own totals
file. The extension is always "TOT".
Please make note that if your copy of StatusC is not
registered that the total file will have "Unregistered BBS" in
the BBS line of the bulletin. If you keep the file and register
StatusC you will have to edit the top line of the bulletin or
erase the file and start over.
This file/bulletin has unlimited possibilities. If you are
making more than one StatusC execution, say for different
formats, only the first one will be executed with the rollover.
So this file will only contain that color format. It is complete
with whatever color codes existed in the original bulletin. The
colors can be removed or replaced with whatever colors you want
manually using a text editor.
The file has a three line header when first created, (1)
line with BBS name in it, (2) an explanation of what it is, (3) a
header termination line. It then has one line for Export total
and one line for Import total followed by a blank separation
line. Each successive appendage is three lines total. A year's
worth of information would have a total of thirty-nine lines.
What you do with this information is up to you. Just another
friendly option added to the program. If you are going to use it
as an active bulletin it can be copied anywhere you want. Just
make sure that if you want the next rollover appended to the end
that you keep the file in the current directory for the execution
of StatusC. If you change this directory make sure you move the
total bulletin(s) to your new directory.
It should be noted that when you start using StatusC for the
first time that if your Cam-Mail log(s) are not just the current
month's log(s) that the log does not roll over until the month in
the log equals your system's current month. The first archive
will contain everything to date. The new log will start at the
first current month's date StatusC finds in the current month's
part of the log. Bulletins generated will show information only
for the current month and from this point on each rollover
archive will contain only the previous month's log.
Errors
Errors are written to the same directory as STATUSC.EXE in a
file called STATUSC.ERR. If the file already exists additional
errors are appended to the end of the file. It may be deleted
after you have made note of any errors. It's existence it not
required by the program.
During the start up procedures that program displays
"Searching!" while it is looking for the directory STATUSC.EXE is
located in. Also "Configuring!" while it is reading in and
verifying all information in the configuration file. These are to
show you what the program is doing should lockups occur. I had
problems in these areas and took some time to isolate them. At
least now these problem areas can be isolated. Normally these two
displays should be very quick and unreadable depending on system
speed and StatusC's configuration.
If StatusC has trouble with the log files, like finding
it/them, it first tries to create a "no data bulletin" and do an
normal error exit. If it cannot create these bulletins is makes
the error exit that displays the help screen. These two exits
would normally be an error in the configuration file: wrong path,
wrong file name, configuration file name not used, etc.
Cam-Mail's EXPORT.EXE and IMPORT.EXE
Follow your instructions in CAM-MAIL.DOC on calling your
EXPORT.EXE and IMPORT.EXE programs and your network definition
setup(s). Make sure you have the /LOG switch on both the
IMPORT.EXE and EXPORT.EXE. Examples follow:
EXPORT INTELEC /LOG
IMPORT INTELEC /LOG
Other options may be used on the command line. My examples
are just to make sure you have the log option turned on. StatusC
must find both Exports and Imports in the log(s). You then call
StatusC with a configuration file that contains the name of the
network definition produced log. Example shows Intelec as both
the network name and network definition name and these might not
actually be the same:
(1) Unregistered BBS
(2) 0000
(3) Intelec
(4) INTELEC.LOG
(5) C:\BBS\BLT7
(6) INTELEC.LOG
(7) C:\BBS\BLT77
(8) C:\BBS\BLT777
(9) ANSI2
If you have more than one network you must have a
configuration file or files for each one. Line #3 would contain
the next network name and lines #4 and #6 would contain the names
of the next network log. This would be repeated for as many
networks as you have Cam-Mail configured for.
Perhaps you want to make a bulletin with the PCBoard @X0
codes and one using straight ASCII codes and yet another using
ANSI codes. The .CFG files would contain the bulletin names and
the form setting (#9):
STATUSC STATUSC.CFG
(.CFG with PCB, uses ANSI codes and IBM extended graphic
characters)
STATUSC STATUSC2.CFG
(.CFG with ASCII, ASCII and no IBM extended graphic
characters)
STATUSC STATUSC3.CFG
(.CFG with ANSI, ANSI colors and no IBM extended graphic
characters)
You just call StatusC as many times as needed, with as many
configuration files as needed to generate whatever formats you
want for each network that you have. On my 386/33 it takes less
than twenty seconds to run the program on a 6,500 line test log
(from three BBS systems).
The StatusC Program
If you don't like the program please write to me and explain
why. Send me any suggestions you might have. If they enhance the
overall program I will try to incorporate part, some, all, in the
next release.
The program package represents many hours of programming,
testing, updating and more testing as well as LD telephone calls
to distribute the beta and release copies. Please support my
efforts and register your copy.
PKZIP.EXE used by the StatusC Program
"PKZIP.EXE" must be somewhere in your path or in the current
directory. When the month changes in the CAM-MAIL.LOG the program
archives the current log into a file using 'ML'+ the current date
(ML010193.ZIP, etc.). It also includes the current log (1 or 2)
and all three bulletins. It creates this in the directory that
contains the log file (import log if two logs used). The program
then rewrites the log using only the current new month's data.
This way there is only one month's log data in your Cam-Mail
log(s).
I have corrected the archiving problems with the log(s)
while SHARE.EXE is loaded. This was not my error, but something
with DOS, Share and Borland's Pascal. I don't know who is at
fault.
The bulletins are added to the archive so the last
information posted on the BBS before rollover is available should
this information be required by the you.
If you do not want the previous month's log(s) simply delete
the archive from your hard drive. In your calling batch file you
can add "IF EXIST ML*.ZIP DEL ML*.ZIP" and this will auto-delete
the archive.
If the program has any problems with your log(s) such as
file not found, no exported conferences found, a bulletin is
generated showing that there was an error in the log and that no
imported/exported messages were found. The program aborts on
these errors. The program confirms each item in the configuration
file before it does anything else. See errors below
There must be at least one meg of free disk space for the
archive to be executed. I have no idea the possible sizes and if
anyone has problems with the archive with one meg as the minimum
please let me know and I will increase the size of the free space
required. I have been unable to trap PKZIP.EXE errors from within
my Turbo Pascal 7.0 programs. I believe PKZIP handles them and
does not pass them along to operating system.
StatusC Registration
Send BBS information and one of the following in $ U.S.
(1) Registration only via routed Rime node ID.........$10
Not a safe or reliable form of registration.
(2) Registration only via mail........................$10
(outside U.S. please add $2) Better registration.
(3) Registration and latest version via mail......... $12
(outside U.S. please add $4) Include diskette size.
(4) Registration and latest version via mail and
copy of all James Huckabey Doors and PC software..... $15
(outside U.S. please add $5) Include diskette size.
(5) Limited Special Registration of Status and StatusC
add $5 to any of the above options. *** Offer good only
through August 15, 1993 ***
Option: 1: [ ] 2: [ ] 3: [ ] 4: [ ] 5: [ ]
Diskette Size: 360: [ ] 1.2: [ ] 720: [ ] 1.44: [ ]
Your current version number: [ ]
Please supply name of BBS to be added to program, up to sixty
characters. Anything longer will be truncated, no exceptions.
This is to be on one line of code and must be legible since the
serial number is based on exact syntax. I cannot be responsible
for unreadable data. Please print. Case sensitive!
Example: "Jim's Graphic BBS". In StatusC it comes out as the
following in all bulletins generated:
==================(Jim's Graphic BBS)==================
[-------------------------------------------------------------]
FROM:
Your Name:
---------------------------------------------------
Address:
---------------------------------------------------
City:
---------------------------------------------------
State & Zip:
---------------------------------------------------
HUB ID: NODE ID:
---------------------- --------------------
Phone(voice): (data)
--------------------- ---------------------
Your registration number and any diskettes, if requesting
current version or other software, are sent by return mail or via
Rime and routed Node ID if this is your choice. E-Mail is not
that reliable.
James Huckabey
3621-A Fraser Street
Bellingham, Washington 98226 U.S.A.
(206) 671-2868 (voice) I do have a USR 14.4 DS!
You can also contact me at:
Corporate Headquarters BBS
Sysop: Bob Neal
RelayNet (tm): CHQBBS (#1255)
(815) 886-3233 or 886-9381 (14400 V32bis)