Note:|
Program file: |
MODLISTG2.EXE |
|
Purpose: |
This tool is used to manage the various Praetor lists. It is invoked from a command prompt or batch file with one or more parameters. If importing new list entries, the change
takes effect immediately with
the very next message. |
|
Usage: |
MODLISTG2 <command> <parameters>. See
below. |
|
Other: |
You can display a help screen by invoking this program with '?' as the one and only parameter. |
|
Command and parameters |
Description | ||||||||
|
/HELP or /? |
Display a command summary. | ||||||||
|
/SORT: <list> |
Sort the items of the specified list. | ||||||||
|
/CLEAR: <list> |
Clear all entries from the specified list. | ||||||||
|
/CPYITEMS: <source-list>, <destination-list> |
Copy all entries from the source to the destination list. | ||||||||
|
/MOVITEMS: <source-list>, <destination-list> |
Move all entries from the source to the destination list; source list
is empty. | ||||||||
|
/EXPLISTS: <summary-file> |
Export a summary of the Praetor lists with all their entries into the
text file specified. | ||||||||
|
/SETLISTS: <summary-file> |
Restore the Praetor LIST.DAT file with the lists found in the specified summary file. NB: There is no space after the colon. This command will also backup the original Praetor.DAT file is made
before restoring, giving that backup copy a name of the form PRAETOR.<yyyymmdd>
where the date is used as a 8-digit extension. | ||||||||
| /EXPRULES: <rule-file> |
Export a summary of rules to the specified file. | ||||||||
| /MODIFY: <list> /INP:<input-file> |
Modify the list with entries found in the specified input file. Each line of this file can be one of the following: +<item> to add the item -<item> to remove the item Example:
| ||||||||
|
/ADDITEMS:<list> /INP:<input-file> |
Add the items found in the input file into the named list. The input file must have 1 item per line without the need for the '+' or '-' character in the first column position. For a checked list, you need to have either a space to indicate unselected
entry, or a '>' for a selected checked entry. | ||||||||
|
/DELITEMS:<list> /INP:<input-file> |
Delete items in the specified file from the named list. Format
of the input file is one entry per line without the
need for the '+' or '-' character in the first column position. |
MODLIST can be invoked either with individual commands or a single command file can be created with all needed parameters and then invoked with the command file specified as a parameter.
MODLISTG2 command-file
To see the names of the various lists used by Praetor's numerous selectable conditions, click here.
Note:
|
The underscores in the list names and case are significant and must be used when using MODLIST tool although they appear without underscores in the Praetor administration program. Also, be sure all input-file entries are immediately followed by a carriage return-line feed (CRLF) end-of-line terminator. Any trailing spaces between your entry and the CRLF will be considered as significant and will be imported into the list. Unintentional trailing spaces are not obvious when the list entry is show on-screen and may cause Unexpected filtering results because the search using that list will fail to match on the entry. |
Invoke the program twice as follows:
MODLISTG2 /MODIFY: _approved_local_address /INP: manual.txt
MODLISTG2 /SORT: _approved_local_address
where manual.txt contains:
|
+John.Galt@mydomain.com |
Place these following entries into a file called Auto.txt:
|
/MODIFY: _approved_local_address /SORT: _approved_local_address |
Invocation:
MODLISTG2 Auto.txt
Combining the concepts introduced in the above two examples, here is the recommended method to use if you can automatically generate the list of entries into a file.
Using the sample manual.txt file, place these following MODLIST commands into a second file called AutoInp.txt.
|
/MODIFY: _approved_local_address /INP: manual.txt |
Next, using a scheduling program, invoke MODLIST as follows:
MODLISTG2 AutoInp.txt