Dec 262017
 
For WILDCAT! BBS 2.x - Automatically delete users who haven't called in x days. Will generate report of affected users first, if desired.
File USERZAP.ZIP from The Programmer’s Corner in
Category BBS Files
For WILDCAT! BBS 2.x – Automatically delete users who haven’t called in x days. Will generate report of affected users first, if desired.
File Name File Size Zip Size Zip Type
USERZAP.DOC 4345 1832 deflated
USERZAP.EXE 16934 16411 deflated

Download File USERZAP.ZIP Here

Contents of the USERZAP.DOC file


UserZap :: Release 1.0 [a Wildcat 2.x utility]

(c) 1991, Clyde W. Grotophorst, GMUtant Software

GMUtant OnLine BBS :: (703) 323-3100

****************************************************************

You may freely copy and distribute UserZap
Please read this entire file before using
the program

****************************************************************


UserZap exists for a single purpose--to automate the deletion of users
from your user database (USERFILE.DAT) if they haven't called in a while.

IMPORTANT CAVEAT: If you plan to use this program to actually delete
records, you need to have WCREPAIR.EXE (a Wildcat utility program from
Mustang Software) available. That program will need to be run after
UserZap to rebuild the user file indexes. UserZap works on the datafile
(USERFILE.DAT) but not the indexes!

Installation: Copy UserZap.EXE to the sub-directory where USERFILE.DAT
is stored.

To use: Type UserZap at the DOS prompt and follow the onscreen instructions.

Details:

Armed with your answers to 3 questions, UserZap goes to work pruning your
system's user file. Each record in USERFILE.DAT that meets the 3 criteria
will be deleted. You have the option of running the program in a read-only
mode to first determine what settings to use.

The deletion criteria:

1) Number of days since user last called (e.g., enter 365 to delete all
users who haven't called in a year).

2) A threshold on the number of times the caller has logged in (e.g., if
you say 5 and the caller has called 6 times, he won't be deleted. This
is included for those poor souls (like myself) who do not have a
clock in their WildCat PC, thus periodically run into the situation
where the date reverts to 01/01/80 after a power failure on the
weekend. You may have a very active caller who called in yesterday
when your system date was wrong, and he'd be deleted based on the
LAST CALLED field in his user record.

3) A security level to process (only those callers with the security
level you enter will be deleted)...another safety feature. If you
provide high access levels to customers, but they don't call often,
you don't want to accidentally blow them out of your file.

Once you answer those questions, you are posed with several processing
options:

[C] Count only. UserZap will run through your file and count the
number of affected records.

[W] Count and write only. UserZap counts affected records and writes
an ASCII file listing everyone who would be deleted. Here is a
sample of that report (TOZAP.USR):

Nick Carter Last Call: 05/30/89 SecLvl:5 Times: 1
K Schneider Last Call: 08/31/89 SecLvl:5 Times: 2
Mark Flynn Last Call: 06/16/89 SecLvl:5 Times: 4
Jc Murillo Last Call: 06/09/89 SecLvl:5 Times: 1
Joe Flanagan Last Call: 06/12/89 SecLvl:5 Times: 1

[Z] ZAP. This will go through your USERFILE.DAT database and mark records
for deletion if the 3 conditions are met for a given user. For
example, if you tell UserZap that you want to get all callers
who haven't called in 300 days, have called the system fewer
than 5 times, and have a security level of 5 (not 5 or lower,
just 5), then a user record matching that criteria will have
the STATUS field set to delete.

When the [Z] option is selected, UserZap also creates an
ASCII file (ZAPPED.USR) which lists all those who were marked
for deletion.


IMPORTANT! When you have finished running UserZap with the Z option, you
will have to run WCREPAIR to rebuild the USER database--more
specifically, to rebuild the indexes.


I have tested UserZap on a WildCat 2.55S system. I can not accept any
liability for use on other versions of WildCat but I don't see why it
wouldn't work...you can use the C or W options without concern since
neither of those options modify your file.


GMUtant OnLine BBS - 703 323 3100



 December 26, 2017  Add comments

Leave a Reply