From: sys_admin@condor.nepean.uws.edu.au (Bob Thomas)
Newsgroups: comp.sys.prime
Subject: (none)
Date: 6 Oct 92 07:14:19 GMT
Article-I.D.: usenet.9210060710.AA17906
Reply-To: Info-Prime@Blx-A.Prime.COM
Organization: University of Western Sydney,Nepean,New South Wales,Australia.

GROUP TRAINING TOOLS ON THE PRIME COMPUTERS



This article describes two methods by which each member of a group can
watch (on their own terminal) the activity on another terminal.

These methods can be used to teach by example (using FOLLOW or show/watch)
or by participation (using SHOW/WATCH).

Please note that there are a number of restrictions at present.  These are
described in section 4.

The first method (FOLLOW) requires the group members to list a file created
by the active participant.  This file records all the messages that appear
on the active participant's terminal.  The others in the group are shown
the contents of the file as the messages are written to it.

The second method (SHOW/WATCH) allows observers to see what is in the
buffer of the active participant's terminal.  A circle can be established
so that the actions on each person's terminal are displayed to the whole
group.

Section 3 describes how to determine and change Access Rights.

Section 4 describes some limitations and possible solutions.

Section 5 shows how to get more information about the commands mentioned in
this article.


1. FOLLOW

1.1 Description

 The leader starts a file which records all the terminal activity for that
person.  The others in the group FOLLOW the file as details are put to it.

 The FOLLOWERS can:

  watch what is happening on the leader's terminal;

  stop following, perform their own commands, and start following again.

The FOLLOWERS cannot:

  show their own terminal activities to others unless they start a similar
output file and the others FOLLOW that file instead of the leader's file;

  participate in the leader's session by using their own terminal.


1.2 How to do it

1.2.1 Decide where the output file is to be created.

 It is recommended that public directories be used.  One such directory is
UDATA (to which staff have write access and everyone has read access).

 Alternatively, create the output file in a personal directory and give the
others in your group Read-Access as described below.

1.2.2 The leader changes to the required directory by using the ATTACH
command:

  A directory-pathname

 eg A UDATA

 If this is a public directory, the others in the group can change to this
directory also.

1.2.3 The leader starts the file by entering

  COMO  filename  -QUERY
  or COMO  filename  -CONTINUE

  eg COMO  DEMO.COMO  -QUERY

 The COMO (Command Output) command directs a copy of the terminal display
to the specified filename.  If the -CONTINUE argument is included, the
output is appended to the file.

1.2.4 If the COMO file is in a private directory, the leader gives others
Read-Access by entering

  EDAC  filename  $REST:UR

 eg EDAC  DEMO.COMO  $REST:UR

Note: The others must have use (U) access to all directories above the
file.

1.2.5 The others FOLLOW the file:

   COMO  filename (if in the same directory)
  or FOLLOW  full-pathname-of-file

  eg FOLLOW  UDATA>DEMO.COMO

1.2.6 To stop FOLLOWing, hold down the control (CTRL) key and press P.
Note:  this action will be shown as (CTRL)P in the remainder of this
article.

1.2.7 To restart FOLLOW, enter the command as at 1.2.5.

1.2.8 The leader closes the output file by:

  COMO  -E

1.2.9 This file should be deleted unless needed for future work.  DISK
SPACE IS A LIMITED RESOURCE.

1.2.10 If the file is kept, it will be overwritten by the next COMO using
that filename unless the -CONTINUE option is specified.  If -CONTINUE is
specified, subsequent output will be appended to the file.

1.2.11 To browse through an existing file, issue the FOLLOW command, then
use control (CTRL)S to stop the scrolling display at any point.  Use
control (CTRL)Q to continue scrolling.

 Similar commands are

  SLIST  filename
  KLIST  filename

 but these can only be used after the leader has closed the output file.



2. SHOW/WATCH

2.1 Description

 The SHOW/WATCH commands permit a circle of users to each show all others
in the circle what is occurring on their terminal.

 The SHOW command allows a user to show another user what is happening on
the first user's terminal.

 The second user issues the WATCH command to start watching.

 Only one user can WATCH another's terminal, but these SHOW/WATCH commands
can be daisy-chained to include a whole group and may be extended to a
circle.

 The WATCHERS can:

  watch what is happening on any of the terminals above them in the chain,
or on any terminal in a circle;

  perform operations even while WATCHING (Note:  that all terminal displays
are passed to the next WATCHER[S]);

  stop WATCHING, perform own commands, start WATCHING again.

A SHOW/WATCH circle allows each participant to show others what they are
attempting.  There are limits (eg usually only one person can update a file
at a time).  This SHOW/WATCH circle has the potential to be a valuable
educational tool.  The SHOW/WATCH circle can be used to allow students or
lecturers to demonstrate a process or technique to a group.  The WATCHERS
do not need access rights to any files since they are WATCHING the buffers
of the terminal.


2.2 How to do it

2.2.1 The SHOW command gives permission to a particular user to have access
to WATCH the terminal.

 A particular user is specified by a login-id (eg S993214 or J.BLOGGS).



 You may enter

   SHOW  login-id
  or SHOW  -ALL


  eg SHOW  S993214

2.2.2 The individual or one of the group you have specified may now enter.

   WATCH  login-id

 where the login-id is that of the user who issued the SHOW.

 A message is displayed on the terminal of the SHOW-er to indicate who is
WATCH-ing.

2.2.3 To stop the WATCH, enter

   WATCH  -OFF

2.2.4 To stop SHOWing, enter

   SHOW  -DISABLE_USER

2.2.5 An example:

Given four students with login ids of S01, S02, S03, S04, all in group
Newsgroups: comp.sys.prime