100 lines
4.2 KiB
HTML
100 lines
4.2 KiB
HTML
<html>
|
|
<head>
|
|
<title> Invocation </title>
|
|
</head>
|
|
<body>
|
|
<h1>Program Invocation</h1>
|
|
<p>
|
|
SICS is a client server system. This means there must be a server running
|
|
somewhere as a prerequsite for SICS operation. This server program lives on
|
|
the instrument computer. To check for its existence you need to log on to
|
|
that computer and execute the command: <b> CheckSICS</b>. If this test fails
|
|
to find the server, it can be started by typing <b>DMCServer</b> at that
|
|
computer. Please note, that this has to happen as Instrument user (
|
|
for example DMC) on the instrument computer.
|
|
</p>
|
|
|
|
<p>
|
|
The SICS clients are the programs a user interacts with. Their main purpose
|
|
is to forward commands to the server and to display the answers. A client
|
|
also implements the status display. Various clients exist for different
|
|
platforms.
|
|
</p>
|
|
|
|
<h2> DMC program Invocation on Digital Unix</h2>
|
|
<p>
|
|
On LNS DigitalUnix systems the command <b>dmccom </b> will start a command
|
|
line client. Even this is an X11 application. If it fails to start, make
|
|
use the DISPLAY variable is properly set. If not type: <BR>
|
|
setenv DISPLAY YourComputer.psi.ch:0.0 <BR> replacing the YourComputer bit with
|
|
the name of your machine. Once started up, dmccom shows a menubar, a
|
|
large list window at the top, a smaller one below, followed by an edit field
|
|
and a row of buttons at the very bottom. At the left lower corner that is a
|
|
red field which should say: Disconnected. This is a status display. In order
|
|
to make DMCCOM usable a connection to the server needs to be established.
|
|
This can be done by clicking at the DMC entry in the Connect menu. Please
|
|
allow some time for the establishment of the connection. Once this is done,
|
|
the status display at the bottom will change to the current status of the
|
|
server. Now commands can be typed into the edit field at the bottom. The
|
|
response of the server will be displayed in the top listbox. The lower
|
|
listbox will hold a history of commands typed. Commands in this list can be
|
|
reinvoked by double clicking them. By clicking on them with the right button
|
|
they can be copied into the edit field for editing.
|
|
</p>
|
|
<p>
|
|
A status display for DMC can be started by typing <b>dmcstat</b>.
|
|
</p>
|
|
|
|
<! This file will be included for all invocation sections to doc>
|
|
<h2>Accessing SICS through Telnet</h2>
|
|
<p>
|
|
SICS is able to communicate with standard TCP/IP telnet clients. Suitable
|
|
telnet clients are available on allmost all computer platforms free of
|
|
charge as part of the network software. In order to access SICS with telnet
|
|
you need to know the following five bits of information:
|
|
<ul>
|
|
<li>The name of the computer where the SICS server is running.
|
|
<li>The port number at which the SICS server lsitens for telnet connections.
|
|
<li>The login word.
|
|
<li>A valid username.
|
|
<li>A valid password for your user name.
|
|
</ul>
|
|
This information will be supplied to you by your instrument scientist if she
|
|
finds you and your cause honorable enough.
|
|
</p>
|
|
|
|
<p>
|
|
Loging in to SICS through telnet requires the following steps:
|
|
<ul>
|
|
<li>Invoke your telnet client and try to contact machine name at the port
|
|
number given. For example on a Unix or VMS this looks like:
|
|
<pre>
|
|
telnet machine.psi.ch 7654
|
|
</pre>
|
|
Of course this may differ if you use a telnet client on a different
|
|
platform.
|
|
<li> If things go well, you'll be connected to the SICS server then, though
|
|
he does not tell you about it. However, SICS will not allow you to type
|
|
commands yet. You have to login with the magic three words: <b>loginword
|
|
username password</b>. Only if you get this right, the SICS server will
|
|
print a welcome message and you may type commands to the server.
|
|
</ul>
|
|
You can logoff from the SICS server by typing <b>logoff</b>.
|
|
</p>
|
|
|
|
|
|
<h2>DMC Simulation Invocation</h2>
|
|
<p>
|
|
There exists a simulation version of the DMC instrument control program.
|
|
This is the same program as the actual control program. However, all drivers
|
|
have been replaced by simulation drivers. This means, this program does not
|
|
interact with the hardware. It can be used for training and in order to
|
|
test command files. The simulation server can be invoked with the
|
|
command <b>DMCSIM</b>. A simulation client with the command <b>dmcsim</b>.
|
|
There is no status display simulator as this could only display random
|
|
numbers.
|
|
</p>
|
|
|
|
</body>
|
|
</html>
|