TOPS-20 User's Guide - Chapter 3 Communicating with other users
home PDP-10 TOPS-20 User's Guide Prev: Chapter 2 Communicating With The System Next: Chapter 4 File specifications

Chapter 3 Communicating with other users

This chapter describes:

  1. Getting a list of users on the system
  2. Linking with other terminals
  3. Reading mail
  4. Sending mail
  5. Sending quick messages
  6. Communicating with the operator
  7. Controlling messages and terminal links

top

3.1 Getting a list of users on the system

To get a list of users currently on the system, type the command SYSTAT, and press the RETURN key. The SYSTAT command reports on the status of the system:

        @SYSTAT
         Mon 26-May-88 15:25:55  Up 6:09:39
         12+5 Jobs   Load av   0.13   0.10   0.06

        Job  Line Program  User
          9   120  EMACS   TAMBUR
         11   251  MACRO   GUNN
         12   131  FILDDT  MARTIN
         13   176  EXEC    GREEN
         14   140  MS      SULLIVAN
         26    63  SYSDPY  DEUFEL
         27   173  EXEC    BERRY
         33   DET  EXEC    MORIL
         34    65  EMACS   WORLEY
         45   142  EXEC    HARAMUND
         50*  210  SYSTAT  MORIL
         51   105  EXEC    BRANNON

          1   232  PTYCON  OPERATOR
          2   233  JNPGPD  OPERATOR
          3   234  EXEC    OPERATOR
          4   235  NMLT20  OPERATOR
          5   236  MCBNRT  OPERATOR

The first line of output gives the day of the week, date, time, and the length of time since the system was last started. In the above example, the date is Monday, May 26, 1988 at 3:25:55 PM. The system has been up just over six hours.

The second line gives the number of user jobs plus the number of operator jobs. There are 12 timesharing jobs, plus the operator of the system who is running 5 programs. The last three numbers on this line indicate the load average on the system over a one, five, and fifteen minute period. The load average is a measure of system demand.

The third line contains the column headings for the job number, the line number, the program, the user, and the user's originating system. The number of the job attached to your own terminal (in this case you are job 50) appears with an asterisk (*) next to it in the job column.

To display information about the jobs on a specified node in the TOPS-20 cluster, include the NODE keyword and node name argument.

        @SYSTAT NODE KL2102
         Thu 13-Aug-88 13:08:12
         THEP Up    0:10:33 17+6 Jobs   Load av   0.11   0.12
         Job  Line Program  Node    User             Origin
         231   DET  DTRSRV  KL2102 Not logged in
         232   DET  RMSFAL  KL2102 Not logged in
         233   DET  RMSFAL  KL2102 Not logged in
         234   434  EXEC    KL2102 LOMARTIRE         LAT1(LAT)
          .
          .
          .
         228   235  MAILS   KL2102 OPERATOR
         229   236  WATCH   KL2102 OPERATOR
         230   237  EXEC    KL2102 OPERATOR

If you specify an asterisk as the node name, the SYSTAT command displays information on all nodes in the TOPS-20 cluster.

  
        @SYSTAT SYSTEM NODE *
         Thu 13-Aug-88 13:02:00
         DISNEY Up 223:12:12 17+6 Jobs  Load av  0.3    0.27   0.14
         THUP   Up   0:10:33 11+5 Jobs  Load av 10.36  10.27  10.14
         CLYDE  Up  26:34:31  6+8 Jobs  Load av  1.33   1.21   0.99
         CONRO  UP  12:13:14  2+5 Jobs  Load av  5.01   4.95   4.99

top

3.2 Linking with other terminals

One way to communicate with a user that is logged-in to the system is by linking terminals. This allows you to conduct a two-way conversation. To link terminals, give the TALK command followed by the name of the user you want to talk to. The system prints a message informing you that the terminals are linked, and prints the @ sign on the following line. Now, everything you type, or the system prints on your terminal is also printed on the terminal you are linked with.

        @TALK (TO) MAYO

        LINK FROM SARTINI, TTY26

After you see the @ sign, you can conduct your conversation using one of the following options: an exclamation mark, the REMARK command, or a combination of both options.

Begin each line you type with an exclamation point (!). After you press RETURN, the system prints an @ sign on the following line and you can continue typing, beginning each line with an exclamation point. If you do not begin the line you type with an !, after you press RETURN, the system prints the message ?UNRECOGNIZED COMMAND.

        @TALK (TO) MAYO

        LINK FROM SARTINI, TTY26
        @! This is a test.

