Beijing Paradise BBS Backup

home *** CD-ROM | disk | FTP | other *** search

/ Beijing Paradise BBS Backup / PARADISE.ISO / software / BBSDOORW / XLAX_232.ZIP / XLAXNODE.DOC < prev next >

Wrap

Text File | 1989-02-18 | 77.8 KB | 1,782 lines

XLAXNODE II The Next Generation Nodelist Utility Program and Documentation Copyright 1987, 1988 By Scott Samet Friends of Dorothy 1:135/990 This version adds support for FrontDoor 2.0 (Gamma 1.13 and later) and TPBoard 5.0. The program has been overlaid to reduce memory usage by 20k, and several bugs have been corrected. Acknowledgements This program was inspired, in part, by the work done by Thom Henderson in XLATLIST and Rick Huebner in PCPEXCH. Credit also goes to Mike Janke (135/4) and Chris Baker (135/14) who put up with all sorts of stupid questions when I didn't know an Opus from an ice cube. And to the sysops of Net 135, especially Henry Van Leer (135/27) who tested version 0.0 and used it anyway! Most of the support for Seadog functions is a result of Chris Baker and Al de la Torre (135/7) sending netmail messages that started "Why doesn't it..." XLAXNODE II Page 2 License The program and associated documentation are Copyright. Programs with alphabetic characters in their version number are BETA versions. Distribution of these versions is prohibited and use is restricted to authorized beta testers. DISTRIBUTION: You may distribute the program on magnetic media or via modem, provided you distribute the original, unaltered archive. You may repack and change the file type to reflect the use of another library utility (PAK, ZOO, DWC, etc). You may not alter, add or delete anything within the file. This program is distributed in combination with its companion program, XlaxDiff, as a single file. If you received one without the other, someone has violated the distribution license. USE: You may use this program for a thirty day evaluation period without charge. After the evaluation period, you are expected to pay the license fee or discontinue using the program. During the evaluation period, the program will request keyboard input each time it is invoked. After installation of the license key, the program will operate without intervention. It can then be used in an unattended batch file. The $10 license fee covers operation of this program and the companion program, XlaxDiff, to create a nodelist for a single node. If you operate multiple nodes or distribute compiled nodelists to other systems, a license is required for each. To request a license, send the zone/net:node number(s) used in your control file NODE statement. No payment is required for AKA numbers; do NOT include them in your list. Send $10 for EACH node listed, your name and address (legibility counts) to: Scott Samet PO Box 162082 Miami, FL 33116-2082 USA Payments must be in US Dollars on a US Bank; or Canadian Post Office US Dollar Money Orders. Send currency at your own risk. Your License key(s) and thirty-second installation instructions will be sent via FidoNet. Keys not deliverable via FidoNet will be mailed. XLAXNODE II Page 3 Warranty This program is distributed on an as-is basis. You have a thirty day evaluation period to decide if it operates to your satisfaction. EXCEPT AS PROVIDED ABOVE, AND SUBJECT ANY CONTRARY PROVISIONS OF APPLICABLE STATE LAW, ANY AND ALL IMPLIED WARRANTIES, INCLUDING WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, AND ANY WARRANTY COVERAGE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES ARE HEREBY DISCLAIMED. IN NO EVENT SHALL DAMAGES EXCEED THE LICENSE FEE PAID. If you have suggestions or problems, before or after licensing, please follow the problem reporting procedures found at the end of this document. XLAXNODE II Page 4 What does it do? XlaxNode is a nodelist processing utility designed to replace many of the existing utilities with a single step. It will produce any or all of the following files in one pass: Opus 1.0x: NodeList.Sys and NodeList.Idx* Opus 1.1x: NodeList.Dat and NodeList.Idx* Binkley 1.50: NodeList.Ext and NodeList.Idx* QuickBBS: QNL_DAT.BBS and QNL_IDX.BBS (including Pursuit processing and the "Binkley Extensions") TBBS/Seadog: NodeList.Dog, NetList.Dog and Index.Dog FrontDoor 2.0: Nodelist.FDX, Nodelist.FDA, Phone.FDX, Phone.FDA, Userlist.FDX, Password.Sys and FDNet.PVT TPBoard 5.0: NodeList.TPB and NetList.TPB * A single NodeList.Idx may be shared by all three files. In addition, it will produce the following files that are not specific to a particular system: NodeList.Fon RouteGen work file FidoUser.Lst User Name lookup file NodeList.BBS Time honored FidoNet Nodelist NodeList.DLM Delimited for Spread Sheet or Database import The following files are optimized for interface with Opto- Isolated Carbon-based Biochemical Systems: NodeList.Prn 132 columns wide (index optional) NodeList.Txt 80 columns wide (index optional) NodeList.Dbl 80 columns, two lines per node (index optional) NodeText.BBS 80 columns, no pagination, for online viewing Coord.nnn 80 columns, Zone, Region and Net Coordinators The program will do the processing required to support PC Pursuit scripts for Opus 1.0x and 1.1x and Binkley. It will also prune the nodelist, selecting the desired Zones and Nets. XLAXNODE II Page 5 What doesn't it do? XlaxNode is designed as a FidoNet utility. Nodelists produced by other networks should be processed correctly if they conform to FidoNet Technical Standards Document FTS- 0002. Non-conforming nodelists may produce unpredictable results (in other words, you may not like the output). OPERATION There are some differences between this program and the program(s) you are probably using. You may get an error message or even different results. Take a time to read the docs and avoid problems. By default, this version uses IBM PC BIOS calls for the video display. The -G switch on the command line will force the use of ANSI escape sequences. Machines without PC BIOS compatibility, such as the Z-100 or DEC Rainbow MUST use the -G switch. When used under DOS 2.x, the EXE file must reside in the current directory; the DOS PATH will not suffice. XLATLIST processes DIAL and COST strings in the order you enter them. If you have the same string more than once, XLATLIST will ignore the extra ones. You will now get an error message. You need to figure out why you have duplicates, and fix your input file. If you have a shorter string before a longer one, e.g. "1-305" before "1-305-555", than XLATLIST will never use the longer string. XlaxNode sorts the strings and the longest are processed first. In the previous example, both strings will be used. Failure to heed these warnings will result in different output than you are used to getting. By default, the program will look for a file named XLAXNODE.CTL in the current directory. This can be overridden by using -Cfilename on the command line. The dummy control file (XLAXNODE.CTL) included with the program contains an INCLUDE statement to read your existing XLATLIST.CTL file. Since this version can produce any or all of its output files in a single pass, the default is to disable all output. Insert additional statements to enable the XlaxNode output and options you need. XLAXNODE.CTL is a standard Ascii text file. Each control statement is entered on a separate line. A semi-colon indicates that the rest of the line is to be treated as comments. Blank lines or lines starting with semi-colons are also comments. No line, even a comment line, may exceed 255 characters in length. XLAXNODE II Page 6 You may augment or override commands in the control file by placing them on the DOS command line. Commands that require arguments must be enclosed in Ascii quotes ("). The COST and DIAL commands require multiple lines and cannot be placed on the DOS command line. For example, if you are running a temporary modem at 1200 baud, you might enter: XLAXNODE "MAXBAUD 1200" This is the same as including the corresponding statement at the end of your control file. If an error occurs during processing, XlaxNode will terminate and return an error code that can be tested in the batch file. Error codes and their causes are: 0 Normal completion, no errors. 1 No output files enabled. 2 CRC Error in input nodelist. 5 Not enough memory to continue. 6 No NODELIST.nnn file found to process. 7 Error in a control statement. 8 Attempt to open a file failed. 9 Sort or Disk I/O Error occurred. COMMANDS INCLUDE filename Indicates an auxiliary file containing XlaxNode Control statements. XlaxNode will read and process the named file, then continue with the next statement in the current file. Include files may be nested, subject to DOS limits on the number of files open. NODE <zone>:<net>/<node> This is REQUIRED. It must be the first statement of the control file. Enter the primary node number of the system on which the compiled nodelist will be used. Do not enter AKA addresses. Example: NODE 1:234/567 XLAXNODE II Page 7 UPDATE command-string NOUPDATE Allows you to invoke a nodelist update program (XlaxDiff or equivalent) before processing begins. Command-string is the full command, including all arguments, just as you would type it at the DOS prompt. If the program returns an error code greater than 1, XlaxNode processing will be aborted. Examples: UPDATE XlaxDiff /E=D:\NetFiles /C UPDATE EditNL Only one UPDATE is permitted. If you have multiple nodelists to update, you will need to use a batch file to run XlaxDiff before you invoke XlaxNode. COUNTRY Here's where you enter the international telephone prefix for your country. The default is "1-", which is used by most of North America. MAXBAUD nnnn [<flagvalue> <baudrate>]... Tells the maximum speed of your modem. This value will replace the speed of any faster nodes. The optional flag mmmm pairs specify a different baud rate to be used if <flagvalue> appears in the flags field of the nodelist entry. If more than one <flagvalue> matches a nodelist entry, the last one will be used. Examples: MAXBAUD 1200 ; All calls limited to 1200 MAXBAUD 2400 HST 9600 ; HST at 9600 others at 2400 MAXBAUD 2400 HST 9600 V32 9600 ; HST and V32 at 9600 MODEMSTRING <flagvalue> <prefixstring> <suffixstring> Inserts <prefixstring> in front of the phone number and <suffixstring> after the number when <flagvalue> appear's in a node's flag field. TrailBlazer owners may want to insert something like the following into their control file to force PEP mode when calling another PEP modem: MODEMSTRING PEP S50=255DT This command can be repeated. If a node matches more than one <flagvalue> only the last one will be used. XLAXNODE II Page 8 PUBLIST [path\]nodelistname This allows you to override the standard name, NODELIST, for the input file. Specify an optional drive:path, followed by the 1-8 character file name. Do NOT enter the period or file type. The program will select the latest list provided you do not have any files over six months old. Multiple Public lists are NOT supported. Use ADDLIST for any additional lists, such as AlterNet or EggNet. Example: PUBLIST D:\OPUS\FILE\NET\NODELIST PUBLIST ANETLIST XLAXNODE II Page 9 ADDLIST <filename>... MYLIST <filename>... PVTLIST <filename>... These keywords allow you to specify additional nodelists. Entries from MYLIST files will be included in the human readable nodelists. Entries from PVTLIST files will not. By popular demand, and against my better judgment, FSC002 is relaxed to permit spaces and tabs in these lists. ADDLIST functions like MYLIST except that the header line with CRC value is MANDATORY. Use ADDLIST when processing a distributed nodelist like AnetList or Egglist. Opus 1.0x and Seadog may have problems if net numbers are duplicated. The NET keyword may be used to modify problem net numbers. You may include as many file names as will fit on the line and use as many of these statements as you wish. Use "###" as the file type to select the highest numbered nodelist. Example: ADDLIST ANETLIST.### PVTLIST POINT1.NET POINT2.NET Some users may wish to treat zoned nodelists, such as AlterNet or EggNet, as if they were part of their own zone. This allows direct calls, without the use of a ZoneGate. This may be done by prefixing the file name with an exclamation point. This feature, which I call the "Region Replacement", causes the Zones to be changed to Regions in the output file. Be sure to include ZONE and/or NET statements to make the required selections. All references to these nodelists within XlaxNode (Password, Phone, XPursuit, etc.) MUST refer to the original zone. Example: ADDLIST !ANETLIST.### NET 7:40 PASSWORD 7:40/0 YOOHOO Nodelists must be called in the following sequence: Lists without Zone Statements Zoned Lists with Region Replacement Zoned Lists without Region Replacement XLAXNODE II Page 10 ZONE <n> [<n>...] ONEZONE GATED ALLZONES COMPLETE The Zone statement selects the zones to be included in the nodelist. Do not overlook your own zone; it is not included unless you request it. For compatibility with earlier versions, OneZone or Gated is interpreted as "Zone n" where n is the zone you specified in your NODE statement. AllZones or Complete is interpreted as "Zone 1 2 ... 99". Zones 1 - 99 are supported. Most other nodelist processors automatically include certain admistrative nodes for every zone. XlaxNode normally omits these nodes to reduce the chances of dialing an international call by accident. They may be included with the NET command. Zone Coordinator (n:n/0) records are always selected and cannot be excluded due to internal housekeeping considerations. Older software, such as Opus 1.0x and Seadog, does not recognize zones in the nodelist. The entire nodelist is assumed to be in your zone. If you use the Zone or AllZones commands to select another zone, all its nets will be included as if they were in your zone. This may cause problems with duplicate net numbers. See the NET statement for a solution. Newer software, such as Opus 1.1x, Binkley or QuickBBS, supports zones. You may select as many zones as you wish, or restrict zones to reduce the size of the nodelist. See the NET command for examples. NET <zone>:<net> [ <newnumber> | - ] OZONE <zone>:<net> [ <newnumber> | - ] The NET command serves several functions. You must always enter the zone and net number. The zone does not have a default value. OZONE is accepted for compatiblity with other programs. Listing a zone:net with no other arguments will include the net, even if its zone has not been requested by the Zone statement. Listing a zone:net followed by a minus sign will exclude the net, even if its zone has been requested by the Zone statement. XLAXNODE II Page 11 Listing a zone:net followed by a new net number will include the net in the output files and alter its number. Opus 1.0x and Seadog may have problems when net numbers are duplicated. This option allows you to resolve this conflict. Example 1: NODE 1:234/567 ; My Zone is Zone 1. ONEZONE ; Same as "ZONE 1" NET 2:2 ; Include Zone 2 Admin Nodes NET 2:501 ; Also include Net 2:501 Example 2: NODE 2:345/678 : My Zone is Zone 2. ZONE 1 2 7 ; Select Zones 1, 2 and 7 NET 1:1200 - ; Exclude Net 1:1200 NET 1:1201 - ; Exclude Net 1:1201 NET 2:50 ; Region 2:50 Independents NET 3:3 ; Add Zone 3 Admin Nodes NET 7:500 7500 ; Change Net 7:500 to 7500 NET 7:630 7630 ; Change Net 7:630 to 7630 Example 3: NODE 1:135/990 ZONE ; Don't select ANY zones NET 1:135 ; Just my own net NET 1:369 ; and the one next door SORTWORK [path\]filename If a sort cannot be completed in memory, a disk work file will be created and deleted when no longer needed. SORTWORK controls where the file will be placed. An Extended or Expanded Memory ramdisk is an ideal place for this file. If this statement is omitted, the file will be created in your current directory. The SEADOGLIST, FDLIST, SINDEX, and USERLIST/INTERLIST options trigger sorts, although only the user lists are likely to overflow to disk. BUFFERS <number> Allows you to increase or decrease the size of the file I/O buffers used by the program. The default is 4; values of 1 to 6 may be specified. If you specify too large a value, the program will abort with a Heap Overflow message. For best performance, use the largest value that will allow the program to run without any of the sorts reporting a disk work file has been used. Example: BUFFERS 6 XLAXNODE II Page 12 REPORT NOREPORT Generates a cute little report about how many nodes there are, how many are down, on hold and private. Since the program doesn't have any limits on the number of nodes, why do you care? Default is NOREPORT. CRCCHECK NOCRCCHECK Causes XlaxNode to scan the input files and report any CRC errors even if no output files have been requested. If any output files are requested, this command is ignored and CRC checking will always be done. Default is NOCRCCHECK. PROGRESS NOPROGRESS Displays the input filename, zone, region and net number while the nodelist is being scanned. Using this option with a speech board will really slow things down. NOPROGRESS suppresses this display. PROGRESS is the default. COMMENTS NOCOMMENTS Copies any comments from the raw nodelist the report file as they are read. Error messages from the nodelist generation utilities are inserted in the nodelist as comments. Don't confuse these messages with messages generated by XlaxNode. NOCOMMENTS is the default. HOSTMARKER <string> Flags any host routed private and hold nodes by inserting <string> in front of the node name. Any program that displays the node name will display this flag. It serves as a warning that there is no way to send direct transmissions (file requests, attaches, crash mail) to this node. String may be 1-10 characters and should be omitted to cancel this function. Example: HOSTMARKER Host> HOSTMARKER The second example cancels host flagging. The default is the less than symbol (<). XLAXNODE II Page 13 DASH NODASH The exciting NODASH option strips the dashes out of phone numbers written to the nodelist files. Some modems get upset if the dial strings are too long, and this can make them shorter. It also makes them very difficult to read. DASH is the default. Unlike Other<tm> programs, XlaxNode knows if a number is domestic or international, even if the dashes are removed. OLDOPUSLIST [ NOPURSUIT | OLDPURSUIT | NEWPURSUIT ] VERSION5 [ NOPURSUIT | OLDPURSUIT | NEWPURSUIT ] NOOLDOPUSLIST For Opus 1.0x. Writes the NODELIST.IDX and NODELIST.SYS files. NOOLDOPUSLIST is the default. VERSION5 is accepted for compatibility with ParseLst. The PURSUIT subcommands allow you to control the Pursuit script processing. The default, NOPURSUIT, suppresses script processing for this nodelist. OLDPURSUIT does the processing for Opus 1.0x, while NEWPURSUIT does the processing for Opus 1.1x and Binkley. If you are using Binkley to do all your mail, but wish to share the nodelist with Opus 1.0x, then the NEWPURSUIT option might be helpful. NEWOPUSLIST [ NOPURSUIT | OLDPURSUIT | NEWPURSUIT ] VERSION6 [ NOPURSUIT | OLDPURSUIT | NEWPURSUIT ] NONEWOPUSLIST For Binkley 2.0+ and Opus 1.1x. Writes the NODELIST.IDX and NODELIST.DAT files. NONEWOPUSLIST is the default. VERSION6 is accepted for compatiblity with ParseLst. The PURSUIT subcommands allow you to control the Pursuit script processing. The default, NOPURSUIT, suppresses script processing for this nodelist. NEWPURSUIT does the normal processing for Opus 1.1x and Binkley, while OLDPURSUIT does the processing for Opus 1.0x. I can't think of any reason for doing old style pursuit processing with this nodelist. Let me know if you do. BINKLIST NOBINKLIST Writes the NODELIST.IDX and NODELIST.EXT files. NOBINKLIST is the default. These files provide additional information needed by Binkley 1.50 when running with the TBBS/Seadog files as the primary nodelist. XLAXNODE II Page 14 QUICKBBSLIST [ NOPURSUIT | OLDPURSUIT | NEWPURSUIT ] NOQUICKBBSLIST Writes the QuickBBS QNL_DAT.BBS and QNL_IDX.BBS files. NOQUICKBBSLIST is the default. The PURSUIT subcommands allow you to control the Pursuit script processing. The default, NOPURSUIT, suppresses script processing for this nodelist. NEWPURSUIT does the normal processing for Opus 1.1x and Binkley, while OLDPURSUIT does the processing for Opus 1.0x. I can't think of any reason for doing old style pursuit processing with this nodelist. Let me know if you do. SEADOGLIST NOSEADOGLIST Writes the NODELIST.DOG, NETLIST.DOG and INDEX.DOG files. NOSEADOGLIST is the default. TBBSLIST NOTBBSLIST Synonyms for SEADOG. TPBLIST NOTPBLIST Writes the NODELIST.TPB and NETLIST.TPB files. NOTPBLIST is the default. FDLIST [ LONGUSER | SHORTUSER ] NOFDLIST Writes the FrontDoor 2.0 files. See the heading "FrontDoor Considerations" for important information about how XlaxNode and FrontDoor interact. NOFDLIST is the default. SHORTUSER shrinks the user index by removing multiple listings for a single name. The "best" node for each name will be selected. LONGUSER, the default, will include all listings. USERLIST [ OPUS | SEADOG ] INTERLIST [ OPUS | SEADOG ] NOUSERLIST Creates an alphabetical directory of sysops and their node numbers. USERLIST is restricted to the sysops of nodes selected by you ZONE and NET commands. INTERLIST includes sysops of all nodes, selected or not. The default, NOUSERLIST, is for the No-Zone. OPUS, the default, formats the userlist for use with Opus 1.10 and Binkley. SEADOG formats it for use by Seadog systems. XLAXNODE II Page 15 ROUTE [ NOPURSUIT | OLDPURSUIT | NEWPURSUIT ] NOROUTE Writes NODELIST.FON, the ROUTEGEN work file. Mainly a Seadog file, rumor has it that this file is sometimes used by non-Seadog sysops. Default is NOROUTE. If OLDPURSUIT is selected, the flags field of each Pursuitable node will have the string "PCPURSUIT" appended. This can be checked in RouteGen with "FLAG-PCPURSUIT". If NEWPURSUIT is selected, "PCP-xxxxx" will be appended, where xxxx is the PCP outdial mnemonic. The general case can be checked with "FLAG-PCP-". To check a specific city, use "FLAG-PCP-FLMIA". NOPURSUIT is the default and suppresses all Pursuit processing for this file. NODELIST [ FIDO | OPUS | SEADOG ] NONODELIST Writes the NODELIST.BBS file. This file is not used by XlaxNode. There is no need to create it unless it is required as input for some other nodelist processor. The FIDO, OPUS, and SEADOG subcommands select the particular format to be generated. OPUS and NONODELIST are the defaults. FIDOPRN FIDOTXT FIDODBL NOFIDOLIST Gives you a people-readable version of the nodelist. FIDOPRN is 132 columns wide. FIDOTXT is 80 columns wide. FIDODBL is 80 columns wide, but uses two lines per node, like the LISTGEN output file that I am not old enough to remember. The default, NOFIDOLIST means you don't want any of these disk space hogs. See the section on PC Pursuit processing for information on how the contents of these files are modified for Pursuitable nodes. Also see SINDEX/INDEX and SQUEEZE. INDEX SINDEX NOINDEX Appends an index to the FIDODBL, FIDOPRN and FIDOTXT lists. SINDEX is sorted by Zone/Region/Net number, INDEX is in the same order as the lists. NOINDEX is the default. XLAXNODE II Page 16 NODETEXT [ <headerfilename> [ <trailerfilename> ] ] NONODETEXT Another people-readable version of the nodelist. This is formatted for online viewing. There are no page breaks or form feeds. If headerfilename and trailerfilename are specified, these files are inserted at the start and end of the generated report. You can insert a introductory message and/or oANSI control commands. See the section on PC Pursuit processing for information on how the contents of this file is modified for Pursuitable nodes. Also see SQUEEZE. COORDLIST NOCOORDLIST Creates a file named COORD.nnn, where nnn is the number of the input nodelist. This is a human readable text file listing the Zone, Region and Net coordinators. Also see SQUEEZE. SQUEEZE NOSQUEEZE Reduces the size of the human readable files by replacing strings of blanks with tabs. Reductions of 15-35% are typical, as are similar increases in execution time. NOSQUEEZE is the default. You may wish to avoid this option if you are using any kind of program to read the FIDOLIST files. Some programs are confused if the input file contains tabs, buttons or suspenders. DELIMITEDFILE [PURSUIT | NOPURSUIT] NODELIMITEDFILE This is a parsed version of the nodelist formatted for loading into dBASE, Lotus, Reflex or the like. A detailed file description is given near the end of this document. The additional processing triggered by the PURSUIT option is also described. ADDR This XLATLIST command has been replaced by the ADDRLIST command. XLAXNODE II Page 17 ADDRLIST filename This command refers to a personal file of names and node numbers that will be added to the FidoUser.Lst file. If one of these names exists in the nodelist, the address specified here will override the one that would normally be selected. The file is a standard ASCII text file. Each line has the following format: Address_String User_Name_String Address may be any string up to twenty characters. Seadog allows non-FidoNet addresses, so the address is not edited. Neither the address or name field may have any embedded blanks. Example: 1/1 Fido_News 1/1 FidoNews 3:3/0 Zone_Three_Cooord Palace@EmeraldCity@Oz The_Wizard IGATE [<zone>:[<net>/]]node OGATE [<zone>:[<net>/]]<node> GATE [<zone>:[<net>/]]<node> HUB [<zone>:[<net>/]]<node> The specified nodes will be marked in the NODELIST.FON files. In SeaDog mode, they will also be marked in the NODELIST.BBS file. Network host nodes are always marked as IGATE nodes and Network hub modes are always marked as HUB nodes. You need to enter these statments only for nodes that are not marked automatically. These commands may be repeated. PHONE [<zone>:[<net>/]]<node> <phonenumber> Allows you to override a node's phone number. If zone or net is omitted, your own will be assumed. This statement can be repeated as required. Entering a phone number for a private node will cancel the node's private status and host routing. Numbers entered with the PHONE command do not get listed in the human readable nodelists. You should enter the phone number in exactly the same format as the numbers in the nodelist. Use the DIAL translation to make any required alterations to the phone number. Example: PHONE 135/990 1-305-555-1212 XLAXNODE II Page 18 FLAG [<zone>:[<net>/]]<node> <+/=><flagstring> Allows you to replace or append to a node's flags. If net is omitted, your net will be assumed. A equal sign replaces a nodes flags, a plus appends to them. You should enter the flags in exactly the same format as the nodelist. This statement can be repeated as required. Examples: FLAG 135/990 +#CM: ; adds #CM: to existing flags FLAG 135/990 =HST,MO: ; replaces with HST,MO: BAUD [<zone>:[<net>/]]<node> <speed> Allows you to override a node's baud rate. If zone or net is omitted, your own will be assumed. This statement can be repeated as required. Example: BAUD 135/990 56000 ; Can you wait for this modem? PASSWORD [<zone>:[<net>/]]<node> password Allows you to enter a password into the Nodelist. Passwords are written to the Old and New Opus Nodelists, the QuickBBS nodeliist and the Binkley Nodelist. OldOpus truncates the password to six characters, the other nodelists to eight. Like PHONE or BAUD, this command may be repeated as desired. If you specify a password for a private node, the program will issue a warning message and cancel the node's host routing. Example: PASSWORD 222/1 HotWoc PASSWORDFILE filename Provides an alternate method of entering passwords into the Nodelist. This file is the same format as the OpusNode.PWD file. Each line has the following format: [[<Zone>:]<Net>/]Node Password Example: 333/1 HotWoc 444/2 P42JW9 2:555/1 PW4ME2U ; OldOpus Truncated to six chars XLAXNODE II Page 19 DIAL <domestic> <international> It's unlikely that you will be able to use the numbers from the nodelist exactly as they are. If 1-305-555-1212 is a local call, the phone company is likely to laugh at you if you try to dial all 10 digits. Numbers in the nodelist need to be "munged" into a format acceptable to Mother Bell (or Gee Hee Hee). The DIAL table is a set of rules for that job. It starts with a DIAL line, contains zero or more detail lines, and finishes up with an END statement. Each detail line in the DIAL table consists of a search part and a replacement part. The search part of each line is matched against a node's phone number. As soon as a match is found, the part matched is replaced, and processing continues with the next phone number. Assume the following line in the DIAL table: 1-305-555 555 ; Search for "1-305-555" replace with "555" If the phone number is 1-305-555-1212, then the 1-305-555 will be replaced by 555 and the result is 555-1212. This is the normal format for a local call. You'll probably want a DIAL line like this for every local prefix. Now consider long distance within your own area code. You probably need to dial 1 and the seven digit number. After listing all your local prefixes in the DIAL list, make the following entry: 1-305- 1- If the 1-305-976 prefix was not individually included in the DIAL list, then this entry would change 1-305-976-1212 into 1-976-1212. If you can dial your entire area code without a 1- prefix, then you don't need to detail the local exchanges. Just specify: 1-305- / This will strip the 1-305- from every number in the area code. For most places, this about covers it. For long distance calls outside your own area code, you dial the number just as it appears in the nodelist. XLAXNODE II Page 20 Here's an abbreviated version of my DIAL list: DIAL / 011-/# 1-305-222 222 ; local call 1-305-223 223 ; local call . . . 1-305-939 939 ; local call 1-305 1- ; long distance within 305 END If you're sharp, you're wondering about the / 011-/# on the DIAL statement. The entries on the DIAL statement specify what to do if NONE of the DIAL lines match. For domestic calls, we don't need to do anything. The first slash just serves as a place holder so nothing gets done to domestic numbers. For international calls we need to insert 011- in front of the number. Inserting # at the end of international numbers speeds completion of the call. If you're connected to a switchboard that needs 9 before all local calls, and 8 before all long distance calls, then your table might look like this: DIAL 8 8-011 1-305-222 9-222 ; local call 1-305-223 9-223 ; local call . . . 1-305-939 9-939 ; local call 1-305- 8-1- ; long distance within 305 END Suppose that you want to use a dial-up long distance carrier for those places not listed in your dial list. The following DIAL statement would do the job: DIAL 950-1234W9876* 011- This is saying, if a domestic phone number does not match anything in the DIAL list, then insert 950-1234W9876* before the number. International numbers would still get a 011- prefix. XLAXNODE II Page 21 Until now, I've ignored a feature that will not be used by many people. In addition to inserting things before the phone number, you can append things to the end of phone number. That's where the slash comes into play. If your long distance company wanted the security code AFTER the number, the DIAL statement would look like this: DIAL 950-1234W/*9876 -011 This says to insert 950-1234W in front of the number and *9876 after the number. When I called the slash a place holder, it was saying to insert nothing before and nothing after the number. You can use the slash in a DIAL detail line as well. If you wanted to use the dial up service within my your area code, then the line in your DIAL table would look like this: 1-305- 950-1234W/*9876 This would turn 1-305-976-1212 into 950-1234W976-1212*9876. NOTE! There is a difference in the way that XLATLIST and I handle dial entries. XLATLIST searches them in the order entered, so if you had entered: 1-305 1- 1-305-555 555 XLATLIST would NEVER use the second line. I sort them and always search the longest ones first, so I WOULD find and use the second line. If you enter strings in a sequence that will result in output different from XLATLIST, a warning message will be generated. As far as the program is concerned, domestic is any number that has the prefix specified in the COUNTRY statement (defaulting to 1-). Canada, Bermuda, parts of Mexico and the Caribbean Islands are dialed as domestic calls. You may have 1+ long distance service from a company that do not handle all these places. If you are using one of these companies, you will need something like: 1-809 10288-1-809 to send these calls via AT&T. A little hint: The discount periods for foreign places are not the same as for the US. From the US to Canada, lowest rates are midnight to 8 am, seven days a week. Daytime on Saturday and Sunday is NOT the lowest rate. XLAXNODE II Page 22 COST <dom-cost> <int-cost> [<spec-cost>] The COST table assigns prices to be charged for Network (Matrix) mail. It is structured a lot like the DIAL table. It begins with a COST statement, has one or more detail lines, and finishes with an END statement. The COST statement itself accepts three values, the prices for domestic, international and special nodes. These prices are defaults for any number that is not listed in the detail section. Special nodes are private nodes that you have assigned a password. They cannot be host routed, and there is no phone number available, so this cost will be used. If omitted, it defaults to the domestic value. Lines in the detail section start like lines in the DIAL list, with a partial phone number to search for. Each search string is followed by a cost, and an optional baud rate. The baud rate becomes an upper limit for calls to the numbers specified. Rather than continue with rules, an example should make it clear. COST 35 125 1-305-222 0 ; local call 1-305-223 0 ; local call . . . 1-305-939 0 ; local call 1-305 25 ; my own area code. 1-813 25 ; other places in Fla. 1-904 25 ; rest of Fla. 1-809-422 50 1200 ; Nassau 1-809-423 50 1200 ; Nassau 1-809 75 ; Bermuda, Bahamas, Etc. 1-905 90 ; Mexico 1-416 50 ; Ontario Canada 1-514 50 ; Quebec Canada . . . 1-800 0 ; Free Call END This first few lines make local E-Mail free. Calls to the rest of Florida are 25 cents. Calls to Nassau are fifty cents, and no matter what the speed in the nodelist, I want to call at no more than 1200 baud. The rest of area 809 is 75 cents. Calls to Mexico are 90 cents, etc. Any place not mentioned in the list will be 35 cents if it starts with the 1- prefix, and $1.25 otherwise. XLAXNODE II Page 23 PURSUIT <filename> <cost> <baud> <cxl-string>... This command defines certain parameters for PC Pursuit processing. For many sysops, the defaults are satisfactory. Filename defines the name of the various files used in Pursuit processing. The default is PCP. In the descriptions that follow, this filename is assumed. If you use a different name, you will have to make the necessary adjustments to the names used in the examples. The default cost is one cent. Opus 1.03 considers any node with a zero cost to be a local call. If you have your behavior windows set up to allow local calls during the day, then Opus will place daytime Pursuit calls and you'll be billed $10 - $14/hr. By setting the cost of a Pursuit message to a penny, Opus will not consider it a local call and avoid the high-rent periods. Opus 1.10 and Binkley allow you to set one value for the price a user is charged for a message and a different value for call scheduling purposes. See the remarks under the heading "OPUS 1.1x COST FIELDS". Baud is the maximum speed to be used for PC Pursuit. You should set it to 2400 (the default) unless you do not have a 2400 baud in-dial to Telenet. For any given node, the program will use the lowest of the node's baud rate, Telenet's outdial rate (from the data file described below) for the node's city, the in-dial rate specified here, and MAXBAUD. Even if it's not clear, it works perfectly. If Cxl-String appears in a node's flags entry, then Pursuit processing will be bypassed for that node. This allows you to bypass Pursuit and dial direct when a node has an HST or PEP modem. When this string is omitted (the default) all eligible nodes will be processed. Cxl-String can be repeated as many times as desired. You'll need a file called PCP.DAT containing a list of area codes and exchanges that can be reached via PC Pursuit. A sample PCP.DAT is included, but Telenet is actively adding new cities. The basic skeleton of the PCP.DAT file can be downloaded from the Pursuit bulletin board. Each line begins with an area code, starting in column one, followed by a list of exchanges within that area code. Exchanges need not be in sequential order. For example: 305 223 226 227 232 233 235 238 250 251 252 XLAXNODE II Page 24 This information should already be in the file when you download it. Insert a header line in front of each city. It's a standard Ascii text file, so use your favorite text editor. The header line consists of the word "NODE" in column one, a space and the name assigned to the outdial city by Telenet, another space and the maximum outdial baud for that city. This example indicates the outdial D/DCWAS supports 2400 baud (1200 is assumed). NODE D/DCWAS 2400 The Washington outdial node handles calls for area 202 and parts of 301 and 703. You should list all three area codes under a single header: NODE D/DCWAS 2400 202 xxx xxx xxx xxx xxx xxx 202 xxx xxx xxx xxx xxx xxx 301 xxx xxx xxx xxx xxx xxx 301 xxx xxx xxx xxx xxx xxx 703 xxx xxx xxx xxx xxx xxx 703 xxx xxx xxx xxx xxx xxx The New York outdial node serves 212 and 718, but you must dial 1-718 before calls to the latter. In this case you have a PREFIX statement: NODE D/NYNYO 2400 212 xxx xxx xxx xxx 212 xxx xxx xxx xxx PREFIX 1-718- 718 xxx xxx xxx xxx 718 xxx xxx xxx xxx The sample file included should make this clear. Any line that does not start with an area code or the words NODE or PREFIX will be treated as a comment line. The sample file uses semi-colons, but almost anything could have been used. For OLDPURSUIT processing, you will need PCP.INP, a skeleton script file used to create scripts for reaching each Pursuit outdial city. The specialized scripts will have file names PCP.1, PCP.2, etc. XLAXNODE II Page 25 The PCP.INP file is an Opus dialer script with two modifications. Special markers indicate where the outdial node and the special area-code prefix must be dialed. When the script is customized, the outdial node from the NODE statement will be inserted. If there is an area-code prefix, then it will be inserted as well. The two spots where these prefixes are to be inserted are indicated by statements starting in column one: <<<NODE>>> <<<PREFIX>>> The <<<NODE>>> statement causes the program to insert a line like: XMIT NYNYO into the output script. The <<<PREFIX>>> statement causes a line like: XMIT 1-718- to be generated if needed. If not, it will be suppressed. For NEWPURSUIT processing, you will need PCP.S12 for 1200 baud calls and PCP.S24 for 2400 baud calls. XlaxNode does not use these files or even check they exist. They will be used by Opus or Binkley when you place a call to one of these nodes. DIAL processing is very generalized, and works on the basis of string matches. In order to work with international phone numbers, it makes no assumptions about their format or punctuation. PURSUIT processing is just the opposite. It works only with North American format phone numbers. The number must look like "1-NNN-NNN-NNNN"; be exactly fourteen characters long, start with a "1" and have three hyphens where indicated. The other characters must all be numbers, and the middle digit of the area code must be a zero or a one. Any number not meeting these criteria is not eligible for Pursuit processing. How does PC Pursuit Processing interact with DIAL processing? An area code/prefix that you fully specify in the DIAL list will take priority over the Pursuit entry. An DIAL entry consisting of a shorter string will NOT take priority over the Pursuit entry. XLAXNODE II Page 26 What if you live in a Pursuitable city? You don't want to use Pursuit to make local calls. Assume both prefixes are listed in PCP.DAT, but 305-555 is local and 305-976 is long distance. You probably have the following DIAL lines: 1-305-555 555 1-305 1 The DIAL entry that matches 555 is nine characters long, so it would be used, and the call would not be placed with Pursuit. The DIAL entry that matches the 976 number is less than nine characters long, so the Pursuit processing takes priority. There are a few locales that do not require a prefix when dialing long distance calls within your own area code. In that case you probably have a single DIAL line to strip the 1- and area code from all numbers in your area code. You will need to disable your own city in the PCP.DAT file. Change the baud rate in the NODE statement to zero to disable a city. Suppose you want to bypass Pursuit and use your Super- 56000 baud modem for a specific number? Use the following command: XPURSUIT 1:135/990 Pursuit processing will be bypassed for this node. You can use as many XPURSUIT commands as you wish. Pursuitable nodes will be marked by inserting a ">" character in front of the node's name. This symbol will be displayed by any program that uses the nodelist files to obtain a nodename. You may alter or suppress the flag with the following command: PCPMARKER string where string is 1-10 characters that will be used to mark PCP nodes. If string is omitted, no flagging will be done. XLAXNODE II Page 27 In addition, the human readable lists will have the PCP node name inserted in front of the node's city. The NODELIST.FON file will have the word "PCPURSUIT" added to the flags field. NOTE: The sample PCP script files included with XlaxNode are not represented as working scripts. They are intended to give you an idea of how scripts are constructed. I don't use PC Pursuit and I am unable to provide any support for writing or debugging PCP scripts. Please seek assistance from PCP Gurus on the PURSUIT BBS, the Pursuit Echo, or the support echo for your BBS/Mailer. ALSO NOTE: There's no way I can keep the file of PCP exchanges current, so I'm not going to try. The current list is available for download on the PURSUIT BBS. PCPLIST NOPCPLIST PCPLIST causes a file named PCP.PCP to be written. This file is a compressed version of the data contained in PCP.DAT file. The program PCP, supplied with XlaxNode, uses this file. NOPCPLIST is the default, and the file is suppressed. XLAXNODE II Page 28 PRIVATE, HOLD and DOWN NODES Down nodes are omitted from the output files. Independent nodes marked hold or private are also omitted, since FidoNet policy states that an RC is not expected to route mail for these nodes. Private and hold nodes within a network will receive the phone number, baud rate, flags and password for their host (or hub, if they have one). This means your mailer should be able to call their host and deliver the mail. See the HOSTMARKER command for an additional feature. If you place a password on a private node, mail can no longer be host routed. If your mailer called the host with the node's password, the host would reject the call. If you place a password on a private node, XlaxNode will warn you that the node's mail must be placed on hold for pickup. Conversely, if you have a password for a node's host, but not for the node itself, your nodelist will contain the host's password. If the node calls you, he will not have the correct password, and your mailer will reject the call. None of these restrictions apply to FrontDoor. All nodes, including Hold, Down and Private are written to the nodelist. FrontDoor handles these special cases itself. OPUS 1.1x COST FIELDS The Opus 1.1x nodelist, also used by Binkley, has provisions to maintain two cost fields for each node. One is the cost charged the user for each message sent. The other is used in the event scheduler to control when calls can be placed. This allows you more flexibility, since your charging and routing no longer have to use the same cost. You can allow users to send free messages to Pursuitable nodes, but specify a cost that prevents daytime calls. Every place that XlaxNode allows a cost to be entered, you may enter two values, separated by a colon. The first value is the traditional message cost. The second is the call cost for event scheduling purposes. If you omit the second cost, it defaults to the message cost. You may enter these values in the COST header line, COST detail lines, and the Pursuit COST field. Example: PURSUIT PCP 0:1 ; Free to users but no calls during day COST 0:25 150 ; Generous Sysop gives free domestic mail 1-305-596 1:0 ; Charge users a penny for local email XLAXNODE II Page 29 FRONTDOOR CONSIDERATIONS This version of XlaxNode produces files compatible with FrontDoor 2.0 Gamma 1.13 and later. It will not work with earlier versions. There are a number of things to keep in mind when using XlaxNode instead of FrontDoor's FDNC and Setup programs FD handles session passwords by having the Setup program modify the PASSWORD.SYS file. Recompiling the nodelist with FDNC has no effect on this file. XlaxNode recreates the PASSWORD.SYS file from the passwords in your control file; passwords entered with Setup will be lost. You may prefer to ignore the PASSWORD.SYS file created by XlaxNode and do all your password maintenance with Setup. FD expects you to combine all your secondary nodelists (ADDLIST, MYLIST, PVTLIST) into a file named FDNODE.PVT, which is used as input to the nodelist compiler. XlaxNode reads all your secondary lists and writes FDNODE.PVT for use by FD. If you are converting from FDNC to XlaxNode, make sure you rename an existing FDNODE.PVT file so that it is not overwritten. FD requires that DIAL and COST strings match a part of the number that ends with a hyphen. For example, if the phone number was 1-305-555-1212, any of the following would match: 1-305-555- 1-305- 1- The following will NOT match because they don't end in a hyphen: 1-305-555-1212 1-305-555 1-305-55 1-305 1 DELIMITED FILE The delimited file is a version of the nodelist formatted to easily import into dBase, Lotus, Reflex or (gag) a BASIC program. There is no zone selection for this file and MYLIST files are included. Each node is a single line, consisting of a list of fields separated by commas. Strings are enclosed in quotes. XLAXNODE II Page 30 A sample database definition for dBase-III, NODELIST.DBF, is included. The commands USE NODELIST and APPEND NODELIST.DLM DELIMITED will load this database. You may wish use the MODIFY STRUCTURE command to shorten some of the field lengths before loading. For Lotus, use the command "File Import Numbers". Allow a LONG time and a LOT of memory. If you rename the file to type "PRN", the Reflex2 Translate command will accept this file as type "TEXT". All you need to do is supply field names. XLAXNODE II Page 31 The fields, in order, are: Keyword: Will contain one of the following: "ZONE", "REGION", "HOST", "HUB", "PVT", "HOLD" or "". "" is a normal node. Down nodes are not included in the file. Zone: an integer. Region: an integer. Net: an integer. Node: an integer. Node Name: a quoted string. Sysop's Name: a quoted string. City: a quoted string. Node Phone: phone number as it appears in the nodelist, a quoted string. Private nodes will have "- Unpublished-" in this field. For Hold or Private nodes, the remaining fields refer to the host's (hub, net, region, zone) information. For normal nodes, they contain the node's own information. Dial Phone: phone number after dial translation, a quoted string. Baud: an integer. Pursuit City: if Pursuit processing enabled and node is dialable via Pursuit, the outdial city, in quotes. Otherwise "". CM: continuous mail indicator, the letter T or F, not quoted. Flags: a quoted string. This example has been wrapped to fit the format of the document. In the file, it occupies a single line. "ZONE",1,1,0,"Intl FidoNet Coord","David Dodell", "Scottsdale AZ","1-602-235-9653", "1-602-235-9653",1200,"AZPHO",T,"XP:,#CM:" XLAXNODE II Page 32 CAPACITY XlaxNode has no limit on the size of the nodelist that it can process. Its use of memory is quite dynamic, and it's hard to say how much memory is required. For a small control file with BUFFERS 1, it will run in 150K. Substantial control files (including full PC Pursuit processing) with the default BUFFERS value may take 250k. The options that invoke the sort (SEADOGLIST, FDLIST, INTERLIST, USERLIST and SINDEX), will add to the time and memory requirements. All sorts attempt to process the entire file in memory, but will overflow to disk if required. The XlaxNode.Cfg file used by older versions of the program is no longer needed. You may delete the file. BUGS, PROBLEMS, COMPLAINTS, SUGGESTIONS and COMPLIMENTS Reduce your netmail or postage bill by sending all unpleasant communications, particularly about Crippleware, to NUL. If you have a problem with the software, do ALL of the following: If running any kind of network, multitasker, or TSR, try the problem in a stand alone environment. The prime rule is "If I can't reproduce the problem I can't fix it." If you are running any kind of odd hardware or old operating system (MS-DOS version 2.1), try to get a friend to run it on a more common configuration. If you are having trouble with Pursuit scripts, you are on your own. I don't use Pursuit, and have no way to debug a script. The scripts provided are examples and I don't pretend they will run on your system. Indicate the version number of XlaxNode you are running. Include the type of machine (IBM PS/50, Homemade AT clone), the name (MS-DOS, PC-DOS) and version number of your operating system. Indicate the total memory size and the amount of available memory displayed by ChkDsk or Mapmem. I may have to restrict my memory to recreate the problem. XLAXNODE II Page 33 Redirect the program's output to a file: XlaxNode > Error.Rpt Create an archive that contains a copy of your control file (don't forget included files), any private nodelists, plus any other information you think may be germane to the error. Do not remove PASSWORD or PHONE statements. You may wish to overstrike confidential information with X's. Indicate any options you are using on the XlaxNode command line. If none, say so. Make YOUR node number part of the archive name so I don't have to figure out where XlaxNode.Ctl came from. Send a netmail message with the appropriate supporting files to Scott Samet at 1:135/990. Until appropriate gateways are established, I am able to respond to non- FidoNet addresses. The license fee does NOT include telephone support. Please do not telephone without first making an appointment via netmail. XLAXNODE II Page 34 INDEX Acknowledgements ......................................... 1 ADDLIST <filename>... .................................... 9 ADDR .................................................... 16 ADDRLIST filename ....................................... 17 ALLZONES ................................................ 10 BAUD [<zone>:[<net>/]]<node> <speed> .................... 18 BINKLIST ................................................ 13 BUFFERS <number> ........................................ 11 BUGS, PROBLEMS, COMPLAINTS, SUGGESTIONS and COMPLIMENTS . 32 COMMENTS ................................................ 12 COMPLETE ................................................ 10 COORDLIST ............................................... 16 COST <dom-cost> <int-cost> [<spec-cost>] ................ 22 COUNTRY .................................................. 7 CRCCHECK ................................................ 12 DASH .................................................... 13 DELIMITEDFILE [PURSUIT | NOPURSUIT] .................. 16 DIAL <domestic> <international> ......................... 19 FDLIST [ LONGUSER | SHORTUSER ] ..................... 14 FIDODBL ................................................. 15 FIDOPRN ................................................. 15 FIDOTXT ................................................. 15 FLAG [<zone>:[<net>/]]<node> <+/=><flagstring> .......... 18 GATE [<zone>:[<net>/]]<node> ........................... 17 GATED ................................................... 10 HOSTMARKER <string> ..................................... 12 HUB [<zone>:[<net>/]]<node> ........................... 17 IGATE [<zone>:[<net>/]]node ............................. 17 INDEX ................................................... 15 INTERLIST [ OPUS | SEADOG ] ............................ 14 License .................................................. 2 MAXBAUD nnnn [<flagvalue> <baudrate>]... ................. 7 MODEMSTRING <flagvalue> <prefixstring> <suffixstring> .... 7 MYLIST <filename>... .................................... 9 NET <zone>:<net> [ <newnumber> | - ] ................. 10 NEWOPUSLIST [ NOPURSUIT | OLDPURSUIT | NEWPURSUIT ] ..... 13 NOBINKLIST .............................................. 13 NOCOMMENTS .............................................. 12 NOCOORDLIST ............................................. 16 NOCRCCHECK .............................................. 12 NODASH .................................................. 13 NODE <zone>:<net>/<node> ................................. 6 NODELIMITEDFILE ......................................... 16 NODELIST [ FIDO | OPUS | SEADOG ] ...................... 15 NODETEXT [ <headerfilename> [ <trailerfilename> ] ] ..... 16 NOFDLIST ................................................ 14 NOFIDOLIST .............................................. 15 NOINDEX ................................................. 15 NONEWOPUSLIST ........................................... 13 NONODELIST .............................................. 15 NONODETEXT .............................................. 16 NOOLDOPUSLIST ........................................... 13 NOPROGRESS .............................................. 12 XLAXNODE II Page 35 NOQUICKBBSLIST .......................................... 14 NOREPORT ................................................ 12 NOROUTE ................................................. 15 NOSEADOGLIST ............................................ 14 NOSQUEEZE ............................................... 16 NOTBBSLIST .............................................. 14 NOTPBLIST ............................................... 14 NOUSERLIST .............................................. 14 OGATE [<zone>:[<net>/]]<node> ........................... 17 OLDOPUSLIST [ NOPURSUIT | OLDPURSUIT | NEWPURSUIT ] ..... 13 ONEZONE ................................................. 10 OPERATION ................................................ 5 OZONE <zone>:<net> [ <newnumber> | - ] ................. 10 PASSWORD [<zone>:[<net>/]]<node> password ............... 18 PASSWORDFILE filename ................................... 18 PCPLIST ................................................. 27 PHONE [<zone>:[<net>/]]<node> <phonenumber> ............. 17 PROGRESS ................................................ 12 PUBLIST [path\]nodelistname ............................. 8 PURSUIT <filename> <cost> <baud> <cxl-string>... ........ 23 PVTLIST <filename>... .................................... 9 QUICKBBSLIST [ NOPURSUIT | OLDPURSUIT | NEWPURSUIT ] ... 14 REPORT .................................................. 12 ROUTE [ NOPURSUIT | OLDPURSUIT | NEWPURSUIT ] .......... 15 SEADOGLIST .............................................. 14 SINDEX .................................................. 15 SORTWORK [path\]filename ................................ 11 SQUEEZE ................................................. 16 TBBSLIST ................................................ 14 TPBLIST ................................................. 14 UPDATE command-string .................................... 7 USERLIST [ OPUS | SEADOG ] ............................ 14 VERSION5 [ NOPURSUIT | OLDPURSUIT | NEWPURSUIT ] ..... 13 VERSION6 [ NOPURSUIT | OLDPURSUIT | NEWPURSUIT ] ..... 13 Warranty ................................................. 3 ZONE <n> [<n>...] ....................................... 10 END