Trailing-Edge
-
PDP-10 Archives
-
BB-H348C-RM_1982
-
swskit-v21/debugging-tools/dynets/dynets.mem
There are no other files named dynets.mem in the archive.
---------------
|d|i|g|i|t|a|l| INTEROFFICE MEMORANDUM
---------------
TO: DECnet users DATE: 8-Feb-80
FROM: NCSS
EXT: HOTLINE (6492)
LOC/MAIL STOP: MR1-2/H22
SUBJ: DYNETS User's Manual
DYNETS is used to perform testing of DECnet at the NSP
logical link level. DYNETS is used to perform the line loopback
tests during DECnet installation verification. In the field, it
may be used to perform loopback tests to isolate hardware
problems. (See LOOPBACK-TESTS.MEM for examples.)
DYNETS.EXE is distributed on the DECnet distribution tape.
During installation it is restored to PS:<UETP.LIB>. The sources
and an EXE file have also been included on the DECnet SWSkit.
DYNETS may be run simultaneously with other DECnet
applications on a timesharing system. A stand-alone machine is
not required. DYNETS does not require privileges.
See the attached user's manual for a description of commands
and features.
Page 2
User's Manual For
DECNET Dynamic Exerciser Test System
(D E C N E T D Y N E T S)
The DECNET Dynamic Exerciser Test System (DYNETS) is a program which
provides the capability of exercising the DECNET NSP functionality as
implemented on TOPS-20 release 4, through an easy to use and understand
command language. The command language incorporates the same
user-oriented features as the system EXEC, such as, keyword recognition,
guide phrases, and help phrases through the "?" character. The system
provides the user with the ability to dynamically establish and destroy
logical link connections with other tasks in the network, to selectively
send and receive on the links which have been established, to specify
the source from which the messages to be sent are to be taken, and to
declare available server connections which may be connected to by other
tasks.
The Dynamic Exerciser Test System is the major tool to accomplish the
testing of TOPS-20 DECNET task-task support. The package allows the
user to create a task to task network environment. The tester will be
able to specify the names of his server tasks, the names of the target
tasks/nodes to which he desires to establish links, the file from which
to take the message stream to send, and the byte size to be used when
opening the logical link connection. Input may be taken from a command
file or from the terminal, which will be used to monitor the running of
a test session. The program will issue appropriate error messages when
errors are detected in its operation.
This product is intended for use by system developers, software field
maintenance personnel, and others who wish to simulate a user
environment network situation for dynamic exercise and regression
testing of TOPS-20 DECNET implementations.
The implementation provides flexibility in obtaining different types of
networking situations. As many different network JSYSs and flavors of
each are employed as was possible to work into the implementation.
The test system exists and runs in the normal TOPS-20 environment as a
regular user program. The package requires the DECNET communications
support of the system under test. It was a goal to provide a package
which would be as independent of the hardware configuration of any
particular front-end as possible. The program will require an operable
MCB of a version that is compatible with the TOPS-20 release under test
and the appropriate front-end hardware to run the particular MCB. The
tester will be responsible for determining the specific front-end
hardware and network configurations required to conduct any specific
test. For testing with objects on another host the appropriate
communications hardware, modems, circuits, remote system
hardware/software and test package for that host will be required. No
USER'S MANUAL FOR DECNET DYNAMIC EXERCISER (DYNETS) Page 3
special monitor or hardware functionality to support the test system,
other than that stated in this section, is required.
1.0 NETWORK TEST SYSTEM BLOCK DIAGRAM
+---------+ +---------+
! ! ! !
! ! ! !
! CONTROL ! ! LOG !
! FILE ! ! FILE !
! ! ! !
! ! ! !
+---------+ +---------+
! /!\
! !
! !
\!/ ! +-----------+
+-------------------------------------+ ! !
! ! ! TOPS-20 !
! ! ! DECNET !
! D E C N E T ! ! INTERFACE !
! DYNAMIC !<-------->! SUPPORT !<-D-T-E->
! EXERCISER ! ! FOR !
! ! ! NETWORK !
! ! ! SERVICES !
+-------------------------------------+ ! PROTOCOL !
/!\ ! !
! +-----------+
!
\!/
+-------------+
! CONTROL !
! TERMINAL !
+-------------+
USER'S MANUAL FOR DECNET DYNAMIC EXERCISER (DYNETS) Page 4
2.0 POSSIBLE TESTING CONFIGURATIONS
+---+
+--------+ ! D !
! DYNETS !<------->! E !
+--------+ ! C !
! N ! +-------+ COMMUNICATION
+--------+ ! E !<--D-T-E-->! M C B !=====/ /===== LINK TO OTHER
! DYNETS !<------->! T ! +-------+ REMOTE SYSTEM
+--------+ ! !
! S !
! P !
! T !
+---+
1. Two test systems within a single TOPS-20 host may communicate
with each other via the NSP interface through an intra-host
logical link. This is the most common scenario for field
purposes. This requires two copies of DYNETS running under
separate jobs, with one in echo mode and one in loop-back mode
(see below).
2. A dynamic exerciser in a TOPS-20 host may test with an object
which runs under MCB in the front-end. The object meant to be
used is TEST72, but this option has not been fully implemented.
3. The dynamic exerciser residing in a TOPS-20 host system may be
used to do testing with some other test package running under
another operating system on another machine type, e.g., an
RSX11M system. Again, this option has not been fully
implemented, but similar tests may be done with DTR/DTS.
The test system will operate a link in two modes.
. Echo mode allows the system to test with other DECNET test packages
which provide a logical message loop-back capability. In this
mode, it will send messages and expect to see those same messages
returned from the remote object. This mode is provided by the
ESTABLISH command.
. Loop-back mode provides a logical loop-back path to a test system
in the same or another host. The other host could be an RSX11
system, RSTS system, or RT-11 system. In this mode it will
complement the operation of another test package operating in echo
mode. In other words, any messages received will be returned to
the sender. This mode of operation is provided as a default for
the DECLARE command when creating a server link.
USER'S MANUAL FOR DECNET DYNAMIC EXERCISER (DYNETS) Page 5
3.0 COMMAND FUNCTION DESCRIPTION
The following commands provide the tester with control over the
operation of the test system and provide the ability to control the test
scenario.
ESTABLISH Requests the test system to make a logical link
connection to a specified host-object. Echo mode is
automatically set.
DECLARE Requests the test system to declare a link as a specific
network object on its host. In other words, DYNETS
declares itself to be a server on this host. Loop-back
mode is automatically set.
SEND Directs the test system to transmit a message or group of
messages to another object on the network via established
logical link connections.
RECEIVE Requests the test system to begin receiving test messages
on logical link connections from another object.
INTERRUPT Directs the test system to transmit interrupt messages at
a specified interval while sending data messages to
another object on the network. This has not yet been
implemented.
PURGE Directs the test system to perform an asynchronous
disconnect on logical link connections established to
another object. This has not yet been implemented.
DISESTABLISH Directs the test system to destroy logical link
connections. It performs a synchronous disconnect. If
DYNETS is the test program running on the other side of
the link, the remote copy of DYNETS will do another
DECLARE command automatically, but another ESTABLISH
command must be given on this side before any more data
is transferred.
SET Sets various attributes of the network file
specification. Not implemented; do not use this
command.
WAIT Prevents DYNETS from going into input wait. Useful as
the last command to DYNETS in a batch control file if
DYNETS is to run undisturbed.
TAKE Standard command file facility.
HELP Types a help message.
EXIT Exits to monitor.
USER'S MANUAL FOR DECNET DYNAMIC EXERCISER (DYNETS) Page 6
4.0 COMMAND SYNTAX DESCRIPTION FOR MAJOR COMMANDS
ESTABLISH (LOGICAL LINK TO) target-name switches
Target-name specifies the host/object to be connected to and is
of the general form:
DCN:host-objectname-descriptor.taskname;attribute:data...
Note that this command gives the tester the ability to
establish multiple logical links with a single target object.
Switches are /WAIT:n - Wait for object to become available.
The system will wait nnn seconds for the link
to be established. If the link has not been
established at the end of this time period an
error message will be issued. Essentially
this turns on the OPENF OF%AWT bit and begins
a timeout sequence. The default is
/WAIT:120.
/NOWAIT - Do not wait. If the link can not be
established immediately an error message will
be issued.
/BYTE:n - The byte size to use on this link.
/RECL:n - The maximum length of the records to be
used.
DECLARE (SERVER NAME) server-name switches
Server-name is the network object name to be declared to this
host and is of the general form:
SRV:servername-descriptor.taskname
Switches are /BYTE:n - The byte size to use on this link.
/RECL:n - The maximum message size to use.
/DELAY:n - Delay the transmission of each message
n seconds. If not specified, no delay will
be provided.
SEND (TO) target-name (FROM MESSAGE FILE) msg-file-name switches
Msg-file-name is the name of a file from which to take the
messages to be transmitted. Target-name is the object to which
the messages are to be transmitted.
Switches are /TIMES:n - Repeatedly transmit the messages "n"
times. The default is "n=1", i.e., single
transmission.
USER'S MANUAL FOR DECNET DYNAMIC EXERCISER (DYNETS) Page 7
/DELAY:n - Delay the transmission of each message
"n" seconds. If not specified, no delay will
be provided.
/BYTE:n - The byte size to use on this link.
/INTERRUPT:n - Send an interrupt message every n
seconds.
/RECL:n - The record size to use for this
transfer.
RECEIVE (FROM) target-name switches
Target-name is the object from which the tester desires to
begin receiving messages. The data which is received is
written into target-name.LOG. If the transfer was successful,
this log should match the original file which was sent.
Switches are /TIMEOUT:n - Specifies a timeout value in seconds
in which to wait for a message to be
received. The default is no timeout.
/RECL:n - Specifies the maximum length of the
records to be received.
/BYTE:n - The byte size to use on this link.
INTERRUPT (OBJECT) target-name switches
Target-name specifies the object to which the tester desires to
send an interrupt message. Not yet implemented.
Switches are /EVERY:n - Send interrupt messages after every "n"
data messages have been sent. If not
specified interrupt messages will be sent
after every 100 data messages.
PURGE (OBJECT) target-name
Target-name is the object on the network to which the tester
desires to flush any outstanding message traffic. Not yet
implemented.
DISESTABLISH (FROM OBJECT) target-name
Target-name is the object on the network from which the tester
desires to destroy logical link connections.
USER'S MANUAL FOR DECNET DYNAMIC EXERCISER (DYNETS) Page 8
5.0 COMMAND USE EXAMPLES
An example of the commands required to start a test with an RSX11M
system follows.
PTYCON> DEFINE (SUBJOB #) 0 (AS) TO
PTYCON> DEFINE (SUBJOB #) 1 (AS) FROM
PTYCON> ALL-LOG LNEFF
PTYCON>
**** TO(0) 17:47:56 ****
2102 Development System, TOPS-20 Monitor 4(3245)
@LOG LNEFF
Job 11 on TTY217 12-Feb-80 17:47:56
**** FROM(1) 17:47:56 ****
2102 Development System, TOPS-20 Monitor 4(3245)
@LOG LNEFF
Job 8 on TTY220 12-Feb-80 17:47:56
PTYCON>
**** TO(0) 17:48:01 ****
Tue 12-Feb-80 17:47:59 Up 1:46:27
@
**** FROM(1) 17:48:02 ****
Tue 12-Feb-80 17:48:00 Up 1:46:27
@
PTYCON> ALL-DYNETS
PTYCON>
**** TO(0) 17:49:05 ****
DYNETS
**** FROM(1) 17:49:06 ****
DYNETS
PTYCON>
**** TO(0) 17:49:06 ****
12-Feb-80 17:49:06 * [DYNETS STARTING]
DYNETS>
**** FROM(1) 17:49:06 ****
12-Feb-80 17:49:06 * [DYNETS STARTING]
DYNETS>
PTYCON> CONN TO
[CONNECTED TO SUBJOB TO(0)]
DYNETS>!Start this copy of DYNETS in loop-back mode. Once started,
DYNETS>!this copy of DYNETS will not require further attention.
DYNETS>
DYNETS>DECLARE SRV:.TO /BYTE:7 /RECL:132
12-Feb-80 17:51:18 * [DYNETS OK]
DYNETS>^X
PTYCON> CONNECT (TO SUBJOB) FROM
[CONNECTED TO SUBJOB FROM(1)]
DYNETS>!Start this copy in echo mode. This is the copy most of
DYNETS>!the commands will be typed to.
DYNETS>
USER'S MANUAL FOR DECNET DYNAMIC EXERCISER (DYNETS) Page 9
DYNETS>ESTABLISH (LOGICAL LINK TO) DCN:-TASK-TO.FROM /BYTE:7 /RECL:132
% DYNETS: SEGMENT SIZE - 256
% DYNETS: OPT DATA - 101065061062060060
12-Feb-80 17:52:35 * [DYNETS OK]
DYNETS>
**** TO(0) 17:52:35 ****
% DYNETS: ACCEPTING CONNECTION FROM - 2102-TASK-FROM.TO
% DYNETS: USER-ID(SQM) PASSWORD(JPCAXS) ACCOUNT(07995)
**** FROM(1) 17:52:35 ****
DYNETS>!Now enable this copy to receive data which will be echoed to it.
DYNETS>RECEIVE (FROM) DCN:-TASK-TO.FROM
12-Feb-80 17:53:28 * [DYNETS OK]
DYNETS>!Now send a file across the link and back. The received data
DYNETS>!will be put into a log file.
DYNETS>SEND (TO) DCN:-TASK-TO.FROM.0 (FROM MESSAGE FILE) TEST.MEM.3
12-Feb-80 17:55:24 * [DYNETS OK]
DYNETS>
**** TO(0) 17:55:24 ****
% DYNETS: SERVER LINK DISCONNECTED, REOPENING
**** FROM(1) 17:55:24 ****
^X
PTYCON> ALL-EXIT
PTYCON>
**** TO(0) 17:55:45 ****
EXIT
12-Feb-80 17:55:45 * [DYNETS OK]
12-Feb-80 17:55:45 * [DYNETS TERMINATING] (ELAPSED TIME: 00:06:39)
@
**** FROM(1) 17:55:45 ****
EXIT
12-Feb-80 17:55:45 * [DYNETS OK]
12-Feb-80 17:55:45 * [DYNETS TERMINATING] (ELAPSED TIME: 00:06:39)
@
PTYCON> KILL ALL
PTYCON> EXIT
@!DYNETS should have left us a log file
@VD -TASK-TO.LOG
NET:<LNEFF>
-TASK-TO.LOG.1;P777700 3 5935(7) 12-Feb-80 17:53:28
@RENAME (EXISTING FILE) -TEST-TO.LOG.* (TO BE) TEST.LOG.1 !New file!
-TEST-TO.LOG.1 => TEST.LOG.1 [OK]
@!Now compare the input and output files
@FILCOM
*TTY:=TEST.LOG,TEST.MEM
No differences encountered
*^C
@
USER'S MANUAL FOR DECNET DYNAMIC EXERCISER (DYNETS) Page 10
This version of the test system is compatible with the DECNET
implementation available on Release 4 of the TOPS-20 monitor. It is
compatible for testing purposes with the exerciser test systems written
by the Maynard SQM group for the RSX-11M and RT-11.
The system provides the capability of interfacing with other network
test systems, currently under development or already implemented, which
use the DECNET Network Services Protocol.
The error messages from the test package are output as 7 bit ascii
strings. They are in a format which will allow easy integration with
the User Environment Test Package.
An example of some of the error messages which might be produced during
the test run described are:
? DYNETS: COULDN'T OPEN LINK
? DYNETS: JSYS ERROR - invalid object
6.0 SUMMARY OF COMMAND SYNTAX
ESTABLISH (LOGICAL LINK TO) target-name [/BYTE:n] [/WAIT:n] [/RECL:n]
[/NOWAIT]
DECLARE (OBJECT NAME) server-name [/BYTE:n] [/RECL:n] [/DELAY:n]
SEND (TO) target-name (FROM MESSAGE FILE) msg-file-name [/BYTE:n]
[/TIMES:n] [/INTERRUPT:n] [/RECL:n] [/DELAY:n]
RECEIVE (FROM) target-name [/BYTE:n] [/TIMEOUT:n] [/RECL:n]
DISESTABLISH (FROM OBJECT) target-name
HELP (WITH DYNETS)
TAKE (COMMANDS FROM) filespec (LOGGING OUTPUT ON) filespec
EXIT (TO MONITOR)
WAIT (AND DON'T ISSUE NEXT PROMPT)
Where:
target-name = DCN:host-objectname-descriptor.taskname;attributes...
server-name = SRV:servername-descriptor.taskname
The following commands have not been implemented:
INTERRUPT (OBJECT) target-name [/EVERY:n]
PURGE (OBJECT) target-name
USER'S MANUAL FOR DECNET DYNAMIC EXERCISER (DYNETS) Page 11
SET ACCESS-CONTROL
DEFAULT ATTRIBUTES (TO) string
BDATA
BPASSWORD
CHARGE
DATA
PASSWORD
USERID
[End of DYNETS User's Manual]