To avoid typing the exclamation point on each line when you have several lines of text, give the REMARK command. After you give the REMARK command, the system prints a message advising you to type the remark, and end it with CTRL/Z. The system does not print an @ sign when you use REMARK. After you type the message and end with CTRL/Z, the system prints the @ sign on the next line.

        @TALK (TO) MAYO

        LINK FROM SARTINI, TTY26
        @REMARK
        Type remark. End with CTRL/Z

        PER YOUR REQUEST, A NEW COPY OF THE
        UPDATED LIST OF MANUALS IS AVAILABLE
        IN THE DIRECTORY <NEW-MANUALS>. ^Z

You can use a combination of the exclamation point and the REMARK command when you TALK with another user. Use REMARK for a several line comment and the ! for a shorter comment. To end the link with another user's terminal, give the BREAK command. The other user can also give the BREAK command to end the link with your terminal.

        @TALK (TO) MAYO

        LINK FROM SARTINI, TTY26
        @REMARK
        Type remark. End with CTRL/Z.

        PER YOUR REQUEST, A NEW COPY OF THE
        UPDATED LIST OF MANUALS IS AVAILABLE
        IN THE DIRECTORY <NEW-MANUALS>. ^Z
        @!THANKS, I HAVE SEVERAL ITEMS TO ADD TO THE LIST.
        @!SEND MAIL TO HOLLAND WITH THE INFO.
        @BREAK (LINKS)

When you are linked to another user's terminal, the other user's job is not affected by what you type. For example, if another user is running a program that is waiting for a command, and you TALK to that user, the system does not interpret what you type as a command to that user's program. Anything output to one terminal is output to the other as well. Thus you can show another user the output from a program by running it, or the contents of a file by typing it.

If the user you want to TALK to does not want to receive links from another terminal, the system rings the bells on both terminals five times, then prints the following message on your terminal:

        ?Refused, Send mail to user instead

Refer to Section 3.7, Controlling Messages And Terminal Links, for information on refusing and receiving links.

If the user you want to TALK to is not logged in, the system prints the following message:

        ?User is not logged in
         Send mail to the user instead

top

3.3 Reading mail

There are two types of mail that you can receive at your terminal: mail from the system and mail from other users. You can receive system and user mail when you are logged in or logged off the system.

top

3.3.1 System Mail

System mail is sent to all users on the system by the operator or a privileged user. This type of mail automatically prints on your terminal when you log in.

        TOSCA, Computer Engineering, TOPS-20 Monitor 7.0(7)
        @LOGIN (USER) SARTINI (PASSWORD)___ (ACCOUNT) 341
         Job 57 on TTY127 16-MAR-88 09:49:24
         Date:  16-MAR-1988 0842-EST
         From:  OPERATOR at TOSCA
         To:  SYSTEM
         Subject:  SYSTEM SHUTDOWN

        The system will not be available tomorrow from noon to 2:00  p.m.
        due to scheduled maintenance.

When system mail is sent while you are logged in, you are notified with the message:

        [New message-of-the day available]

To read the new message of the day, use the INFORMATION MAIL SYSTEM command:

        @INFORMATION MAIL SYSTEM
        Sender: OPERATOR
        Date: 23 Jul 88, 1033-EST
        From: OPERATOR
        To: SYSTEM at KL2102
        Subject:  Lineprinter paper

        A new shipment of lineprinter paper is now available  for  anyone
        who needs to replenish paper.

top

3.3.2 User Mail

User mail is mail sent to you by another user on your system or a system in your network. When you log in, you are notified of new mail with a message similar to:

        You have mail from COMBS at 08:18:13

When user mail arrives while you are logged in, you are notified with a message similar to:

  
       [You have netmail from COMBS@GIDNEY at 14:40:56]

The program that you can use to read messages sent to you by another user is DECmail/MS. (For complete information on the DECmail/MS program, refer to the TOPS-10/TOPS-20 DECmail/MS Manual).

To start the DECmail/MS program, type MS and press RETURN. The system prints:

        @MS
         Last read:23-Apr-88 13:00.  24 messages, 5 pages.
         Message 19 flagged.
        MS>

The lines that appear between the MS command and the MS> prompt give you the status of your mail file.

