home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
BBS
/
SFPK317B.ZIP
/
SFPK317B.DOC
< prev
next >
Wrap
Text File
|
1992-01-18
|
15KB
|
379 lines
SFPACK 3.17B
The Smart Message Base Packer for Spitfire 3.0/3.1
(For Registered SFUTI Users)
Copyright 1989, 1990, 1991 by Smart Office Solutions
All Rights Reserved
Smart Office Solutions, Inc.
84 South Division Street
New Rochelle, NY 10805
Voice: (914) 632-1496
BBS: (914) 576-6139 HST
RIME: ->SOLUTION
Intelec: ->SOLUTION
Compuserve: 70062,3536
SFPACK 3.17B Page: 1
Table of Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
Features . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Reference . . . . . . . . . . . . . . . . . . . . . . . . . . 3
The SFPACK Command Line . . . . . . . . . . . . . . . . 3
Command Line Options . . . . . . . . . . . . . . . . . . 3
AREA: . . . . . . . . . . . . . . . . . . . . . . . 3
DAYS: . . . . . . . . . . . . . . . . . . . . . . . 3
SPRV: . . . . . . . . . . . . . . . . . . . . . . . 3
RCVD: . . . . . . . . . . . . . . . . . . . . . . . 3
MSGS: . . . . . . . . . . . . . . . . . . . . . . . 3
NOBAK . . . . . . . . . . . . . . . . . . . . . . . 3
DUPCK . . . . . . . . . . . . . . . . . . . . . . . 3
NOLOG . . . . . . . . . . . . . . . . . . . . . . . 3
RENUM . . . . . . . . . . . . . . . . . . . . . . . 4
Miscellaneous Operational Notes . . . . . . . . . . . . . . . 5
Differences From Previous Versions . . . . . . . . . . . 5
Log File Generation . . . . . . . . . . . . . . . . . . 5
Error Reporting . . . . . . . . . . . . . . . . . . . . 5
Place Holding . . . . . . . . . . . . . . . . . . . . . 5
Message Numbers . . . . . . . . . . . . . . . . . . . . 6
Recovering From a Critical Error . . . . . . . . . . . . . . 6
Technical Support . . . . . . . . . . . . . . . . . . . . . . 6
SFPACK 3.17B Page: 2
Introduction
SFPACK is no longer an integral part of the SFUTI package. One
of the many changes in Spitfire 3.0 is the use of NetMail
compatible message index files which make a special packer for
SFUTI operation unnecessary. The internal Spitfire packer can be
used freely.
As a "thank-you" to the many Sysops who have registered their
SFUTI packages, SOS has decided to continue to maintain SFPACK
and to offer it to registered SFUTI users free of charge. If you
have registered your SFUTI package, you are granted a license to
use the SFPACK software on one computer system or Local Area
Network. Please note that SFPACK 3.17B will refuse to function
unless your SFUTI system is currently registered.
Features
Full file sharing and MultiNode / Local Area Network
compatibility.
All parameters are passed on the SFPACK command line. This allows
you to pack different message bases with different parameters.
Smart Dual 32 bit CRC duplicate checking removes duplicates.
Messages can be packed by age (number of days old).
Messages can be packed based on Private & Received status.
Messages can be packed based on size (number of messages).
Backup files are created but can be suppressed.
SFPACK will NOT attempt a pack unless enough disk space is
available.
SFPACK will pack messages that are included in a "thread" and
will handle all necessary "thread" updating required by the
removal of a threaded message.
Completely SAFE operation. No changes are made to your original
message bases until the entire pack operation has been completed
successfully.
Full backup files are created during SFPACK operation.
Full logging of SFPACK's activities is available.
SFPACK 3.17B Page: 3
Reference
The SFPACK Command Line
-----------------------
The parameters passed to SFPACK on its command line may be placed
in ANY order. However, if the same parameter is passed on the
command line twice only the second occurrence will be honored.
For example, if you issued the command:
SFPACK AREA:4 DAYS:30 DAYS:90
SFPACK will pack the message base to 90 days.
Command Line Options
--------------------
AREA:xx This parameter indicates which message bases SFPACK should
process. If the AREA: parameter is not specified, SFPACK
will pack ALL message bases with the command line supplied.
Valid area values are one area number or a range of area
numbers (xx-xx). Multiple area values may be used provided
they are separated by commas. The following are valid AREA
commands:
AREA:5
AREA:1-20
AREA:1,3,9
AREA:1,3,17-200,13,5-8
DAYS:dd This parameter indicates the age of messages that SFPACK
should leave in the message bases. If you specify DAYS:30,
all messages older than 30 days will be removed.
SPRV:dd This parameter indicates that Private mail that has not yet
been received by the addressee should NOT be packed unless
it is more than dd days old. When this parameter is used,
the DAYS parameter has no effect on Private / Un-Received
mail.
RCVD: This parameter indicates that messages that are marked BOTH
Private and Received should be removed.
MSGS:xx This parameter specifies the MAXIMUM number of messages to
leave in the message base. SFPACK will trim the message
base to the number of messages specified here BEFORE
applying any other command line parameters. Other
parameters may further reduce the number of messages
remaining upon completion.
NOBAK This parameter specifies that the backup files (*.BKI,
*.BKD, *.BKP) should be deleted at the completion of a
successful pack operation.
DUPCK This parameter actives SFPACK's Flying Dual 32 Bit CRC
duplicate removal algorithm.
NOLOG This parameter deactivates log file updates.
SFPACK 3.17B Page: 4
RENUM This parameter causes your messages to be renumbered
sequentially starting at 1. This parameter should only be
used if your message numbers are unusually high, or if you
suspect index file damage. RENUM writes a brand new
SFMSGxx.IDX file after renumbering, to be sure that the all
files are in sync.
* NOTE: If you are using the PCRelay Networking Software,
then you MUST delete all the THREAD.xxx files that
correspond to your RENUMbered message bases. Please be
aware that the THREAD.xxx files are numbered by your
network's NATIONAL conference numbers, and NOT the
conference numbers that your Spitfire uses locally.
/? This parameter will display a summary of valid SFPACK
command line parameters.
SFPACK 3.17B Page: 5
Miscellaneous Operational Notes
Differences From Previous Versions
----------------------------------
The DATE: parameter is no longer supported.
The NODUP parameter has been changed to DUPCK.
The SPRV: parameter has been added.
Log File Generation
-------------------
SFPACK normally logs its activities to a disk file named
SFPACK.LOG located in the UTI home directory. Creation and
updating of the log file may be suppressed by using the NOLOG
parameter on the command line.
Error Reporting
---------------
SFPACK is designed as an extension to a registered SFUTI system.
As such, it contains the same central disk file error reporting
as the SFUTI package. All critical errors will be fully logged
to the SFUTI.ERR file located in the SFUTI home directory.
In addition, SFPACK will set a DOS ERRORLEVEL when it aborts due
to a critical error. This ERRORLEVEL may be tested in the batch
file that runs your packing event. For more information on the
DOS ERRORLEVEL value, please refer to your DOS documentation.
Place Holding
-------------
SFPACK will NEVER remove the last message in a message base.
This message is critical and must remain on file as the "place
holder" for the last message number issued by your Spitfire
system. For proper threading and NetMail operation, it is
imperative that no two messages are ever assigned the same
number. If this last "place holder" message is determined to be
a duplicate, SFPACK will mark the message as deleted, but not
physically remove it from the file. Thusly, your users do not
see the duplicate message, but the "place holder" is still in
place.
SFPACK 3.17B Page: 6
Message Numbers
---------------
The actual unique message numbers used by Spitfire 3.0 and SFPACK
3.17B for proper thread maintenance are NOT displayed to you or
your users during regular on-line messaging functions. Spitfire
continues to display the relative number of the message starting
with 1 and ending with the total number of messages on file. Do
not be concerned if it appears that messages have been
renumbered.
Recovering From a Critical Error
--------------------------------
SFPACK uses the safest mechanism possible for packing your
message bases. Your original files (SFMSGxx.DAT, SFMSGxx.PTR,
and SFMSGxx.IDX) are not written to during the packing cycle.
SFPACK writes out NEW message bases under the file names
SFMSGxx.NWD, SFMSGxx.NWP, and SFMSGxx.NWI. When the program has
reached completion WITHOUT encountering a critical error, the
following actions are performed:
SFMSGxx.DAT is renamed to SFMSGxx.BKD
SFMSGxx.PTR is renamed to SFMSGxx.BKP
SFMSGxx.IDX is renamed to SFMSGxx.BKI
SFMSGxx.NWD is renamed to SFMSGxx.DAT
SFMSGxx.NWP is renamed to SFMSGxx.PTR
SFMSGxx.NWI is renamed to SFMSGxx.IDX.
If you have used the NOBAK command line parameter, the following
additional actions are performed:
SFMSGxx.BKD is deleted
SFMSGxx.BKP is deleted
SFMSGxx.BKI is deleted.
If SFPACK encounters a critical error at any stage before this
final processing cycle, your original message base files will
still be on disk under their original names as if the packer
never operated. Using this method allows you to safely pack your
message bases in an event.
Technical Support
-----------------
Refer to your SFUTI documentation for Technical Support
procedures.
SFPACK 3.17B Page: 7
Index
AREA: . . . . . . . . . . . . . . . . . . . . . . . . . . . 1, 3
Command line . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Conference . . . . . . . . . . . . . . . . . . . . . . . . . . 4
DATE: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
DAYS: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
DUPCK . . . . . . . . . . . . . . . . . . . . . . . . . . 1, 3, 5
Error . . . . . . . . . . . . . . . . . . . . . . . . . . 1, 5, 6
ERRORLEVEL . . . . . . . . . . . . . . . . . . . . . . . . . . 5
File names . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Introduction . . . . . . . . . . . . . . . . . . . . . . . 1, 2
License to use . . . . . . . . . . . . . . . . . . . . . . . . 2
Local Area Network . . . . . . . . . . . . . . . . . . . . . . 2
Log file . . . . . . . . . . . . . . . . . . . . . . . . 1, 3, 5
Message number . . . . . . . . . . . . . . . . . . . . . . . . 5
MSGS: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
MultiNode . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
NetMail . . . . . . . . . . . . . . . . . . . . . . . . . . 2, 5
Network . . . . . . . . . . . . . . . . . . . . . . . . . . 2, 4
NODUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
NOLOG . . . . . . . . . . . . . . . . . . . . . . . . . . 1, 3, 5
PCRelay . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
RCVD: . . . . . . . . . . . . . . . . . . . . . . . . . . . 1, 3
RENUM . . . . . . . . . . . . . . . . . . . . . . . . . . . 1, 4
SFPACK . . . . . . . . . . . . . . . . . . . . . . . . . . . 0-6
SFUTI.ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Smart Office Solutions . . . . . . . . . . . . . . . . . . . . 0
SPRV: . . . . . . . . . . . . . . . . . . . . . . . . . . . 1, 5
Support . . . . . . . . . . . . . . . . . . . . . . . . . . 1, 6