TCP command option list on the
screen:
TCP H
For the TcpLink 3000 USB only the commands 'A', 'D', 'G', 'H', 'N', 'P', 'S' and 'V' are available.
TCP is given by the following
parameter list:
default destination:
a: (default archive is the floppy drive)
/ (default destination directory on the floppy is / )
default numeric parameters:
20 (default Aspect timeout constant is 20 sec)
30 (default unit timeout constant is 30 sec)
1 (default block count display rate)
1 (default special internal parameter is 1)
default Disnmr command specification:
S #CURDAT (by default Disnmr sends the current data file)
The default configuration can be printed by the command
TCP A
In order to alter the configuration, it is required to generate
a new TCP program that has one or more of these parameters
changed. This may be performed several times and allows you
to maintain an arbitrary number of TCP programs on the disk,
each with a different configuration.
At first you must set up a text file
containing the desired default destination, numeric parameters,
and DISNMR command specification in the following format
(this is just one example and will be further illustrated by other
examples later):
indigo (destination host name)
max (user login id on destination host)
xam12xrt (user password on destination host)
/usr/people/max/datafiles (destination directory on host )
20 30 1 1 (numeric config. parameters, see above)
S #CURDAT (disnmr command specification)
exit (must terminate the file)
After having set up the the configuration file (lets assume
you have chosen the name config.tcp), proceed as follows:
ADAKOS region 1 (from where you
normally start \dis), and region 1 has at least 128K memory
assigned. This can be verified using the ADAKOS DMP command.
ADAKOS mode:
LOA TCP 202000
TCP CONFIG:A
STO TCPF 202000[20K];202001'IXP
TCPF A
The first command will load TCP at a high memory address
(at offset octal 200000 from the normal ASPECT 3000 load address 2000).
The second command starts TCP at its usual low memory address
and puts the new configuration constants from the specified file
in the program loaded in high memory. The third command stores
the updated program under a new, user defined name on disk.
The number in brackets is the program size that may increase when
new versions come up. We therefore recommend to check the size
via DIR TCP before storing, and use the true size.
The last command, finally, prints out the configuration of this
program for verification.
TCP and TCP f
with a different internal configuration. Let us consider the
following to examples:
TCP S SPEC.001
TCPF S SPEC.001
The first command would archive the specified file on floppy
diskette since this is the default destination after
installing TCP . The second command would send the file to
the host indigo because we generated TCP f to have this
default configuration. Here is another example that illustrates a configuration file:
a: (destination archive name)
/spec1d (destination directory on archive )
25 35 1 1 (numeric config. parameters)
SUN:S #CURDAT (disnmr command line)
exit (must terminate the file)
In this case the default destination is not a host on the network,
but a floppy disk archive. Note that no login id
and no password need be specified.
The two timeout constants and the \dis
specification line have also been changed.
DISNMRDISNMR sepcification line of the configuration file
the same arguments may be specified that
are allowed for TCP itself. In the example a file transfer
to the station SUN is requested if the TCP program configured
by this file is called from DISNMR via PASC. The file argument
# CURDAT indicates that the file to be transferred is
the current DISNMR data set defined via the RE command. Any argument
other than #CURDAT would directly denote a file name
specification requiring the same syntax as if TCP was called
from ADAKOS command level.
One major drawback of executing TCP from DISNMR is the inability
to specify arguments. You may type PASC TCP, but not
PASC TCP <args>. This disadvantage can be circumvented
by storing several TCP programs on disk, e.g. one that archives
files and one that retrieves files (lets say TCP and TCPF). Then,
PASC TCP and PASC TCPF would perform the desired
tasks.
Particularly in DISNMR AU programs in could be of advantage to
do both, sending and receiving files using the same or different
destinations. This problem is easily solved by setting up
configuration files containing the desired destinations and
DISNMR specification lines, and then generate the appropriately
configured TCP programs that may then be invoked from the AU
program via PASC.