home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
BBS
/
NLU_111.ZIP
/
NLU.DOC
< prev
next >
Wrap
Text File
|
1993-06-15
|
35KB
|
792 lines
Node List Update Utility 1.05b
Copyright 1993
All Rights Reserved
By Les Fenison
Fido Net 1:105/751
Family Net 8:77/7
Advanced Computer Design & Consulting
24008 Butteville Rd NE
Aurora, OR 970022
(503) 678-3050
═════════════════════════════════════════════════════════════════════════════
Node List Update Utility (NLU) Page 1
═════════════════════════════════════════════════════════════════════════════
CONTENTS
1 Disclamer....................................Page 2
2 What is Node List Update Utility?............Page 2
3 Programs Needed to Operate NLU...............Page 3
4 About Shareware..............................Page 3
5 How To Register..............................Page 4
6 The ACDC BBS.................................Page 4
7 System Requirements..........................Page 5
8 Distribution Files...........................Page 5
8.1 Version History..........................Page 5
9 Running NLU..................................Page 5
10 Configuring NLU..............................Page 6-11
Regkey.....................................Page 6
MaxDiffs...................................Page 6
MaxLists...................................Page 6
InboundDir.................................Page 6
DownloadDir................................Page 7
NodeListDir................................Page 7
ListName(s)................................Page 7
DiffName(s)................................Page 7
ListDesc(s)................................Page 8
DiffDesc(s)................................Page 8
LogFile....................................Page 8
LogMode....................................Page 8
LogStyle...................................Page 8
TossFiles..................................Page 9
Update_FileList............................Page 9
FileList_Order.............................Page 9
Zip, Zip2..................................Page 9
Unzip, Unzip2..............................Page 9
Zipview, Zipview2..........................Page 9
Arc, Arc2..................................Page 9
UnArc, UnArc2..............................Page 9
ArcView, ArcView2..........................Page 9
Lzh, Lzh2..................................Page 10
UnLzh, UnLzh2..............................Page 10
LzhView, LzhView2..........................Page 10
ArcPref....................................Page 10
ApplyDiff..................................Page 10
Cleanup....................................Page 10
Convert....................................Page 11
SkipTest...................................Page 11
MagicDir...................................Page 11
MagicList..................................Page 11
11 Program Flow Description.....................Page 12-14
═════════════════════════════════════════════════════════════════════════════
Node List Update Utility (NLU) Page 2
═════════════════════════════════════════════════════════════════════════════
1 Disclaimer
ACDC hereby disclaims all warranties relating to this product,
whether express or implied, including without limitation any implied
warranties of merchant ability or fitness for a particular purpose. ACDC
cannot and will not be liable for any special, incidental, consequential,
indirect or similar damages due to loss of data or any other reason, even if
ACDC or an authorized ACDC agent has been advised of the possibility
of such damages. In no event shall the liability for any damages ever
exceed the price paid for the license to use software, regardless of the
form and/or extent of the claim. The user of this program bears all risk as
to the quality and performance of the software.
2 What is Node List Update Utility?
It is a utility that will process your incoming nodelists. (If
enabled) it will toss the incoming nodelists from your inbound directory
to the directory where you store your nodelists available for download
from hereon refereed to as the download directory. It can optionally
update your FILES.BBS with a description that you provide which can
include a day number.
Next NLU will check to see if their is a LIST or DIFF in your
download directory that is newer than the one in your active directory.
The active directory is the directory where your mailer, BBS, and or
nodelist compiler looks for lists and diffs. If a newer list or diff
does exist in the download directory it will be unachieved into the
active directory.
Next (if enabled) it will apply the DIFFS to the LISTS and
optionally cleanup the old diffs and lists.
Next it will check to see if there is a list or diff in the
active directory that is not yet in the download directory. If it
finds a newer list or diff it will archive it and place it in your
download directory and optionally update FILES.BBS.
Next it will check to see if there are more of a DIFF or LIST
in the download directory than you specified as a maximum. If so it
will purge old diffs or lists.
The program comes with three different versions. There is a
OS/2 version called NLU2.EXE, a DOS version called NLU_DOS.EXE, and
a family mode version which will run in either OS/2 or DOS called
NLU.EXE.
═════════════════════════════════════════════════════════════════════════════
Node List Update Utility (NLU) Page 3
═════════════════════════════════════════════════════════════════════════════
3 Programs Needed to Operate NLU
There are three methods of compression supported. They are ZIP, ARC,
and LZH. You will need utilities for the methods that you use on your
system. It is recommended that you have all three just in case someone
sends you a different version of a list or diff. Utilities to apply
the DIFF files such as XLAXDIFF or other such utilities may also be
used.
IMPORTANT NOTE ABOUT UNARCHIVERS!!!!
Not all archivers will support wild cards. It is your responsibility
to make sure that your unarchivers will support wild cards and a
view option. The syntax used to archive, unarchive, and view contents
must be supplied in NLU.CTL.
4 About Shareware
NLU is Shareware. PKZIP, LHA, and ARC are also shareware. Shareware is NOT
free. It is computer software offered for sale at a set price and the only
real difference between Shareware and other commercial software products is
the method of distribution and the important "try before you buy" feature.
With Shareware you are normally licensed by the owner/author of the program
to operate the Shareware distribution copy on a trial basis. Then if you
like it and make regular use of it, you are bound to pay for it.
Registered users are those users that elect to pay for NLU ($5) and
register that payment with ACDC. By virtue of registration and payment
for the program, registered users are granted a license to continue to
utilize the program on their personal computer for as long as they choose.
This license authorizes the user to use the program on any personal computer
system he or she may own so long as the program is operated on only one
computer system at a time.
Site licenses for use of NLU on multiple computers are available upon
request at a reduced fee that is based on the number of single machines
licensed for use.
═════════════════════════════════════════════════════════════════════════════
Node List Update Utility (NLU) Page 4
═════════════════════════════════════════════════════════════════════════════
5 How To Register
There is no functional difference between the Shareware distribution
version of NLU and the registered version except for the annoying beeps
and delays and user intervention at the end of the program. Registering
your copy will remove the little annoyances.
The price of NLU is $5.00. you may register NLU by sending a check
or money order to us. See the included file NLU_REG.DOC for the
order form.
Special site license rates for licensing multiple copies are available.
Please call for rate schedule information.
Foreign (non-US/Canada) orders must include a $2.00 special handling
fee in addition to the $5.00 registration fee. Also, no checks on banks
located outside the United States will be accepted.
This Shareware version of NLU may be freely copied and passed on to
other individual users for their evaluation.
Upgrades to later versions are available to all users on the
ACDC BBS at no cost. Access to the BBS is a privilege granted by ACDC
that may be revoked at any time for any reason. Those who request
upgrades via telephone or mail must remit a $5.00 charge for an upgrade.
upgrades from the BBS are free.
6 The ACDC BBS
The ACDC BBS is up from 12am midnight to 7am Pacific time. The
BBS phone line is a voice line during daytime hours.
(503) 678-3050 - 1200/2400/9600//14400/16800 (USR DUAL STD)
The ACDC Shareware Products BBS operates 6 hours per day, 7 days
per week excluding mail hour from 2am to 3am and is open to all callers.
The latest version of NLU and all programs that are supported or used by
NLU may be obtained via the BBS or file request. To file request the
latest version of NLU use the magic filename of NLU. To request the
full package of archive utilities used by NLU use the magic filename
of NLU_UTIL. You may also file request our files list with the magic
filename of FILES. The BBS also serves as an avenue for product
support. You may report problems or ask questions about the operation of
NLU via the message facility of the BBS. Or send netmail to Les Fenison.
Our Fido Net address is 1:105/751 and the Family Net address is 8:77/7.
═════════════════════════════════════════════════════════════════════════════
Node List Update Utility (NLU) Page 5
═════════════════════════════════════════════════════════════════════════════
7 System Requirements
NLU may be operated on any IBM PC/XT/AT/PS2 or compatible running under
DOS 2.0 and above or OS/2.
All monitor and graphics cards are supported, including "composite" (2
color) monitors and backlit laptop screens.
8 Distribution Files
The following files are included in NLU distribution package:
NLU.EXE - Family mode version
NLU_DOS - DOS version
NLU2.EXE - OS/2 Version
NLU.CTL - Commented Configuration File
NLU.DOC - This Manual
NLU_REG.DOC - Registration information & Form
WHATSNEW.NLU - Latest product info (if needed)
ACDC prohibits the modification of any of these files in any way,
shape, or form except by the individual evaluator or purchaser.
8.1 Version History
1.0b - Initial beta release.
1.01b - Corrected a bug that in some rare cases could cause the day number
entered into the FILES.BBS to be 0. Fixed some minor cosmetic
things. Added to the DEBUG level of the log so it would include
output of all shell commands.
9 Running NLU
To access NLU from anywhere in your system, place the EXE file in
a directory that is identified in your DOS path string. To operate NLU,
simple type the name of the EXE file and press the Enter key. NLU will
need to know where its configuration file is. If the configuration file
is found in the current directory it will use it. If the configuration
file is not in the current directory then you may specify the path and
name of the configuration file on the command line. The default
configuration file is NLU.CTL but may be called anything you want as
long as it is specified on the command line.
═════════════════════════════════════════════════════════════════════════════
Node List Update Utility (NLU) Page 6
═════════════════════════════════════════════════════════════════════════════
10 Configuring NLU
Configuration data is normally stored in a file named NLU.CTL.
This file is heavily commented and should be very easy to setup with
any text editor.
The configuration file is made up of comments and keywords
followed by options. The keywords and options are as follow;
Keywords may be in any case upper or lower. All comments must
begin with a semicolon(;). Keywords MUST start in column 0. A space
before a keyword will keep it from working. The format is a KEYWORD
followed by OPTIONS The keyword should be followed by the option in
the following format;
MAXDIFFS 5
Do not include quotes such as
MAXDIFFS "5".
Do not use equal signs such as
MAXDIFFS=5.
KEYWORDS;
REGKEY
After this keyword you should enter your registration key. If you
are not registered then DO NOT include this keyword. Registration
entitles you to free support, removes the annoying sounds and delays,
and removes the user intervention at the end. It only costs $5.
See NLU_REG.DOC for registration information.
MAXDIFFS
Maximum number of nodediffs to keep in the download directory.
If the keyword is left out nodediffs will not be purged. Same with
MAXDIFFS 0. For example, if you only wanted to keep the five latest
NODEDIFFS you would use the MAXDIFFS 5
MAXLISTS
Maximum number of nodelists to keep in the download directory.
If this keyword is left out nodediffs will not be purged. Same with
MAXLISTS 0.
INBOUNDDIR
This is the path where your mailer puts the inbound files. This
path is ignored unless the TOSSFILES keyword is used. Place the whole
path including the drive letter after the INBOUNDDIR keyword.
═════════════════════════════════════════════════════════════════════════════
Node List Update Utility (NLU) Page 7
═════════════════════════════════════════════════════════════════════════════
DOWNLOADDIR
This is the path where you keep your nodelists and nodediffs for
download or filerequest. Place the whole path including the drive
letter after the keyword.
NODELISTDIR
This is the path to your active nodelists. This is where your
nodelist.### files are kept and where your nodediff.### files are
applied to the nodelist.###. Place the whole path including the drive
letter after the keyword.
LISTNAME
This keyword should be followed by the name of the nodelist file
with the no extension. This keyword may be used more than
once if you have lists for more than one net. If used more than once
for more than one list then the order of the lists MUST BE THE SAME AS
THE DESCRIPTIONS IN LISTDESC AND DIFFNAMES!! Place the whole path
including the drive letter after the keyword. For example if you had
the fido list, the family net list, and the D'bridge list you would use
the following;
LISTNAME NODELIST
LISTNAME FMLYLIST
LISTNAME DBNET
DIFFNAME
This keyword works just like the LISTNAME keyword and follows the
same rules. If specified more than once for more than one net the order
MUST BE THE SAME AS THE ORDER USED IN LISTNAME AND THE DESCRIPTIONS AND
LIST NAMES! For example, If you had the lists we used in the example
above for LISTNAME then you must use the following for DIFFNAME.
DIFFNAME NODEDIFF
DIFFNAME FMLYDIFF
DIFFNAME DBDIFF
If one of the lists is rather small and never has a diff but rather a
new list every week then you must specify the diff anyway to keep the
number of entries the same as the LISTNAME and LISTDESC.
═════════════════════════════════════════════════════════════════════════════
Node List Update Utility (NLU) Page 8
═════════════════════════════════════════════════════════════════════════════
LISTDESC
Follow this keyword with the description for the NODELIST.Z##
in the FILES.BBS file. This keyword is ignored unless the
UPDATE_FILELIST keyword is used. If you want a day number to
be included in the description then replace the day number
with a ~D. For example if you wanted the description to read;
Node list for day number 101 you would use the following;
LISTDESC Nodelist for day number ~D
If a download counter is used then it should be added here as well
Here is an example of a download counter;
LISTDESC [000] Nodelist for day number ~D
If you have lists for more than one network then YOU MUST HAVE MORE
THAN ONE LISTDESC. The number of list descriptions must be the
same as the number of calls to LISTNAME and DIFFNAME. The order and
quantity must be exactly the same! Here is an example that would
work with the above examples.
LISTDESC FidoNET nodelist for day number ~d
LISTDESC Family Net list for day number ~d
LISTDESC Dbridge net list for day number ~d
DIFFDESC
This works the same as LISTDESC except it is used for the diff
files. Once again you must have the same number of entrys here as
you have in LISTDESC, LISTNAME, and DIFFNAME. The order and quantity
must be the same. Here is an example that will work with the above
examples;
DIFFDESC FidoNET nodediff for day number ~d
DIFFDESC Family Net diff for day number ~d
DIFFDESC Dbridge diff for day number ~d
LOGFILE
If you want a log file put the full path and file name after this
keyword.
LOGMODE
Options available for this keyword are TERSE, VERBOSE, DEBUG, and
NONE. TERSE will log all errors and any true action. In other words, if
NLU were to check for files to toss and there were none it would not be
logged but if there were files to toss it would log it. Using VERBOSE
will log everything that TERSE logs plus some progress information. DEBUG
will log everything that TERSE and VERBOSE will log plus much more
including commands that were issued to external utilities like PKZIP and
so on.
LOGSTYLE
Options available for this keyword are FRONTDOOR, DBRIDGE, and
BINK. More options can be added as I receive samples of other logs.
═════════════════════════════════════════════════════════════════════════════
Node List Update Utility (NLU) Page 9
═════════════════════════════════════════════════════════════════════════════
TOSSFILES
This keyword has no options. If the keyword is present then files
will be tossed from the inbound directory specified in INBOUNDDIR to
the download directory specified in DOWNLOADDIR.
UPDATE_FILELIST
This keyword has no options. If the keyword is present then the
FILES.BBS files will be updated.
FILELIST_ORDER
If the UPDATE_FILELIST keyword is not used then this keyword will be
completely ignored! The options for this keyword are TOP BOTTOM and SORT.
If TOP is used then the description will be placed on the top of the
FILES.BBS. If BOTTOM is specified then the description will be placed
at the bottom of the FILES.BBS. If the SORT option is specified then
the description will be inserted at the point where the FILE fits in
alphabetical order. The options TOP, BOTTOM, & SORT MUST BE IN CAPS!
ZIP DOS Command to add a file to a zip
ZIP2 OS/2 Command to add a file to a zip
UNZIP DOS Command to extract a file from a zip
UNZIP2 OS/2 Command to extract a file from a zip
ZIPVIEW DOS Command to view a zip file.
ZIPVIEW2 OS/2 Command to view a zip file.
The above keywords are the command line syntax for ziping and
unzipping. DO NOT use destructive options such as -M to move
to a zip but rather -A to add to a zip. Likewise for unzipping
don't use the command that deletes the origional .zip. If the
keyword is needed and is not provided then the zipping or
unzipping will not take place. WARNING!!! Some versions of zip
will cause the system to lockup if the wrong command line options
are used!. To be sure that the command line options are correct
try the command first from the command line yourself. Any command
that requires operator response beyond the initial command line will
not work with NLU.
ARC DOS Command to add a file to an arc file.
ARC2 OS/2 Command to add a file to an arc file.
UNARC DOS Command extract a file from an arc file.
UNARC2 OS/2 Command to add a file from an arc file.
ARCVIEW DOS Command to view the contents of an arc file.
ARCVIEW2 OS/2 Command to view the contents of an arc file.
The above keywords are the command line syntax for arcing and
unarcing. DO NOT use destructive options such as -M to move
to a arc but rather -A to add to a arc. Likewise for unarcing
don't use the command that deletes the origional .arc. If the
keyword is needed and is not provided then the arcing or
unarcing will not take place. WARNING!!! Some versions of arc
will cause the system to lockup if the wrong command line options
are used!. To be sure that the command line options are correct
try the command first from the command line yourself. Any command
that requires operator response beyond the initial command line will
not work with NLU.
═════════════════════════════════════════════════════════════════════════════
Node List Update Utility (NLU) Page 10
═════════════════════════════════════════════════════════════════════════════
LZH DOS Command to add a file to an lzh file.
LZH2 OS/2 Command to add a file to an lzh file.
UNLZH DOS Command extract a file from an lzh file.
UNLZH2 OS/2 Command to add a file from an lzh file.
LZHVIEW DOS Command to view the contents of an lzh file.
LZHVIEW2 OS/2 Command to view the contents of an lzh file.
The above keywords are the command line syntax for lzhing and
unlzhing. DO NOT use destructive options such as -M to move
to a lzh but rather -A to add to a lzh. Likewise for unlzhing
don't use the command that deletes the origional .lzh. If the
keyword is needed and is not provided then the lzhing or
unlzhing will not take place. WARNING!!! Some versions of LHA
will cause the system to lockup if the wrong command line options
are used!. To be sure that the command line options are correct
try the command first from the command line yourself. Any command
that requires operator response beyond the initial command line will
not work with NLU.
ARCPREF
Options are Z for zip, A for arc, or L for LZH. This will specify
your preference of packing methods.
APPLYDIFF
Include this keyword if you want diffs applied to lists.
APPLYCOMMAND DOS command to apply diffs
APPLYCOMMAND2 OS/2 command to apply diffs
After these keywords place the command to apply diffs. If you need
to be in a special directory to run the command then use a batch
or .cmd file that does the CD for you. It is not necessary for the
batch or cmd file to return you to the current directory.
CLEANUP
Cleanup has four options, LISTS, DIFFS, ALL, and NONE. This keyword
has no effect if you did not include the APPLYDIFF keyword. This
keyword specifies what files to cleanup after applying a nodediff.
With the LISTS option, the old list will be removed from the active
directory after applying the diff and creating the new list. The
DIFFS option will cause the diff to be deleted from the active
directory after being applied. The ALL option cleans up both lists
and diffs. The NONE option disables all cleanup the same as omitting
the keyword.
═════════════════════════════════════════════════════════════════════════════
Node List Update Utility (NLU) Page 11
═════════════════════════════════════════════════════════════════════════════
CONVERT
Convert has no options. Including this keyword will cause any archived
files that are in a different format than the format specified in the
ARCPREF keyword will be converted to your preferred format.
SKIPTEST
The use of this keyword is NOT RECOMMENDED! This keyword will disable
the archive confidence test that runs each time NLU is started. The
confidence test tests all necessary options of the archive commands
to make sure they are installed properly. In the event that you
install a new version of zip, arc, LHA or whatever this test will insure
that your lists and diffs will not be trashed as a result of an
unexpected change.
MAGICDIR
This keyword should be followed by the path to a magic file
directory. This is for mailers like D'bridge that don't have a magic
file list. If this keyword is used then the magic directory will be
updated to contain only the newest of each list and diff. This means
that you can tell your mailer to send {magicdir}\nodelist.* for the
magic file NODELIST and so on. Comment out this keyword if you do
not want to keep a magic directory or don't want NLU to update it.
MAGICLIST
This keyword specifies the name of the list file that your
mailer uses to specify magic file names. The format of this list
file is;
MAGICNAME d:\pathname\filename.ext
for example
NODELIST E:\FILES\NODELIST\NODELIST.Z41
NODEDIFF E:\FILES\NODELIST\NODEDIFF.Z41
FMLYDIFF E:\FILES\NODELIST\FMLYDIFF.Z41
FMLYLIST E:\FILES\NODELIST\FMLYLIST.Z41
etc.
═════════════════════════════════════════════════════════════════════════════
Node List Update Utility (NLU) Page 12
═════════════════════════════════════════════════════════════════════════════
Program Flow
Before getting started with the program flow it is very important to
understand some terminology. First of all there are four directories
involved. Each directory has a name which will be used from hereon.
First there is the inbound directory where your mailer puts incoming
files. This directory will be called "INBOUND". Then there is the
directory where you keep files for others to download and/or file
request. This directory will be called "DOWNLOAD". The third directory
is the directory where you keep your unarchived lists for your nodelist
compiler. This directory will be called "ACTIVE". Some mailers will
support MAGIC file names which can be used for people to file request
the latest LIST or DIFF. The latest LIST & DIFF can be kept in a special
directory for Magic file requesting. This directory will be refereed
to as MAGICDIR.
Since this document is written for both the technically minded and the
not so technically minded I will attempt to describe the program flow
in a rather simple form so that all will understand. In the flow I will
place labels. You will find some lines that say "GO BACK TO LABEL ###".
This should be self explanatory soon.
Beginning the Program Flow;
STEP 1 ** CONFIDENCE TEST **
If the SKIPTEST keyword is NOT included then;
Run the archive confidence test by creating a test text file
called TESTFILE.123. This file is then archived into a LZH
format file called TESTFILE.L23. The LHA view command is then
executed to see if the origional TESTFILE.123 can be found. Then
LHA is called to unarchive TESTFILE.L23 into TESTFILE.123. This
will test all three commands (archiving, unarchiving, & viewing).
If any of these three failed the program will display an error
message and terminate. This test is then repeated with the
ARC format then with the ZIP format.
STEP 2 ** REGISTRATION CHECK **
If you are NOT registered then;
Annoying beeps and sounds and delays will happen and you will
be told that you are not registered and just how cheap it is to
register your copy ($5).
If you ARE registered then;
Your name will quickly and silently be displayed as the
registered owner.
STEP 3 ** FILE TOSS **
If the TOSSFILES keyword IS included then;
Any files in the INBOUND directory that have a file name matching
a file name specified with either the LISTNAME or DIFFNAME keyword
will be MOVED to the DOWNLOAD directory.
If the UPDATE_FILELIST keyword is included then;
The files that were just tossed into the DOWNLOAD directory
will be inserted into the FILES.BBS files in the order
specified by FILELIST_ORDER. The descriptions added will
be as specified in LISTDESC or DIFFDESC.
═════════════════════════════════════════════════════════════════════════════
Node List Update Utility (NLU) Page 13
═════════════════════════════════════════════════════════════════════════════
STEP 4 ** FILE CONVERSION **
If the CONVERT keyword IS included then;
Any files that are in the DOWNLOAD directory that are in a format
other than that specified by the ARCPREF keyword will be converted
to the format specified by ARCPREF. The FILES.BBS file will be
updated with the modified file names.
STEP 5 ** LIST & DIFF INSTALLATION **
If there is a LIST file in the DOWNLOAD directory that is newer than
the file in the ACTIVE directory by the same name then;
The file is unarchived into the active directory.
If there is a DIFF file in the DOWNLOAD directory that is newer than
the file in the ACTIVE directory by the same name then;
The file is unarchived into the active directory.
STEP 6 ** DIFF TO LIST APPLICATION **
If there is a DIFF file in the ACTIVE directory AND the APPLYDIFF
keyword is used then;
The command specified by the APPLYCOMMAND or APPLYCOMMAND2 will
be executed and DIFFS applied to LISTS.
STEP 7 ** NEW LIST ARCHIVING **
If there is a LIST file in the ACTIVE directory newer than the newest
file by the same name in the DOWNLOAD directory then;
The newer LIST file will be archived into the DOWNLOAD directory
using the format specified in the ARCPREF keyword. If the
UPDATE_FILESLIST keyword is specified then The FILES.BBS file will
be updated with the newly archived file.
STEP 8 ** DOWNLOAD DIRECTORY PURGING **
If the number of LISTS in the DOWNLOAD directory is greater than
the number of lists specified by MAXLISTS then;
The oldest LIST files will be purged until the number of lists
is NOT greater than the number of lists specified by the MAXLISTS
keyword. This is a per list name function. For example: if you
have two different lists like NODELIST and FMLYLIST then this
procedure would be repeated for each list.
If the number of DIFFS in the DOWNLOAD directory is greater than
the number of diffs specified by MAXDIFFS then;
The oldest DIFF files will be purged until the number of diffs
is NOT greater than the number of diffs specified by the MAXDIFFS
keyword. This is a per diff name function. For example: if you
have two different diffs like NODEDIFF and FMLYDIFF then this
procedure would be repeated for each diff.
STEP 9 ** ACTIVE DIRECTORY PURGING / CLEANUP
If there are more than one of each LIST in the ACTIVE directory and
the CLEANUP keyword includes ALL or LISTS then;
The excess lists will be deleted from ACTIVE.
If there are ANY DIFFS in the ACTIVE directory and the CLEANUP keyword
includes ALL or DIFFS then;
All DIFFS will be deleted from ACTIVE.
═════════════════════════════════════════════════════════════════════════════
Node List Update Utility (NLU) Page 14
═════════════════════════════════════════════════════════════════════════════
STEP 10 ** MAGIC FILE UPDATE **
If the keyword MAGICDIR is used then;
The MAGICDIR directory will be updated to include only the newest
of each LIST and DIFF file.
If the MAGICLIST keyword is used then;
The magic list will be updated to include only the newest of each
of the LISTS and DIFFS.
STEP 11 ** MORE REGISTRATION CHECKING **
If you are NOT registered then;
You will be presented with a random four digit number and asked
to re-enter that number to continue. The program will not
continue until you re-enter that number. Each time you enter
an incorrect number you will be presented with the same number
again and asked to enter it. This makes it impossible to run
in unattended mode until you register. It's only $5.00 to
register.
END of Program.