Total Communications System tm TCOMM User Supported Version 1.6 published by The CommSoft Group The CommSoft License Agreement The CommSoft Group provides this user supported program for your use. You assume responsibility for the selection of this program to achieve your intended results, and for the installation, configuration, use and results obtained from the program. LICENSE You may: 1. use this user supported program on any IBM or IBM compatible Personal Computer; 2. copy the program into any machine for backup in support of your use of the program; 3. transfer the program and license to another party if the other party agrees to accept the terms and conditions of this Agreement. You must reproduce and include the copyright notice(s) without modification on any copy of the program. You must not modify the INFO file that is included with the program. You must provide the INFO file with any application of the program such that it is displayed for users when the Description command is executed. You must not charge a fee for this program that exceeds the cost of the medium on which it is stored plus postage and ten percent for handling. YOU MAY NOT USE, COPY, MODIFY, OR TRANSFER THE PROGRAM OR ANY COPY, IN WHOLE OR IN PART, EXCEPT AS EXPRESSLY PROVIDED FOR IN THIS LICENSE. TERM The license is effective until terminated. You may terminate the license at any time by destroying the program together with all copies. The license will also terminate upon conditions set forth elsewhere in this Agreement or if you fail to comply with any term or condition of this Agreement. You agree upon such termination to destroy the program together with all copies in any form. ii LIMITED WARRANTY THE PROGRAM IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE ENTIRE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. SOME STATES DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSION MAY NOT APPLY TO YOU. THIS WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS AND YOU MAY ALSO HAVE OTHER RIGHTS WHICH VARY FROM STATE TO STATE. The CommSoft Group does not warranty that the functions contained in the program will meet your requirements or that the operation of the program will be uninterrupted or error free. The program is provided for demonstration purposes only. LIMITATIONS OF REMEDIES The CommSoft Group's entire liability and your exclusive remedy shall be to make available a copy of the user supported program for download from a user support bulletin board system. IN NO EVENT WILL THE COMMSOFT GROUP BE LIABLE TO YOU FOR ANY DAMAGES, INCLUDING ANY LOST PROFITS, LOST SAVINGS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE SUCH PROGRAM EVEN IF PEOPLE HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, OR ANY CLAIM BY ANY OTHER PARTY. SOME STATES DO NOT ALLOW THE LIMITATION OR EXCLUSION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES SO THE ABOVE LIMITATION OR EXCLUSION MAY NOT APPLY TO YOU. iii GENERAL You may not sublicense, assign or transfer the license or the program except as expressly provided in this Agreement. Any attempt otherwise to sublicense, assign, or transfer any of the rights, duties or obligations hereunder is void. This Agreement will be governed by the state of Maryland. Should you have any questions concerning this Agreement, you may contact The CommSoft Group by writing to The CommSoft Group, PO Box 3652, Gaithersburg, MD, 20878. YOU ACKNOWLEDGE THAT YOU HAVE READ THIS AGREEMENT, UNDERSTAND IT AND AND AGREE TO BE BOUND BY ITS TERMS AND CONDITIONS. YOU FURTHER AGREE THAT IT IS THE COMPLETE AND EXCLUSIVE STATEMENT OF THE AGREEMENT BETWEEN US WHICH SUPERSEDES ANY PROPOSAL OR PRIOR AGREEMENT, ORAL OR WRITTEN, AND ANY OTHER COMMUNICATIONS BETWEEN US RELATING TO THE SUBJECT MATTER OF THIS AGREEMENT. iv Third Edition (August 1, 1987) This product could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes will be incorporated in new editions of this manual. TCOMM is designed to provide all the unattended communications capabilities in one package that most people need and use. An unattended communications system should provide robust electronic mail, file transfer and remote software execution capabilities. An unattended communications software System Operator should not have to exit the system to perform system configuration changes and callers should not have to wait for program segment chaining when moving from one subsystem to another. The system should also provide absolute security and robust flexibility. TCOMM provides all these capabilities and more in one software package. This user supported version of TCOMM was designed to provide users with a feel for the operation of the commercial versions of TCOMM. The commercial versions of TCOMM contain far more features than this user support version as described in the INFO file distributed with this software. The only limitation in this version of TCOMM is that it does not contain all of the features found in the commercial versions of TCOMM and TCOMMnet. (c) Copyright Larry Jordan Associates 1984, 1985 (c) Copyright The CommSoft Group 1986, 1987 All Rights Reserved. v About The Authors TCOMM User Supported Version 1.6 is written in C and assembly language. The software was originally designed by Larry Jordan in 1983 and written by Larry Jordan and Jan van der Eijk based on several man-years of experience writing and testing unattended communications software. TCOMM was first published commercially as Version 1.15 in February 1985. Demonstration Version 1.5 and commercial version 2.0 were published in August 1985. All software modifications have been made by Jan van der Eijk since August 1985, including the changes required for Version 1.6 and the commercial versions of TCOMM and TCOMMnet. vi Preface This manual provides you with the following information about TCOMM: o How to install and setup a TCOMM system o Product features and system requirements o IBM Personal Computer setup required to operate TCOMM o How to set up bulletin, program and file menus o How to personalize display files and messages o How to customize the unattended TCOMM mode of operation o How to install and use file transfer protocols o How to interact with the system o How to troubleshoot problems and understand system messages If you have difficulty getting TCOMM up and running or you experience problems with the software, please read this manual again before calling for help. Almost all the questions received to date have been answered in the documentation manual. A great deal of effort went into the development of this documentation. It could save you time and efforts to read it carefully. vii Assumptions If you are going to communicate with a remote computer in the TCOMM terminal mode, this manual assumes that you already know the procedure for connecting with that computer. If you are not familiar with the procedure, you should refer to the remote computer's user manual or operations manual for information about that computer's login procedure. This manual also assumes you have a working knowledge of asynchronous communications with the IBM Personal Computer. If you are new to data communications with personal computers, you should read the book titled Communications and Networking for the IBM PC and Compatibles before attempting to start up TCOMM. This book is published by Prentice-Hall and is available in most IBM Personal Computer retail stores and in book stores that sell personal computer books. viii Contents Chapter 1. Introduction What is TCOMM? ............................... 1 TCOMM Software in Perspective ................ 2 TCOMM System Overview ........................ 3 Chapter 2. Getting Started System Requirements .......................... 4 Hardware Setup ............................... 7 Software Installation ........................ 9 TCOMM Initial Setup .......................... 14 Customizing the Text Files ................... 17 TCOMM Startup ................................ 31 Chapter 3. Local System Controls Function Key Controls ........................ 32 Operator Main Menu ........................... 36 Chapter 4. System Operator Access System Operator Passwords .................... 42 System Operator Privileges ................... 43 System Operator Remote Maintenance ........... 44 Chapter 5. Unattended System Operation Waiting for a Call ........................... 45 Detecting Caller Parameters .................. 45 The Welcome Message .......................... 46 Caller Login ................................. 46 Chapter 6. Smart Terminal Operation Getting to the Terminal Menu ................. 49 Smart Terminal Commands ...................... 50 Communication Parameters ..................... 51 ix Chapter 7. System Maintenance Bulletins .................................... 53 Mail Subsystem ............................... 53 User Data Base ............................... 54 User Data Base Data Fields ................... 57 Activity Log ................................. 60 Files Subsystem .............................. 60 Data Backup .................................. 60 Chapter 8. System Operation Tips Caller Activity .............................. 61 Long Unattended Periods ...................... 61 Avoiding Caller Problems ..................... 61 Uploaded File Tips ........................... 63 Generating System Usage ...................... 65 Chapter 9. System Configuration Profile System Configuration Profile ................. 67 Chapter 10. System Security New Caller Login Privileges .................. 100 User Security Level Modification ............. 104 Preregistered Users .......................... 104 Chapter 11. Caller Groups Configuring Groups ........................... 105 User Data Base Group Designation ............. 107 Chapter 12. External File Transfer Protocols Location of Protocols ........................ 109 Design of Protocols .......................... 109 Chapter 13. Problem Diagnosis Finding a Solution ........................... 111 Missing Files ................................ 111 System Configuration Problems ................ 112 Software Incompatibilities ................... 112 Hardware Configuration ....................... 112 xi Chapter 14. Who To Call Telephone Support ............................ 113 xi Chapter 1. Introduction What Is TCOMM? TCOMM is a software package designed to provide robust electronic mail, remote program execution, and file exchange between microcomputers. After it is properly installed and initially configured, TCOMM can operate with a minimum of maintenance 24 hours a day. The system is designed to support information interchange needs of both novice and advanced users. TCOMM is written in the "C" language which provides compact and high performance code. Because the program is compact, the TCOMM developers were able to include many powerful features in the system while maintaining fast response to user commands. The execution speed of the software allows high-speed file transfer even on a diskette drive based system. TCOMM's file transfer speed is limited only by current dialup asynchronous modem hardware technology. TCOMM allows flexible implementation. The system command structure and security scheme allows the System Operator to tailor software operation and user access to match specific information exchange or file transfer needs. TCOMM was designed and written for maximum reliability and integrity. The TCOMM System Operator can rest assured that callers can only access and perform functions they have been authorized to use. The proprietary design of the security system and the absence of published system source code add to the high reliability and integrity of the system even under most adverse user exposure. The system senses potential caller abuse patterns and records the information for System Operator review. TCOMM can also be configured to "lock-out" callers that do not adhere to posted system rules. Because of the robust unattended communications features offered in TCOMM, it is worthwhile to explore typical uses and major features of the software before initial operation of the system. The following paragraphs place TCOMM in perspective relative to other types of unattended communications software packages and provide a review of TCOMM features that will assist the System Operator during initial operation of the software. Experienced unattended communications software operators may want to skip these sections and go directly to Chapter 2. 1 TCOMM Software In Perspective Communications software is generally categorized as either attended or unattended. Attended communications software requires the presence of a Personal Computer operator to interact with a remote computer system. This type of software emulates a terminal device. Unattended communications software automatically handles incoming calls and only requires intermittent operator attendance. Unattended communications software is normally further categorized as either host, bulletin board, or electronic mail software. A host software equipped Personal Computer is used primarily for remote operation. This type of system can accept calls from remote terminals and execute commands received through the serial port just as it executes local keyboard commands. A bulletin board equipped Personal Computer is primarily used for message and file exchange. This type of system is capable of receiving and storing messages and files received from a remote computer and is capable of transmitting messages and files to a remote computer. An electronic mail system is used to exchange mail between callers. This third type of unattended software usually offers enhanced message exchange capability but limited file transfer features. TCOMM combines both attended and unattended communications software features in a single package and offers bulletin board, host and electronic mail features. The system can be used to access other micro, mini, or mainframe computers using smart terminal communications. The System Operator can interact with these computers from the keyboard. The System Operator or local users can logon the system and use the electronic mail and bulletin features in the same way that remote callers use the system. TCOMM can be placed in an unattended mode to allow remote callers to use the system. TCOMM will automatically answer calls and match communication parameters with each caller. The system can also screen callers based on a built-in security system and allow callers to perform only communication functions assigned by the local System Operator. In the unattended mode, TCOMM allows remote callers access to bulletins and messages. Bulletins created by the System Operator can be listed. Messages left by other callers and the System Operator can be read. Callers can also leave messages for other callers and the System Operator. Messages can be declared public or private. If the System Operator has configured the system to support multiple caller groups, public messages and bulletins can be segregated by group. 2 The unattended TCOMM mode allow the system to send and receive files. The system allows remote callers to transfer ASCII text files and binary program and data files. These file transfers can be performed with or without special protocol error-checking techniques. If the System Operator has configured the system to support multiple caller groups, files available for downloading can be segregated by group. TCOMM allows callers to execute external programs made available by the System Operator. The System Operator can use this feature to survey callers or to allow callers to place orders for products. Programs made available for caller execution do not have to be special communications programs--any program or software written for the IBM PC that uses BIOS and PC-DOS calls for video output can be executed. Software written in BASIC and software that writes directly to hardware (such as Lotus 1-2-3) cannot be executed remotely. Beyond these general characteristics, there are several TCOMM capabilities worth noting. The following paragraphs describe these capabilities. TCOMM SYSTEM OVERVIEW Figure 1-1 provides a diagram of the major TCOMM capabilities. As this figure shows, TCOMM consists of ten major subsystems. Local Operator Access | ------------------------------ | | | | Config- Data Base Operator Smart Remote uration Maintenance Controls Terminal Caller Profile | Access | | ------------------------------------------------------ | | | | | | Bulletin Change Files Mail Operator Programs Subsystem Subsystem Subsystem Subsystem Subsystem Subsystem Figure 1-1. TCOMM Subsystems diagram. 3 Chapter 2. Getting Started SYSTEM REQUIREMENTS TCOMM requires certain hardware and software to operate properly. If these requirements are not met, the system may not operate as described in this manual. The following paragraphs describe the TCOMM requirements. Hardware Requirements TCOMM is compatible with a variety of IBM PC hardware configurations, but the less disk space available the more file maintenance the System Operator must perform. With frequent System Operator maintenance, an active system could operate from two dual-sided diskette drives. An infrequently maintained active system will require at least a five megabyte fixed disk. TCOMM will operate with a variety of Hayes Smartmodem compatible modems. Most System Operators prefer external modems because the activity and status lights help diagnose system configuration and telephone system problems. The modem and telephone system recommendations in this manual are based on the Hayes Smartmodem. If a different modem is selected for use with TCOMM, it is the user's responsibility to ensure that the modem is completely Hayes compatible. The minimum TCOMM hardware requirements are as follows: Computer System --------------- IBM PC, IBM PC XT, IBM Portable PC, IBM PC AT, IBM PS/2 320 Kb Random Access Memory (RAM) Two dual-sided diskette drive or fixed disk 80 column monitor Battery powered clock/calendar with PC and XT (optional) Communications Hardware ----------------------- Hayes compatible 300, 1200 or 2400 bps modem, Asynchronous communications adapter, and RS-232C cable (with all 25 pins connected) or Hayes compatible internal modem adapter board 4 Compatible Modems ----------------- The following modems have been tested with TCOMM and are compatible with the software: MultiTech Systems, MultiModem 224 U S Robotics, Courier 2400 ARC Electronic Products, 24K and 24K Plus Telephone Equipment ------------------- Voice grade telephone line Standard modular RJ11 jacks Modular telephone cable Other Equipment --------------- Parallel Printer (optional) The switches inside external, stand-alone Hayes Smartmodems must be positioned as shown in Table 2-1. These switch settings will work with many other communications software packages, including PC-TALK. If you do plan to use other communications software, refer to the documentation for the package to be sure it will operate properly with the TCOMM required Hayes switch settings. Switch settings for the internal Hayes Smartmodem 1200b do not have to be changed from the factory settings. The configuration of the Hayes Smartmodem 2400 does not have to be changed either. TCOMM uses software commands to change the configuration of these modems. TCOMM should only be used with versions 123 and above of the Hayes Smartmodem 1200. Earlier versions may not answer the telephone properly and could cause TCOMM to malfunction. The Hayes "ATI" command will cause the Smartmodem to respond with its version number. A full 25 pin RS-232C cable should be used to connect an external modem with the IBM PC or XT asynchronous communications adapter. In addition to the signals that are transmitted through RS-232C pins 1 through 8, TCOMM requires the use of pins 20 and 22. The pin 20 signal is for Data Terminal Ready and is required for command transfer from the PC to the modem. The pin 22 signal is for Ring Indicate. TCOMM must see this signal before it will tell the modem to answer an incoming call. To be sure all 25 pins are connected have an electrical technician check the cable. New cables should be specifically ordered with all 25 pins connected. Cables used with the IBM PC AT serial/parallel adapter should have all nine pins connected. Pin 9 must be connected to support 5 auto-answer of incoming calls. Table 2-1. Hayes Smartmodem 300 and 1200 switch settings. --------------------------------------------------------------- Switch Position Function ------ -------- ----------------------------------------- 1 Up Allows the modem to hangup the phone when the PC drops the Data Terminal Ready signal. 2 Up Modem results codes are sent to the PC in English words. 3 Down Modem sends results codes to PC when commands are received from the PC. 4 Down Modem does not echo commands back to the PC. 5 Down Modem will not answer incoming calls automatically (TCOMM does this). 6 Up Enables the PC to determine if a carrier signal is coming from a distant modem. 7 Up Indicates modem is connected to an RJ11 modular telephone jack. 8 Down Enables modem to recognize commands. Software Requirements TCOMM will operate under DOS versions 2.0, 2.10, 3.0, 3.10, 3.20 and 3.30. It will also operate with the DOS PATH command. Multiple copies of TCOMM version 1.6 will not operate properly under multitask or multiuser versions environments. These capabilities are supported in the TCOMMnet commercial version of TCOMM. Some interrupt driven "stay resident" programs that operate in a background mode such as print spoolers or RAM disks may be incompatible with TCOMM. Data path utilities that allow you to open data files located in other subdirectories may cause performance problems for TCOMM. Background software that uses the communications ports to dial telephone numbers will cause problems with TCOMM. If problems arise when these programs or utilities are being used, the background mode software should be removed from the system and the PC should be restarted from a cold shutdown state (turn the power switch off for at least 10 seconds then turn the power back on) before restarting TCOMM. To be completely safe, use only software that is distributed on the IBM DOS diskettes when you are operating TCOMM. 6 HARDWARE SETUP Proper operation of TCOMM requires proper IBM PC and peripheral setup, including communications and printer hardware. There are power line and telephone line setup requirements that must also be met. The following paragraphs describe the differences between the standard configurations of these devices and the configurations required by TCOMM. This manual assumes that you have the operations manual for each of the computer devices and you are already familiar with their setup and operation. Communications Hardware The communications hardware setup depends on the type of modem selected. An external modem provides indicator lights that help problem diagnosis and readily show system activity, but an asynchronous adapter and cable must be provided. An internal modem is safely stored inside the PC system unit, but there are no indicator lights to help with problem diagnosis. The following communications setup procedures are separated by modem type. External Modem Setup An external modem hardware configuration will require the components described in the following paragraphs. Asynchronous Communications Adapter The TCOMM default Configuration Profile setup assumes that you will use the asynchronous communications adapter as communications port 1. This is sometimes designated as "COM1" or "COM1:" and is the default setting for the standard IBM Asynchronous Communications Adapter. If you are already using COM1 for a serial device such as a printer or a light pen, you will need to operate TCOMM on a second communications port. Be sure the adapter switches or jumpers are set up for COM2 before the adapter is installed in the PC. The Initial Setup should be modified to reflect the use of port 2 during the software installation process. RS-232C Cable A standard 25 pin RS-232C cable should be connected between the IBM PC and XT asynchronous adapter and the modem to be used with TCOMM. A 9-pin RS-232C cable should be used between an IBM PC AT serial/parallel 7 adapter and the modem. The cable can be the flat ribbon type or the round shielded type. Shielded cable should be used in areas that have high electrical noise generators such as areas adjacent to elevator shafts or high-voltage power lines. Be sure the cable is securely connected to the asynchronous communications adapter and the modem. External Modem TCOMM is compatible with external Hayes Smartmodems. The front cover of the Hayes modem must be removed and the configuration DIP switches must be positioned as shown in Table 2-1. TCOMM should only be used with versions 123 and above of the Hayes Smartmodem 1200. Earlier versions may not answer the telephone properly and could cause TCOMM to malfunction. The Hayes "ATI" command will cause the Smartmodem to respond with its version number. Internal Modem Setup The Hayes internal modem configuration switches do not have to be changed from the factory settings unless the modem is used as communications port 2. The TCOMM default Configuration Profile setup assumes that you will use the internal modem as communications port 1. This is sometimes designated as "COM1" or "COM1:" and is the default setting for the Hayes Smartmodem 1200b. If you are already using COM1 for a serial device such as a printer or a light pen, you will need to operate TCOMM on a second communications port. Be sure the modem switches are set up for COM2 before the modem is installed in the PC. The Initial Setup should be modified to reflect the use of port 2 during the software installation process described later. Printer If TCOMM activity is to be logged to a printer, an IBM PC compatible parallel printer should be connected to a parallel adapter in the PC. TCOMM assumes that the printer is attached to printer port LPT1; this can be changed to LPT2 or LPT3 in the Configuration Profile. The printer output is done in TTY mode without pagination or form-feed control. No special print formatting is performed. If you use a printer, be sure that it has sufficient paper and that the power is on. Also be sure that the printer is in print mode, not in a local control mode. TCOMM will not operate properly if system activity printing is requested and the printer 8 is not properly set up. Telephone Line Most applications require a dedicated voice grade telephone line. A dedicated line can be used 24 hours a day without interfering with normal business or home voice communications. It should also be noted that a "data line" is not needed for most unattended communication systems. Voice grade lines are not as good for data communications as dedicated data lines, but for most TCOMM applications voice grade lines are sufficient. Voice grade lines are much less expensive to install than data lines. For personal use, you may also find that you can get pulse (rotary) lines at less cost than touch-tone lines. Most auto-dial, auto-answer modems provide both pulse and touch-tone options. Power Line Surge Protection Many System Operators use power line surge suppressors to eliminate power line spikes. This device is only useful if it is designed for fast response and high voltage filtering. Several IBM PC systems have operated around the clock for thousands of hours without surge protection and without system damage even in areas that have frequent electrical storms. The owners of these systems may have just been lucky. If you will feel more comfortable with a power-surge suppressor installed, you should get a good one. SOFTWARE INSTALLATION Installation of TCOMM requires startup of the IBM PC and execution of an installation program. TCOMM is shipped on one dual-sided diskette and will require the creation of Work diskettes if you plan to use diskette drives with the system. A two dual-sided diskette drive configuration will require two Work diskettes. The following paragraphs contain the Work diskette creation procedures. These procedures may be repeated in the future should the Work diskettes become unusable. Starting Your System Place the PC-DOS diskette in drive A. If your computer is off, turn on the power. If your computer is already on, press Ctrl, Alt and Del simultaneously to restart the system. Enter the appropriate responses to system requests for date and time unless your system includes a battery powered clock/calendar that does this automatically. 9 Note: It is important to enter the correct date and time when operating TCOMM. Many of the system features depend on these parameters. After you enter the date and time, you will receive the normal diskette drive A input prompt. Making Work Diskette(s) This procedure creates PC-DOS formatted diskettes for TCOMM operation. The number of diskettes you will need will depend upon your system configuration. Two Dual-Sided Diskette Drives You will need two Work diskettes for operation of TCOMM in two dual-sided diskette drives. Label these two diskettes TCOMM System Work and TCOMM Files Work. Format the TCOMM System Work diskette by placing the diskette in the diskette drive B and entering the following command: format b:/s When this format operation is completed, remove the TCOMM System Work diskette and place the TCOMM Files Work diskette in the B drive. Enter the following command to format the Files diskette: format b: One Fixed Disk and One Diskette You will not need a Work diskette for operation of TCOMM on a fixed disk drive unless you plan to have some files reside in a diskette drive. Initial setup using a fixed disk drive assumes that you will not use a diskette drive. You may change that configuration using the TCOMM Configuration Profile described later. Installing the System Operation of the TCOMM system is controlled by a Configuration Profile. This profile contains default values that are read each time the software is started and each time a caller logs off the system. The information stored in the profile determine the communications and printer ports to be used, what type of monitor is being used with the system, the locations and names of TCOMM files, the security levels required for execution of each system command and many other items of data. Because of the number of parameters contained in this profile and the power of some of the 10 parameters, three typical system configurations were chosen as default profiles. During the installation of TCOMM, you will have to chose one of the three default configurations. You will also be given the opportunity to modify the first page of the default system parameters--this page will contain all the items most people will want to alter during the initial setup of the system. After the TCOMM installation is completed, you may review the full configuration Profile to be sure the default values in the profile meet your needs. Configuration Profile access and execution are described in Chapter 9. The three default profiles are Private, Registered, and Bulletin Board. Each of these profiles can be installed in a system with two dual-sided diskette drives or a fixed disk. The Bulletin Board profile should only be installed on a fixed disk if more than 100 callers will be accessing the system. A brief description of the operation of TCOMM with each of these profiles is described in the following paragraphs. Private Profile The Private profile allows only the System Operator to access the system from a remote location. If a caller dials into the system and is unable to provide the special System Operator password when asked for a first and last name, the telephone connection will be broken. When the System Operator dials into the system and provides the special password, this caller will be given full access to the system. The Private profile is designated as 'P' during the installation process. Registered Profile The Registered profile allows the System Operator and the members of two preregistered groups to call into the system. The System Operator is given full system access after providing the special password. Callers that are preregistered as members of the two groups called GROUP1 and GROUP2 are immediately placed into these groups when they call into the system and provide their names and passwords. All other callers are turned away by the system if they are not found in the preregistered data base--the telephone connection is dropped after the caller is told he or she is not allowed access to the system. GROUP1 and GROUP2 were chosen as examples to illustrate group setup. You may want to go to the Configuration Profile and change these names before starting TCOMM operation. If you do change the group names, be sure to change the disk drive subdirectory names to match the names you place in the profile as discussed in Chapter 11. 11 The Registered profile is designated as 'R' during the installation process. Bulletin Board Profile The Bulletin Board profile allows all callers to enter the system and execute normal caller functions. Callers can read and leave messages, read bulletins, execute external programs, communicate with the local System Operator, upload and download files, and change some minor system operational characteristics. Only the System Operator and callers who are given an access level of 99 are allowed to perform functions normally reserved for the System Operator. The System Operator and callers who are given an access level of 99 by the System Operator are allowed to read all private mail and delete all messages; callers with these credentials are also allowed to perform user data base functions. The Bulletin Board profile does not allow callers to exit to DOS. If you want to exit to PC-DOS or if you want to allow special people to exit to PC-DOS from a remote terminal, you may modify the profile after the installation procedure is completed as discussed in Chapter 9. The Bulletin Board profile is designated as 'B' during the installation process. SOFTWARE INSTALLATION PROCEDURE Remove the PC-DOS diskette from diskette drive A and insert the TCOMM System diskette (the distribution diskette) in diskette drive A. Refer to the following installation section that describes your system configuration. Two Dual-Sided Diskette Drives This setup copies the TCOMM software, the TCOMM default Configuration Profile, the TCOMM batch operation file and all system text files to a diskette that will be run in drive A. The remaining Files Subsystem files are copied to a diskette that will be run in drive B. The TCOMM Profile contains all default diskette drive assignments. Enter the following command: INSTALL profile 2 substituting the letter of the chosen profile (P, R or B) in place of the word profile. 12 The installation program will indicate its progress and will prompt you for assistance. The installation procedure will also allow you to modify the first page of the Configuration Profile by executing an Initial Setup program. Refer to the Initial Setup subsection of this software installation procedure for an explanation of each of these initial setup parameters. The installation program will also prompt you when the installation is finished. When the installation procedure is complete, place the System Work diskette in diskette drive A and the Files Work diskette in diskette drive B. One Fixed Disk and One Diskette This setup creates subdirectories on the fixed disk and copies files to these subdirectories. A master subdirectory called "TCOMM" and five subdirectories called "TCOMM\SYSTEM", "TCOMM\TEXT", "TCOMM\MESSAGES", "TCOMM\PROG", and "TCOMM\FILES" will be created. The TCOMM program, the Configuration Profile, and all required system files will be copied to the "TCOMM\SYSTEM" subdirectory. All system help and bulletin files will be copied to the "TCOMM\TEXT" subdirectory. All message files will be copied to the "TCOMM\MESSAGES" subdirectory. All file transfer related files will be copied to the "TCOMM\FILES" subdirectory. All external program execution related files will be copied to the "TCOMM\PROG" subdirectory. The selected profile contains these default disk drive assignments. With this setup, PC-DOS must be on the fixed disk. This is required for automatic restart of the program should the system fail as a result of incorrect configuration settings. Automatic restart that results from a power outage will require the addition of a battery backup date and time adapter board in the IBM PC and XT; the AT comes configured with this capability. The command that obtains the date and time during system restart will have to be added to the TCOMM startup batch file called "TC.BAT" that is copied to the TCOMM\SYSTEM directory. The command TC will also have to be added to the normal PC-DOS AUTOEXEC.BAT file. A sample AUTOEXEC.BAT file called AUTOEXEC.TC is included on the TCOMM System disk. If you are going to allow caller exit to PC-DOS, caller execution of external programs or System Operator execution of operating system commands from within TCOMM, you will have to copy the COMMAND.COM file from a PC-DOS disk to the TCOMM\SYSTEM directory after the installation process is completed and before starting TCOMM. Be sure the version of COMMAND.COM you copy to this subdirectory matches the version of PC-DOS you are currently using. 13 Enter the following command: A:INSTALL profile f drive substituting the letter of the chosen profile (P, R or B) in place of the word profile and a letter indicating the fixed disk drive designation in place of the word drive. The fixed disk drive letter will normally be C. The installation program will indicate its progress and will prompt you for assistance. The installation procedure will also allow you to modify the first page of the Configuration Profile by executing an Initial Setup program. Refer to the Initial Setup subsection of this software installation procedure for an explanation of each of these initial setup parameters. The installation program will also prompt you when the installation is finished. Because of diskette space limitations, the Kermit file transfer protocol and the Xmodem source code are not included in the installation process. These two items are included on the Protocol Source Code diskette. If you wish to use the Kermit protocol, you should copy the KERMIT.EXE file to the System Work diskette or the TCOMM\SYSTEM subdirectory. You should also add KERMIT.EXE to the list of protocols in the Configuration Profile after the software installation process is completed. The Xmodem source code is an example of how to write file transfer protocols for TCOMM and should not be loaded into the TCOMM system area. TCOMM INITIAL SETUP During the TCOMM installation process, a configuration file containing default system operational parameters was copied to the TCOMM System Work disk or the TCOMM\SYSTEM subdirectory. Some of the parameters in this file must be reviewed and customized for your specific needs. The installation procedure executes an Initial Setup program that allows you to edit and modify only those parameters that have to be modified. The following paragraphs tell you the meaning of each Initial Setup parameter and how to edit the parameters during execution of the Initial Setup program. Initial Setup Parameter Editing All the parameters a new System Operator must review and modify are contained in the Initial Setup. Please review these parameters during execution of the Initial Setup program and modify the values that need to be changed. A detailed discussion of each parameter is provided later in this procedure. 14 To modify a profile parameter, type the parameter item number then press ENTER. TCOMM will prompt you for a new value. Type the new value then press ENTER. When all items have been reviewed and all changes have been made, type U and press ENTER to update the system profile settings. Initial Setup Parameters The following paragraphs describe the initial setup parameters that you must review and customize to match your computer hardware. Operator's first and last name This parameter is the System Operator's real first and last name. TCOMM will automatically use this name when the System Operator enters a message for a caller. This name is also recorded in the system activity log when the System Operator downloads or uploads a file. Operator's remote login code name The Operator's remote login code name is the name the System Operator will use when dialing into the system from a remote terminal or computer. The System Operator will get special control privileges if the code name is used during remote login. Note: TCOMM does not allow the Operator's code first name and last name to be the same as the Operator's real first and last name. This keeps callers from trying to use the System Operator's name in an attempt to get higher privileges. If a caller attempts to login using the Operator's real first and last name, TCOMM will drop the caller off the system and recycle to wait for another caller. Password required to access Operator Main Menu This local password controls System Operator access to the Operator Main Menu. The password should be one that the System Operator will not easily forget because access to this Configuration Profile is controlled by the same password. If you do forget the local access password, use a text editor to review the contents of the PROFILE.TC file to determine the password. 15 Maximum bits per second rate of system modem The System Operator should enter the maximum system modem speed here. Modem speed is rated in baud or bits per second (bps). If a Hayes Smartmodem 1200 is used with the system, a value of 1200 should be entered. If a Hayes Smartmodem 2400 is used, a value of 2400 should be entered. Entering an incorrect value could cause TCOMM to malfunction. Minimum allowable bits per second rate of system The System Operator should enter the minimum system modem speed TCOMM is to support. Modem speed is rated in baud or bits per second (bps). If a Hayes Smartmodem 1200 is used with the system, a value of 300 can be entered. If a Hayes Smartmodem 2400 is used, a value of 300 can still be entered. Entering an incorrect value will not cause TCOMM to malfunction, but it could keep some callers from accessing the system. Entering a value of 1200 will keep all 300 bps callers from accessing the system--some System Operators use this minimum modem speed to eliminate low speed modem users that may be abusing the system. Communication port to be used (1 or 2) TCOMM allows the System Operator to select either asynchronous port 1 or 2 corresponding to PC-DOS devices COM1 and COM2. These ports can be IBM or IBM compatible asynchronous ports with Hayes compatible modems attached via RS-232C cables or they can be internal Hayes Smartmodems. Selecting the wrong port will cause TCOMM to fail during its startup sequence. A message indicating this error will appear on the screen, and the System Operator will be allowed to correct the selection. Printer port to be used (1, 2 or 3) TCOMM allows the System Operator to select printer port 1, 2 or 3 corresponding to PC-DOS devices LPT1, LPT2 and LPT3. These ports can be IBM or IBM compatible parallel printer ports with IBM compatible printers attached via parallel cables. Selecting the wrong port will cause TCOMM to fail when caller activity or system error information is sent to the printer. A message indicating this error will appear on the screen, and the System Operator will be allowed to correct the selection. Operator's office hours starting time (military) The System Operator should enter the time of day (military format) that availability for caller paging will start. Caller pages before this hour will result in a friendly message indicating the System Operator is not available; the caller will be given your office hours at that time. To answer a caller page 16 (the system will beep to indicate a caller page) the System Operator should press function key F10. Note: Function keys F5 and F6 can be used later to temporarily override this office hour setting. Operator's office hours ending time (military) The System Operator should enter the time of day (military format) that availability for caller paging will end. Caller pages after this hour will result in a friendly message indicating the System Operator is not available; the caller will be given your office hours at that time. To answer a caller page (the system will beep to indicate a caller page) the System Operator should press function key F10. Note: Function keys F5 and F6 can be used later to temporarily override this office hour setting. Type of display adapter (Enhanced, Color, or Monochrome) If you wish to use an Enhanced Graphics Adapter and a color monitor connected to the adapter, enter Enhanced here. If you wish to use a color graphics adapter and a RGB color monitor connected to to the adapter, enter Color here. If you plan to use an IBM monochrome monitor connected to a monochrome display adapter, enter Monochrome here. Any monitor other than the IBM monochrome monitor is considered a color monitor by TCOMM. System Operators with prior unattended communications system experience may wish to customize TCOMM operation to meet specific communication needs beyond those addressed in the Initial Setup. You may want to establish caller access levels required to perform system functions that are different from the default profile values. You may also want to separate upload and download directories to keep callers from viewing and downloading files that have been uploaded by other callers. You may further wish to limit caller access to certain system functions. All of these changes and others can be made in the Configuration Profile as discussed in Chapter 9. CUSTOMIZING TEXT FILES Before executing TCOMM it is necessary to modify some of the system text files to meet your specific needs and to identify your system to callers. Table 2-1 shows the TCOMM files associated with each TCOMM system. Table 2-2 contains the list of files that must be modified. Table 2-3 provides the locations of each of the files listed in Table 2-2. A brief description of files listed in Table 2-3 is provided in the following paragraphs to help you decide how to modify the files. Appendix E contains 17 more information pertaining to the relationship between files and TCOMM subsystems. Most System Operators have found that it is easier to modify files with a full screen text editor such as the IBM Personal Editor than it is to modify files one line at a time with a line editor such as Edlin. If you use a text editor to customize files, store the files as "plain vanilla" ASCII text. If a word processor is used to edit the files, the final stored files should be saved on disk as print image files without printer control characters. Tabs should not be used in the files to conserve disk space because all terminals do not accept the 8- character-equivalent spacing that the IBM PC uses for tabs. The names of many of the TCOMM files are contained in the Configuration Profile and can be changed by the System Operator. Refer to Chapter 9 for more details on changing system filenames. 18 Operator Main Menu Startup Login __________________ ____________ _______ HELP AUTOEXEC.BAT WELCOME USERDATA.TC WARNING LOG.TC STATUS.TC NEWUSER PROFILE.TC PROFILE.TC COMMAND.COM Main Command Bulletin Subsystem Change Subsystem ____________ __________________ ________________ HELP PROFILE.TC HELP PROFILE.TC BULLET USERDATA.TC BULLET1 BULLET2 PROFILE.TC File Subsystem Mail Subsystem Operator Subsystem ______________ ______________ __________________ HELP HELP HELP FILES USERDATA.TC PROFILE.TC FILES1 MAILINDX.TC LOG.TC FILES99 Mx USERDATA.TC FILES99.TC STATUS.TC PROFILE.TC CALLERS.TC LOG.TC XMODEM.EXE KERMIT.EXE CRCXMODM.BAT YMODEM.BAT Smart Terminal Programs Remote ______________ _____________ ________________ HELP HELP HELP PROFILE.TC PROG USERDATA.TC PROG1 LOG.TC PROG2 COMMAND.COM Table 2-1. TCOMM files. 19 Table 2-2. Customizable files. ______________________________________________________ File Name Subsystem Use Should Be Modified ------------ ------------- ------------------ AUTOEXEC.TC All Yes TC.BAT All Optional WELCOME Login Yes WELCOME.G Login Yes NEWUSER Login Yes NEWUSER.G Login Yes PROG Programs Yes PROG1 Programs Yes FILES Files Yes FILES1 Files Yes FILES2 Files Yes HELP All Optional WARNING Login Optional BULLET Bulletins Optional BULLET1 Bulletins Optional BULLET2 Bulletins Optional FILES99 Files Optional FILES99.TC Files Optional 20 Table 2-3. Location of customizable file. ______________________________________________________ Dual Fixed File Name Diskette Disk ------------ -------- ------------------ * AUTOEXEC.TC A: C:\ (root directory) TC.BAT A: C:\TCOMM\SYSTEM WELCOME B: C:\TCOMM\TEXT WELCOME.G B: C:\TCOMM\TEXT NEWUSER B: C:\TCOMM\TEXT NEWUSER.G B: C:\TCOMM\TEXT PROG B: C:\TCOMM\PROG PROG1 B: C:\TCOMM\PROG FILES B: C:\TCOMM\FILES FILES1 B: C:\TCOMM\FILES FILES2 B: C:\TCOMM\FILES HELP B: C:\TCOMM\TEXT WARNING B: C:\TCOMM\TEXT BULLET B: C:\TCOMM\TEXT BULLET1 B: C:\TCOMM\TEXT BULLET2 B: C:\TCOMM\TEXT FILES99 B: C:\TCOMM\FILES FILES99.TC B: C:\TCOMM\FILES * note - The C fixed disk is used as an example only. Any acceptable PC-DOS drive designation can be used and must be specified in the profile. Batch Files TCOMM operation is normally invoked from a PC-DOS batch file and can be set up for automatic recovery from power failures. The following batch files should be reviewed and modified to meet your needs. TC.BAT ------- TC.BAT can be used to start TCOMM operation. This file will cause TCOMM to restart if the system fails due to configuration problems or abnormal caller activity. If the system fails, the TC.BAT file will produce bell sounds to let you know there is a problem. If you exit TCOMM after starting it using TC.BAT, you will have to hold down the Ctrl key and strike the Break (Scroll Lock) key to break the automatic restart of TCOMM. 21 AUTOEXEC.TC ------------ AUTOEXEC.TC allows you to automatically start TCOMM when the PC is powered on. It will also cause TCOMM to restart after a power failure. This file is further used to restart TCOMM if the modem carrier signal is lost during caller execution of an external program or caller exit to DOS. If you normally use an AUTOEXEC.BAT batch file, you will need to modify the AUTOEXEC.TC file to include your system startup commands. AUTOEXEC.TC should be renamed AUTOEXEC.BAT and placed on the System Work diskette or in the fixed disk root directory. For proper system restart after power failure or recovery from loss of carrier during external program execution, the PC system unit must contain a batter powered clock/calendar and the proper call to that device must be included in the AUTOEXEC.BAT. If you normally execute TCOMM from a fixed disk drive but also keep a diskette in the A diskette drive, you must take special precautions to allow the system to restart from the A drive diskette. You must format the diskette with the /S option so that the operating system files are copied to the disk. You must leave a copy of the COMMAND.COM file on the diskette. You must place a an AUTOEXEC.BAT file on the diskette and include a command at the top of the file to switch to the fixed disk before executing the normal AUTOEXEC.BAT file described in the previous paragraph. An example of the AUTOEXEC.BAT file contents for the A drive is shown as follows: C: AUTOEXEC These commands cause the system unit to switch execution from the A drive to the C fixed disk drive, then execute the normal AUTOEXEC.BAT file. This file will switch operation to the TCOMM directory and execute the TC.BAT batch file described earlier. Initial Login Files System login files are displayed for callers during the TCOMM login. These files should be reviewed and modified as necessary to reflect the TCOMM application. Graphics versions of these files can be created with a text editor such as the IBM Personal Editor. Graphics files contain the special IBM ASCII extension characters with ASCII values above 127. The graphics versions should have the letter "G" appended to the original filenames as filename extensions (e.g., WELCOME.G, NEWUSER.G, etc.). The Configuration Profile determines whether callers are allowed to view graphics files. A caller has to elect Graphics during login or at the Options menu and has to be using a full 8 data bits before these special files are displayed. 22 Graphics version of the WELCOME and NEWUSER files are included on the distribution diskette. A complete set of the IBM ASCII extension characters is provided in a distribution-diskette file called GRAPHICS. These characters can be copied to existing or new graphics files to add special effects. WELCOME ------- WELCOME is the first text file displayed when a caller dials into the system. It must be present for proper TCOMM operation, and it should be modified to identify your system. To keep the full WELCOME file displayed during caller login, the file length should be less than 21 lines. Many System Operators include a text or graphics diagram of the TCOMM system hardware in the WELCOME file. The diagram can reduce TCOMM system hardware-related questions. WELCOME.G --------- WELCOME.G is an extended ASCII (graphics) version of the WELCOME file. You may use this design to create your own graphics welcome message. WARNING -------- WARNING is a text file that warns users of the consequences of system abuse. The sample WARNING file included on the distribution diskette was written for public access systems where a strong warning is often required. Closed preregistration or private systems will not need this strong a warning. This file is displayed just before validation of the callers name and location is requested by TCOMM and should establish the ground rules for system use. The caller can re-enter a new name and location after reading this file. NEWUSER ------- NEWUSER is a text file that is displayed for new system callers just before the caller Main Command menu is presented for the first time. This should contain a friendly message about your TCOMM system and its intended purpose. 23 System Text Files The following text files are used for caller information in several subsystems. You should review each of these files and modify the ones that do not reflect your initial system operational characteristics. INFO ---- INFO is the master TCOMM system information file. Callers are allowed to view the contents of INFO by executing the Operator Command menu Description command. INFO is a convenience file for the System Operator--it reduces caller questions about the specific hardware and software supporting the TCOMM system. This file also includes TCOMM ordering information for callers that are interested in starting a TCOMM system. BULLET ------ BULLET is a bulletin menu file and is the prefix name for system bulletins. This is a text file and can be displayed in one of two ways. First, it is displayed following the WELCOME file when a user first enters the system if the System Operator has requested "forced Bulletins display" in the Configuration Profile. Second, it is displayed when a caller or the System Operator executes the Menu command at the Bulletin Command menu. The BULLET file must be present for the Bulletin Subsystem to work properly. The BULLET file provided on the distribution disk is an illustration of a typical bulletin menu file. You should create your own bulletin menu file to match your bulletin files. The bulletin menu filename can be changed from BULLET to another name in the Configuration Profile. Most System Operators organize bulletin menus and bulletins according to subject. The bulletin main menu usually tells callers how to list the other bulletin menus and bulletins. Logically, the menus and bulletins are a tree structure as shown in Figure 2-1. 24 Figure 2-1. Bulletin menu and file structure. ----------------------------------------------------------- BULLET | | ---------------------------------- | | | | | | | | BULLETaa BULLETbb ............... BULLETzz ------------------------------------------------------------- The bulletin file suffixes aa through zz can be letters or numbers. Most System Operators prefer numbers (i.e. BULLET1, BULLET2, etc.). A third level could be added to this structure containing bulletin submenus. For example, the main bulletin menu could refer to bulletin submenus 1, 2, and 3. If submenu 1 (file BULLET1 in this case) referred to bulletins 1a, 1b, and 1c, the actual bulletin filenames would be BULLET1a, BULLET1b, and BULLET1c. The only limit to the bulletin tree structure is the PC-DOS filename conventions. Filenames are limited to eight characters and cannot contain periods between letters. Dashes and underscores are allowed in filenames and can be used to designate bulletins. For example, the third level of a bulletin file tree could contain bulletins 1-a, 1-b and 1-c. This would require a bulletin filename prefix change in order to stay within the DOS eight character limit for filenames. If the bulletin filename prefix was changed to BULL, the third level bulletin files would be named BULL1-a, BULL1-b, and BULL1-c. The BULLET file provided on the distribution diskette is shown in Figure 2-2. ==================== Bulletin Menu ======= Updated ====== 1 - XMODEM protocol information 4/11/84 2 - The KERMIT file transfer protocol 4/12/84 Figure 2-2. Distribution BULLET file. BULLET1 and BULLET2 ------------------- BULLET1 and BULLET2 are the two bulletins referenced in the BULLET file. These are examples of bulletin files that have numbers as designators. You may choose to use letters to designate bulletins rather than numbers. Each bulletin filename should begin with the same name as the bulletin menu file--the 25 name chosen in the Configuration Profile as a bulletin filename prefix. Bulletin filenames should end with the letters or numbers shown in the bulletin menu file. The two bulletin files provided with TCOMM are the same as appendices A and B. These two bulletins help to explain the Xmodem and Kermit file transfer protocols provided with TCOMM. You may want to leave these two bulletins in your system and add new bulletins to the the list. PROG ---- PROG is the Programs Subsystem main menu file and is the prefix name for Programs Subsystem program menus. This is a text file and can be displayed in one of two ways. First, it is displayed following execution of the Menu command in the Programs Subsystem. Second, it is displayed when the List command is executed in the Programs Subsystem followed by a carriage return. The PROG file must be present for the Bulletin Subsystem to work properly. The PROG file provided on the distribution disk is an illustration of a typical programs main menu file. You should create your own programs main menu file to match your executable external program menus. The programs main menu filename can be changed from PROG to another name in the Configuration Profile. Most System Operators organize the menus of externally executable programs according to program type. The main program menu usually tells callers how to list the other menus. Logically, the menus are a tree structure as shown in Figure 2-3. Figure 2-3. Programs menu structure. ----------------------------------------------------------- PROG | | ---------------------------------- | | | | | | | | PROGaa PROGbb ................. PROGzz ------------------------------------------------------------- The suffixes aa through zz can be letters or numbers. Most System Operators prefer numbers (i.e. PROG1, PROG2, etc.). The PROG file contained on the TCOMM distribution diskette is shown in Figure 2-4. If you wish to add more executable programs to the system at this time, you should modify this file. 26 ========= Remotely Executable Programs ======== Menu Program Functions ------ -------------------------- 1 Disk directory sort Figure 2-4. Distribution PROG file. PROG1 ----- PROG1 is the program menu referenced in the PROG file. This is an example of a programs menu that has a number as a designator. You may choose to use letters to designate menus rather than numbers. Each programs menu filename should begin with the same name as the programs main menu file--the name chosen in the Configuration Profile as a programs menu filename prefix. Programs menu filenames should end with the letters or numbers shown in the programs main menu file. The programs menu files contain the names of programs that callers are allowed to execute. Each filename of a program should be followed by a brief description of the program. Figure 2-5 shows the contents of the PROG1 file that is provided with TCOMM. If you wish to add more programs to this menu, PROG1 should be modified. Figure 2-6 shows a typical programs menu used in software sales. ============= Program Menu 1 ============= Program Program Function ------ ----------------------- SD Sorted disk directory Figure 2-5. Distribution PROG1 file. -----======= Executable Programs Menu x ========----- Program name Program description ------------ -------------------------------------- PRODUCTS List of available products and prices ORDER Order software listed by PRODUCTS DEMO Demonstration of software product 1 SURVEY Survey of caller interests Figure 2-6. Software sales program menu. 27 You should note that the program menus do not list the filename extensions of the executable programs. TCOMM executes external programs using the same conventions as PC-DOS. Any directly executable program including batch files can be executed from a remote terminal. The system allows the caller to enter up to 40 characters on the program execution command line. The only characters that are not allowed are disk drive and subdirectory designations to keep callers from executing files not made available for them and file output redirection to keep callers from overwriting existing files in the program disk area. FILES ----- FILES is the name of the file download master menu and the prefix filename for download file menus. FILES contains the names or numbers of the download menus. The download menu names use the FILES prefix with letters or numbers appended to match the menu letter or number scheme shown in the FILES file. At least one FILES file must be present on one of the diskettes available for downloading for proper system operation. A file menu is a text file that the System Operator creates to describe files available for downloading. The file contains a one-line entry for each file available for downloading. The System Operator should use a full screen text editor such as the IBM Personal Editor to create file menus. Most System Operators use the following format for file data: filename extension bytes date - description An example of this format is shown in Figure 2-7. The file menu format shows the name, size, date and description for each file available for downloading. -----===== Download Menu 1 =====----- Filename Size Date File description ----------- ----- ------- --------------------------- SD COM 1536 2/15/85 - Sorts file directory LIBRARY EXE 26367 1/25/85 - Source code library program SQ EXE 32678 3/12/85 - Squeezes files and programs Figure 2-7. Sample file menu. The download menu file conventions are as follows: 28 o The file menus must be text files created by the System Operator using a text editor and stored without tab substitution for blank spaces. For example, the IBM Personal Editor command used to store the download menu shown above is: save FILES1 notabs o The file menus filenames must begin with the download menu filename prefix designated in the Configuration Profile. The default download file menu filename prefix is FILES. o There is only one file menu for public uploads and it must be on the disk drive designated for uploads. o There is only one file menu for private uploads and it must be on the disk drive designated for uploads. Most System Operators organize file menus according to subject. The primary file menu usually tells callers how to list the other menus. Logically, the menus are a tree structure as shown in Figure 2-8. Figure 2-8. File menu structure. ----------------------------------------------------------- FILES | | ---------------------------------- | | | | | | | | FILESaa FILESbb ................. FILESzz ------------------------------------------------------------- The suffixes aa through zz can be letters or numbers. Most System Operators prefer numbers (i.e. FILES1, FILES2, etc.). Figure 2-9 shows the contents of the FILES menu file distributed with TCOMM. Figure 2-10 shows the contents of the FILES1 menu file referenced in FILES. You may want to leave the bulletins shown in these files available for callers to help them understand the Xmodem and Kermit file transfer protocols. If you wish to add more file menus to the system at this time, be sure to list the additional menus in the FILES master download menu. 29 =================== Download Master Menu =========================== Menu Type of Files Menu Type of Files ---- -------------------------- ---- ------------------------ 1 TCOMM Bulletin files 99 Uploaded files Figure 2-9. Distribution FILES file. ======================== File Menu 1 ============================= Filename Size Date File description ------------- ----- ------- -------------------------------- BULLET 170 2-05-85 - Master Bulletin directory BULLET1 10008 1-02-85 - XMODEM protocol information BULLET2 13971 1-20-85 - The KERMIT file transfer protocol Figure 2-10. Distribution FILES1 file. FILES99 ------- FILES99 is the file on the upload disk that will contain public uploaded file information. During system operation this file will contain the name, size, upload date, and a description of each file received by TCOMM. This information is appended to the end of FILES99 by TCOMM as each file is uploaded, unless the caller designates the file as private when TCOMM asks for a description of the file. By using the filename FILES99, the System Operator can easily allow callers to list the upload menu. If callers are allowed to download files that have been recently uploaded, they can get the upload list by requesting download menu 99. The number 99 is appended to FILES by TCOMM and file FILES99 is displayed. You should have no need to modify this upload file menu at this time unless you wish to add a date to the first line of the file to indicate the date the system was first started. As you receive upload files you will want to use a full screen text editor to move the file records from the upload menu to a regular download menu. By using a full screen editor to move the records, you can mark and move an entire line at a time. TCOMM System Operators have also written utility programs that allow you to move these upload records to specific download menus. More information can be obtained regarding these utilities by calling the TCOMM support center listed in Chapter 14. FILES99.TC ---------- FILES99.TC is the upload menu for private upload files. This file can only be viewed or downloaded by the System Operator and 30 callers with System Operator privileges. It will contain the same kind of upload file information contained in FILES99 and is updated by TCOMM after each private upload file is sent to the system. Callers may elect this upload menu by entering an '*' as the first letter of the upload file description. The private upload menu should be given a filename extension of 'TC' to keep callers from accessing the file. TCOMM will not allow callers with access privileges lower than the System Operator to list or download files that have 'TC' filename extensions. You should have no need to modify this private upload menu at this time except to add an initial startup date to the first line of the file. TCOMM STARTUP In order to start up TCOMM, the following procedures should be completed for your specific hardware configuration: Two Dual-sided Diskette Drives The TCOMM program and its profile settings are located on the System Work diskette in diskette drive A. Change the default diskette drive designation to A if it is not already set to A. Type the command TCOMM and press ENTER to start the TCOMM program. One Fixed Disk Drive and One Diskette The TCOMM program and its profile settings are located on the TCOMM\SYSTEM subdirectory. Change the default drive to this subdirectory. Type the command TCOMM and press ENTER to start the TCOMM program. 31 Chapter 3. Local System Controls TCOMM provides the System Operator with two local methods of system control. The Function Key Controls are used to dynamically change TCOMM operational characteristics during operation, and the Operator Main Menu used to locally operate TCOMM. FUNCTION KEY CONTROLS Most of the TCOMM Function Key Controls may be used at any time during TCOMM operation. The function keys that only work when no one is currently dialed into the system are discussed later. When a function key is pressed, the new status of that key is displayed at the bottom of the screen. Because of space limitations on the 25th line of the display, only the recent function key status change is displayed. Function Key Menu If the System Operator has configured the system for display of caller activity, the Function Key Control menu shown in Figure 3- 1 will appear each time TCOMM is started and after each caller ends a session. This menu will clear after a short period to prevent screen damage caused by prolonged display of the same image. This screen clear is done with a standard PC-DOS function and will not harm your display adapter or monitor. The function key menu can be refreshed at any time by pressing any key. The function key menu can only be displayed after local user access or remote caller login by pressing the HOME key. Figure 3-1. Function Key Control Menu -------------------------------------------------- Exit system and return to DOS Go to Operator Main Menu Toggle printing of activities on/off Enter Terminal Mode Toggle Operator available all day on/off Toggle Operator available hours on/off Operator gets system after this caller Give caller Operator privileges Toggle local display on/off Force system into chat mode End chat mode Display this Function Key menu This display will clear soon to prevent burn-in -------------------------------------------------- 32 If the System Operator has turned off local caller activity display in the Configuration Profile, the Function Key Control menu will not be displayed while the system is waiting for a caller to dial in. The function key menu will be displayed if a key is pressed while the system is waiting for a caller. The HOME key can also be used to display the Function Key menu when caller activity is being displayed, except during keyboard chats with callers. If this menu is displayed while a caller is on-line, the menu will clear when the local System Operator or the caller presses a key. Function Key Action Some function keys are not operational during certain phases of TCOMM operation. Function key response takes place when TCOMM checks the keyboard for System Operator activity. Response may not be immediate because TCOMM is optimized for response to caller requests. These special circumstances and the actions caused by each function key are discussed in the following paragraphs. F1 -- Exit system and return to PC-DOS Function key F1 allows easy exit to the disk operating system. The System Operator may wish to exit TCOMM to perform other work and F1 provides this opportunity. The System Operator is asked to confirm this request before TCOMM exits to PC-DOS. The F1 key does not work after the F2 key has been pressed for local TCOMM access. The F1 key is only operational when no one is using the system either locally or remotely. If a remote caller is using the system, the local System Operator must use the F2 key to achieve system access. If the local System Operator has pressed the F2 key to achieve system access, then exit to PC-DOS can be achieved by executing the Exit command at the Operator Main Menu described later in this chapter. F2 -- Go to Operator Main Menu F2 allows the System Operator or a user to locally operate the system. If a user is on-line through a modem connection when you press F2, TCOMM will indicate that local access will drop the caller from the system and ask if you wish to drop the current caller. If no caller is on-line or you elect to drop the current caller, TCOMM will present a request for the System Operator password. If you press ENTER at the System Operator password prompt, you will be given immediate access to the system in caller mode. You will be allowed to login and execute only those system commands you are normally allowed to execute as a remote caller. This mode of access can be used by local Assistant System Operators who 33 have been given high access levels at the User Data Base Maintenance Menu. It can also be used for local user access to the mail system for message exchange with remote callers. If you enter the local System Operator password at the prompt, you will be given immediate access to the Operator Main Menu. The System Operator password is contained in the TCOMM Configuration Profile. The distribution disk contains the default password 'TC' which should be changed to a new password during initial system configuration. During local access, TCOMM keeps the modem in the offhook state. Callers will get a busy telephone signal during this period. Without this busy signal, callers would assume the system is inoperable. With the busy signal, callers will assume someone else is on the system and call back later. The modem is returned to the onhook state when local access is ended. The F2 control should be used before callers are allowed to access the system for the first time. The System Operator should go to the Operator Main Menu then to the Configuration Profile to be sure the system is configured properly. The System Operator should also execute the Local command from the Operator Main Menu followed by execution of caller menu commands to be sure the system operates properly in the local access mode. To fully test the system from the caller perspective, the System Operator may want to execute F2 and press ENTER followed by a login using a caller's name, data and password. This last method will allow a review of all login welcome, warning and newuser files that callers will see. F3 -- Toggle printing of activities on/off F3 causes the system to either start or stop printing caller activities. The Configuration Profile that is supplied on the distribution diskette sets this function to Printer Off to eliminate initial startup problems. The F3 key should not be used to toggle the printer on unless the printer has been turned on and sufficient paper is available to print caller activities. The caller activities that will be printed are file uploads, file downloads, and system errors caused by caller actions. Before activating the printer, be sure the printer contains sufficient paper and that the printer is in the online state. Improper operation of the printer could cause performance problems for TCOMM. F4 -- Enter Terminal Mode F4 provides direct access to the TCOMM Terminal Mode. The System Operator can use this mode to make calls to other computers or to test the modem. A full description of this mode is contained in Chapter 6. 34 F5 -- Toggle Operator available all day on/off F5 changes the System Operator availability hours designated in the Configuration Profile. F5 changes Operator availability from specific office hours to all day. When F5 is set to on, TCOMM allows callers to page the System Operator for a greater part of the day than normal. This function is useful for increasing System Operator availability during weekends. Pressing F5 a second time will return System Operator availability to normal office hours. F6 -- Toggle Operator available hours on/off F6 turns System Operator availability on and off. When F6 is set to on, callers are allowed to page the System Operator during the office hours selected in the Configuration Profile or during any part of the day if F5 has been set to on. When F5 and F6 are both set to off, callers are not allowed to page the System Operator during any part of the day. F7 -- Operator gets system after this caller F7 allows the System Operator to reserve the system for local use after the current caller logs off. As soon as the current caller logs off, TCOMM will ask for the local System Operator password. The System Operator will have to enter the correct password before being given access to the Operator Main Menu. When the System Operator finishes local system operation, TCOMM will recycle and wait for the next caller. F8 -- Give caller Operator privileges F8 allows the System Operator to give a caller temporary System Operator access privileges. This function is necessary when a user is on-line and needs special access control for a short period of time. These special privileges end when the caller logs off the system or the System Operator presses F8 again. F9 -- Toggle local display on/off F9 turns local caller activity display on and off. The local display default condition is selected in the Configuration Profile, but F9 allows the System Operator to override this setting. The override remains in effect until the System Operator resets F9 or exits the system. If the System Operator has turned off local display in the Configuration Profile, TCOMM will only display one screen of information during initial startup. The function key menu will 35 not be displayed unless the HOME key is pressed or local display is toggled back on using the F9 key. F10 -- Force system into chat mode F10 is only operational when a caller is on-line; it allows the System Operator to force the system into a keyboard chat mode. The System Operator can force the system into the chat mode at any time except during a file transfer. F10 should also be used to answer an Operator page. When F10 is pressed, the caller is informed that the System Operator is breaking in for a chat. After F10 is pressed, the System Operator and the caller can carry on a conversation. When the conversation is finished, the System Operator must press the ESC key to return the system to normal operation. ESC -- End chat mode The ESC key is used to end a keyboard chat between the System Operator and a caller. TCOMM resumes operation at the point the F10 key was pressed to enter the chat mode. HOME - Display this Function Key menu The HOME key is used to display the Function Key Control menu. This key will result in display of the Function Key menu any time except during keyboard chats with callers. If the HOME key is pressed while a caller is on-line, the Function Key menu will be cleared when the System Operator or the caller presses a key. If there is no activity on the system, the menu will clear in four minutes to prevent screen damage caused by prolonged display of a single image. OPERATOR MAIN MENU The Operator Main Menu is used for system configuration and maintenance. It should be used during initial system setup to confirm or change default system settings. It should be used later to alter the system configuration or to modify system files. The Operator Main Menu is shown in Figure 3-2. 36 Figure 3-2. Operator Main Menu. -------------------------------------------------------- --==== Operator Main Menu ====-- A - Activity log display C - Configuration Profile D - Delete activity log E - Exit to DOS K - Kill all old messages L - Local system access M - Maintain User Data Base O - Operating system commands P - Pack user data base R - Remove deleted users T - Terminal mode U - Unattended mode H - Help Command: -------------------------------------------------------- System Operator Password Before you are allowed access to the Operator Main Menu you are prompted for a System Operator password. This password is used to prevent unauthorized local TCOMM access. After properly responding to the password request, you are given full access to the Operator Main Menu, and you are allowed to execute all Operator Main Menu commands. The default System Operator access password is 'TC' when the system is first installed. This password should be changed in the Configuration Profile to ensure system security. Operator Main Menu Commands The System Operator executes Main Menu commands by typing a letter and pressing ENTER. Each Operator Main Menu command is discussed in the following paragraphs. A - Activity log display The Activity command displays caller activity and system error records. A record of each file downloaded from the system and uploaded to the system is displayed including the date and time and the protocol used. A record of each system error is displayed including a description of the error. A record of each attempted security violation is also displayed. The file displayed with this command is the system activity log file designated in the Configuration Profile. A description of each error message that 37 may appear in this file is shown in Appendix C. C - Configuration Profile The Configuration Profile command provides access to the system default settings. This allows the System Operator to change system filenames and disk drive designations. It also allows customization for special operational needs. This Profile should be accessed when a new system is set up to confirm settings. A detailed discussion of the Configuration Profile is provided in Chapter 9. D - Delete activity log The Delete command lets the System Operator delete the system activity log without exiting to PC-DOS. The activity log increases in size without limit as the system is used and must be periodically deleted. After reviewing the file using the Activity log command, the file should be deleted. If the log file is not periodically deleted, the active system file disk drive will fill up and TCOMM will malfunction. E - Exit to DOS The Exit command allows the System Operator to temporarily return to DOS. TCOMM will request confirmation before executing this command. All temporary Function Key Control settings are cleared when this command is executed and the system exits to DOS. If the System Operator has not elected to leave the telephone line off hook when returning to DOS, the modem will be reset to factory default conditions when the Exit command is executed. The telephone line should only be left off hook if the line is dedicated to TCOMM operation, and the System Operator wants callers to get a busy signal when the system is being used for applications other than TCOMM. K - Kill all old messages The Kill command causes TCOMM to purge all messages that have been on the system longer than the period selected in the Configuration Profile. The default period established during TCOMM installation is 3 months. If you want to keep old messages a longer period or a shorter period than 3 months, you should modify this value in the Configuration Profile. 38 L - Local system access The Local system access command allows the System Operator to access the system caller menus. After local access is achieved, the System Operator can perform most TCOMM functions that callers are allowed to perform. The System Operator is given the system access control level designated in the Configuration Profile. This access level gives the System Operator special message and file access privileges. These special privileges are discussed in Chapter 4. To return to the Operator Main Menu from local system access, the System Operator must execute the Logoff command at the caller main menu. The function key F1 cannot be used to exit from the local access mode because several open files cannot be properly closed until the Logoff command is executed. M - Maintain User Data Base The Maintain command provides access to the User Data Base Maintenance Menu. A full screen data base control system is executed from within TCOMM. This system allows the addition of new users or the modification of user data. The data base menu is discussed in Chapter 7. O - Operating system commands The Operating system commands allow the System Operator to execute any DOS command or execute any program or batch file located on a diskette or on a fixed disk. The System Operator can change default drives or directories before executing a command. The System Operator must execute the EXIT command to return to TCOMM operation after executing the Operating system command. TCOMM automatically returns to the System Work diskette or the TCOMM\SYSTEM subdirectory as designated in the Configuration Profile prior to restarting. The Operating system command allow the System Operator to load a text editor and edit system text files. The command can also be used to list files in a drive or directory. Files can be deleted or copied to other locations. The command also allows the System Operator to format new diskettes to be used for file uploading. TCOMM is still resident in memory during this temporary exit to DOS and consumes approximately 180 Kbytes or random access memory. This reduction in available memory may prevent you from executing some external software or may reduce the work space for your text editor. The Operating system command requires that the PC-DOS command processor, COMMAND.COM, reside on the A drive of a diskette system or in the system directory (TCOMM\SYSTEM) of a fixed-disk system. The Operating system command first loads COMMAND.COM, then gives command control to the System Operator. Any error 39 messages produced by command execution after the Operating system command is executed are the same as PC-DOS error messages and are not documented in this manual. The System Operator must return to TCOMM by typing EXIT and pressing return when the temporary exit to DOS is completed. Failure to perform this function will reduce the memory available for other software execution. Starting TCOMM again without EXITing the previous return to DOS could result in improper operation of the TCOMM file transfer protocols caused by insufficient free memory. P - Pack User Data Base The Pack command causes TCOMM to pack the user data base by removing inactive users. Users that have not been on the system within the allowed inactivity period established in the Configuration Profile are removed from the data base. This operation reduces the data base contents to active system users and speeds up the caller login sequence. Users eliminated during this pack operation may be added back to the data base later. This command is normally used once a month for open access systems that are not configured for automatic data base pack. Note: Users that have been marked for system lockout are not removed from the data base unless their status is changed to deleted before the Pack operation is initiated. If the System Operator has elected in the Configuration Profile to keep a backup copy of the user data base during pack operations, TCOMM creates a backup copy of the data base before the pack is executed. The backup file has the filename extension 'BAK'. R - Remove deleted users The Remove command causes TCOMM to purge users that have been marked for deletion in the user data base. Until this action is performed, the System Operator is free to delete and undelete users at the User Data Base Maintenance Menu without causing the actual contents of the data base to change. This command is often used with closed systems to eliminate callers that are no longer allowed system access. For example, an employee that terminates from a company would have to be deleted from the company TCOMM communication system data base to keep the person from continuing to access sensitive company information. Note: Users that have been marked for system lockout are not removed from the data base unless their status is changed to deleted (access level is changed to the letter 'D') before the elimination operation is initiated. 40 If the System Operator has elected in the Configuration Profile to keep a backup copy of the user data base during pack operations, TCOMM creates a backup copy of the data base before the pack is executed. The backup file has the filename extension 'BAK'. T - Terminal mode The Terminal command allows the System Operator to execute a smart terminal communications program from within TCOMM. When the communications session is completed, operation will return to the Operator Main Menu. The name of the smart terminal program to be executed must be designated in the Configuration Profile. The default terminal program name is TC-TERM (this program is supplied as part of TCOMM), but any smart terminal program can be selected. The selected program must reside on the TCOMM System Work diskette or in the TCOMM\SYSTEM subdirectory, unless a drive or directory prefix is supplied with the terminal program filename in the Configuration Profile. The capabilities and characteristics of TC-TERM are discussed in Chapter 6. If your external smart terminal software does not execute properly when activated from within TCOMM, you may need to reset the modem to factory default operating parameters. This can be done by turning the modem off, then turning it back on. You can also reset Hayes compatible modems to factory default settings by sending the proper AT commands to the modem (i.e., ATZ or AT&F for Hayes Smartmodems). U - Unattended mode The Unattended command returns TCOMM to the unattended mode of operation. The Function Key Control menu will be displayed if the local display is set to on; TCOMM will then wait for a caller. Failure to execute this command will prevent TCOMM from answering incoming calls. H - Help The Help command displays a help file containing a brief description of each Operator Main Menu command. 41 Chapter 4. System Operator Access The System Operator can access TCOMM locally or remotely. Local access allows the System Operator to perform all maintenance functions and most caller functions. Remote access allows the System Operator to perform all caller functions and most maintenance functions. Local and remote System Operator access also allows the Operator to execute commands normal users are not allowed to perform. Both local and remote access is password protected to enhance the security and integrity of the system. Callers that are given System Operator privileges are allowed to perform most of the remote System Operator functions. System Operator Passwords Passwords control both local and remote System Operator access. If function control key F2 is pressed, TCOMM immediately requests a System Operator local password. If function control key F7 is pressed, TCOMM requests the System Operator local password after the current caller logs off the system. By typing the correct password and pressing ENTER, the operator is given access to the Operator Main Menu. By selecting Maintenance at the Operator Main Menu, the System Operator can perform all user data base editing and maintenance tasks. By selecting Configuration Profile, the System Operator can access and modify the TCOMM operating characteristics. The System Operator can also modify the Operator access passwords in the profile and should do so on a periodic basis. The System Operator can dial into TCOMM from a remote terminal or computer but must use a code name in place of caller first and last name. By using these special configuration profile code names, the System Operator is given special remote system control. Any attempt to use the real System Operator first and last name from a remote location will result in immediate session termination. This feature helps prevent system abuse by remote callers. Callers who have been given System Operator privileges in the user data base do not use a special name to access the system. These callers use their real names and the passwords they have selected. TCOMM assigns them special privileges after finding their records in the user data base. System Operator privileges should be given out sparingly because abuse of the system by one of these callers could create a great deal of confusion. 42 System Operator Privileges From the local Operator Main Menu, the System Operator can access all menus used by remote callers. By selecting local system access at the Operator Menu, the System Operator is given a direct path into TCOMM that is an abbreviated version of a normal login sequence. After a display of system status, the System Operator is given the caller Main Command menu. From this menu the System Operator can access all caller related subsystems. When dialing in from a remote location, the System Operator can access all caller menus. After TCOMM recognizes the System Operator's special names during the login process, the system bypasses all login message files and the Bulletin Subsystem. TCOMM displays system status, then passes System Operator control to the caller Main Command menu. The System Operator cannot access the full screen Operator Main Menu from this menu, but all functionality of the Operator Main Menu is provided at a special Remote Command menu that will be discussed later in this chapter. Regardless of the method of entry, TCOMM gives the System Operator special control privileges. These privileges differ, however, depending upon the access method as discussed in the following paragraphs. Refer to the Caller Menu section of Chapter 5 for a discussion of the caller menu commands available to the System Operator. System Operator Message Privileges Callers are normally allowed to read only public messages and private messages directed to them. Callers are also allowed only to delete messages they direct to others and private mail directed to them. The System Operator has to have greater privileges than those given to other callers in order to monitor the system for improper caller activity and to perform mail maintenance. To accomplish this, TCOMM allows the local System Operator or callers with System Operator privileges to read all public and private messages in the Mail Subsystem regardless of group designation. System Operator privileges also include the ability to delete any message regardless of the sender or recipient. Finally, System Operator status allows the local or remote user to modify message status; private messages can be made public and public messages can be made private. The special commands that appear on the caller menus that allow these functions to be performed are documented in Chapter 5. System Operator File Privileges The System Operator can perform all File Subsystem functions, but certain functions are limited to remote access. A remote System Operator can download any file available on the download disk drives, including the TCOMM system files that have the 'TC' filename extension. As a security measure, normal callers are 43 not allowed to download these system files. A local System Operator can perform file download functions at the keyboard, but downloads are limited to the ASCII text file mode. This technique is used to review ASCII files. A remote System Operator can upload any file. If the file already exists, a warning is provided and the System Operator is allowed to abort the file upload. Unlike normal callers, however, the System Operator is allowed to overwrite existing files, including TCOMM system files. System Operator Remote Maintenance The System Operator is given a special command at the Operator Command menu called Remote. This command only appears if the caller is the System Operator or has System Operator privileges. This command provides access to the Remote Subsystem. The caller must provide the Operator access password before this subsystem menu is displayed. The password is the same as that required for local system access and is 'TC' in the default Configuration Profile. This password should be changed to another word or letter-character combination to enhance security. The Remote Subsystem allows the System Operator to perform most of the functions included in the local Operator Main Menu. The activity log can be displayed and deleted. The data base can be packed to remove deleted and inactive users. A line-at-a-time TTY style data base maintenance menu can also be executed. Users can be added and deleted and user records can be modified. This menu also allows the caller to exit to PC-DOS unless the System Operator has prohibited this capability in the Configuration Profile. After exiting to PC-DOS, the caller can execute any PC- DOS command or execute any program that writes screen output using BIOS or PC-DOS calls (IBM calls these programs "well behaved"). A detailed discussion of each remote caller command is provided in Chapter 5. The actions performed by these commands that pertain to remote and local System Operator access are explored. 44 Chapter 5 Unattended System Operation The TCOMM unattended mode of operation automates many communication functions a person can perform at the PC keyboard. The system not only eliminates the need for a full-time local communications operator, it provides a structured and predictable environment to support the information needs of remote callers. WAITING FOR A CALL After TCOMM is started, the software interacts with the system modem to prepare for a remote caller. TCOMM invokes the modem controls designated in the Configuration Profile, then waits for a caller to dial-in. When a call does come into the system, TCOMM senses the modem ring indicate signal and forces the modem to answer the call. The modem is not left in an autoanswer mode because it could answer a call before TCOMM is ready to respond. DETECTING CALLER PARAMETERS After answering a telephone call from a remote modem, the TCOMM system modem establishes a carrier signal with the remote modem. When this "locking-in" process is completed, TCOMM automatically senses the speed of the caller's modem and switches operating speed to match. TCOMM can switch from 300 bits per second to as high as 9600 bits per second if the modem used with TCOMM is fully Hayes compatible--the modem must send the PC the connection data rate immediately after the carrier signal is established. If the locking-in process is not completed within 30 seconds after a call is received, TCOMM assumes the call was not made by a remote modem and recycles to wait for another call. This action also prevents autodial modems from monopolizing the telephone line if the software that drives them has not been properly programmed. If the locking-in process is properly completed, TCOMM sends the caller a welcome message then waits for carriage returns from the remote computer. TCOMM switches parity to match the remote system's parameters when it receives this carriage return. When this matching process is completed, TCOMM begins interaction with the remote caller. The first interaction is the display of the TCOMM version number and a list of the caller's communication parameters. The parameters are displayed to help callers understand the communications process. Later, file transfer information will relate to this information. 45 If the System Operator has elected to provide graphics text files for callers, TCOMM displays the following input prompt next: Is ' ' the number one (Y/N/Why)? where ' ' is the ASCII character equivalent to the number one with the high bit set to one. If the caller's terminal cannot display the special PC-DOS or MS-DOS ASCII characters (ASCII values 128-255), the high bit will be stripped off, and the number one will be displayed. If the caller answers no to this prompt, TCOMM will use graphics versions of system text files if they are available. If the caller answers yes, TCOMM will display normal system text files. If the System Operator has elected to display input data field widths when caller input is requested, the system displays the following input prompt next: _ Is your cursor directly under the dash at the right (Y/N/Why)? If the caller answers yes, TCOMM will display dots to indicate data field widths when input fields are more than one character wide. The caller's cursor will be moved back to the first dot of each field to indicate the data input starting point. If the caller answers no to this prompt, TCOMM assumes the caller's display does not support cursor left control and will not provide data field width indicators. If the field width is critical, TCOMM will provide a dashed line above the input field to show its width. THE WELCOME MESSAGE TCOMM next presents each caller with the contents of the welcome file. This file can be text or a combination of text and graphics and is developed by the System Operator. Many System Operators include a diagram of their computer system in the welcome message so callers have a feel for the TCOMM system. For public access systems, this type of graphic depiction of the TCOMM computer can eliminate many caller questions about hardware. Sample text and graphics welcome messages are supplied on the TCOMM distribution diskette. CALLER LOGIN TCOMM starts a login procedure after displaying the welcome file. The caller is asked to enter identification information (normally a first and last name). When the caller has successfully entered this information, TCOMM searches the user database for its occurrence. TCOMM stops the search when the caller's record is found in the user data base. The system then asks for a password. If the password entered by the caller matches the user 46 password retrieved from the data base, the system proceeds to the next caller input request. If TCOMM does not find a match with the caller identification information in the user data base, the system assumes the caller has never dialed in before and requests additional information. The additional information requested is determined by the System Operator in the Configuration Profile. Three fields of data can be requested and can be customized for each TCOMM application. The Warning Display When a new user logs into TCOMM, the system displays a file called WARNING before asking for caller confirmation of entered data. This file should contain caller login and system operation rules. Display of this file before the caller data confirmation request gives the caller an opportunity to reconsider the consequences of entering faulty data. A sample WARNING file is included on the TCOMM distribution diskette. Password Request The system next requests a password that will be used for identification during future calls. After confirming the password, TCOMM creates a new record in the user data base and stores the requested information. Along with the information provided by the caller, TCOMM stores caller default security access obtained from the Configuration Profile. TCOMM will invoke this stored data each time the caller logs into the system. Optional Bulletins Menu If the System Operator elects in the Configuration Profile to force all callers to view the Bulletin Subsystem menu, all callers go to this menu after a successful login. If callers are not forced to view the Bulletin menu, they bypass the Bulletin Subsystem. Mail Check The next item in the TCOMM login sequence is a mail check. TCOMM searches the Mail Subsystem message index and informs the caller if he or she has mail waiting. This mail scan locates both public and private mail directed to the current caller. The message number and the group associated with the message is displayed for each message waiting. When the System Operator executes the Local access command at the Operator Main Menu, local access begins with this mail check. The mail check is also executed immediately after TCOMM 47 recognizes the System Operator's password when the System Operator dials in from a remote terminal. System Statistics Display If the System Operator elects in the Configuration Profile to allow callers to view system operational data, TCOMM displays current system data next. This display shows total system callers, last message number left by a caller, the last message read by the current caller, and the total number of active messages. System Operators of open access public systems usually activate this display. When the mail status report and statistics display are completed, TCOMM pauses while the caller reads the report. When the caller signals TCOMM to continue by pressing ENTER, the system presents the caller Main Command menu. 48 Chapter 6. Smart Terminal Operation TCOMM contains a terminal mode that allows the System Operator to interact with the system modem or a remote computer. The System Operator can use the TC-TERM program supplied as part of TCOMM or select any other smart terminal program. If a smart terminal program other than TC-TERM is to be used, the program name must be designated in the Configuration Profile. TC-TERM is not designed to be a robust smart terminal communications system. It is normally used to test the system modem to be sure it is working properly or to perform simple keyboard interaction with another computer. For a full-featured smart terminal communications, a package such as PC-TALK, ProComm, Crosstalk, or Smartcom should be considered. TC-TERM allows the System Operator to change communication parameters, control local character echo, interact with a remote computer or a local modem through a serial port or hangup the telephone. These and other TC-TERM terminal features are discussed in the following paragraphs. GETTING TO THE TERMINAL MENU The System Operator can access the terminal program in two ways. Before a caller comes on-line, function key F4 will cause TCOMM to go directly to the terminal program. The System Operator can also access the program by selecting Terminal Mode at the Operator Main Menu. Regardless of the method of access, the Smart Terminal Menu shown in Figure 6-1 is displayed. --=== Smart Terminal Menu ===-- H - Hangup telephone I - Interactive terminal mode L - Local echo toggle on/off P - Parameters change Q - Quit Terminal mode ? - Help Command: Figure 6-1. Smart Terminal Menu. The Smart Terminal Menu help file is shown in Figure 6-2. Each Terminal command is discussed in the following paragraphs. 49 ------========== Smart Terminal Menu Help ===========------ H - Hangup telephone and drop modem carrier signal I - Interactive terminal conversation mode L - toggle Local echo of keyboard characters on or off P - Parameter change -- port, speed, parity, and data bits Q - Quit Terminal mode and return to previous menu Figure 6-2. Smart Terminal Menu help. SMART TERMINAL COMMANDS The Smart Terminal Menu commands are executed by typing the first letter of the command and pressing ENTER. Each command is discussed in the following paragraphs. H -- The Hangup command causes TC-TERM to drop the modem carrier signal and hang up the modem telephone. I -- The Interactive command causes TC-TERM to go into an interactive conversation mode. All System Operator keyboard input except the ESC key will be sent out the selected serial communications port after this command is executed. The ESC key will cause TC-TERM to return to the Smart Terminal Menu. The default serial port is the same as the one selected for TCOMM in the Configuration Profile. To select a different serial port, execute the Parameters command. L -- The Local echo toggle allows the System Operator to control the local display of keyboard input during the interactive conversation mode. If two characters are being displayed or no characters are being displayed on the monitor with each keystroke, the Local echo command should be executed. P -- The Parameter change command allows the System Operator to change communication ports and parameters. The Parameters Menu is discussed later. Q -- The Quit command allows the System Operator to return to TCOMM. If the Function Key menu was used to access the TC-TERM, the Quit command will return the System Operator to the Function Key menu. If the Operator Main Menu was used to access the TERM, the Quit command will return the System Operator to the Operator Main Menu. 50 COMMUNICATION PARAMETERS TERM communication parameters are changed by executing the Parameters command at the Smart Terminal Menu. The Parameters Menu displayed when this command is executed is shown in Figure 6-3. The Parameters Menu help file is shown in Figure 6-4. The Parameter Menu commands are discussed in the following paragraphs. ----------------------------------------------------- --=== Parameters Menu ===-- 1 - 300,N,8,1 2 - 300,E,7,1 3 - 1200,N,8,1 4 - 1200,E,7,1 5 - 2400,N,8,1 6 - 2400,E,8,1 7 - 9600,N,7,1 8 - 9600,E,7,1 A - select port COM1: B - select port COM2: ? - Help Q - Quit to terminal menu Present Parameters: Command: --------------------------------------------------------- Figure 6-3. Parameters menu. 51 ---------------------------------------------------------------- -------========= Communication Parameters Help ===========------ 1 - 300 bps, No parity, 8 data bits, 1 stop bit ( 300,N,8,1 ) 2 - 300 bps, Even parity, 7 data bits, 1 stop bit ( 300,E,7,1 ) 3 - 1200 bps, No parity, 8 data bits, 1 stop bit ( 1200,N,8,1 ) 4 - 1200 bps, Even parity, 7 data bits, 1 stop bit ( 1200,E,7,1 ) 5 - 2400 bps, No parity, 8 data bits, 1 stop bit ( 2400,N,8,1 ) 6 - 2400 bps, Even parity, 7 data bits, 1 stop bit ( 2400,E,7,1 ) 7 - 9600 bps, No parity, 8 data bits, 1 stop bit ( 9600,N,8,1 ) 8 - 9600 bps, Even parity, 7 data bits, 1 stop bit ( 9600,E,7,1 ) A - Serial port COM1: B - Serial port COM2: Q - Quit to Smart Terminal Menu ----------------------------------------------------------------- Figure 6-4. Communication parameters help. Numbers 1-8 -- The numbers 1 through 8 are used to select the communications speed in bits per second (bps), the parity, the number of data bits and the number of stop bits. These preset parameter selections are the only ones TC-TERM supports. Even parity should be used when a remote host computer is set up to receive Mark or Space parity. A -- The A command is used to the change communication port to COM1. This is the normal default port for most asynchronous adapters and internal modems. B -- The B command is used to change the communication port to COM2. This is the nondefault port for most asynchronous adapters and internal modems. Configuration switches or jumpers are used to change the adapter card or modem designation. This port selection is normally used only when the COM1 port is used by another device such as a plotter or printer. Q -- The Q command is used to return to the Smart Terminal Menu. This command should be executed only after the selected parameters are reviewed at the "Present Parameters" prompt. 52 Chapter 7. System Maintenance TCOMM requires periodic system maintenance. The maintenance requirements depend on caller access frequency and the level of caller activities. As system usage increases, required file and message maintenance increases. This chapter presents typical maintenance functions. BULLETINS The TCOMM bulletins are text files and may need periodic update and revision. Bulletins should be produced and edited using a text editor such as Edlin or the IBM Personal Editor. The System Operator can use a word processor to maintain bulletins but the files should be stored on disk in a nondocument ASCII format. The System Operator should only include extended MS-DOS and PC-DOS ASCII characters (characters with ASCII values greater than 127) in bulletins that are designated as graphics bulletins. The System Operator should append the letter 'G' as a filename extension to these bulletin filenames. Including these special ASCII characters in nongraphics bulletins can result in confusing displays for callers. When new bulletins are added to the system and existing bulletins are edited, the System Operator should reflect these updates in the master bulletin menu. The master bulletin menu updates have to be performed manually; modifications of bulletins or bulletin submenus do not automatically result in update modifications of the master menu. MAIL SUBSYSTEM The Mail Subsystem maintenance requirements are directly proportional to Mail Subsystem usage. Frequently used systems require message review two or three times a week. The System Operator should read every message and delete messages that do not adhere to stated system rules. The message Modify command should be used to change the public/private status of messages when appropriate. Callers may leave messages that require System Operator response. Requests for information or questions may be posed. Timely System Operator response to caller requests can enhance the utility of the TCOMM system. A few callers may leave messages that are abusive. The System Operator will have to watch for messages of this type and delete them. Callers that insist on leaving abusive messages will have to be locked out of the system at the User Data Base Maintenance 53 Menu. Public messages not directed to a specific individual require System Operator maintenance. These messages can only be deleted by the System Operator. The System Operator should delete old public messages as required to provide disk space for new messages. The System Operator can set up the system for automatic deletion of old messages by activating that feature in the Configuration Profile, but a frequently used message system will still require deletion of some messages to keep the number of messages from reaching the maximum number established in the Configuration Profile. The System Operator must delete messages directed to the Operator by name. Public and private messages directed to the System Operator can consume a great deal of disk space if not periodically eliminated. The System Operator may want to leave some public messages on the system for callers to read, but private messages to the System Operator should be deleted if they are not needed for future reference. The message archive feature can be activated in the Configuration Profile to force the system to keep a copy of every message sent or received; this feature should be used to archive messages rather than keeping them on- line. USER DATA BASE The System Operator can maintain the user data base from the Operator Main Menu, the User Data Base Maintenance Menu, and the Remote Command menu. Maintenance activities will depend upon the open or closed nature of the system. Open systems that allow all callers to access the system require more frequent data base maintenance than closed systems that allow only preregistered user access. System Operators of open access TCOMM systems should periodically pack the user data base at the Operator Menu to remove inactive system users. Most System Operators perform this function early each month to reduce the size of the user data base. The pack operation removes users that have not called into the system for a time period that exceeds the inactivity time limit designated in the Configuration Profile. The pack operation does not eliminate locked-out users from the data base; the locked-out status of these users is retained until changed by the System Operator. The System Operator can elect in the Configuration Profile to have the data base packed automatically each day. If this automatic pack is activated, the manual packing in not required. Automatic pack is the same as manual pack--locked out users are retained. This automatic pack is performed the first time the system is started on a specific day or after the first caller logs off after midnight. 54 A backup copy of the data base can be automatically retained if this feature is activated in the Configuration Profile. When activated, the backup copy is made just before an automatic or manual data base pack is performed. The backup copy of the data base will have the filename extension 'BAK'. System Operators of closed TCOMM systems should periodically review and revise preregistered users data. New users may have to be added and existing users marked for deletion. The System Operator may also wish to remove users marked for deletion by executing the Operator Main Menu Remove command. If data base automatic backup is activated, the Remove command also produces a backup copy of the data base. The operator modifies user data at the User Data Base Maintenance Menu. The menu commands and data base fields that can be modified by the System Operator are discussed in the following paragraphs. The User Data Base Menu produced by the TCOMM distribution profile is shown in Figure 7-1. The User Data Base Editor menu displayed when the Add and Modify commands are executed is shown in Figure 7-2. Add -- The operator should use the add command to add new users to the user data base. This technique allows the System Operator to establish and add to a data base of preregistered users. By setting the required system access level higher than the default new caller access level and assigning added users access levels above the required system access level, the operator can limit system access to these preregistered users. These preregistered users can also be designated to be members of up to six private groups. The add command can be used to add users to the data base in an open access system as well. This is normally done to add assistant System Operators when the system is first put into operation. The add command can also be used to establish the members of a private group when the group feature of the system has been activated. The data fields available when using the Add command are discussed later. Backward -- The Backward command will display the previous user data base record unless the current record is at the top of the data base file. To check the records of new users in an open access system, the System Operator can go to the end of the data base using the End command, then use the Backwards command to review each new record. 55 Delete -- The operator can use the Delete command to mark a user for later deletion from the data base. The Delete command changes a user access level from a numeric value to the letter 'D'. The Remove command at the Operator Main Menu is used to remove from the data base users marked for deletion. Executing the Delete command a second time at a user record will return the user to normal user status with the access level of a new caller. The Modify and Lock commands can also be used to change the user status after the Delete command has been used. End -- The End command allows the System Operator to go to the end of the data base file. Forward -- The Forward command displays the next user record contained in the user data base. If the current record is at the end of the data base file, the Forward command will move the System Operator to the beginning of the file. Lock -- The Lock command locks the currently displayed user out of the system by assigning the user an access level of zero. This user will be unable to access TCOMM in the future. Locked- out users are not eliminated from the data base when a Pack or Remove operation is performed. The user lock-out is preserved until the System Operator reinstates the user or marks the user for deletion. Executing the Lock command a second time at a user record will return the user to normal status with the access level of a new caller. Modify -- The operator can use the Modify command to modify the data associated with each registered system user. User names can be changed and passwords can be modified. User access levels can also be changed. This command should also be used to designate callers for private groups. All data fields that can be modified are discussed later. The System Operator can use the cursor keys and the ENTER key to move from one data field to another. By pressing ENTER at the last displayed data field, the Modify function is terminated. If a data field is not modified before the System Operator presses ENTER at that field, the field contents remain unchanged. The System Operator is asked to confirm all changes before they are stored in the data base. Quit -- The Quit command returns the System Operator to the Operator Main Menu. All changes made during the maintenance session and confirmed by the System Operator are retained in the data base. 56 Search -- The System Operator can search the data base for a specific user with the Search command. Execution of the Search command results in the request for user identification. TCOMM converts the information to all caps and looks for matching information in the data base. The search begins at the top of the data base file and continues until a match is found. If TCOMM reaches the end of the data base file without finding the requested user, a user not found message is displayed. The System Operator is not required to enter the full user name when performing a search. The search can be based on first name, last name or just a series of name characters. If part of a user's name is relatively unique, the System Operator can enter that part of the name as the basis of the search. If TCOMM finds the requested name characters, the System Operator can use the command 'C' to continue the search for the next occurrence of the same string of characters. The C command can be used until TCOMM reaches the end of the data base. Top -- The Top command allows the System Operator to go back to the beginning of the data base file. USER DATA BASE DATA FIELDS The following paragraphs describe the user data base data fields. This discussion is based on the data field names provided with the TCOMM distribution system Configuration Profile. The field names that can be altered by the System Operator are identified. First and last name: This data field contains the user's unique identification. The name of the field displayed is chosen by the System Operator in the Configuration Profile and is called the "User name identification string." The Add command can be used to enter a user name or identification in this field. The Modify command can be used to alter the data. New users are prompted for this information the first time they call. This field must contain information. Street address: The name of this field is also chosen by the System Operator in the Configuration Profile and is called the "First user information string." A company wide electronic mail system may use this field to display the caller's department. The Add command can be used to create this data for a new user and the Modify command can be used to alter existing data. New users are prompted for this information the first time they call. This field does not have to contain data. 57 City, state & zip: The name of this field is also chosen by the System Operator in the Configuration Profile and is called the "Second user information string." A company wide electronic mail system may use this field to display the caller's division. The Add command can be used to create this data for a new user and the Modify command can be used to alter existing data. New users are prompted for this information the first time they call. This field does not have to contain data. Area code & number: The name of this field is also chosen by the System Operator in the Configuration Profile and is called the "Third user information string." A company wide electronic mail system may use this field to display the caller's telephone extension. The Add command can be used to create this data for a new user and the Modify command can be used to alter existing data. New users are prompted for this information the first time they call. This field does not have to contain data. Access: The access field contains the user access level. The contents of this field should be a number in the range 1 to 99, the user deleted symbol 'D' or the user lock out level 0. The Add command can be used to create this data for a new user and the Modify command can be used to alter existing data. The user cannot create or alter this data. This field must contain data. Groups: The Groups field contains the private group preregistration of the user. The Add command can be used to create this data for a new user and the Modify command can be used to alter existing data. The user cannot create or alter this data. This field does not have to contain data. Only the user registration group numbers should be placed in this field. The numbers should correspond to the group names specified in the Configuration Profile. For example, if the first caller group name is TEACHERS and the second caller group name is STUDENTS, a user registration for access to both groups will be as follows: |12 | It should be noted that the numbers are not separated by spaces or other characters. The group numbers can be in any order. 58 Lastcalled: The Lastcalled field contains the last date and time the user called into the system. If a user is added to the system by the System Operator, the current date and time is automatically entered into this field. When a new user calls into an open system, the current date and time is entered into this field automatically by the system. Each time a user calls into the system this field is updated to the current date and time. When a data base pack is performed, inactive users are removed from the system based on the contents of this field relative to the date and time of the pack. This field must contain data. Last Msg: The Last Msg field contains the number of the last message read by the user. This field is updated each time the user calls into the system. The Add command can be used to create this data for a new user and the Modify command can be used to alter existing data. This field does not have to contain data. Page length: The Page length field contains the screen height of the user's display screen (number of lines). This field is updated each time the user calls into the system and the field contents can be altered by the user at the Change Command menu. The Add command can be used to create this data for a new user and the Modify command can be used to alter existing data. This field must contain data. Password: The Password field contains the user's password. This field is updated each time the user calls into the system and the field contents can be altered by the user at the Change Command menu. The Add command can be used to create this data for a new user and the Modify command can be used to alter existing data. This field must contain data. Record: The Record field contains the user record number. The contents of this field are created by TCOMM each time a user is added to the data base. The user record numbers are sequential starting with number 1. The user records are renumbered each time a Pack or Remove operation is performed. The System Operator cannot directly alter the contents of this field. This field must contain data. 59 ACTIVITY LOG The TCOMM activity log has no size limit and must be periodically reviewed and deleted. The System Operator should review the file to note system error messages and caller activity patterns. If error messages appear in the file, the System Operator should resolve the errors as noted in Chapter 13. If caller activity patterns indicate attempted system abuse, the offending callers should be locked out of the system at the User Data Base Maintenance Menu or warned of the consequences of these activities in the Mail Subsystem. Frequent use by a specific caller in a closed pre-registration system could mean the caller name and password have been distributed to several people. After activity log review and follow-up, the System Operator should execute the Operator Menu Delete command to delete the activity log file. FILES SUBSYSTEM The files and menus in the File Subsystem require periodic maintenance. Most of this maintenance will center around the upload disk drive. The System Operator must review uploaded files to be sure they conform to file upload rules. Files not conforming to upload rules must be deleted and their description data deleted from the appropriate upload menu (public or private). If the System Operator has configured the system for separate upload and download disk drives, uploaded files must be copied to download drive(s) before they can be made available for caller download. The System Operator should also move the description of these files from the upload menus to the appropriate download menus by using a text editor such as the IBM Personal Editor. DATA BACKUP Many TCOMM system files require periodic backup. The System Operator should make backup copies of text files as they are created or modified. Active system files will require more frequent backup. The user data base (USERDATA.TC) and the mail index (MAILINDX.TC) are the most critical active files. The System Operator may want to make backup copies of these files monthly. For critical TCOMM implementations, the System Operator may wish to make active file backups weekly. A backup copy of the user data base is automatically created if the System Operator has activated this feature in the Configuration Profile. 60 Chapter 8. System Operating Tips There are a several important facts to consider before you start TCOMM operation. The following paragraphs contain information that may save you time, money, and frustration. CALLER ACTIVITY The System Operator of a new public access TCOMM system is often frustrated because the system does not get much activity at first. Some System Operators get so frustrated that they shut down the system before it really gets started. This is unfortunate because it usually takes time for a new system telephone number to get into circulation. Most systems only receive a few calls during the first two months of operation. Some new systems are also slow to catch on because people take time to adjust to new ways of corresponding. For System Operators that get beyond this break-in period, however, there are new experiences in store. LONG UNATTENDED PERIODS Inactive systems do not use much disk space to log users or record caller activity and can be left unattended for long periods. Active systems can only be operated for a few days without system maintenance. You will be able to judge this after operating the system for several months. If you operate a TCOMM system at home and it cannot be left unattended for the duration of a vacation or trip you plan to take, you should not inform callers that your system will be out of operation while you are away from home. Telling callers your system will be inoperable for a week or two may be a courtesy, but it may also invite thieves to your house. You could say that your system will be in the shop for maintenance for that period of time, but you could also say nothing. People who call while you are away and do not get an answer will simply think your system "crashed" and has not been restarted. Some System Operators leave their modems off hook while on vacation. If you configure the system to leave the modem off hook after exit to PC-DOS, then exit to PC-DOS just before leaving for vacation, the modem presents a busy signal for all callers. AVOIDING CALLER PROBLEMS An Operator can take actions and precautions that reduce caller related problems. The tips contained in the following paragraphs are based on several man-years of single user and multi-user 61 unattended communications system operations experience. Many of these tips were learned the hard way. Setting the Tone An unattended communication system generally develops a personality that reflects the attitudes and interests of its System Operator. If you wish to operate an open access professional system that caters to adults and business people, do not place game programs in the download menus and delete all game-related messages that appear on the system. If you wish to stay well within the law with regard to proprietary and copyrighted text, data, and files, specifically ask callers not to deposit these items and periodically review all messages and uploaded files to be sure that none creep into the system. By posting bulletins on specific topics and deleting messages that do not pertain to these topics, you can establish a system theme. This is important for business applications of TCOMM. Posting Telephone Numbers You should not post voice telephone numbers on a public access system unless you are willing to spend a great deal of time on the telephone. Posting your number on an active public system can result in 5 to 20 calls a day. One purpose of an unattended communications system is the elimination of voice calls-- answering a caller's question in a public reply will answer that question for many future callers. For closed systems, on the other hand, you may wish to post the System Operator's voice telephone number as a last resort source of help. Some people just cannot adjust to computer-based information systems and may need human assistance. Demanding Callers Public system users can sometimes be demanding. They may ask for advice or counsel or they may ask for files you have removed from the system. After answering these demands several times, most System Operators learn to say "no" politely. If you are a professional in a certain trade or business, you also have to be careful about providing advice or counsel on a public information system; you may be technically liable for actions taken on the basis of your advice. This is particularly true for lawyers and medical doctors. 62 Prank Callers Almost all electronic information systems receive prank calls. Some callers just want to have fun and others want to interfere with the operation of your system. TCOMM is designed to handle these callers, but a person seriously interested in "stopping the show" may find a way to do so. You should keep track of these callers and lock them out of the system. You may also want to leave messages for people you suspect to be pranksters to make them aware of your observations; knowing there is someone watching may be enough to keep some ill-intentioned callers away. Profanity There are some system callers who insist on using profanity. You will have to monitor messages and files to be sure they meet your standards. Text that does not meet your standards will have to be edited or purged. Upload Rules A TCOMM system set up for private company correspondence may not require System Operator surveillance to ensure adherence to upload rules. A public access system will require upload surveillance. If your system allows public access and file uploading, you should post rules for the files you will accept. Some callers like to upload copyrighted files to public systems just to see what kind of response they will get. You may be held responsible for public access to that copyrighted material. Besides posting upload rules, you will have to monitor uploaded files to be sure none of them are commercial software packages. You may also want to post rules on the types or quality of software you will accept. If you operate a public access TCOMM system for a special interest group, you may want to limit files to those that would be of interest to the group. You may have less control over the quality of files you get. Some system Operators test all software uploaded to their systems, but this is impractical for active system Operators. You may just want to post a disclaimer on the quality of software found on your system. UPLOADED FILE TIPS Files uploaded to TCOMM sometimes require translation before they can be used. Text files created by certain word processors or text editors may need carriage returns or line feeds added. ASCII text files and program source code may also be altered by communications software during the file transfer process. These files may also require modification before use. The following 63 paragraphs provide tips on handling the upload file problems. Text Files If an uploaded text file cannot be properly listed to the display using the PC-DOS TYPE command, it requires post processing. If each line displayed is written over the top of the previous line displayed, the file needs a linefeed added after each carriage return. If the text is readable but not aligned properly along the left side of the screen, the file needs a carriage return placed in front of each linefeed in the file. If the file was produced by a word processor and contains special 8-bit ASCII characters (Greek symbols and graphics characters) it must be translated to a "plain vanilla" 7-bit text file. The BASIC programs shown in Table 8-1 are included on the distribution diskette to perform these functions for you. Table 8-1. BASIC Translation programs. Program Name Function ------------ ------------------------------------------ ADDLF.BAS Adds a linefeed after each carriage return ADDCR.BAS Adds a carriage return before each linefeed UNWS.BAS Converts a word processor file to text BASIC Source Code If someone uploads a BASIC file to you and it will not list on your screen using the PC-DOS TYPE command, you should go into BASIC, load the file, list it, then resave it using the same name. If you get a `Direct Statement In File' error printed on the screen when you load the file, that means the file contains a text statement (a line with no line number). This will not interfere with the resaving of the file unless the direct statement is at the beginning of the file. If the file lists properly, then the direct statement is at the end of the file. If the file does not list properly, then the direct statement is at the beginning of the file and must be removed using a text editor before the program can be loaded and run. Do not attempt to save a BASIC file after getting the `Direct Statement In File' error during loading without listing the program first; you will destroy the file otherwise. If you wish to load an uploaded file (a BASIC program or any other text file) into a text editor to change the content of the file, you will have to first add line feeds to the end of each line. 64 Dangerous Files The System Operator should assume that any executable program file uploaded to system has the capability of destroying all files on the PC. This can be caused by documentation errors, incorrect program execution, or malicious program design. To be sure all programs execute properly, perform the following steps: 1. If a program is interpretive BASIC (has a filename extension of BAS), load it into the BASIC interpreter and list it to the monitor. Check the program for suspicious commands such as KILL. 2. If a program is a directly executable module (has a filename extension of COM or EXE), copy the program to a blank diskette before executing it. If the program attempts to delete files or change the active drive, use the Ctrl-Break key combination to terminate execution of the program; turn the computer off if the Ctrl-Break keys do not halt program execution. Under no circumstance should you test an uploaded program on a hard disk containing valuable files. GENERATING SYSTEM USAGE A TCOMM System Operator can influence system activity level. Caller activity is a function of the utility of the information contained in the system and the level of publication of the system telephone number. The System Operator can control both of these variables. Seed Messages If caller message activity is lower than you want or expect, seed the message system with questions and answers that are relevant to your audience. Controversial bulletins and messages can also elicit caller response. You may want to log into the system under assumed names to give the appearance of multiple users when you are building this seed information base. A sincere interest in caller queries and timely response to requests for help and information are key ingredients in an active and useful system. Seed Files Many public and private system users are primarily interested in files that are available for download. Typical systems receive one upload for every one hundred files downloaded. To increase initial system use place useful public domain files in the download system. You should also encourage file uploads if you are interested in receiving files from callers. 65 Periodic additions of new files also encourage system use. Files should be added that will be of interest to the audience you wish to attract. Encourage Callers Encouraging callers to use specific TCOMM capabilities may generate greater system usage. The operator can develop Bulletins or enter messages that describe the capabilities and benefits of certain features. Providing illustrations of commands beyond those contained in system help files may also benefit callers. Novice system users are often timid when it comes to using the system to its fullest capability; a little encouragement will help them overcome any fears they have with regard to TCOMM communications. 66 Chapter 9. System Configuration Profile The System Configuration Profile parameters control the operation of the system and optimize TCOMM performance for your specific hardware and communication needs. The Configuration Profile parameters can be changed at any time to alter the way TCOMM operates or responds to callers. Periodic review and modification of these parameters could result in improved TCOMM performance. To modify a profile parameter, type the parameter item number then press ENTER. TCOMM will prompt you for a new value. Type the new value, then press ENTER. When all items have been reviewed and all changes have been made, type U and press ENTER to update the system profile settings. TCOMM will return you to the Operator Main Menu. The Forward and Backward commands allow you to move forward and backward through the profile one page at a time. To abort the Profile update and return to the Operator Main Menu type A and press ENTER. The changes made in the Profile during this editing session will be lost when the Abort command is executed. The TCOMM Configuration Profile is stored in a file called PROFILE.TC that must reside in the TCOMM system drive or subdirectory. If TCOMM cannot find the PROFILE.TC file during startup or recycle, internally stored default parameters will be used until you modify them. TCOMM will indicate that PROFILE.TC could not be found and will ask you to review and modify the default parameters before further execution is allowed. Be sure to include drive designations in front of directory designations where file locations are specified. For example, text files on a fixed disk would normally be stored in the C:\TCOMM\TEXT directory, not in the \TCOMM\TEST directory. Failure to include the drive designation in the location parameters may prevent TCOMM from returning to the system drive and directory during certain command executions. The following paragraphs describe each Configuration Profile parameter in the order they appear when the Configuration Profile command is executed at the Operator Main Menu. The actions caused by some of these parameters may not become completely apparent until the system is returned to operation. If you are unsure of the actions caused by certain parameters, test the parameter changes by going to local system access from the Operator Main Menu after the changes are made. Most caller commands can be executed locally by the System Operator. 67 1. Operator's first and last name This parameter is the System Operator's real first and last name. TCOMM will automatically use this name when the System Operator enters a message for a caller. This name is also recorded in the system activity log when the System Operator downloads or uploads a file. 2. Operator's remote login code name The Operator's remote login code name is the name the System Operator will use when dialing into the system from a remote terminal or computer. The System Operator will get special control privileges if the code name is used during remote login. Note: TCOMM does not allow the Operator's code first name and last name to be the same as the Operator's real first and last name. This keeps callers from trying to use the System Operator's name in an attempt to get higher privileges. If a caller attempts to login using the Operator's real first and last name, TCOMM will drop the caller off the system and recycle to wait for another caller. 3. Password required to access Operator Main Menu This password controls System Operator local access to the Operator Main Menu. The same password controls System Operator remote access to the Operator Command menu. After the local System Operator presses function key F2 to access the Operator Main Menu, this password is requested. After the remote System Operator executes the Operator command at the main caller menu, this password is also requested. The password should be one that the System Operator will not easily forget because access to this Configuration Profile cannot be achieved unless the System Operator is able to access the Operator Main Menu. 4. Maximum bits per second rate of system modem The System Operator should enter the maximum system modem speed here. Modem speed is rated in baud or bits per second (bps). If a Hayes Smartmodem 1200 is used with the system, a value of 1200 should be entered. If a Hayes Smartmodem 2400 is used, a value of 2400 should be entered. Entering an incorrect value could cause TCOMM to malfunction. 68 5. Minimum allowable bits per second rate of system The System Operator should enter the minimum system modem speed TCOMM is to support. Modem speed is rated in baud or bits per second (bps). If a Hayes Smartmodem 1200 is used with the system, a value of 300 can be entered. If a Hayes Smartmodem 2400 is used, a value of 300 can still be entered. Entering an incorrect value will not cause TCOMM to malfunction, but it could keep some callers from accessing the system. Entering a value of 1200 will keep all 300 bps callers from accessing the system--some System Operators use this minimum modem speed to eliminate low speed modem users that may be abusing the system. 6. Communication port to be used (1 or 2) TCOMM allows the System Operator to select either asynchronous port 1 or 2 corresponding to PC-DOS devices COM1 and COM2. These ports can be IBM or IBM compatible asynchronous ports with Hayes compatible modems attached via RS-232C cables or they can be internal Hayes Smartmodems. Selecting the wrong port will cause TCOMM to fail during its startup sequence. A message indicating this error will appear on the screen, and the System Operator will be allowed to correct the selection. 7. Printer port to be used (1, 2 or 3) TCOMM allows the System Operator to select printer port 1, 2 or 3 corresponding to PC-DOS devices LPT1, LPT2 and LPT3. These ports can be IBM or IBM compatible parallel printer ports with IBM compatible printers attached via parallel cables. Selecting the wrong port will cause TCOMM to fail when caller activity or system error information is sent to the printer. A message indicating this error will appear on the screen, and the System Operator will be allowed to correct the selection. 8. Operator's office hours starting time (military) The System Operator should enter the time of day (military format) that availability for caller paging will start. Caller pages before this hour will result in a friendly message indicating the System Operator is not available; the caller will be given your office hours at that time. To answer a caller page (the system will beep to indicate a caller page) the System Operator should press function key F10. Note: Function keys F5 and F6 can be used to temporarily override this office hour setting. 69 9. Operator's office hours ending time (military) The System Operator should enter the time of day (military format) that availability for caller paging will end. Caller pages after this hour will result in a friendly message indicating the System Operator is not available; the caller will be given your office hours at that time. To answer a caller page (the system will beep to indicate a caller page) the System Operator should press function key F10. Note: Function keys F5 and F6 can be used to temporarily override this office hour setting. 10. Monitor adapter is Enhanced, Color, Monochrome If you wish to use an IBM Enhanced Graphics Adapter and an IBM Enhanced Color Display connected to the adapter, enter Enhanced here. If you wish to use an RGB color monitor connected to either a color or enhanced graphics adapter, enter Color here. If you plan to use an IBM monochrome monitor connected to a monochrome display adapter, enter Monochrome here. Any monitor other than the IBM monochrome monitor is considered a color monitor by TCOMM. For example, a green or amber display that is connected to the composite port of a color graphics adapter is considered a Color monitor. If TCOMM fails to function properly after this parameter is altered, the wrong monitor adapter type may have been selected. If the wrong adapter has been selected, the software will operate properly, but the local System Operator will not receive screen display output from the system. To correct this problem, complete the following steps: 1. Turn off the IBM PC system unit for one minute. 2. Turn the system unit back on. 3. Change to the TCOMM system drive or directory (the A drive in a diskette drive system or the TCOMM\SYSTEM directory in a fixed disk system). 4. Copy the system profile backup called PROFILE.BAK to the PROFILE.TC file by executing the following command: COPY PROFILE.BAK PROFILE.TC 5. Restart TCOMM by typing TCOMM and pressing return. 11. System Operator mode foreground color The System Operator should select a color other than 7 for this parameter only if a color monitor is used. The foreground and background color combinations allowed are the same as those 70 allowed by the IBM BASIC language. These colors and their associated numbers are discussed in the IBM BASIC manual and are listed below: Color Color Number ____________ ____________ Black 0 Blue 1 Green 2 Cyan 3 Red 4 Magenta 5 Brown 6 Light gray 7 Dark gray 8 Light blue 9 Light green 10 Light cyan 11 Light red 12 Light magenta 13 Yellow 14 White 15 12. System Operator mode background color The System Operator should select a color other than 0 for this parameter only if a color monitor is used. The foreground and background color combinations allowed are the same as those allowed by the IBM BASIC language. These colors and their associated numbers are discussed in the IBM BASIC manual and are listed in parameter 11. 13. Caller mode foreground color The System Operator should select a color other than 7 for this parameter only if a color monitor is used. The foreground colors allowed are the same as those allowed by the IBM BASIC language. These colors and their associated numbers are discussed in the IBM BASIC manual and are listed in parameter 11. 14. Name of terminal program to be used This is the name of the smart terminal program TCOMM will execute when the Terminal command is executed at the Operator Main Menu or when the F4 function key is pressed at the function key menu. TC-TERM is supplied as a part of TCOMM and can be designated here. Any other communications program can also be designated. If no communications program name is provided, TCOMM will execute the TC-TERM smart terminal software when the System Operator elects to enter the terminal mode. 71 15. User name identification string This information request text will be presented to callers during login as a request for identification. Most System Operators will use FIRST & LAST NAME: for this string. This information will be stored in the user data base and can be reviewed or edited in the User Data Base Maintenance Subsystem. 16. First user information string This string will be the presented to callers during login as a request for caller related information. Most System Operators will use STREET ADDRESS: for this string. This information will be stored in the user data base and can be reviewed or edited in the User Data Base Maintenance Subsystem. 17. Second user information string This string will be the presented to callers during login as a request for caller related information. Most System Operators will use CITY, STATE & ZIP: for this string. This information will be stored in the user data base and can be reviewed or edited in the User Data Base Maintenance Subsystem. 18. Third user information string This string will be the presented to callers during login as a request for caller related information. Most System Operators will use AREA CODE & PHONE: for this string. This information will be stored in the user data base and can be reviewed or edited in the User Data Base Maintenance Subsystem. 19. Drive for static system text files This designates the location of the TCOMM text files that are not modified or updated by system operation. A random access memory drive (virtual disk) can be used to speed up display of these files. A fixed disk subdirectory can also be used. The static TCOMM system files are: HELP WELCOME NEWUSER WARNING BULLET INFO NEWUSER.G WELCOME.G Additional bulletin and graphics files will also be located on this drive or directory. If a disk drive root directory is to be used for the text files, the drive designation must end with a colon and a backslash (for example, A:\). If a more than one disk drive is to 72 be used with TCOMM and a subdirectory is to be used for the text files, the disk drive letter and a colon must precede the path name. The path name must end with a backslash. For example, C:\TCOMM\TEXT\ is the normal designation for the text drive in a hard-disk system. If one fixed disk is to be used for all TCOMM operations, the disk drive letter and colon do not have to precede the path name. 20. Drive for Mail subsystem message files This designates the location of the Mail Subsystem message files TCOMM creates during system operation. These files should be located on a physical disk drive. A power failure will result in the loss of messages left by callers if a random access memory (virtual disk) disk drive is used. The TCOMM message filenames will begin with the letter 'M' and will end with a unique message number. They are automatically created by TCOMM but can be edited by the System Operator. A sample message file named M1 is provided with TCOMM. The message index file MAILINDX.TC will not be located with the messages files. It will be located with the TCOMM system files so it can be easily located with a disk drive directory search. If a disk drive root directory is to be used for the message files, the drive designation must end with a colon and a backslash (for example, A:\). If a more than one disk drive is to be used with TCOMM and a subdirectory is to be used for the message files, the disk drive letter and a colon must precede the path name. The path name must end with a backslash. For example, C:\TCOMM\MESSAGES\ is the normal designation for the message drive in a hard-disk system. If one fixed disk is to be used for all TCOMM operations, the disk drive letter and colon do not have to precede the path name. 21. Drive for remotely executable programs This designates the location of the TCOMM external programs that can be executed by callers at the Programs Command menu. If the programs to be made available for callers have the potential to erase or destroy other files, this drive or directory should not be the same as that designated for other TCOMM subsystems. If a disk drive root directory is to be used for the program files, the drive designation must end with a colon and a backslash (for example, A:\). If a more than one disk drive is to be used with TCOMM and a subdirectory is to be used for the program files, the disk drive letter and a colon must precede the path name. The path name must end with a backslash. For example, C:\TCOMM\MESSAGES\ is the normal designation for the program drive in a hard-disk system. If one fixed disk is to be used for all TCOMM operations, the disk drive letter and colon do not have 73 to precede the path name. 22. Drive for active system files This designates the location of the TCOMM files that are modified or updated during system operation. These files should be located on a physical disk drive. A power failure will result in loss of updated information if a random access memory (virtual disk) disk drive is used. The active TCOMM system files are: STATUS.TC USERDATA.TC MAILINDX.TC CALLERS.TC LOG.TC The system drive will also contain the following executable TCOMM files: TCOMM.EXE XMODEM.EXE KERMIT.EXE If a disk drive root directory is to be used for the active system files, the drive designation must end with a colon and a backslash (for example, A:\). If a more than one disk drive is to be used with TCOMM and a subdirectory is to be used for the active files, the disk drive letter and a colon must precede the path name. The path name must end with a backslash. For example, C:\TCOMM\SYSTEM\ is the normal designation for the active system file drive in a hard-disk system. If one fixed disk is to be used for all TCOMM operations, the disk drive letter and colon do not have to precede the path name. 23. Drive available for file uploading This designates the disk drive or subdirectory to receive all files uploaded to the system. If you plan to operate a public access system with a fixed disk drive configuration, you may want to limit file uploads to a diskette drive. An active system can fill a fixed disk quickly with uploaded files. You may also want to designate a different drive or subdirectory for upload activity than the drives or subdirectories you designate for download files. This segregation of upload files from the download areas will allow you to review uploaded files before other callers are allowed to download them. If a disk drive root directory is to be used for file uploading, the drive designation must end with a colon and a backslash (for example, A:\). If a more than one disk drive is to be used with TCOMM and a subdirectory is to be used for the upload files, the disk drive letter and a colon must precede the path name. The path name must end with a backslash. For example, C:\TCOMM\FILES\ is the normal designation for the upload file drive in a hard-disk system. If one fixed disk is to be used for all TCOMM operations, the disk drive letter and colon do not have to precede the path name. 74 24. 1st drive available for file downloading 25. 2nd drive available for file downloading 26. 3rd drive available for file downloading 27. 4th drive available for file downloading 28. 5th drive available for file downloading These diskette drives or fixed disk subdirectories contain files you wish to make available for callers to download. The system will search each diskette or subdirectory in the order you specify until it finds the file requested by a caller. If a file transfer protocol supports wildcard file transfers and the System Operator has activated wildcard transfers in this profile, the first drive or directory listed for the 1st drive available for download will be the only one searched for files to send to the caller when the caller asks for a filename containing either the '*' or '?' wildcard character. This drive or directory designation is the only one passed to the file transfer protocol module. One diskette drive or subdirectory designation can be placed after each of these download drive requests or several drive or directory designations can be stacked on each line. If only one drive or subdirectory is placed on each line, it must begin with the drive letter and a colon and end with a backslash. For example, B:\ will cause the system to search the B drive root directory. If drive or directories are stacked on each line, they should be separated by a semicolon and should conform to the PC- DOS PATH command syntax. For example, the designation A:\;C:\TCOMM\FILES\ will cause the system to search the A drive then search the files subdirectory on the C drive. Each drive or directory designation must end with a backslash. 29. Should guest Operators be allowed to Exit to DOS This parameter determines whether callers with System Operator privileges are allowed to exit to DOS at the Remote Command menu. If this question is answered NO, only the System Operator will be allowed to exit to DOS; guest System Operators will be allowed to execute all other remote System Operator functions except exit to DOS. 30. Should callers be told free disk space at upload This parameter allows the System Operator to determine whether callers are to be informed of the free disk space on the upload drive when a file upload is performed. A YES parameter will cause TCOMM to provide the free disk space information. A NO parameter will prevent TCOMM from giving out this information. System Operators using a fixed disk system often do not want callers to know the amount of system free space because it can encourage system abuse. 75 31. Should ASCII file transfers be displayed This parameter determines whether ASCII file transfers are displayed if local display is on. A YES parameter will result in display of the file as it is transferred if the file transfer is in ASCII mode and local display is on. A NO parameter will prevent display of the file as it is transferred in ASCII mode. A NO parameter should be used to increase the speed of ASCII file transfers; local display of files as they are transferred in ASCII mode slows down the transfer at communications speeds above 300 bps. 32. Should wildcard file transfers be allowed This parameter allows the System Operator to determine whether callers are allowed to use wildcard characters in filenames when files are being downloaded or uploaded. A YES parameter will cause TCOMM to pass filename requests containing wildcards such as '*' or '?' to the requested file transfer protocol. A NO parameter will cause TCOMM to deny file transfers that contain wildcard filenames. Caution: This parameter should be used with care because it could result in a system security breach. If callers are allowed to download files using wildcard filenames, any file can be downloaded from the first drive or directory designated for downloading. When this parameter is set to YES, the drive or directory designated for file uploads should not be the same as the first drive or directory designated for downloads; this will keep callers from downloading files designated as private when they were uploaded. 33. Filename extensions that signify binary files TCOMM assumes files with the following filename extensions are binary and require a file transfer protocol to ensure error-free transfer: BIN EXE COM BAS OBJ LIB If you want other filename extensions to signify binary files, you should enter those filename extensions here. The filename extensions can be stacked with a semicolon placed between each. 34. Should callers get bulletins menu after login This parameter determines the initial operation of TCOMM when a caller logs in. A YES parameter will cause TCOMM to pass each caller through the Bulletin Subsystem before allowing access to the caller Main Command menu. A NO parameter will cause TCOMM to 76 bypass the Bulletin Subsystem after a caller logs in. In either case, a caller with sufficient access privilege can go back to the Bulletin Subsystem from the Main Menu. 35. Should caller access time be limited If this parameter is set to NO, callers will be allowed unlimited time on the system; only elapsed time on the system will be displayed before each menu. If this parameter is set to YES, callers will be given time limits per session and per day based on the profile parameters that follow. Callers with System Operator privileges will be given unlimited time on the system. 36. Session time limit increment per security level This parameter allows the System Operator to select the maximum length of time a caller can stay on the system during a single session based on caller access security level. This time increment is multiplied times the caller security level to get the maximum caller session duration. A system that only operates at 300 bps will generally require a longer maximum time limit than one that operates at 1200 bps. An Operator may also want to reduce the time limit as the system becomes more active. Time limit increments usually vary between 7 and 20 minutes. A 7 minute increment will give a caller with a security level of 5 a session time limit of 35 minutes. 37. Daily time limit increment per security level This parameter allows the TCOMM System Operator to select a maximum time limit per day based on caller security level. This increment will be multiplied times the caller security level to determine the maximum time limit per day. This feature keeps a caller from calling back into the system several times during a day and using the maximum time allowed per session. By limiting caller time per day, the System Operator can make the system available for more callers per day. A daily time increment of 10 minutes will give a caller with a security level of 5 a daily time limit of 50 minutes. The caller can call back several times during a given day as long as the total time on the system is less than the daily time limit. 38. Caller input timeout duration (in minutes) This time will determine how long TCOMM will wait for caller input before timing out. When a timeout occurs, TCOMM will go to the next highest menu level. If a timeout occurs at the caller Main Command menu, the system will terminate the session and recycle to wait for the next caller. A timeout duration of 3 minutes is typical. 77 39. Should mail be sent only to registered users This parameter allows the System Operator to select either a closed or an open system. A NO parameter will allow callers to send messages to callers who are not yet registered system users. A YES parameter will allow callers to only send messages to registered users and to the System Operator. This parameter can be used to control the volume of mail that passes through the system. It can also be used to reduce the number of public messages, thereby reducing the System Operator maintenance chores (public messages can be deleted only by the System Operator). 40. Should callers be allowed to send messages to ALL This parameter determines whether callers can send mail to ALL if the previous parameter was set to YES. A YES parameter here allows callers to send public messages to ALL instead of to a specific individual when mail can only be sent to registered users. This parameter reduces the volume of public mail that is not directed to callers who have been on the system before or who have not been preregistered by the System Operator. A NO parameter here will prevent callers from sending mail to anyone but registered users if the previous parameter was set to YES. 41. Alternative Operator name to use for mail check When TCOMM checks for the existence of new messages for a caller, it uses the exact name of the caller. When the System Operator accesses the system locally or remotely, TCOMM checks for new mail sent to the System Operator's first and last name specified in the first parameter in this profile. This alternative System Operator name parameter allows the System Operator to designate an additional name to use during the new mail check. The system expands the word SYSOP to the System Operator's first and last name when messages are written by callers, so it is unnecessary to enter the word SYSOP for this parameter. 42. Should mail be separated by group for the Operator This parameter allows the System Operator to elect to read all messages regardless of the current group access selection. A YES parameter here will allow the System Operator to read all messages regardless of the group designation of the messages without changing to each group first. A NO parameter here causes messages to be segregated for the System Operator the same way they are separated for normal callers; to read a message sent to the members of a group, the System Operator will first have to change access to that group at the Change Command menu. This parameter applies to local and remote System Operator access. 78 43. Maximum number of messages allowed This parameter designates the maximum number of messages the system will allow. If too many messages are allowed, the message storage disk will become full and system maintenance will be difficult to perform. A two dual-sided diskette system should limit the number of messages to 100, and the messages should not be located on the same diskette with upload or download files. For a large disk capacity system, the maximum number of messages can be large. The maximum number of messages in a fixed disk system is limited only by the disk capacity. An active system with 1500 registered users can average 500 active messages if the maximum number of messages is set higher than 500. TCOMM will limit messages if free disk space is less than 3000 bytes. The system needs some space to perform mail index maintenance when messages are deleted and will not allow the creation of new messages when free disk space drops below this margin. 44. Should automatic mail pack be performed This parameter allows the System Operator to reduce system maintenance by activating an automatic mail pack to be performed the first day of each month. A YES parameter will activate the automatic mail pack and messages that have been on the system longer than the period specified in the next parameter will be deleted. A NO parameter will deactivate the automatic mail pack. 45. Months of message retention before deletion Messages left on the system longer than this period will be automatically deleted the first day of each month if automatic mail pack has been activated. A typical duration for active messages is 3 months. 46. Should mail be automatically archived This parameter allows the System Operator to save a copy of all messages that are entered into the system. A YES parameter will cause TCOMM to keep a copy of each message; each new message will be appended to the end of the file specified in the next parameter. A NO parameter will deactivate the mail archive procedure. If this parameter is set to YES, the mail archive file must be periodically copied to a backup disk and the file deleted from the active disk. Failure to perform this maintenance will cause the active disk drive to become full and degrade the performance of the system. 79 47. Drive and name for mail archive file This parameter should contain the drive designation and the name of the file to be used during message archive operations, if the previous parameter was set to YES. The format of this parameter is as follows: drive:\subdirectory\archivefile For example, the designation C:\TCOMM\SYSTEM\ARC will place a copy of each message at the end of a file called ARC located on the C drive in the TCOMM\SYSTEM subdirectory. If space is limited on the drive that is to contain this file, it should be periodically copied to a diskette or another drive and deleted from the location specified here. If the file does not exist the first time a message is created, the file will be created by TCOMM. 48. Should automatic data base pack be performed This parameter allows the System Operator to activate automatic monthly user data base packing to reduce manual system maintenance. A YES parameter will cause automatic packing to occur the first day of each month and will delete inactive users according to the inactivity period selected by the System Operator. A NO parameter disables automatic data base packing. If NO is selected, the System Operator must perform periodic manual data base packing at the Operator Main Menu. 49. Months of inactivity before user is deleted This parameter allows the System Operator to select the period of user inactivity allowed before a user is purged from the system data base. The parameter is used by TCOMM when the System Operator manually performs a user data base pack or when TCOMM performs an automatic data base pack. 50. Should a backup copy of the data base be retained This parameter allows the System Operator to retain a backup copy of the user data base each time it is packed to remove inactive users or users marked for deletion. A YES parameter causes TCOMM to keep a backup copy of the old data base. A NO parameter prevents TCOMM from keeping a copy of the old data base. 51. Should system statistics be displayed at log in This parameter allows the System Operator to turn TCOMM operational statistics display on or off. If YES is selected, TCOMM will display the total number of callers that have accessed the system, the last message number left by a caller, and the 80 last message the current caller has read. These data are displayed just before the caller Main Command menu is displayed the first time during login. If NO is selected, these data are not displayed. YES is normally selected for public access systems, and NO is selected for closed private systems. 52. Should caller activity be displayed on screen This parameter determines whether caller activity is displayed during unattended TCOMM operation. Some System Operators, especially new ones, like to watch caller activity. Others like to turn off the display of caller activity most of the time. This Configuration Profile parameter allows the System Operator to choose to have local "snoop" on or off. A YES parameter will cause the system to display user activity as soon as the system answers the telephone. A NO parameter will cause the system to clear the screen a short time after system startup and keep the screen blank under all subsequent operating conditions. TCOMM allows the System Operator to temporarily override the default snoop condition with "snoop toggle" function key F9. This override allows the System Operator to turn the display of caller activity on and off; the override is reset to the Configuration Profile selected condition when the System Operator exits the system to DOS. The TCOMM display screen is protected from prolonged display burn-in. This is achieved by a time delayed clearing of the Function Control Key menu screen after the system is started and after the system recycles from a caller session. This temporary blanking of the screen is, however, independent of caller activity display. 53. Should callers be able to select graphics files This parameter determines whether callers are allowed to view graphics text files. A graphics file is a system text file with the letter 'G' as a filename extension. A YES parameter allows callers to view graphics versions of system text files if they dial in using 8 data bits and indicate they can display PC-DOS or MS-DOS characters during log in or at the TCOMM Change menu. If graphics are allowed and elected but a graphics system text file is not found, the normal nongraphics version of the file will be displayed. If NO is selected, TCOMM will not ask callers if they can display PC-DOS or MS-DOS characters during login, and caller selection of graphics at the Change menu will not result in graphics file displays. 81 54. Should user input data field widths be displayed If this parameter is set to YES, TCOMM will check to see if each caller can display cursor left properly during the log in procedure. If the caller's communications software moves the cursor left when it receives a Control-] (ASCII 029) character, then TCOMM will provide dots to indicate data field widths when the caller is asked for input. The cursor will be moved back to the first data field character position. If the caller's communications software cannot display cursor left or a NO parameter is entered here, data field widths are not displayed unless the field widths are critical--a series of dashes above the input field is used in these cases. 55. Should system welcome be interruptable This parameter allows the System Operator to determine whether the initial system welcome message is interruptable. A YES parameter allows callers to abort the welcome file display by entering a Control-K. A NO parameter will prevent callers from aborting the welcome file display. This parameter is used to force callers to read the welcome file during each log in. 56. Default user page length (24 for IBMPC) The default page length determines the number of lines TCOMM will display before paginating a file. TCOMM will display bulletin, menu, help, and message files one page at a time based on this page length parameter. If all users dial-in with computers that use only 16 line screen displays, then a value of 16 should be entered. The IBM PC monochrome and color monitors normally provide 24 lines of display when used with communications software. If you enter a value of 0 for page length, all file displays will be continuous. 57. Default user line width (10-80) The default line width determines the message editor line width. A value of 70 will cause automatic word wrap when text entry reaches column 71. This parameter should be set for 39 when all remote callers will be using 40 column monitors. 58. Security level required to enter the system This minimum caller security level required to enter the system is used to screen callers. If TCOMM is used as a closed system allowing access by registered users only, this parameter should be set to 1 or higher and the default security level of new callers (profile item number 59) should be set to 0. By using these parameters and limiting the number of registered users to less than 200, registered users will seldom get a busy signal 82 when they dial the system. If TCOMM is to be set up as an open public system, this parameter should be set to 1 and the default security level of new callers should be set higher than 1. 59. Access level assigned to new unregistered callers The security level assigned to new callers is used to screen callers and to control new caller command execution. If this value exceeds the minimum security level required to access the system, TCOMM is considered an "open system" because all callers are allowed access to the system. If this value is less than the minimum security level required to access the system, TCOMM is considered a "closed system" because unregistered new callers are not allowed system access. For new unregistered callers in an open system, this value will determine the system commands that can be executed by the caller. The caller will be allowed to execute commands that have security requirements equal to or less than this value. 60. Security level for Operator privileges The security level for Operator privileges is used to give callers other than the System Operator special system control. A caller with this security level will have the same remote access system command execution authority as the System Operator except exit to DOS which is controlled by a Configuration Profile parameter. A System Operator can authorize assistant System Operators by giving them this access level in the user data base. A high value is recommended for this parameter to ensure that only authorized callers get System Operator privileges; most System Operators give this parameter a value of 99. 61. Security level to read ALL private mail Callers with this security level can read all messages--public and private. This allows the System Operator to designate an assistant to help read and maintain system mail. A high value is recommended for this parameter to keep unauthorized callers from reading private mail intended for other callers. 62. Security level to enter Bulletin Subsystem This security level is used to control execution of the Bulletins command at the caller Main Command menu. Callers with access levels below this value will not be allowed access to the Bulletins Subsystem. 83 63. Security level to enter Change Subsystem This security level is used to control execution of the Change command at the caller Main Command menu. Callers with access levels below this value will not be allowed access to the Change Subsystem. 64. Security level to enter File Subsystem This security level is used to control execution of the Files command at the caller Main Command menu. Callers with access levels below this value will not be allowed access to the Files Subsystem. 65. Security level to enter Mail Subsystem This security level is used to control execution of the Mail command at the caller Main Command menu. Callers with access levels below this value will not be allowed access to the Mail Subsystem. 66. Security level to enter Operator Subsystem This security level is used to control execution of the Operator command at the caller Main Command menu. Callers with access levels below this value will not be allowed access to the Operator Subsystem. 67. Security level to enter Programs Subsystem This security level is used to control execution of the Programs command at the caller Main Command menu. Callers with access levels below this value will not be allowed access to the Programs Subsystem. 68. Security level to leave Comment for Operator This security level is used to control execution of the Comment command at the caller Operator Command menu. Callers with access levels below this value will not be allowed to leave private comments for the System Operator. 69. Security level to list system Description This security level is used to control execution of the Description command at the caller Operator Command menu. Callers with access levels below this value will not be allowed to list a description of the system. 84 70. Security level to Page Operator This security level is used to control execution of the Page command at the caller Operator Command menu. Callers with access levels below this value will not be allowed to page the System Operator. 71. Security level to Execute programs This security level is used to control execution of the Execute command at the caller Programs Command menu. Callers with access levels below this value will not be allowed to execute external programs made available by the System Operator. 72. Security level to Find string in programs menus This security level is used to control execution of the Find command at the caller Programs Command menu. Callers with access levels below this value will not be allowed to search for programs made available by the System Operator. 73. Security level to List programs menus This security level is used to control execution of the List command at the caller Programs Command menu. Callers with access levels below this value will not be allowed to list program menus made available by the System Operator. 74. Security level to list programs main Menu This security level is used to control execution of the Menu command at the caller Programs Command menu. Callers with access levels below this value will not be allowed to list the Program Subsystem main menu. 75. Security level to list New program menus This security level is used to control execution of the New command at the caller Programs Command menu. Callers with access levels below this value will not be allowed to search for new programs made available by the System Operator since the callers were on the system last. 76. Security level to Brief scan the mail This security level is used to control execution of the Brief command at the Mail Command menu. Callers with access levels below this value will not be allowed to list abbreviated scans of 85 Mail subsystem messages. 77. Security level to list recent Callers This security level is used to control execution of the Callers command at the Mail Command menu. Callers with access levels below this value will not be allowed to list recent system callers. 78. Security level to read mail From the user This security level is used to control execution of the From command at the Mail Command menu. Callers with access levels below this value will not be allowed to automatically search for mail left by them for other callers. 79. Security level to Read private and public mail This security level is used to control execution of the Read command at the Mail Command menu. Callers with access levels below this value will not be allowed to read private or public mail left for them by other callers or the System Operator. 80. Security level to Locate string in messages This security level is used to control execution of the Locate command at the Mail Command menu. Callers with access levels below this value will not be allowed to automatically search for a string of selected characters or numbers in messages headers. 81. Security level to Scan mail This security level is used to control execution of the Scan command at the Mail Command menu. Callers with access levels below this value will not be allowed to scan private or public mail left for them by other callers or the System Operator. 82. Security level to read mail sent To the user This security level is used to control execution of the To command at the Mail Command menu. Callers with access levels below this value will not be allowed to automatically search for mail left for them by other callers or the System Operator. 86 83. Security level to list system User information This security level is used to control execution of the Users command at the Mail Command menu. Callers with access levels below this value will not be allowed to list the names of registered system users. If you want callers to know the names of other system users in order to encourage the exchange of information, this security level should be set lower than normal caller access levels. 84. Security level to Write mail This security level is used to control execution of the Write command at the Mail Command menu. Callers with access levels below this value will not be allowed to create messages for other callers. 85. Security level to read messages Nonstop This security level is used to control execution of the Nonstop command at the Read Mail Command menu. Callers with access levels below this value will not be allowed to read messages nonstop starting at the current message. 86. Security level to Reply to messages This security level is used to control execution of the Reply command at the Read Mail Command menu. Callers with access levels below this value will not be allowed to reply to the message currently displayed. 87. Security level to Select next message to read This security level is used to control execution of the Select command at the Read Mail Command menu. Callers with access levels below this value will not be allowed to select the next message number to display after the message currently displayed. 88. Security level to Delete mail This security level is used to control execution of the Delete command at the Read Mail Command menu. A callers with an access level below this value will not be allowed to delete the message currently displayed unless the message was sent to or from the caller. Only callers that are to get System Operator privileges should be given this access level. 87 89. Security level to Find string in bulletin menus This security level is used to control execution of the Find command at the caller Bulletin Command menu. Callers with access levels below this value will not be allowed to automatically search for character strings in bulletin files. 90. Security level to List bulletins This security level is used to control execution of the List command at the Bulletin Command menu. Callers with access levels below this value will not be allowed to view the Bulletin Subsystem bulletin files. 91. Security level to list bulletin main Menu This security level is used to control execution of the Menu command at the Bulletin Command menu. Callers with access levels below this value will not be allowed to list the Bulletin Subsystem main menu. 92. Security level to list New bulletins This security level is used to control execution of the New command at the caller Bulletin Command menu. Callers with access levels below this value will not be allowed to search for new bulletins made available by the System Operator since the callers were on the system last. 93. Security level to Download files This security level is used to control execution of the Download command at the Files Command menu. Callers with access levels below this value will not be allowed to download files contained on the download disk drives. 94. Security level to Find files This security level is used to control execution of the Find command at the caller Files Command menu. Callers with access levels below this value will not be allowed to automatically search for character strings in download menu files. 95. Security level to List file download menus This security level is used to control execution of the List command at the Files Command menu. Callers with access levels below this value will not be allowed to list download menus contained on the download disk drives. 88 96. Security level to list file download main Menu This security level is used to control execution of the Menu command at the caller Files Command menu. Callers with access levels below this value will not be allowed to list the download file main menu. 97. Security level to list New file download menus This security level is used to control execution of the New command at the caller Files Command menu. Callers with access levels below this value will not be allowed to search for new download menus made available by the System Operator since the callers were on the system last. 98. Security level to Upload files This security level is used to control execution of the Upload command at the Files Command menu. Callers with access levels below this value will not be allowed to upload files to the upload disk drive. 99. Security level to overwrite files on upload This security level is used to control execution of the Upload command at the Files Command menu. Callers with access levels below this value will not be allowed to upload files using filenames that already exist on the system. This prevents callers from abusing the system by overwriting TCOMM system files. 100. Maximum security violations before disconnect This value determines the number of security breach attempts a caller is allowed before the system automatically reduces the caller's access level to zero and logs the caller off. Security breach attempts are defined as attempts to execute commands that are above the caller's access level (these commands do not appear on the caller's menus), too many password changes by the caller, and attempts to download system files that have 'TC' as a filename extension. The maximum number of security violations before disconnect should be set high enough to allow for some caller errors. If this value is set to one, a single caller command entry errors could cause the system to terminate a session. A value of 5 or higher is recommended for normal system use. 89 101. Maximum password attempts at log in This value determines the number of password entry attempts a caller is allowed before the system automatically logs the caller off. The maximum number of password attempts should be set high enough to allow for some caller errors. If this value is set to one, a single password entry error will cause the system to terminate a session. A value of 3 is recommended for normal system use. 102. Maximum password changes in a session This value determines the number of password changes a caller is allowed to make at the Change Command menu. The maximum number of password changes should be set high enough to allow for some caller errors. If this value is set to one, a single password change attempt will cause the system to produce an error message and record an attempted security violation. A value of 3 is recommended for normal system use. 103. Maximum caller records to keep in caller log The maximum number of caller records to keep in the caller log determines the size of the caller history file. The caller log contains recent callers names, locations, access dates and times, and communication parameters used. For diskette drive systems this value should be set to less than 50. For fixed drive systems, a value of 200 is recommended. 104. Maximum unattended system errors allowed The maximum unattended system errors allowed determines the number of errors the system should sustain before terminating operation. System errors can be caused by missing system files or improper disk drive designations in the Configuration Profile. A value of 10 should provide a margin for occasional errors. The activity log (LOG.TC) should be periodically reviewed at the Operator Main Menu for evidence of system errors. 105. Filename extension for system files This parameter contains the filename extension that TCOMM checks when a callers elects to download a file. Only callers with System Operator privileges are allowed to download files that have this extension because these files are assumed to contain sensitive system operation or caller data. Most System Operators use the letters TC to designate system files. 90 106. Filename for system caller log This parameter contains the name of the callers log file. The filename should have the filename extension designated in parameter 105 if you want to keep callers from downloading the file. This documentation manual assumes the filename is CALLERS.TC. 107. Filename for system user data base The user data base filename should be entered here. This file will contain sensitive user data and should not be made available for caller review and downloading. Use the filename extension designated in parameter 105 to prevent caller access to this file. This documentation manual assumes the filename is USERDATA.TC. 108. Filename for system status This parameter contains the name of the TCOMM status file. The status file will contain the number of the last message entered, the total number of callers that have accessed the system, and the last message number read by the System Operator. Use the filename extension designated in parameter 105 to prevent caller access to this file. This documentation manual assumes the filename is STATUS.TC. 109. Filename for system activity log The system activity log file will contain a list of all file downloads and uploads as well as system errors. This file will contain sensitive disk drive and filename information and should have the filename extension designated in parameter 105 to prevent caller access. This documentation manual assumes the filename is LOG.TC. 110. Filename for the mail index This parameter contains the name of the system message index file. Private mail information will be contained in this file and its filename extension should be the one designated in parameter 105 to preclude caller access. This documentation manual assumes the filename is MAILINDX.TC. 111. Prefix filename for bulletin files This filename is used for the Bulletins Subsystem master bulletin menu and the prefix for bulletin filenames. The name should pertain to bulletins for ease of system maintenance. The bulletin menu should refer callers to bulletins by number or letter. This 91 documentation manual assumes the filename is BULLET. 112. Prefix filename for download file menus This filename is used for the Files Subsystem master download menu and the prefix for download file menu filenames. The name should pertain to file menus for ease of system maintenance. The download menu should also refer callers to file menus by number or letter. This documentation manual assumes the filename is FILES. 113. Prefix filename for program file menus This filename is used for the Programs Subsystem master download menu and the prefix for program menu filenames. The name should pertain to program menus for ease of system maintenance. The program menu should also refer callers to program menus by number or letter. This documentation manual assumes the filename is PROG. 114. Name of public upload file menu This parameter contains the name of the public upload file menu. File information for public file uploads will be appended to this file. If callers are allowed to download recently uploaded files (the uploaded files go to a drive or subdirectory that is also designated for downloading), they will be allowed to list the contents of this file. This documentation manual assumes the filename is FILES99. 115. Name of private upload file menu This parameter contains the name of the private upload file menu. File information for private file uploads will be appended to this file. Private file transfer information will be contained in this file and its filename extension should be the one designated in parameter 105 to preclude caller access. Callers will not be allowed access to this file regardless of its location unless they have System Operator access privileges or know the name of the file. This documentation manual assumes the filename is FILES99.TC. 116. 1st file transfer protocol filename This is the name of the first file transfer protocol that will appear after the word Ascii in the protocol selection prompt displayed for callers during the file transfer procedure. TCOMM will display the name of the protocol only; the filename extension must be included with this parameter but will not be displayed in the protocol selection prompt. If a caller selects 92 this protocol at the protocol selection prompt, TCOMM will load and execute this external protocol program. If callers are to be allowed to perform only ASCII file transfers, no parameter should appear here. System Operators normally include at least XMODEM.EXE, CRCXMODM.BAT and YMODEM.BAT in addition to the built- in ASCII capability. Refer to Chapter 12 for more details on external file transfer protocols. 117. 2nd file transfer protocol filename This is the name of the file transfer protocol that will appear in the protocol selection prompt after the protocol designated in the above parameter. This and any subsequent file transfer protocol parameter can be left blank; TCOMM will skip blank parameters and add only those protocol filename parameters designated. . . . . . . 124. 9th file transfer protocol filename This is the last designation parameter for file transfer protocols. 125. Should modem be offhook after local exit to DOS This parameter allows the System Operator to select the modem offhook default condition after exit to DOS. Some System Operators like to leave the modem in an offhook condition when they exit to DOS so callers will get a busy signal; callers will think the system is busy and will call back later. A NO parameter causes TCOMM to reset the modem to factory default settings when the System Operator exits to DOS from the Operator Main Menu. A YES parameter causes TCOMM to leave the modem offhook when the System Operator exits to DOS from the Operator Main Menu. If the F1 function key is used to exit to DOS, the modem is always reset to factory default settings. 126. Should modem speaker be on during system operation This parameter allows the System Operator to select the modem sound default condition. Some System Operators like to hear the high-pitch modem carrier sound when the modem answers a call. Most System Operators find the sound annoying and prefer to have the sound turned off. The TCOMM default condition is for modem sound OFF. An ON parameter turns the speaker on. An OFF parameter turns the speaker OFF. 93 127. Should caller group designation be activated If the System Operator wishes to segregate callers into groups, this parameter should be YES. Group separation allows the System Operator to make the system appear different for each group. A software vendor can provide software support for more than one software package by separating software owners into groups. A company can also separate the system logically by departments or divisions. Custom bulletins and download menus can be set up. Messages can also be segregated by group. TCOMM allows a maximum of 9 private and a maximum of 19 public groups beyond the default "open system" group. Each group has a name and that name is used to locate bulletins and files for the group. The group name is used as a prefix subdirectory name for Bulletin, Program, and File Subsystem menus and files. For example, a group called STAFF will require a subdirectory named TCOMM\TEXT\STAFF for text files and a subdirectory named TCOMM\FILES\STAFF for download and upload operations. External programs available for execution also requires a subdirectory for each caller group. All messages go into one common message area. The mail index file keeps a record of the message sender's group designation and allows only members of the same group to read messages designated as public. The System Operator is prompted for a group name when a public message is posted; the System Operator can send a public message to a specific group or to all groups. 128. Should callers be placed in 1st registered group This parameter allows the System Operator to automatically direct callers to their private groups immediately after log in. If this parameter is set to YES and groups are activated, callers preregistered for at least one private group are placed in the first group recorded in their user data record. If this parameter is set to NO or groups are not activated, callers are placed in the "open group" after successful log in. Callers not preregistered for a private group are always placed in the "open group" after successful log in. 129. Private groups end with what group number (9 max) The System Operator can establish up to 9 private groups. This parameter determines the last group number that will be treated as private and the number cannot exceed nine. All group names recorded beyond this number will be considered public. Callers have to be preregistered for private groups in the user data base before they can change to these groups at the Change Command menu. Callers can change to public groups without preregistration. 94 130. 1st caller group name This is the group name for the first caller group. Callers are allowed to be members of up to six private groups. Callers that are designated for more than one private group in the user data base can change private groups during a session at the caller Change menu. If group one is a private group, the number 1 must appear in the group data field of a caller's user data base record before the caller can change to this group. If group one is a public group, any caller can change to this group without preregistration. To change to group one, this name must be provided by the caller after the Access command is executed at the Change Command menu. . . . . . . . 138. 9th caller group name This is the group name for the 9th caller group. This is the last caller group that can be designated as private. All groups beyond this number have to be public if they are used. Public groups can start at any group number from 1 to 9. Group numbers from 10 to 19 are always considered public. . . . . . . . . . 148. 19th caller group name This is the group name for the 19th caller group. This is the last public caller group number. 149. Program prompt for Main Command menu This parameter allows the System Operator to change the caller Main Command menu name to another name. The parameter entered here will replace the words 'Main Command' at the caller main menu when TCOMM operates. 150. Command name to enter Bulletin subsystem This parameter allows the System Operator to define the command required to access the Bulletin Subsystem. The parameter entered here will appear in the caller main menu when TCOMM operates. The 95 first letter of this command will be used to provide access to the Bulletins Subsystem. 151. Command name to enter Change subsystem This parameter allows the System Operator to define the command required to access the Change Subsystem. The parameter entered here will appear in the caller main menu when TCOMM operates. The first letter of this command will be used to provide access to the Change Subsystem. 152. Command name to enter Files subsystem This parameter allows the System Operator to define the command required to access the Files Subsystem. The parameter entered here will appear in the caller main menu when TCOMM operates. The first letter of this command will be used to provide access to the Files Subsystem. 153. Command name to Logoff This parameter allows the System Operator to define the command required to logoff TCOMM. The parameter entered here will appear in the caller main menu when TCOMM operates. The first letter of this command will be used to initiate logoff. 154. Command name to enter Mail subsystem This parameter allows the System Operator to define the command required to access the Mail Subsystem. The parameter entered here will appear in the caller main menu when TCOMM operates. The first letter of this command will provide access to the Mail Subsystem. 155. Command name to enter Operator subsystem This parameter allows the System Operator to define the command required to access the Operator Subsystem. The parameter entered here will appear in the caller main menu when TCOMM operates. The first letter of this command will provide access to the Operator Subsystem. 156. Command name to enter Programs subsystem This parameter allows the System Operator to define the command required to access the Programs Subsystem. The parameter entered here will appear in the caller main menu when TCOMM operates. The first letter of this command will provide access to the Programs Subsystem. 96 157. Program prompt for Bulletin Command menu This parameter allows the System Operator to change the caller Bulletin Command menu name to another name. The following parameters allow the System Operator to redefine the Bulletin menu commands: 158. Command name to Find a string in bulletin menus 159. Command name to List bulletins 160. Command name to list bulletin Menu 161. Command name to list New bulletins 162. Program prompt for Change Command menu This parameter allows the System Operator to change the caller Change Command menu name to another name. The following parameters allow the System Operator to redefine the Change menu commands: 163. Command name to change current group Access 164. Command name to Display user data 165. Command name to change Graphics mode 166. Command name to change Password 167. Command name to change screen Size 168. Program prompt for Files Command menu This parameter allows the System Operator to change the caller Files Command menu name to another name. The following parameters allow the System Operator to redefine the Files menu commands: 169. Command name to Download files 170. Command name to Find a string in file menus 171. Command name to List files available for download 172. Command name to list file download main Menu 173. Command name to list New download file menus 174. Command name to Upload files 175. Program prompt for Mail Command menu This parameter allows the System Operator to change the caller Mail Command menu name to another name. The following parameters allow the System Operator to redefine the Mail menu commands: 97 176. Command name to get a Brief scan of messages 177. Command name to list recent Callers 178. Command name to read mail From user only 179. Command name to Locate string in message headers 180. Command name to Read private and public mail 181. Command name to Scan messages 182. Command name to read messages directed To user 183. Command name to List all current system Users 184. Command name to Write a message 185. Program prompt for Operator Command menu This parameter allows the System Operator to change the caller Operator Command menu name to another name. The following parameters allow the System Operator to redefine the Operator menu commands: 186. Command name to leave Comment for operator 187. Command name to list system Description 188. Command name to Page the operator 189. Program prompt for Programs Command menu This parameter allows the System Operator to change the caller Programs Command menu name to another name. The following parameters allow the System Operator to redefine the Programs menu commands: 190. Command name to Execute programs 191. Command name to Find a string in program menus 192. Command name to List programs menus 193. Command name to list main programs Menu 194. Command name to list New program menus 195. Program prompt for Read Mail Command menu This parameter allows the System Operator to change the caller Read Mail Command menu name to another name. The following parameters allow the System Operator to redefine the Read Mail menu commands: 196. Command name to Continue reading messages 197. Command name to Delete messages 198. Command name to Modify message status 199. Command name to list messages Nonstop 200. Command name to Reply to a message 201. Command name to Select a message number 98 202. 1st caller name characters to disallow TCOMM will not allow a caller to use this parameter as a first or last name. The system will terminate caller log in if the caller uses this character string as a first or last name. This feature allows the System Operator to eliminate alias typically used by people who abuse public information systems. This parameter is limited to one word. TCOMM automatically disallows use of the word 'THE' as a first name, so the word 'THE' should only be listed here if you want it eliminated as a last name as well. . . . . . . . 210. 9th caller name characters to disallow This is the last word TCOMM checks against caller names during the log in process. 99 Chapter 10. System Security TCOMM provides a robust security system that allows flexibility in system set up and operation. The system can be configured for open public access or closed preregistered access. The system can also be configured to provide open access to some features and preregistered access to other features. The security system is divided into three major control areas as described in the following paragraphs. NEW CALLER LOGIN PRIVILEGES The Configuration Profile allows the System Operator to designate the new caller default login access privileges. The System Operator designates the default security level for people who are accessing the system for the first time. The System Operator also designates the caller security level required to execute system commands. TCOMM compares the caller security level to the security level required for command execution each time the caller enters a command. If the caller's security level is equal to or higher than the required security level for the command, TCOMM executes the command. If the caller's security level is lower than the required security level for the command, TCOMM responds with a message indicating that the caller's access level does not allow execution of that command. TCOMM provides two additional security measures based on caller access level. If a caller's access level is lower than the security level required to execute a command, the command is not displayed for the caller. If the caller reads the menu help file, identifies a command that does not appear on the menu, then tries to execute the command, an attempted security violation is assumed. If the total number of security violation attempts exceeds the maximum allowed attempts designated in the Configuration Profile, the caller is logged off the system and locked out--the caller's access level is reduced to zero. The System Operator can raise the caller's access level back to normal at a later date by using the data base management system. TCOMM can be set up as an open system allowing free access for new callers by setting the new caller security level equal to or higher than the security level assigned to TCOMM commands. For example, the new caller security level can be set to 5 and the access level required to execute all system commands can be set to 5. With this combination, the caller can execute all commands except those reserved for people with System Operator privileges (System Operator access level is set to 99 in the examples in this manual). This combination of security levels are shown in Figure 10-1. 100 Security level required to enter the system ...... 2 Access level assigned to new unregistered callers. 5 Security level for Operator privileges ........... 99 Security level to read ALL private mail .......... 99 Security level to enter Bulletin Subsystem ....... 5 Security level to enter Change Subsystem ......... 5 Security level to enter File Subsystem ........... 5 Security level to enter Mail Subsystem ........... 5 Security level to enter Operator Subsystem ....... 5 Security level to enter Programs Subsystem ....... 5 Security level to leave Comment for Operator ..... 5 Security level to list system Description ........ 5 Security level to Page Operator .................. 5 Security level to Execute programs ............... 5 Security level to Find string in programs menus .. 5 Security level to List programs menus ............ 5 Security level to list programs main Menu ........ 5 Security level to list New program menus ......... 5 Security level to Brief scan the mail ............ 5 Security level to list recent Callers ............ 5 Security level to read mail From the user ........ 5 Security level to Read private and public mail ... 5 Security level to Locate string in messages ...... 5 Security level to Scan mail ...................... 5 Security level to read mail sent To the user ..... 5 Security level to list system User information ... 5 Security level to Write mail ..................... 5 Security level to read messages Nonstop .......... 5 Security level to Reply to messages .............. 5 Security level to Select next message to read .... 5 Security level to Delete mail .................... 5 Security level to Find string in bulletin menus .. 5 Security level to List bulletins ................. 5 Security level to list bulletin main Menu ........ 5 Security level to list New bulletins ............. 5 Security level to Download files ................. 5 Security level to Find files ..................... 5 Security level to List file download menus ....... 5 Security level to list file download main Menu ... 5 Security level to list New file download menus ... 5 Security level to Upload files ................... 5 Security level to overwrite files on upload ...... 99 Figure 10-1. Open system configuration. TCOMM can be set up as a closed system allowing access for only preregistered callers by setting the new caller security level less than the security level assigned to TCOMM commands. For example, the new caller security level can be set to 2 and the access level required to enter the system can be set to 5 as shown in Figure 10-2. With this combination, the caller will be logged off the system as soon as a search of the user data base indicates the caller is not a preregistered user with an access level of 5 or higher. 101 Security level required to enter the system ...... 5 Access level assigned to new unregistered callers. 2 Security level for Operator privileges ........... 99 Security level to read ALL private mail .......... 99 Security level to enter Bulletin Subsystem ....... 5 Security level to enter Change Subsystem ......... 5 Security level to enter File Subsystem ........... 5 Security level to enter Mail Subsystem ........... 5 Security level to enter Operator Subsystem ....... 5 Security level to enter Programs Subsystem ....... 5 Security level to leave Comment for Operator ..... 5 Security level to list system Description ........ 5 Security level to Page Operator .................. 5 Security level to Execute programs ............... 5 Security level to Find string in programs menus .. 5 Security level to List programs menus ............ 5 Security level to list programs main Menu ........ 5 Security level to list New program menus ......... 5 Security level to Brief scan the mail ............ 5 Security level to list recent Callers ............ 5 Security level to read mail From the user ........ 5 Security level to Read private and public mail ... 5 Security level to Locate string in messages ...... 5 Security level to Scan mail ...................... 5 Security level to read mail sent To the user ..... 5 Security level to list system User information ... 5 Security level to Write mail ..................... 5 Security level to read messages Nonstop .......... 5 Security level to Reply to messages .............. 5 Security level to Select next message to read .... 5 Security level to Delete mail .................... 5 Security level to Find string in bulletin menus .. 5 Security level to List bulletins ................. 5 Security level to list bulletin main Menu ........ 5 Security level to list New bulletins ............. 5 Security level to Download files ................. 5 Security level to Find files ..................... 5 Security level to List file download menus ....... 5 Security level to list file download main Menu ... 5 Security level to list New file download menus ... 5 Security level to Upload files ................... 5 Security level to overwrite files on upload ...... 99 Figure 10-2. Closed system configuration. TCOMM can also be set up as a partially open system allowing access for all callers but allowing only preregistered callers to execute certain commands. For example, the new caller security level can be set to 2 and the access level required to execute normal system commands can be set to 2 or 5 as shown in Figure 10-3. With the configuration shown, new callers can only change default display parameters, read bulletins, read mail sent to them, and send comments to the System Operator. Preregistered 102 callers with access levels of 5 or higher can execute all commands except those reserved for the System Operator. Security level required to enter the system ...... 2 Access level assigned to new unregistered callers. 2 Security level for Operator privileges ........... 99 Security level to read ALL private mail .......... 99 Security level to enter Bulletin Subsystem ....... 2 Security level to enter Change Subsystem ......... 2 Security level to enter File Subsystem ........... 5 Security level to enter Mail Subsystem ........... 5 Security level to enter Operator Subsystem ....... 2 Security level to enter Programs Subsystem ....... 5 Security level to leave Comment for Operator ..... 2 Security level to list system Description ........ 2 Security level to Page Operator .................. 5 Security level to Execute programs ............... 5 Security level to Find string in programs menus .. 5 Security level to List programs menus ............ 5 Security level to list programs main Menu ........ 5 Security level to list New program menus ......... 5 Security level to Brief scan the mail ............ 5 Security level to list recent Callers ............ 5 Security level to read mail From the user ........ 5 Security level to Read private and public mail ... 5 Security level to Locate string in messages ...... 5 Security level to Scan mail ...................... 5 Security level to read mail sent To the user ..... 2 Security level to list system User information ... 5 Security level to Write mail ..................... 5 Security level to read messages Nonstop .......... 2 Security level to Reply to messages .............. 5 Security level to Select next message to read .... 5 Security level to Delete mail .................... 5 Security level to Find string in bulletin menus .. 5 Security level to List bulletins ................. 2 Security level to list bulletin main Menu ........ 2 Security level to list New bulletins ............. 2 Security level to Download files ................. 5 Security level to Find files ..................... 5 Security level to List file download menus ....... 5 Security level to list file download main Menu ... 5 Security level to list New file download menus ... 5 Security level to Upload files ................... 5 Security level to overwrite files on upload ...... 99 Figure 10-3. Partially open system configuration. 103 USER SECURITY LEVEL MODIFICATION The security level of callers can be altered after they have logged in for the first time. The System Operator can increase or decrease a caller's security level at the User Data Base Maintenance Menu. From the Operator Main Menu, the System Operator executes the Maintenance command to get to the data base. The System Operator then executes the Modify command to edit the user data fields. The System Operator can delete callers from the User Data Base Maintenance Menu. The Delete command changes the callers access level to 'D' and the caller's record will be eliminated from the data base when the Remove command is executed at the Operator Main Menu. The System Operator can lock out callers. The User Data Base Maintenance Menu provides a lockout command. Execution of this command changes the caller's access level to zero. A caller with a security level of zero will be denied access to the system. TCOMM drops the caller from the system by hanging up the telephone as soon as the caller's record is found in the data base. Locked out callers are not removed from the system data base during Remove and Pack operations; the System Operator has to change the caller's access level to a number greater than zero or to a 'D' (by using the Delete command) before the caller's record can be removed from the data base. PREREGISTERED USERS The User Data Base Maintenance Menu allows the System Operator to set up a list of preregistered users. The Add command allows the System Operator to enter the data fields for a user, including the user's security level. When the user calls the system for the first time, TCOMM will give him or her the security level entered by the System Operator. This security level can be modified at any time by the System Operator. The user cannot modify the security level. 104 Chapter 11. Caller Groups The System Operator can logically divide the system into caller groups. This allows the System Operator to separately communicate with two or more groups of people. It also allows separation of messages, bulletins, executable programs and upload/download files by group. This flexibility is necessary for software support of more than one product and for secure communications among the members of different groups in an organization. Caller groups are designated in two ways as described in the following paragraphs. CONFIGURING GROUPS The Configuration Profile is used to turn the group separation on and off and to establish the names and public/private status of groups. To turn group separation off, the following Configuration Profile setting is necessary: 127. Should caller group designation be activated ..... NO If a NO answer is provided at this prompt, the group designation is disabled and all callers will be placed in the default "open group" Bulletin, Programs, and Files Subsystems. All public messages will be placed in the default open group category--any caller with message read privileges can read these public messages. A YES parameter in the Configuration Profile activates the group separation of bulletins, programs, files and messages. At least one group name must be provided if groups are activated. If groups are activated, the System Operator can chose two other options. First, callers registered in the user data base for at least one group can be automatically placed in the first group that appears in their data base record. Second, the System Operator can setup both private and public groups. Callers have to be preregistered for private groups; callers may change to public groups without prior registration. A maximum of nine groups can be designated as private and the remaining groups can be public. All of the Configuration Profile group parameters are shown in Figure 11-1. 105 Should caller group designation be activated ..... Should callers be placed in 1st registered group . Private groups end with what group number (9 max). 1st caller group name ............................ . . . 19th caller group name ........................... Figure 11-1. Configuration Profile group prompts. Group names are used by TCOMM to locate the programs and files reserved for the groups. The group names have to be used as disk drive subdirectory designations on the drives or in the directories for system text files, executable programs, system upload files and system download files. For example, a fixed disk system with open access for some callers and closed access for a group called TEACHERS will have the Configuration Profile settings shown in Figure 11-2 and the disk directory names shown in Figure 11-3. If subdirectories are not setup for all groups, file access errors will occur and error messages will appear in the system activity log. These file access errors will also be reported to callers and can cause confusion. Be sure all group subdirectories are setup to eliminate this confusion. Should caller group designation be activated ..... YES Should callers be placed in 1st registered group . YES Private groups end with what group number (9 max). 9 1st caller group name ............................ TEACHERS Figure 11-2. TEACHERS group profile parameters. c:\tcomm\system all system files c:\tcomm\messages all message files c:\tcomm\text open access text files c:\tcomm\text\teachers text files for TEACHERS group c:\tcomm\prog open access executable programs c:\tcomm\prog\teachers program files for TEACHERS group c:\tcomm\files open access download files c:\tcomm\files\teachers download files for TEACHERS group c:\tcomm\files open access upload files c:\tcomm\files\teachers upload files for TEACHERS group Figure 11-3. Disk drive subdirectories for groups. The files to be accessed only by the TEACHERS group should be 106 located in the TEACHERS subdirectories. Callers not designated in the user data base as members of the TEACHERS group will not be allowed access to these files. Callers not preregistered for the TEACHERS group are placed in a default open group status when they log in. Callers designated as members of the TEACHERS group will be given automatic access to the TEACHERS group when they log in. These callers can change to the open group at the Change Command menu or remain in the TEACHERS group throughout the session. Callers registered for more than one private group can change from one group to another using the Access command at the Change menu; the groups available to the caller are listed when the Access command is executed. After changing to a particular group, a caller can access files and messages reserved for that group. USER DATA BASE GROUP DESIGNATION Users are assigned to groups at the User Data Base Maintenance Menu. A user record can be created and a group designation established. A user record associated with someone who has already dialed into the system can also be modified to add group designation. The Add command is used to create new records. The Modify command is used to modify records of existing users. The group designation in the data base should match the group numbers in the Configuration Profile. If a caller is to access the first and third groups, the data base group designation should be as follows: Group |13 | A maximum of six group designations are allowed for each user. The numbers may be in any order and should not be separated by spaces or other symbols. When a caller requests a change to a new caller group, TCOMM first checks to see that the caller group name matches one of the names in the Configuration Profile. If the group name does not exist, TCOMM displays an error message. If the group name appears in the Configuration Profile but does not match one of the caller's group number designations stored in the user data base, an error message is displayed. If the group name is legitimate and matches one of the current caller's group number designations, the caller is given access to the new group bulletins, programs and files. A caller can read all of his or her incoming or outgoing mail regardless of the caller group attachment. The To and From commands at the Mail Command menu provide this capability. A caller can only read public mail, however, when it is directed to callers in one of his or her group designations. For example, a caller designated for groups 1 and 3 can only read public mail sent to caller groups 1 and 3 and mail sent to members of the open group. Public mail sent to other groups can only be read by members of those groups. To read public mail directed to a group 107 using the Read command, a caller has to switch to that group using the Access command at the Change Command menu. When a caller has changed to a group designation, all public messages sent by that caller will be directed to the members of that group. If a caller wants to send messages to more than one group, the caller will have to change to each group name before sending messages to that group. The System Operator is allowed more power and flexibility in the mail system than normal callers. The System Operator can send a public message to any group without changing access to that group; the System Operator is prompted for a group name when a message is specified as public. The System Operator may also read all messages regardless of their group designation. If the System Operator has elected in the Configuration Profile to keep his or her mail segregated by group, then the System Operator has to change access to each group at the Change Command menu before messages directed to the group can be read. If the System Operator has not elected to segregate messages, then the System Operator can read all mail regardless of group designation without changing group access. Group separation and security levels can be combined to provide a flexible and powerful caller support system. The System Operator's imagination is the only limit to the application of these controls. 108 Chapter 12. External File Transfer Protocols TCOMM allows the System Operator to easily add file transfer protocols to the system at any time. File transfer protocols tend to change and improve with time. TCOMM is designed to allow this change to take place without system owners having to depend upon anyone for complete file transfer protocol support. The TCOMM software package includes the Xmodem and Kermit protocols, but system owners can replace these protocols with new versions or modified versions of the same protocols. The System Operator can also write and add special purpose protocols to the system. LOCATION OF PROTOCOLS File transfer protocols are designated in the Configuration Profile. The ASCII screen capture technique of file transfer is built into the main TCOMM.EXE program file. All other file transfer protocols are treated as external executable files. TCOMM expects these files to be on the system drive and in the system subdirectory for proper execution; all protocol program files must be located on the same drive and in the same directory with the TCOMM.EXE file. During the initial installation and setup of TCOMM, the Xmodem, Crcxmodem and Ymodem protocols are automatically copied to the system drive and directory. The designations for these protocols are also included in the Configuration Profile. If the System Operator wants to add other file transfer protocols to the system, the protocol files must be copied to the proper drive and directory, and the new protocol designations must be added to the Configuration Profile. This applies to the Kermit protocol included on the Protocol Source Code diskette. DESIGN OF PROTOCOLS Because of its popularity, the Xmodem protocol is used as an example of the techniques used in the development of external protocols. The source code for the executable Xmodem file is included on the Protocol Source Code distribution disk. From this source code you can see how information is passed from the main program file to the protocol. You can also see the information creation process that must be followed to provide the TCOMM.EXE file the data it needs to properly record file transfer information after the protocol program completes execution. When wildcard file uploads and downloads are supported in a protocol, the file data for each file transferred must be stored on the disk in the XFERSISE file with a carriage return and linefeed at the end of each line of file data. TCOMM reads this file when the transfers have been completed to update system information files. 109 The Xmodem source code is written in 'C' and is compatible with the Lattice compiler. Protocol programs can be written in any language that provides asynchronous communications support for the IBM PC family of Personal Computers. Compiled and interpreter languages can be used. The C source code comments provide tips on the techniques used in communications, but these techniques may vary from one language to another. The protocol writer is responsible for the proper design, development, coding and testing of a protocol before callers are allowed to execute the protocol through TCOMM. Failure to perform protocol development properly can result in confusion and frustration for system callers and should be avoided. The protocol program writer can make certain assumptions about the environment when a protocol starts. Protocol programs can assume that TCOMM has already initialized the communications port designated in the Configuration Profile. Programs written in BASIC should use the OPEN statement to simultaneously setup communications buffers and initialize the communications port. Protocol programs should assume that the communications carrier signal already exits between TCOMM's modem and the remote caller's modem. Protocol programs should also frequently check to be sure the carrier signal is still present; this is usually done any time input is expected from the remote system. If the carrier signal is lost, the protocol program should automatically create the file transfer data needed by TCOMM then exit to PC-DOS. TCOMM will resume operation when the protocol exits to DOS. TCOMM rebuilds its required working environment when a protocol program terminates. Communications interrupts are reset and communication buffers are setup. TCOMM also takes the file transfer information provided by the protocol and enters information into the system activity log and, if necessary, in the file upload menu. If the protocol does not properly create the FILESIZE file documented in the Xmodem source code, TCOMM will be unable to record file transfer information properly. 110 Chapter 13. Problem Diagnosis System operational problems become apparent in three ways. During initial system startup, Configuration Profile data errors may cause the system to fail. During normal system operation, errors may occur; a record of these errors will appear in the Activity Log. Errors may also be reported by system callers. The following paragraphs will help you solve these problems. FINDING A SOLUTION Some errors may have obvious causes and the corrective procedures may be simple. For example, a disk drive read/write error may be caused by a drive door left open. The System Operator easily solves this error by closing the drive door. Other errors such as system files not found during normal operation may require more diagnosis before a solution is discovered. The first step in solving a system problem is understanding the circumstances that contributed to the error. A review of the Activity Log will indicate file upload and download activity that existed before an error occurred. The pattern of file activity may help identify the problem. If a problem is reported by a caller, you should request a complete description of the caller actions that caused the error. If you witness an error during caller access or during your own system access, note the specific actions that produced the error. The solutions to typical TCOMM errors are described in the following paragraphs. A list of system error messages is also shown in Appendix C. MISSING FILES If TCOMM is unable to find a file, an error message is generated. If the error is caused by a caller request for a bulletin or download file that does not exist, ignore the error. If the error indicates that a system file or message file could not be found, the error should be investigated. Missing system files are usually caused by a Configuration Profile parameter entry error or a file location error. TCOMM searches for files on drives and in subdirectories as designated in the Profile. If files are not located or named as designated in the Profile, an error message will occur. Some errors such as a missing mail file index will also cause a TCOMM subsystem to malfunction. Carefully check the Configuration Profile and the location and names of files to be sure they agree before seeking other solutions. 111 SYSTEM CONFIGURATION PROBLEMS Configuration Profile data may generate errors beyond files not found. Incorrect data entry could cause both error messages and system malfunction. For example, incorrect designation of the asynchronous port number will cause system startup to fail. Other errors such as incorrect Operator office hours will simply cause system functions to improperly execute. Carefully check each Configuration Profile parameter to be sure all parameters have been entered correctly. SOFTWARE INCOMPATIBILITES Some software combinations will cause TCOMM to malfunction. This type of error is usually associated with resident background software such as print spoolers and pop up utility functions. These background tasks can interfere with the hardware or software interrupt services TCOMM is designed to use. If problems such as high file transfer errors occur when this type of software is in use, the software should be removed and TCOMM restarted. If TCOMM runs properly after the background software is removed, the background software should not be loaded and operated concurrent with TCOMM operation. HARDWARE CONFIGURATION The IBM Personal Computer hardware should conform to the requirements specified in Chapter 2. Any deviations from these requirements could cause TCOMM errors or malfunction. Selecting the wrong modem, for example, could cause TCOMM to ignore incoming calls. 112 Chapter 14. Who To Call If you have difficulty getting TCOMM up and running or you experience problems with the software, please read this manual again before calling for help. Almost all the questions received to date have been answered in the documentation manual. A great deal of effort went into the development of this documentation. It could save you time and efforts to read it carefully. A TCOMM system is operated in the Washington, DC area to answer questions and provide software support. The system operates 24 hours a day. The TCOMM support data line number is as follows: 301-428-7931 (data line) If the system does not respond or the number rings busy, try redialing the number using the automatic redial feature of your communications software. 113