SYSTEM SYSOPS COMMANDS MANUAL for Pascal Integrated Communications System (PICS) Version 1.0 August 1,1986 Les Archambault PICS.PAS and the associated support files (including this documentation file) are Copyright (c) 1986 by Les Archambault. Non-commercial, public distribution and use of this system is permitted. All commercial rights are reserved. Distribution of PICS should include this documentation. In this section, I will describe the PICS commands that are NOT covered in the Users Guide (PICSUSR.MAN) and are only available to the Sysop and assistants (access level >=250). I assume that you have read and understand that document and have used a PICS system. The theory of operation and details of how PICS does things will be covered in a separate section. While the system is idling, i.e. waiting for a call, the CRT screen will be cleared and the cursor randomly repositioned every few seconds to eliminate any possibility of phosphor burn. If the system is re-cycling from a caller logoff and the space left on disk is less than the amount set, the local Sysop console will display a message approximately every five times the cursor moves. It will detail the disk space problem and stay on the screen for about 6 seconds. This indicates that the Sysop should take whatever action is necessary to make more disk space available. IDLING (WAITING FOR CALL) COMMANDS If you desire, you may get a system status report by entering a CONTROL J at the Sysop console (terminal). PICS will then display the other two possible commands on the status line of the console. The other two commands are Control C for exiting PICS, and Control L for local Sysop use. In addition the screen will display the following information: Auto Macro Operation ON/OFF If ON, the hour macro processing starts. 300 Baud Caller restriction ON/OFF If ON, the hours the restriction applies. Chat Function ON/OFF If ON, the hours chatting will be accepted. Message Length Limit ON/OFF If ON, the number of lines per message allowed. Public Messages Restricted ON/OFF Extra Time on system granted If ON, the hours and number of minutes added. This message will stay on the console screen for about 25 seconds. SYSTEM IN USE NOTES While the system is in use by a caller, the following in use commands are available to the Sysop (^ means control character): ^J Display menu of console commands on the status line. ^W: Sysop initiated CHAT ^E: Blank out remote caller screen, on/off ^R: Grab system for local use after caller logs off. ^T: Twit ^W Sysop initiated CHAT. The current user is issued a message and the system enters the chat mode. This command bypasses the time of day checks and may be entered at any time (chat hours are restricted to callers requesting chat). ^E 'Blank' remote screen. Toggle output to remote system. Useful to help a lost user find a file or message. May also be used to validate a remote user since the access level is temporarily set to SYSOP level and then reset when remote I/O is reinstated. ^R 'Delayed' shutdown. When the current user logs out, the modem is made busy and the system rings the bell to indicate that it is available. This funtion is useful on busy systems when the sysop has trouble getting access. Until the operation actually takes place, this key may be used to alternately turn the function on and off. If the sysop doesn't take action to take over the system in a reasonable period of time, the system will put itself back online waiting for calls. The local console screen will show a countdown message. ^T 'Twit' key. Immediately hang up on remote user. The previous command is preferred to gain system access, but sometimes this command is necessary. =============================================================== MESSAGE READING SYSOP COMMANDS While reading messages and at the Read

prompt there are two Sysop Commands available, and . Etended Sysop Commands This command acts on the current message being read and will show you a new prompt: Sysop Message Command

elete message - marks message deleted. ide Message - Marks message as Restricted and therefore invisible until Sysop releases it. ndividual - Marks message as Private. ove - Lets you change the message area. o Purge - Toggles the protection from purging and notifies you of the status.