To read any unread messages in the current message file, use the READ NEW command:

        MS>READ (MESSAGE SEQUENCE) NEW
        Message 24 (261 chars), received 23-Apr-88 22:46:35
        Date: 23 Apr 1988 2248-EDT
        From: MORRILL at KL2102
        To: RANDERSON at KL2102
        Subject: Project Meeting
        Message-ID: <"MS10(2055)+GLXLIB1(1056)" 11818792562.11.542.18243
        at KL2102)
   
        There will  be  a  project  meeting  today  at  4  p.m.   in  the
        Engineering Conference Room.
           ========
        MS read>>

This command displays all messages in the current message file that you have not read. After the READ command displays a message, it leaves your terminal at read-command level, as indicated by the "MS read>>" prompt. Press the RETURN key to read the next new message (or to return to the MS> prompt if there are no other new messages).

To read any of the messages again, use the READ command at the MS> prompt or at read-command level.

        MS>READ (MESSAGE SEQUENCE) message sequence
or
        MS READ>>READ
where: message sequence specifies the messages you want to read. At read-command level, it is assumed that you want to reread the current message.

Mail you receive from other users is contained in a file called MAIL.TXT. Although the mail program locates this file automatically, you should be aware of its location. This is described in Section 4.6.2, The Device POBOX:.

top

3.4 Sending mail

Another way to communicate with a user is to send mail with the DECmail/MS program. DECmail/MS handles local and network mail, which goes to users of different (remote) computers. DECmail/MS also provides facilities for filing, retrieving, editing and deleting mail messages.

You can send mail to a user currently on the system, or to a user who is not logged in. The DECmail/MS program can also send mail to a group of users. To start the DECmail/MS program, type MS and press RETURN; the system prints MS>. Type the SEND command. After you give the SEND command, the DECmail/MS system prompts you for the "To". Type the user name or names (if you type a group of user names, separate them with commas); the system prints cc:. Type the name(s) of the user or users you want to receive a copy of the mail; the system prints Subject:. Type a one-line heading for the message.

        MS>SEND
        To: PORADA, MORRILL, MCELMOYLE
        cc: BROPHY
        Subject: SYSTEM CHANGES

Now, the DECmail/MS system types the following help message on your terminal:

       Message (ESC  to  enter  Send  level, ctrl/Z  to  send, ctrl/K to
               redisplay, ctrl/B to insert file, ctrl/E to enter editor):

After the DECmail/MS system types the help message, anything you type (other than ESC and the control characters) is assumed to be the text of your message.

Type a line of text and issue CTRL/Z to send the message:

        THERE IS A LIST OF THE NEW SYSTEM
        CHANGES AVAILABLE IN THE PROJECT
        ROOM.
        ^Z

The DECmail/MS system types information similar to the following, letting you know that the message was successfully sent:

        Processing mail...
        Mail queued for delivery by MX
        MS>

If you send mail frequently to a group of users, store the list of names in a file. Then, when you run the DECmail/MS program, instead of typing the entire list of names after the To:, you can type the name of the file, preceded by an @ sign. (Refer to Chapter 4 for information on specifying files and to Chapter 5 for information on creating files.)

        MS>SEND
        To: @USERS.LST
        CC:
        Subject:

For a complete description of the DECmail/MS program, refer to the TOPS-10/TOPS-20 DECmail/MS Manual.

top

3.5 Sending quick messages

Another way to communicate with a user who is logged in to the system is to send a message with the SEND command. To send a message, give the SEND command followed by the user name and a message with up to six 80-character lines of text. The system prints your user name, terminal line number and message on the receiving terminal.

SEND does not detect the status of the receiving terminal. So, if the receiving terminal is turned off or the user is not logged in, the message cannot be received. Before you SEND a message, use the SYSTAT command to verify that the receiver is logged in to the system.

The following example illustrates the SYSTAT command and the SEND command:

        @SYSTAT KISTLER
          10    11  EXEC     KISTLER
        @SEND KISTLER Are you on the North project interest list?

To type a multiple line message, just keep typing past the end of the line and onto the next line without typing RETURN. SEND reorganizes your message so that words split between two lines appear correctly formatted on the receiver's terminal.

        @SEND KISTLER The North project team meets every Friday at 9 in 
        the Lunar Conference Room.

The message appears on the receiver's terminal as:

        From LEOPOLD on line 11:
        [The North project team meets every Friday at 9 in the Lunar
         Conference Room.]

To send a message to a user on a remote node in the TOPS-20 cluster, specify the /NODE: switch:

        @SEND /NODE:THUP ANDERSON Don't forget the meeting!

top

3.6 Communicating with the operator

