Digital PDFs

AA-P379B-TB

May 1986

184 pages

Original

7.6MB

Document:	TOPS-10 DECnet and PSI Installation Guide Apr86
Order Number:	AA-P379B-TB
Revision:	0
Pages:	184
Original Filename:	AA-P379B-TB_TOPS-10_DECnet_and_PSI_Installation_Guide_Apr86.pdf

OCR Text

TOPS-10
DECnet and PSI
Installation Guide
AA-P379B-TB

April 1986
This manual describes the procedures for generating
and installing DECnet and TOPS-10 PSI software on the
DECsystem-10.
This manual supersedes the DECnet-10 Network Generation
and Installation Procedures, order number AA-P379A-TB,
and the TOPS-10 PSI Installation Guide, order number
AA-CK82A-TB.

OPERATING SYSTEM:

TOPS-10 V7.03

SOFTWARE:

DECnet V4.0
GALAXY V5.1
TOPS-10 PSI V1.0

Software and manuals should be ordered by title and order number. In the United States. send orders
to the nearest distribution center. Outside the United States. orders should be directed to the nearest
DIGITAL Field Sales Office or representative

Northeast/Mid-Atlantic Region

Central Region

Digital Equipment Corporation
PO Box CS2008
Nashua. New Hampshire 03061
Telephone:(603)884-6660

Digital Equipment Corporation
Digital Equipment Corporation
Accessories and Supplies Center Accessories and Supplies Center
1050 East Remington Road
632 Caribbean Drive
Schaumburg. Illinois 60195
Sunnyvale. California 94086
Telephone:(312)640-5612
Telephone:(408)734-4915

Western Region

- digital equipment corporation. marlboro. massachusetts

First Printing, February 1984
Revised, April 1986
Copyright ©1984, 1986 by Digital Equipment Corporation. All Rights Reserved.

The information in this document is subject to change without notice and should not
be construed as a commitment by Digital Equipment Corporation. Digital Equipment
Corporation assumes no responsibility for any errors that may appear in this document.
The software described in this document is furnished under a license and may be used or
copied only in accordance with the terms of such license.
No responsibility is assumed for the use or reliability of software on equipment that is
not supplied by Digital Equipment Corporation or its affiliated companies.

The following are trademarks of Digital Equipment Corporation:

DEC
DECmate
DECsystem-10
DECSYSTEM-20
DECUS
DECwriter
DIBOL

MASSBUS
PDP
PIOS
Professional
Q-BUS
Rainbow
RSTS

RSX
RT
UNIBUS
VAX
VMS
VT
Work Processor

The postpaid READER'S COMMENTS form on the last page of this document requests
the user's critical evaluation to assist us in preparing future documentation.

CONTENTS

PREFACE
CHAPTER 1
1.1
1.2
1.2.1
1.2.2
1.3
1.4
1.5
1.6
1.7
CHAPTER 2
2.1
2.2
2.3
2.3.1
2.3.2
2.3.3
2.4
CHAPTER 3
3.1
3.2
3.3
3.3.1
3.3.2
3.4
3.5
3.6
CHAPTER 4
4.1
4.1.1
4.1.2
4.1.3
4.1.4
4.1.5
4.2
4.2.1
4.2.2
4.2.3
4.3
CHAPTER 5
5.1
5.2

NETWORK CONFIGURATIONS
KS NETWORK CONFIGURATION
• 1-1
KL NETWORK CONFIGURATIONS
1-2
DECnet Network Configurations
•••••
1-2
PSI Network Configuratio~s • • • • • •
1-3
OVERVIEW OF INSTALLATION PROCEDURES
• 1-5
PRRPARATION • • • • • • • • • • • • •
1-8
INSTALLATION WORKSHEETS • • • • • •
• • • • • 1-9
FILES REQUIRED FOR INSTALLING NETWORK SOFTWARE • 1-16
FILES REQUIRED FOR INSTALLING PSI
• • • • • • • 1-17
GENERATING TOPS-10
RESTORING DECNET FILES •
• • • •
. . • • •
RESTORING PSI FILES
GENERATING THE MONITOR • •
Hardware Definition for KL Syste~s •
Hardware Definition for KS Systems • • • • • •
Specifying Network Configuratio~s
GENERATING GALAXY
• • • • • • • • • • •
•

2-1
• 2- 2
• ~-3

2-3

• 2-5

2-5
• 2-6

INSTALLING DN20 NODES
STARTING NETGEN
• • • • • •
CONFIGURING MCB SOFTWARE • • • • •
CONFIGURING PSI FRONT-END SOFTWARE
Defining the X25-Server Access Passworo
Adjusting Executor Parameters
CHECKING NETGEN PARAMETER VALUES
RECONFIGURING SOFTWARE • • • • •
CREATING DN20 SOFTWAR8 • • • • •

•
• • • •
• • • •
• •

3-1
3-2
3-4
3-5
3-6
3-6
3-7
3-8

CONFIGURING NETWORK NODES
RUNNING NIPGEN • • • • • • • • • • • • •
Describing the Host Node • • • • • • • • • •
Describing Adjacent Nodes
••••••
Describing MCB Configurations (KL/DN20 only)
Describing Remote Nodes
•••••
Describing Nodes for File Transfer Tests •
NIPGEN COMMAND AND CONTROL FILES •
NCP.CMD
NIPTST.CTL •
NIPNFT.CTL •
• • • •
NIPGEN ERROR MESSAGES

4-1
• • 4-2
• • 4-2
4-3
• • 4-4
• 4-5
• 4-5
• 4-6
4-6
• • 4-6
• • 4-6

GENERATING PSI INITIALIZATION FILES
EDITING THE X25CNF.BNF FILE
RUNNING COMGEN • • • •

iii

• • • 5-1
• • • • • 5-2

CHAPTER 6
6.1
6.2

6.3
6.4
6.5

6.6
6.7
6.S
6.S.1
6.8.2
6.9
6.9.1

6.9.2
6.9.3
6.9.4
6.10
6.11
6.11.1
6.11.2

6.11.3
APPENDIX A

STARTING AND VERIFYING NETWORK SOFTWARE
PREPARING SYSTEM FILES
STARTING NETWORK SOFTWA~B
• • • •
• • •
•
VERIFYING NETWORK SOFTWARE
TROUBLESHOOTING NETWORK SOFTWAR8 •
• •
VERIFYING THE NETWORK
• • • •
TESTING NETWORK CONNECTIONS
• • • • • •
• •
TESTING FILE TRANSFER
VERIFYING PSI CONN8CTIO~S
• • • • • •
Performing the X.25 Loop Test
•
Testing X.25 Connectivity
VERIFYING X.29 CONNECTIONS • • •
Calling the Local Pad (TELENET)
Signing on to the Network Gateway
Connecting to the TOPS-10 Host Syst~~
Disconnecting from the TOPS-10 System
COMPLETING THE INSTALLATION PROCEDURB
• • • •
INSTALLING PSI ACCESS SOFTWARE ON OTHER NODES
Installing Access Softwar~ • • • • • • • •
Restarting NML • • • • • • • • • • • • •
Activating Network Management

B.l
B.l.l
B.l.2
B.l.3
B.l.4
B.l.5
B.2
B.3
B.4
B.4.1
B.4.2
B.4.3

B.4.4
B.4.5
B.4.6
B.5

• • 6-3
6-3
•
•
•
•

•
•
•
•

6-4
6- 5
6-6
6-6
6-6

• • 6-7
1S-10
6-10
6-10
6-11

IS-II
6-12

•

6-13
6-13

NETGEN

NETGEN INPUT FEATURES
A.l
NETGEN PARAMETERS
• • • .
A.2
PS I PARAMETERS • • • • •
A.3
Known Circuits Characteristics • • • • •
A.3.1
Known Lines Characteristics
A.3.2
X25-Protocol Parameters
••••
A.3.3
Module X25-Protocol Characteristics
A.3.3.1
Module X25-Protocol Characteristics Known
A.3.3.2
DTEs • • • . • • • • • •
List Module X25-Protocol Characteristics
A.3.3.3
Known Groups • • * • • • • • • • •
X25-SERVER Parameters
• • • • • • • •
A.3.4
Module X25-SERVER Characteristics
A.3.4.1
fVlodule X25-SERVER Characteristics Known
A.3.4.2
Destinations • • • • • • •
BUFFER SIZE GUIDELINBS •
A.4
A.5
NETGEN COMMANDS
••••
NETGEN ERROR MESSAGES
A.6
APPENDIX B

6-1
• • 6-2

•

•
•
•
• •
•
•

~-l

A-I
A-6
A-6
ll,-7

• A-7

• A-S
A-10
A-10

A-II
A-II
A-II
A-13
A-14
A-40

PSITST
RUNNING PSITST • • • • •
Normal Environme~t •
Private Environment
Duplicating PSITST Process~s •
Missing PSITSB Process •
• •••
GALAXY Compatibility.
• •••
ACCESS PORTS • • • • • • • • •
INITIALIZATION • • • •
LOGGING
• • • • • •
Log File Contents
User Command Log Entry •
Event Log Entry
••••
Received Data and Facilities Log Entry.
Clear and Reset Diagnostic Log Entry • •
Examples • • • •
PSITST COMMANDS
••••••
iv

• B-2
• • B-2
• • B-2
• • 8-3

• • 13-4
•

•
•
•
•
• •
•

B-4
B-4
B-5
B-5
B-6
B-7
B-7
• • B-B
• • B-9

13-10
B-20

B.6
APPENDIX C

PSITST ERROR MESSAGES

8-50

GLOSSARY

INDEX
FIGURES
1-1
1-2
1-3
1-4
1-5
1-6
B-1

Configuration of a DN20/TOPS-10 PSI Node
DECnet Hardware Worksheet
• • • • • •
PSI Hardware Worksheet • • • • •
••••
Software Worksheet • • • • • • • •
• •
Network Configuration Worksheet
PSI Software Worksheet ~ • • • • • . • • • •
PSITST Software Components • • •
•

• • • 1-4
• • 1-10
1-11
••
1-12
1-13
••
1-15
• • • B-2

1-1
1-2
1-3
2-1
A-I

Network Configuration Matrix
• • • • • • 1-2
Maximum Line Configuratio~s
• 1-3
Supported Devices (PSI)
• • • •
• 1-4
Monitor Symbols for DECnet • • • • • • • • • • • • 2-4
Parameter Values For MONGEN and NETGEN • • • • • A-14

TABLES

PREFACE

This manual describes the procedures for
configuring TOPS-10 DECnet
and
PSI
(Packetnet Switching
Interface)
nodes
in a network.
The
procedure for installing network software
includes
instructions for
generating a TOPS-10 monitor that supports the network configuration.
The tools that are provided for configuring the host node,
front-end
software,
and
for generating network links are described, as well as
verification tools for testing
network communication.
This manual
also contains software configuration procedures
to verify DECnet
network links over Ethernet (NIA20) circuits.
The
installation procedures
include
information
for
configuring
front-end
software
for DN20 devices.
You can run DECnet software on
the front end, or on
PSI
(X.25)
software.
This manual
contains
instructions
for installing both types of network front ends, because
you must install DECnet in order to run PSI software.
To
install
a
DECnet MCB
front end, follow all the procedures EXCEPT those in gray
shading.
To install PSI software, follow all the procedures INCLUDING
those in gray shaded areas.
Intended Audience
This manual is intended to be used by the experienced TOPS-10 operator
or software specialist.
It explains all the information needed to
install DECnet or PSI on the TOPS-10 KL or KS system and on
the DN20
front
end
(KL systems only).
To perform the installation procedures
documented in
this manual,
you must also
be
familiar
with
the
procedure for installing the TOPS-10 Inonitor and the GALAXY system.
Before attempting
to
install
TOPS-10
networks,
see
the TOPS-10
Software Installation Guide, which contains worksheets for recording
information that you must supply during
the
installation procedure.
Some of
that information will be necessary during the DECnet and PSI
installation procedure as well.
This manual contains all the commands you need to restore
files
from
distribution tapes using the BACKUP program.
This manual assumes that
you are experienced with the tape mounting and dismounting
procedures
and
the BACKUP program.
For more information about these proce~ures,
see the TOPS-10 Operator's Guide.
The DECnet network is controlled by the NCP command level
within
the
OPR program.
To verify the network connections and correct problems,
you must know how to run OPR and use NCP commands to
control
network
parameters and devices.
The OPR program is described in the TOPS-10
Operator's Command Language Reference Manual.
To
learn more about
DECnet network management and PSI network management commands, see the
TOPS-10 DECnet and PSI System Manager's and Operator's Guide.
vii

For PSI instellations, you should refer to
cards fo~ PSI network-specific info~n~tion:
0

PSI NSI

PSI NSI DATANET-l Card

PSI NSI 'l'RANSPAC Card

PSI NSI TELENET Card

PSI NSI DATEXP Card

PSI NSI 'rYMNET Card

PSS

the

following

reference

Card

You may need the x.2S and X.3 parameters
Packet Switching Network (PPSN).

supplied

your

Public

The following lists CCITT (Consultative Committee for International
Telegraph and Telephone)
recommendations relevant to users of the
TOPS-10 PSlsoft'N'are and the CCI'TT publications in which those
recommendations are discussed.
The information in this manual is
subject to change. For more information contact the CCITT.
Recommendation

Documen t
-.-----

X.3

Document AP VII-No.

5-E

X.25

Document AP VII-No.

X .. 28,X.29

Document AP VII-No.

The following document contains a complete and unabridged form of the
key CCrTT recommendations as they appear in Fasclle VIII.2 of the
Yellow Book of the Consultative Committee for International Telegraph
and Telephone, 1981 e<iltion.
The X.2S Protocol and Seven Other Key CCIT'r Recommendations:
X.I, X.2, X.3, X.21 bis, X.28, and X.29,
Lifetime Learning Publications~ Belmont, California 1981.
l

vii i

Conventions in this Manual
The following conventions
descriptions and examples:

are

used

this

manual

command

UPPERCASE PEINT

indicates what you
s t r i nq •

Lowercase letters

indicate a
type of variable
(name,
number,
for example)
)
in r) command
strinq for which you must supply the
actual text or number.

type

command

:Inf()r",t~ttd.J'l·hi9hli9hted

:$hadin9~pt'1 testo'

with
gray
conf :LgtJrati()n : .and

i~s~.allation.of . . . PSlnodef~·.O:il1Y.,.·~11
.nory;o;.sb~Q~d,.ar~a·$, . app~y . l~O', p:oth ::DEqnet
and'PStI .•. ;ns:~aJla.tJpn, unlH'ss oth¢.rwise

not'ed' 1'h t£h~te·xe.··"

. .

<ESC>

means press the ESCape or ALTmode key.

ineans hold thl~ CTRL key and press the
character "x. w For example,
<CTRL/C>
means hold the CTRL key while you press
the letter "C.'Ii

Unless the instructions in the manual indicate otherwise"
every command by pressinsr RETUHN.

you must end

This manual contains installation procedures for both DECnet and PSI
software
for TOPS-10 systems.
To install PSI software, you also must
install DECnet software on the host node.
Organization of this Manual
Chapter 1, NETWORK CONFIGURATIONS, contains descriptions of the
various hardware confi9urations that are required to ~:;upport DECnet
and PSI gateway software. This chapter also contains an overview of
the entire
installation procedure,
instructions
Eor preparing to
install network soEtware, and worksheets you can use L.>
record
th,e
values of the numerous parameters requirE'd in the procedures.
The
files required for installing DECnet and for
instRlling PSI gateway
are also listed in this chapter.
If you have never installed DECnet and PSI, Chapter 1 will
help you
get started.
If you have
installed network software before, you
should read this chapter to review changes to
the software and
the
installation procedure.
Chapter 2, GENERATING TOPS-10,
describes the procedures you must
follow to configure the host system software to prepare it to support
DECnet communications.
These instructions are based
on
those
described in the TOPS-10 Software Installation Guide.

Chapter 3, INSTALLING
DN20
NODES,
contai~s
a
description
procedures
for
c~nfiJuring
and
generating
DN20 software.
installatior1 (]Ot?::; not incllldF~ d DN2~', you can skip Chaptl=r 3.

of
the
I f yo ur

The DN20 front end (supprJrte r1 hy
I{L
systems
only)
r;all
['lJn
DECnet
f r 'J tl t - end
so f t 'II Ci r e
( c a 11 e d t heM CB) 0 r P:; I gat e way so E t w:=j r e •
Us i n g
the Nr~TGEN proCjrcllTI, you c~l1figure the front end software by
dnswering
questions
in
.3 ~lialo'J and in~ludin'] the values of para:neters for the
netw'.)rk. G:Jn:igurCition
fi.l~s.
N~~TGEN
produr;es
these
configur3':ion
f i1 es ,
wh i c h
art?
pro c E! S :'3 e: 1 ;) y
a
bat ,.~ h
con t r olE iJ f! t hat i S a Iso
des C' rib e din t h L::; c h d pte r" •
Cha pte r 4, CONFICURING NETWORK
NODES,
(1 es,~ t" i b(7S
t he
~) ro c ed 11 r e
fa r
creating
network
SupP0rt
fi les .,nd veri f ication batch Ei les f()r the
net.work software.
You run the NIPGEN pro']ram to
create
the
N(:P.CMi)
fi Ie
use:1
by
OPR
and
the
batch contr()l Ei les you can dS(~ tr) test
net.work conne,::tior'ls.
This chapter also contains rlescriptions
of
the
changes
you
must
rnake
to
systr~:n
initialization
fil.p,s
(such
dS
SYS,]OB.INI and SY:;TEM.CMD) to :3t~rt tlp network softw"'lu!
'':Itltom.~ti',''.'!alll
~t system st~rt~p.

To install PSI, you must also run the COMGEN program to Greate the PSI
iniiiallzati9n file for OPR, X2SNM.CMD. COMGEN allows you to create
files that are used by the batch jobs that verify PSI network
connect fons.
Chapter 5, GENERATING PSI INITIALIZA.TION FILES, describes the methods
for testing network functions, and ways to correct errors or problems
you might find. This chapter also contains procedures for installing
PSI software on other TOPS-10 systems in the PSI network.
After y~)U have followed the prr)Ct2jur(~S in Chapters 2
thr'ough
5,
th,~
network
!3hould
be
installe"]
and
rut1nin(J.
Tl-je ,lppendixes contai.n
add i t i 0 r'l a l i n E() en a t ion
r1 h 0 u t
too I s u s e d
:J iJ r i IV]
the
i n.s tal 1 a t .i. 0 !)

praced u r ."!:; •
AppenrJi:< A, NETGEN,
messa]es in rletail.

lists the

NETC;r~N

commands,

parameter:;,

r1t1d

err')(

p~) I

t e r ms

Appendix B, PSITST, describes the PSITST program in detail.
A P pen (] i x

::, G LOS S /\ RY, r:; 0 n t a ins a 9 los') ,) r y :) f
that are usp,d in this manual.

the

f) E C net) n d

CHAPT:ER 1
NETWORK CONFIGURATIONS

TOPS--10
DECnE't
extE~n(ls
the
capabilities
of
the
DECsyste~n-10
by
supplying
protocols
that
TOPS-10
programs
use to communicate with
programs on other systems.
The DECnet protocols that
~overn
message
communication
allow
3ny
task
running
under
the TOPS-10 operating
system to communicate with any other task in the
network.
DECnet-10
allows
communications
'~vith
other
systerns
running
DECnl=t and DN20
communications front ends.

';;Th~>'TtjPq~10"r~qk4S!tn~t 5ystemlnter f,ace, (PSI), Gateway provides access
The PSI Gateway is 'the

',i;to'>cP1,JPli¢'pa9k,~tSw~tcllin9 Ne two rks.o (PPSNs).
;!i:tlt'~rc~~ce,:petrreel-l a,P1?SN'and a DECnet: net:woik.

"The "'" Gateway, ,softW'are
" D~~9net-U' software" in a DN20 as several Multifunction
"j:;omrnunica'ttons Base (MeB) processes.
Tn the network,
each
processor
Hr,e$lde$,~lth

i s a n 0 dew 1 t h a n am e and a un i que ide n t i f yin gad d res s •
Th e s y s t e ill S
in the network that support intf~r;lctive command execution are the host
nodes.
All
processors
dedicated
to input and/or outp~t are called
front ends, or servers, becaus(~ these types of nodes depend on a
host
node for loadtng software into me!WJry and perfonnirvJ software recovery
ElInctions.
The DECnet front e'nd is based on the
DN21~
comrnunic"ltions
-Jevice.
To install the network soEtware, you must be Eamiliar with the type oE
hardwarE~
that
}'our
system include:-;, and you must know the names and
address numbers of nodes that will communicate wit~ the
system.
You
configure
your
network
node by id€~ntifying the nodes in the network
and describing the har~ware and software characteristics of the nodes.
The TOPS-10 system runs on two diEEerent types of processors,
the
KS
These
(DECSYSTEM-2020) r
or
the
f~L
(DECsystem-1090/l091/109 5).
which
processors have different network c~nfiguration
possibilities,
are described separately below.
1

1.1

KS NETWOHK CONFIGURATION

The KS system running TOPS-10 has mare limited capabilities
than
the
larger
KL
processor:
the
KS
does
not
support
DN20
hardware.
Therefore, to install network software on
a
KS
system,
it
is
not
necessary
to
bllild MCB or X.25 gateway software.
To use thi:3 manual
to install KS network software, Eollow all
the
instructions
except
those
in
Chapter
3 or
those
that
are
gray-shaded.
Ignore all
procedures related to the NETGEN program, the DN20 front end, and PSI.

1-1

NgTWORK CONFIGURATIONS
1.2

NETWOR¥: CONFIGURA'JrIONS

TOPS-10 on a KL processor supports DECnet
~nd
PSI communic~tions.
DECnet configurations include the DN20 running MCB softw3re, or the KL
can communicate in the DECnet network over
the Ethernet.
The KL
processor supports DN20 front ends running PSI softw~re as well.
The
PSI network confiquration is describj~d in Section 1.2.2.
The DN20 processes data transferred over synchronous communi~ations
lines.
The
DN20
is
a PDP-II
processor
that
I'uns
I:he MCH
(Multifunction Communi~at:ions
Base)
operating system..
You
must
configure
the MCB software
using the NETG~N program before you can
loacl the DN20.
nSCneL also supports the NIA20 device,
which provides communic~tion
between nodes on
the same Ethernet network.
Althouqh DECnet is not
require] for Etheo1et communicat.ions, it provides methods of ensuring
data inte!]rity, such ,y, automatic retransmission of lo':;t ;ne~:;::;a'Jes.
Th e Ethe U1 e t .'l1 I 0 \~7 S DEC net toe 0 'n mun i cat e wit h the 1 0 cal are d
0 f
the
network,
including
up to
L024
nodes.
DECnet allows up to 63 such
areas, each consisting of
up to
1024
nodes.
This configuration
requirp.s
that nodes with addresses outsUle of the local network area
be specified using the area number as well as local node address,
in
the form:
area.adr]rr~ss.

DECnet

Net'~ork

Configurati.ons

The KL and KS

net\~rork

configurations are illustrated in Tabll:! 1-1.

1.2.1

Table 1-1:

Network Configuration Matrix
---,

CPU Type:

Circuits:

ETH--0
DTE-0 - ( 1-3)
DTE-l- ( 1- 3)

::P-~=;;----I

DTE-2-(1-3)

Node Types:

-t- - -- - - - - Front end
Nodes:

Host
Target
Ad j acent
Remote
File Transfer
MCB --Adj ';'1ce nt

KDP~~-l

Host
Ad j r'lcent

I
I

Remote
File Tcansfer

_No~:~~~=~-:I

DN20/MCB

----------_._--

Before you can ge~erate and inst~ll network communications software,
your system manager must determine the bau~ rate for communications
based on the type of network controller and
the number of lines.
Table 1-2 lists the maximum line configurations allowed for each type
of network device and
the maximum line speeds allowed
Eor each
configuration.

l-~

NETWORK CONFIGURATIONS
Table 1-2:

Maximum Line Configurations
Supported
Devices

Lines Allowed
At Baud Rates

NIA20

1 per CPU

DMCll

2 lines at 1000kb, or
4 lines at 56kb

DMRII

2 lines over 56kb, or
4 lines at 56kb

DUPII

8 lines requlrlng
1 KMC-ll per 4 DUPlls.

On KL systems:

On the DN20:

This KMC/DUP combination
is referred to as a KDP.
On KS systems:
KDP

1.2.2

2 lines allowed

PSI NetworkConfi9urati.ons

This sedtiQndescribes PSI hardware configurations.
installing PSI software, continue at Section 1.3.

you

are

not

You must ruri TOPS-10 PSI on a DECsystem-1090/1091/1095 •...Follol,JI the
same. proced~re for all of these machines. To run TOPS~10 PSl~ the
TopS-10 monitor~ GALAXY software, and DECnet-10 software ~ust. 'b~
insta-lled •.. You may be running in either timesharing or stand-alone
mode while you ~onfigure the fJoftware, ~ut you must reload the .syste:m
to install the software and verify the network connection~.
Netwbrk dorifiguratlon files are provided on two distribution lapes~
,0'

DE,Cnet-10 Distri bution Tape

TOpS-10 PSI Distribution Tape