ublic - Marks the message as Public. ead - Marks the message as having been read. uit this command. alidate Caller With this command you are able to validate the caller who left the current message being read. The callers log-in information will be displayed and the proposed (default) access level and time allowed on system will also be shown. You will have a chance to change these if you wish. ave Message to Disk File This command will save the current message being read to a disk file in the System File Section. You will be prompted for the filename to use for the file. If it already exists, you will be asked is you want to use it anyway. After recording the message (and header) you will be returned to reading messages. After both of these commands are used, you are returned to the message reading commands and can continue reading the next message. ================================================================ FILES SUB-SYSTEM SYSOP COMMANDS The following commands are only available to the sysop and assistants, (access level of 250-255) even though they are located in the Files subsystem. The command prompts will be displayed only if the current user access level >=250. COPY - This command is used to copy a file from the current File Section to another File Section. When the copy is completed successfully, the system will ask if the source file should be deleted. DELETE - This command is used to delete any file from the currently logged File Section. Verification is requested before the action takes place. RENAME - Allows renaming of any file in the current File Section. STAT - Shows the status: (visible/invisible) of the named file in the current File area and asks if you want to reverse the status. ================================================================= UTILITIES SYSOP COMMANDS isplay Users - You are given the choice of several kinds of lists from the following menu. If current user access is less than 250 the rief list is automatic. Type of List ll - A complete list of all users and all information in each user record is displayed. rief - This is the same list shown to regular callers. (Names only) xceptional - Users having access higher than the default value or greater time allowed on the system are displayed. nvalidated - Unvalidated Users are displayed. hat - The Sysop answers a chat request with the Escape key if he desires to chat with the caller. Either party can exit the chat with a Control C character. ime - After displaying the information you will be asked if you want to change the time. If you do, you will be prompted for year, month, day, hour, minute, and second (one at a time). It is expecting up to 2 numeric digits as a reply. =============================================================== SYSOP SUB-SYSTEM COMMANDS The sysop sub-system command menu is accessed by typing "X" at any function prompt (this option is locked out to users below access level 250). The sysop menu may be displayed by entering "?" (see sample partial menu below). The user, log, and message files may be displayed on the CRT or printed to the LST device based on the condition of the print toggle. In addition, the Audit file command can be used to write the LOG or Message files to a disk ASCII text file. NOTE: After the sample menu, each command is described in more detail. Sysop Sub-System Partial Menu ----------------------------- udit trail toggle Macro operations uild Message

