Differences

This shows you the differences between two versions of the page.

--- commands:sysop [2019-04-17 18:21] – created stimpy
+++ commands:sysop [2026-08-25 03:37] (current) – removed - external edit (Unknown date) 127.0.0.1
@@ Line 1: / Line 1: @@
-====== SysOp Commands ======
-There are several commands available from the main menu which are designed to help you, the SysOp, to do many common maintenance functions.  Using these commands you can do these following tasks and more:
-  * View, print, search, and delete the callers logs
-  * Pack the current message base
-  * Change a user record
-  * Drop to DOS from remote
-The security level for these functions should be set high enough so that only authorized people will have access to the commands. To assign the security levels for these commands, use PCBSetup and select Security Levels > Sysop Functions.
-===== 1  Manage Caller Log =====
-This (Sysop) command enables you to manage the caller log that PCBoard creates for the current node .  You can view, print, search, and delete the caller log.
-==== Subcommands ====
-|**D**|Delete caller log.|This subcommand will delete the caller log for the current node.  You may want to use this subcommand to periodically delete the caller log to prevent it from taking up too much disk space. **WARNING:** Once deleted, PCBoard cannot recover that caller log.|
-|**P**|Print caller log.|If you use this subcommand, the caller log for the current node will be displayed on the screen and also sent to the printer port that is defined in PCBSetup.|
-|**S**|Search caller log for text.|The more callers your system has the more difficult it will be to find the information you are looking for in the caller log.  PCBoard provides search capabilities to allow you to search the log file for any text. You can do both a simple one word or one phrase search or you can do complex Boolean searches using the AND, OR, and NOT operators.  For more information on Boolean searching please see Searching For Text in the Sysop's Guide chapter of this manual.|
-| ||If PCBoard finds a match when searching the caller log, the log entry for the entire call will then be displayed.  The search text that was found will be highlighted for clarity.|
-| ||When PCBoard searches through the callers logs it does not try to match case.  If you tell PCBoard to search for Jim Smith then any caller log that contains the text JIM SMITH would be a match.|
-|**V**|View caller log.|Using this subcommand you can view the caller log.  The display starts with the most current caller.|
-==== Description ====
-The callers log provides you with information about who has called your system, what node they called in on, highlights of what they did online, what date and time they called, etc.  When you view the caller log, PCBoard will display the file to you in reverse order beginning with the last caller to the system.
-You will also want to periodically search the caller log because that is where any system error messages may be displayed.  In addition, when a user attempts to access a command that is not available to them,  that information is almost always written to the caller log.
-The caller log is simply a condensed history of what has taken place on the BBS.  The 1  command enables you to not only view the information stored in the caller log but also to print and/or delete the caller log.
-==== Examples ====
-To view the current node's caller log on your display, type the following at the command prompt:
-V
-You may want to regularly search your caller log for possible system errors.  When executed from the command prompt, the following command will search for any caller log entry that contains the word FAIL or the word ERROR.
-S FAIL > ERROR
-===== 2   View/Print User List =====
-Enables you to either view or print a list of users.  Each user is listed on a separate line.
-==== Subcommands ====
-|**P**|Print user listing.|When you use this subcommand, a list of users will be printed to the printer you have defined in PCBSetup.|
-|**V**|View list of users.|This subcommand will enable you to display a list of your users on the screen.|
-==== Description ====
-The list that this command produces lists each user, their city, last call date, last call time, and total minutes used so far. All of this data is listed on one line.  The users are listed in the order that they appear in the user file.
-The only time the SysOp information (user record #1) is displayed is if the user defined in that record is issuing the command.  This means that if you use co-SysOps to help you maintain the system they will not be able to view any information about the main SysOp user record.
-===== 3   Pack/Renumber Messages =====
-This command enables you to pack the message base for the current conference.  When you pack the message base you can eliminate messages in the current conference that are old, that are private and have been read, or those that have been marked for deletion.  After executing this command, several questions will be asked to help determine the messages that should be packed.  The following details each of the questions that will be asked.
-=== Pack the Message Base? ===
-This question is asked to confirm that you want to pack the message base.  Valid responses are:
-|**N**|Do not pack the message base. Instead, return to the conference command prompt.|
-|**Y**|Continue packing the message base. Additional questions will be asked that will determine what criteria you want to use for deleting messages (if any).|
-=== Generate ONLY a New Index File? ===
-This question is asking if you want to only regenerate a new index file for the message base.  Valid responses for this question are:
-|**N**|If you enter this response, additional questions will be asked to determine the criteria for deleting messages.|
-|**Y**|If you enter this response, no other questions will be asked. Instead, PCBPack will be run immediately and create a new index for the conference.  Creating a new index file is useful if you suspect that the current index may be corrupt for some reason.|
-**TIP:**  To accomplish this same task  by executing PCBPACK yourself,
-use the /INDEX command line parameter.
-=== Purge older than ===
-This question asks you to enter the cutoff date for keeping messages.  Any messages that are older than the date that you enter will be deleted from the message base.  In the field provided, enter the cutoff date for keeping messages.  The default date in this field is 010180 which will not delete messages by date.
-**TIP:** To accomplish this same task  by executing PCBPACK yourself,  use the /DATE command line parameter.
-=== Purge RECEIVED+PRIVATE Msgs? ===
-Messages that have been assigned RECEIVER ONLY message security are only useful to the receiver.  Once the message has been read by this user, you may want to delete it from your message base. The question that you are asked will determine if these messages will be deleted or left in your message base to be packed out by other criteria.  Valid responses are:
-|**N**|Leave any RECEIVER ONLY messages in the message base.  To be deleted, they will have to meet other packing criteria.|
-|**Y**|All RECEIVER ONLY messages that have been read will be deleted from the message base.|
-**TIP:** To accomplish this same task  by executing PCBPACK yourself, use the /PURGE command line parameter.
-=== Renumber during repack? ===
-This option is designed to allow you to renumber the message base if you exceed the 16,000,000 maximum message number limit. When renumbering your message base, PCBPack does NOT update the last message read values for your users.  Therefore, if you renumber the message base without adjusting these values, your users may not be able to see new messages because their last message read value remains unchanged.  Using System Manager, you can reset your user's last message read pointer to 0 to avoid this problem.  Valid responses to this question are:
-|**N**|Do not renumber the message base -- message numbers will remain unchanged.|
-|**Y**|The message base will be renumbered beginning with the number that you specify when prompted.  When the message base is renumbered, the last message read values will not be updated.|
-**TIP:** To accomplish this same task  by executing PCBPACK yourself,  use the /RENUMBER command line parameter.
-==== The Packing Process ====
-Once you have answered all of the questions, PCBoard will load and run PCBPack.  When PCBPack is finished, control will be returned to BOARD.BAT.  If you do not load PCBoard using BOARD.BAT, you will be left at the DOS prompt.
-===== 4   Recover a Killed Message =====
-This command enables you to recover a message that has been deleted or killed.  A message that has been deleted cannot be recovered if the message base has been packed since the message was deleted.
-==== Subcommands ====
-|**[msg #]**|Message number to recover.|The only subcommand that is supported is the message number.  You need to type the message number that you wish to recover.  If you type in the number of a message that does not exist  you will be notified that the message does not exist.|
-==== Description ====
-When a message is deleted from the message base via the Kill command it is only marked for deletion.  You can recover any message that is marked for deletion and make it active again by using the 4 command.  Of course, if the message has been physically deleted by packing the message base the message cannot be recovered.
-===== 5   List Message Headers =====
-This command will list message header information.  The information pertaining to a message is listed on one line for easy viewing.
-==== Subcommands ====
-|**[beg. msg.  #]**|Beginning message number.|This is the message number that you wish to begin the scan with.  The default scan direction is in the forward direction.  If you wish to go in the reverse direction please see the - subcommand.|
-|**+**|Scan in forward direction.|When appended to the beginning message number you can set the direction in which PCBoard scans the message base.  For example if you enter 762+ PCBoard will begin scanning at message number 762 in the forward direction.|
-|**-**|Scan in reverse direction.|When appended to the beginning message number you can set the direction in which PCBoard scans the message base.  For example if you enter 3569- PCBoard will begin scanning at message number 3569 in the reverse direction. **NOTE:** PCBoard defaults to searching in the forward direction.|
-|**A**|Scan selected conferences.|Scans not only the current conference but also those conference which you have set for scanning via the SELECT command or the S conference flag in the users record.|
-|**ALL**|Scan all conferences.|Scans all conferences you are registered in even if you have not marked the conference for scanning.|
-|**F**|Message from you.|Only messages that are from you, the user currently online, will be displayed.|
-|**L**|Begin with last message in message base.|Sets the beginning message number to the last message in the message base.  When you use this subcommand you may omit the beginning message number.|
-|**NS**|Display in non-stop mode.|The listing of messages will be displayed in non-stop mode.  This means that there will be no more? prompts each time the screen becomes full.|
-|**S**|Messages that you have not read yet.|Searches only those messages that you have not read yet.|
-|**TS**|Messages that contain particular text.|This subcommand enables you to search for text in the message body, the TO: field, and the FROM: field.  You can search for a word/phrase or you can use any Boolean search.  For more information on searching for text please see Searching For Text in the SysOp's Guide chapter of this manual.|
-|**USER**|Messages from a particular user.|You may search the message header for a particular user.  When PCBoard searches for a particular user it will search both the TO: and the FROM: fields in the message header.  You must enter a full user name. Partial matches cannot be made with this command.|
-|**Y**|Messages addressed to you.|Only messages that are addressed to the user that is currently online will be listed.|
-==== Description ====
-The 5 command can be used to quickly search message headers for information.  This command will produce a list on the screen that shows such information as who the message is to and from as well as the subject of the message.
-The only difference between the 5 command and the Q command is that the former will display active messages and also those messages which have been marked for deletion.
-==== Format of the list ====
-The list that is produced by the format contains the following information:
-Sts.  Displays the status of the message.  An A indicates that the message is active while an I indicates that the message is inactive (marked for deletion).
-|**Msg#**|The actual message number in the message base.  Just before the message number is a status code that shows if the message has been read, etc.  For a list of status codes please see the section titled Status Codes.|
-|**Ref#**|If the message is a reply, then this field will contain the message number which was replied to.|
-|**To**|Displays who the message is addressed to.  Only the first 15 characters of the user name are displayed.|
-|**From**|Displays who the message is from.  Only the first 15 characters of the user name are displayed.|
-|**Subject**|Displays the subject of the message.  Only the first 25 characters of the subject are displayed.|
-==== Status Codes ====
-Next to each message number is a status code.  You can use these status codes to determine if the message has been read, if it has replies, etc.  The following is a list of all valid message status codes:
-|**[blank]**|A message which can be read by anyone.|
-|*****|A private message to a specific person which has not been read by the person it was addressed to.|
-|**+**|A private message which has been read by the person it was addressed to.|
-|**-**|A message to a specific person, which was readable by anyone, which has been read by the person it was addressed to.|
-|**~**|A comment to the SysOp which has not been read by the person defined as SysOp record #1.|
-|**`**|A comment to the SysOp which has been read by the person defined as SysOp record #1.|
-|**%**|A message protected by sender password which has not been read.|
-|**^**|A message protected by sender password which has been read.|
-|**!**|A message protected by group password which has not been read.|
-|**#**|A message protected by group password which has been read.|
-|**$**|A message protected by group password which is addressed to ALL.|
-==== Examples ====
-To display the header information for all messages in the current message base in reverse order you would issue the following at the command prompt:
-L
-To search for all messages (beginning with the first message in the message base) either to or from a user named Wally Peterson you would issue the following at the command prompt:
-USER WALLY PETERSON 1+
-===== 6   View a File =====
-Enables any file to be displayed.  Even if you are calling in from remote you can view any file.
-==== Subcommands ====
-|**[filename]**|The filename you wish to view online.  This file may be any valid DOS filename.|
-==== Description ====
-Sometimes you may want to view a file while you are online. This command will display any file in it's raw form making it primarily useful for viewing ASCII files.  With this command, you could view batch files, display screens, or any other text file.
-This command is most useful when used from remote because you can quickly view a file on screen without having to do a remote drop to DOS.
-=== Example ===
-If you want to display C:\PCB\BOARD.BAT, type following at the command prompt.
-   C:\PCB\BOARD.BAT
-===== 7   User Maintenance =====
-Enables you to modify any user record.  You can adjust security levels, conference registrations, and more.
-==== Subcommands ====
-|**[record #]**|User record number.|Displays the user record number you type.  If you wish to view record number 10 you would type 10.|
-|**A**|Add a user.|Using this subcommand you may add a user to your users file.  You will be asked to provide the basic information to create the record such as a password, security level, etc. If you attempt to create a record for a user that already exists you will be informed that they already have a record on the system.  If this happens you may want to use the F subcommand to help you locate that record so you can make the appropriate changes.|
-|**C**|Change current user record.|When you use this subcommand you can make changes to the key fields of the user record (e.g., security level, expiration date, city).  The user record that is currently selected is the one that will be edited.|
-|**D**|Delete current user record.|Marks the current user record for deletion.  You will first be asked to confirm the deletion. If you proceed to delete the record then the security level will be changed to 0 and the deleted flag will be set to Y.  You can tell if a user record is marked for deletion by looking for a DL: on the display.  If there is a Y next to it then the user has been marked for deletion.  Otherwise there should be a N and the user has not been marked for deletion. **NOTE:** The user will not be physically be removed from the user file until you pack the users file.|
-|**F**|Find a user.|When you select this subcommand you are asked for the name to search for.  The user file will be searched for the name you supply - partial names will not match.  If the name is found then their user file will be displayed and you can use any other subcommand like C or D to modify the record.|
-|**L**|List all user records.|Displays the user records beginning with the first user record all of the way to the end.  The format for the output is the same as if you were to select one individual record. **NOTE:** Any user records that have a security level higher than the current user will not be displayed in the list.|
-|**P**|Print all user records.|Displays the same information as the L subcommand but sends it to the defined printer instead.|
-|**Q**|Quit.|Quits the user record editor and returns you to the command prompt.|
-|**S**|Search user records for text.|This subcommand enables you to search the user records for specific text.  PCBoard will search all ASCII text inside of the user file.  This means fields such as user id, address, phone numbers, password, city, and the two comment fields will be searched.|
-|**U**|Undelete a user record.|If there is a user record that has been marked for deletion you can use this subcommand to undelete the user.  If you do, you will need to manually change the user security level and expired security level because they were originally changed when the user record was deleted.  You can use System Manager to make the appropriate changes.|
-**NOTE:** Any changes made to a user record (e.g., changes in security level, city) while the user is on line will not take affect until the next time the user calls in.  For immediate changes to a user record, please refer to the SysOp function keys in the PCBoard chapter of this manual.
-==== Description ====
-PCBoard gives you easy access to the user records while you are online either locally or remote.  You can do such things as adding users, deleting users, editing user records, etc.  For security purposes, PCBoard will not allow you to see information about those users who have a security level higher than your own.  This enables you to have co-SysOps without enabling them to see the passwords and other sensitive information about users with higher security levels.
-==== Format of Record Display ====
-When a user record is displayed on the screen, it is shown in the following format:
-|**1:**     |BOB SYSOP    ||ANYCITY, ANYPLACE        ||||**P/W:** |*ANYPASSWORD                                  ||||||||
-|**D:**     |999-999-9999 ||**V:**  |999-999-9999     ||| **LD:** |06-24-93  ||**LT:**|10:15  |**EX:**|Y      |**PR:**|G|
-|**Sec:**   |250|**E/Sec:**|250     |**TO:**|13|**PL:** | 23      |**UP:** |32|**DN:**|57     |**ET:**|0      |**DL:**|N|
-|**E/Date:**|00-00-00     ||**D/D:**|90543    ||**T/D:**| 3463463 |**T/U:**|346246                                |||||||
-|**C1:**    |                             ||||||**C2:** |                                                        ||||||||
-|**ALIAS:** |WARLOCK WILLY                                                                                |||||||||||||||
-|**ST#1:**  |100 Elm Street                                                                               |||||||||||||||
-|**ST#2:**  |Apartment #32                                                                                |||||||||||||||
-|**CSZC:**  |Jackson, TN  38325  UNITED STATES                                                            |||||||||||||||
-|**NOTE:**  |.....................                 ||||||**Comment Field #1**|||....................               ||||||
-|**NOTE:**  |.....................                 ||||||**Comment Field #2**|||....................               ||||||
-|**NOTE:**  |.....................                 ||||||**Comment Field #3**|||....................               ||||||
-|**NOTE:**  |.....................                 ||||||**Comment Field #4**|||....................               ||||||
-|**NOTE:**  |.....................                 ||||||**Comment Field #5**|||....................               ||||||
-|**VERIFY:**|1001 WAYS TO USE CLIPS                                                                       |||||||||||||||
-The first line of each record displays the user's record number, name, city, and password.  The following discusses the rest of the items you will find in each record:
-|**D:**|Data phone number|
-|**V:**|Voice phone number|
-|**LD:**|Last date the user called the system|
-|**LT:**|Last time the user called the system|
-|**EX:**|Expert user status|
-|**PR:**|Default protocol letter|
-|**Sec:**|Security level|
-|**E/Sec:**|Expired security level|
-|**TO:**|Number of times the user has called the system|
-|**PL:**|Page length setting|
-|**UP:**|Number of files uploaded|
-|**DN:**|Number of files downloaded|
-|**ET:**|Number of minutes spent on the last day the user called the system|
-|**DL:**|Whether or not the user is marked for deletion.|
-|**E/Date:**|Expiration date of the user.|
-|**D/D:**|Total number of bytes downloaded today.|
-|**T/D:**|Total number of bytes downloaded from the system.|
-|**T/U:**|Total number of bytes uploaded to the system.|
-|**C1:**|Comment1 field.|
-|**C2:**|Comment2 field.|
-The rest of the fields shown on this display will only be shown if you have installed the appropriate PSA.  For example, the ALIAS line will only be displayed, if you have installed the Alias PSA (System Manager > Users Info File Maintenance > Install PCBoard Supported Allocation).
-|**ALIAS:**|The name the user has selected as their alias|
-|**ST#1:**|First address line|
-|**ST#2:**|Second address line|
-|**CSZC:**|City, state, zip, and country fields.|
-|**NOTE:**|The five lines provided by the notes PSA|
-|**VERIFY:**|The information the user has entered for verification purposes.|
-==== Locating a User to Edit ====
-You can use the S and F subcommands to help you locate the user you wish to edit.  If you use the F subcommand, you must know the full user name to search for.  Unless a perfect match is found then no record will be displayed.  Alternatively you may use the S subcommand if you wish to search for text or you do not know the full name.  Any dates you wish to search for must be in YYMMDD format because that is the way they are stored in the user file.
-==== Examples ====
-If you wish to search for AMY SEXTON's user record you would type the following at the command prompt:
-F AMY SEXTON
-If you wish to locate all users who potentially call from Cassidy, WY then you would type the following at the command prompt:
-S CASSIDY, WY
-===== 8   Pack User File =====
-The user defined as record #1 in the user file can use this command to pack the user file while other users are online.  When you pack the user file, you can eliminate users who have not called for a while or that have been marked to be deleted.  After executing this command, several questions will be asked to help determine the users that should be packed.  The following details each of the questions that will be asked.
-==== Pack the user file? ====
-This question is asked to confirm that you want to pack the user file.  Valid responses are:
-|**N**|Do not pack the user file.  Instead, return to the conference command prompt.|
-|**Y**|Continue packing the user file.  Additional questions will be asked that will determine what criteria you want to use for deleting users (if any).|
-==== Keep 'Locked Out' users? ====
-Locked out users are those that have a security level of 0 but have not been marked for deletion.  Your response to this question will determine whether these users will be deleted.  Valid responses are:
-|**N**|Locked out users will be deleted from the user file.  Since the locked out records will be removed,  the users will no longer be prevented from logging in under the name that was previous locked out.|
-|**Y**|Locked out users records will remain in the user file.  This will prevent these users from logging into the system again.|
-==== Purge older than ====
-Your response to this question will determine the cutoff date for deleting inactive users from the user file.  The default date is 010180 implying that no users will be removed for inactivity.  For example, if you want to delete all users who have not called since April 1st, 1994, you would enter 040194 in this field.
-==== Keep whose security => ====
-Quite often it is desirable to exempt users of a certain security level or higher from being packed out of the user file. The default security level is 100 which prevents anyone of this security level or higher from being deleted when the user file is packed.
-===== 9   Remote Drop to DOS =====
-Enables you to drop to DOS from remote.  Once in DOS you can run standard DOS commands or other DOS applications.
-==== Subcommands ====
-|**Y**|Yes.  Normally when you select the 9 command and then press ENTER you will be asked to confirm the drop to DOS.  If you wish to bypass this confirmation you may use the Y subcommand.|
-==== Description ====
-Inevitably there will be a time when you are calling into your system from remote and realize that you need to drop to DOS and do a little maintenance.  When you incur a situation like this, you realize just how handy the 9 command is to have around. With this command you can drop to DOS and run other programs. PCBoard allows maximum flexibility by running a batch file called REMOTE.SYS to drop you to DOS.
-==== Setting Up REMOTE.SYS ====
-For the most reliable remote DOS access, you need to use a third-party program.  This program should be able to redirect your screen displays.  At the very least, it should be able to handle all text mode applications.
-DOORWAY is a program written by Tri-Mark Engineering that will handle just about any 80x25 text mode program.  It will redirect the text mode screen to the remote user using the popular ANSI escape codes.  A sample REMOTE.SYS using DOORWAY might look like this:
-	set box=no
-	doorway com1 /s:.\ /v:d^O /o: /k:v0 /c:dos
-	set box=
-	c:
-	cd \pcb
-	board
-Two things should be noted about the above example.  If you are using a serial port other than COM1 then you will have to make the appropriate change to reference the port you are using.  In addition, the last two lines of this example return you back to your PCBoard subdirectory and then execute BOARD.BAT to reload PCBoard.  It is essential that you return back to your PCBoard subdirectory before you execute BOARD.BAT.  Verify that you change to the appropriate drive and subdirectory.
-==== Using Function And Alt Keys ====
-When you drop to DOS, you may load one of your maintenance programs such as PCBFiler or PCBSetup.  Most likely your communications program will intercept all of the cursor movement and function keys.  Check your communications program to see if it supports what most call DOORWAY mode.  This mode in communications programs will allow them to pass the cursor key movements and function keys to the remote system.
-===== 10   Execute DOS Command =====
-This command enables you to execute DOS commands directly from the PCBoard command prompt.
-==== Description ====
-When this command is executed you are asked for the command you would like to execute.  Once you type in the command, PCBoard will shell to DOS and execute the command you issue.
-==== How much memory is available when shelled out? ====
-The amount of memory that will be available depends on your answer to Swap Out During Shell in PCBSetup > Configuration Options > Switches.  A Y means that you will have slightly less memory available to you than you had when you loaded BOARD.BAT. An answer of N means that you will have slightly less then the free memory shown on the status line.
-Please keep in mind your memory restrictions because if you run an application and there is not enough memory available, you will return back to PCBoard without the command executing.
-==== What programs can be run? ====
-When you are on locally, you can run any application assuming you do not run into any memory restrictions.  When you are executing this command from remote, however, there are some items you must take into consideration.
-If the command you execute from remote requires any interaction or input from the keyboard, you will not be able to execute these programs using the 10 command.  The reason you cannot use these programs is that you are logged in remotely and have no control over the BBS's keyboard.  If you attempt to run one of these programs, that node on your system will appear to hang.
-What really happened is PCBoard executed the program and then ran into a situation that required keyboard input.  PCBoard waits until the program is finished before returning which means the node will be stuck until it can be fixed.  If you need to run an application that requires user interaction or input from the keyboard you should use the 9 command instead.
-===== 11   View Users Currently Online =====
-Enables you to view a list of all of the active nodes, who is online, and what they are currently doing on the BBS.
-==== Description ====
-On multinode systems this command displays the name and location of users that are currently online on all of the nodes in the system.  This display also shows what the user is currently doing on the system.
-==== Status Messages ====
-The display of all active nodes has a Status column.  This column displays a brief description of what the user is currently doing online.  A list of status messages follows:
-  * Auto Logoff Pending
-  * Available for CHAT
-  * CHAT Request Sent
-  * CHATTING with Group
-  * DOS Recycle Pending
-  * Dropt to DOS Pending
-  * Drop to DOS - Urgent
-  * Logging into System
-  * No Caller this Node
-  * Out of Code in DOOR
-  * Paging the Sysop
-  * Run/Answer Script
-  * Running Event
-  * Transferring a File
-  * Unavailable for CHAT
-As you can see, you can obtain a significant amount of detail about what each user is doing online from executing the 11 command.
-==== Additional Information ====
-Since the 11 command is a SysOp command, you will also have additional information available to you.  The following shows the status messages that will show additional information when you use this command:
-==== Transferring a File ====
-When a user is transferring a file, PCBoard will display as much information as it can.  Internal protocols, by their very nature, update after each file.  If PCBoard knows enough about the file transfer, it will display if a transfer is an (U)pload or a (D)ownload, the filename that is being transferred, the protocol letter used, the size of the file being transferred, and finally the estimated time of transfer.  The line underneath the user's name may resemble the following:
-	(D) PCBMULT.ZIP (G) 44,573  -  0.6
-This tells you that the user is downloading a file called PCBMULT.ZIP using protocol letter G and that the file is 44,573 bytes which will take approximately .6 minutes or about 36 seconds to transfer.
-	(U) TESTSLC.ZIP (G) 141,042  -  1.6
-This entry shows that the user is uploading a file called TESTSLC.ZIP using protocol letter G.  The size of the file is 141,042 bytes and will take about 1.6 minutes or 1 minute 36 seconds to upload.
-	(U) ... (Z) ...
-This simply shows that the user is uploading using the protocol defined by the letter Z, but the filename and transfer information could not be determined because the protocol is external.
-PCBoard updates this information at various times.  The following details when internal and external protocols update the information for this display:
-=== Internal Protocols ===
-Internal protocols, by their very nature, know how to update PCBoard.  As each file is transferred, the display will be updated to show the current status.  The only exception is if a user is using an internal non-batch protocol to upload a file. In this case, you will only see that the user is uploading a file and what protocol they are using.
-=== External protocols ===
-External protocols do not update nearly as often simply because they do not know what to update since most are not PCBoard specific.  PCBoard does its best on downloads by showing the last file that will be transferred.  On uploads, you will simply see that someone is uploading a file and what protocol they are using.  You will not know what file they are uploading.
-**NOTE:** If a user is viewing the contents of a file, PCBoard will show the name of the file they are viewing below their user name.  The format that the filename is displayed in is the following:
-	F V FILENAME.EXT
-==== Entering a Message ====
-When a user is entering a message, you will be shown what conference they are in, followed by who the message is being addressed to.  For example, if the user was in conference 9 and entering a message to JOHN SMITH then you would see the following under the user's name:
-	(9) => JOHN SMITH
-==== Run/Answer Script ====
-If a user is completing a script, you will see the conference and the script number they are completing listed underneath their name.  For example, if a user was in conference #1 and filling out script #2, you would see the following under the user's name:
-	(1) => #2
-If you have a script questionnaire which is a PPE file, the filename of the PPE will be displayed.  For example:
-	C:\PCB\GEN\SCRIPT2.PPE
-==== Running Event ====
-When an event is running on a node, PCBoard will update the display of the nodes to show the event number and event name that is currently running.  The format for the display is:
-	#1 -> DAILY
-This example shows the display if event #1 is executing and the event BATCH file is called DAILY.
-=== Example ===
-If you execute the 11 command you might see a display which looked like this:
-^ (#)  ^ Status                 ^ User                                   ^
-|**1** | Transferring a File    | STEWART OGDEN (HIGHLAND, KS)           |
-|      |                        | (D) PCBMULT.ZIP (G) 44,573  -  0.6     |
-|**2** | Run/Answer Script      | FRED KORKLEWSKI (ALBURY HEIGHTS, NV)   |
-|      |                        | (1) => #2                              |
-|**3** | Entering a Message     | BILLY CRUMP (GREENMEADOW, NV)          |
-|      |                        | (9) => JOHN SMITH                      |
-|**4** | No Caller this Node                                            ||
-|**5** | No Caller this Node                                            ||
-|**6** | No Caller this Node                                            ||
-|**7** | Transferring a File    | WINIFRED NEIDERHAUSER (SAN SIMEON, NE) |
-|      |                        | (U) ... (Z) ...                        |
-|**10**| No Caller this Node                                            ||
-|**11**| No Caller this Node                                            ||
-|**12**| Logoff Alternate Node                                          ||
-Enables you to immediately logoff a user that is currently online.
-==== Subcommands ====
-|**[node #]**|Node number.  The node number you wish to logoff.  The user is displayed a message which informs them that an automatic logoff has been initiated.|
-==== Description ====
-Sometimes you may need or want to logoff a user that is currently on another node.  PCBoard provides a SysOp command that enables you to do this.  When you issue this command you must supply the node number that you wish to log off.  Once you type in a valid node number the user will be logged off of the system
-NOTE:  If the user is currently in a third party application, such as a door, they will not be logged out of the system until they return back to PCBoard.  Likewise, the user will be allowed to finished any file transfers before they are logged off of the system.
-===== 13   View Node Caller Log =====
-Enables you to view other node's caller logs from any other node.  You may search or view any or all node's caller logs.
-==== Subcommands ====
-|**[node #]**|Node number.|The node number you wish to view or A to view all nodes.  If you enter a node number that does not have a caller log then an error message will be written to the caller log notifying you that the caller log for the node specified does not exist.  In addition, entering a number which exceeds the number of nodes in your software license will re-display a list of who is currently online so that you can pick a valid node.|
-|**A**|All caller logs.|Specifies that all node log files should be used not just an individual node.  This subcommand is most useful when used in a search using the S subcommand.|
-|**S**|Search for text.|The more callers your system has the more difficult it will be to find the information you are looking for in the various caller logs.  PCBoard provides capabilities for you to search the log file for any text.  You can do a simple one word, one phrase, or a complex Boolean search using the AND, OR and NOT operators.  For more information on Boolean searching please see Searching For Text in the Sysop's Guide chapter of this manual. |
-If PCBoard finds a match when searching the caller log, the log entry for the entire call will then be displayed.  The search text that was found will be highlighted for clarity.
-When PCBoard searches through the caller logs it does not try to match case.  If you tell PCBoard to search for Jim Smith then any caller log that contains the text JIM SMITH would be a match.
-==== Description ====
-The caller logs provide you with information about who has called your system, what node they called in on, highlights of what they did online, what date and time they called, etc.  When you view the caller log PCBoard will display the file to you in reverse order beginning with the last caller to the system.
-You will want to periodically search the caller log because that is where any system error messages are recorded.  In addition, when a user attempts to access a command that is not available to them,  that information is written to the caller log.
-==== Examples ====
-To view node 5's caller log you would type the following at the command prompt:
-5
-You may want to regularly search all of your caller logs for possible system errors.  When executed from the command prompt, the following command will search for any caller log entry on any node that contains the word FAIL or the word ERROR.
-A S FAIL > ERROR
-===== 14   Drop Node to DOS =====
-Enables you to drop another node to the DOS prompt from any other node.
-==== Subcommands ====
-|**[Node #]**|Node number.|The node number you wish to drop to DOS.|
-==== Description ====
-This command will drop any active node to a DOS prompt.  You are asked if you wish to have the node drop to DOS after the caller logs off, or if you wish to immediately drop that node to DOS.
-In order to drop to DOS immediately, PCBoard must be in control. If the user is shelled out to an external protocol or running a door, the node will not be dropped to DOS until PCBoard regains control.
-===== 15   Recycle Node =====
-This command will mark the node number that you specify to be recycled.  When recycling the node, you can execute a batch file to perform any necessary processes (e.g., updating files) in BOARD.BAT.
-==== Subcommand ====
-|**[node]**|Node number to recycle.|This value represents the node number that will be recycled.|
-==== Description ====
-When a node is recycled, PCBoard exits with an errorlevel of 6 and then continues executing BOARD.BAT.  You can use this recycle to run a batch file that would update necessary system files or whatever is needed.  Simply add a line to  BOARD.BAT that checks for an errorlevel of 6.  If an errorlevel of 6 is detected, run the appropriate batch file.  The following might resemble your new BOARD.BAT file:
-	@echo off
-	c:
-	cd\pcb
-	set pcb=
-	set dszlog=pcbdsz.log
-	if exist remote.bat rename remote.bat remote.sys
-	if exist door.bat del door.bat
-	if exist endpcb del endpcb
-	pcboard
-	if exist remote.bat remote
-	if exist door.bat door
-	if exist endpcb goto end
-	if errorlevel == 6 call c:\update.bat
-	board
-	:end
-In this example, C:\UPDATE.BAT would be executed if the node is marked for recycling.  Because the call statement is used, DOS will return control back to BOARD.BAT which will execute the next line which consequently reloads PCBoard.  The system is ready for callers again and the batch file updated any necessary files.
-**NOTE:** A node can also be marked for recycling by pressing ALT-R while a user is online.
-===== BR   Broadcast Message to Any Node =====
-Enables you to send a brief message to any node number.  You can use this command to notify users that you are about to shut down the system or just to say hello.
-==== Subcommands ====
-|**[node #]**|Node number.|This can be any active node number.  You may also type ALL in place of the node number to broadcast the message to all active nodes.|
-|**[message]**|Message to send to another node.|Any text up to 48 characters in length.  Text is displayed in all capital letters and punctuation is omitted.|
-==== Description ====
-Allows any user with SysOp security to display a message to any or all active nodes.  This command is useful to notify users that the system may be going down, or if you wish to have all users log off of the system.
-When the message is displayed to the user it will also send a beep to help get the user's attention.
-**NOTE:** All subcommands must be placed on the command line.  If you type BR and press enter then you will be returned back to the command prompt and no action will have taken place.
-If a user is not in PCBoard (e.g., the user is currently in a DOOR) then the user will not see the message because they were not in PCBoard at the time the broadcast message was sent.
-==== Examples ====
-To broadcast a message to node 1 which says PLEASE LOG OFF AS SOON AS POSSIBLE you would type:
-	BR 1 PLEASE LOG OFF AS SOON AS POSSIBLE
-To broadcast a message to all active nodes which notifies the users that you would like them to log off of the system you would type the following at the command prompt:
-	BR ALL PLEASE LOG OFF AS SOON AS POSSIBLE