The di~tribution tapes are BACKUP-formatted tapes.
You mustcrea<tea dtrect«:>ry on dIsk for storage of the 9E!t1eratiPrl ·an(l
installation files.
You
wi.!1 need to allocat$15,09{0b'10cks for
DF;Cnet/~Sl~storage •. Consult wi th your system manager. to' be .. ·sure
YQ'u
{haVe enp ugh space be fo re you beg in the genera t i on proced ut.es.·

must know your
hardware
configuration
to
perform
this
installation..
The
maximum
number of each type of suppoifed
commun ieat i,ons d E~vi ce in the DN20 X. 25 gatewa y f ron tend is' shown in
Table 1-1.
For more informa~ion, see the TOPS-10 PSI VI." GPD
(Software Product Description).
---,
'.lOll

1-3

NETWORK CONFIGURATIONS
Table 1-3:
Device

Supported Devices (PSI)
Max imum Numb€'r

DMClls

DMRlls

KMC-ll

DUPlls
for KDP

'fOPS-10 PSI, in a DN20 X.25 gateway front end, supports 2
to the PPSN and 1 DECnet-10 connection.

connections

If your system supports more thc'3n 1 (one)
DN20
front end,
see the
DECnet-10, Version 3.0 SPD for a list of devices supported on the DN20
l)ECnet frontend~- The fol1owinq diagram illustrates the configuration
of a typical PSI front-end node.

KLy

)J-

CFE

KLx

CFE

MRS-3699-S4

Figure 1-1:

Configuration of a

DN2~/TOPS-10

1-4

PSI Node

NETWORK CONFIGURATIONS
1.3

OVERVIEW OF INSTALLATION PROCEDURES

in this
To install DECnet, you must follow all the steps described
manual except those that are in gray shaded boxes. If you are
"~!'lstal+ihgPSI, ,you, mu:;;t
follow all the steps in this manual,
/'$ticludin9tho~e :In gray fshaded boxes.
The procedure for generating and installing DECnet is summarized here
for your convenience.
This is only an overview of the installation
procedure. The actual installation instructions begin with Chapter 2 •
•

Step 1:

Initial Preparation

Before you install network software, you must become familiar
with the procedure and the tools you will use in the
procedure. Read this manual from start to finish, and fill
out the worksheets provided at the end of this chapter. The
time you spend preparing to install the network software may
prevent confusion and errors during the installation process.

Log into a directory that has access to all necessary files
for a monitor generation. In this manual, we call this your
"build directory."

If this system has no previous version of DECnet, create a
unique directory for DECnet files.
If you are installing
,1'SJ;and tl1ere:ls no previous version of PSI; create a
spe'ci,al ar,ea for PSI files.

Restore files from the
build directory.

Read the beware files. Check the distribution package for a
hard copy of the beware file.
The hard-copy beware file
!=:Iln~r!=:~o~!=: th~ on-lin~ beware file.

:rfyou,~re installing PSI, re 13 torethe "files
distributibn tape to your build directory.

Sefqr¢ installing PSI software, read the I?SI.BWR file.
If
th~re
15 "B hard copy of the beware file in thed istr ibution
package,. the hard-copy supersedes the on-l ine beware file.

Prepare your information using the worksheets provided at the
end of this chapter.

~Step 2:

DECnet

distribution

tapes

from

the

your

PSI

Modify MONGEN and GALGEN Procedures

Generate your TOPS-10 monitor using the instructions in the TOPS-10
Software Installation Guide. Modify the MONGEN and GALGEN procedures
to include network information.
Instructions for modifying the
monitor and GALAXY generation procedures are described in Chapter 2.
o

Generate the TOPS-10 monitor with network support.

Generate the GALAXY software with network support.

You can install the monitor and GALAXY now, or you can
generate the network software first, and install the entire
s y stem 1 ate r •

1-5

NETWORK CONFIGURATIONS
•

Step 3:
DN20

Configure Front-end Software
you must configure software that will be loaded
into
DECnet, you must enerate and install MCB software for

The following steps are applicable only to systems that include
front
ends.
KS systems do
not support DN20
front
ends
for
network
communications.
Therefore, if you are installing DECnet on KS,
you
can skip these steps.
The following procedure is documented in Chapter 3.
o

Run the NETGEN program and initiate the dialog
to describe
the
hardware
and software characteristics of your DN20.
To
generate MCB software
choose the DN20
ion when NETGEN
starts ..

After you run NETGEN, check the configuration information and
make
any corrections
that
are
required.
When
you are
satisfied
with
the
configuration
information,
save
the
configuration files.

file
that
Submit the batch control
MCB
software,
this
so ftwa re.
Fa r
MCBSYS.CTL. i~~~:T~~;~~~.~~~~~tf~n~~~~j~~~~~

builds
front-end
the
batch
is called
job

Check the log file from the batch job for any errors
in
the
build
process.
If
you must change any configuration
information, run NETGEN again, and use the RESTORE command to
restore
the
configuration
file.
Modify the necessary
parameters, and use the SAVE and FINISHED commands
to
save
the changes.
Then submit the batch control file once again.
The batch control file creates a system image for
the
front
end
as a file named nodename.SYS, where nodename is the name
of the front-end node, as you specified in the NETGEN dialog.

•

Copy nodename.SYS to the SYS:

Copy any other necessary files to SYS: •

Step 4:

area.

Create Network Configuration Files

Next you must create files to load network
software and verify the
network connections.
The
NIPGEN program,
described in Chapter 4,
allows you to enter the appropriate information and creates
the
file
you need to load and verify network software.
o

Run the NIPGEN program to create
the command
and
files used to verify and load your network software.

Copy the NCP.CMD command file, created by NIPGEN,
directory to the SYS:
area.

1-6

control

from

your

NETWORK CONFIGURATIONS
To install PSI, you must also use COMGEN to generate PSI
installation
and verification control files by performing the following procedures:
1.

Edit the file X25CNF.BNF and
parameters.

substitute

your

site-specific

Submit the COMGEN.CTL batch job, which produces the following
files:
X25NM.CMD, PSITST.INI, and X29SRV.INI.

Check the log file produced by the batch job for
any errors
In
the building process.
If there are errors in COMGEN.LOG,
correct the errors in X25CNF.BNF and run COMGEN again.

When the confi3uration procedure is finished, edit
the
system
files
SYSJOB.INI,
SYSTEM.CMD~
and
NCP.CMD
to
include
commands
tha t
automatically start up the network software •
. . Step 5:

Load and Verify Network Software

Load the monitor and [rant-end
software.
Verify
that
the
loarling
process
is
complete,
and
verify
that
network
connections
are
activated.
Procedures for accomplishing this are described in Chapter
S; a summary follows:
o

Ha I t t h e

[ ron ten c1,

t h ~ n shu t cl 0 wn

and

reload

the

TOPS-10

system.
the
monitor
procedures to

If the TOPS-10 monitor doe:3 not cOlne
up,
load
that
was
runniwl previou!3ly, and examine yC"-lr
find the error.

1fT (I P S -- 1 0 'J 7 • 0 3 and the fro n ten d com e up co rr- e c t 1 Y ,
sub mit
the
batch
filC' NIPT~:.'I'.CTL from NIPGEN to verify connections
to the ildjacent nodes.
Check NIPTST.LOG
Eor
errors
before
proceeding.
If
there
are errors in the log file, you must
run NIPCI~N to correct the errors, then resubmit NIPTST
until
it runs without errors.

If the network does not come up,
with the fol1owin~ procedures:

try

start

manually

Use the OPR command TAKE to take SYS:NCP.CMD.

For PSI installation procedures, you
can
also
use
the
TAKE command to execute the commands in SYS:X25NM.CMD, to
~efine X.25 network management parameters.

Use the NCP command LOAD NODE to load the DN20.
DN2C come~') on line, resubmit th,e NIPTST control

If
file.

the

If there are other DECnet nodes in the network, te~3t
networ"k
file
transfer capabilities, by submitting the NIPNFT control
file.
Check the loq
file
and
correct
any
errors
before
proc ped i ng •

1--7

NETWORK CONFIGURATIONS
o

To verify the PSI X .. 25
following' procedure:

connections,

perform

the

Use NCP SET and LOOP LINE commands to perform a
loop test.

Run PSITST, using the PSITST.INI script file to test X.25
capabilities.

Check the PSITST log for errors.
Correct
repeat PSITST until it runs without errors.

In addition, you can
following procedure:

network

verify

X.29

functions

Call up your local PAD.

Connect to the (X.2S) gateway.

Log out from the host system.

Return to the! local PAD.

After you have veriEieJ

the

lsi n']

set

hardware

errors

and

using

the

connections and
the soEtware
the nod e .j a t a:) t1 s,,~ Eo r a 11 the
nodes in your network, hy editin(j NCP.CMD to
,'nclune node
dRfinitiuns Eor each n01e in the network.
I

t h~ s e p r () c e d u r e:::;,

IJ p

When y~u are sdtisfied with TOPS-10 Version 7.03 and
the
network, c-;opy the new monitor to thE? :'-3ystem boot::;trap tape.

For PSI installation, you can install PSI access software on
other TOPS-10 nodes, as described in the following procedure:
1.

Install the necessary
TOPS-10 nod es ..

gateway

access

Modify the system startup files.

Restart NML on the remote system.

Run OPR and TAKE the X25NM command file.

files

other

If you have corrected all er:c()t-~; you f')und during
the cunEigur,ltion
procedure, the network software will be fully installerl.

1. 4

PHEP.~RATION

If you prepare youe information before performinq
the (~'onfiqur()tion
procedllre rlescrih'2d
in
this marlllal,
the procedure \-,ill run more
smoothly.
Observe the ~JiJideline;s :;ummariz~?rl below before you begin to
configure network software.
()

If you ha'Je n·eV0r installed this versi.on of DEC::net or PSI
heEore,
read
this entire manual.
It explains the tools anrl
parameter::; you l111St define to configure
thE'
network.
Hardware and
soEtware
terms are rlefined
in Appendix c.
PSI-specific hardware and software terms are
indicated hy
'Jray shadin9.
! -8

NETWORK CONFIGURATIONS
To install DECnet software without
PSI gateway software,
perform all the procedures applicable to your configuration,
ignoring the gray-shaded areas of this manual.

Fill out the
worksheets
provided
in
this chapter,
using
parameters
that
reflect
the
actual
hardware at
the
installation.
In many cases, you can accept default values
for
hardware and software parameters, but you must make sure
that these defaults are appropriate
to
the
installation
configuration.
Some of
this
information may be available
only from a DIGITAL service representative.
Also, make sure that each software parameter
is within
the
accepted
range.
You may choose
to
accept
the default
parameters
supplied
by the
installation
tools:
a
safe
procedure, but the default values do not necessarily produce
optimal performance.
Software parameters entered in the MONGEN monitor-generation
dialog must be consistent with those supplied in the NETGEN
dialog.
Those parameters and
the
tradeoffs
involved
in
selecting different values are discussed in Appendix A.

Secure a
terminal
and
location where you will
not be
interrupted during
the on-site configuration, and set aside
at least two hours
for
the configuration procedure.
The
amount of
time
you will
need depends on your own rate of
progress, the characteristics of your configuration, and
the
response
time of
the system you are using.
To install the
final version of your network software, you will have to shut
down the system and the front ends, then reload the system.

You begin the DECnet generation procedure by generating
your monitor
and GALAXY system with network facilities enabled.
Chapter 2 contains
descriptions of the specific MONGEN and GALGEN questions that pertain
to
DECnet and PSI.
See the TOPS-10 Software Installation Guide for a
complete description of
the monitor generation and
installation
procedures.

1.5

INSTALLATION WORKSHEETS

To install DECnet and PSI software, you must provide information about
the hardware and software that will be supported by the configuration.
You can use the following worksheets to record
information that
you
can obtain
from
your
Field
Service
representative and the system
manager.

1-9

NETWORK CONFIGURATIONS
DN20 Hardware Worksheet for DECnet (KL only)
For each DN20, record the following
DTE number

information:

(DTE-0-1, -2, or -3):

Number of DMClls (0 to 5):
DMC-0
DMC-l
DMC-2
DMC-3
DMC-4

cost:
cost:
cost:
cost:
cost:

------ - - - - - -

Number of DMRlls (0 to
DMR-0
DMR-I
DMR-2
DMR-3
DMR-4

half
or
half
or
half
or
- - or
half
- - or
half

Number of KDPs

5) :

duplex,
duplex,
duplex,
duplex,
duplex,

full
full
full
full
full

cost:
cost:
cost:
cost:
cost:

(0 to 2) :

For KDP-0, number of DUPlls ( 0 to 4 )
KDP-0-0
KDP-0-1
KDP-0-2
KDP-0-3

max imum
maximum
max imum
maximum

baud
baud
baud
baud

rate:
ra te:
rate:
rate:

- - - - - cost:
cost:
_._--- cost:

cost:

For KDP-I, number of DUPlls (0 to 4):
KDP-1-0
KDP-I-I
KDP-I-2
KDP-1-3

maximum
max imum
maximum
max imum

baud
baud
baud
baud

ra te:
------ cost:
ra te: - - - . - cost:
r a t(~ :
- - - - cost: - - - - . cost:
ra te:

For KDP-2, number of DUP11s (0 to 4):
KDP-2-0
KDP-2-1
KDP-2-2
KDP-2-3

max imum
maximum
max imum
maximum

Figure 1-2:

baud
baud
baud
baud

rate:
cost:
rate: _._---- cost:
ra te:
cost: - - - - . rate: - - - - - - cost:
.--~----

DECnet Hardware Worksheet

1-10

NETWORK CONFIGURATIONS
DN:?0 Hard w.:.te Wor kshe.~t for PS I

(RL onI y)

For each DN20, specify:
'DTE nUll'lber (OTE-"-l, -2, or -3):
Cost:
If there is a DMCll, specify the cost:
If. there is a DMHll, specify half
Cost:

- - or full - - - duplex.

----~----- ...- ......- - -... *-.~

Number of KDP devices on the DN20

( l~

1) :
----------.-.~.'.---

For KDP-0, specify the number of DPU circuits (0 to 3):
For each KDP circuit, supply the following information:
KDP-0~0

datalink protocol type (DDCMP-DMC or LAPS):

Maximum baud rate:
-----'---.--.-Cos t (D DCM P- DMC 0 n1 y )-;----------------..,--.. -.--. --_._,....._- --"-_.--_. __... -. -~-----.

DTE addres~ (LAPB onl~i~~~--~~.~~=~~~__~
Channel range for this DTE (LAPB only) : ___"___............_ ...._ .. _.._...___._. ______
protocol type (DDCI\<1P-DMC, LAPB) : _ _ _ _ ~_~_ _rate:
________ "~,.,,..._.____..___ ._,______._
Cost (DDCMP-DMC only)::
____~_ _
.. __._____._~_~____..._. "__. _. _____
DTE addtess (LAPB only):
G~an nel ra 09 e fo r thi s DT E(L'A PB 0 n iY}:---·-"'"--~----~~~~~·-===~:-=

KDP~0-1pataljnk

Ma:~ im Uftl'b a U:¢

KDP-:-~~2(:iat;a~ 1nk

protocol type

(DDC1VJP-DMC, LAPB) ! ___- -

Maximum hatJd rate:
Cost '. (DDCr.1J.'::" DMC

. . -.-.--------

0 n 1 y) : ---- -.-.--.------~-.~-.-~---..---~.--.--"--."---'--'--._.-.-.'

0 n1y
Chant'leJrange for this

r;[)'I'E
_~=-'--=:=:--=='==--"=====~:_-(LAPB only) ! _ _. _______._ _._. _ _ _
. ___',_._._

DTE ad dres s

(LA PB

Figure 1..;.3:

PSI Hardware Worksheet

1-11

NETWORK CONFIGURATIONS

Network Software Worksheet (KS and KL)
Dis~ Space Needed:
DECnet V4.0
TOPS-10 V7.03
CUSP
TOPS-10 PSI V1.0

For NIA20 only:
2000 blocks
For DN20/DECnet: 10,000 blocks
For PSI/DECnet: 17,500 blocks

The following parameters apply to DN20 nodes for both MCB and PSI
generation procedures.
Refer
to Appendix A for information about
these parameters:
DN20 node name:

address:

Parameter

Default

Buffer size

(290 to 576)

Identification

(1 to 32 char's)

Inactivity timer

(1 to 65535 sec's)

Maximum address

(2 to 255 )

255

Max imurn cost

(1 to 1022 )

100

Maximum hops

( 1 to

30)

Maximum links

(3 to 23)

Max imum visits

(16 to 255)

---------------------------------

Outgo il19 timer

( 1 to 65535 sec's)

----------

Retransmit fae to r

( 1 to 15 )

Routing timer

(1 to 65535 sec's)

Transmit password

(1 to R char's)

DECNET20

Management user
Management account
Management password
Figure 1-4:

Software 1Norksheet

1-12

576
DECNET

Ve r s i ,)-n---=3-.-:'0'--R-e-=1:-e-a-s-e--

---------

-----------------

-------------------------.------------------

NETWORK CONFIGURATIONS
Network Configuration Worksheet
This worksheet lists the parameters you must supply to
the NIPGEN
program,
to configure the network software
for your host system.
These parameters apply to both DECnet and PSI installation procedures.
NIPGEN is described in Chapter 4.
Host Node Definition:
Host name:

-------------------------------------------------------------

Host node address:

----------------------------------------------------

For the NIA20, specify circuit names as ETH-0: ____________________
DN20 Node Definition
(Supply the following for each DN20 node that must be down-line loaded
from the host system.)
Target node name: _____________________________________________________
Target node address: _________________________________________________
Host's service circuit for target node:

----------------------------

Target node type: _____________________________________________________
Target node's service password:

-------------------------------------

Target node's Ethernet address: ____________________________________
Adjacent Node Definition
(Supply the following for each node directly adjacent to the host.)
Adjacent node name:

-------------------------------------------------------------------------------------------------

Adjacent node address:

Host node circuit to adjacent node:
DN20 Adjacent Node Definition
(Supply the following for each node directly adjacent to the DN20.)
Adjacent node name:

---------------------------------------------------

Adjacent node address:

------------------------------------------------------------------------------------

DN20 circuit to adjacent node:
Figure 1-5:

Network Configuration Worksheet

1-13

NETWORK CONFIGURATIONS
DN20 Network Management Information
(Supply the following for each DN20.)
Network management user-id:
Network management account:
Network management password:
(Supply the following for each remote node in the network.)
Remote node name:
Remote node address:

-----------.-------------------

File Transfer Test Information
(Supply the following for each node with which you will
transfer tests.)
Test file transfer to node name:
File transfer node address:
User-id for file transfer test:
Account for

file transfer test:

Password for file transfer test:
Figure 1-5:

Network Configuration Worksheet (Cont'd)

1-14

perform

file

NETWORK CONFIGURATIONS
PSI Software Worksheet
To install PSI software, you must edit the distributed
X25CNF.BNF file, providing the following information:

copy

the

DN20-node-name:
DTE-address:
Name- 0 f -PPSN-:--P PSN - ae e e s s _. pa s wo rcf;·----·-·-·--,.----------_ _ _ _ _ _ _ _ _ r+_· _ _ _ _ .... n _ _ ... _

................... _ _

The following information defines the PSI frame-level characteristics.
If your PPSN subscription requires non-default values for any of the
following parameters, you can use the NE1'GEN program to change the
values. Otherwise, you should not change these parameters.
NETGEN
Parameters

CCITT

Max imum Window

Default
Value 7

Maximum Retransmits N2

Retransmit Timer

1'1

3000

Maximum Data

Max.

packet si ze

128

Max imum Window

Max.

window size

Restart 1'imer(sec)

1'20

180

Call Timer ( sec)

T21

200

Reset 1'imer(sec}

1'22

180

Clear Timer(sec)

T23

180

Maximum Clears

Max imum

Max imum Resets

Max imum

Max imum Restarts

Max imum

Figure 1-6:

PSI Software Worksheet

1-15

PlPSN

V,3"1 ue

NETWORK CONFIGURATIONS
1.6

FILES REQUIRED FOR INSTALLING NETWORK SOFTWARE

This manual assumes that TOPS-10 Version 7.03 is being
installed,
or
has been
installed.
Instructions
for
installing
the monitor are
included in the TOPS-10 Software Installation Guide.
You can generate
the monitor
anCl--the---network software, then install them on the same
system reload.
Or you can install TOPS-10 and
GALAXY,
then
install
the network
software.
For
the
network generation procedure, the
system need not be brought up for standalone operation, but
you will
have to reload the system to install the network software.
The DECnet installation procedure and the PSI
installation procedure
are very similar.
To
install
PSI software, you must also include
DECnet files.
Therefore, the files
described
in
this
section are
important
for
BOTH DECnet and PSI installation procedures.
Section
1.7 describes files required ONLY for PSI installation.
If
you are
not
installing
PSI, you can skip Section 1.7.
If you are installing
PSI, you must read this section as well as Section 1.7.
All the DECnet-specific network configuration files
are
supplied on
the DECnet-10 Version 4.0 Distribution Tape.
The monitor distribution
tape contains the BACKUP program, which you use to copy files from the
distribution
tapes to the disk area.
You may also use BACKUP to save
the network software after
you have generated
and
installed
the
netwo rk.
The DECnet distribution tape contains the following files to help
generate and install DECnet and PSI network software:
o

The documentation
incl ude:

files

associated

with

DECnet.

you
These

The DECNET.BWR file contains important information about
the software and changes since the previous version.
The
beware file may also be distributed
in hard-copy form
with the distribution package.
The hard-copy beware file
supersedes the on-line beware file.
The .HLP files are text files
commands.

that describe

The .DOC files describe the edits made
modules.

the

network

the

software

Files needed to support the task-to-task, file transfer,
and
network command terminal capabilities for your configuration.

Software tools, including programs and
batch control
files
that
allow you to configure your network software, generate
front end software, ~nd verify network connections.
These
tools are described below.

NIPGEN.EXE, a program that enables you to generate files
for
verifying
and
loading
your network software.
You must run
NIPGEN for both DECnet and PSI installation procedures.

You must install front-end software if you have a DN20
communications
front
end.
The DN20 can run either MCB software (for DECnet) or X.25
gateway software (for PSI).
The following files allow you to generate
and install front-end software for KL systems:
o

NETGEN.EXE, a program that allows you to enter parameters for
either
DECnet or
PSI
front-end network software.
You run
NETGEN
to
configure
DN20
MCB
software
for
DECnet
communications, or X.25 software for PSI communications.
1-16

NETWORK CONFIGURATIONS

NETGEN creates the configuration files
NETPAR.MAC
and
CETAB.MAC, which contain the system parameters and database
for
the DN20, and
NMLACC.MAC,
which
defines
access
information that remote sites must furnish before they can
issue certain commands.
NETGEN also creates the configuration file that you describe
in
the
NETGEN
dialog.
The dialog creates the file
nodename.CNF.

1.7

DNMAC.EXE, a cross-assembler for PDP-II macro source files.

PDP-ll files for all modules needed
for any configuration,
including object modules, symbol tables, and memory maps.

TKB36.EXE, a program that constructs
images from object files.

VNP36.EXE, a program that creates the front-end system image.

MCBSYS.CTL, a control file for building the MCB software
DECnet.

FIL~S

PDP-II

formatted

task

for

REQUIRED FOR INSTALLING PSI

I,naqdition to the files list.ed in Section 1.6, you must also hav'~ tbe,
foll:<,>wln<j, ,files if you are installing PSI software:
in stall at i on too 1 s •

Do c urn en t. a t ion f i 1 e s abo u t

tO~s-10binary

PDP-II fi.les for configuritlg PSI software} these inclw:le ta,sk,
modI.11es ,symbol tables" and memotymaps.

TOPS-10 source files needed for, PSI installation.

Tools used for installing and verifying

t: he

flIes needed fat inst~llati~h.

PSI~

MCB~.25.CTL i.s a control file for bldlding a DN20 ,X.25 gatewd,Y,'frp;rt
end for TO'PS-10 PSI systE~ms.
When the 'commands in th is EfIe have. 'been
executed, YQur build dirE~ctory will contain the necessary PSI' sys'terh
imag.efile for the DN20.

Among the binary files are PSITST.EXE, a program that allows you to
verify y~ur host's connection to the X.25 gateway.
PSITST is
ciomprised of PSITSB.EXE,
a
background
process
that
fjandle~
cc>tnmunfca t iOhs \Ii i th thE~ X. 25 PPSN, and PS ITST. EXE, a fOreg round'
process, which prOVIoes a
user command interface to control the
activity of the background process.
To make X.29 connections" 'yOU use
another binary file, X29SRV.EXE.
This program provides X" 29 network functions, and is descr ibed ih the
TOP$-10 PSI User's Guide .. Many of these files are provide.d
in the
DECnet- and -PSI "distr-r5ut ion packages. Others are crea ted dur Ing the
installation procedure ..

The instructions for installing a monitor to support
networks are described in Chapter 2~

1-17

DECnet

and

PSI

CHAPTER 2
GENERATING TOPS-10

Before you can perform the DECnet and PSI generation procedures, you
must generate a TOPS-10 monitor and GALAXY subsystem to support
network functions.
Use the TOPS-10 Software
Installation Guide to
install TOPS-10 and GALAXY.
This chapter describes only those steps
you must modify to support DECnet and PSI.
Log in, using the PPN where you wish to perform the generation.
The
disk area used
for generating and installing software is called the
"build area." If this is the first version of DECnet to be
installed
on the system, use the CREDIR program to create such a directory, to
contain the DECnet-related files.
In the
following
procedures,
the
[100,200]
directory is used.
(See the TOPS-10 User Utilities Manual
for more information on the CREDIR program.)

2.1

RESTORING DECNET FILES

Use
the BACKUP program to
restore the
files
from
the
DECnet
distribution tape to disk.
(See the TOPS-10 User Utilities Manual for
more information on the BACKUP program.)

To restore the DECnet files, mount the DECnet distribution tape and
type the commands
in the
following
procedure.
(Use
the actual
magnetic tape drive unit identifier in place of MTxn:.)
.RUN BACKUP
/TAPE MTxn:
/REWIND
/SSNAME ALL
/SUPERSEDE ALWAYS
/PROTECTION 155
/RESTORE *.*
/UNLOAD
/EXIT
Dismount the DECnet distribution tape and verify that the DECnet files
exist in the proper directory, using the DIRECT command.
Before proceeding, read the DECnet beware file, DECNET.BWR.
Note that
any hard-copy beware file supersedes the copy on the DECnet tape.

2-1

GENERATING TOPS-10
The DECnet distribution tape contains files
that you must copy to
SYS:.
Use
the COpy command to transfer the following files from the
bui ld area to SYS: •
• COPY
.COPY
.COPY
.COPY
.COPY

SYS:=NFT.EXE
SYS:=NML.EXE
SYS:=FAL.EXE
SYS:=CTHNRT.EXE
SYS:=NETWOR.EXE

You must also copy the NFT.HLP and CTHNRT.HLP files to the HLP: area:
.COPY HLP:=NFT.HLP
.COPY HLP:=CTHNRT.HLP
If the configuration includes a DN20 front end
must also copy the following files to SYS:.

(KL systems only),

you

DTEMPT.SYS
DTEMPS.SYS
DTEDMP.SYS
If you are not installing PSI, you can skip Section
with the instructions in Section 2.3.

2.2

and

proceed

RESTORING PSI FILES

This section applies to PSI
installations only.
To
install
PSI
sqftware,
you must restore the DECnet distribution files as well as
the PSI distribution files.
To resto~e the PSI files, mount
the PSI
distribution
tape and
run BACKUP.
Use
the following commands to
restore the files with BACKUP:
.R BACKUP
/TAPE MTxn:

/REWIND
/SSNAME ALL
/SUPERSEDE ALWAYS
/PROTgCTION 155
/RESTORE *.*
/UNLOAD'
/EXIT
When you are satisfied with the files you have restored, dismount the
PSI
tape.
Read the PSI.BWR file using the TYPE command, as shown in
the following example:
.TYPE PSI.BWR
When you have read both the DECNE'r~BWR and
PSI.BWR files,
following commands to copy the required files to SYS: •
• COPY SYS!~PSITST.EXE
.COPY SYS:=PSITSB.EXE
.COpy SYS:=X29SRV.EXE
.COPY SYS:=B36ILB.REL
Copy the X25SYM.UNV file to the UNV: area:
.COpy UNV:=X25SYM.UNV

2-2

use

the

GENERATING TOPS-10

":U$~'t: h~:.,: f:()ll~~Wirg,:~~domm ands

::,area':

' ,'"

• COpy REL,:~X25GAF. REL
.copf REL::=X~~'GAM.RJSL

2.3

GENERATING THE MONITOR

The following sections describe the MONGEN program,
for supporting DECnet and PSI network software.

with

procedures

Follow the directions in the TOPS-10 Software
Installation Guide to
generate the TOPS-10 monitor with MONGEN, and answer the questions
that are listed here with the appropriate network information.

2.3.1

Hardware Definition for KL Systems

For KL systems, MONGEN's HDW dialog asks the following questions:

# of DTEs on CPU0(1,1-4):
If you are generating a monitor for a multiple processor system,
request is repeated for each processor.

this

Respond with the number of DTEs you will use. The range is 1 to 4.
Since the
first DTE supports the console front end (RSX20F), specify
at least 1 DTE port.
For each DTE you specify, you will be asked:
Type of front end on DTEn (RSX20F,ANF10,IBM,DECnet):
Type DECnet in response to this question for any DTE
support communications with the DECnet or PSI front end.

that

In monitor generation for all TOPS-10 systems, MONGEN asks:
Decimal "symbol,value"
At this point, you may want to specify values for DECnet-related
parameters.
Consult your system manager before changing the values of
any of these parameters.
The symbol names and the default values for
the DECnet-related parameters are listed below.
See the TOPS-10
DECnet and
PSI System Manager's and Operator's Guide for more
information about these parameters.

2-3

GENERATING TOPS-10
Table 2-1:

Monitor Symbols for DECnet
-_._-_._•._--_.

Defaul t
Value

Symbol

__. _ - - - - - - - - - - - - - - - -

Parameter

Control parameters:
30*1000
1*60*1000

Incoming timer value
Outgoing timer value

Data link parameter
%DLBSZ

576

Maximum data links buffer size

Router parameters:
%RTB3M

%RTBEA
%RTBRA

64
32

%RTBSZ
%R.TBTI

576
40*1000

%R.TCST
%RTCTO
%R.TITM
%RTMX3
%R.TMXC
%RTMXH
%RTMXN
%RTMXR

1
60*1000
1*60*1000
255
100
16
1023
16

%RTMXV
%RTPRI
%RTT3M
%RTTMI
%RTTM3
%RTTM4

20
5
2
10*60*1000
15*1000
30*1000

Hello timer multiplier for broadcast
adjacencies
Maximum number of end node adjacencies
Maximum number of broadcast router
adjacencies
Buffer size (bytes)
Default maximum routing message interval
(Ethernet)
Default cost for circuit
Endnode cache timeout
Initialization timer
Default maximum node address for router
Maximum line cost
Max imum hops
Maximum node address
Default maximum number of routers on an
Ethernet
Maximum visits
Node's priority to be the designated router
Hello timer multiplier for non-broadcast
Routing timer (mill iseconds)
Hello frequency timer (milliseconds)
Node listener timer (milliseconds)

LLINKS parameters:
%NSDLY
%NSWGT
%NSINA
%NSRTH
%NSFLR
%NSRUF
%NSADL

3*16
10
120
10
1000
10000
2

Delay factor
Delay weight
Inactivity timer
Retransmission threshold
Delay floor (ms)
Delay roof (ms)
ACK delay in seconds
NOTE

The buffer size parameter
(%RTBSZ)
is critical
to
smooth operation of network communications.
The value
associated with this symbol should be the same as that
assigned
to MCB nodes
in
the NETGEN program (see
Chapter 3).
The buffer size paramet~r is discussed in
Appendix A.

2-4

GENERATING TOPS-10
2.3.2

Hardware Definition for KS Systems

For KS systems, the HDWGEN dialog asks the
following
questions that
pertain to DECnet. Answer all the questions in the HDWGEN dialog as
described in the TOPS-10 Software Installation Guide, until
you come
to this question:
#KMC/DUP Lines (0,0-2):
Type the number of KDP circuits on the KS system.
Type of line for KDPx(ANF10,DECNET f USER):
This question is repeated for each KDP (KDP0,KDP1,KDP2).
You type the
word
DECNET
for
the
KDP
circuit that will support DECnet
communications.

2.3.3

Specifying Network Configurations

At the end of the HDWGEN section, select the NETGEN option to
configure network support for your TOPS-10 monitor.
This section is
identical for KL and KS systems.
The MONGEN section that defines your system network configuration
is
called NET.
Be sure
to
use
the same node names and addresses to
define your host system in the following
dialog and
in the NIPGEN
dialog, described in Chapter 4.
After you specify the
file
for
configuration file, MONGEN asks:

storing

the

network-related

Network software (y,N)
Respond to this question with "Y."
Then MONGEN asks:
Name of central site [Six character.s or less.]:
Respond with the name of the host node, in six characters or
There must be at least one alphabetic character in the name.

less.

After the network definition questions for ANF-10, MONGEN asks:
DECnet software?(Y,N):
Respond to this question with "Y."
Immediately following this, MONGEN

asks~

DECnet area number of central site (1,1-63):
If you have multiple areas, type the area number for
system.
Otherwise, your area number is assumed to be 1.

the

TOPS-10

DECnet node number of central site(1,1-1023):
Respond with the node number by which
identified
in
the DECnet network.
between 1 and 1023.

2-5

the TOPS-10 system will be
This must be a decimal number

GENERATING TOPS-10
MONGEN then asks:
Ethernet software(Y,N)
If the system has a NIA20 driver with an Ethernet
question with "Y."

port,

answer

The rest of the monitor generation process
is
identical
directions in the TOPS-10 Software Installation Guide.

this
the

You MUST run
the FGEN dialog,
to generate
the
feature
test
conditionals for
the system. These feature test settings are stored
in F.MAC.
FGEN allows you to choose between the KL feature
test set
(KLFULL) and the KS feature test set (KSFULL).
It is not necessary to
change the standard settings for any feature test switches to support
DECnet or PSI network communications.
After MONGEN generates F.MAC, exit from the MONGEN program by pressing
<CTRL/Z).

2.4

GENERATING GALAXY

If your site has modified GALAXY, you must run the GALGEN program to
generate GALAXY with DECnet.
The directions for running GALGEN are
given in the TOPS-10 poftware Installation Guide.
The GALGEN dialog consists of questions and prompts to help you record
GALAXY-related parameters.
The possible answers follow the question
and are enclosed in parentheses.
The default answer
is shown
in
brackets,
following
the possible answers.
To select the default
answer, press RETURN in response to the question.
NOTE
The following procedure need only be performed on
systems where one or more modules in the GALAXY system
have been modified.
The distributed versions of the
GALAXY programs have DECnet facilities enabled.
Note,
however, that if you make one change to any GALGEN
parameter,
you must supply the answers to the entire
GALGEN dialog, and you must follow
the
GALAXY
generation procedures to produce the GALAXY system you
desire.
In the following procedure, you must include the answers shown
as well as any additional answers required by the installation:

here,

GALGEN asks the following question:
Will you be running applications: (YES,NO)

[NO] YES

GALGEN prompts:
Application name or carriage return to exit (1-20 characters) :NCP
GALGEN then asks the following question:
Table name for NCP (1-6 characters):

2-6

NCPTAB

GENERATING TOPS-10
GALGEN asks:
Internal ORION application (YES,NO)
Simply press RETURN in response to
internal application.

this

[NO]
question.

NCP

not

Application name or carriage return to exit (1-20 characters):
Include all applications required for the system, as listed
in the
TOPS-10 Software Installation Guide.
Press RETURN when you have no
other applications to enter, then proceed with the dialog
until
you
see the following question:
Default network-type for FAL streams (ANF-10,DECnet)
DECNET

[ANF-10]

Type DECNET in response to this question, if you want FAL (File Access
Listener)
streams to assume NFT transfers are from DECnet nodes,
unless the FAL stream has been defined as an ANF-10 FAL stream.
You
can define each FAL stream using the OPR program.
Complete the monitor and GALAXY generation procedures as documented in
the TOPS-10 Software Installation Guide.
the monitor
is
- newAfter
compiled and
loaded,
you can start- the
monitor and GALAXY
subsystem;
or you can continue with the network generation procedures
described in Chapters 2 through 5, and start the monitor, GALAXY,
and
network software at the same time.

2-7

CHAPTER 3
INSTALLING DN20 NODES

This chapter describes a procedure for creating software configuration
files
for
the DN20 front end. This front end is not supported on KS
processors.
If your configuration does not include a DN20
front end
for network communications, skip this chapter and continue with
Chapter 4.
If your system includes any DN20 processors you must configure the
software
to
run on those processors.
The software can support
DECnet-10 communications or DECnet and PSI communications.
When you
configure
the
DN20
software,
you must specify the type of
communications software
to
support.
Before
you
begin
the
configuration procedure described below, review the information you
must provide during
the procedure using
the Hardware Worksheets
provided
in Chapter 1.
F ure 1-2 is
ided for DECnet front end
configuration information.
To configure communications software for
the DN20,
run the NETGEN
program and
specify the type of networking software (DN20/DECnet or
PSI).
Using NETGEN's START dialog, you can configure the files
that
are used by a supplied batch job to create image software for the
DN20.
The files created by NETGEN for both
types
of
DN20
configurations are:

3.1

NMLACC.MAC

CETAB.MAC

NETPAR.MAC

node-name.CNF

STARTING NETGEN

To start the NETGEN program, type:
.RUN NETGEN
NETGEN responds with an identifying message and then prompts
type of software to configure:

for

the

TOPS-10 Network Configurator for DN20 or X25 Version 4A(50)
Node type:
You must first specify the
type of software to configure.
To
configure
DN20/DECnet
software,
type
"DN20."
Procedures for
configuring the DECnet front-end software continue in Section 3.2.
3-1

INSTALLING DN20 NODES
To configure PSI software,
type
"X25."
Procedures for configuring
PSI/X.25
software continue
in Section 3.3.
You can skip the
procedures in Section 3.2.
Initially, you describe the networking parameters by responding to the
START dialog.
If there are existing configuration files and you want
to modify the configuration information, you can RESTORE the files
as
described in Section 3.5.
If are not familiar with
the
parameters you must change,
or
the
commands you use to change them, please see Appendix A.
This appendix
contains complete descriptions of all the NETGEN commands, parameters,
and error messages, and describes methods for correcting the errors.

3.2

CONFIGURING MCB SOFTWARE

The following procedure allows you to specify characteristics of
the
DN20/DECnet software.
For the procedure to specify characteristics of
a PSI nod~, refer to Section 3.3.
The values used in these examples represent common values
that allow
the software
to
run efficiently.
However, you might find that an
adjustment of some parameters (for example, table sizes)
can
provide
more efficient network operation.
For complete information about the
NETGEN parameters, commands, and error messages, refer to Appendix A.
The following steps assume that you are logged
into
the directory
where you will
build your MCB software and have restored the DECnet
distribution tape into your disk area.
The
following
examples
use
[100,200]
as
the
PPN.
Replace
this PPN with your actual PPN when
performing the procedures.
command
activates
the
In
the
following
examples,
the
START
in these examples are
configuration dialog.
The answers given
but your
answers must
representative of typical parameter values,
reflect the actual hardware on your system.
The following examples illustrate the creation of an MCB node called
NEWER.
During your procedure, replace NEWER with your actual MCB node
name •
• RUN NETGEN
NETGEN responds with an identifying message:
TOPS-l0 Network Configurator for DN20 or X25 Version 4A(50)
Node type:

DN20

NETGEN)START
Node name:
NEWER
Node address:
12
Transmit password:
(The text you enter for transmit password IS echoed.)
What DTE port number is used for this DN20:

3-2

INSTALLING DN20 NODES
The total number of DMClls and DMRlls must not exceed 6
How many DMCll lines are on this DN20:
1
DMC-0 Cost:
3
How many DMRII lines are on this DN20:

DMR-0 Duplex:
Full
DMR-0 Cost:
3
How many KDPs are on this DN20:

Number of DUPll lines on this KDP:
KDP-0-0 Maximum Baud Rate:
KDP-0-0 Cost:
3

19200

KDP-0-l Maximum Baud Rate:
KDP-0-l Cost:
4

2400

[Configuration Saved On:
DSKB:NEWER.CNF[100,200]]
[Generating DSKB:NMLACC.MAC[100,200]] [OK]
[Generating DSKB:CETAB.MAC[100,200]] [OK]
[Generating DSKB:NETPAR.MAC[100,200]] [OK]
[Configuration complete]
Type SAVE and FINISH after any additional changes
.Type EXIT to terminate NETGEN
NETGEN)
Check the current parameters for
the MCB to be sure that the
information
is correct.
If you make no changes to the information,
you can EXIT from NETGEN, because the output files have already been
saved.
You may optionally assign management account parameters to
the DN20,
thereby controlling access to the MCB software. These management
parameters are not set automatically, and
there are no defaults
supplied with the configuration.
If you build the MCB software
without defining these parameters~ any user will be allowed to access
the MCB network management
information,
thus placing confidential
network information in danger of being discovered by unauthorized
users.
The network management parameters are not included when you RESTORE an
existing MCB configuration file to modify its characteristics.
If you
RESTORE an existing MCB, you must define the management parameters
again.
To define MCB network management parameters,
type
commands to NETGEN before you SAVE the configuration:

the

following

NETGEN)DEFINE EXECUTOR MANAGEMENT ACCOUNT acct-string
NETGEN)DEFINE EXECUTOR MANAGEMENT USER user-id
NETGEN)DEFINE EXECUTOR MANAGEMENT PASSWORD password
After you define these parameters, you use SAVE
configuration, and FINISHED to save the output files.

3-3

save

the

INSTALLING DN20 NODES
3.3

CONFIGURING PSI

FRON~r-END

SOFTWARE

To configure PSI software, answer the 'Node Type:'
prompt with X25.,
You can either use the dialog triggered by the START command 1 ot y~fi(
may enter your own 1 ist of commands.' If you choose
to comb lnath A'
START dialogue and explicit commands, such as DEFINE or INCLUD~,
individual commands only (:tfter you have concluded the START dialog. ·. ':ff
To accurat.ely describe your configuration, you will
need
to enter.;
parameters summar:tzed in the PSI Hardware Worksheet (Figure 1-3). You':'
can obtai.n defaults for some parameters by pressing RETURN.
after yo,,]"
type the command.
The following
example
configuration dialog •

uses

the

START

command

activat~

• RUN NETGEN
TOPS-·10 Network Confi.gurator for DN20 or X25Version 4A(50)
Node type:X25
NETGEN>START
Node name: DNX25
Node address: 120
Transmit Password:
(The text you enter for transmit password IS echoed.)
What DTE port number is used for this node:

The total number of DMC1ls and DMRlls must not exceed 6
How many DMCll lines are on this node:
0
How many DMRl1 lines are on this node:
How many KDPs are on this node:

Number of DUP11 lines on this KDP:
KDP-0-0 Data link protocol type:
KDP-0-0 Maximum Baud Rate: 9600
KDP-0-0 Cost: 10
KDP-0-1
KDP-0-1
KDP-0-l
KDP-0-1

2
DDCMP-DMC

Data link protocol type:
LAPB
Maximum Baud Rate: 9600
DTE address:
311030300171
Channel range for this DTE:
20-1

X.25 Network name: TELENET
X.25 Destination name: X29SRV
Destination node: 6
Destination object: 34
priority: 1
Call Ma s k: F :~'
Call Value: I~l
Subaddresses:

3-4

the

X.2S Destine,tion name: PSITST
,Dest1nation node: 6
D~~tlrii~ion object:' X25TST
Pr iorlty: 0
Call Mask:
Subaddresse$:

.25 Dest inGI t ion name ~
[Configurati.on Saved On:
DSK:DNX25.CNF[100,200]]
teenerat ing DSK: NMLACC. MAC [100 l' 200]] [OK)
[Generat iOg DSK: CETAB. Ml",C (100 ,200]] [OK:I
[Gene rat Ing DSK: NET PAR • MAC[ 100 l' 200 J ) [OK)
[C~nfiquration

complete]

Type ,~AVE and FINISH after any additional changE~s
"Type'EXIT to terminate NETGEN

If you respond that there are KDPs on your DN20, NETGEN immed lately,
Cl$k:sfor infort\1ation regarding the lines on the first KDI?
To inclu,d~
aDECne't..;.101ine J• specify DDCMP-DMC to the 'Data link protocol, type:-"
prompt~
LApS,' used for PSI/X25, is the detault for that promptj

"m:usf'

'1'o>permft,pstTST to run and to allow X.29 terminal
access,
you
DI~STINATION
paramett::!rs, with the exception ' of' ,the"
Des'tin(ltion Node parameter, which rl~quires you to spec ify you'r own ,Kr:.

$;pepify ,the
node num,b.er.,

LeNS 1Logical ChnnnelNurttbers) are used

outgoing

for

calls

<the

order ih wh ieh they are spec.i f i.~d. Most PPSNs ass 19n channels {o~r
incomIng calls starting wi. th the lo1,,;est value assigned to you 'and:
proceeding
to h.igher values.
To rl~duce the chance of an incoming, ahd'
and outgoing cal:L from

simultaneously ,attempting

use

t:he

s'?t'mt=f

channel, you should define your channel'range in descending order~

·:j .•3~1 'J)efining the X25-f)erver Access Password

You can define the access password for the ~.25 server modul~,u,~~rtg"
'the NE'l~G,EN' proqram.
If you have previously created ap~Ig~~~Y{.j¥.
image, lnclueji.ng the aCCE~SS password r then RESTORE the imaget)slng:fihe"
RES'rORE command to NETG EN, the acc·ess password is not included Int;h.e
restored image. Therefore, if you ,are reconfiguringan exlstln9~~,:l
nod~,
you ml4st use the DEFINE MODULE ,X25-SERVER ACCESS P~.~SW'9f\R
command t:o redef i ne the access pass'Word, then use SAVE and FINISHBD,t,Q
retain the changes.
s'
'1',0 define the password that the users will be required
to
supply :'t::o'
',access the X. 215 ga tewl3Y node, type DgFINE MODULE X25;...SERVElr ACCF;~;9
'PASSWORDfollowed by the password itself.

Remember that all parameters, includ ing your password,
must be typed in uppercase letters.

NETGEN)DEFINE
to
info rma tion ..

Remember

use

MODULE

SAVE

X25-SERVER ACCESS
and

FINISHED

3-5

PASSWORD password

save

the

configuration

INSTALLING DN20 NODES

3':~3. 2

Adj Y~,tiJ'lg Hxecutor Parameters

,~'£ your confi9yration contains a DMC/DMRwith
1l1:t.1~t> d ~t:inethe, EXECUTOR
MAXIMUM ADDRESS

EXECUTOR BUFFER SlZE to 290.

'",";

theDN20 processor,
you
to 140 or less, and the
Type the following commands:

NETGEN>DEFlNE: EXECUTOR MAXIMUM }\DDRESS 140
NETGEN>OEFINE: EXECUTOR BUFFER SIZE 290
If you haveanet~7ork with less than 140 nodes, and your
installation
does not,>us~a
DMC/DMH device, fora> "DECnet line,
it is still
recommended" to define the EXECUTOR Ml\XIMUM ADDRESS to 140 and EXECUTOR
'~UFFER~IZE
to 290 to achieve better ~erformance.
These param~ters
m~st'have the same value on every node in the network (see Table A-I).

t~.me~ber

"to

!,r~nformation.

3.4

use

SAVE

and

FINISHED

save

the

cOl)figuration

CHECKING NETGEN PARAMETER VALUES

Before saving the NETGEN parameters, you can check them using the LIST
command.
The
following
example shows the information displayed by
LIST EXECUTOR CHARACTERISTICS for a DN20 node named NEWER (node number
12) ..
NETGEN)LIST EXECUTOR CHARACTERISTICS
Executor Node = 12 (NEWER)
Identification = DECnet-10 V3.0 Release
Management Version = 3.0.0
Loop Coun t = 1
Loop Length = 127
Loop With = Mixed
Incoming Timer = 10
Outgoing Timer = 60
NSP Version = 3.2.0
Maximum Links = 11
Delay Factor = 2
Delay Weight = 3
Inactivity Timer = 30
Retransmit Factor = 5
Routing Version = 1.3.0
Type = Routing
Routing Timer = 60
Maximum Address = 255
Maximum Cost = 100
Maximum Hops = 16
Maximum Visits = 32
Buffer Size = 576
Transmit Password = DECN&T20
NE'l'GEN)
If you find any errors in the configuration described by the
LIST
command,.
you can modify the NETGEN parameters until you are satisfied
that your own configuration has been accurately described.
After
making changes
to
the parameters, be sure to use both the SAVE and
FINISHED commands to preserve the changes before you exit from NETGEN.

3-6

INSTALLING DN20 NODES

3.5

RECONFIGURING SOFTWARE

If the system already has DECnet and/or PSI software, there may be an
existing
configuration
file for the DN20.
The configuration file is
named node-name.CNF, where node-name is the name of the DN20 node.
If
you need to change any parameter values for the DN20, you can restore
the .CNF file with NETGEN to adjust parameter values.
NETGEN provides a RESTORE facility to simplify reconfiguration of an
existing
network node.
The RESTORE command allows you to specify a
.CNF file that you created earlier.
(See Appendix A for
information
about the RESTORE command.)
You modify the configuration
using
INCLUDE,
EXCLUDE,
and
DEFINE
commands.
Use
INCLUDE and EXCLUDE to change hardware parameters and
DEFINE to change software parameters.
Then
type
SAVE
to
save
the
mod i fied
configuration file, and use the FINISHED command to generate
the other NETGEN output files.
If you have set any Management Parameters (User,
Account,
Password),
they are not restored when you use the RESTORE command.
Whenever you
restore a configuration, you must use the DEFINE command
to
set
the
management
parameters,
and
the SAVE and FINISHED commands to retain
them.
;;For PSI nodes, i:: you have set the X25-SERV~H . ACCESS. PASSWORD,
this
f~~arameter
is
09t, restored
with
th~.C~Ffi~~ •. Therefore , if you
rr~?t9rf;<aJ?~I cO.1fl9urati9nfile,you. mustusetl'le DEFINE
command
to
~~eflhe'~the

X2S';"'SER\lER ACCESS PASSWORD, then use the SAVE and FINISHED

~V'<'.<."""''';': ...... :':'. ".':. '.'.....,', .. ,.. '.'.. ,:, ....... , . ..

~~;pml1\~p,Q~ . to ·:·t:.¢t:91n.the<p.~l$$WO rd -:

The
following
sequence adds a
third
DUPl1
to
the
previous
configuration,
defines
the
network management parameters, and saves
all the output files •
• R NETGEN
NETGEN>RESTORE NEWER.CNF
[Configuration Restored From: DSKB:NEWER.CNF[100,200]]
NETGEN>INCLUDE KDP 0
Number of DUPII lines on this KDP: 3
KDP-0-0 Maximum Baud Rate: 19200
KDP-0-0 Cost: 3
KDP-0-1 Maximum Baud Rate: 2400
KDP-0-1 Cost: 4
KDP-0-2 Maximum Baud Rate: 9600
KDP-0-2 Cost: 5
NETGEN>DEFINE EXECUTOR MANAGEMENT USER MAROTTA
NETGEN>DEFINE EXECUTOR MANAGEMENT ACCOUNT INSTALL
NETGEN>DEFINE EXECUTOR MANAGEMENT PASSWORD SECRET
NETGEN>SAVE
[Configuration Saved On:
DSKB:NEWER.CNF[100,200]
NETGEN > F'INISHED
[Generating DSKB:NMLACC.MAC[100,200]
[Generating DSKB:CETAB.MAC[100,200]
(Generating DSKB:NETPAR.MAC[100,200]
NETGEN>EXIT

3-7

INSTALLING DN20 NODES
3.6

CREATING DN20 SOFTWARE

Before you create the front-end
software,
procedures have been accomplished:

make

sure

the

following

Run NETGEN to create the files necessary for completing
procedure.
You must have the following files:
1.

node-name.CNF, where node-name is the name of the DN20

CETAB.MAC

NETPAR.MAC

the

If the files created by NETGEN are stored
in a sub-file
directory
(SFD) ,
you must run the SETSRC program (described
in the TOPS-10 User Utilities Manual).
With SETSRC,
enter
the
SFD followed
by /SCAN,
which allows
the
following
procedures to access files in the SFD.

For PSI installations at Etlropeal1 sites, rename your '" RSXIIS
task '" file."
The. RSXlIS.TSK file supplied on the DECnet-10
dist.ribution tape isfor a 60. HeI"fztilller and
is equivalent
to the RSX60H.TSR file on the'TOPS-l0 PSI distribution tape.
To alJqw the timer in your t)N20 to run at 50 Hertz, type:
.. COPY RSXllS.TSK=RSX50H."TSK

Submit the batch contr01 file that is supplied
on your distribution
tape to the batch system.
For DECnet installations, the batch control
filE? is named MCBSYS.CTL.
Fot PSI installations, the., bat:ch fil~. ;'l."
named MCBX25.CTL.
When you submit the batch job, remember to specify a time limit of at
least 1/2 hour.
The SUBMIT command for a DECnet DN20 is shown below:
.SUBMIT MCBSYS.CTL/TIME:30:00/NOTIFY:YES
For PSI installations, using
~bntrol

th~?

following command to submit the batch

f~le:

.. SUBMIT:.MC13X2 5.CTL/T1:ME: 30: 00/NOT'±Fy';,tES
The system displays a message like the following,
either MCBSYS or MCBX25:

where

job-name

When the job has completed, the system displays the following type
message:

[Batch job job-name queued, request #60, limit 00:30:00]

[From SYSTEM: Job job-name request #60 finished executing at hh:mm:ss]

3-8

INSTALLING DN20 NODES
The batch job does the following:
o

Takes a checksum directory of all required files

Assembles MACRO-II source modules

Creates TSKs and STBs (tasks and symbol tables)

Builds the DN20 system image, nodename.SYS

Deletes OBJ files

The PSI batch job, MCBX25, also deletes t.l1e fl1eNMLACC.MA.C.
Examine
the . log . file produced . by the batch job for errors. You should first
check the' log to see lfthe batch job ended succe'ssfull y.
If there
were errors in the .CTL file, you must go back and correct those
errors.
A successful job produces the DN20 system image; an unsuccessful job
creates no system image. If your log file contains error messages,
assembly errors, or undefined global symbols, determine the cause of
the error, correct it, and resubmit the batch control file.
You must check the batch log file for the size of the generated system
image.
If the system image is greater than 124K words, the
configuration is too large to load into the DN20.
To determine the
size of the system image, find the following lines in the batch log
file:
"The conj ured system image is xxxK words.
Consider ing buffers,
yyyK words of memory will be required during execution."
If the value of yyy is greater than 124,
large.

your

system

image

too

You can adjust the size of the configuration. To change the system
image size, you run NETGEN, restore the .CNF file, and reduce the
complexity of your DN20 configuration. The procedure for restoring a
configuration file is described in Section 3.5. You must change the
parameters to omit a device or adjust the size of the buffers.
(Refer
to Section A.3 for more information on DN20 buffer sizes.)
After changing parameters, you must use the DEFINE command to define
any management access parameters. These parameters are not restored
with the RESTORE command. After you have made all parameter changes
needed,
use
the SAVE and FINISHED commands to save the new
configuration file.

If 'th~,Dif20'isc<)nfJgured for: PSlnletwor~Jng, tt1~ X25-$~RVER A.CCES'S'
f?~SSW().Rt)<i.~,nqtre~tore~d wi th. the. CNgftl~. .•.. ~r~ethe r-1C13' m?nag~ment
a.9~(;l.lntt.>(:lta~et:e:r~,i fyou . restore 1'l'pi:qyqnf 19utation yoU rou~t t)EFINF,;.
t:li~:.X2?+SE:RVER ACCESS PASSWORD and use SAVE 'and F.lNISHED to reta Inth~.:
·a~fin ition.
After adjusting parameters, submit the batch control file once again.
You
must
repeat this procedure until the batch job finishes
successfully and the value of the yyy in the message above is less
than 124K words.

3-9

INSTALLING DN20 NODES
After the control
file
is successfully processed,
your directory
contains a
file named node-name.SYS, where node-name is the name of
the DN20.
Put the node-name.SYS file on SYS:
using the COPY command.
If the DN20 node is named NEWER, the following command is used to copy
the file to SYS: •
• COpy SYS:=NEWER.SYS
You must repeat Sections 3.1
through 3.4
for
each DN20
in your
configuration,
and
you must repeat the procedure whenever you add a
DN20 to the network configuration or change a DN20 configuration.

3-10

CHAPTER 4
CONFIGURING NETWORK NODES

Now you can configure the network for
your host system.
If your
system
includes any DN20 nodes for DECnet or PSI front-ends, you must
configure these nodes according to the procedures in Chapter 3.
Before you can load the nodes and test their connectivity,
you must
create
the command and control files used in the loading and testing
procedures.
The NIPGEN program creates these files.
The NIPGEN program is described in the following sections.
Remember,
the PPN used
in these examples is [100,200], and the node name is
NEWER.
Replace these with your own PPN and node name.

4.1

RUNNING NIPGEN

The NIPGEN program allows you to describe
information for the following types of nodes:
o

Host nodes

Adjacent nodes

Remote nodes

File transfer test nodes

network

configuration

The NIPGEN program provides a
list of the valid answers to each
question
in the dialog when you type "?" in response to the question.
Use
the worksheets
in Chapter 2 to
record
the exact hardware
characteristics of your site before starting the program.
You can exit from NIPGEN by pressing RETURN when NIPGEN asks for
a
node name
to configure.
You can halt NIPGEN without creating output
files by pressing <CTRL/C> at any time during the dialog.
If you encounter any errors in running NIPGEN, refer
for error descriptions and recovery procedures.

4-1

Section

4.3

CONFIGURING NETWORK NODES
4.1.1

Describing the Host Node

When you run NIPGEN, it first asks you to enter information about the
host system.
For example, to specify the KL system NEWER, with node
address 12, use the following commands:
.RUN NIPGEN
NIPGEN for DECNET Version 4.0
Host node definition section.
Host name: NEWER
NEWER's node address: 12
NEWER's CPU type(KL10): KL
The host node name and address must be identical to the node name you
specified
in
the NETGEN portion of the MONGEN dialog.
If you press
RETURN to the request for CPU type, NIPGEN assumes you are configuring
the network for a KL system.
The NIPGEN dialog requires node addresses for
each node.
The node
address you specify must be unique,
and cannot conflict with any
previously assigned node address.

4.1.2

Describing Adjacent Nodes

Next, you must describe the nodes that are adjacent to the host system
in
the network configuration.
This must include any MCBs in the KL
configuration.
The following example describes the adjacent nodes for
NEWER, which are:
o

MCB0, a DN20 running MCB

NEXUS, a KL on the Ethernet

The NIPGEN dialog requires a circuit name for each adjacent node.
You
can choose any of the circuit names listed by"?" that are appropriate
to your hardware configuration.
The following is a list of the valid
circuit types for adjacent nodes:
For KL systems,
o

DTE-n-m for MCB nodes
where n

= the CPU number and m

ETH-0 for Ethernet nodes

For KS systems,
o

KDP-0-0

KDP-0-1

For node NEWER
Adjacent node definition section.
(Type an extra CR when through)
Adjacent node name: MCB0
MCB0's node address: 20
NEWER's circuit to MCB0: DTE-0-1

4-2

the DTE number on the CPU.

CONFIGURING NETWORK NODES
You can specify the network management user-id, account, and
password
for
the DN20.
If you included these parameters in the NETGEN dialog
(described in Chapter 3), you must also include the same parameters in
the NIPGEN dialog.
If you omit the network management parameters, there are no default
settings and any user will be allowed access to the network management
information on that DN20.
It is
recommended
that you specify the
network management
information to prevent unauthorized access to the
DN20 node, for example:
Network management's user-id: MAROTTA
Network management's account: DEC10
Network managementWs password: SECRET
After allowing you to specify network management parameters,
NIPGEN
repeats the "Adjacent node name"
question.
The node NEXUS
is
specified on an Ethernet network connection in the following example:
Adjacent node name: NEXUS
NEXUS's node address: 25
NEWER's circuit to NEXUS: ETH-0
When you have finished listing the nodes adjacent to the host node,
press RETURN to the "Adjacent node name" question.
NIPGEN continues
by asking questions about nodes connected to the DN20 node.

4.1.3

Describing MCB Configurations (KL/DN20 only)

If you have included any MCB node types in the Adjacent Nodes section,
NIPGEN now asks
for
MCB configuration information.
If you did not
include an MCB in the Nodes section, NIPGEN proceeds to
the Remote
Node definition section, described in Section 4.1.4.
You can describe the network environment for
each DN20 that you
included
in
the DN20 Nodes section, as illustrated in the following
example. NIPGEN allows you to describe nodes immediately adjacent to
the DN20.
For each node adjacent to the DN20, you must specify the name
circuit on
the DN20 that is connected to the adjacent node.
see all the possible circuit names by typing
"?"
to
the
question.
The following types of circuit names are allowed:
o

DMC-n (where n is in the range of 0-3)

DMR-n (where n is in the range 0-3)

KDP-n-m (where n is 0 or 1, and m is in the range 0-3)

4-3

of the
You can
circuit

CONFIGURING NETWORK NODES
The following
questions are asked
for
each DN20
that you have
configured.
This example illustrates the procedure for including two
nodes (FLORA and FAUNA) adjacent to the DN20:
For MCB MCB0:
Adjacent node definition section.
(Type an extra CR when through)
Adjacent node name: FLORA
FLORA's node address: 7
MCB0's circuit to FLORA: DMC-0
Adjacent node name: FAUNA
FAUNA's node address: 8
MCB0's circuit to FAUNA: KDP-0-0
Adjacent node name:
To end the list of nodes adjacent to the DN20,
"Adjacent node name" question.

press

RETURN

the

If there are any more DN20/MCBs, NIPGEN repeats
the
Adjacent Nodes
questions for each DN20/MCB.
When there are no more DN20/MCBs, NIPGEN
proceeds to the Remote Node definition section.

4.1.4

Describing Remote Nodes

After you describe adjacent nodes, you must describe the remote
nodes
in
the network configuration.
List each remote node and its unique
address in this section, and press RETURN to
the Remote node name
question when you are finished.
This example describes three remote nodes, LARRY, CURLY, and MOE.
Remote node definition section.
(Type an extra CR when through)
Remote node name: LARRY
LARRY's node address: 30
Remote node name: CURLY
CURLY's node address: 31
Remote node name: MOE
MOE's node address: 32
Remote node name:
When you press RETURN to the node name question,
the File Transfer Test section.

4-4

NIPGEN

proceeds

CONFIGURING NETWORK NODES
4.1.5

Describing Nodes for File Transfer Tests

The installation and verification process may include tests of the
file transfer software.
For these tests, NIPGEN requires the user-id,
account, and password of a valid account on each system.
NIPGEN
repeats
the following question for each adjacent and remote node that
you specified (except MCBs):
File Transfer test section.
Test file transfers to NEXUS? YES
File transfer user-id: MMAROTTA
File transfer account:
File transfer password:
(does not echo)
Test file transfers to FLORA? NO
Test file transfers to FAUNA? NO
Test file transfers to LARRY? YES
File transfer user-id: MMAROTTA
File transfer account:
File transfer password:
(does not echo)
Test file transfers to CURLY? NO
Test file transfers to MOE? NO
[Generating DSKC:NCP.CMD[100,200]]
[Generating DSKC:NIPTST.CTL[100,200]]
[Generating DSKC:NIPNFT.CTL[100,200]]

NIPGEN returns your job to the monitor automatically, and creates the
listed
files
in your directory.
These
files are used
in the
installation and verification procedures that are described in Chapter
6.
If you encounter any errors in the process of using NIPGEN,
refer
to
Section 4.3
for a description of the problem and how to recover from
the error.

4.2

NIPGEN COMMAND AND CONTROL FILES

NIPGEN creates the following command and control files, which are used
to verify and
load the configured nodes and to test connectivity to
specified remote nodes:
NCP.CMD
NIPTST.CTL
NIPNFT.CTL
Each file is described in the following subsections.

4-5

CONFIGURING NETWORK NODES
4.2.1

NCP.CMD

NCP.CMD is a command file that is read by the OPR program to:
o

Define the node names and addresses of all of the nodes.

Define the databases for DN20 nodes.

The NCP.CMD file must be stored
to function properly.

4.2.2

in SYS: for the commands in

the

file

NIPTST.CTL

NIPTST.CTL is a control file created to:

4.2.3

Examine the host node.

Verify the connectivity between the host and adjacent
including MCBs, if applicable.

Verify the connectivity between MCBs and adjacent
any.

nodes,

NIPNFT.CTL

NIPNFT.CTL is a control file that contains commands to NFT to transfer
files between adjacent nodes.

4.3

NIPGEN ERROR MESSAGES

In the process of running NIPGEN, you may receive the error messages
listed below.
The messages
are listed here in alphabetical order,
with suggestions for ways to correct the error.
The
following
are
warning messages
that
indicate a possible error condition and allow
you to correct the error.
? NIPGEN Ambiguous switch or keyword:

"x"

You did not type enough of the command
to distinguish
it
from
other similar commands.
You must type more letters to uniquely
identify the command.
To display a list of valid commands or
arguments, type a question mark (?).

? NIPGEN File "filename" close error - Error description
An error was encountered closing your file.
error is displayed after the error message.

A description of the

? NIPGEN File "filename" open error - Error description
An error was encountered opening your file.
error is displayed after the error message.

A description of the

? NIPGEN File "filename" output error - Error description
An error was encountered while information was being written to a
file.
A description of the specific error is displayed after the
error message.

4-6

CONFIGURING NETWORK NODES

? NIPGEN Invalid character in number:

"c"

You have used special characters that
Node numbers must be 1 to 1023.
? NIPGEN Invalid node address:

NIPGEN

does

not

accept.

"node number"

The node address you have specified is
incorrect.
The address
must be a unique number in the network ranging from 1 to 1023.

? NIPGEN Invalid node area:

"node area"

The node area you have specified is incorrect.
in the range 1 to 63.

? NIPGEN Invalid node name:

The area must

"node name"

A node name can contain 1 to 6 alphabetic and numeric characters
only.
Special characters are not allowed.
The node name must be
a unique name in the network.
? NIPGEN Invalid number of KDPs:

"n"

The number of the KDP controller you have specified
DECSYSTEM-2020 is outside the valid range of 0 to 2.

? NIPGEN Invalid number of MCBs:

"n"

The
number
of
MCBs
you
have
specified
for
your
DECsystem-1090/1091/1095 is outside the valid range of 0 to 9.

? NIPGEN Invalid number of synchronous lines:

"n"

The number of synchronous lines you have specified for
is outside the range of 0 to 16.

? NIPGEN Node name may not exceed 6 characters:

MCB

"x"

The node name you specify must contain 1 to 6
characters.
Special characters are not permitted.

? NIPGEN Not confirmed:

your

alphanumeric

"x"

A carriage return was expected instead of "x".

? NIPGEN unrecognized switch or keyword:

"x"

You have not specified a unique
keyword.
recognition feature
or the question mark (?)
command arguments.

4-7

Use
NIPGEN's
to display valid

CHAPT1E:R 5

GENERATING PSI INITIALIZATION FILES

no instal1in ;J PSI software, skip this chapter
the verificat on procedures described in Chapter 6.

'If'youar~,

and

start

trow~V~,t',f('you,~reinstall ing

PS!(X.2S) network software,
you must
p,]:"ogram to create' the command files required to lO,ad
a'l1(t'st~r~·tle:tw()rksoJtwareand test packages., Procedures for
running
tl1$~"¢OM(fE'Nprog rdm are described in this chapter.

ll~~', th~!,.'CO~GEN
'''. ".:.

.. :.:;

. ::.:. :" :

".'

:: :.":: .. ;: .. ": ~': •••~

,orpSI::i~si:al1ations, theCOMGEN program ,creates command files to
fnltTate 'iie,twork
activity.
"he ' COlVIGEN
program requires the following
' , " , < ',',
'",',
,
,,',
~lles:

}(2?CNF~J:~NF, a templa t.e ,file that yo u
mus t
ed it to
"pa~~JTI~t;:~rs , for "the' specific'
installation.
This

incl ude
f lIe is

:desc'r ibjed' in Section 5.1.

:fp~~$~:""ft~'~:sat~>li$ttfbuted wi ththkpsI·so ftwa re ,ana res ~o red to dis:k
,~,~,)~e'Scr'nje:q', In',,Chapter

:,f~:/~r~~J~',t~~~.'lnl tial! zatiqnf iles ,y()umustfirs~ edit the X2StNF.BNF
fl~.~fo"pqfit:lil'l. infgrmatlon about tbe' PSI,gatew~y,:
::p~'dgr'~pt'~'
,
,

~ ~"";>:'

';:<".;

,'~",

,." , ;~'

>se;'ttlP

PEn upautomatica1ly, you must
Y6\lt. syst:'em'" t6 'bri Tl 9 TOPS-10
pto'lided' on' you,r'TOPS-·10 PSI tape.

B,,::~h~,,"X25'CNF!lB~F

file
'~Nr.~~f'cP n t~.i }'lS' . ' pa r am e te r 8
,tt'oi:J~,:fl'e'$
lrst~q
above..
'
. ,.. <"
.:." ,.. ' .....
'.. . ".. ."
":.
~~i :.~;

/::n,:,
';",'

/.:/
<::-:: ~:.;:~ ,

then run the COMGEN

,':>"~;"

'req~ired

build ,the

command

:~..

':'<bli2:~"N:()t)E "'N~Mt)

: ";::'. DN20 - nod ~Ll)a~"~"" 'I

('O!EhPpRESS>'::= DTt""add ress 'I
'<t{E'TWOR~ NAr>1E) . ' : :=name-()f'-PPSN I

<G~~~W,p.;y P:1\f3S:WORD> , : :::: PPSN-access~,password

"Xk'UJllllS1;:S'tippl}/vallle!? for the items'to the right

0feach 1.1.n.~· is te r:m ina ted byt.he sequence:
'y"
,~

5-1

the

sign

and

~fNERATING

PSI INITIALIZATION FILES

The values to supp:y are described in the following table:
Item

Meaning

DN20-·node-name

DECnet node name of the DN20
X.25; for exampl<~, DNX25.

DTE-atdd ress

X.25 DTE address of the line to
PPSN; for example, 311030300171.

the

name-of-PPSN

Name of PPSN to which you
example, TELENET.

connect;

for

PPSN-access-password

Default password used to access
gateway; for example, SECRET.

the

supporting

Ci\UTION
The PPSN-access-password must be
identical
to the
password you suppl led to the NETGEN program in Chapter
4 (refer to the DEFINE X25-SERVER ACCESS information
in Section A.5).
If the NETGEN and COMGEN programs do
not have the same password,
PSI verification will
fail.
After the software is installed successully,
you may remove references to the access password
in
the X25CNF.BNF file.
Remember that all installation parameters,
including
your password, must be typed in UPPERCASE LETTERS.
When you submit the COMGEN control file, the COMGEN
three times to produce the files listed below.

5.2

program

executes

X25NM.CMD is an OPR command file to set up X.25 network
management.
You can append this file to NCP.CMD to simplify
network startup and file maintenance.

PSITST.INI
func t 10 ns.

command

script

test

X.25

net wor k

is a
X29SRV.INI
i.mpl emen ta t ions.

command

sc r Ipt

test

X.29

network

RUNNING COMGEN

Submit the COMGEN.CTL file using the following command.
The COMGEN
batch job processes the .BNF files to build the necessary files for
testing your X.25 node •
• SUBMIT COMGEN.CTL/TIME:30:00/NOTIFY/OUTPUT:LOG
[Batch job COMGEN queued, request 166, limit 00:30:00]
When the job has completed, the system displays a message in the form:
[From SYS'1'EM: Job COMGEN request
Examine the COMGEN.LOG file
errors.

~66

produced

finished executing at hh :mm :ss]
by

the

batch

job

for

fatal

A successful job produces the necessary PSI files described earlier.
If your log file contains assembly errors, determine the cause of the
error, correct it, and submit the COMGEN.CTL file again.
5-2

CHAPTER 6
STARTING AND VERIFYING NETWORK SOFTWARE

This chapter
describes
the
procedures
for
creating
system
initialization files
to
automatically load
network software.
The
procedure for starting the system and verifying network connections is
followed by instructions for troubleshooting network software.

6.1

PREPARING SYSTEM FILES

To
start
network
software
automatically,
the
new
network
initialization files must be placed in the appropriate system areas
and certain changes must be made
to system startup files.
The
following
procedure assumes
that
the OPR program is used to start
GALAXY and network activity by executing the SYSTEM.CMD file.
Check
the startup procedures on the TOPS-10 system and make the appropriate
changes to the system startup files.
First, copy the NCP.CMD command
file created
by NIPGEN from
your
directory to
SYS:.
If a previous version of NCP.CMD exists in SYS:,
you must append your changes to the previous file.
'~tPSI ',insJa}latioi'ls, you
mayappendt:he ...•file .X25NM .. CMD
N.Cl'~CMP:.fll.~ .>t<) .:>si~pl.lf¥ the ... 1nl'-tiaJ.izi;ltlon . ,procedure.
·fo~lowlpg'·cQmmahdt;.9append X25NM.CMD'to':NCP.CMD:
'
~~'~'.

th~,

Use '6h~f"

;.COl',X.~CP:.¢,MP;;=NCJ? .GMD,.X ~:~NM ~,¢r1Q '
If there is no existing NCP.CMD file
in
command to copy the new NCP.CMD to SYS: •

SYS:,

use

the

following

• COPY SYS:=NCP.CMD
To bring the network up automatically when the system starts
must edit the system files SYSJOB.INI and SYSTEM.CMD.

up,

you

SYSJOB.INI is read by the INITIA program at system startup, so
it
is
often used
to
start detached system processes.
To start DECnet
processes, SYSJOB.INI must include the following commands to start the
DECnet management process:
LOG
NML
To start the FAL program, the OPR.ATO file must include the
commands:
:SLOG
:DEF FAL=
FAL-R FAL

6-1

following

STARTING AND VERIFYING NETWORK SOFTWARE
To start PSI prOCE:sses, the SYS.JOB. INI
following c()~mands:

file

also

contain' the:

LOG
X29SRV

LOG
PSITSB'
The SYSTEM.CMD file is automatically read
and
executed by the
OPR
program at system startup.
The
following commands must be in the
SYSTEM.CMD file to include DECnet:
TAKE SYS:NCP.CMD
SET FAL-STREAM n NETWORK-TYPE DECNET
START FAL-STREAM n
You must include one START command line for each FAL stream that will
run.
The value of n is the number of the FAL stream, where you may
run FAL streams for each File Access Listener to
run on the
system
s im ul taneousl y.
For the PSI initialization procedure, if the file X25NM.CMD was not
appended
to NCP.CMD,
the SY:STEM.CMD file must also
include the
following command line:
TAKE SYS:X25NM.CMD
For. PSI installation, use the PIP utility and the
indirect command
file GENCI?Y. CeL b::- move f j[les c rea ted in previous steps to SYS:.
Type
the following commands to execute GENCPY:
.R PIP
*GENCPY@
*<CTRL/Z>
Verify that the following files have been copied to
DIRECT command:

SYS:

using

the

.DIRECT SYS:
~~ Y S T EM. C MD

NCP.CMD

X29SBV.INI
SYS,JOB. I NI

See the TOPS-~_ DECne! and PSI System Manager's and
Operator's Guide
for
downline-Ioading
procedures and
the commands to place in the
SYSJOB.INI
and
SYSTEM.CMD files
to
accomplish
this
operation
automatically.

6.2

STARTING NETWORK SOFTWARE

To load network software, you must shut down the system and reload
it
with
the latest versions of the monitor, GALAXY, and DECnet software.
See the TOPS-10 Software Installation Guide for
complete
information
about this procedure.---

6-2

STARTING AND VERIFYING NETWORK SOFTWARE
To reboot the system in an orderly fashion, do the following:

6.3

Inform system users that timesharing will end in a
time.

Halt the DN20.

Shut down the system.

Reboot from disk.

Log

specified

in.

VERIFYING NETWORK SOFTWARE

Once the TOPS-10 monitor is up and running, and you have been able
to
log in as usual, verify that the network has been started by using the
NETWORK command.
It may take several minutes to load DN20 nodes and
for
the network to initialize.
If your new monitor does not come up,
you can try to reboot a second time.
If it still fails
to come up,
revert
to the previous monitor, using the procedures described in the
TOPS-10 Software
Installation Guide.
Then check
your
TOPS-10
installation procedure to be sure your new monitor has been installed
correctly.
Check to see if DN20 nodes were downline loaded.
data base using the following NCP command:

You can check a node

NCP)SHOW NODE node-name CHARACTERISTICS
If the NCP command displays
information about
the DN20,
the node
database is set up.
If the node is not running and the node data base
is set up, you can initiate the operation using the following commands
to OPR:
.R OPR
OPR)ENTER NCP
NCP)LOAD NODE nodename
If the SHOW NODE command to NCP fails, then you have to initialize the
network database.
To set up the database, type the following NCP
command:
OPR)TAKE SYS:NCP.CMD
If no errors occurred and the loading process is successful,
begin the verification procedures.

6.4

you

can

TROUBLESHOOTING NETWORK SOFTWARE

If the TOPS-10 7.03 monitor is up and running, but your network has
failed
to come up, you can try to start the network manually.
To do
this, use OPR to define your network nodes and load the DN20 nodes.
Run the OPR program and then issue the TAKE SYS:NCP command.
This
causes the commands
in
the NCP.CMD command
file to be executed,
defining the network topology and describing all information required
to load DN20 nodes.

6-3

STARTING AND VERIFYING NETWORK SOFTWARE
After you
issue
this command
to NCP,
ensure
that the
load
is
successful.
Use
the NCP SHOW command to display information for the
node you just loaded.
If the load is not successful, determine
the
cause of the failure, correct it, and perform this procedure again.
CHKll is a module that resides in the DN20.
It starts when the DN20
is loaded
and displays messages concerning
available memory, the
number and status of devices, and any detected errors.
If
you have
difficulty bringing
up the front end, use CHKll output to determine
your errors.
Immediately before typing the NCP LOAD NODE command,
type the following at another terminal:
.R DTELDR
*/TALK:nn
where nn are the two digits used to
identify the
example, for DTE-0-l, you would use "01" for "nn".

DTE

You can also use SPEAR to look at CHKll output from a
NML logs the CHKll output to SYS:ERROR.SYS.

number.

For

load.

If the DN20 fails to come up, you must revert to the previous versions
of the monitor
and
network software.
Refer to Chapter 2 to review
your installation procedure for an error.
Check the log file from the
generation procedure
in Section 3.4 for possible errors, and to make
sure the system-image size
is less than 124K words.
For DECnet
installation,
this
batch
log
file
is MCBSYS.LOG.
For PSI
installation, the batch log file is called MCBX25.LOG.

6.5

VERIFYING THE NETWORK

Log into your account and set your path to the build directory.
Type
the NETWORK command to see if the new DN20 nodes are reported in the
display.
For example:
• NETWORK
[ANF10 network: connected to KL1026(26), located at NOVA(31), 10 nodes]
Node
CHERRY
(1)
TAPE12 Load/Sirus System
09-12-85
Node
JUBLEE
(2)
DN87S V23(210)
9-JAN-84
KL1026
(26)
RL240A DEC10 Development
10-22-85
Node
NOVA
(31)
DN87S V24(226)
l2-Mar-85
Node
OW ARF
( 33 )
ON 2 0 V24 ( 227 )
3 - S EP -, 8 5
Node
Node
JINX
(34)
DN20 V24(225)
l2-FEB-85
COMET
(70)
DN200 V24(226)
12-Mar-85
Node
MREAST
(71)
Mister East KS702/46F
07-31-85
Node
TWINKY
(77)
Hostess Twinky KL703/54A
10-02-85
Node
BACALL
(121)
DN20 V22E/70B
Node
[DECnet network: local node KL1026, 48 reachable nodes in area 7]
BRUNO
CAEWK2 CAEWK3 CAEWK4 CAEWK5 CAEWK6 CAEWK7
BRONCO
CURIUM
DAR
DARTS
DCHPS
DCSVAX DEMILO DESADE
CURIE
ELI
ELIGUS
EMILY
EPOCH
ESGPRT FASTER FERMI
EINSTN
JBOAT
IONIAN
IRAO
IROBOT ISAVAX ISHTAR JACKSO JAWS
MATE
MATISE MAX
MCAD
MDR228 MDR268 MDR292
MASTER
MRTEIS
MURRAY MUSEUM NIMBUS NOBEL
NU
NYHPS
MRSVAX
Note that you can use the /DECNET switch wfth the NETWORK
display only DECnet nodes.

6-4

command

STARTING AND VERIFYING NETWORK SOFTWARE
Verify the success of the loading procedures by running OPR and
issuing
the NCP command SHOW NODE.
For example, display the network
information for the node named DEMILO:
.R OPR
OPR>ENTER NCP
NCP>SHOW NODE DEMILO CHARACTERISTICS
12:30:29 NCP
Request
45; Show Node Summary Completed
Remote Node = 6.131 (DEMILO)
Circuit = ETH-0
Next Node = 7.93 (MONTY)
NCP>
If the DN20 nodes are listed by NETWORK and in the SHOW NODE output,
the automatic system startup procedures are correct.
If the DN20 is
not listed in these displays, review the system files described
in
Section 6.1 and correct the errors.

6.6

TESTING NETWORK CONNECTIONS

The batch job NIPTST is supplied to display network characteristics
and
to
test network connections through the DN20.
This batch job is
useful for both DECnet and PSI installations.
Use the NIPTST.CTL batch control file created by NIPGEN to perform the
following operations:
o

Display the node characteristics of the host system.

Display the node characteristics of adjacent nodes.

Perform LOOP tests to adjacent nodes.

To submit the NIPTST.CTL file to the batch system, type the
command:

following

.SUBMIT NIPTST.CTL/NOTIFY:YES/OUTPUT:LOG/TIME:30:00
[Batch job NIPTST queued, request #98, limit 00:30:00]
You will receive notification when the job is done. When the job is
finished,
the log file is printed automatically.
Check the log file
for fatal errors and correct the cause of any errors.
If an error indicates a timeout condition, you can adjust
interval allowed for testing each circuit. The normal time
this job is 10 minutes per circuit tested.
You can adjust
interval
for
the WAIT command in the batch control file,
installation test timing.

the
time
limit for
the time
to modify

Carefully check the batch job log file for errors.
If you find
no
errors, continue with your installation; otherwise, find the cause of
the errors, correct them, and resubmit the batch job.

6-5

STARTING AND VERIFYING NETWORK SOFTWARE
6.7

TESTING FILE TRANSFER

If you included file transfer testing in the NIPGEN program (described
in Chapter 4), use the NIPNFT.CTL batch control file created by NIPGEN
to test file transfer between the host processor and nodes
in
the
network
that support NFT (Network File Transfer).
NIPNFT.CTL copies
an ASCII file from one DECnet host node to another and back again, and
compares the output file with the input file.
Submit the NIPNFT.CTL file to the batch system by typing the following
command:
.SUBMIT NIPNFT.CTL/NOTIFY:YES/OUTPUT:LOG/TIME:20:00
[Batch job NIPNFT queued, request #99, limit 0:20:00]
You will be notified when the batch job has completed.
Check the log
file generated by the batch job, examine the file for errors, and
verify that file transfers have completed successfully. The output of
the batch job will be in NIPNFT.LOG.

6.8

VERIFYING PSI CONNECTIONS

If you are instal I lng PS I, ver i fy the PSI connec t ions af ter
you make
sure the DECnet part of. your installation is working_
If you are not
installing PSI, you can skip this section and proceed to Section 6.10
to complete the installation procedures.

To test and ver i fy PS I connec t ions, you can:

6.8.1

Perform a hardware loop test.

Test X.. 2S capabllities.

Call up your local PAD.

Connect to the (X.2S) gateway.

Performing the X.25 Loop Test:

To perform a loop test, use theNCP commands SET LINE and LOOP LINE.
Use the following commands to start the LOOP test.
This example tests
KDP-0-0 •
• R OPR
OPR)ENT NCP
NCP>SET EXECUTOR NODE nodename
NCP)SET LINE KDP-0-0 STATE OFF
After you type these co~mands, disconnect the modem and attach a
loopback connector to the KDP line.
Then type the following commands:
NCP>SET LINE KDP-0-0 CLOCK INTERNAL
NCP)SET LINE KDP-0-0 SERVICE ENABLED
NCP)SET LINE KDP-0-0 STATE ON
NCP>LOOP LINE KDP-0-0 COUNT m WITH MIXED LENGTH n
NCP)SET LINE KDP-0-0 STATE OFF

6-6

.-;TAI1:TINC }\ND VEHTFYING NETWORK SOFTWARE
The LOOP LINE command contains t.hre4= variables: the line-id (KDP-0-0)
is the same line-id used in previous commands. The COUNT value (m)
specifies the number of times the test data is to be returned; the
value of LENGTH [n) specifies the length of the test data, in bytes.
When per-forminq the LOOP LINE command, do not use a COUNT greater than
1000
or a LENGTH greater than 127.
Failure to observe this
restriction can cause the loop test to t~ke longer than the 3 minute
timeout period.
If in response to the LOOP command you receive one of the following
messages, you must reload the DN20 before the DN20 will respond to
network management commands:
Loop Line Failed, Operation failure
Timed out wet it inq for response

You will receive these messages if the loop line test takes
than 3 minutes, or if the line is not functioning properly.

longer

When the test is successfu:ly completed, remove the loopback connector
and reconnect the line to the modem. Type the following commands to
turn the line en:
NCP)SET LINE KDP-0-0 CLOCK EXTERNAL
NCP)SET LINE KDP-0-0 SERVICE DISABLED
NCP)SET LINE KDP-0-0 STATE ON
The KDP line will not start if the modem has not been connected to the
line.
If the KDP line does not start, connect the modem, turn the
line off, then turn it back on, using the following commands to NCP:
NCP)SET LINE
NCP>SE:T LINE

6.8.2

KDP~0-0

STATE OFF

KDf'~0-Qf

STATE ON

Testing X.25 Connectivity

Run the PSITST program tc. test the connection from your host to the
PPSN you have chosen.
For a complete description of the PSITST
program, see AppendixB. PSITST tes:tsthe commands in PSI'l"'ST.INI, and
exits automatical~y ~hen the test is cdmpleted.

X~25

To '~ctivate PSITST,type:
.R PSITST

After
The following is ·an example of a succ:E!ssful PSITST eXE'c'ltion.
you run PSrrST, it is importantto'c:heck the log file for errors.
The
log fIle entries are described in Appendix B.

6-7

STARTING

}~,ND

VERIFYING NETWORK SOFTWARE

Example:
.R PSITST
KL1010, RC703 7.03 System, TOPS-10 Monitor 7.03(00)
TOPS-10 PSI PSITST Version 1.0(7)
(Normal Environment)
Monday, October 15, 1985 09:21:09AM
Port 1/: 0;

Status

Network = TELENET
Object Identification = X25TST
Port State = Running
Error State Detail = None
Last Port Request = Accept Incoming Call
Last Request Error = None
Network Data = None
Network Interrupt = None
Port it 1;

Status

Network = TELENET
Port State = Running
Error State Cetall = None
Last Port Request = Read Accept Data
Last Request Error = No Data To Read
Network Data = None
Network Interrupt = None
Port it 0;

Data

More Bit Setting = Enabled
Transmitted Interrupt = None Outstanding
Received Interrupt = None ~ltstanding
Data Transmission = Normal
Received Normal Data Packet = 38 bytes
101 102 103 104 105 106 107 110 111 112
113 114 115 116 117 120 121 122 123 124
125 126 127 130 131 132 060 061 062 063
064 065 066 067 070 071 015 012
Last Data Reception Error = No Data To Read
port 1/: 1;

Data

More Bit Setting = Enabled
Transmitted Interrupt = None Outstanding
Received Interrupt = None Outstanding
Data Transmission = Normal
Transmitted Normal Data = 38 bytes
101 102 103 104 105 106 107 110 111 112
113 114 115 116 117 120 121 122 123 124
125 126 127 130 131 132 060 061 062 063
064 065 066 067 070 071 015 012
Port I

Wait For
Incoming
Received
Received

IABCDEFGHIJI
IKLMNOPQRSTI
I UVWXYZ0123 I
1456789..
I

Counters
Incoming Calls = 1
Calls Accepted = 1
Normal Data Packets = 25
Normal Data Bytes = 950

6-8

IABCDEFGHIJI
IKLMNOPQRSTI
I UVWXYZ0123 I
1456789..
I

~JTARTING

Port # 1;

AND VER I FYING NETWORK SOFTWARE

Counters

Call Requests = 1
Transmitted Normal Data Packets = 25
Transmitted Normal Data Bytes = 950
Port # Ii

Status

Network = TELENET
Port State = Running
Error State Detail = None
Last Port Request = Read Port Status
Last Request Error = None
Network Data = None
Network Interrupt = None
Po r t # 1;

Da ta

More Bit Setting = Enabled
Transmitted Interrupt = None Outstanding
Received Interrupt = None Outstanding
Transmitted Reset Diagnostic = 377 (255)
Data Transmission = Normal
Transmitted Interrupt Byte = 377 (255)
Transmitted Normal Data = 38 bytes
101 102 103 104 105 106 107 110 III 112
113 114 115 116 117 120 121 122 121 124

I ABCDr;FGHIJ I
IKLMNOPQRSTI

125 126 127 130 131 132 060 061 062 063
064 065 066 067 070 071 015 012

IUVWXYZ0123!
1456789. •
I

Initialization Completed
EXIT

PSITST collects status information in the log file PSITST.LOG(I,2] for
your inspection. Use the TYPE command to display the contents of this
file •
• TYPE PSITSTuLOG(1,2]
If no errors occurred as you ~an the I09P~ack t~st
node is connected to the PPSN.
.

and

~SITSi,

your

If YO,u encounter E~rrors connecting to.· the PPSN, check the sta,tus of
the X.25 line by running OPR and typing the following commands.
(See

the ~lJ! DEenet:. ano PS:r~ System Manai;ler'sand
informati90.)

operatorl~~

Guide

for

addition~l

OPR)ENTER Nep

NCP)TEL~ nOdE!name SHOW KNOWN I"I1Hf'STA'tliS

X.2S· lJ,net~ ,'90" l?:utthe substate
is
tl1e l:ine.tothe PPSN is notfunc'tion~ng
prcfp~rly •.. Return to'Sectlon 6.8.1 ang perJonn the, Io(,ptest . aga1n.
;If the
loop test: 'completes successful1y~,tht~re,maybe a problem wi th
the lease·d 1 tne to your PI?SN. Consultyptir PP$'N., representative for
further'assi~tan(:e. " I f
tbe lpoptes;i;fails(,youmcIY have a. faulty
l<DPitheref.ot;e, ybu'should consult yq\lr~f1~1(1,s~XyJc,E:1, ["e,presentative.
If

the

state

y,our

synchton'izingors~~r:tir'9,

:',\",

<..

Xf the X~25 l.ine:ls6)1 t but no SUb$t<ite~j,$·di:spl~f~d,' check the vat ues

for DTE. address l' defaultdata.$ize,~;'d~£a~lt: \iJndqw s~ ze , and channel
range.
If you arE! unsureoft::he oO'rl~,~ct'~va·llJeS,90nsult . your PPSN
representative to determine the corr'dct'Valu'e:;:.
6-9

ST.A.RTING P.ND VER I FYING NETWORK SOFTWARE
6.9

VERI:FYING X.29 CONNECTIONS

The TOPS-10 X.29 software, X29SRV, enables you to connect your
terminal, through a PPSN, to a TOPS-IS host. To make this connection,
you must:
o

Make a physical connection between your facility and the PPSN
PAD.

Create a virtual circuit that connects
X29SRV through the X.25 gateway node.

Connect your terminal to the TOPS .... 10 host.

your

terminal

Calling the Local Pad (TELENET)

6.9.1

You
need
telephone
access
to
a
local
PAD
(Packet
Assembler/Disassembler) •
Go to a dial-in terminal and call the PAD
(get the number from your System or Network Manager).
If you ~re using an acoustic coupler ,when you hear a high-pitched
tone, place the telephone handset in the acoustic coupler. If you are
using a dataset, change the DATA/TALK switch to DATA and place the
handset in the telephone cradle.
Examples in the following steps use TELENET as the local pad.
Press the RETURN key twice to
with a message, such as:

se~~

the PPSN herald.

TELENET

responds

TEtENET'
800 l8C

TELENETthen pr.ompts you to

~dentify

your terminal model:

TERMINAL=
If your terminal is type VTxxx J' enter:
Dl
Otherwi$e, enter:
A8

Or, press

6.9.2

th~

RETURN key.

SIgning on to the Network Gateway

Enter the appropriate information to sign on to your gateway (see your
System or Network Manager for specifics):
.C 311l71!)
311 171D CONNECTED

Digital Equipment Corporation, TOPS-10 PSI Gateway X.29 Server
Friday, July 15, 198!) 03:39:03 Vl.0(0) #110 (00)
X29SRV>
6-10

:3'TARTING A.ND VEHIFYING NETWORK SOFTWARE
If you do not receive
connection has
failed.
following reasons:
o

the connect message from
the PPSN,
the
The connection could
fail for one of the

The X.25 module database is
incorrect.
Use
the
following
commands
to verify that the destination node is specified
(:0 rree tl y:
NCP)SET EXEC NODE node-name
NCP>SHOW MODULE X25-SgRVER CHARACTERISTIC KNOWN DESTINATION
If necessary, run NETGEN again, as described in Chapter 3, to
adjust the faulty parameters.

6.9.3

X29SRV is not running properly.
Check your CTY listing
for
errors.
(See the TOP8-10 DECnet and PSI Syst~ Manager's and
.operator_~~
Gui~_~ -ror---a -complete
description of
X29SRV
configuration commands,
and
for
a
list of X29SRV error
messages) •

Connecting to the TOPS-10 Host System

In response to the X29SRV prompt, type the CONNECT

command,

followed

by
the node name of the TOPS-I0 system.
(See the TOPS-10 PSI User's
Gu~S!.~. for a complete description of X29SRV user
command'~;:) When
you

see
the TOPS-10
log in as usual.

monitor prompt, type the command TTY NO ECHO.

Then

X29SRV>CONN KL1010
RL222B
DEC10 System
15:40:34 TTY 66 System 1010/1020
Connected to Node KL1010 Line 166
Please LOGIN or ATTACH
.TTY NO ECHO
.LOGIN
After you type the node name, the system banner appears.
If you do
not see the banner, verify that the requested node is in operation and
DECnet-10 is installed properly.
If the node and DECnet are running,
the node may have depleted
DECnet or system resources.
Try again
later.

6.9.4

Disconnecting from the TOPS-10 System

To disconnect from the TOPS-10 system, type the following command:
.. KJOB
Job 36 User MRT [100,200]
Logged-off TTY44 at 15:17:18 pm IS-Jul-8S
Runtime: 0:00:01. KCS:23, connect time:0:03:24
Press the BREAK key to return
to
the gateway.
The TOPS-10
software responds with BREAK and returns the X29SRV prompt.
<BREAK>
BREAK
;.(29SRV>

6-11

X.29

STARTING AND VERIFYING NETWORK SOFTWARE
Type the CLEAR command to disconnect from X29SRV.
X29SRV>CLE:AR
DISCONNECTING •••••••••
B17 12 DISCONNECTED
00 0e 00:m0:01:l7 30 25
After you receive the disconnect message, hang up your telephone.,

6.10

COMPLETING THE INSTALLATION PROCEDURE

For both DECnet and PSI installations, there are a few steps that must
be accomplished to conclude the network installation procedure.
In NCP.CMD, you must
include SET NODE commands to
establish
the
correspondence between the node name and node address for all nodes in
your network.
In the NIPGEN procedure described
in Chapter 4,
the
node associations were
provided
for
nodes included in the testing
procedures.
If there are any other nodes in
the network,
edit the
NCP.CMD file
and add a line for each node in the network that is not
already in NCP.CMD.
For each node,
add
a command similar
to
the
following,
where node-address is the node number and node-name is the
name of the node:
SET NODE node-address NAME node-name
For example, to add node JAKE (node number 25),
line in NCP.CMD:

place

the

following

SET NODE 25 NAME JAKE
After you edit NCP.CMD, copy the file to SYS:.
To activate
the node
database while
your system
is
running
under timesharing, use the
following command:
.R aPR
OPR>TAKE SYS:NCP.CMD
This activates the node database immediately.
As long as NCP.CMD is in SYS:, and the SYSTEM.CMD file contains the
line
TAKE
NCP.CMD,
the
network
database will be activated
automatically whenever aPR is started on the system console terminal.
When you are satisfied with the functioning of the monitor and network
software,
copy the new monitor,
DECnet,
and GALAXY files to the
appropriate system areas.
This completes the DECnet instal~ation and
verification procedures.
For PSI installations, if you want to aCcess the PSI gateway node from
other TOPS-10 host systems, you must install the PSI access software
on those systems.
The procedure to accomplish this is documented
in
the next section.

STARTING P.ND VERI FYING NETlyOHK SOFTWARE

6.11

INSTALLING PSI ACCESS SOFTWARE ON OTHER NODES

To allow users of other 'I'OPS-10 systems in your network to access the
PSI gateway node that you have installed, you must also install the
files listed in Section 6.11.1 on those TOPS-10 nodes. If you are not
installing the gateway access software on any other TOPS-10 system,
the installation procedure is complete.
You can use

installation
software.

NFT to copy files to other nodes, or
procedures described below to manually

Repeat the following steps for each
access to the PSI gateway node.

6.11.1

TOPS-10

node

perform
install

the
the

will

allow

TOPS-10

node,

that

Installing Access Software

To install the gateway access
perform the following steps:

software

another

Install DECnet-10 on that node.

Install the TCPS-10 PSI files that were restored from tape,
or generated during the installation procedures, on the
system areas. 'J'he files you must copy to the TOPS-10 systems
are:
SYS:OPR.EXE

SYS:X25NM.CMD
SYS:B361LB.REL
REL:X25GAM.P.EL

REL:X25GAF.REL
UNV:X25SYM.UNV
HLP:NCP .. HLP

6.11.2

Restarting NML

Start NML by restarting the system Qr by following the NML startup
procedures described in the .!OPS-l.~ DECnet: and PSI .§>"y~~~em. Manager's
and operator's Guid_~.

6.11.3

Activating Network Management

Use OPR to take the X25NM.CMD command file to activate network
management capabilities.
(If you merged X25NM .. CMD with NCP.CMD, you
only have to execute the NCP.CMD file.)
.ROPR
OPR>TAKE SYS:X25NM.CMD
If your connection to the· PPSN and your system startup files work
correctly, and YOLlr log files contain no errCl[s; you a.re finished.
If
some parts of your network are still not opet'ational, you must resolve
the errors and repeat the apprc-priate lnstallation procedures to
correct the software.

6-13

APPENDIX A
NETGEN

This appendix describes the NETGEN program in detail.
It lists
the
software and hardware parameters that you use to configure DECnet and
PSI
front-end
software.
The
NETGEN
commands
are
listed
in
alphabetical
order,
then
the error messages that NETGEN can display
are described, also in alphabetical order.

A.I

NETGEN INPUT FEATURES

NETGEN provides several features that
commands and arguments.
You can:

A.2

help

you

the

enter

Type a question mark in response
to
display a list of NETGEN commands.

Type a question mark after the
a rg umen ts.

Press the ESCape key after the command to display guidewords
for
the argument.
Or press ESCape while typing a command or
argument, to complete the command or argument name.

Abbreviate commands, keywords, and arguments.

command

NETGEN

necessary

list

prompt
the

valid

NETGEN PARAMETERS

This section describes the parameters you need for
the operation of
network software in your DN20.
These parameters apply to both DECnet
and PSI installations.
Parameter

Meaning

Node type

The first parameter you must specify is
the
type
of
front-end node you want to configure.
You can
specify DN20 for a DECnet front end or X25
for
a
PS I f ron tend.
Default:

Node name

None

The name for the node you are generating.
The
name must begin with an alphabetic character and
cannot exceed six characters.
Default:

None

A-l

NETGEN
Paramet.er

!'lean in..9.

Node address

A number that identifies the address of the node
being generated.
This address must be unique
within the network. Any decimal number in the
range 1 through 255 can be specified, provided it
does not duplicate an address assigned to another
node in the network. Generally, you should use
low numbers for addresses of nodes in a small
network.
You cannot use a node address larger
than the Maximum Address you specify.
If you
enter an address incompatible with your Maximum
l\ddress or Buffer Size, NETGEN warns you.
Default:

Identification

A string you can use to identify the software you
are generating.
The string can be seen with the
NCP SHOW EXECUTOR CHARACTERISTICS command.
You
can specify any text string of 1 to 32 characters.

Default:
Outgoing Timer

DECNET V3.0 Release

The number of seconds to wait for acknowledgement
from a remote node to a connect request issued
locally. The range is 1 to 65535 seconds.
Defaul t:

Max imum Links

None

The maximum number of supported logical links to
the DN20/MCB.
Each virtual circuit requires a
logical link.
This parameter applies to the
number of links to tasks residing in the MCB (such
as NML).
It does not affect links to nodes other
than the MCB.
This parameter does affect the
number of PSI links, which resides in the MCB.
The maximum number of links should be at least
equal to the maximum number of virtual circuits
you want to support, plus 3.
(A logical link is a
software connection allowing programs on different
nodes to transmit data to each other.)
The range
is 3 to 16.
Defa ul t:

Inactivity Timer

Number of seconds to wait before exercIsIng a
logical link when there is no received traffic on
the link.
A condition of No Receive Traffic can occur, for
example, because the network is disconnected, or
because the physical line went down.
When the
number of seconds specified have elapsed, NSP
sends a data request message over the logical
link.
If, after a certain amount of time (see
Retransmit
Factor) ,
there
has
been
no
acknowledgement of the message, NSP decides that
the physical network supporting the logical link
has failed. The range for the inactivity t.imer is
1 to 65535 seconds.
Default:

A-2

NETGEN
Parameter

Meaning

Retransmit Factor

The number of times the node retransmits a message
without
receiving
acknowledgement before the
DN20/MCB software supporting a logical link has
failed. The range is 1 to 15.
Defaul t:

Routing Timer

Maximum amount time to wait before transmitting a
routing message. The range is 1 to 65535 seconds.
Defaul t:

Max imum Add ress:

The highest node number in the same network as the
node you are configuring, plus 2, to allow for
future expansion. The specified value must be at
least equal to the node address of the node you
are configuring. This parameter determines the
highest node address in the network.
For example,
a network with node numbers 1, 2, and 5 must have
a maximum address of at least 5. Nodes numbered
greater than the maximum address are not visible
to the MCB, and thus cannot be accessed. The
range is 1 to 255.
The Maximum Address, Buffer Size, and Node Address
you use must be compatible.
NETGEN computes
Buffer Size depending on the Maximum Address you
enter, and warns you if they are incompatible.
See Section A.2 for more information about the
Buffer Size parameter.
Defaul t:

Max imum Cost

Highest
allowable
cost
associated
with
a
particular logical path. This parameter depends
on the individual line cost
(the
cost
of
transferring a message over a line), and path
costs. This value is calculated as the sum of the
line costs of all lines over which the data is
routed. The range is 1 to 1022.
Default:

Max imum Hops

100

The maximum number of hops allowed between any
pair of nodes in the network. The range is 1 to
30.
Default:

Max imum Vi sits

255

The maximum number of visits to network nodes that
any individual message can make in the attempt to
find the correct destination node.
When a node
receives a message with a visit count greater than
the value of the Maximum Visits, the node discards
the message.
The Maximum Visit value must be
greater than or equal to Maximum Hops. The range
is 16 to 255.
Defaul t:

A-3

NETGEN
Parameter
Buffer Size

The size of buffers the system uses
to
transmit
and
receive data over
any physical link in the
network.
The size you specify must be the same on
every node
in
the network because a DECnet node
cannot communicate with any node whose buffer size
differs
from
its own.
The range is 515 to 576.
NETGEN computes the minimum buffer size depending
on
the Maximum Address you enter.
If you enter a
buffer
size
that
is less
than
the
computed
minimum,
NETGEN warns
you.
See Section A.2 for
more information about the buffer size parameter.
Default:

Transmit Password
Receive Password

576

Optional parameters identifying the password
sent
to a
remote node
during
an
initialization
sequence.
The
password must be an alphanumeric
string from 1-8 characters long.
In a
DECnet
network,
passwords are required to initialize MCB
nodes.
In a Phase IV network, passwords are only
used
in initializing nodes with dialup lines used
by the network.
Passwords are not checked
on
incoming
requests
to
DECnet,
but a
Transmit
Password may be required by other nodes
in the
network.
Default:

DECNET20

Management Parameters
You can set these
three parameters to
restrict
users at remote terminals from giving NCP commands
that affect your local node.
The parameters are:
Account
User I.D.
Password

Up to 16 characters
Up to 16 characters
Up to 8 characters

No default is set for these parameters.
If you do
not
include
these access control parameters, any
user
at any remote
terminal
has unrestricted
access to local network management commands.
If you set these parameters, a
user must supply
this
information before performing NCP commands
that affect your
node.
Any remote
users can
display local
network
information using the NCP
SHOW and
LIST commands,
but
the
management
parameters are not displayed.
The network management parameters must also be
supplied
in
the
NIPGEN program, as described in
Chapter 4.

A-4

NETGEN
Parameter

Meaning

Logging File Event Classes
DECnet provides a facility for logging information
that has potential significance in the operation
or maintenance of the network.
Logged information
includes
the location of
information about the
event as well
as
number
of
events
lost,
initialization
failures,
and circuit losses.
Significant events are recorded by SPEAR
in
ERROR.SYS.
See the TOPS-10 DECnet and PSI System
Manager's
and
QEerator's
Guide
for
more
information about
the event classes and event
types.
Hardware
DMCll

Number of DMClls on your DN20.
You may have no
DMClls,
or
from 1
to 6 DMClls on a DN20.
The
DMCll
is
a
single-line
microprocessor-based
interface
to
the network.
The DMCl1
is a
synchronous DMA device.
Default:

DMRll

Number of DMRl1s on your DN20.
You may have no
DMRlls,
or
from 1 to 6 DMRl1s on a single DN20.
The DMRll is a
single-line, microprocessor-based
interface
to
the network.
The DMRll
is a
synchronous DMA device.
Default:

DUPll

2 (0 if no KDP)

Number of the DTE with which the DN20
interfaces
to
the processors
(not
the number of DTEs).
Normally, the DN20 used for DECnet uses DTE number
1,
2,
or 3.
You cannot use DTE number 0 because
DTE-0-0 is always dedicated to the console front
end.
Note
that DECnet
identifies the DTE as
DTE-CPU-n,
as opposed
to DN20s, which always
interpret the DTE as DTE-0-n.
Default:

KDP

Number of DUPll devices on the KDP (0-3).
Default:

DTE20

DTE-0-1

Number of KDPs on your DN20 (0 to 2).
A KDP is a
combination of a KMCll controller and one to four
DUP 11 s (t h e de fa u 1 t i s
two DUP 11 s) •
Wit h the
KMCll,
the DUPl1
functions
as a direct memory
access
device
(DMA) •
The
interface
is
synchronous.
Default:

A-5

NETGEN

,A.3' PSI PARAMRTERS
This section describes the parameters that must be defined for the
>Qperation' 'o~ ',', ,P~;iI' in your DN20. You can display the values for these
pa~ameters u~ing the LIST command.

A.3.1

Known Circuits Character.istics

The par,metet§ in this section apply
(PVCs) •
Parameter

Permanent

Virtual

Circuits

Meanin9
is the name that the system manager assigns to the
(Permanent Virtual Circuit). The circuit-id
is an ASCI! string of up to 16 characters.

PVC

Default:
DTE

address

is an ASCII string that represents the
to which your PVC is defined~
Defa ul t:

Node

tYPE~

None
DTE

address

None

is the type of front-end software, either DN20

X2S.

Default:
Channel

is the logical channel number associated with
PVC, as defined by your PPSN.
Default:

Maximum data

the

None

is the packet size for the PVC, as defined by your
PPSN. The range is from 1 to 65535.
Default:

Maximum wfnc]c;>w

X25

128

is the window size for the PVC, as defined by your
PPSN. The range is 1 to '255.
Default:

A-6

NETGEN

Known Lines Characteristics

A .. 3.2

PSI line parameters define the hardware and data link protocol
(frame
level
protocol)
parameters necessary to communicate with the PPSN.
For proper operation of your PPSN link, it is important to
set
these
parameters with the values recommended by your PPSNe

Line

j s
'"' h ,.)

Pro tncol

the 1 irll? t.ha t connec ts yo ur DN 20
1 5n e can 0 n 1 y be a KDP 11 •

the

PPSN.

the data link orotocol type used on
the
line.
t :3 t J-' f~ f) r 0 t~ 0 <:: 0 1 for a n X. 2 5 con nee t ion ..

1\ {) B

j,hPB

Retransmit

rr il1C;:'

tlle
(~:

;

link

dcltZ:}

interval

([[IS)

timer used

t.()

~JeterJnine

which an unacknowledqed

a~ter

rd:;-;r·litt~t;:~(l.4'

The

t~imer

inter'\lal

th~~

data frame
is given .irt

{ms).
You must supply the val ue
c:H<l
f)'.]
'Your
PPSN.
(The
CClT,]" frame level
·p'te: ',:. e I
I S " 1':) .: .. )
'l'h era na e is 1 to 65535 ..

: ~.'- i..:::';':JCCII'U;

IS the maXImum frame level
: :;1"1"

i".'h

\011

rn.ust

l':J;::N.
('The CC!'1"I' frame
-,:'[:('! ;::>1/qe :; ''; 1 to /. 55 ..

window size for the
the value defined by

S;IPP] y

level

parameter

-, I ,:" i ' i ~

r"\,::l x in UIII

JS ine

:;1. (; t: r {i il S mIt s

i,:':: .. ransmlttf:d

m2~imum

Imf:T.

number of times a data
frCime
is
at the expirat:ion t)f the
Retransmit

must supply thE: value defIned hy your
1 e v (~ 1 p a [ am E' t e r i s " N 2" .. )

YUH

pi rJ <
( T h c·
C '-. I TT f :r am e
1H, J::' .:1 rl Q f~ '!O, 0 to:.? 5 5 ..

of the
LAPS lines, which
The baud rate can be one of
:J ::r.) 11(1\>'1 nq val ues, 1200, 1800, 2400,
~600i
;:'~~li/l.
/2(,H~" or' 96~'0 ..
is the rate of speed

Hatt:

( ,"",flU t

9600 ~

!::?!;\.'CE(l

!·.·Ct::illl L:

P.3.J

X25-Protocol Parameters

X2r~-P:rotoccl tJac.:tmeters detine the parameters required ~:o maintai.n the
X .. .,.~5 pac ket J t.~vel pro tocol •
ThE' pac ket 1 evel pro to col is nee e::5sa r y to

es~ablish

a connection between two users over a virtual circuit.

TherE: ace

two

tyne~~

\j:;r.}rr,,:;·t,,~ s

(UTE

.tC~5-P:rot(,col

thel'!... anD] \

a Dr':: v

, ':1(' ';(0)
-

•

all connections between the DN20 and

i()ciepcncien t! •
1:.',;)'

tt,)

parameters:

'j :',,:~

t:n

ram.? te r s

A-7

specific
connection
(DTE
a :r e
d E: sec i b ed
i n ; : hen ext

NETGEN
A.3.3.1

Module X25-Protocol Characteristics Me~10ng

Parameter
Default data

is the default packet size, in bytes, for switched
virtual circuits.
You must supply the value
defined by your PPSN. The default data size is
the value of the packet size used for an Bve when
the flow control parameter negotiation facility is
not used.
(See the TOP8-10 PSI User's Guide for
additional
information- on
the --flow;
control
parameter negotiation facility.) The range is I to
1021.
De fa u 1 t :

Defaul t window

is the default packet-level window size
for
switched virtual circuits.
You must supply the
value defined by your PPSN.
The Default Window
size is the value of the window size used for an
sve when the flow control parameter negotiation
facility is not used. The range is 1 to 7.
De fa Ull t:

Max 1m urn da ta

is the maximum packet size that can be used when
the flow control parameter negotiation facility is
used. The range is 1 to 1021.
Default:

Max imum window

1 28

128

is the maximum window size that can be used when
the flow control parameter negotiation facility is
used. The range is 1 to 255.
Default:

Maximum clears

is the maximum number of times the software will
retransmit an unconfirmed clear request when the
Clear Timer wait interval is reached.
If your
PPSN does not recommend a value, use the default.
The range is 1 to 255.
Default:

Max imum rese ts

is the maximum number of times the software will
retransmit an unconfirmed reset request when the
Reset Timer wait interval is reached.
If your
PPSN does not recommend a value, use the default •
. The range is 1 to 255.
Defaul t:

Maximum restarts

is the maximum number of times
to retransmit an
unconfirmed restart request when the Restart Timer
wait interval is reached. If your PPSN does not
recommend a value, use the default. The range is
1 to :~5 5.

Defaul t:

A-8

NETGEN

Parameter

Meaning

Call timer

is the number of seconds the
software will
wait
before clearing an outgoing call request for which
there has been no response.
If the value of
the
Call
Timer
is
zero,
outgoing
calls are not
cleared.
If your PPSN does not recommend a value,
use the default.
The range is I to 255.
Default:

Clear timer

is the number of seconds the
software will
wait
before
retransmitting a
clear request for which
there has been no response from the PPSN.
If
the
value of Clear Timer is zero, clear requests are
not
retransmitted.
If your
PPSN
does
not
recommend
a val ue, use the de fa ul t.
The range is
o to 255.
Defaul t:

Reset timer

180

is the number of seconds the
software will
wait
before
retransmitting
an
unacknowledged restart
request.
If your PPSN does not recommend a value,
use the default.
The range is 0 to 255.
Defaul t:

Maximum groups

180

is the number of seconds the software will
wait
before
retransmitting
an
unacknowledged
reset
request.
If your PPSN does not recommend a value,
use the defaulto
The range is 0 to 255.
De fa u1 t :

Restart timer

200

180

is
the maximum number of closed
user groups
supported
by the X25-PROTOCOL module.
The range
is 0 to 20.
Defaul t:

A-9

NETGEN
A.3.3.2

Module X25-Prot(lcol Characteristics Known DTEs --

Parameters
DTEaddress

Meaning
is the DTE add re!ss of the physical connec t ion
the PPSN (ASCII string, 1-15 digits).
Default:

Line-id

Channels

for

the

physical

None

are a range of logical channel numbers used
outgoing SVcs (Switched Virtual Circuits).
De fa u 1 t :

Maximum channels

for

No n e

are the maximum number of logical channel numbers
that can be assigned to incoming and outgoing SVCs
for a DTE. The maximum channel range is 0 to 20~
Default:

A. 3. 3. 3

None

is the device identification
connection to the PPSN.
Default:

List Module X25-'Protocol Characteristics Known Groups -

If your PPSN subscription specifies that you are a member of a closed
user group or a bilateral closed user group, you need to specify the
parameters in this section. User groups are described in the TOPS-10
DECnet ~ PSI ~~ste~ Mallager'~,! .and Operator's Gui~~.
Parame tef.§..

Mean j~!!9.

Group name

is the name for tbeuser group,
syst€!m manager.
Default:

DTE address

the

None

is the number assigned by your PPSN for the closed
user group on the DTE defined above. The range is
o to 9999.
Default:

Group type

is the address of the DTE for which the user group
is defined (ASCII string of 1-15 digits).
Default:

Group number

assigned

None

is Bilateral if this is a bilateral closed
group; otherwise, omit this parameter.
Default:

None

A-10

user

NETGEN

A.3.4

X25-SERVER Parameters

The X25-Server module's primary fun(~tion is to de ermine v/hich user
receives the
incoming virtual circuit connect oh (virtual calls).
Each user job that is ellg ible to
receive
incom ng calls must be
defined
in the destination database, which is maintained by the
X25-Server module~
The following
s~ctions
describe
X25-Server
parameters.

A.3.4.l

Module X25-SERVER Characteristics -

Parameters
Max imum circuits

is the maximum number of virtual circuits
(sves
and PVCs)
the Server Module can have open. The
range is 0 to 2e.
Defanl t:

Maximum
Destinations

Maximum number Qf DECnet objects that Can receive
incoming calls. The range is 1 to 20.
Defaul t:

A.3.4.2 Module X25-SERVER Cbaracteristics I<nownDestinations- The
following . paramtE'ters, 'which are found in, the de,!3tJnation data base,
are necessary to route an Incomingyirtual ,call to ,a .pECnet object.
For adescriJ?ti()n of how the X25-SgHV~Rmqdule uses these parameters,
See the TOPS-I" pECnet ~.pdPSI Sysbem Manager's and '01?e~.ato~~§. Guide ..
Me a n.ill.9.
'ls;theDECnet C19ces$OQr)tr?lacq.o'Jnts:tr lng' to be
":used whEm the'. X2!5,...,Se):"ve,r mod~leconnects to the
"\lestination of an .. i'nQ0l'nJ99 call'.
For detail(~d
.infQI"mation, See>·t11e . .TOPS....l"OEGnet and PSI Syst~:.!!!
,fJ\anager's and Op~rat:Qr is Guide ..
Defanl t:

Nlliistririg
,..
,

---

...

":--

fSa hexadec imalstrJ~9~. ofll~,to.. 16 characters,
·used to determiri~t:hedes~ina~ion of ~n incoming
'call based on th,ec9Jltent 9f·th~. user call data
,fiel~(~ of
the~n.?PJT1in~Gal~ ,packet.' It is added
byte-by..-byte tothe;,user cal.1.· dCi:ta . . . fJeld, of. the
incoming call . . rac~et.
The ~esul ting str Ing is
compared with the Call Value.
.'
'Default:
..Is

Null string

a hexadec imalsti}ng, ()flJP~o

16 , characters,
to determine thE! ,destination of {in i ncom i 119
,:cal ~ . based on tpf-Jcontel'ltof':th~ use):" call data
;'field of the incoming G{illpack·~t •... It i s compar(~d
~yte-by-byte with the sirJng
r~sulting
from the
ci;lll mask operation to determine' the destination
'of an incoming eall.
u~ed

De fa ul t:

Null str Ing

A-II

NETGEN

Parameters

Mean in~9..

Group name

is the name used to determine the destination of
an incoming call based on user group membership.
If given, only incoming calls with this user group
n~me will be routed to this destination.
Default:

Node number

is used when the X25-Server module connects to the
destination of an incoming call. The range of
this parameter is 1 to 255.
Defaul t:

Number

are the range of the local DTE subaddresses tised
to determine the destination of an incoming cjll.
If given, only those calls with the called DTE
subaddress in the specified range are routed to
this destination.
A subaddress is a decimal
number from 0-99.
Default:

User-id

Null string

is the level of priority associated with a. gtven
entry in the destination data base. The highest
priority is 255 and the lowest is 0.
If an
incoming call maps to more than one destination,
the one with the higher priority is chosen.
If
there is more than one match with equal priorit~,
the first is chosen.
Defaul t:

Subaddresses

None

is the access control passwo rdtobe used when the
X25-Server module connects to the destination of
an incoming call.
Default:

Priority

Null string

is the DECnet object identification to be used
when
the
X25"';Server module connects to the
destination of an incoming ~all.
This parameter
is required.
Default:

Password

None

is the full remote DTE address used to determine
the destination of an incoming call based on the
calling DTE address in the incoming packet.
If
given, only incoming calls from the designated DTE
address are routed to this destination.' The
address is up to 15 digits in length.
Default:

Object

Null string

is the DECnet access control user identification
to be used when the X2S-Server module connects to
the/destination of an incoming call.
Default:

Null string

A-12

NETGEN
A.4

BUFFER SIZE GUIDELINES

The buffer size of the DN20 MCB software determines the
largest size
for
a message
that
the DN20 can send or receive.
NETGEN allows a
buffer size from 290 to 576 bytes.
The default
is
576,
which
is
appropriate
for most configurations.
However,
if the batch job
MCBSYS.CTL reports a system image size that is larger than l24K,
and
if you have no devices you can omit from the configuration, you must
reduce the buffer size.
The buffer size you set with NETGEN must be compatible with
the
Maximum Address entered
in MONGEN's network configuration dialog.
Ideally, the two values should be identical.
However,
systems that
contain NI hardware, without DN20 or CI hardware, may set the Maximum
Address to a much higher value than the maximum supported by the DN20.
The buffer size MONGEN symbol (%RTBSZ) should be the same value as
that assigned
to MCB nodes in NETGEN.
You can adjust the Ethernet
buffer size by defining the appropriate monitor symbol in
the HDWGEN
portion of MONGEN.
The symbols are listed in Table 2-1.
To adjust the DN20 buffer size in NETGEN, use the following command:
NETGEN)DEFINE EXECUTOR BUFFER SIZE nnn
The size of the buffer must be a decimal number between 515
and
576.
Refer
to
Table A-I for suggested buffer sizes in relation to network
si ze.
If you wish to use a DMC/DMR for the DECnet line in
the TOPS-10 PSI
Gateway node,
you must restrict the maximum node address in your
network to 140 or less and the buffer size on every node
in
the
network to 290.
F::ven thQll<jhyour install~tlon dqesn9tl,l~e. th~P.r4C/pMRdeYice for
DEene t
lil1:~:. in the TOPS71~l'SI·G.g.t'~,'9at •. :.:tlle.p~J(!l.\11t. 'v~Jll~S. ,of 255
maximum node.addreE)s .9n<j>576 ,,;o:. rb,1l:fJer·,~iz~·<::qr('ge:'·tpq19:rge
if
have a.small network.' If yourne:tw()r~:h:a·E)'l~:$$.~,Qanl1~, nodeS,
will obtain,bette:~gerfot'm9nceAf You 'se:tthem~,}drilbm nqde. aqdr'e'ss
140 and the buffer
ze to 290'"
" , ..

'si

,'.. , .".

the

for
you
you
to

. ~,

.,. ;~~~.:J ..;,'

Maximum Address
(2- 140)
If your network has.<tnore'than 140 ry~d~s/i,~'YO~\l~ll¥'l:r~~~~'
the DECnet Ifne in the 'I'OPS-10 PSI Ga tewi,iy ·fu:)(le.;."

A-13

for

NETGEN
Table A-I provides the parameter values as they are required by the
MaNGEN procedure and the NETGEN program.
To determine the parameter
values for a maximum address that is not in the
table, calcu~ate as
follows:
for each increment of the maximum node address, add 2 bytes
to the corresponding minimum buffer size.
For example,
if your
maximum node address
is 146, the buffer size must range from 297 to
576 bytes.
Table A-I:

A.5

Parameter Values For MaNGEN and NETGEN

Maximum Address

Buffer Size

145

295 - 576

155

315 - 576

165

335 - 576

175

355 - 576

185

375 - 576

195

395 - 576

205

415 - 576

215

435 - 576

225

455 - 576

235

475 - 576

245

495 - 576

255

515 - 576

NETGEN COMMANDS

To define the initial MCB configuration, see Chapter 3.
The syntax
for
the
individual NETGEN commands
is described on the following
pages.

A-14

NETGEN

Syntax:

DEFINE CIRCUIT

c i teui t·-id

c;H1\N.NE Lnon

' )

J·.M'.' ·.A... I ....M'...U M...·..··{·...D.·.A.:·.T· A. .:·..·•..

(

DrEnnn

· t..·•.•.

n.' '.n
.. n....
, x. . :' WINDOW'
hnn .}.....
TYPE X25

Description:
Define the characteristics of the allowed circuits that are PVCs.
Arguments:
C ire u it- id: c i r cui t numb e r; d ef a ul t , no n e
Channel:
numeric value, 0 to 4095;deJault, '0
DTE:decimal DTE address, 1 t.o IS digits; default, none
Maximum Data: numeric value, 1 to 65535, gefault, 128
Maximum Window:
numeric value, Ito 255, default, 2
Type:
X25; default, X25

Example:
~".

. . : ..

. .~.:.

. .'

NETGEN>DEFINE CIRCUIT DTE-0-1 MAXIMUMOATA 100
NETGEN)

A-IS

NETGEN
DEFINE EXECUTOR

Syntax:
ADDRESS nnn
BUFFER SIZE nnn
[DENTIFICATION txt
INACTIVITY TIMER nnn
ACCOUNT txt }
MANAGEMENT
PASSWORD txt
{ USER txt
DEFINE EXECUTOR
MAXIMUM

1.~~!!E~~~nnnl
LINKS nnn
VISITS nnn

NAME txt
OUTGOING TIMER nnn
PHASE II LINKS n
RECEIVE PASSWORD txt
RETRANSMIT FACTOR nnn
ROUTING TIMER nnn
TRANSMIT PASSWORD txt
Description:
Defines the characteristics of the host node,
and sets network
management
parameters.
The management ACCOUNT,
USER,
and
PASSWORD control access to NCP from remote nodes.
Arguments:
Address:
numeric value, 1 to 255; default, none
Buffer Size:
numeric value, 515 to 576; default, 576
Identification:
text, 1 to 32 characters;
default, DECnet-10 V3.0 Release
Inactivity Timer:
numeric value, 1 to 65535 seconds; default, 30
Management Account:
string, 1 to 16 characters; default, none
Management Password:
string, 1 to 8 characters; default, none
Management User-Id:
string, 1 to 16 characters; default, none
Maximum Address: node address,
numeric value, 10 to 255;
default, 255
Maximum Cost:
numeric value, 1 to 1022; default, 100
Maximum Hops:
numeric value, 1 to 30; default, 16
Maximum Links:
numeric value, 3 to 23; default, 11
Maximum Phase II Links: numeric value, 0 to 40; default, none
Maximum Visits: numeric value, 16 to 255; default, 32
Name:
node name, 1 to 6 characters; default, none
Outgoing Timer:
numeric value, 1 to 65535 seconds; defaultv 60
Receive Password: string, 1 to 8 characters; default, none
Retransmit Factor:
numeric value, 1 to 15; default, 5
Routing Timer: numeric value, 1 to 65535; default, 60
Transmit Password: string, 1 to 8 characters; default, DECNET20

A-16

NETGEN
DHFINE KNOWN LINES C()mmand (X. 25 onl y)

Syntax:
IRETRANSMISSION TIMER nnnl
DEFINE KNOWN LINES)MAXIMUM{RETRANSMITS nnn}(
\
WINDOW nnn
J
Description:
Defines parameters for the LAPB X.25 line.
Arguments:
Retransmission Timer: numeric value, 1 to 65535 milliseconds;
default, 3"00
Maximum Retransmits: numeric value, 0 to 255; default, 20
Maximum Window: numeric value, 1 to 255; default, 7
Example:
NETGEN)DEFINE KNOWN LINES MAXIMUM WINDOW 5
NETGEN)

A-17

NETGEN
DEFINE LOGGING FILE EVENT Command

Syntax:
DEFINE LOGGING FILE EVENT event-class
Description:
Specifies the types of network events to be logged in the logging
file.
The supported
event classes and types are listed in the
example for the LIST LOGGING command.
Arguments:
Event class:
numeric form, n.m, where n is the event class and rn
is the event type(s) within the class.
Example:
NETGEN)DEFINE LOGGING FILE EVENT 3.1
NETGEN)

A-l8

NETGEN

Syntax:

DATA nnl'l
}
{ WINDOW nn:n

CHANNELS nnn
CLEARS nnn
DATAnnn

GRQUPS finn

RES Elf'S "'rin n
RESTARTS nnn
WINDOW nnn

nnn

De sc ip ~lon:;,:
, .. :~:" .. -< .. ~ .. ~.,.:'

Defiri~.~,: :par~m~:~'~rs dJes9ribing the virtue.1 circuit to the PPS~.
Atg umen't~:;"

, 'nllmer iq,y~1ue, 1·:~'(); ... 25:5; .. aefa~11t:,?:00 . secdnds:
.

:'·~r::L.;',: ii9111:erlc yalue, 1 .to2·!)5; .. d.efaylt,.180p~90nd s
~:~~:::::.:;:flu~€!:r"icval ue, .. 1. to . . 10?}.;:· dEl!f~ut~f 128 .: ..
:nUll't¢r J9.'V al ue ,·• 1 .. :t~:2f).? i ·. • ·<3e£~1.llt:1 . 2
~<l9·re~~., 1,... }p. t? .(Ji<Jit:.~;.:, d~l~.M,~ t,' no:tie:
t1 0,-',1. ..1::0 . 16 i ... q ef a tl~t:/:nOt~tiJ.·< .•.•. . .:....> .. ', ,.
,::.,:~Ulil.~'x;..i~;V all);'ej ·t.:.~:O·ff'r .df!::f <14Jt:, . ?:0
"':,pu~erlc . v.alue,'0tQ.·':25'~:l'q~'~atllt,

6":.

).)~:u~~.:rJ.c::.,valll~~ . . 1.~oJ0~J)4:€!~~,l1l't:, . . +28
p~';i:,,~:l11.lIll:~~r;' +g."'v~lu,t3 i •• ". t,o'.'.2.0,; . .•:. <l~.~~:R+, t,: 0'
11 UJ:Il:r.r lq' va 1 ue,.0t9lt55;'<l ~ f~ tilt,€;
<~ :'U .tlUm er Ie v ~lue, .0..t~.r;Z5:;;:(ref9U 1 t, . 6
p,~,(:":j~ t;qt~rio:. \l a.1ue,.} . ~9 ." ,:2?;$.;A~f:~\;llJ:,,:.~f '

"", :'.:x; .

f';l,j;,a~ phei'l1 um.r- r to; ·. . q~ea,y,l,t,: .•. :hoQ'~.'>~ ".'~:':"" .'.
,r'rR':,,\'~lLl:~.t.'0.1:o.9,9t},~J •. d:~~ault', .nohe"
t£~:'.,'·· .'. ~. e'r. rcv~l ue, .. ' ~.':to:2',S'?)'J3~la,pJt'f lS0$~q()nds
',:"." )1,~tet,t9: yalue;1 . ~q,·?'S!"r,,(j,ef,aul~,,'.180 s'e'conds
,~'R~~.,>(g B,t;,lorial p.arard~,t etl j" '~'~'~'~:uXt,;Qone
~<;

, ~BtG,
NE-T:G

"~, >~"b~;:

':.,' .

.' . " ,..~

ri4~'!i.M!1t.EX 15-PRO~~~Ot. MAhMYM "CIlA}/Ntts

A-19

NETGEN
DEFINg MODULE X25-SERVER Command (X.25 only)

Syn tax:
ACCES~)PASSWORD

~ ACCOUNT tx t

txt,

(USER tx t

4"'

ACCOUNT txt
CALL jl"1ASK hex }
lVALUE hex
GROUP txt
MAXIMUM{CIRCUITS nn
'}
DESTINATIONS nn
DEFINE MODULE X25-SERVER

NODE nnn{DESTINATION txt
}
KNOWN DESTINATIONS
NUMBER nnn
OBJECT{name txt }
number nnn
PASSWORD txt
PRIORITY nnn
SUBADDRESSES nnn
USER txt

Description:
Defines parameters for the X.25 Server. The Server maintains the
interface between a DECnet logical link to the Gateway user and
the X.25 virtual circuit to the remote packetnet user.
When a
virtual call comes in, these parameters are provided by the PSI
software to set up a logical link to the Gateway user.
J'l.rguments ::
Access Account: text, 1 to 16; default, none
Access Password: text, 1 to 16; default, none
Access User: text, 1 to 16; default, none
Account~
text, 1 to 16; default, none
Call Mask: hexadecimal mask, 1 to 16; default, none
Call Value: hexadecimal value, Ito 16; default, none
Destination: node name, 1 to 16; default, none
Group: group name, 1 to 16; default, none
Maximum Circuits: numeric value, 1 to 20; default, 8
Maximum Destinations: numeric value, 0 to 20; default, 4
Node number: numeric, I to 255; default, none
Number: full remote DTE address, 1 to 15; default, none
Object name: alphanumeric, 1 to 16; default, none
Object number: numeric, 1 to 255; default, none
Password: text, 1 to 16; default, none
P rio r i t y : n um e ric, 0 to 2 5 5 ; de fa u It, 0
Subaddresses: numeric range, 0 to 99; default, none
User: alphanumeric, 1 to 16; default, none
A-20

NETGEN
DEFINE MODULE X25-SERVER Command (X.2S only)

(Cont.)

Example:
NETGEN)DEFINE MODULE X2S-SERVER MAXIMUM CIRCUITS 12

A-2l

NETGEN
EXCLUDE Command

Syntax:
EXCLUDE

(DMCll nnni
)DMRll nnn
) DTE20 nnn
~KDP nnn

Description:
Removes a device from the configuration.
In certain cases, NETGEN
command.
I f yo u type:

provides

default

for

the

EXCLUDE

included

device

NETGEN>EXCLUDE DMRll <ESC>
NETGEN automatically fills in the most recently
number for each device.
Arg umen ts:
DMCll:
DMRll:
DTE20:
KDP:

number
number
number
number

of
of
of
of

DMCll,
DMRll,
DTE, 1
KDP, 0

0 to 5
0 to 5
to 3
to 2

A-22

NETGEN
EXIT Command

Syn tax:
EXIT
Description:
Exits from NETGEN procedure.
Saves no
files
unless you have
begun with the START command.
To save your configuration files,
use SAVE and FINISHED before typing EXIT.

A-23

NETGEN
FINISHED Command

Syntax:
FINISHED
Description:
Indicates that you have finished your configuration.
When you
give this command, NETGEN writes its output files, NMLACC.MAC,
CETAB.MAC and NETPAR.MAC, to your directory.
If you have
generated a system that is incomplete or not a supported
configuration, NETGEN warns you.
See Chapter 3 for examples
using this command.

A-24

NETGEN
HELP Command

Syn tax:
HELP
Description:
Displays a short description of the function of NETGEN.

A-25

NETGEN
INCLUDE Command

Syn tax:
INCLUDE

(DMCll nnn)
) DMRll nnn ~
') DTE20 nnn (
~ KDP nnn
,

Description:
In certain cases, an
Adds a device to the configuration.
automatic default is provided for the INCLUDE command. NETGEN
provides 0 as a default or the next available number for all the
devices; however, the default for DTE20 is always 1.
For each DMRll you include, NETGEN asks you to specify the type
of transmission as either HALF or FULL duplex and prompts you for
th e cos t 0 f the 1 in e (a n urn be r fro mIt 0 2 5). Th e de fa u1 t cos t
is 1.
For each DMCll and DTE20 you include, NETGEN prompts you for the
cost of the line. The default cost for the DMCll and the DTE20
is 1.
NOTE
NETGEN default values for circuit cost may be
different from default values provided in the
MONGEN procedure.
Verify your values before
continuing with the installation.
If you include a KDP, NETGEN prompts you to specify the number of
lines on the KDP (KDPs numbered 1 to 4), the maximum baud rate
(line speed) for each, and the cost of the line as shown in the
example below. The default cost for the KDP is 0.
Arguments are described under the EXCLUDE command.

A-26

NETGEN
INFORMATION Command

Syntax:
INFORMATION

NODE
}
{ NODE-TYPE

Description:
The NODE argument displays the node name and node
NODE-TYPE argument displays either DN20 or X2S.
Example:
NETGEN>INFORMATION NODE
Node name is:
NEWER
Node address is:
12
NETGEN>INFORMATION NODE-TYPE
Node type is:
NETGEN>

DN20

A-27

address.

The

NETGEN
LIST Command

Syn tax:
EXECUTOR CHARACTERISTICS
LIST

)

~CIRCUITS CHARACTERISTICS'
LINES CHARACTERISTICS
'MODULES CHARACTERISTICS'
EVENTS

CHARACTERISTICS

X25-StRVER CHARACTERISTICS

l~~l1~n tl< t·~
lENOWN{GR~&~~}j

i;
)1

...N
.. OW.• N OgSTINATIONS}
{ . • ·.K
DESTINATION txt
!

Description:
Displays the characteristics you have set for executor and known
circuits and lines.
Also lists the supported event class types,
for the DEFINE LOGGING FILE EVENT command.
See the TOPS-10
DECnet and
PSI System Manager's and Operator's Guide for more
information about logged events.
Examples:
NETGEN)LIST LOGGING FILE EVENTS
LOGGING = FILE
SINK = (host)
EVENTS
0.0-3,6-9
EVENTS
1.2
EVENTS
2.0-1
EVENTS
3.0-2
EVENTS
4.0-10,12-13
EVENTS
5.6-12
EVENTS
6. 3- 4

A-28

NETGEN
LOG Command

Syntax:
LOG filespec
Description:
Logs all of your NETGEN commands in a disk file.
If you make a
mistake
in your NETGEN procedure,
you can TAKE this log file
instead of reentering all of the commands.
The default filename for the LOG file is the node name specified
in your NETGEN dialog.
For example, if your current node name is
MARL, your default LOG file is MARL. LOG.
Argument:
output file specification
Example:
NETGEN)LOG ? name of output file to record TTY input
NETGEN)LOG MARL. LOG
NETGEN)

•

A-29

NETGEN
PURGE EXECUTOR Command

Syntax:

PURGE EXECUTOR

IDENTIFICATION
ACCOUNT
) MANAGEMENT

{~~~~WORD}

~OUTGOING TIMER
Description:
Removes a parameter you have previously set.
event-class:
command

Arguments:

logging file event class and type,

A-30

refer

LIST

NETGEN
PURGE CIRCUIT COJnmand

(X. 25 only)

Syn tax:

PURGE CIRCUIT circuit-id

{CHANNEL

JDTg

} MA:<IMU;-.1

~TYJ?E: X25
Df-;,!SG

DATA
{ WINDOW

}l~

r i pt ion:

Removes an X.25 parameters that has been previously set.

Circuit-id:

circuit-number; default, none

Example:
NETGEN>PURGE CIRCUIT DT8-1-l TYPE X25

A-31

NETGEN
PU~GE

KNOWNf LINES Command (X.25 only)

syntax:
PURGE KNOWN LINES

(MAXIMIMUM{RET~.AN~MITS})

WINDOW

lRETRANSMISSION TIMER

Description:
Clears the values for the KNOWN LINES parameters
set.
Example:
NETGEN>PURGE KNOWN LINES RETRANSMISSION TIMER

A-32

that

you

have

NETGEN
PURGE LOGGING FILE EVENT Command

Syn tax:
PURGE LOGGING FILE EVENT event-class
Description:
Clears any logging file event classes that are currently enabled.
Refer to the LIST LOGGING FILE EVENT command.
Argument:
event-class: n.m, where n is the class type and m is
type(s) to be purged from the database.
Example:
NETGEN>PURGE LOGGING FILE EVENT 3.1
NETGEN>

A-33

the

event

NETGEN

PURGE MODULE X25-PROTOCOL Command (X.25 only)

Syn tax:
PURGE MODULE X25-PROTOCOL

CALL TIMER
CLEAR TIMER
MAXIMUM CLEARS
RESE'!'S
RESTARTS
RESE'I' TIMER
RESTART TIMER
ALL GROUP name
ALL KNOWN GROUPS
GROUP name TYPE

Description:
Purges the X25-PROTOCOL characteristics set by the DEFINE
X25-PROTOCOL command.
Example:
NETGEN>PURGE MODULE X25-PROTOCOL RESET TIMER
NETGEN)

A-34

MODULE

NETGEN
PURGE MODULg X25-SERVEH Command (X.25 only)

Syntax:

PURGE MODULE X25-SERVER

ALL
ALL DESTINATION node-name
ALL KNOWN DESTINATIONS

ACCESS

ACCOUNT
PASSWORD
{ USER

ACCOUNT

DESTINATION nOde-name}
{ KNOWN DESTINATIONS

CALL ~1ASK
CALL VALUE
GROUP
NUMBER
PASSWORD
PRIORI'fY
SUBADDRESSES
USER
Description:
Clears values set by the DEFINE MODULE X25-SERVER command.
Example:
NETGEN>PURGE MODULE X25-SERVER PASSWORD DESTINATION NEWNOD
NETGEN>

A-35

NETGEN

RES'I'ORE Command

Syn tax:
RESTORE filespec
Descrjption:
Restores an existing DN20 configuration file from disk.
When you
restore
a
configuration
file,
the
appropriate .MAC files are
initialized hy NETGEN.
If
you
have
set
any Management
Parameters
(User,
Account,
Password),
~~hey
are
not
restored
when
you
use
the RESTORE
command.
W~enever you change your configuration, use the
DEFINE
command
to
set
the
management
parameters
and
the
SAVE and
FINISHED commands to retain them.
For ?SI. insti~,11ations, the, X25·-SERVER ACCESS
PASSWORD
is
not
rest,o',red,with. the configuration. file.
If you restore an X.25
configu~atlon file, you must use tbe D~FINE X25-SERVER command to
set
the
password,
and
use
the SAVE and FINISHED commands to
reta
the pB sswo rd •

Refer
to
Section
3.2
configuration files.

for

procedures

for

Argument:
input

filespec

Example:
MARL.CNF
[ Configuration Restored From: MARL.CNF[100,200]]
NF:TCEN>

NETGEN>RE~TORE

A-36

modifyinq

MCl~

NETGEN
SAVE Command

Syntax:
SAVE filespec
Description:
Saves the current DN20 configuration parameters.
The output file
is named node.CNF, where node is the node name of the MCB node.
Arg ument:
output file specification
Example:
NETGEN)SAVE MARL.CNF
[ Configuration Saved On: MARL.CNF[100,200]]
NETGEN)

A-37

NETGEN
START Command

Syntax:
START
Description:
Engages the user
in an interactive dialog to enter
node
configuration parameters for DN20s to configure either MCB
software for the DECnet network, or PSI gateway software for the
X.25 network.
NETGEN gives warning and fatal error messages as necessary and,
if there are no fatal error messages, writes output files to the
user's directory.
The user may need to
give
additional
configuration commands and end the task with a FINISHED command.
NETGEN provides defaults for some parameters when you use the
START dialog. Display the defaults by pressing the ESCAPE key.
Refer to Chapter 3 for procedures for defining a DN20 node.

A-38

NETGEN
TAKE Command

Syn tax:
TAKE filespec
Description:
Tells NETGEN to read commands from the specified disk file rather
than expecting these commands to be entered from the terminal.
The default file specification is node.CMD,
node name of the MCB to be configured.
Arg ument:
input filespec
Example:
NETGEN)TAKE MARL.CMD
NETGEN)

A-39

where

node

the

NETGEN
A.6

NETGEN ERROR MESSAGES

This appendix contains error messages that NETGEN displays.
These
messages can occur when you enter information to NETGEN, or when you
try to SAVE the NETGEN files and EXIT from NETGEN.
The first character of each message
indicates
error.
The characters and their meanings are:
?

Fatal error

Warning message

the

severity

the

configuration,

you

configuration,

you

Information message
Some warning messages are not preceded with a flag.
The messages are listed in alphabetical order.

Address Must Be In Range 1 to 255
The specified node address must be in the range 1 to 255.
?Cannot open log file
?Cannot read file after open ok
[Configuration Restored From:
[Configuration Saved On:

filename]

?DMCII is already included, exclude it first
You cannot include a DMCII more than once.
?DMCll not in configuration
You have not included a
cannot exclude it.

DMCII

your

?DMRII is already included, exclude it first
You cannot include a DMRll more than once.
?DMRII not in configuration
You have not included a
cannot exclude it.

DMR1I

your

?Error opening restore file
?Error opening save file
?Error Reading Restore File - Data Area Corrupted
?Error writing save file
%Have you issued a SAVE command for this configuration?
The SAVE command saves all your configuration parameters.
If you
exit
from NETGEN without saving the configuration, and discover
errors that require
you
to
rerun NETGEN,
you will
have to
configure the node from the initial settings again.

A-40

NETGEN
?Illegal character in node name
A node name can contain alphabetic characters and
characters only.
Special characters are not allowed.

numeric

?Illegal to Exclude DMCll Other Than The Last One Included
To determine the correct number,
command.

use

the

INFORMATION

LIST

number

you

number

you

?Illegal to Exclude DMRll Other Than The Last One Included
To determine the correct number,
command.

use

the

INFORMATION

?Illegal to Include DMClls except in Numeric Order
Use the INFORMATION or LIST command to find the last
incl uded.
?Illegal to Include DMRlls except in Numeric Order
Use the INFORMATION or LIST command to find the last
incl ud ed •

?Illegal to Exclude KDP Controller other than last one Included
Use the INFORMATION or LIST command to find
last KDP included.

the

number

the

?Illegal to Include KDP Controllers except in numeric order
Use the INFORMATION or LIST command to find
last KDP included.

the

number

?Incorrect DTE20 number
The number you specified is outside the valid range (1 to 3).
?Invalid KDP Controller Number
The number you gave for the KDP controller is outside
range (0 to 2).

the

valid

the

valid

?Invalid KDP number
The number you gave for the KDP controller is outside
range (0 to 2).
?Invalid number of DUPll lines, must be in range 1-4
The number you gave for the number of DUPll lines is outside
valid range.
Use a value from 1 to 4.

the

?KDP Controller is already included, exclude it first
You cannot include a KDP controller more than twice.
?KDP not in configuration
You have not included a KDP in your configuration, so you
exclude it.

A-41

cannot

NETGEN
?KDPll Number Must Be In Range " To 2
The number you gave for the KDP controller is outside
range (0 to 2).
?Length Of Save File Differs From Expected
This File

Length

The file specified in a RESTORE
Check your file specification.

command

the

valid

Cannot

Restore

wrong

length.

?Logging error
%More than 8 communications lines on a DN20 is unsupported.
You have included too many synchronous lines on your

DN20~

?Name Must Contain At Least One Alphabetic Character
A node name must contain at least one alphabetic character.
?Name Must Start with Alphabetic Character:

"nnn"

A node name cannot begin with a number or special character.
?No such DUPll in this KDPII
?Number of DMxll

(DMC/DMR) Devices Exceeded -

Cannot Add this DMCII

The maximum number of combined DMCII and DMRII
inc I ud e is 6.
?Number of DMxl1

(DMC/DMR) Devices Exceeded -

devices

you

can

Cannot Add this DMRII

The maximum number of combined DMCII and DMRII
incl ude is 6.

devices

you

can

Warning message.
Runnable software is created if you see
message, but you should set this parameter for each node.

this

%Physical address already in use
?Physical Address Must Be In Range I To 255
?The Node Address has not been set

?The node address must be less than or equal to the number of nodes in
the net.
The output files are not written.
Check your node address.
If
the
address
is larger than the number of nodes in the network,
your node will be unable to talk to its host, and all loads will
fa il •
The node address requires a MAXIMUM ADDRESS of at least xxxx
The node address you use and the maximum address you give must be
compatible.
Correct either one.
?The Node Name has not been set
Runnable software is created if you see
this
should set this parameter for each node.

A-42

message,

but

you

NETGEN
The number of nodes in the net requires a BUFFER SIZE of at least xxxx
The number of nodes in the network and the buffer size
must be compatible.
Change either one or the other.

you

use

This system is not supported by DEC
You have created software with parameters outside the allowed
ranges.
See the documentation describing configuration for the
valid ranges.
%Version Mis-Match -

File Might Not Be Compatible

Warning message.
You have specified a file in a RESTORE command
that may be the correct length, but the data in the file may not
be compatible with the current software.
Check your file
specification, or rerun NETGEN.
?You have not configured any communications lines.
This is a fatal error message.
If you receive this message,
the
output
files
are not written.
You have not
included any
synchronous lines (DMC, DMR, KDP) for your DN20 node.
The DN20
configuration must
include at least one synchronous line for
communication with the network.
?You have not specified any communications lines.
You must include at least one communications line
you are configuring.

for

any

node

between

your

?Your DN20 has no DTE.
The output files are not written.
host and your DN20 is required.

A-43

DTE-20

link

APPENDIX B
PSITST

This appendix describes the PSITST program, which is used as a test
package and software development tool. You can use PSITST to isolate
faults during the installation, or to verify the installati,on hardware
and software components.
PSITST provides a way for users to test communication software during
software development. Logging features of PSITS1 can be used to debug
the software being developed, trace data traffic to or from user
software, or detect events on a virtual circuit between the user
software and PSITST.
PSITST consists of two processes: PSITSB and PSITST.
PSITSB is a
background process that handles communication with the PPSN.
It
creates a switched virtual circuit and causes data to be transmitted
over that circuit. PSITST is a foreground process that provides ~ou
with command interfaces to control activities of the PSITSB background
process.
These processes are
following functions:

used

verify

installation

Successful completion of outgoing X.25 requests

Successful processing of incoming X.2S calls

Data transmission over a virtual circuit

Virtual call clearing

testing

the

The two processes communicate through the Interprocess Communication
Facility (IPC~ mechanism. A copy of the PSITSB can communicate with
only one foreground process PSITST at any one time.
In a normal environment, PSITSB is started by the system and continues
in the background as a detached job.
You need only to run the
foreground process PSITST in order to communicate with your PPSN.

B-1

PSITST

PSITSB

User Command
Interfilce

Figure B-1:
B.1

IPCF
Communlc:ation

Jt----:----tt
Gateway
Access Protocol

PSITST Softw.are Components

RUNNING PSITST

PSITST can run in both a normal
and a private environment.
In a
normal
environment,
PSITSB is accessible to all users on the system;
however, PSITSB cannot be accessed simultaneously by more than one
user.
You can set up both processes to create a private foreground
process in which PSITST communicates with the private background
process, PSITSB, only.

B.1.1

Normal Environment

In this environment, assume that PSITSB has been started by the system
file,
SYSJOB.INI, at startup time and is running as a detached job.
To run PSITST, type:
.. RUN PSITST
PSITST responds by displaying a message similar to the following:
KLl010 RN176D Triple System, TOPS-10 Monitor 7 .. 03{00}
TOPS-10 PSI PSITST Version 1 .. 0 (QI)
(Normal Environment)
Monday, March 7, 1985 02:19:00PM
PSITST displays tbe prompt:, PSITST>, when it is ready to receive your
commands.

B.1.2

Private Environment

In this environment, it is assumed that you will start both
beginning with PSITSB.
Te. run PSITSB, type:
• GET SYS: PS IT'SB
Job setup

• D 0 1 135

.CSTART
.DETACH
From job 29

B-2

processes

PSl1'ST
You can now proceed to log
typi ng:

into the

system

different

job

.LOGIN 100,200
JOB 36 RN176D Triple System TTY126
Passwo rei:
Other jobs detached with the same PPN:
Job 29 FSITSB running
Do you want to ATTACH to this job?
[YJ NO
[LGNJSP Other jobs same PPN:29]

run PSITST, type:
.GET SYS:PSITST
setup

,Tob

.D 0 1 135
.ST~RT

PSITST responds by displaying a message similar to the following:
KL1010, RN176D Triple System, TOPS-I0 Monitor 7.03(00)
TOPS-I0 PSI PSITST Version 1.0(0)
(Private Environment)
Monday, March 7, 1985 02:19:00PM
PSITST displays the prompt, PSITST>, when it is ready to receive
commands.

8.1.3

your

Duplicating PSITST Processes

If another user is running PSITST in the normal environment, your copy
fail
and a message similar to the following will be
of PSITST will
displayed:
KL1010, RN176D Triple System, TOPS-10 Monitor 7.03(00)
TOPS-10 PSI PSITST Version 1.0(0)
(Normal Environment)
Monday, March 7, 1985 02:19:00PM

? PSITST Process Already Exist
?Encountered IPCF Error

If this message is displayed in the private environment, it indicates
that another copy of PSITST has been initiated by one of your other
login jobs.

B-3

PSITST
.1.4
rf
d

Missing PSITSB Process

the PSITSB process is not running \lJ'hen you run the PSITST program,
message similar to the following will be displayed on your screen:
KL1010, RN1760 Triple System, TOPS-IS Monitor 7.03(00)
TOPS-10 PSI PSITST Version 1.0(0)
(Normal Environment)
Monday, March 7, 1985 02:19:00PM
? PSTTST Partner Process Does Not Exist

? Encountered IPCF Error

B 1.5
5

GALAXY Compatibility

If your system supports a version of GALAXY ,that is not compatible
with the field image GALAXY, PSITST may fail.
If PSITST fails due to
incompatible G.a.LAXY software, it displays a message !~imilar to the
following and halts:
KL10l0, RN176D Triple System, TOPs-10 Monitor 7.03(00}
TOPS-10 PSI PSITST Version 1.0(0)
(Normal Environment)
Monday, March 7, 1985 02:19:00PM
Failed to initialize GALAXY

B.2

ACCESS PORTS

PSITST maintains ten ports for access to,tbe TOPS·10 PSI Gateway node.
Each port isassoeiat.ed w:ith a virtu(il pix;quit. A PS,ITST port maps to
a port in the TOPS-10 PSI Gatewaya~ a swi.tched orperlTlanen~ port.
A
switched port is associated with a switched virtual circuit. A
permanent , port is associated wi th.a p~rmanent virtual circuit., The
association is defined by the PSlTSrLISTEN~ CALL, ~nd OPEN commands.
The CLOSE command erids the associatJrin.
A port may be specified by its numeric identification, which ranges
[rom 0 to 9. A collection of ports m~y also be identified by their
characteristics. PSITST maintains three types of ports:
known,
active, and inactive.
A port is considered to be one of the
following:
known

whetn it has been referenced, at least once, by any of
the PSITST commands that affect its characteristics and
staltus.

active

wh E' n a vir t: ua lei r cui t:
thc:t port.

inactive

when a virtual circuit is
thClt port.

8-4

cur r en t 1 Y ass a cia ted

wi th

with

longer

associated

PSITST
B.3

INITIALIZATION

You may prepare a
set of
PSITST commands and
save
them
in
the
initialization file PSI'I'ST.INI in your directory.
PSITST executes the
commands in this indirect command file every time you run the program.
For
initial
PSI checkout,
a
copy of PSITST.INI is provided on the
distribution tape.
Using
the
initialization feature
is discouraged
in
the
normal
environment,
as you may unintentionally interfere with another user's
PSITSB communication setup.
If all
initalizations commands
displays a messaae similar to:

are

executed

successfully,

PSITST

KL1010, RN176D Triple System, TOPS-10 Monitor 7.03(00)
TOPS-10 PSI PSITST Version 1.0(0)
(Private Environment)
Monday, March 7, 1985

02:19:00PM

Initialization Completed
PSI'rST>
If PSITST fails to execute any of the commands in
the
initialization
file,
it notifies you by displaying appropriate messages on the
terminal similar to:
KL1010, RN176D Triple System, TOPS-10 Monitor 7.03(00)
TOPS-10 PSI PSITST Version 1.0(0)
(Private Environment)
Monday, March 7, 198

02:19:00PM

? Command "LISTEN 0 OBJECT USER"

failed

PSITST>

B.4

LOGGING

PSITST software keeps track of events, transmitted and received
data,
and counters
for
each port.
This
information can
be
recorded
selectively in a log file for any specific interval.

B-5

PSIT:ST
Log File Contents

B.4.l

The soft",.,are records the information in the log file DSK:PSITST.LOG.
If the log file already exists, the softwaie appends the new
information to the current log file. The following information types
can be recorded in the log file:
o

User commands

The following events:
TOPS-10 priority system interrupt
Receipt of call request ~acket
Automatic accept of incoming call
Call request being accepted
Call request being re5e(~ted
Permanent virtual circuit beingalloca ted successfuily
Failure to obtain a permanent virtual circuit
Automatic no--communication confirmatiohon perrnangnt
virtual circuit
'
Receipt of reset indication p~cket
Automatic reset confirm4tion
Rece:iptof r.~set confintlatJonp~ck~t
Switched virtual circuit befn~Jcl elir e<i d:UE~ bo fa i1.ur:e'to
confi rma reset .~ndicatJonpr()mptly
Receipt of interrupt~essa9~packet
Automat ic in te rr opt conf irrn~~lon
Rece:ipt of itlterrup~,C:9hfJrin'~:ttotfpaCket.
Rece :ipt of clear ind .i?a1~iot1.pa'ck~t
R.ace:t pt of clear con f.irrrl(;l,tiot1PCic:k~t
Bece:lpt of c(,rrupted h91~ma1.d<:ltapa'c1<(;!ts
Receipt of corrupted qual~;ied da~apackets
Port fatal er.'ror, due t(»).o$sof 90mJ9~niGatlon wi t;:h . t;:he"
'TOPS··10 PSI Gateway nod:~;and'portsta'te 'bE~comes eRROR

Zeroed counters

Received accept data

Received accept

Received call data

Received call facilities

'Rece ived reset cause and d i (~g h 0 s tic

Received interrupt data packets

Received normal data packetg

Received qualified data packets

Received clear C;:3use and diagnostic

Received clear dc~ ta

Rece ived clear facilities

In the normal environment, the log file is written to the PPN [l,2J.
In the private environment, the log file Is written to the PPN from
which the user starts the background process, PSITSB.

8-6

User Command Log Entry

B.4.2

The format of recorded user command is:
hh:mm:ss

PSITST> <command>

[PSITST response or error message]

where <command>

is the user command as typed.

For exarnplf?:
16:19:50
PSITST> CALL 1 REMOTE DTE 311030300012
? Command "CALL 1 REMOTE DTE 311030300012 " failed
16:20:01

PSITST> CALL 1 REMOTE DTE 311080100170

16:29:16

PSITST> SEND 1 NORMAL DATA fILE CRIGHT.TXT.4

16:29:21

PSITST> SHOW

Port I

* COUNTERS

Counters

Incoming Calls = 1
Calls Accepted = 1
Normal Data Packets = 2
Normal Data Bytes
177

Wait For
Incoming
Received
Received

Port I 1;

Counters

Call Requests = 1
Transmitted Normal Data Packets = 2
Transmitted Normal Data Bytes = 177

Event Log Entry

B.4.3

The format of recorded event is:
hh : mm: 55

Po;~'

<n>~

where:
<n> is the port number
<event message> is one of the following:
o

Accepted Incoming Call

Confirm,:~d

Confirmed Reset Indication

Switched Circuit Is Denied

Received Clear Confirmation Packet

Received Clear Indication Packet

Fatal Error Condition

Received Call Connectp.d Packet

Received Call Request Packet

Interrupt Request

B-7

PSITS'T

Received Interrupt Confirmation, P?lcket

Received Interrupt Packet

Permanent Circuit Is Heserved

o ,Permanent Circuit Is Denied
o

TOPS-I0 Priority System Interrupt Indication

Received Reset Confirmationp~cket

Too Much Delay A.fter Virtual Circuit Reset

Received Reset Indication Packet

Received Corrupted Normal Data

Received Corrupted Qualified Data

For example:
11:19:49

Port

Rece ived Incoming Call Packet

11:19:49

Port

Accepted Incoming Call

11:19:49

Port

Received Call Connected Packet

Received Data and Facilities Log Entry

B.4.4

hh:mm:ss Port

<n>; <data type> I <count> (data)

where:
<n> is the port number
<count> is the length of the dat~ in octets
<data type) is one of the following;
0

Received Accept Data

Received Accept Facilities

Received Call Data

Received Call Facilities

Received Clear Data

R.ece ived Clear F'ac 11 1 ties

Received Interrupt Data

Received Normal Data Packet

Received Qualified Data Packet

PackE~t

B-8

PSITST

For example:
16:29:04

Port # 0;

Received Call Facilities, 8 bytes

001 000 000 041 005 002 006 010
16:29:18
bytHS
124
141
156
145
16 :3
040
156
012
14:3
167
145
143
040
16 : 29 : 18

Port # 0;

Received Normal Data Packet (More bit) , 128

150
162
1 !31
162
145
142
144

040
151
145
040
150
165
157
171
144
040
040
151
040

P~7

143
1 ~)1
162
150
141

151
145
163
040
040
145
040
156
157
164
155
040
156

163
040
150
141
141
040
143
154
162
150
163
154
144

Port # 0;

150 040
16~) 163
164 150
143 157
156 IS7

B.4.5

1 ••• ! ••••

164
151
145
160
164

150
157
040
171
151

163 1S7
163 040
144 040
154 151
144 040
163 145
160 151
040 151
141 156
164 150
157 146
J.43 145
167 151

146 164
146 165
165 156
143 145
155 141
144 040
145 144
156 040
143 145
145 040
040 163
156 163
164

167
162
144
156
171
141
015
141
040
164
165
145

l'I'his softwl
lare is fur I
Inished und I
ler a 1icenf
Ise and may!
I be used al
Ind copied .1
I.only in al
Iccordance I
I with the tl
lerms of sui
Ich 1icensel
I and wit I

Received Normal Data Packet, 49 bytes
145
156
141
162
143

040
015
142
151
145

lSI 156
012 157
157 166
147 150
056 015

143
146
145
164
012

154
040
040
040

lh the inc11
fusion •• of I
Ithe above I
Icopyright I
Inotice ••• I

Clear and Reset Diagnostic Log Entry

The format of the clear and reset diagnostic entry is:
hh :mm: ss Po r t

(n>; <type> Cause <cause>, Diagnostic <diagnostic>

vihere:
<n> is the port number
<type> is the diagnostic type (Clear or Reset)
<cause> is the value of the cause byte in octal and decimal
(diagnostic> is the value of the diagnostic byte
in octal
decimal
Example:
16: 30:11

Port -# 0;

Reset Cause 000

16:.30:35

Port # 0;

Clear Cause 000 (0), Diagnostic 177 (127)

8-9

(0), Diagnostic 377 (255)

and

PSITST
B.4.6

Examples

The following threl~ examples show the type of entries
for successful and unsuccess ful transm i ss ions.

you

might

see

Example 1:
The following example shows the type of entries you might see with a
successful connection on Port 0, a calIon Port 1, and a successful
transmission of data.
Node KL1010 - KL10l0, RC703 7.03, TOPS-10 Monitor 7.03(00)
TOPS-10 PSI PSITST Version 1.0(5)
(Normal Environment)
Monday, October 15, 1985 09:2l:09AM
09:21:09

PSITST> ENABLE 0 LOGGING ALL

09:21:10

PSITST) DISABLE 0 LOGGING PRIORITY SYSTEM INTERRUPT

09:21:12

PSITST> ENABLE 1 LOGGING ALL

09:21:13

PSITST> DISABLE 1 LOGGING PRIORITY SYSTEM INTERRUPT

09:21:14

PSITST) SET 0 OBJECT X25TST

09:21:15 PSITST> ENABLE 0 AUTOMATIC ACCEPT INTERRUPT
CONFIRMATION
RESET CONFIRMATION
09:21:16

PSITST> SET 1 NE'l'WORK TELENET

09:21:17

PSI'rST> SET 1 REMOTE DTE 31J060701234

09:21:18

PSITST) LISTEN 0

09:21:24

PS rrST> CALL 1

09: 21 : 25

Port # 0;

Received Call Request Packet

09:21:25

Port # 0;

Received Call Fa'cilities, 8 bytes

001 000 000 041 005 002 006010

I ..., • ! ,., ....

09:21:25

Port # 0;

Accepted Incdming Call

09:21:25

Port # 1;

Received Call Connected Packet

09:21:25

Port # 1;

Received Accept Facilities, 6 bytes

000 041 005 002 006 010

8-10

I .! •.••

PSI'1'S'I'
09:21:29

PSITST> SHOW

Port # 0;

* STATUS

Status

Network = TELENET
Object Identification = X25TST
Po rt S ta te = Runn Ing
Error State Detail = None
Last Port Request = Accept Incoming Call
Last Request Error = None
Network Data = None
Network Interrupt = None
Po r t # 1 ;
Network

Status

= TELENET

Port State = Running
Error State Detail = None
Last Port Request = Read Accept Data
Last Request Error = No Data To Read
Network Data = None
Network Interrupt:;:: None
PS,ITST) SEND 1 NORMAL DATA STRING "ABCDEFGHIJKLMNOP
09: 21: 31
QRSTUVWXYZ012345678 9",15,12 COUNT 25
09: 21: 31
101
113
125
064
09:21:32
101
113
125
064
09:21:32
101
113
125
064
09: 21 : 32
101
113
125
064
09:21:33

Pc rt # 0;
lei2
114
126
065

Heceived Normal Data packet,

103 1~'4 105 106
115 116 117 120
127 130 131 132
066 067 070 071

Port # 0;

107
121
060
015

110 111 112
122 123 124
061 062 063
012

38 bytes
IABCDEFGHIJI
!KLMNOPQRSTI
! UVWX YZ 01 23 I
1456789 ••
I

Rece ived Normal Data Packet, 38 bytes

le;2 103 lQJ4 105
114 115 116 117
12:6 127 130 131
065 066 067 070

106
120
132
071

107
121
060
015

110 I I I 112
122 123 124
061 062 063
012

I ABCDEFGHIJ I
I KLMNOPQRS'r I
I UVWXYZ 01231
14~56789 ••
I

Pert # 0;

Received Normal Data Packet, 38 bytes

1Qi2 103 1 ~'4
114 115 116
lL:6 127 130
065 066 067

105 106 107 110 111 112
117 120 121 122 123 124
131 132 060 061 062 063
1070 1071 QI15 1012

I ABCDEFGHLJI
IKLMNOPQRSTI
I UVWXYZI0123!
1456789 ••
I

Port # 0;

Heceived Normal Data Packet,

38 bytes

lel 2
114
126
065

103
115
127
066

If14
1J.6
130
067

Port # 0;

101 1~12 103 1"4
113 114 115 116
125 126 127 130
064 1065 066 067

1135
117
131
070

106 107
1210 121
132 QI60
071 015

1110 I I I 112
122 123 124
061 062 063
012

IABCDEFGHIJI
IKLMNOPQRSTI
lUVWXYZI01231
1456789 ••
I

Heceived Normal Data Packet,

38 bytes

105 106 107 110 111 112
117 120 121 122 123 124
131 132 QJ60 061 1362 1063
1070 1071 Q1l5 012

IABCDE:FGHIJI
IKLMNOPQRSTI
I uvwx YZ 01 2 3 I
1456789 ••
I

B-ll

PSITs'r

09:21:33
101
113
125
'064
09:21:33
101
113
125
064
09:21:33
101
l13
125
,064
09, ;21: 34

Port # 0;

Recelved Normal Data Packet, 38 bytes

102
114
126
065

105
117
131
070

101
113
125
0'64
09:21: 34

101
113
125
064
09: 21: 35
101
113
125
064

107
121
060
015

110 111 112
122 123 124
061 062 063
012

IABCDEFGHIJI
IKLMNOPQRSTI
IUVWXYZ01231
1456789 ••
I

Received N'ormal Data Packet, 38 bytes

10.2
114
126
06 ~3

105
117
131
070

103
115
127
066

104
116
130
067

106
120
132
071

107
121
060
015

110 III 112
122 123 124
061 062 063
012

lABCDEF'GHIJI
IRLMNOPQRSTI
IUVWXYZ0123!
1456789 ••
I

Po:~·t

i 0-

Received NQrmal Data Packet, 38 bytes

10:2
114
126
065

103 104
115 116
127 131l'
066 067

105
117
131
070

Port # 0;

106 1j~7
120 1 :21
132 060
071 015

110 III 112
122 123 124
061 062 063
012

Rece ived Normal Data Packet,

103 104 105 106 1"7
115 116 117 120 121
127 131~ 131 132 060
066 067 070 071 015

110 111 112
122 123 124
061 062 063
012

/ABCDEFGHIJI
IKLMNOPQRSTI

I UVWXY~~012 31
1

1456789 ••

38 bytes
fABCDEFGHIJI
IKLMNOPQRST/
IUVWXY2:01231
1456789 ••
I

Port # 0;

Received Normal Data Packet, 38 bytes

102
114
126
06 :;

105
117
131
070

103 104
115 116
127 130
066 067

Port # 0;

101 10~: 103 104
113 11~! 115 116
125 126 127 13~'
064 06~, 066 067
09:21:34

106
120
132
071

Port # 0i

,101 102
113 114
125 126
064 06!)
09: 21: 34

103 104
115 116
127 130
066 067

Port # 0;

106 Hn 110, 111 112
120 121 122 123 124
132 060 061, 062 063
071 015 012

I ABCDEF'GHIJ 1
IKLMNOPQRSTI
I UVlII/XYZ0123I
14567~9. ;;
I

Received Normal Data Packet, 38 bytes
105
117
131
070

106
120
132
071

107
121
060
015

110 111 112
122 123 124
061 062 063
012

/ABCDEFGHIJI
I KLr-1NOPQRST I
IUVWXYZ01231
1456789 ••
I

Received Nc,rma1 Data Packet, 38 bytes

102 103 104 105 106 107 110 III 112

I ABCDEFGHIJ I

114 115 116 117 120 121 122 123 124

IKLMNOPQRSTi
lUVWXYZ01231
1456789 ••
I

126 127 130 131 132 060 061 062 063
065 066 067 070 071 015 012
Port # 0;

Received Normal Data Packet, 38 bytes

102
114
126
065

105 106 107, 110 III 112
117 120 121 122 123 124
131 132 060 061 062 063
070 l~ 71 015 012

103
115
127
066

104
116
130
067

8-12

IABCbEFGHIJi
IKLMNOPQRSTI
I UVWXYZ01231
1456789 ••
I

PSITST
09: 21 : 35

Port # 0;

101 1!~2 103 10'4
113 114 115 116
125 126 127 130
064 065 0'66 067
09: 21 : 35

Port # 0;

leI 102 10'3 10'4
113 114 115 116
125 126 127 130
064 065 066 067
09: 21 : 35
101
113
125
064
09:21:36
101
113
125
064
09: 21: 36
101
113
125
064
09: 21: 36
101
113
125
064
09;21:37
10'1
113
125
064
09:21:37

Rec(~

105
117
131
070'

Ived Normal Data Packet, 38 bytes
106
120
132
071

107
121
060
015

110 111 112
122 123 124
061 062 063
012

IABCDEFGHIJI
I KLMNOPQRSl" I
IUVWXYZ01231
1456789 ••
I

Received Normal Data packet, 38 bytes
105 106 107 lIe 111 112
117 120 121 122 123 124
131 132 060 061 062 063
070' 071 015 012

I ABCDEFGHIJ I
IKLMNOPQRSTI
IUVWX'tZ01231
1456789 ••
1

Port # 0;

Received Normal Data Packet, 38 bytes

102
114
126
065

105
117
131
070'

103
115
127
066

104
116
130
067

P,:>rt # 0;
102
114
126
055

106
120
132
071

107
121
060
015

110 I I I 112
122 123 124
061 062 063
012

I ABCD.EFGHIJ I
IKLMNOPQRSTI
!UVWXYZ01231
1456789 ••
1

Received Normal Data Packet, 38 bytes

103 11~4 105 106
115 116 117 120
127 130 131 132
066 067 070 071

107
121
060
015

110 111 112
122 123 124
061 062 063
012

I ABCDEF'GHIJ I
IKLMNOPQRSTI
I fJVWXYZ012 31
1456789 ••
I

Port # 0;

Received Normal Data Packet, 38 bytes

12'2
114
126
0,65

105
117
131
070

10' 3 1134
115 116
127 130
066 067

106
120
132
071

107
121
060
015

110 111 112
122 123 124
061 062 063
012

IABCDEFG IJ I
IKLMNOPQRSTI
IUVWXYZ01231
1456789 ••
I

Pt)rt # 0-,

Received Normal Data Packet, 38 bytes

102
114
126
065

105 106 107 110 I I I 112
117 120 121 122 123 124
131 132 060 061 062 063
070 ~171 015 012

103
115
127
066

104
116
130
067

1l\8CDEFGHIJI
IKLMNOPQRSTI
IUVWXYZ01231
1456789 ••
I

Port # 0;

Received Norma Data Packet, 38 bytes

1!212
114
126
065

105
117
131
070

103
115
127
066

104
116
130
067

Port: # 0;

10'1 102 103
113 114 115
12~; 1 (~6 127
064 065 066

104
116
130
067

106
120
132
071

107
121
060
015

110 111 112
122 123 124
061 062 063
012

IABCDEFGHIJI
IKLMNOPQRSTI
!UVWXYZ01231
1456789 ••
I

Received Normal Data Packet, 38 bytes
105
117
131
070

106 1 e; 7 110 I I I 112
120 121 122 123 124
132 1~60 061 062 063
071 \;:'15 012

8-13

IABCDEFGHIJI
IKLMNOPQRST\
I UVWXYZ012 31
1456789 •.

PSITST
09:21:37

Port,# 0;

101 102 103 104
113 114 115 116
125, 126 127 130
1364 065 1366 067
09: 21: 37

Port '# 0;

'leI 102 103 104
113 114 115 116
125 126 127 130
064 065 066 067
09: 21':38

Port # 0;

Received Normal:pa,ta I>~cj.(.~t" 3fiJbyt~s"
105
117
131
070

106
120
132
071

107 110 III 112
121 122' 'Ii3 124
060 ,06,~ 062 063
015012

rABcJ)EFbIi:IJJ
.IKLMNOJ?QR$Tl
" I UVWXYZ0123 I
,,1'456789..
,

Received Normal Data I?ac:k~t, 38 bytes
105
117
131
070

1136
120
132
071

1137 110 III 112
121 122 123 124
06'0 ~(51 062 063
015 012

Received Normal ,Data

IABCDEFGHIJI

'I KLMNOPQR'ST I
!UYWX¥z01231
1456789 •• ' I

,.
" ..

leI 1132 1133 104 105 106 1fjT, lIe 111 112

.,'

,."

.. ","

'J A~'cDEr¢HI,fl

113 114 115 116 117 120 121 122 123 124
IRLMNOPQRST J
125 126 127 1313 131 132 060 0pl 1362 0,63"
I U'lWX¥,Z0 1231
064 065 066 067 1370 071 1315 ,~r2
',\'1456789"",,, t
~ <( .... ". ~<:. ..~
" .~',
09:21: 38

Port '# 0:

101 102
113 114
125 126
'064 065
09:21:46

103
115
127
066

104
116
130
067

Received NormaiData Pack~l,:38 byt~~
105
117
131
070

106
120
132
071

I I I 112
123 124
1362 et?~

IABCDE'FGffXj I

IF<I:.MNOPQR$TI

,J u VW~YZ 0123 I
14567$9 •• '"

PSI'I'ST) SHOW * DATA

Port # 0;

Data

More BIt Setting = Enabled
Tran$mi.tbed,Interrupt = NoneOutf3tand ing
Received Interrupt = None Outstanding
Data Transmission = Normal
'.
Received Normal Data Pac'keti~ 38 bytes
,'101" 1 ~ 2 103 104 105 106 10'7, 110,,, III 112
'113114 11 5 116 117 1 20 121 12,2' 12 3 12-4
'125 126 127 130 131 132 060,061 062 063
064065 066 067 070 071 015 B 1 2 ,
Last Data Reception Error ::'NoData'To
Pot t i 1;

JABC b~FGfttJI
"I KLMl\lOl'QRSTj
Il.JVWX¥,~ 01~' 31

J 45678'9..

Data

More Bit Setting = Enabled
Transmi fb~d Interrupt:: None. 6ut:st~nding
,Rece ived Inter rupt = None OU'1:starlding
DataTr ansm 1 ss ion = Normal
TransmittE~d. Normal Data:: 38' bytes
101 102 103 104 105 106 107 110 III 112
11~ 114 115 116 117 120 121 122 ii3 124
125 126 127 130 131 132 063 061 062 063
064 065 066 067 070 071 015 012

8-14

'I ABCDE.f'GHI~JI
IKLMNOPQR$TI
I UVWX'iz'012 3t
1456789."
I

PSI,]'ST
09:21:47

PSITST> SHOW * COUNTERS

Port i 0;
Wait For
Incoming
Received
Received
Port i

Counters
Incoming Calls = 1
Calls Accepted = 1
Normal Data Packets = 25
Normal Data Bytes = 950
Counters

Call Requests = 1
Transmitted Normal Data Packets = 25
Transmitted Normal Data Bytes = 950
09:21:48

PSITST) RESET 1 DIAGNOSTIC 377