There are no other files named ekonet-sender.mem in the archive.
EKONET/SENDER User's Guide
EKONET and SENDER constitute a simple demonstration (or test) of
task-to-task communication between two TOPS-20 systems. In this
demo, an input file is sent to a remote system and is then simply
returned, and the returned data is written to an output file. A
baud rate calculation is performed on the remote side of the
DECnet link. To test the success of the data transfer, the input
and output files may be compared with FILCOM.
1.0 RUNNING EKONET
EKONET should be started on the remote -20 system before SENDER is
run. EKONET does not require privileges. It prompts for a server
name to use and then sleeps, waiting for a logical link
connection. This connection will usually be from SENDER, although
it could be from any program.
When the connection is made, data is read from the link and
returned to the sender. At end of file, the baud rate and
effective baud rate of the transfer are calculated, and then
Unlike many server programs, EKONET does not restart
itself after a link has been disconnected. It must be
restarted manually for each new test.
The baud rate is the number of bits transferred per second of
elapsed time. The time begins when the logical link connection is
made with SENDER, and the count of bits includes both received and
transmitted data. Since the line is full duplex, data can be
moving in both directions at once, so it is theoretically possible
to see a baud rate higher than the physical baud rate of the line.
Do not use the baud rate as an estimate for other DECnet
applications, especially if these other programs essentially move
data in one direction only. Your performance guess may be too
The effective baud rate is the number of bits transferred per
second of runtime. It in no way represents a baud rate of the
line or the capabilities of any other part of the hardware.
2.0 RUNNING SENDER
SENDER is started on the local system after EKONET is started
remotely. It does not require privileges. It prompts for input
and output filenames and the name of the DECnet file specification
with which to connect. After the file has been returned by
EKONET, SENDER exits.
A sample run of EKONET and SENDER is shown below. For the purpose
of a easy-to-understand example, both programs are running on the
same node. A more interesting demonstration would result by
running EKONET on a remote TOPS-20 node.
PTYCON> !WE HAVE SET UP TWO PTYCON JOBS
PTYCON> WHAT ALL
EKO(0) 7 LNEFF EXEC TI 0:0:2
SND(1) 65 LNEFF EXEC TI 0:0:2
PTYCON> !FIRST, START EKONET
PTYCON> CONN EKO
[CONNECTED TO SUBJOB EKO(0)]
DECnet File Specification (SRV:.taskname):SRV:.EKONET
PTYCON> !EKONET IS NOW SLEEPING, WAITING FOR A CONNECTION
PTYCON> !NOW START SENDER
PTYCON> CONN SND
[CONNECTED TO SUBJOB SND(1)]
INPUT FILE NAME:TEST.TXT
OUTPUT FILE NAME:TEST.CHK
DECnet File Specification (DCN:node-TASK-taskname.):DCN:2102-TASK-EKONET.
**** EKO(0) 15:53:07 ****
BAUD RATE= 50400
EFFECTIVE RATE: 604800
**** SND(1) 15:53:07 ****
@!THE BAUD RATE IS VERY HIGH BECAUSE THIS WAS JUST
@!A LOCAL DECNET CONNECTION
@!NOW COMPARE THE TWO FILES TO MAKE SURE THE TRANSFER
@!OCCURRED WITHOUT ERRORS
No differences encountered
PTYCON> KILL ALL
[End of EKONET/SENDER User's Guide]