urge files hange System parameters ead Messages elete user ystem Directory dit user oggle printer ndex rebuild alidate User og file list ewin file processing oodbye (logoff) udit Command --------------- A standard ASCII text file can be created from the log and mes- sage files by turning on an audit trail and using the 'L' and 'R' sysop commands. The system will show you the default File Section where the Audit File will be written and ask if you want to make a change. The created file consists of the system date as file name with a numeric extension starting with zero. For example, the first time the audit trail is enabled on the 15th of August 1985, the name would be 08-15-85.000. If the audit trail were turned off and on later in the same day, the file name would be 08-15- 85.001. uild Message Command ----------------------- With this command you are able to build a message (in the message base) from a disk file (ASCII text file only). The file to be used must be in the System File Section. You will be prompted for the header information and then the name of the file to be used as the body of the message. hange System Parameters Command ---------------------------------- This command gives the Sysop the ability to make changes to the system operational default settings that are contained in the PICSDEF.INC file. The default settings take effect when PICS is entered and remain set until changed. See the Defaults section of this manual for a complete description of these settings. You will be asked if you wish to change the SYSTEM or PURGE settings. This division of the settings is for screen display convenience only. elete User Command --------------------- The sysop is asked for a name to be deleted from the user file. PICS prompts to insure that this is the action desired and if so, deletes the user and any messages addressed to or from that user. dit User Command ------------------- The record of the selected user is displayed and the cursor is positioned at the password field. Because the user name is used as the key to this record, the sysop will not be given the opportunity to change either the first or last name fields. The time of last access is also unchangeable. You will be prompted for the number of the item that you want to change and shown the exit sequence. In all other cases which require the user name, PICS expects an exact match between the characters entered and the name in the file. In this command (Edit User), PICS is somewhat more forgiving and will find the record which is equal to OR GREATER THAN the entered name. For example, if you cannot remember how John Smith spells his last name, enter 'John Smith' and PICS will find the record even if John spells his last name 'Smithe.' The drawback to this of course, is that it is possible to get the wrong user record if two names are very similar, so be very careful that you have the expected record before editing. Note: It is in this command that you are able to change the user record flag bits that control each user's priviledges and authorization to enter conferences. There are seven possible conferences, but don't set any flags above the maximum number you are using, as that would give the user access to possible future conferences. There are currently five active user priviledge flags: Allow downloading files Allow entering of private messages Allow entering of public messages Allow entering any messages Exempt user from User File purges. When a new user record is created, the user is not granted authorization for any conferences. The first four priviledge flags are set to allow the indicated actions, and the user is not exempt from a User file purge. ndex rebuild Command ----------------------- If you suspect that either the user file or its index may be damaged, this command may be used to rebuild the index file and recover from certain types of damage to the user data file. File damage should never occur during normal operation, but power fluctuations and faulty disks and drives can cause problems. During execution of this command, the record number, a linked list element, and the user names are displayed. For more infor- mation about the structure of data files when using the Turbo Toolbox, refer to the Turbo Toolbox Referance Manual (c) Borland International. og file list Command ----------------------- PICS maintains a time and date stamped list of most system opera- tions. This command will display this list. From the information contained in this file, the sysop can determine what kind of activity the system is being used for, what users seem to be having problems, what users are abusing their privileges, etc. If audit file generation is turned on, the log information will be written to this file. ewin file processing Command ------------------------------- PICS marks all uploads with the system attribute bit (making them invisible) to prevent directory display, and stores a one line description of the file. This command allows the sysop to release the file and description for access by normal users, hide the file and description from normal users, delete the description (not the file itself), edit the description. Until the file is purged (see Purge), all entries may be freely edited by the sysop. For example, when a user uploads a file, PICS will mark the file as hidden until the sysop has a chance to review the contents of that file. If appropriate, the sysop can release the file (making it visible in the File Section directory) for users. At that time, not only will the file be available in the NEWIN section (or section where the Sysop has moved it) for downloading, but the description entered at upload time can be seen by other users using the Newin command at the files sub-system menu. In addition to the file name and description, PICS displays the name of the individual that performed the upload and the time and date the operation was completed. When the file has 'aged' in the NEWIN section sufficiently, the delete command will delete the description and mark the file as hidden once again. Conventional CP/M utilities or extended sysop commands may then be used to move the file to a more permanent file area and reset the system attribute bit, making it visible again. Macro Operations Command ---------------------------- In addition to being able to read characters from either the keyboard or the remote channel, PICS can read from an internal character string called a macro. This string can be used to execute any sequence of operations as defined by the sysop. The macro string is fed into the multiple command buffer for execution so be sure that it is a completely executable set of commands. Macro operations may be performed while the system is being used by the Sysop, or from the automatic macro operation switch setting where the system logs the Sysop in and performs the macro string even though there is no one at the local console. For example, the sequence 'T;Y;U;U;A;^M;X;L;R;P;A;Y;T' performs the following operations: Toggle the printer on T Yes, really do it Y Utility sub-system entry U User file listing of ... U All users A No starting name specified ^M (carriage return) Re-enter the sysop sub-system X List the log file L Read the messages R Purge ... P All files A Yes, really do it Y Toggle the printer back off T Remember if you have the auto macro processing switch turned on so that the macro will execute by itself every day, the last command in the macro MUST be a G so that the system will terminate the macro and go back online waiting for callers. (During the auto macro execution, the system thinks the sysop is using the system locally.) This type of operation is typical of that performed during the regular maintenance of the PICS files and can take some time to complete. The ability to perform these operations unattended can be very convenient. Three commands are available to control the macro operation: Display the contents of the macro buffer Edit the macro string (editing commands are described in the User's Guide) Start the macro PICS is still monitoring both the local keyboard while processing a macro, so the sysop can pause (^S) or cancel (^C) a command, but macro processing will continue until complete. Since a carriage return is used to terminate the entry of a new macro string, a slash (/) may be entered into the macro. When encountered, PICS will convert this character into a carriage return.

urge files Command --------------------- This command purges and compresses system data files of deleted entries. It processes four different files, each selectable by a single command, or all four files together. All commands are verified before continuing. Sufficient disk space must be available for these operations or PICS will report an error and terminate. Should this happen, PICS will automatically recover from the old files the next time it is started, but extraneous files may be left on the disk. Purge All - This command purges all four files, i.e. it automatically performs a purge of the log, newin, user, and messages files. Purge Log - This command removes all entries from the log file. Purge Newin - This command removes all entries marked "deleted" in the newin file. Purge Messages - As described in the introduction, deleting a message only marks that message for delete. To physically remove the message from the disk, the message files must be purged. Purge Users - This command deletes all users that have not logged in within the times specified at compile time. When a user is deleted with this command, PICS will also delete any messages sent to or from the user. ead messages Command ----------------------- All messages currently on file are displayed in numerical order. If the audit trail is on, these messages are also written to that file. ystem directory Command -------------------------- A directory of all files in sections with access levels of 20 or less is built in the LOGIN section. This directory can be used by remote users to speed file download operations. oggle printer Command ------------------------ The currently assigned LST device is alternately enabled and disabled. To prevent possible toggling while remote, this com- mand is verified before continuing. alidate user Command ----------------------- This command allows the sysop to validate a user from the Sysop sub-system menu instead of going into the message file. It is most helpful when you know the name of the user that you want to validate. NOTE: The validate and delete commands will only operate on users of a lower access level. The edit command will operate on users of the same or lower access level. This access level structure allows the primary sysop to affect all user records in the system, including his own, but alternate sysops can neither affect nor view the record of the primary sysop. In addition, since the validate and delete commands only operate on users of a lower access level, the hazard of valida- ting or deleting oneself has been reduced. CAUTION: Since the primary sysop can edit any user record, please exercise care not to lower your own access level! The only known recovery from this action (if there are no other sysops at the 255 level) would be to use a file zap utility such as PATCH.COM.