Category : BBS Programs+Doors
Archive : MSGTOS2C.ZIP
Filename : MSGSWI.DOC
Output of file : MSGSWI.DOC contained in archive : MSGTOS2C.ZIP
MSGTOSS Version 2.0
High-Performance FidoNet Mail Processor for RBBS-PC
Copyright(c) 1989-92, Mike Zakharoff & Warren Muldrow
Mike : FidoNet 1:138/154 Rbbsnet 8:918/10
Warren: FidoNet 1:3617/1 Rbbsnet 8:928/1
ALL RIGHTS RESERVED
R E F E R E N C E M A N U A L
for
MSGTOSS Command Line Switches
Written by Mike Zakharoff
The MSGTOSS supports a multitude of command line switches to support vari-
ous aspects of tossing, scanning, and maintenance functions. MSGTOSS has
nine major command line switches each of which calls a special function of
MSGTOSS. For instance, to execute the tossing mode of MSGTOSS, the command
line /TOSS initiates the session. Each major switch and its associated
sub-switches are discussed in detail.
MSGTOSS supports 'Meta-Commands' where an unlimited number of command lines
can be defined and reduced to a single command entry.
DISCLAIMER
----------
The authors make no claims or warranties with respect to the contents or
accuracy of this publication, or the product it describes, including any
warranties of fitness or merchantability for a particular purpose. Any
stated or expressed warranties are in lieu of all obligations or
liability for any damages, whether special, indirect, or consequential,
arising out of or in connection with the use of this publication or
the product it describes. Furthermore, the right is reserved to make any
changes to this publication without obligation to notify any person
of such changes.
MSGTOSS 2.0 Command Line Switches
L I C E N S E
-------------
MSGTOSS is not a Public Domain program and is not free. MSGTOSS is
copyright(c) 1989,1990,1991,1992 by Mike Zakharoff and Warren Muldrow.
Non-registered users of this program are granted a two week license to
evaluate the program suitability for their requirements. Any usage of
Msgtoss beyond evaluation time period requires registration. Use of non-
registered copies of Msgtoss beyond the original evaluation period is not
wished. You are free to distribute the PUBLICLY AVAILABLE shareware version
of MSGTOSS.
MSGTOSS is SHAREWARE. MSGTOSS was not an easy project, as it took 1000's
of hours to develop and test. The author has written other RBBS utilities
such as MSGRENUM, MAILWAIT, MSGECHO, FIXMSG, all of which were released as
freeware; none of which compares to the complexity of MSGTOSS. Fu-
ture releases of MSGTOSS will depend upon how much support the author
receives. Therefore the author is asking $25.00 for its use to:
MIKE ZAKHAROFF
18004 22ND ST CT E
SUMNER, WA 98390
Keep in mind that the authors could have easily crippled MSGTOSS with all
sorts of schemes, including disabling the multi-tasking/network support,
requiring a password, annoying "not-registered" lines appended to the tear
line, beg screens, long delays, and other things to pester you to support
the authors. If I were to figure out the amount of hours it took to devel-
op and test this program, it would easily run into 10,000 hours of personal
time that really can't be assigned any value. This was a service to the
RBBS-PC community, and its development will set the stage for RBBS-PC's fu-
ture in the Fidonet comminity. Cards and letters always welcome!
Registered users will receive a personal registration code (See REGCODE in
MSGCFG.DOC), and as much personal support as possible. Non-supporters
will basically be doomed to slither in their own guilt for all eternity.
WARRANTIES
----------
MSGTOSS is guaranteed only to occupy space on your hard drive. Therefore
the use of MSGTOSS is solely at your own risk! MSGTOSS had been beta
tested extensively to eliminate bugs, however due to the limitless pos-
sibilities of system configurations, no warranty is possible. Also,
there are no guarantees that the author will upgrade MSGTOSS.
TRADEMARKS
----------
The following products are mentioned in this document:
Desqview,Makearc,Ommm,Qmail & Rbbs-pc
Page - 2
MSGTOSS 2.0 Command Line Switches
TABLE OF CONTENTS
-----------------
Page
Major command line switches ............................ 6
Command Line Switches - COMMON ........................ 7
COMMON SWITCH MATRIX ................................ 7
/CFG:xxx ............................................ 7
/BBS:xxx ............................................ 7
/LOCK ............................................... 8
/FIX ................................................ 8
/FIXC ............................................... 8
/WDIR ............................................... 8
/AREA:xxx,xxx,xxx ................................... 9
/AREAF:File.Ext ..................................... 9
/DDA ................................................ 10
/COUNT .............................................. 10
/TOSS - Toss RBBS, FIDO & NETMAIL messages ............. 11
/TOSS SWITCHES (BASIC) .............................. 11
/TOSS ............................................ 11
/PREP ............................................ 11
/PREX ............................................ 11
/TUNK ............................................ 12
/TCAP ............................................ 12
/NSTOP ........................................... 12
/LOCK ............................... (COMMON) ... 12,8
/FIX ................................ (COMMON) ... 12,8
/FIXC ............................... (COMMON) ... 13,8
/WDIR ............................... (COMMON) ... 13,8
/DDA ................................ (COMMON) ... 13,10
/TOSS SWITCHES (ADVANCED) ........................... 13
/FEED ............................................ 13
/FMAX:xxx ........................................ 13
/KNET ............................................ 14
/KUNK ............................................ 14
/KRTE ............................................ 14
/PKTS:xx ......................................... 14
/DLOG ............................................ 14
/DKP ............................................. 14
/OPUS ............................................ 15
/MUSER:xx ........................................ 15
/CFG:File.Ext ....................... (COMMON) ... 16,7
/BBS:File.Ext ....................... (COMMON) ... 16,7
/AREA:xxx,xxx ....................... (COMMON) ... 16,9
/AREAF:File.Ext ..................... (COMMON) ... 16,9
Page - 3
MSGTOSS 2.0 Command Line Switches
TABLE OF CONTENTS (continued)
-----------------
Page
/SCAN - Scan (export) new locally entered mail ......... 17
MIRROR SCANNING...................................... 17
/SCAN SWITCHES (BASIC) .............................. 17
/SCAN ............................................ 17
/RBBS ............................................ 18
/FIDO ............................................ 18
/LOCK ............................... (COMMON) ... 18,8
/FIX ................................ (COMMON) ... 18,8
/FIXC ............................... (COMMON) ... 18,8
/DDA ................................ (COMMON) ... 18,10
/SCAN SWITCHES (ADVANCED) ........................... 18
/RSCAN:zone:net/node ............................. 18
/HWM ............................................. 19
/CFG:File.Ext ....................... (COMMON) ... 19,7
/BBS:File.Ext ....................... (COMMON) ... 19,7
/WDIR ............................... (COMMON) ... 19,8
/AREAF:File.Ext ..................... (COMMON) ... 19,9
/AREA:xxx,xxx ....................... (COMMON) ... 19,9
/SIZE - Chop message bases to preset SIZE .............. 20
/SIZE ............................................... 20
/SIZE-UP ............................................ 21
/CFG:File.Ext .......................... (COMMON) ... 21,7
/BBS:File.Ext .......................... (COMMON) ... 21,7
/LOCK .................................. (COMMON) ... 21,8
/FIX ................................... (COMMON) ... 21,8
/FIXC .................................. (COMMON) ... 21,8
/WDIR .................................. (COMMON) ... 21,8
/MWRST - Reset users Mailwaiting Bit (all msgs) ........ 22
/MWRST .............................................. 22
/CFG:File.Ext .......................... (COMMON) ... 22,7
/BBS:File.Ext .......................... (COMMON) ... 22,7
/LOCK .................................. (COMMON) ... 22,8
/FIX ................................... (COMMON) ... 22,8
/FIXC .................................. (COMMON) ... 22,8
/WDIR .................................. (COMMON) ... 22,8
/STAT - Report on message base statistics .............. 23
/STAT ............................................... 24
/COUNT ................................. (COMMON) ... 24,10
/CFG:File.Ext .......................... (COMMON) ... 24,7
/BBS:File.Ext .......................... (COMMON) ... 24,7
/LOCK .................................. (COMMON) ... 24,8
/FIX ................................... (COMMON) ... 24,8
/FIXC .................................. (COMMON) ... 24,8
Page - 4
MSGTOSS 2.0 Command Line Switches
TABLE OF CONTENTS (continued)
-----------------
Page
/TEST - Test MsgToss Setup Configuration ............... 25
/TEST ............................................... 25
/COUNT ................................. (COMMON) ... 26,10
/CFG:File.Ext .......................... (COMMON) ... 26,7
/BBS:File.Ext .......................... (COMMON) ... 26,7
/LOCK .................................. (COMMON) ... 26,8
/FIX ................................... (COMMON) ... 26,8
/FIXC .................................. (COMMON) ... 26,8
/WAIT - Wait for users, create MSGWAIT.BAT file ........ 27
/WAIT ............................................... 27
/CFG:File.Ext .......................... (COMMON) ... 27,7
/BBS:File.Ext .......................... (COMMON) ... 27,7
/LOCK .................................. (COMMON) ... 27,8
/GLOB:xxx - Globally execute xxx for all msg bases ..... 28
/GLOB:xxx ........................................... 28
/GBAT ............................................... 29
/CFG:File.Ext .......................... (COMMON) ... 29,7
/BBS:File.Ext .......................... (COMMON) ... 29,7
/LOCK .................................. (COMMON) ... 29,8
/NLST - Recompile the node list (MSGTOSS.NOD) .......... 30
/NLST ............................................... 30
/EID - Execute MSGEID.EXE - EID Database Maintenance .. 31
/EID ................................................ 31
Display MSGTOSS.EID index ........................ 31
Make MSGTOSS.CFG parameters match ................ 32
Pack (remove dead space) ......................... 32
Clear a particular AREA ........................ 32
Clear all inactive AREAs ....................... 32
Clear all NODE:x AREAs ....................... 32
Change all NODE:x to NODE:y ...................... 32
Display EID data for AREA ........................ 32
Change MAXAREAS & DUPSIZE ........................ 32
MSGTOSS.CMD Meta-Commands - (no slashes) ............... 33
MSGTOSS Meta-Commands ............................... 33
SUMMARY ............................................. 33
MSGTOSS ErrorLevel Semaphore File Codes - Errorlevels .. 34
ERRORLEVELS ......................................... 34
INDEX (See MSGIDX.DOC).................................. <-
Page - 5
MSGTOSS 2.0 Command Line Switches
Major command line switches
---------------------------
MSGTOSS is a comprehensive mail processor for RBBS systems. As a con-
sequence, there are currently 41 command line switches, over 46
MSGTOSS.CFG configuration parameters and 19 MSGTOSS.BBS keywords that
all interrelate with one another. This tremendous number of interre-
lated system configuration items demonstrates the amount of flexibility
built into MSGTOSS.
In addition to tossing and scanning messages, it has other non-mail
utilities built-in. Because of this, there are TEN MAJOR command line
switches, which tell MSGTOSS what major operation is being requested.
When a major command line switch is issued, any other switches not re-
lated to the major operation are ignored. You cannot issue TWO major
command line switches simultaneously. For purposes of this documenta-
tion, these will be referred to as 'major command line switches'. Here
are the TEN major command line switches.
1) Toss RBBS, FIDO & NETMAIL messages -------> /TOSS
2) Scan (export) new locally entered mail ---> /SCAN
3) SIZE message bases to preset RECS:xxx ----> /SIZE
4) Reset users Mailwaiting Bit (all msgs) ---> /MWRST
5) Report on message base statistics --------> /STAT
6) Test MsgToss Setup Configuration ---------> /TEST
7) Wait for users, create MSGWAIT.BAT file --> /WAIT
8) Globally execute xxx for all msg bases ---> /GLOB:xxx
9) Recompile the node list (MSGTOSS.NOD) ----> /NLST
10) Execute MSGEID.EXE - EID Database Maint --> /EID
NOTE: Executing MSGTOSS
display. You can then enter the number of the major command line
switch, then all related switches are displayed along with a de-
scription and purpose.
------------------------> ATTENTION! <------------------------
Read the above paragraph carefully! Alot of questions about set-
ting up MSGTOSS can be answered by simply entering 'MSGTOSS
mand line switches (associated with the major command line
switch) with its built-in help function.
----------------------------------------------------------------------
Page - 6
MSGTOSS 2.0 Command Line Switches
Command Line Switches - COMMON
-------------------------------
MSGTOSS has ten command line switches that are shared between the major
switches. If a command line switch is shared between two (or more) ma-
jor switches, it is considered a 'common' command line switch.
Here is a summary of the common command line switches, along with its
associated major switches.
COMMON SWITCH MATRIX
--------------------
Common Major Switches
---------- ---------------------------------------------------
/CFG: - /TOSS /SCAN /SIZE /MWRST /STAT /TEST /WAIT /GLOB:xx
/BBS: - /TOSS /SCAN /SIZE /MWRST /STAT /TEST /WAIT /GLOB:xx
/LOCK - /TOSS /SCAN /SIZE /MWRST /STAT /TEST /WAIT /GLOB:xx
/FIX - /TOSS /SCAN /SIZE /MWRST /STAT /TEST
/FIXC - /TOSS /SCAN /SIZE /MWRST /STAT /TEST
/WDIR - /TOSS /SCAN /SIZE /MWRST
/AREA: - /TOSS /SCAN
/AREAF: - /TOSS /SCAN
/DDA - /TOSS /SCAN
/COUNT - /STAT /TEST
Another way of looking at the above matrix, probably more useful:
Major Common Switches
----------- ------------------------------------------------------
/TOSS - /CFG: /BBS: /LOCK /FIX /FIXC /WDIR /AREA: /AREAF: /DDA
/SCAN - /CFG: /BBS: /LOCK /FIX /FIXC /WDIR /AREA: /AREAF: /DDA
/SIZE - /CFG: /BBS: /LOCK /FIX /FIXC /WDIR
/MWRST - /CFG: /BBS: /LOCK /FIX /FIXC /WDIR
/STAT - /CFG: /BBS: /LOCK /FIX /FIXC /COUNT
/TEST - /CFG: /BBS: /LOCK /FIX /FIXC /COUNT
/WAIT - /CFG: /BBS: /LOCK
/GLOB:xx - /CFG: /BBS: /LOCK
/CFG:xxx
-------
Use alternate MSGTOSS.CFG file. This is useful for those who
need to separate various *.BBS files and who use a multitude of
mail processing utilities. In other words, if you use this switch,
you are probably a HUB of some sort.
Used with: /TOSS /SCAN /SIZE /MWRST /STAT /TEST /WAIT /GLOB:xx
-------------------------------------------------------------------
/BBS:xxx
--------
Use alternate MSGTOSS.BBS file. This is useful for those who
need to separate various *.BBS files and who use a multitude of
Page - 7
MSGTOSS 2.0 Command Line Switches
mail processing utilities. In other words, if you use this
switch, you are probably a HUB of some sort.
Used with: /TOSS /SCAN /SIZE /MWRST /STAT /TEST /WAIT /GLOB:xx
------------------------------------------------------------------
/LOCK
------
Invoke multi-tasking/network file locking protocols in accordance
with the LOCKTYPE----> parameter (see MSGCFG.REF). Available pro-
tocols include DESQVIEW, NETBIOS, PC-NET and 10-NET.
MSGTOSS adheres to standard file/record locking protocols
used by RBBS-PC when tossing/purging/sizing message bases.
MSGTOSS will flash "status" lights in the lower right-hand corner
of the status of the LOCKING mechanism for both the USERS and MES-
SAGES files being processed.
When using NETBIOS, MSGTOSS will use the MESSAGES----> parameter,
to determine which directory to write/create the IBMFLAGS file used
with NETBIOS.
For more information, see LOCKTYPE--->, LOCKTIME--->, LOCKWAIT--->
(in MSGCFG.REF) and MULTITASKING/NETWORK SUPPORT (in MSGTOSS.DOC).
------------------------------------------------------------------
/FIX
------
If you add the switch /FIX to the command line, then MSGTOSS will
automatically SHELL to FIXMSG (Version 1.4, Mike Zakharoff, avail-
able as FIXMSG14.xxx) if it detects a corrupt message file
while doing the purge. It will execute FIXMSG twice, and if it
still fails to correct the problem MSGTOSS will abort.
NOTE: Also see /FIXC.
Used with: /TOSS /SCAN /SIZE /MWRST /STAT /TEST
------------------------------------------------------------------
/FIXC
------
If you use the switch /FIXC switch (vice just /FIX), MSGTOSS will
do the same as /FIX, but if the repair failed will copy the BLANK
message base (model) as specified by the BLANKMSG---> parameter
over the corrupt message base, and rename it to *.BAD. This pre-
vents MSGTOSS from aborting due to a corrupt message base.
Used with: /TOSS /SCAN /SIZE /MWRST /STAT /TEST
------------------------------------------------------------------
/WDIR
------
To obtain faster purging, mailwaiting and sizing MSGTOSS can be
configured to use a work directory. This is set via the WORKDIR--
--> parameter. If a RAM disk, MSGTOSS will first copy the message
base to the RAM disk (if enough room exists) and will purge the
message base as required. After purging, MSGTOSS will then copy it
Page - 8
MSGTOSS 2.0 Command Line Switches
back automatically. In addition, if paging excess users to the
disk is required, MSGTOSS will use the work directory for faster
operation. MSGTOSS will also use this directory for other disk in-
tensive tasks when needed.
NOTE: If using multi-tasking/network support, MSGTOSS will not copy
the message base to the ram disk, as a possibility exists
where users may be on-line.
Used with: /TOSS /SCAN /SIZE /MWRST
NOTE: Does NOT have to be a RAM disk.
------------------------------------------------------------------
/AREA:xxx,xxx,xxx
------
Allows tossing only one selected echo area (/AREA:COMM) or mul-
tiple echo areas (separated by commas). The use of this command
WILL NOT delete the *.PKT file after completion of tossing UNLESS
all of the messages happened to be tossed properly. In other
words, the *.PKT files will still be available for further process-
ing. Example:
MSGTOSS /TOSS /PREP /AREA:COMM
Will ONLY toss the echomail in the COMM conference
Used with: /TOSS /SCAN
------------------------------------------------------------------
/AREAF:File.Ext
------
This works in conjunction with /SCAN, /RSCAN or /TOSS, and func-
tions exactly the same as the /AREA:xxxx,xxxx,xxx switch, except
the echo names are derived from a plain ascii file. The most use-
ful purpose for this is for FIDO scanning where you can process
CONFMAIL.OUT that is generated by most fido editors, and only scan
those areas listed.
A plain ascii file exists that contains a list of echos to pro-
cess, as follows:
RBBS-PC
NETMAIL
COMM
FORSALE
If this file is called CONFMAIL.OUT then execute as follows.
MSGTOSS /SCAN /FIDO /RBBS ..... /AREAF:CONFMAIL.OUT
Used with: /TOSS /SCAN
------------------------------------------------------------------
Page - 9
MSGTOSS 2.0 Command Line Switches
/DDA
----
Don't Display (tossing and scanning) Activity. Will significantly
increase the speed of tossing and scanning, as informational mes-
sages regarding which messages are tossed where will be suppressed.
Also see /NSTOP switch.
Used with: /TOSS /SCAN
------------------------------------------------------------------
/COUNT
------
The /COUNT switch is used with the /STAT & /TEST switches, which
will force MsgToss to do an actual count of the messages in each
area instead of estimating. This will allow for non-sequential
numbering that may result from deleted messages. If an error is
encountered during the count process, MsgToss will attempt to fix
the message base depending if the command line contained /FIX or
/FIXC switches.
Used with: /STAT /TEST
------------------------------------------------------------------
Page - 10
MSGTOSS 2.0 Command Line Switches
Toss RBBS, FIDO & NETMAIL messages - /TOSS
------------------------------------------
/TOSS SWITCHES (BASIC)
--------------
/TOSS
------
The /TOSS major command line switch signals MSGTOSS to start a
carefully planned sequence, used more often than any other
switch. There are 7 phases to the TOSSING of messages:
1) Un-Pack mail packets
2) Identify domain/zone/net/node of *.PKT files
3) Analyze *.PKT files
4) Purge/expand RBBS message bases as required
5) Toss messages (RBBS message bases or Fido)
6) Set the mailwaiting bit for conference users
7) Create a MSGTOSS.LOG file for message base activity
8) Create miscellaneous BAT/CMD/CTL files for other maintenance.
NOTE: See MSGTOSS THEORY OF OPERATION for a description of each
phase of the above.
------------------------------------------------------------------
/PREP
------
Will pre-purge the message bases before tossing (used most often).
MSGTOSS will either PURGE the message bases or EXPAND (or both)
prior to tossing. If you specified the /PREP switch (pre-purge),
MSGTOSS will first load all of the USERS in a particular con-
ference in memory (see NOTE:), and will commence to purge
non-user messages. This is accomplished via a 'pack-in-place'
method, where the messages flagged to keep will be 'shuffled'
to the beginning of the RBBS message base, as others are being
deleted.
NOTE: MSGTOSS will purge ONLY ENOUGH messages for successful impor-
tation. Therefore, if only 2-3 messages are received in a
particular conference, then roughly the same amount will
be purged (if there isn't enough space to begin with).
NOTE: For any sort of tossing activity, /PREP or /PREX is required.
This informs MSGTOSS what to do in case there is not enough
room available in the respective RBBS message base.
NOTE: If the BBS keyword HIST:1 is true, then all purged messages
will be exported (text format) to a history file.
------------------------------------------------------------------
/PREX
------
If you specified the /PREX (pre-expand) switch, then MSGTOSS will
simply EXPAND the message base as it sees fit and continue on. At
Page - 11
MSGTOSS 2.0 Command Line Switches
a later time (say at a night event) to can CHOP the message bases
back down to their original size by issuing the /SIZE or /SIZE-UP
switches.
------------------------------------------------------------------
/TUNK
------
The /TUNK switch allows tossing UNKNOWN messages from #.MSG into
M.DEF format. If you specify /TUNK on the command line, MSGTOSS
will (if the UNKNOWN area is a FIDO sub directory) analyze and toss
messages that were previously UNKNOWN.
NOTE: Assuming that a previously UNKNOWN message becomes KNOWN, and
the area UNKNOWN is a Fido-Style area, you can toss these
messages into RBBS format via the /TUNK (toss unknown)
switch. The most likely reason for a message to be unknown
is either an omission of the subject area in the MSGTOSS.BBS
file or an improper link between node and host.
The /TUNK switch is meant to be used only when necessary. Placing
it permanently on the /TOSS command line will slow down processing.
It was not meant to be something used to import #.MSG on a regular
basis. Any messages that are still UNKNOWN will be ignored.
NOTE: It is not necessary to have a *.PKT file to process to
execute this switch, so the minimum command line is 'MSGTOSS
/TOSS/TUNK ....other switches' for this.
------------------------------------------------------------------
/TCAP
-----
The /TCAP (Toss MSGCAPTURE) switch provides the same services as
the /TUNK switch, but for messages 'captured' in the MSGCAPTURE di-
rectory. Also see CAPTURE-----> and CAPT:x
NOTE: Those familiar with the /TCAP switch usually use a nightly
event to toss captured messages.
------------------------------------------------------------------
/NSTOP
------
MSGTOSS allows interruption of tossing or analyzing by simply hitt-
ing any key. If this occurs, MSGTOSS will abort as soon as it is
done with the current *.PKT file. Using /NSTOP will allow slightly
FASTER operation because it will not have to check for keyboard in-
put. Also see /DDA switch.
-------------------------------------------------------------------
/LOCK (COMMON)
------
Invoke multi-tasking/network support. See page 8 for more details.
-------------------------------------------------------------------
/FIX (COMMON)
------
Auto-repair RBBS M.DEF(s) via FIXMSG. See page 8 for more details.
------------------------------------------------------------------
Page - 12
MSGTOSS 2.0 Command Line Switches
/FIXC (COMMON)
------
Auto-repair RBBS M.DEF(s) via FIXMSG. See page 8 for more details.
------------------------------------------------------------------
/WDIR (COMMON)
------
Use RAM disk for faster operation. See page 8 for more details.
------------------------------------------------------------------
/DDA (COMMON)
----
Don't display (toss/scan) activity. See page 10 for more details.
------------------------------------------------------------------
/TOSS SWITCHES (ADVANCED)
--------------
/FEED
------
If you are a HUB, or you support POINTS, MSGTOSS can simultaneously
create *.OUT files addressed to your nodes/points by using the
/FEED switch on your /TOSS command line. Using this switch will
automatically feed your nodes & points as MSGTOSS is tossing to
your RBBS message bases (M.DEF) or #.MSG format.
NOTE: The use of the switch requires alot of more extra processing
(SEEN-BY lines, etc.). If you are simply a static node DON'T
use this switch.
NOTE: The /FMAX:xxx switch is normally used with this switch.
------------------------------------------------------------------
/FMAX:xxx
------
For HUBS, when doing a /FEED, MSGTOSS will either exit processing
or SHELL out to a packer when /FMAX:xxx messages have been ex-
ported. This allows MSGTOSS to gracefully exit, pack up to *.OUT
file generated, then continue processing until all are complete.
The CFG entry is PACKERCMD----> The switch is /FMAX:xxx (short for
/FEED Maximum) And they work together. For instance:
PACKERCMD--->QMAIL -PACK --or--
PACKERCMD--->OMMM --or--
PACKERCMD--->MAKEARC etc.
And /FMAX:1000 is added as a switch:
MSGTOSS will, after exporting 1000 messages (in any combination to
any set of nodes), and done with the current PKT file, close ALL
*.OUT files, and SHELL out to PACKERCMD. When done, will return
back, re-open *.OUT files, and continue on.
NOTE: If PACKERCMD---> is blank ("") then MSGTOSS will exit.
Page - 13
MSGTOSS 2.0 Command Line Switches
For more information, see PACKERCMD---> in MSGCFG.DOC.
------------------------------------------------------------------
/KNET
------
Kill (ignore) NETMAIL messages. This is useful for HUB's where an-
other tosser handles NETMAIL and routing (like QMAIL).
Previously, you would have to use a 'dummy' directory and clear it
out after a toss. This is normally used in conjunction with the
/KRTE switch also.
NOTE: You still need to have an area called NETMAIL.
------------------------------------------------------------------
/KUNK
------
Kill (ignore) messages that have UNKNOWN areas. This is useful for
HUB's where another tosser handles feeding of downstream nodes, but
you want to use the complete *.PKT files, even though they contain
echomail that your local system (M.DEFs) do not carry. This switch
is sometimes used with the /DKP (Don't Kill Packets) switch to al-
low this 'double processing'.
NOTE: You still need to have an area called UNKNOWN.
------------------------------------------------------------------
/KRTE
------
Kill (ignore) ROUTEMAIL messages. This is useful for HUB's where
another tosser handles NETMAIL not addressed to your system (like
QMAIL). Previously, you would have to use a 'dummy' directory and
clear it out after a toss.
NOTE: The area ROUTEMAIL is still optional, but having it and using
this switch serves no useful purpose. Normally, this is used
with the /KNET switch.
------------------------------------------------------------------
/PKTS:xx
------
Process only if there are at least xx packets present. Useful for
HUBS where small *.PKTs trickle in, and you only want to go through
a complete tossing process until there are enough *.PKTs available
to warrant it. Will gracefully exit with errorlevel if less than
xx packets are present.
------------------------------------------------------------------
/DLOG
------
Will append the following information to a file called
MSGTOSS.DUP whenever a duplicate is detected. MSGTOSS.DUP contains
the following information... DATE, PKT, PKT MSG, AREA and WHO
FROM (Net/Node) for tracking information.
NOTE: This only applies when the CDUP:1 keyword is active.
------------------------------------------------------------------
Page - 14
MSGTOSS 2.0 Command Line Switches
/DKP
------
Don't Kill Packets. Intended in hubbing situations where you wish
to keep the *.PKT files for further processing. This will delete
the *.IDX file but will leave the *.PKT file available for other
processors (like for HUB work). Be extremely careful, as if your
other mail processor crashed and *.PKT files are left in the
MSGTOSS files directory, then MSGTOSS will happily re-process them.
For safety sake, it would be better to IMMEDIATELY move the
*.PKT files to another directory after MSGTOSS has processed them.
------------------------------------------------------------------
/OPUS
------
MSGTOSS now supports OPUS-Style dates (date-written & date-arr-
rived) for #.MSG files. Some utilities such as Hector Santos's
Silver Express (off-line reader for RBBS, among others) require
these special dates to be written in the message header.
NOTE: Don't add it unless necessary, as it requires a little extra
processing.
------------------------------------------------------------------
/MUSER:xx
------
While MSGTOSS is tossing mail, you can have it constantly update
one of the RBBS-PC node-records of the main message base via the
/MUSER:x command line switch, where x is the node number MSGTOSS
will permanently occupy. Example:
You run TWO nodes. If you enter /MUSER:3 on the /TOSS command
line, MSGTOSS will update node record #3 of the main message base
and act just like another user on-line. Users who enter the [W]ho
function on the main menu will then see a display similar to this:
Node 1 Online at 9600 BAUD: SYSOP KENT ,WA
Node 2 Online at 2400 BAUD: JOHN HENDRICKS SEATTLE,WA
Node 3 Online at 9600 BAUD: MsgToss 2.0 - Mail System PURGING MSG BASES
When MSGTOSS goes off-line, the node record will still exist and
the SYSOP can then see when the last mail run was. Creative sysops
can disable RBBS-PC(s) requirement to show 'Waiting for next cal-
ler' then the node record actually shows 'off-line' by making a
simple code change in the RBBS-PC '[W]hos on' source code.
NOTE: See MSGTOSS.DOC, "Modify RBBSSUB2.BAS to Support /MUSER:x" to
find the code modification to RBSSUB2.BAS to provide the
above feature.
Then all users will see even those that are off-line, including
MSGTOSS, example:
Node 3 Offline at 300 BAUD: MsgToss 2.0 - Mail System Last: 01-23 15:14
MSGTOSS will now permanently occupy position number three of the
MAIN RBBS MESSAGE base... this means that when MSGTOSS is busy
tossing, purging, mailwaiting... etc. a REAL USER on your system
Page - 15
MSGTOSS 2.0 Command Line Switches
can execute the [W]ho Else is ON function on the main menu, and the
user can see that MSGTOSS is currently ONLINE, tossing, purging,
etc... The user is MSGTOSS, and the city/state is the MSGTOSS
'status' of what it is currently doing.
Make sure you DON'T specify a node number where its possible that a
REAL user could be on-line.. MSGTOSS should always have its OWN
node line, so its always there (like #3). If you specify /LOCK on
the command line, then MSGTOSS will use file locking procedures (as
it should) before it messes with the node records.
If you enter 'MSGTOSS /MUSER:0' then MSGTOSS will clear any node
records that contain the text "MSGTOSS".
If you DON'T run multiple nodes, then this switch is worthless, un-
less you use one of those 'This was the LAST user on the system'
utilities.
------------------------------------------------------------------
/CFG:File.Ext (COMMON)
------
Use alternate MSGTOSS.CFG file. See page 7 for more details.
------------------------------------------------------------------
/BBS:File.Ext (COMMON)
------
Use alternate MSGTOSS.BBS file. See page 7 for more details.
------------------------------------------------------------------
/AREA:xxx,xxx,xxx (COMMON)
------
Only toss/scan /AREA:xxx,xxx,xxx. See page 9 for more details.
------------------------------------------------------------------
/AREAF:File.Ext (COMMON)
------
Only toss/scan areas in File.Ext. See page 9 for more details.
------------------------------------------------------------------
----------------------------------------------------------------------
Page - 16
MSGTOSS 2.0 Command Line Switches
Scan (export) new locally entered mail - /SCAN
----------------------------------------------
MSGTOSS will scan M.DEF or #.MSG messages for new messages, and export
them to all the NET/NODES in the MSGTOSS.BBS file for its associated
area. More information on this exists in MSGTOSS.DOC (/SCAN section).
For RBBS message bases, when MSGTOSS has finished exporting a message,
it will append a '
or the sysop know that the message has been exported. During a MSGTOSS
purge operation (/PREP or /SIZE), MSGTOSS will replace these
lines with the default origin line, or the origin line as defined by
the ORGN: keyword(s). The reason for this odd method is to allow full
scanning features while users are on-line.
When exporting a FIDO message (#.MSG), msgtoss will set the 'sent' bit,
preventing re-exportation.
The whole /SCAN operation can be executed safely even though users are
on-line, as MSGTOSS will use full multi-tasking/network record locking
protocols (using /LOCK, as defined by LOCKTYPE----->) during a /SCAN,
allowing fully safe scanning.
MIRROR SCANNING
---------------
MSGTOSS 2.0+ provides a notable feature called "mirror-scanning", where
if you have a double-tossed area (RBBS + FIDO, for one area), then if a
user entered a message in the RBBS conference, when exported, will also
create a "carbon copy", complete with Origin: line, in the Fido-Style
directory as well. The same applies to when a user (or yourself) en-
ters a message in a Fido-Style conference, when exported, will create a
carbon copy in the RBBS message base.
For maximum configuration possibilities, you can specify /SCAN /RBBS to
scan just the M.DEF message bases, or /SCAN /FIDO to scan just the
#.MSG areas, or you can do both by entering /SCAN /RBBS /FIDO.
Basically, if you want to scan M.DEFs (only) then...
MSGTOSS /SCAN /RBBS ..... [other switches]
If you want to scan BOTH #.MSG and M.DEFs, then ...
MSGTOSS /SCAN /FIDO /RBBS .... [other switches]
Examples: MSGTOSS /SCAN /FIDO /LOCK (fido only)
MSGTOSS /SCAN /FIDO /RBBS /LOCK (rbbs + fido)
/SCAN SWITCHES (BASIC)
--------------
/SCAN
------
Perform a SCAN (export) operation on either RBBS message bases or
FIDO sub-directories (or both). See text above.
Page - 17
MSGTOSS 2.0 Command Line Switches
------------------------------------------------------------------
/RBBS
------
Include RBBS message bases (M.DEF) during a /SCAN operation.
NOTE: Also see /FIDO command line switch.
------------------------------------------------------------------
/FIDO
------
Include FIDO messages (#.MSG) during a /SCAN operation.
NOTE: Also see /RBBS command line switch
------------------------------------------------------------------
/LOCK (COMMON)
------
Invoke multi-tasking/network support. See page 8 for more details.
------------------------------------------------------------------
/FIX (COMMON)
------
Auto-repair RBBS M.DEF(s) via FIXMSG. See page 8 for more details.
------------------------------------------------------------------
/FIXC (COMMON)
------
Auto-repair RBBS M.DEF(s) via FIXMSG. See page 8 for more details.
------------------------------------------------------------------
/DDA (COMMON)
------
Don't display (toss/scan) activity. See page 10 for more details.
------------------------------------------------------------------
----------------------------------------------------------------------
/SCAN SWITCHES (ADVANCED)
--------------
/RSCAN:zone:net/node (with /AREA: or /AREAF:)
------
For HUBS, The /RSCAN: switch allows re-scanning selected message
areas for a particular net/node. This is normally used in a hub-
bing situation, where you are adding a new net/node to a specified
area in your MSGTOSS.BBS, and you want to send all messages to that
new net/node. Example:
MSGTOSS /RSCAN:[zone]:[net]/[node] /AREA:science,comm
NOTE: An /RSCAN: operation requires either /AREA: or /AREAF:
command line switch.
NOTE: It may be necessary to use the /HWM command line switch to
provide a complete rescan.
------------------------------------------------------------------
Page - 18
MSGTOSS 2.0 Command Line Switches
/HWM
------
MSGTOSS maintains two different High Water Marks (HWMs) for the
/SCAN operation. For RBBS message bases, it utilizes position
121-122 of the RBBS checkpoint record(s) to store the HWM. For FI-
DO areas, it uses message number 1 (1.MSG), position 185-186 to
store this number.
Normally, MSGTOSS will first check the value of the HWM and ignore
all messages whose value is less than the HWM. The /HWM switch ov-
er-rides the true High Water Mark to be in the beginning of the
RBBS message base or 1.MSG. Basically, if you think a message
wasn't exported, add /HWM to the scan command line, like this...
MSGTOSS /SCAN /RBBS /FIDO /HWM
And MSGTOSS will start at the beginning of the message base to look
for non-exported mail.
In addition, this is also usually used with the /RSCAN: switch to
force MSGTOSS to re-scan all messages to a particular net/node.
NOTE: This takes more time to complete a /SCAN.
------------------------------------------------------------------
/CFG:File.Ext (COMMON)
------
Use alternate MSGTOSS.CFG file. See page 7 for more details.
------------------------------------------------------------------
/BBS:File.Ext (COMMON)
------
Use alternate MSGTOSS.BBS file. See page 7 for more details.
------------------------------------------------------------------
/WDIR (COMMON)
------
Use RAM disk for faster operation. See page 8 for more details.
------------------------------------------------------------------
/AREA:xxx,xxx,xxx (COMMON)
------
Only toss/scan /AREA:xxx,xxx,xxx. See page 9 for more details.
------------------------------------------------------------------
/AREAF:File.Ext (COMMON)
------
Only toss/scan areas in File.Ext. See page 9 for more details.
------------------------------------------------------------------
----------------------------------------------------------------------
Page - 19
MSGTOSS 2.0 Command Line Switches
Chop message bases to preset SIZE - /SIZE
-----------------------------------------
/SIZE SWITCHES
--------------
/SIZE or /SIZE-UP
-----------------
Use the /SIZE switches to keep control of the sizes of your message
bases. You can do this by simply altering the RECS:xxxx values in the
MSGTOSS.BBS file and executing:
MSGTOSS /SIZE ... other switches -- or --
MSGTOSS /SIZE-UP ... other switches
The /SIZE-UP switch will increase message sizes (and CHOP) as required
to match the RECS:xxxx values, where the /SIZE will ignore the message
base if the size is smaller than or equal to the RECS:xxxx value(s).
Because MSGTOSS doesn't think twice about expanding a message base dur-
ing a /TOSS when it needs it, this built-in 'smart sizing' code is
built into MSGTOSS to easily maintain tight control on the sizes of the
message bases. In-fact, these built-in utilities are superior to the
RBBS-PC CONFIG utility. After MSGTOSS is initially set up properly,
adding a simple line to your daily maintenance batch file:
MSGTOSS /SIZE (or /SIZE-UP) ... other switches
Will chop the message bases back down to a predetermined level in one
swipe. So again, if MSGTOSS expands a message base, that one command
will cleanly and easily return it back to its original size, using
smart purging techniques. Remember, MSGTOSS will ONLY expand a mes-
sage base if it absolutely needs to. If after the built-in purging
there is still not enough message records, then and only then will it
expand a message base.
NOTE: If the BBS keyword HIST:1 is true, then all purged messages will
be exported (in text format) into a history file. See MSGBBS.DOC
for more info.
For those sysops who decide to run /TOSS with the /PREX (pre-expand)
switch vice /PREP (pre-purge) will absolutely need to add a /SIZE oper-
ation to a daily maintenance event. Allowing the message bases to
expand as required will (sooner than later) exceed the RBBS maximum of
999 messages, causing problems for MSGTOSS.
NOTE: You really should place 'MSGTOSS /SIZE' as part of your daily
maintenance routines.
/SIZE
-----
Will CHOP message bases back down to RECS:xxxx in MSGTOSS.BBS.
NOTE: Also see text above.
------------------------------------------------------------------
Page - 20
MSGTOSS 2.0 Command Line Switches
/SIZE-UP
------
Will Increase (if required) and CHOP to match RECS:xxxx
NOTE: Also see text above.
------------------------------------------------------------------
/CFG:File.Ext (COMMON)
------
Use alternate MSGTOSS.CFG file. See page 7 for more details.
------------------------------------------------------------------
/BBS:File.Ext (COMMON)
------
Use alternate MSGTOSS.BBS file. See page 7 for more details.
------------------------------------------------------------------
/LOCK (COMMON)
------
Invoke multi-tasking/network support. See page 8 for more details.
------------------------------------------------------------------
/FIX (COMMON)
------
Auto-repair RBBS M.DEF(s) via FIXMSG. See page 8 for more details.
------------------------------------------------------------------
/FIXC (COMMON)
------
Auto-repair RBBS M.DEF(s) via FIXMSG. See page 8 for more details.
------------------------------------------------------------------
/WDIR (COMMON)
------
Use RAM disk for faster operation. See page 8 for more details.
------------------------------------------------------------------
----------------------------------------------------------------------
Page - 21
MSGTOSS 2.0 Command Line Switches
Reset users Mailwaiting Bit (all msgs) - /MWRST
-----------------------------------------------
/MWRST SWITCHES
---------------
/MWRST
------
Mailwaiting RESET... Will first ZERO all mailwaiting bits for all
users for all conferences and re-hash. Recommended every now and
then for message maintenance or when first installing MSGTOSS.
This switch provides a easy method of 'fixing' mailwaiting bits in
the RBBS User Bases. The only other known utility that provides a
similar feature is MAILWAIT (Version 1.0, Mike Zakharoff, available
as MAILWA10.xxx).
Using this utility at least once during installation of MSGTOSS
will prevent users from being notified of mail when none actually
exist. MSGTOSS will (as long the MWST:1 keyword is active in
MSGTOSS.BBS fro the conference) automatically maintain the mail-
waiting bits to perfection.
NOTE: Weekly execution of this command is recommended.
------------------------------------------------------------------
/CFG:File.Ext (COMMON)
------
Use alternate MSGTOSS.CFG file. See page 7 for more details.
------------------------------------------------------------------
/BBS:File.Ext (COMMON)
------
Use alternate MSGTOSS.BBS file. See page 7 for more details.
------------------------------------------------------------------
/LOCK (COMMON)
------
Invoke multi-tasking/network support. See page 8 for more details.
------------------------------------------------------------------
/FIX (COMMON)
------
Auto-repair RBBS M.DEF(s) via FIXMSG. See page 8 for more details.
------------------------------------------------------------------
/FIXC (COMMON)
------
Auto-repair RBBS M.DEF(s) via FIXMSG. See page 8 for more details.
------------------------------------------------------------------
/WDIR (COMMON)
------
Use RAM disk for faster operation. See page 8 for more details.
------------------------------------------------------------------
----------------------------------------------------------------------
Page - 22
MSGTOSS 2.0 Command Line Switches
Report on message base statistics - /STAT
-----------------------------------------
Use /STAT to monitor the status of your message bases. Here is an
example of the /STAT parameter...
Conf Num # Sec Num Recs Recs Pct Max Last Est Msg Est HWM First
Name User N Level Recs Used Free Full Msgs Msg Msg Size Cap Msg Msg
------- ---- -- ----- ----- ----- ---- ---- ---- ---- ---- ---- ---- ---- -----
MESSAGE 1439 3 8224 1004 746 258 74 200 206 206 3.6 277 1 06-04
GENEAL 3 3 40 1004 887 117 88 200 143 143 6.2 161 107 01-21
COMM 6 3 40 800 716 84 90 160 89 89 8.0 99 63 01-20
CLIPPER 6 3 40 800 717 83 90 160 90 90 7.9 100 79 01-18
CONSULT 1 3 40 800 714 86 89 160 85 85 8.3 95 80 01-08
COOKING 2 3 40 800 720 80 90 160 79 79 9.1 87 15 01-22
C_PRGM 5 3 5 800 714 86 89 160 94 94 7.5 105 50 01-19
DBASE 2 3 40 800 355 445 44 160 51 49 7.1 111 49 01-20
FEMIN 3 3 40 800 700 100 88 160 59 59 11.8 67 56 01-13
FORSALE 11 3 40 800 707 93 88 160 140 140 5.0 158 138 01-05
HDCONF 4 3 5 800 718 82 90 160 98 98 7.3 109 68 01-19
HDSALE 5 3 5 800 716 84 90 160 149 149 4.8 166 125 01-20
HST 3 3 5 800 720 80 90 160 91 91 7.9 101 74 01-19
HUMOR 7 3 40 800 715 85 89 160 126 126 5.6 141 108 12-25
JOBS 7 3 40 800 712 88 89 160 77 77 9.2 86 74 01-07
OS2 1 3 40 800 712 88 89 160 100 100 7.1 112 99 01-16
PHYSICS 1 3 40 800 712 88 89 160 73 73 9.7 82 73 12-27
PNWTECH 4 3 40 800 719 81 90 160 81 81 8.8 90 81 01-01
PURSUIT 2 3 40 800 716 84 90 160 101 101 7.0 112 101 02-07
QUIKBAS 3 3 40 800 718 82 90 160 99 99 7.2 110 73 01-20
SCIENCE 3 3 40 800 715 85 89 160 67 67 10.6 75 64 01-19
SPORTS 6 3 40 800 717 83 90 160 108 108 6.6 120 85 01-12
TECH 2 3 5 800 717 83 90 160 75 75 9.5 83 28 01-21
TMPLANG 2 3 40 800 63 737 8 160 13 11 5.3 150 13 01-20
VIETVET 2 3 40 800 715 85 89 160 72 72 9.9 80 61 01-21
WARNING 1 3 40 800 718 82 90 160 105 105 6.8 117 105 07-20
RBBS 7 3 40 800 717 83 90 160 90 90 7.9 100 90 12-26
MSGTOSS 1 3 40 800 700 100 88 160 87 87 8.0 99 87 12-02
---------------------------------------------------------------------- --------
Totals: There are 2645 messages in 29 areas averaging 7.3 records per message.
The 2.9 Mb allocated should hold 3458 total messages.
There are 4404 unused records out of 23608 allocated.
NOTE: Unlike the /TEST command line switch, /STAT will not pause every
23 lines for viewing. You can re-direct its output to a disk file.
Most of this data is derived from the message base 'checkpoint' re-
cord(s). Here is a summary of columns:
Conf Name - Name of the RBBS message base minus M.DEF
Num User - Number of users in the conference
# N(odes) - Number of Node records
Sec Level - Security Level of conference (8224 = none)
Num Recs - Actual number of 128-byte Records
Recs Used - Number of Records being occupied by messages
Recs Free - Number of Records Free (able to store messages)
Pct Full - Percentage (%) of total records that contain messages
Page - 23
MSGTOSS 2.0 Command Line Switches
Max Msgs - What 'Max-Messages' is set to for this conference
Last Msg - Number of the Last Message in the conference
Est Msg - Number of estimated messages in message base
Msg Size - Average size (in records) of the messages
Est Cap - Estimated number of messages (based on average size)
HWM Msg - The LAST message that was SCANNED
First Msg - Date of the First message
NOTE: This can be directed to the printer or to a file via DOS
redirection principles.
/STAT SWITCHES
--------------
/STAT
------
See information above.
------------------------------------------------------------------
/COUNT (COMMON)
------
Physically count each RBBS message. See page 10 for more details.
------------------------------------------------------------------
/CFG:File.Ext (COMMON)
------
Use alternate MSGTOSS.CFG file. See page 7 for more details.
------------------------------------------------------------------
/BBS:File.Ext (COMMON)
------
Use alternate MSGTOSS.BBS file. See page 7 for more details.
------------------------------------------------------------------
/LOCK (COMMON)
------
Invoke multi-tasking/network support. See page 8 for more details.
------------------------------------------------------------------
/FIX (COMMON)
------
Auto-repair RBBS M.DEF(s) via FIXMSG. See page 8 for more details.
------------------------------------------------------------------
/FIXC (COMMON)
------
Auto-repair RBBS M.DEF(s) via FIXMSG. See page 8 for more details.
------------------------------------------------------------------
----------------------------------------------------------------------
Page - 24
MSGTOSS 2.0 Command Line Switches
Test MsgToss Setup Configuration - /TEST
----------------------------------------
The /TEST command line is used to test the MSGTOSS configuration. This
checks such things as whether message and user files exist, testing
file handles (FILES=XXX entry in CONFIG.SYS), fido directories, length
of Origin line, whether MSGTOSS is seeing all of the net/nodes in the
MSGTOSS.BBS file, and other tests to make sure MSGTOSS should work ok.
If MSGTOSS finds anything wrong, it will loudly complain, prompting you
to fix the problem. More likely than not, it will probably be directo-
ry/file that does not exist.
At the end of all of the testing, MSGTOSS will essentially execute a
/STAT function for more information.
Use of this command line is absolutely essential during the setup and
installation of MSGTOSS for the first time, and when problems are en-
countered at a later date. It is recommended to execute:
MSGTOSS /TEST /COUNT /FIX ... other switches
During the setup of MSGTOSS. If MSGTOSS detects broken message chains
during this test (using /COUNT & /FIX), MSGTOSS will attempt to fix it
via FIXMSG (Version 1.4, Mike Zakharoff, available as FIXMSG14.xxx).
FIXMSG is required to be in the DOS path for this to work properly.
Example:
Initializing - MSGTOSS.CFG
Initializing - No File Locking Active
Initializing - MSGTOSS.BBS
Unique NET/NODE Index: 1 - 1:138/145@fidonet
Unique Nodes Detected - 1 Minimum FILES=XX is 12
Max nodes for single area is 1
Default Origin line:
* Origin: Msgtoss Support System - Sumner WA (206)862-4874 (Address)
Press any key for file handle test
Opening test file 1
Opening test file 2
Opening test file 3
Opening test file 4
Opening test file 5
Opening test file 6
Opening test file 7
Any key to for statistics (will perfom a /STAT display)
During the /STAT display, MSGTOSS will pause every 23 lines allowing you to
view the message bases. In addition, if any of your MSGTOSS.BBS REC:xxx
keywords don't match the actual size of the message bases, MSGTOSS will re-
port to you (in bright white on red) the fact that this error exists. The
error would look similar to this:
Page - 25
MSGTOSS 2.0 Command Line Switches
RBBS 7 3 40 800 717 83 90 160 90 90 7.9 100 RECS:500
^^^^^^^^^
White/Red
In this case, MSGTOSS is complaining that the actual size of the message
base is 800, but your RECS:xxx value is set to 500. If you get this error,
fix the appropriate RECS:xxx keyword for these message bases. If the
RECS:xxxx value is correct (what you really want it to be), then you can
execute the /SIZE-UP command line switch so MSGTOSS can re-size the message
bases (see /SIZE & /SIZE-UP (this document).
NOTE: All of this information can be re-directed to a DOS file or
printer via DOS re-direction principles.
/TEST
------
Perform a system installation test for MSGTOSS. Report any set-up
errors that would certainly cause headaches at a later time. See
text above for more detail.
NOTE: Absolutely essential during system installation
------------------------------------------------------------------
/COUNT (COMMON)
------
Physically count each RBBS message. See page 10 for more details.
------------------------------------------------------------------
/CFG:File.Ext (COMMON)
------
Use alternate MSGTOSS.CFG file. See page 7 for more details.
------------------------------------------------------------------
/BBS:File.Ext (COMMON)
------
Use alternate MSGTOSS.BBS file. See page 7 for more details.
------------------------------------------------------------------
/LOCK (COMMON)
------
Invoke multi-tasking/network support. See page 8 for more details.
------------------------------------------------------------------
/FIX (COMMON)
------
Auto-repair RBBS M.DEF(s) via FIXMSG. See page 8 for more details.
------------------------------------------------------------------
/FIXC (COMMON)
------
Auto-repair RBBS M.DEF(s) via FIXMSG. See page 8 for more details.
------------------------------------------------------------------
----------------------------------------------------------------------
Page - 26
MSGTOSS 2.0 Command Line Switches
Wait for users, create MSGWAIT.BAT file - /WAIT
-----------------------------------------------
/WAIT
------
The /WAIT command line switch will monitor the 'node records' in
the main RBBS main message base to determine whether all users are
off-line. If all users are off-line, then MSGTOSS will create a
file called MSGWAIT.BAT which can be tested for existence in your
batch file, example:
MSGTOSS /WAIT
If Exist MSGWAIT.BAT Goto SAFE2TOSS
Goto CANTTOSS
If the wait was unsuccessful, then no MSGWAIT.BAT file will be cre-
ated.
The sysop can (DURING the waiting process), press [C]ontinue and
MSGTOSS will continue to process, as if all users are now off-line,
creating MSGWAIT.BAT. This functions as an override.
NOTE: This function is included in MSGTOSS 2.0 for compatibility
purposes only with MSGTOSS 1.3. It essentially is obsolete
via the multi-tasking/network support provided in MSGTOSS
2.0+.
------------------------------------------------------------------
/CFG:File.Ext (COMMON)
------
Use alternate MSGTOSS.CFG file. See page 7 for more details.
------------------------------------------------------------------
/BBS:File.Ext (COMMON)
------
Use alternate MSGTOSS.BBS file. See page 7 for more details.
------------------------------------------------------------------
/LOCK (COMMON)
------
Invoke multi-tasking/network support. See page 8 for more details.
------------------------------------------------------------------
----------------------------------------------------------------------
Page - 27
MSGTOSS 2.0 Command Line Switches
Globally execute xxx for all msg bases - /GLOB:xxx
--------------------------------------------------
/GLOB:xxx
---------
The /GLOB: switches are guaranteed to make life easier. The
switches are /GLOB:xxx and /GBAT.
These two switches allow GLOBAL maintenance to occur on either RBBS
message users, & welcome files as well as Fido sub-directories.
Example:
MSGTOSS /GLOB:COPY C:\RBBS\BLANKM.DEF [MSGFILE]
Will GLOBALLY copy blankm.def over all message bases in your
MSGTOSS.BBS file (deadly, but possible).
MSGTOSS /GLOB:COPY C:\RBBS\BLANKM.DEF [MSGFILE] /GBAT
^^^^^
Notice the /GBAT appended... This will do the same, EXCEPT it will
instead create a file called MSGLOBAL.BAT that will contain the
commands that would have been used to do the first one..
MSGTOSS /GLOB:DEL [FIDOSUB]\*.*
Will delete every #.MSG file in your MSGTOSS.BBS (not recommended).
How about...
MSGTOSS /GLOB:FIXMSG [MSGFILE]
Will globally fix all message bases in one swipe...
MSGTOSS /GLOB:MSGRENUM /MSG:[MSGFILE] /USR:[USRFILE]
Is another possibility....
Again, adding /GBAT will not actually execute, but instead will
create MSGLOBAL.BAT... Allows editing/verification before actually
executing the command.
NOTE: [FIDOSUB] does not have a trailing backslash.
You can also set up multiple MSGTOSS 'Meta-Commands' using /GLOB:
to perform a variety of message base maintenance tasks. Here's an
example:
FKILL /GLOB:ECHO Y|DEL [FIDOSUB]\*.*
Where the '|' character (not allowed at the DOS prompt) can be put
in as a Meta-Command and will delete the contents of ALL of your
Fido subs.
Valid parameters are [MSGFILE] [USRFILE] [WELFILE] [AREA] [FIDOSUB]
Page - 28
MSGTOSS 2.0 Command Line Switches
NOTE: Can't mix RBBS stuff with FIDO stuff; [AREA] is mixable
though.
If you get confused, execute MSGTOSS
reminder of commands.
------------------------------------------------------------------
/GBAT
------
Create MSGLOBAL.BAT for /GLOB:xxx cmds. See /GLOB:xxxx section.
NOTE: /GBAT must be the last entry of the /GLOB: command.
------------------------------------------------------------------
/CFG:File.Ext (COMMON)
------
Use alternate MSGTOSS.CFG file. See page 7 for more details.
------------------------------------------------------------------
/BBS:File.Ext (COMMON)
------
Use alternate MSGTOSS.BBS file. See page 7 for more details.
------------------------------------------------------------------
/LOCK (COMMON)
------
Invoke multi-tasking/network support. See page 8 for more details.
------------------------------------------------------------------
----------------------------------------------------------------------
Page - 29
MSGTOSS 2.0 Command Line Switches
Recompile the node list (MSGTOSS.NOD) - /NLST
---------------------------------------------
/NLST
------
This command line switch executes MSGNLST.EXE, which is used to
compile the MSGTOSS proprietary nodelist called MSGTOSS.NOD. This
is used in conjunction with the DOMAIN------> parameters.
The MSGTOSS.NOD file contains nodelist information that MSGTOSS
uses to identify the Zone:Net/Node@Domain of *.PKT files.
-----------------------> I M P O R T A N T ! <---------------------
The command: MSGTOSS /NLST
Must be entered as part of your nodelist processing batch file.
After you have merged new NODEDIFFs, you need to:
1) Change drive/directory(s) back to the MSGTOSS directory
2) Execute MSGTOSS /NLST
3) Return back to finish other nodelist processing
This will create the MSGTOSS.NOD file in the MSGTOSS directory, us-
ing the MSGTOSS.CFG to obtain the directories where the nodelists
are via the multiple DOMAIN------> entries.
For more information on this switch and how it interacts with the
tossing system, see MSGCFG.DOC, section DOMAIN----->, and
MSGTOSS.DOC, INSTALLATION section 'Create MSGTOSS.NOD using
MSGNLST.EXE'.
------------------------------------------------------------------
----------------------------------------------------------------------
Page - 30
MSGTOSS 2.0 Command Line Switches
Execute MSGEID.EXE - EID Database Maint - /EID
----------------------------------------------
/EID
----
This command line switch executes MSGEID.EXE, which is used to
maintain the MSGTOSS.EID database that contains all of the EID and
MSGEID codes.
The MSGTOSS.EID databse is created when the BBS keyword CDUP:1 is
present in the MSGTOSS.BBS file. MSGEID.EXE allows the user the
ability to view/edit the EID database.
Syntax:
MSGTOSS /EID [file]
[file] = alternate MsgToss CONFIG file (blank = MSGTOSS.CFG)
Produces a similar display:
------------------------------------------------------------------
MsgToss 2.0 02/07/92 (c)1992 Mike Zakharoff Warren Muldrow MSGEID
Actual - MSGTOSS.EID MAXAREAS: 52 DUPSIZE: 224 (actual)
Config - MSGTOSS.CFG MAXAREAS: 52 DUPSIZE: 208
1) - Display MSGTOSS.EID index
2) - Make MSGTOSS.CFG parameters match
3) - Pack (remove dead space)
4) - Clear a particular AREA
5) - Clear all inactive AREAs
6) - Clear all NODE:x AREAs
7) - Change all NODE:x to NODE:y
8) - Display EID data for AREA
9) - Change MAXAREAS & DUPSIZE
H) - Help on the above
------------------------------------------------------------------
MSGEID.EXE will (without any command line parameters) will assume
that MSGTOSS.CFG is in the default directory and obtain the name of
the DUPFILE, MAXAREAS, and DUPSIZE from it.
NOTE: The MAXAREAS & DUPSIZE parameters entered in MSGTOSS.CFG
serve as "approximate" values. MSGTOSS, when it creates the
EID database, will round these values up to accomodate the
internal structure of the EID database. The "(actual)" val-
ues displayed (as shown above) reflects the true capacities
of the EID database.
Display MSGTOSS.EID index
-------------------------
Displays MSGTOSS.EID index that contains all of the AREA(s) and
their associated NODE entries. This is helpful when there is doubt
as to their existance or status. AREA(s) preceeded with a '-'
indicate an INACTIVE or BLANK area.
Page - 31
MSGTOSS 2.0 Command Line Switches
Make MSGTOSS.CFG parameters match
---------------------------------
Will PHYSICALLY modify your MSGTOSS.CFG file to make sure that the
MAXAREAS and DUPSIZE properly match the EID database. After up-
date, will ask if you if you have another (alternate) config file
to update.
Pack (remove dead space)
------------------------
Will reduce the size of the EID database to its smallest possible
size, keeping the original MAXAREAS & DUPSIZE parmeters. You have
the option to keep or purge INACTIVE areas.
Clear a particular AREA
-------------------------
Will clear a SINGLE area from the EID database, along with all of
its associated data (EID & MSGID codes).
Clear all inactive AREAs
------------------------
Will clear all INACTIVE area from the EID database, along with all
of its associated data (EID & MSGID codes). INACTIVE areas are
preceeded by a '-' character.
Clear all NODE:x AREAs
----------------------
Will GLOBALLY clear all AREA(s) with a particular NODE:x entry.
Usefull for clearing AREAS created by changing the order of the
NODE:x entries in in either the MSGTOSS.BBS or MSGTOSS.CFG file.
Change all NODE:x to NODE:y
---------------------------
Will GLOBALLY change all NODE:x entries to another NODE:y entry.
Usefull when re-organizing NODE:x orders in either the MSGTOSS.BBS
or MSGTOSS.CFG file(s).
Display EID data for AREA
-------------------------
Displays the actual MSGID: or EID: codes (in HEX format) entered
for a area. Useful for verifying existance of a certain code.
Change MAXAREAS & DUPSIZE
-------------------------
Allows you to change the MAXAREAS and/or DUPSIZE of an existing EID
database file. Prior to MsgToss 2.0, you would have to erase it.
When re-sizing, will keep all existing EID codes. MAXAREAS is lim-
ited to 1000 or less.
------------------------------------------------------------------
----------------------------------------------------------------------
Page - 32
MSGTOSS 2.0 Command Line Switches
MSGTOSS.CMD Meta-Commands - (no slashes)
----------------------------------------
MSGTOSS Meta-Commands
---------------------
MSGTOSS can now be configured to execute user-defined Meta-Com-
mands. For example...
MSGTOSS TOSS
Could now execute /TOSS /PREP /FIXC, etc... in one clean sweep
The file that contains the Meta-Commands is called MSGTOSS.CMD...
here is a sample:
TOSS1 /TOSS/DDA/DLOG/FIXC/KNET/KUNK/LOCK/NSTOP/PREX/WDIR/DKP
TOSS2 /TOSS/DDA/DLOG/FIXC/LOCK/NSTOP/PREX/WDIR/DKP
FIX /GLOB:FIXMSG [MSGFILE] /NET
RNUM /GLOB:MSGRENUM /MSG:[MSGFILE] /USR:[USRFILE] /NET
These are the configurable Meta-Commands. As you can see, execut-
ing..
MSGTOSS FIX
MSGTOSS CMD
ence.
The original purpose of this is to overcome extremely long commands
at the DOS prompt, but it turned out to be an asset. The Meta-Com-
mand can be named anything and the switches can contain any valid
MSGTOSS switch set.
If you have two Meta-Commands called 'TOSS' and 'NODES' you can en-
ter 'MSGTOSS TOSS NODES
Meta-Commands you have defined or both types of operations. Its
just like you executed both command lines at the DOS prompt, and
are not limited by DOS's command line limit.
SUMMARY
-------
MsgToss Meta-Commands allow you to configure one (or more) single
keywords to mean any combination of MsgToss switches.
MSGTOSS CMD
MSGTOSS xxx
MSGTOSS xxx xxx
MSGTOSS xxx /xx
MsgToss Meta-Commands allow you to configure one (or more) single
Keywords to mean any combination of MsgToss switches (see docs).
------------------------------------------------------------------
----------------------------------------------------------------------
Page - 33
MSGTOSS 2.0 Command Line Switches
MSGTOSS ErrorLevel Semaphore File Codes - Errorlevels
-----------------------------------------------------
ERRORLEVELS
-----------
MSGTOSS supports an errorlevel kludge to allow creative batch file
operations in a variety of situations. This is accomplished via a
semaphore file, and does NOT create a TRUE DOS errorlevel.
NOTE: It should be noted that prior to DOS 5.0, the beta version of
MSGTOSS did support true errorlevels. Because of this
conflict, this was disabled in the MSGTOSS 2.0 release.
Version 2.1 will support true errorlevels.
Here is a summary of the errorlevels supported:
1) Configuration Error ---------------------->255 Errorlevels
2) Command Line Error ----------------------->254
3) Insufficient Disk Space ------------------>253
4) File Open Failure ------------------------>252
5) Trapped a FATAL error (Msgtoss Aborted) -->251
6) Corrupt Message File --------------------->250
7) Message base expansion took place -------->120
8) ConfLock Timer expired ------------------->110
9) Not enough packets (or none) to Toss ----->100
10) Normal end of program --------------------> 0
MSGTOSS will create a zero-byte semaphore file called MSGERLVL.xxx
where xxx is the errorlevel (1+) with leading zeros.
NOTE: MSGTOSS will delete any existing MSGERLVL.xxx files every
time it is executed. Upon an exit, only one (if any)
semaphore file will be present in the MSGTOSS directory.
To capture errorlevels, use your batch file to detect the errorle-
vel(s) via the MSGTOSS errorlevel semaphore files like
MSGERLVL.001, 002, etc.
Example:
:TOSS
MSGTOSS /TOSS /PREP /LOCK
If Exist MSGERLVL.253 Goto DISKFULL
Goto START
:DISKFULL
ECHO Disk Full!!!! >LPT1
Goto START
----------------------------------------------------------------------
Page - 34
Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!
This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.
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/