To communicate with the operator on your system, use the PLEASE program. This program allows you to conduct a two-way conversation with the operator or send the operator a one-way message.

To use the PLEASE program, type PLEASE and press RETURN. PLEASE then prints a message instructing you to type your message and end it with CTRL/Z or ESC. Now, type your message. If you need a response from the operator, end your message by typing CTRL/Z. If you just want to send a one-way message to the operator and do not need a response, end your message by pressing ESC.

In the following example, you need a response from the operator, so you end your message with CTRL/Z. Then, when your dialog with the operator is finished, press ESC.

        @PLEASE
        Enter text, terminate with CTRL/Z to wait for response,
        or ESCape to send message and exit
        What happened to the RP07?<CTRL/Z>
        [PLSOPN Operator at GIDNEY has been notified at 11:18:32]

        11:36:04 From Operator at terminal 2
             => Just aligning the heads - back up in 10 minutes

        Enter new text (Same terminators)

        Thanks<ESC>

In this example you don't need a response from the operator so you press ESC after your message:

        @PLEASE
        Enter text, terminate with CTRL/Z to wait for response,
        or ESCape to send message and exit
        The laser printer is out of paper<ESC>
        [PLSOPN Operator at GIDNEY has been notified at 11:18:32]
        @

If your PLEASE message exceeds one line, press RETURN at the end of the line and continue typing on the next line.

If no operator is in attendance, PLEASE warns you before you can type your message. Your message is still sent and can be answered by the operator when he returns. However you should end your message with ESC, since it may be a long wait before it is answered. To find out if the operator is in attendance before you use the PLEASE program, give the INFORMATION SYSTEM-STATUS command.

For a complete description of the PLEASE program, refer to the TOPS-20 User Utilities Guide.

top

3.7 Controlling messages and terminal links

Several types of messages can appear on your terminal while you are running a program or executing a TOPS-20 command. In addition, another user can link his terminal to yours with an ADVISE or TALK command. You can allow or suppress types of messages and terminal links. This lets you work without interruption or print a clean copy of a file on a hard copy terminal.

top

3.7.1 System Messages

System messages are messages of general interest to all users. These messages are sent by the system, by the operator, or by a privileged user. Some examples of system messages are:

        [Caution -- disk space is low]
        [System going down in 1 minute!]
        [Deleted files will be expunged in 30 seconds]
        [System expunge completed]

You can specify if you want to receive or refuse system messages on your terminal with the RECEIVE or REFUSE SYSTEM-MESSAGES commands. Note that these commands also control the notice of new mail.

To see if your terminal is set to RECEIVE or REFUSE SYSTEM-MESSAGES, give the INFORMATION TERMINAL command. Then give the REFUSE SYSTEM-MESSAGES command to suppress system messages.

        @INFORMATION (ABOUT) TERMINAL-MODE
            .
            .
         REFUSE LINKS
         REFUSE ADVICE
         RECEIVE SYSTEM-MESSAGES
         RECEIVE USER-MESSAGES
            .
            .
        @REFUSE SYSTEM-MESSAGES
CAUTION

Since some system messages report important events, you should use the REFUSE SYSTEM-MESSAGES command only when you need to produce uninterrupted output (such as on a hard-copy terminal). Remember to set your terminal back to RECEIVE SYSTEM-MESSAGES after the output is complete.

top

3.7.2 User Messages

User messages occur when another user issues a SEND command to send a message to your terminal:

        From SMITTY on line 24:
        [Going to lunch?]

You can specify if you want to receive or refuse user messages on your terminal with the RECEIVE or REFUSE USER-MESSAGES commands. In the following example, check to see if your terminal is set to RECEIVE or REFUSE USER-MESSAGES with the INFORMATION TERMINAL command. Then give the RECEIVE USER-MESSAGES command to accept user messages.

        @INFORMATION (ABOUT) TERMINAL-MODE
         TERMINAL VT100
            .
            .
            .
         RECEIVE LINKS
         REFUSE ADVICE
         RECEIVE SYSTEM-MESSAGES
         REFUSE USER-MESSAGES
            .
            .
            .
         TERMINAL FULLDUPLEX
        @RECEIVE USER-MESSAGES

top

3.7.3 Terminal Links

Terminal links occur when another user gives a TALK or ADVISE command to link his terminal to yours:

        LINK FROM PRATT, TTY 123
        !Do you still have my pack?

You can stop another user from linking his terminal to yours with the REFUSE LINKS command. In the following example, check to see if your terminal is set to RECEIVE or REFUSE LINKS with the INFORMATION TERMINAL command. Then give the REFUSE LINKS command.

        @INFORMATION (ABOUT) TERMINAL-MODE
         TERMINAL VT100
            .
            .
            .
         RECEIVE LINKS
         REFUSE ADVICE
         RECEIVE SYSTEM-MESSAGES
         REFUSE USER-MESSAGES
            .
            .
            .
         TERMINAL FULLDUPLEX
        @REFUSE LINKS

Note that if you set your terminal to REFUSE LINKS and another user attempts to TALK to you, the system signals you by ringing bells on your terminal five times.

top

3.7.4 Inhibiting All Non-Job Output

The TERMINAL INHIBIT command stops your terminal from accepting links, system-messages and user-messages; in other words, all output that does not originate from your own job. Use this command when you need to protect your terminal from unwanted output, for example, when printing a file on a hard copy terminal.

TERMINAL INHIBIT essentially has the same function as REFUSE LINKS, SYSTEM-MESSAGES and USER-MESSAGES. However, TERMINAL INHIBIT blocks all links and messages before they can be rejected or accepted by your REFUSE and RECEIVE settings. Therefore, when TERMINAL INHIBIT is in effect, your REFUSE and RECEIVE settings are disabled. Note that in the INFORMATION TERMINAL-MODE display below, a "IS DISABLED" comment follows each REFUSE and RECEIVE setting.

To block all terminal output that does not originate with your job, give the TERMINAL INHIBIT command. Then, check the result with the INFORMATION TERMINAL command.

        @TERMINAL INHIBIT 
        @INFORMATION (ABOUT) TERMINAL-MODE
         TERMINAL VT100
            .
            .
            .
         TERMINAL INHIBIT (NON-JOB OUTPUT)
         REFUSE LINKS IS DISABLED
         REFUSE ADVICE IS DISABLED
         RECEIVE SYSTEM-MESSAGES IS DISABLED
         RECEIVE USER-MESSAGES IS DISABLED
            .
            .
            .
         TERMINAL FULLDUPLEX

Use the TERMINAL NO INHIBIT command to restore your REFUSE and RECEIVE settings.

top

3.7.5 Mail Messages

Mail messages appear on your terminal when another user sends you mail or when you have unread mail. These messages come from two different sources. The first type of mail message is a notice of new mail. This message comes from the mail program and is printed whenever new mail arrives:

        [You have a message from PRATT]

You can specify if you want to receive notice of new mail on your terminal with the RECEIVE or REFUSE SYSTEM-MESSAGES commands.

The second type of mail message results from your giving the SET MAIL-WATCH command.

        [You have mail from PRATT at 16:07:05]

SET MAIL-WATCH causes the system to check your MAIL file for unread mail every five minutes. If the system finds unread mail it prints a message when your terminal is at TOPS-20 command level. This means that if, for example, you are using an editor, the notice of unread mail is not printed until you exit the editor and return to TOPS-20 command level.

You can control the notice of unread mail with the SET MAIL-WATCH and SET NO MAIL-WATCH commands. SET NO MAIL-WATCH is the default.

The SET AUTOMATIC command allows the SET MAIL-WATCH command to send you a message any time, no matter what you are doing at your terminal. The SET NO AUTOMATIC command is the default.

If you want to be reminded of unread mail no matter what you are doing at your terminal, give the SET MAIL-WATCH and SET AUTOMATIC commands.

        @SET MAIL-WATCH
        @SET AUTOMATIC

To see if you have any new mail, give the INFORMATION MAIL command. The system lists the name of the sender and the time received for the last unread message in your MAIL file.

        @INFORMATION MAIL
         Mail from PRATT at 16:07:05

top

3.7.6 Alerts

An alert results from your giving a SET ALERT command:

        [08:55:00 alert - Group meeting in 5 minutes]

Unless you have given the SET AUTOMATIC command, alerts are issued only when your terminal is at TOPS-20 command level. If you do give a SET AUTOMATIC command, alerts will interrupt you no matter what you are doing at your terminal.

You can cancel alerts with the SET NO ALERTS command or you can stop alerts from appearing when you are running a program with SET NO AUTOMATIC.

This command cancels alerts for the next hour:

        @SET NO ALERT +01:00

Check pending alerts with the INFORMATION ALERTS command.

top


home PDP-10 TOPS-20 User's Guide Prev: Chapter 2 Communicating With The System Next: Chapter 4 File specifications