Digital PDFs

AA-EB30A-TC

2000

385 pages

Original

10MB

Document:	DECnet-RSX Guide to Network Management Utilities Sep85
Order Number:	AA-EB30A-TC
Revision:	0
Pages:	385
Original Filename:

OCR Text

Networks· Communications
.... . . . . . .. . . . . . ..... . . . . ... ... .... ......
----. .•

•

DECnet-RSX
Guide to
Network Management Utilities

~D~DD~D

wore

•

DECnet-RSX
Guide to
Network Management Utilities
Order No. AA-EB30A- Te

September 1985
This DECnet-RSX Guide to Network Management Utilities describes
the utilities related to DECnet-RSX network management.

Supersession/Update Information:

This is a new manual.

Operating System and Version:

RSX-11 M V4.2
RSX-11 S V4.2
RSX-11 M-PLUS V3.0
Micro/RSX V3.0

Software Version:

DECnet-11 M V4.2
DECnet-11 S V4.2
DECnet-11 M-PLUS V3.0
DECnet-Micro/RSX V1.0

AA-EB30A-TC
First Printing, September 1985

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 only be used
or copied 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 or its affiliated companies.
Copyright © 1985 by Digital Equipment Corporation
The postage-prepaid Reader's Comments form on the last page of this document requests
the user's critical evaluation to assist us in preparing future documentation.

The following are trademarks of Digital Equipment Corporation:
DEC
DECmate
DECnet
DECUS
DECwriter
DIBOL

~D~DDmD

MASSBUS
PDP
P/OS
Professional
Rainbow
RSTS
RSX

RT
UNIBUS
VAX
VAXcluster
VMS
VT
Work Processor

Ethernet IS a trademark of Xerox Corporation.

This manual was produced by Networks and Communications Publications.

Contents
Preface

Network Management Utilities (CFE, NCP, VNP)
1.1
1.1.1
1.1.2
1.2
1.2.1
1.2.2
1.2.3
1.3
1.3.1
1.3.2
1.4
1.4.1
1.4.2
1.4.3
1.4.4
1.4.5
1.4.6
1. 5
1. 5.1
1.5.2
1.5.3

Configuration File Editor (CFE) ...................................... 1-1
Invoking CFE ........................................................ 1-1
Exiting CFE .......................................................... 1-2
Network Control Program (NCP) .................................... 1-3
Invoking NCP ........................................................ 1-3
Exiting NCP .......................................................... 1-4
ExecutingNCPRemotely ............................................ 1-4
Virtual Network Processor (VNP) .................................... 1-5
InvokingVNP ........................................................ 1-5
ExitingVNP .......................................................... 1-6
Using the Network Management Utility Commands ................. 1-6
General Command Format .......................................... 1-6
Issuing Commands .................................................. 1-7
Using the Help Facility ............................................... 1-8
Command Prompting ................................................ 1-8
Using the LIST and SHOW Commands ............................... 1-9
Exit Status and Error Handling ....................................... 1-9
Command Descriptions ............................................ 1-10
Graphic Conventions .............................................. 1-10
Standard Definitions .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 1-11
RSX-IIM/M-PLUS CFE, NCP, and VNP Command Summary ...... 1-13
CLEAR ALIAS ....................................................... 1-14
CLEAR CIRCUIT ................................................... 1-15
CLEAR EXECUTOR ................................................ 1-16
CLEAR EXECUTOR NODE ......................................... 1-17
CLEAR LINE ........................................................ 1-18
CLEAR LOGGING .................................................. 1-19
CLEARMODULEX25-ACCESS .................................... 1-22
CLEAR MODULE X25-PROTOCOL ................................ 1-23
CLEARMODULEX25-SERVER .................................... 1-24
CLEAR MODULE X29-SERVER .................................... 1-24
CLEARNODE ...................................................... 1-25

Contents-1

CLEAR OBJECT .................................................... 1-28
CLEAR PROCESS ................................................... 1-29
CLEAR SYSTEM .................................................... 1-30
CLEAR TRACE ...................................................... 1-31
DEFINE CIRCUIT .................................................. 1-32
DEFINE EXECUTOR ............................................... 1-36
DEFINE LINE ....................................................... 1-40
DEFINE LOGGING ................................................. 1-44
DEFINEMODULEX25-ACCESS ................................... 1-46
DEFINE MODULE X25-PROTOCOL ............................... 1-47
DEFINEMODULEX25-SERVER ................................... 1-52
DEFINEMODULEX29-SERVER ................................... 1-52
DEFINE NODE ............., ........................................ 1-54
DEFINE OBJECT ................................................... 1-57
DEFINE PROCESS .................................................. 1-59
DEFINE SYSTEM ................................................... 1-61
KMX-DUMP ....................................................... 1-63
LIST CIRCUIT ...................................................... 1-64
LIST EXECUTOR ................................................... 1-65
LIST LINE .......................................................... 1-66
LIST LOGGING ..................................................... 1-67
LIST MODULE X25-ACCESS ....................................... 1-68
LIST MODULE X25-PROTOCOL .................................. 1-69
LIST MODULE X2 5-SERVER ....................................... 1-70
LIST MODULE X29-SERVER ....................................... 1-70
LISTNODE ......................................................... 1-71
LIST OBJECT ....................................... , ............... 1-72
LIST PROCESS ...................................................... 1-73
LIST SYSTEM ....................................................... 1-74
LOAD NODE ....................................................... 1-75
LOAD VIA .......................................................... 1-78
LOOP CIRCUIT .................................................... 1-80
LOOP EXECUTOR + .NODE ........................................ 1-83
LOOP LINE ......................................................... 1-85
PURGE CIRCUIT ................................................... 1-86
PURGE LINE ........................................................ 1-87
PURGE LOGGING .................................................. 1-88
PURGEMODULEX25-ACCESS .................................... 1-89
PURGE MODULE X2 5-PROTOCOL. ............................. " 1-90
PURGEMODULEX25-SERVER .................................... 1-91
PURGE MODULE X29-SERVER ..................... , .............. 1-91
PURGE NODE ...................................................... 1-92
PURGE OBJECT .................................................... 1-94
SET ALIAS .......................................................... 1-95
SET CIRCUIT ....................................................... 1-96
SET EXECUTOR .................................................... 1-98
SET EXECUTOR NODE ........................................... 1-102
SET KNOWN LINES ............................................... 1-103
SET LINE .......................................................... 1-106

Contents-2

1.5.4

SET LOGGING .................................................... 1-110
SETMODULEX25-ACCESS ...................................... 1-113
SET MODULE X25-PROTOCOL. ................................. 1-114
SET MODULEX25-SERVER ...................................... 1-116
SET MODULEX29-SERVER ...................................... 1-116
SET NODE ........................................................ 1-119
SET NODE CIRCUIT .............................................. 1-122
SET OBJECT ...................................................... 1-123
SET PROCESS ..................................................... 1-125
SET SYSTEM ...................................................... 1-127
SET TRACE ....................................................... 1-128
SHOW ALIAS ..................................................... 1-129
SHOW AREA ...................................................... 1-130
SHOW CIRCUIT .................................................. 1-131
SHOW EXECUTOR ............................................... 1-132
SHOW LINE ....................................................... 1-133
SHOWLOGGING ................................................. 1-134
SHOWMODULEX25-ACCESS ................................... 1-136
SHOW MODULE X2 5-PROTOCOL. .............................. 1-137
SHOWMODULEX25-SERVER ................................... 1-139
SHOW MODULE X29-SERVER ................................... 1-139
SHOWNODE ..................................................... 1-141
SHOWOBJECT ................................................... 1-143
SHOW PROCESS .................................................. 1-144
SHOW SYSTEM ................................................... 1-145
SHOWTRACE .................................................... 1-146
TELL .............................................................. 1-147
TRIGGER NODE .................................................. 1-148
TRIGGER VIA ..................................................... 1-150
ZERO CIRCUIT ................................................... 1-152
ZERO EXECUTOR ................................................ 1-153
ZERO LINE ........................................................ 1-154
ZERO MODULEX25-PROTOCOL. ............................... 1-155
ZERO MODULEX25-SERVER .................................... 1-156
ZERO MODULE X29-SERVER .................................... 1-156
ZERO NODE ...................................................... 1-157
ZERO SySTEM .................................................... 1-158
RSX-11SNCPCommandSummary ............................... 1-159
LOOP EXECUTOR/NODE ......................................... 1-160
SET CIRCUIT ..................................................... 1-162
SET EXECUTOR HOST ............................................ 1-;163
SET LINE ... '" ..................................... , .............. If164
SET LOGGING CONSOLE ......................................... 1(165
SHOW CIRCUIT .................................................. 1-166
SHOW EXECUTOR ............................................... 1-167
SHOW LINE ....................................................... 1-168
SHOWLOGGINGCONSOLE ..................................... 1-169
SHOW NODE ..................................................... 1-170
SHOW SySTEM ................................................... 1-171

Contents-3

ZERO CIRCUIT ................................................... 1-172
ZERO EXECUTOR ................................................ 1-173
ZERO LINE ........................................................ 1-174
ZERO NODE ...................................................... 1-175
ZERO SySTEM .................................................... 1-176

Console Carrier Requester (CCR)
2. 1
2.2
2.3

Event File Interpreter (EVF)
3.1
3.2
3.3
3.3.1
3.4
3.4.1
3.4.2
3.4.2.1
3.4.2.2
3.4.2.3
3.4.3
3.4.4
3.4.4.1
3.4.4.2
3.4.4.3
3.4.4.4
3.4.4.5
3.4.4.6
3.5

Invoking and Exiting KDA ........................................... 4-1
Using the KDA Command ............................................ 4-2

LAT Control Program (LCP)
5.1
5.2
5.3
5.3.1

Contents-4

Invoking EVF ........................................................ 3-1
Exiting EVF .......................................................... 3-2
EVF Command Format .............................................. 3-2
Using the EVF Default Command Line ............................... 3-3
EVF Option Descriptions ............................................ 3-4
Using Multiple Option Arguments ................................... 3-6
File Control Options ................................................. 3-6
The Output File Option .............................................. 3-7
The Spooling Option ................................................ 3-7
The Delete Option ................................................... 3-8
Output File Format Control. ......................................... 3-8
Event Selection Options ............................................. 3-9
The ALL Event Option ............................................... 3-9
The DATE Options .................................................. 3-9
The Entity Filter Option ............................................ 3-10
The Event Specification Filter Option .............................. 3-12
The Source Node Filter Option ..................................... 3-13
ISO Switch - Specify Source Node Filter ............................ 3-13
EVF Error Messages ................................................. 3-14

KMX/KMY Dump Analyzer (KDA)
4.1
4.2

Running CCR ........................................................ 2-1
CCR Special Characters .............................................. 2-2
CCRErrorHandling ................................................. 2-2

INVOKING and EXITING LCP ....................................... 5-2
LAT Characteristics .................................................. 5-2
LCPCOMMANDS: Format and Syntax ............................... 5-3
CREATE ............................................................. 5-5

5.3.2
5.3.3
5.3.4
5.3.5
5.3.6
5.3.7
5.3.8
5.3.9
5.3.10
5.3.11

Network Crash Dump Analyzer (NDA)
6.1
6.2
6.3
6.4
6.4.1
6.4.2
6.5
6.6
6.7
6.7.1
6.7.2
6.8

NDA Operation ...................................................... 6-2
System Requirements ................................................ 6-3
Obtaining a Crash Dump ............................................. 6-3
RunningNDA ........................................................ 6-4
Running NDA as an Installed Task ................................... 6-4
Running NDA as an Uninstalled Task ................................ 6-4
NDA Command Syntax .............................................. 6-5
Indirect Command Files ............................................. 6-8
NDA Switches ....................................................... 6-8
Analysis Control Switches ........................................... 6-8
Function Control Switches ......................................... 6-11
NDAErrorMessages ................................................ 6-14

Network Display Program (NTD)
7.1
7.2
7.2.1
7.2.2
7.3
7.4
7.5

DEFINE .............................................................. 5-6
EXIT ................................................................. 5-9
HELP ................................................................ 5-9
LIST CHARACTERISTICS .......................................... 5-10
SET ................................................................. 5-11
SHOW CHARACTERISTICS ........................................ 5-14
SHOW COUNTERS ................................................. 5-16
START .............................................................. 5-18
STOP ............................................................... 5-21
ZERO [COUNTERS] ................................................ 5-22

Invoking NTD ....................................................... 7-2
NTDCommands ..................................................... 7-3
Immediate Mode Commands ........................................ 7-3
Command Mode Commands ......................................... 7-5
NTD Resource Display Format ...................................... 7-6
NTDNodeSummaryDisplayFormat. .............................. 7-10
NTD Area Summary Display Format. ............................... 7-11

Queue Manager (QUE)
8.1
8.2
8.3
8.3.1

FTS and QUE Components ........................................... 8-1
Invoking QUE ....................................................... 8-3
QUE Command Syntax .............................................. 8-3
Initializing/Deleting and Starting/Stopping the Queue and the
Processor ..................................
8-4
Assigning and Deassigning the Processor ............................ 8-5
Holding, Releasing, andDeletingFTS User]obs ..................... 8-6
Related Queue Management Functions .............................. 8-7
e ••••••••••••••••••••••••••

8:3.2
8.3.3
8.4

Contents-5

8.4.1
8.4.2
8.4.3

Trace Interpreter Task (TRI)
9.1
9.2
9.3
9.4
9.5

Purging FTSSYS.LOG and FAL.LOG ................................. 8-7
Listing FTSQUE and FTS]obs ........................................ 8-8
Listing and Purging URB Files ........................................ 8-9

Invoking TRI ........................................................ 9-1
Exiting TRI .......................................................... 9-2
TRI Command Format. ............................... _.............. 9-2
Contents of Trace Output ............................................ 9-4
TRI Error Messages .................................................. 9-5

Utility Error Messages
10.1
10.2
10.3
10.4
10.5
10.5.1
10.5.2
10.5.3
10.6
10.7
10.8
10.9
10.10
10.11

CCR Error Messages ................................................ 10-3
CFE Error Messages ................................................. 10-5
EVF Error Messages ............................................... 10-24
HLD Error Messages ............................................... 10-29
NCP Error Messages ............................................... 10-36
RSX-11M/-PLUS Error Message Format .......................... 10-36
RSX-11 S Error Message Format ................................... 10-38
NCP Error Messages ............................................... 10-38
NDA Error Messages .............................................. 10-56
NTD Error Messages .............................................. 10-61
NTINIT Error Messages ........................................... 10-62
NTL Error Messages ............................................... 10-66
TRI Error Messages ................................................ 10-79
VNP Error Messages ............................................... 10-82

Process Names

Object Type Codes

Examples
7 -1
7-2
7--3
7 -4

Sample Default Resource Display .................................... 7-9
Sample Old Resource Display ........................................ 7-9
Sample Node Summary Display .................................... 7-11
Sample Area Summary Display ..................................... 7-12

8-1

FTS and QUE Components ........................................... 8-3

Figure

Contents-6

Tables
3-1
3-2
4-1
5-1
6-1
6-2
6-3
7 -1
7 -2
8-1
9-1
A-I
B-1

EVF Output Options ................................................. 3-4
EVF Input Options ................................................... 3-5
KDA Command Switches ............................................ 4-2
LAT Command Format .............................................. 5-3
NDA File Default Values ............................................. 6-6
NDA Analysis Control Switches .............,........................ 6-9
NDA Function Control Switches ................................... 6-11
Immediate Mode Commands ........................................ 7-3
Command Mode Commands ......................................... 7-5
FTS and QUE Components ........................................... 8-2
Trace Interpreter Switches .......................................... 9-3
DECnet-RSXProcesses .............................................. A-I
Object Type Codes .................................................. B-1

Contents-7

Preface

The DECnet-RSX Guide to Network Management Utilities presents information
needed to use the utilities that manage a DECnet-RSX node within a DECnet
network. The term DECnet-RSX collectively refers to four DECnet products:
• DECnet-llM. which runs on RSX-IIM
• DECnet-llM-PLUS. which runs on RSX-IIM-PLUS
• DECnet-lMicro/RSX. which runs on Micro/RSX
• DECnet-llS. which runs on RSX-llS
This manual also describes network management utilities for RSX-ll PSI and
DECnet-RSX/PSI. The term DECnet-RSX/PSI refers to an RSX system that
runs RSX-ll PSI and DECnet-RSX simultaneously.
The utilities described in this manual are used to manage DECnet-llM V4.2.
DECnet-llS V4.2. DECnet-llM-PLUS V3.0, and DECnet-Micro/RSX V1.0
nodes. You can use these utilities to m~nage both local and remote DECnet
systems, which may be other than RSX based. Although Phase IV DECnet
provides for cross-system network command operation, there are also some
system-specific commands. RSX systerh-specific commands are flagged in the
DECnet-RSX Network Management Reference Card. For implementations other
than DECnet-RSX, refer to the network documentation for that system.

Preface-1

Intended Audience
This manual is intended for anyone who is responsible for building, maintaining,
and managing the network. In this manual, all such people are collectively
referred to as the network manager.

Structure of This Manual
This manual is tab divided into four distinct parts. The parts and their contents
are summarized below.
Part I CFE, NCP, and VNP

Chapter 1

Network Management Utilities (CFE, NCP, VNP)

Describes the format, parameters, and usage of all CFE, NCP, and VNP
commands.
Part II Network Management Tools

Each of the chapters in Part I I describes the operation of a network
management tool, including commands for its operation and examples of its
use and/or output (where applicable).
Chapter 2

Console Carrier Requester (CCR)

Chapter 3

Event File Interpreter (EVF)

Chapter 4

KMX/KMY Dump Analyzer (KD A)

Chapter 5

LAT Control Program (LCP)

Chapter 6

Network Crash Dump Analyzer (ND A)

Chapter 7

Network Display Program (NTD)

Chapter 8

Queue Manager (Q UE)

Chapter 9

Trace Interpreter Task (TRI)

Preface·2

Part III Error Messages

Chapter 10

Utility Error Messages

Summarizes all error messages for the following tools and utilities: CCR. CFE.
EVF, HLD, LCP. NCP. NDA. NTD. NTINIT. NTL. TRI. VNP.
Part IV Appendixes

Appendix A

Process Names

Lists the valid process names for DECnet-RSX/PSI.
Appendix B

Object Type Codes

Lists the object type codes currently In use.

Associated Documents
Before reading this manual. you should have a working knowledge of [) ECnet
and the RSX-ll operating system you are using. A prerequisite to the effective
use of this manual is familiarity with the overall character of D ECnet as
descri bed in the following manuals:
Introduction to DECnet
DECnet-RSX Network Management Concepts and Procedures

Network generation and postinstallation checkout procedures are described In
the following manuals:
DECnet-RSX Network Generation and Installation Guide
RSX-Il PSI Generation Guide
LAT Network Manager's Guide

Preface-3

Acronyms
The following acronyms for DECnet-RSX and PSI components are used in
this manual:
ACK

Positive acknowledge message

BCUG

Bilateral closed user group

CCB

Communication control buffer

CCITT

Comite Consultatif International Telephonique et Telegraphique

CCR

Console carrier requester

CCS

Console carrier server

CDA

Crash Dump Analyzer

CEX

Communications E xecu ti ve

CFE

Configuration File Edi tor

CSR

Control status register

CUG

Closed user group

DAP

Data Access Protocol

DCB

Device control block

DCE

Data circuit-terminating equipment

DDCMP

Digital Data Communications Message Protocol

DDM

Device dri vet module

DECS

Digital Ethernet Communications Server

DLC

Data link control process

Preface-4

DLL

Down-line system loader

DLM

Data link mapping

DLX

Direct line access controller

DNA

Digital Network Architecture

DSR

Dynamic storage region

DTE

Data terminal equipment

DTR

DECnet test receiver

DTS

D ECnet test sender

DUK

Dump KMX task

DUM

Up-line system dumper

ECL

End Communication layer

EVF

Event File Interpreter

EVL

Event Logger

EVR

Event-logging receiver

FAL

File Access Listener

FRMR

Frame reject error

FTQ

File transfer queue manager

FTS

File Transfer Spooler

HLD

Host Task Loader utility

IeB

Interrupt Control Block

Preface-5

KDA

KMS-ll microcode dump analyzer

KRB

Controller request block

LAPB

Link access procedure. Version B (CCITT recommendation for
frame level protocol)

LAT

LQcal Area Transport

LCN

Logical channel number

LDB

Large data buffer

LLC

Logical link control process

LUN

Logical U ni t N urn ber

MIR

Loopback Mirror

MOP

Maintenance Operation Protocol

NAK

Negative acknowledgment message

NCP

Network Control Program

NDA

Network Crash Dump Analyzer

NFT

Network File Transfer utility

NICE

Network Information and Control Exchange Protocol

N(R)

Next expected sequence number

D ECnet user interface pseudodevice

NTD

Network Display Program

NTDEMO

Network Display Server

NTINIT

Network initializer

Preface-6

NTL

Network loader

PSI user interface pseudodevice

ODT

On-line debugging tool

PIP

Peripheral Interchange Program

PLI

Packet level interface

PSDN

Packet Switching 0 ata Network

PSI

PSI Packetnet System Interface

PVC

Permanent virtual circuit

QUE

Queue manager

RAM

Random access memory

RDB

Receive data buffer

RNR

Recei ve not ready

SCB

Status Control Block

SDB

Small data buffer

SLD

Satellite task loader

SVC

Switched virtual circuit

TDM

Time-division-multiplexed bus

TKB

Task builder

TRI

X.25 trace interpreter task

UCB

Unit Control Block

Preface-7

UFD

User file directory

UIC

User identification code

UMR

UNIBUS mapping register

URB

User Request Block

VMR

Virtual Monitor Console Routine

VNP

Virtual Network Processor

XDT

Executive Debugging Tool

XPT

Routing layer

Preface-8

Conventions Used in This Guide
Convention

Meaning

Monospace

Monospace type indicates examples of system output or
user input. System output is in black; user input is In
red.

[ ]

Sq uare brackets indicate that the enclosed data is optional.
[f a vertical list of options is enclosed, you can specify
only one option. Do not type the brackets when you
enter the command.

{ }

Braces indicate that you must choose one, and only one,
of the enclosed options. Do not type the braces when
you enter the command.

( )

Parentheses enclose a set of options that must be specified
together or not at all.

Options
in lists

The absence of brackets around vertical lists indicates
that the items are optional.

UPPERCASE
LETTERS

Indicate text that must be entered as shown. Uppercase
words can be abbreviated to the first 3 or more unique
characters.

italicized
lowercase words

Indicate generic terms that must be replaced with
specific data. NCP/VNP commands that are system
specific are printed in red. All CFE commands are RSX
system specific.

<KEY>

Indicates that you should press the specified key.
<CTRL/X > indicates that you should press the <CTRL >
key simultaneously with the X key, X being the desired
letter. Note that unless otherwise specified, every
command line is terminated by pressing the <RET> key.
All numbers are decimal unless otherwise noted. All
Ethernet addresses are given in hexadecimal.

Preface-9

1
Network Management Utilities (CFE, NCP, VNP)

This chapter describes the network management utilities and summarizes their
commands. CFE commands modify the permanent database. while NCP
commands modify the volatile (running) database. VNP commands are used to
modify the system image file. VNP is not supported for Micro/RSX systems.
Each utility is described below. including how to invoke it and how to exit
it. Details on how to use the commands and individual command descriptions
follow.

1. 1 Configuration File Editor (CFE)
The Configuration File Editor (CFE) is a privileged utility program that accepts
commands from a terminal or from an indirect command file to modify or
display parameters in the configuration file, CETAB.MAC. which is produced
during network generation. CFE commands operate exclusively on the
permanent database. Note that all CFE commands are privileged. To invoke
CFE, you must be privileged to access the CETAB.~'IAC file.
1.1.1 Invoking CFE

Before invoking CFE. you must know the device and UIC under which
CETAB.MAC resides. After network generation. CETAB.~IAC resides under
one of the following VICs:
DECnet-RSX-IIM/M-PLUS

[x.54]

DECnet-RSX-llS

[x.64]

where x is the network VIC selected during network generation.

1-1

There are two ways to invoke CFE:
1. MCR>RUN CFE

CFE then prompts'
Enter filename:

Enter the name of the configuration file you want to modify. If you omit any
part of the file specification. the default is SY:[cu,.,.ent-uic]CETAB.:NIAC. The
CFE utility reads the specified file and constructs a memory-resident version
of this file. For large configuration files this process takes several seconds.
CFE then prompts

CFE>
Enter your CFE command after the prompt and press RETURN.
2. MCR>CFE

@command file [/TR]

where command file is the name of an indirect command file containing CFE
commands and ITR is an optional switch that allows you to trace the commands
as they execute. You can nest command files.
1.1.2 Exiting

CFE

There are three ways to exit CFE:
1. Use the EXIT command or <CTRL/Z> in response to the CFE prompt to
terminate an editing session and update the configuration file.
CFE>EXIT
MCR>

2. Use the EXIT PURGE command in response to the CFE prompt to terminate
an editing session. update the configuration file. and delete the old file.
CFE>EXIT PURGE
MCR>

1-2

DECnet-RSX Guide to Network Management Utilities

3. Lse the KILL command in response to the CFE prompt to abort an editing
session. The configuration file is not updated. and the old file is retained.

CFE>KILL
MCR>

1.2 Network Control Program (NCP)
The Network Control Program (NCP) is a utility program that accepts
commands from a terminal or from an indirect command file to load, control.
monitor. and test the network software. as well as to down-line load an
RSX-llS system.
There are two versions of ~CP: a full set of commands for DECnet-llM and
M-PLUS systems and a subset of these for DECnet-llS. Both sets of commands
are described in detail in this chapter and are summarized in the DECnet-RSX
Network Nlanagement Reference Card.
You can execute most NCP commands both locally and remotely (see Section
1.2.3). The DECnet-RSX Network Management Reference Card lists all NCP
commands supported by D ECnet-RSX and flags those that are not executable
remotely. It also highlights those commands that are specific to DECnet-RSX
only.
1.2.1 Invoking NCP

There are three ways to invoke NCP:
1. MCR>NCP

NCP then prompts

NCP>
Enter your NCP command after the prompt and press RETURN.

2. MCR>NCP command
where command is any valid NCP command. With this method, you return to
MCR after the command is executed.

Network Management Utilities (CFE. NCP, VNP)

1·3

3. MCR>NCP @command tile [/TR]
where command (i1e i" the name of an indirect command file containIng NCP
commands and ITR is an optional switch that allows you to trace th~ commands
as they execute. You can nest command files.

1.2.2 Exiting NCP

Use either the EXIT command or <CTRL/Z> in response to the ~CP prompt
to exit NCP.
1.2.3 Executing NCP Remotely

Most D ECnet-RSX NCP commands can be issued at your terminal for execution
at any Phase IV or Phase III remote node. In addition. you can issue many
NCP commands not executable by DECnet-RSX. This allows you to use NCP
commands that are supported by other DECnet implementations but not by
D ECnet- RSX. For more information about these other NCP commands. see
the D ECnet documentation of the remote node.
Remote command execution is useful in many ways; for example. you can use
it to modify parameters or display information at a remote node. or you can
down-line load a node that is not adjacent to your system. Remote execution
can be accomplished in two ways:

• To execute a single NCP command at a remote node. issue it with the
TELL prefix (see the TELL command description in this chapter). The
DECnet-RSX Network Management Reference Card summarizes all NCP
commands and flags the few that cannot be executed with the TELL prefix.
• To execute a series of NCP commands at a remote node. use the SET
EXECUTOR NODE command to temporarily set a specified remote node
as the executor. Any subsequent commands that you issue are executed at
that node until you return execution to your own node by issuing a CLEAR
EXECUTOR NODE command. (Both commands are described in this
chapter.) If you exit ~CP. control automatically reverts to the local node.
When you issue commands to be executed at a remote node. you may have
to specify access control information to access the node. You can append the
access control information to the node name. or you can specify an alias node
name that includes access control information. Section 1.5.2 provides more
information on the format of access control information.

1-4

DECnet-RSX Guide to Network Management Utilities

The remote node interprets all commands according to its own network
management software and uses any required default parameters from its own
database. Therefore, you must issue the command as if it were originating at
the remote node. Consult the appropriate DECnet documentation if the node
is other than DECnet-RSX.

1.3 Virtual Network Processor (VNP)
The Virtual Network Processor (VNP) is a pnvileged utility program. VNP is
not supported on .Micro/RSX systems. It accepts commands from a terminal
or from an indirect command file to modify or display the DECnet-R8X
software configuration as contained in an RSX-ll system image file. All VNP
commands are privileged and operate exclusively on the system image file.
VNP does not support commands that cause displays to be written to a file
Before using VNP, you must use the Virtual ~lonitor Console Routine (V~lR)
to set the NETUIC in the RSX system image file. Use one of the following
commands:
VMR>SET INETUIC = [xxx.54] (for RSX-IIM/M-PLUS)
VMR>SET INETUIC = [xxx.641 (for RSX-llS)
VNP uses the NETUIC when it searches for the network software on the LB:
device. Therefore. it is imperative that the proper NETUIC be set in the
system image file and that LB: be assigned.
1.3.1 Invoking VNP

There are two ways to invoke VNP:
1. MCR>RUN VNP

VNP prompts
Enter filename:

Enter the name of the operating system file you want to modify. If you do
not specify the device and UIC. the SY: device and the current UIC are used.
(There is no default file name.) VNP then prompts
VNP>

Network Management Utilities (CFE, NCP, VNP)

1-5

Enter your VNP command after the prompt and press RETURN.
2. MCR>VNP @command tile (fTR]

where command file is the name of an indirect command file containing VNP
commands and ITR is an optional switch that allows you to trace the commands
as they execute. You can nest command files.
1.3.2 Exiting VNP

Use either the EXIT command or <CTRL/Z> in response to the V~P prompt
to exit VNP.

1.4 Using the Network Management Utility Commands
The following sections contain general information on command usage.
1.4.1 General Command Format

Most commands consist of three parts: the command verb, a component on
which the command operates. and one or more parameters that further qualify
the action to be taken on the component. Examples of the general command
format follow:
Command Verbs

Components

Parameter Lists

CLEAR

EXECUTOR

HOST
RECEIVE PASSWORD
TRANSMIT PASSWORD

CLEAR

1-6

l i

fLINE line-id
ALL
"\.KNOWN LINE~ ~

DECnet-RSX Guide to Network Management Utilities

For each command. you must supply the verb. one component option, and
(usually) one or more of the parameters. Generally. the order in which you
specify parameters does not matter. However, some commands have parameters
that are mutually exclusive for the component. For example. in the CLEAR
LINE command above. you must select either ALL or COUNTER TIMER (as
indicated by the braces). whereas you can select one or more of the parameters
for CLEAR EXECUTOR. On many of the SHOW and LIST commands. you
do not have to specify any parameters because there is a default. The system
will prompt you if you omit a required parameter.
1.4.2 Issuing Commands

Enter the command keywords separated by spaces.
Continuing a command. To continue a long command to the next line, insert
a hyphen (-) where you wish to break the line; then enter <RET). You can
continue the command following the prompt on the next line.
Example:

CFE>DEFINE LINE DZ-1-2 DUPLEX FULL SPEED 9600 -<RET>
CFE>VECTOR 360 CSR 160120 <RET>
CFE>
Any necessary spaces in the command must be entered even if one occurs
just before the hyphen.
Abbreviating command keywords. When entering a command. you can
abbreviate any keyword to the first three or more unique characters. For
example, the following two versions of the same command are equally valid:
NCP>~HOW

MODULE X25-ACCESS ALL DESTINATIONS CHARACTERISTICS

NCP>SHO MOD X25-A ALL DES CHA
Note that X25-ACCESS is abbreviated to the first five unique characters to
differentiate it from other entities beginning with the X25~ character string.
For clarity and consistency, all examples in this manual show the full command
syntax.
Entering comment lines. You can enter comment lines by prefacing each line
of text with a semicolon (;).

Network Management Utilities (CFE, NCP, VNP)

1·7

1.4.3 Using the Help Facility

Use the HELP command whenever you need assistance in selecting network
management commands and parameter options. Execution of this command by
any of the three utilities causes a summary of help text to be displayed.
Example:

>NCP
NCP> HELP
Use the HELP keyword with a selected command and/or component to display
the portion of the help file relevant to that command.
Example:

>NCP
NCP>HELP LINE
1.4.4 Command Prompting

Command prompting provides additional assistance when using network
management commands. At any point where you can type a space, type <RET)
instead. This produces a prompt requesting the required information. If you
need additional information after a prompt, you can type <ESC> to display
additional help information.
Example:

NCP>SET <RET>
Set component: <ESC>
Options are:
ALIAS
CIRCUIT
EXECUTOR

1-8

KNOWN CIRCUITS
KNOWN LINES
LINE

LOGGING
NODE
OBJECT

PROCESS
SYSTEM

DECnet-RSX Guide to Network Management Utilities

1.4.5 Using the LIST and SHOW Commands

NCP. CFE. and VNP provide commands that enable you to display information
about network components on your terminal. NCP provides the additional
capability to send display information to a file.
For more information about the SHOW and LfST commands and examples
of the type of information displayed by these commands. see the DECnet-RSX
Netll'Ork l\'lanagement Concepts and Procedures manual.
1.4.6 Exit Status and Error Handling

When CFE. NCP. or VNP terminates, it sets a bit that can be inspected using
the normal RSX exit status handling techniques described in
RSX-IIM/M-PLUS operating system documentation. The utility sets the exit
status to indicate the worst case for the commands executed. The exit status
is especially useful when used in conjunction with the indirect command file
processor's support of this operating system feature. The possible values and
their meanings are summarized below.
Status

Numeric
Value

Meaning

Success

The command executed as requested.

Warning

Minor error. Processing continues.

Error

The command was accepted. but failed to
execute completely. The system waits for a
new command.

Severe Error

The command was not accepted. Processing
stops and control returns to the monitor.
NOTE

The following NCP commands do not affect the exit status:
CLEAR EXECUTOR NODE
EXIT (or (CTRL/Z»
HELP
SET EXECUTOR NODE

Network Management Utilities (CFE, NCP, VNP)

1-9

If the command executes successfully. you receive the utility prompt on the
next line. whereupon you can issue another command. If the command is
unsuccessful. you receive an error message on the next line indicating the
reason for the error. followed by the utility prompt.

Example:

MCR>NCP
NCP>SET LINE DMC-O TOP
NCP>LOAD NODE XYZ
lICP -- Load failed, line communication error
NCP>
Error messages for all three utilities are provided in Chapter 10.

1.5 Command Descriptions
The rest of this chapter is devoted to descriptions of the individual commands
and their parameters. If you need more information on the command
components or their parameters. refer to the DECnet-RSX Network
Management Concepts and Procedures for a more in-depth discussion.
Commands are presented in alphabetical order. The command name and the
utility (or utilities) to which it applies are printed at the top of the page
(many NCP and VNP commands have the same format and are described
together). The full DECnet-RSX-ll1'I1M-PLUS set is described first. The
RSX-llS subset is described at the end of the chapter (NePfS appears at the
top of those pages). All commands are designated as privileged (P) or
nonprivileged (NP) at the top of the page next to the command name. On
combined NCPfVNP commands. an NP designator applies to NCP commands
only. as all VNP commands are privileged.
1.5.1 Graphic Conventions

Review the graphic conventions outlined at the front of this manual. especially
the usage of braces and brackets [ ].
indicates commands or
parameters that are valid for PSI users only.

1-10

DECnet-RSX Guide to Network Management Utilities

1.5.2 Standard Definitions

The following parameters and user-supplied variables are frequently used in
the command descriptions. They are described here to avoid needless repetition.
Exceptions to these definitions are indicated in individual parameter
descriptions. More information about most of these parameters can be found
in the DECnet-RSX Network Management Concepts and Procedures manual.
ace-eon-info

Access control information in one of the following
forms:
luser-id[/password[laccollllt ]]

USER llser-id
account]]
~OTE:

[PASS\VORD

password

[ACCOUNT

DECnet-RSX does not use the account field.

alias-name

An alternative name for a network node. 1 to 6
alphanumeric characters including at least 1 alphabetic
character.

area-flumber

A decimal integer in the range of 1 to 63.

circuit-id

A DECnet circuit identification in the form dev-e[-u][.t]
or a PSI circuit identification consisting of 1 to 6
alphanumeric characters.

csr-address

CSR address in the range of 160000 to 177774 (octal).

dest-name

An X.25 destination name consisting of
alphanumeric characters.

dte-address

A string of 1 to 15 decimal digits forming a DTE
address.

E-address

An Ethernet address consisting of a string of 12
hexadecimal digits in the form nll-Ilfl-nn-nn-nn-nn.

Network Management Utilities (CFE, NCP, VNP)

1 to 6

1-11

eLlent-list

A list of events that belong to the same class. such
as. euent-class.type.

/'ile

A file specification. which is interpreted according to
the executor node's file system. The standard format
for RSX is dev:[uicl{ilellame.type:L'er.

group-name

An X.25 group name consisting of 1 to 6 alphanumeric
characters.

line-id

A line identification in the form dec-c[-uj.

node-address

An area-number followed by a period and a decimal
integer in the range of 1 to 1023. When referring to
the local area, the area number and period are optional.

node-id

A node name (see node-name) or node address (see
node-address).

node-name

1 to 6 alphanumeric characters. including at least 1
alphabetic character.

obiect-id

An RSX task name (1 to 6 alphanumeric characters)
or an object type code (see type-code).

selTice-paSSlOord

A hexadecimal number used as a password for certain
service requests. For DDCMP circuits, it is in the range
of 0 to FFFFFFFF; for Ethernet circuits. it is in the
range of a to FFFFFFFFFFFFFFFF (up to 16
hexadecimal digits).

process-name

A name of a DECnet-RSX process. The process name
is 1 to 3 characters in length. For a list of valid process
names. see Appendix A.

range

A subaddress range consisting of one or two 1- to
4-digit integers in the range of a to 9999. [f you specify
two subaddresses, they must be separated by a hyphen
(-). and the second must be greater than the first (e.g ..
10-100). See PSI iVetwork-speci/'ic Information for the
maximum length of a subaddress on your network.

1·12

DECnet-RSX Guide to Network Management Utilities

type-code

An object typP code in the range of 1 to 255. Use an
from Appendix B.

oblt:'ct t~:pf-' c()de
uector-add,.es~

,-\ vP<..'t III

CHARACTE R 1ST I C~

([)pf<Wll

COUNTERS

(.\ C P only) Displays error and performance statistics
for the specified component.

STATUS

(~CP only) Displays dynamic
specified component.

SUMMARY

(Default for VNP and NCP. invalid for CFE) Displays
only the most useful information for the specified
component.

SCOPE scope

(Valid for privileged users only) Qualifies the extent to
which the specified operation applies (default:
requestor's terminal). Possible values for scope are:

ldd rt~qc:; in the range of 0 to 774 (octal).

tor (' FE) Displays static information for the
c;;peCl t'ied component. ThIs type of information is
automatically dIsplayed for all CFE LIST commands.

GLOBAL

information for

the

The operation applies to all terminals.

TERMIN AL The operation applies to the specified
term-id termInal only. where term-id is a
standard RSX terminal device
identificatlOn.
TO file

(Valid for NCP only) Directs output to the specified
file or device at the local node (default: information
displayed at the calling terminal). If you specify an
existing file as output. the information is appended to
that file. Information is transferred in ASCII in the
same format as it is displayed at the terminal. (See the
description of file. above. for format.)

1.5.3 RSX·11 M/M-PLUS CFE, NCP, and VNP Command Summary
This section describes all of the CFE and NCP commands supported by
RSX-IIM/M-PLUS. VNP commands are described in tandem with the
corresponding NCP command. RSX-IIS NCP commands are described in
Section 1.4.5.
Network Management Utilities (CFE, NCP, VNP)

1-13

NCP/VNP
NP
CLEAR ALIAS

Use the NCP CLEAR ALIAS command to remove the specified alias nodt:
name(s) from the volatile database. Use the VNP command to do the same
with the system image file.
Format:

CLEAR

ALL ALIASES ~

[ [SCOPE] scope]

AL I AS alias-name
KNOWN ALIASES

where
ALL ALIASES

(Valid for privileged users only) Removes all alias names.

ALIAS
alias-name

Removes only the specified alias name.

KNOWN
ALIASES

Removes all alias names for the specified scope.

SCOPE scope

(Invalid for ALL ALIASES) See definition in Section
l.5.2.

Example:

NCP>CLEAR ALIAS NY5 SCOPE TERMINAL TT2:
This command removes the association of alias NY5 with terminal TT2:.

1·14

DECnet-RSX Guide to Network Management Utilities

NCP

P
CLEAR CIRCUIT

Use the CLEAR CIRCCIT command to zero the specified PSI circuit counter
timer(s) in the volatile database.
Format:

where
CIRCUIT
circllit-id

Zeroes the counter timer for the specified circuit
only.

KNOWN
CIRCUITS

Zeroes the counter timers for all known circuits.

Example:

NCP>CLEAR CIRCUIT PVC1 COUNTER TIMER
This command zeroes the counter timer for PSI circuit PVCl.

Network Management Utilities (CFE, NCP, VNP)

1·15

NCP/VNP

p
CLEAR EXECUTOR

Use the )JCP cr EAR EXECUTUR command to remove specified executor
node parameters trom the volatile database. Use the V~P command to do the
same with the system image file.
Format:

CLEAR EXECUTOR

HOST
RECEIVE PASSWORD
TRANSMIT PASSWORD

where
HOST

Removes identification of the host for the executor node.
The executor then defaults to itself as host for service
operations.

RECEIVE

Removes the executor node's receive password.

PASSWORD

TRANSMIT

Removes the executor node's transmit password.

PASSWORD
Example:

NCP>CLEAR EXECUTOR RECEIVE PASSWORD
This command removes the receive password.

1·16

DECnet-RSX Guide to Network Management Utilities

NCP
NP
CLEAR EXECUTOR
NODE

Use the CLEAR EXECCTOR ~ODE command to return NCP command
execution to the local node after issuing an NCP SET EXECFTOR NODE
command.
Restriction:

You cannot use the TELL prefix with this command.
Format:

CLEAR EXECUTOR NODE
Example:

NCP>SET EXECUTOR NODE BOS

NCP>CLEAR EXECUTOR NODE
The first command causes subsequent NCP commands to be executed at node
BOS. The second command returns NCP command execution to the local node.

Network Management Utilities (CFE, NCP, VNP)

1·17

NCP/VNP
P

CLEAR LINE

Use the NCP CLEAR LINE command to unload the specified line(s) and to
remove all associated parameters from the volatile database. Use the VNP
command to do the same with the system image file. You can also use the
NCP command to zero the counter timer(s) for the specified PSI line(s).
Restriction:

Before you unload a D ECnet line. all circuits associated with the line must
be in the OFF state (see SET CIRCUIT). Any PSI line to be unloaded must
also be in the OFF state (see SET LINE and SET KNOWN LINES).
Format:

where
LINE
line-id

Clears the specified line only.

KNOWN
LINES

Clears all known lines.

ALL

Unloads the specified line(s) and removes all associated
line parameters.

COUNTER
TIMER

(Invalid for VNP) Zeroes the counter timer(s) for
the specified PSI line(s).

Examples:

NCP>CLEAR LINE DMC-O ALL
This command unloads DECnet line DMC-O and removes all parameters
associated with it. thus making DMC-O unusable.

NCP>CLEAR LINE SDP-l COUNTER TIMER
This command zeroes the counter timer for PSI line SDP-l.

1·18

DECnet-RSX Guide to Network Management Utilities

NCP/VNP

P
CLEAR LOGGING

Use the NCP CLEAR L()(i(;I\(; command to remove logging parameters
from the volatile databa~t' l <"'t· lht-~ V\ P command to do the "a~e with the
system image file.
Restriction:

\Nhenever a circuit. line. module. node. or sink is specified in a CLEAR
LOGG I~G command. an event list or KNOWN EVENTS parameter must also
be included.
Format:

CLEAR {KNOWN LOGGING }
LOGGING CONSOLE
LOGGING FILE
LOGGING MONITOR

[NAME]
EVENTS ecellt-list
KNOWN EVENTS

EXECUTOR
}
NODE {lOde-id}
$HOST

where
KNOWN
LOGGING

Removes parameters for aU known logging
components.

LOGGING
CONSOLE

Removes parameters for console logging
component.

LOGGING
FILE

Removes parameters for the file logging
component.

LOGGING
MONITOR

Removes parameters for the moni tor logging
component.

NAME

Returns the specified logging component to its default
name (console: COO:; file: LB:[1.6jEVENTLOG.SYS;
monitor: MON ... ).

_ Network Management Utilities (CFE, NCP, VNP)

1-19

EVEi'ITS
event-list

111 <?L'eflt-li<;t

KNOWN
EVENTS

Removes all known events that DECnet-RSX can
gt:>neratp for the ",pecified component.

CIRCUIT
circuit-id

(Invalid for V~P) Inhibits event logging for the
specified CIrcuit (see restriction).

LINE
line-id

Inhibits event logging for the specified line (see
restriction).

MODCLE

(Invalid for VNP) Inhibits event logging for the specified
module (see restriction).

)JODE
node-id

Inhibits event logging for the specified node
(see restriction).

SINK

Inhibits logging of the specified event(s) at the specified
node (see restriction).

1-20

Removes the event dass and type(s) specified
for the specified component.

EXECUTOR

(Default) Events are not to be
logged at the executor node.

NODE node-id

Events are not to be logged at the
specified node.

NODE $HOST

(Invalid for NCP) Events are not
to be logged at the host node.

DECnet-RSX Guide to Network Management Utilities

Examples:

NCP>CLEAR LOGGING CONSOLE EVENT 2 1
This command ct'ase~ logging of ('vent 2.1 to the console.

NCP>SET LOGGING CONSOLE EVENT 2.1 SINK NODE PHL
NCP>SET LOGGING CONSOLE UAME TTl: EVENT 2.1 STATE ON

UCP>CLEAR LOGGING CONSOLE EVENT 2.1 SINK NODE PHL
The first command in this example causes access control rejection events (2.1)
to be logged on the console on node PHL. The second command enables
logging of 2.1 events to TTl: on the local node. The third command reverts
event logging to the local node only. and 2.1 events are no longer logged to
the console on node PHL.

Network Management Utilities (CFE, NCP, VNP)

1·21

NCP

p
CLEAR MODULE
X25-ACCESS

Use the CLEAR \-IODCLE X~5-ACCESS eommand to remove destination
names from 'the volatile dat~lbase.
Format:

where

ALL
DESTINATIONS

Removes all destination names. regardless of
scope.

DESTINATION
dest-name

Removes only the specified destination name.

KNOWN
DESTINATIONS

Removes all destination names for the specified
scope.

SCOPE scope

See definition in Section 1.5.2.

Examples:

NCP>CLEAR MODULE X25-ACCESS ALL DESTINATIONS
This command removes all destination names.

NCP>CLEAR MODULE X25-ACCESS DESTINATION CUGlll TERMINAL TT2:
This command removes destination name CUG III associated with terminal
TT2:.

1·22

DECnet-RSX Guide to Network Management Utilities

NCP

P
CLEAR MODULE
X25-PROTOCOL

Use the CLEAR L\10DCLE X25-PROTOCOL command to zero the counter
timer(s) for the specified DTE(s) or to remove from the volatile database all
parameters for the specified DTE(s) or group(s).
Format:

where
DTE

dte-address Clears the specified DTE only.

KNOWN DTES

Clears all known DTEs.

GROUP
group-name

Removes parameters for the specified group only.

KNOWN
GROUPS

Removes parameters for all known groups.

ALL

Removes all parameters for the specified DTE(s) or
group(s).

COUNTER
TIMER

Zeroes the counter timer(s) for the specified
DTE(s).

Examples:

NCP>CLEAR MODULE X25-PROTOCOL DTE 123456789 COUNTER TIMER
This command zeroes the counter timer for local DTE 123456789.

NCP>CLEAR MODULE X25-PROTOCOL KNOWN GROUPS ALL
This command removes parameters for all known groups.

Network Management Utilities (CFE, NCP, VNP)

1-23

NCP

P
CLEAR MODULE
X25-SERVER
CLEAR MODULE
X29-SERVER

Use the CLEAR MODeLE X25/X29-SERVER commands to zero the counter
timer or to remove the specified destination name(s) and all associated
parameters from the volatile database.
Format:

where
COUNTER
TI)\'IER

Zeroes the server module counter timer.

DESTINATION
dest-name

Removes parameters for the specified
destination only.

KNOWN
DESTINATIONS

Removes parameters for all known destinations.

Example:

NCP>CLEAR MODULE X25-SERVER DESTINATION CHI205 ALL
This command removes all parameters for destination CHI205.

1-24

DECnet-RSX Guide to Network Management Utilities

NCP/VNP

P
CLEAR NODE

Use the CLEAR ~ODE command to remove specified node parameters from
the volatile database on the local node. C se the VN P command to do the
same with the system image file.
Restriction:

NAME is the only valid parameter for VNP.
Format:

CLEAR

NODE node-id

ALL
CIRCUIT
DIAGNOSTIC FILE
DUMP ADDRESS
DUMP COUNT
DUMP FILE
HARDWARE ADDRESS
HOST
LOAD FILE
NAME
SECONDARY LOADER
SERVICE CIRCUIT
SERVICE DEVICE
SERVICE PASSWORD
TERTIARY LOADER

where

NOD E node-id

ALL

Specifies the node whose parameters are to be
removed. You must use a node name if you are
removing the circuit identification (see CIRCUIT
parameter below).
Removes all parameters for the specified node.
If you specify ALL. you cannot include any other

parameters.

Network Management Utilities (CFE, NCP, VNP)

1-25

CIRCUIT

Removes the circUIt identification associated with
the node name for node level loopback testing.

DIAGNOSTIC FILE

Removes the identification of the down-line load
diagnostics file.

DUMP ADDRESS

Removes the node's up-line dump address.

DUMP COUNT

Removes the up-line dump count.

DUMP FILE

Removes the up-line dump file identification.

HARDWARE ADDRESS

Removes the Ethernet address of the system
hardware.

HOST

Removes the host node identification.

LOAD FILE

Removes the down-line load file identification.

NAME

Removes the node name associated with the
specified node.

~ODE

CIRCUIT

Clears the assignment of a node id to a circuit
used for loopback testing. This command does
not apply to Ethernet nodes.

SECONDARY LOADER

Removes the parameter associated with the file
containing secondary loader software for
down-line loading to the node.

SERVICE CIRCUIT

Removes the circuit parameter associated with
the node for down-line load operations.

1·26

DECnet-RSX Guide to Network Management Utilities

SERVICE DEVICE

Removes the service device type.

SERVICE PASSWORD

Removes the password parameter required to
trigger the bootstrap mechanism.

TERTIARY LOADER

Removes the parameter associated wi th the file
containing tertiary loader software for down-line
loading to the node.

Example:

NCP>CLEAR NODE BOS ALL
This command removes all information for the node BOS from the volatile
database.

Network Management Utilities (CFE, NCP. VNP)

1·27

NCP/VNP

P
CLEAR OBJECT

Use the ~CP CLEAR OBJECT command to remove all object parameters
from the volatile database. Use the VNP command to do the same with the
system image file.
Format:

CLEAR

OBJECT type-COde}
"lKNOWN OBJECTS

ALL

where
OBJECT
type-code

Removes parameters for the specified object only.

KNOWN
OBJECTS

Removes parameters for all known objects.

ALL

(Required for NCP; optional for VNP) Specifies that all
parameters are to be removed.

Example:

NCP>CLEAR OBJECT 245 ALL
This command removes all parameters for object 245.

1-28

DECnet-RSX Guide to Network Management Utilities

NCP/VNP

p
CLEAR PROCESS

Use the NCP CLEAR PROCESS command to unload a process and remove
all process parameters from the volatile database. Use the VNP command to
do the same with the system image file.
Restrictions:

• You can unload a process only when it is not being used.
• If you clear NW from the volatile database and then reload it using NCP
SET PROCESS. you must also issue the SET MODULE X25-PROTOCOL
command (first with STATE OFF and then with STATE ON) to update the
process pointers to the database.
Format:

CLEAR PROCESS process-name

where
PROCESS
process-name

Specifies the process to unload.

Example:

NCP>CLEAR PROCESS DLX
This command unloads the D LX process and removes all parameters associated
with it.

Network Management Utilities (CFE, NCP, VNP)

1-29

NCP/VNP

P
CLEAR SYSTEM

Use the NCP CLEAR SYSTEM command to unload the Communications
Executive, release any resources being used by the network, and remove all
system parameters from the volatile database. Use the VNP command to
unload the Communications Executive in the system image file.
Restrictions:

• You cannot use the TELL prefix with this command.
• Before you issue NCP CLEAR SYSTEM, the executor must be in the OFF
state (see NCP SET EXECUTOR).
• If you are running PSI. the X.25 server module must be in the OFF state

(see SET MODULE X25-SERVER).
Format:

CLEAR SYSTEM

1·30

DECnet-RSX Guide to Network Management Utilities

NCP

P
CLEAR TRACE

Use the CLEAR TRACE command to stop tracing of PSI frames on the
specified line(s). For more information on the trace interpreter task. see Chapter
9.
Format:

CLEAR TRACE JL I NE line-id
}
lACTIVE LINES
where

LINE line-id

Disables tracing on the specified line only.

ACTIVE LINES

Disables tracing on all active lines.

Example:

NCP>CLEAR TRACE LINE SDP-O
This command disables tracing of PSI frames on line SDP-O.

Network Management Utilities (CFE. NCP. VNP)

1-31

CFE
p

DEFINE CIRCUIT

Use the DEFINE CIRCUIT command to modify circuit parameters in the
permanent database. You can also use this command to create parameters for
PVCs.
Restriction:

The values used for MAXIlVIUM DATA and l\IAXIMU1VI WINDOW must be
the same as the packet size and window size agreed upon by the network
authorities for the PVC.
Format:

DEFINEfcI RCUIT Circuit-id}
LKNOWN CIRCUITS

COST cost

HELLO T I MER seconds
MAXIMUM ROUTERS number

ROUTER PR I OR I TY }riorit y
SERVICE }DISABLE
.
lENABLE

STATE {;~F}

trib-ad

where

CIRCUIT
circuit-id

1-32

Modifies or creates parameters for the specified
circuit only.

DECnet-RSX Guide to Network Management Utilities

KNOWN
CIRCUITS

.1'Iodifie . . (or creates) parameters for all known
circUIts.

CHANNEL
channel-number

(DECnet DLM and PSI circuits only) Specifies the
logical channel number for a PVC (range. 0 to 4095).

COST cost

(DECnet circuits only) Specifies the routing cost of the
circuit. ~fessages will travel between nodes along the
path with the smallest total cost (range: 1 to 25; default:
varies according to circuit type).

COUNTER
TIMER
seconds

(PSI circuits only) Sets a timer whose expiration
causes the circuit counters to be logged and
zeroed (range: 0 to 65,535).

DTE
dte-address

(DECnet DLM and PSI circuits only) Specifies a
local DTE for a PVC.

HELLO TIMER
seconds

(DECnet circuits only) Specifies the frequency
of routing hello messages sent to an adjacent node on
the circuit (range: 1 to 8191).

1fAXIMUM
ROUTERS
number

(DECnet Ethernet circuits only) Specifies the
maximum number of routing nodes that an Ethernet
circuit can maintain (range: 0 to 32; default: 5).

MAXIMUM
DATA
byte-count

(DECnet DLM and PSI circuits only) Specifies the
maximum packet size for a PVC. For DLM SVCs, this
parameter specifies the maximum packet size to be
negotiated with the network, if allowed. This parameter
value must be at least 5 bytes less than the maximum
data size specified for PSI lines (see DEFINE LINE).
By default, packet size takes the network value specified
by the MAXIMUM DATA parameter in the DEFINE
MODULE X25-PROTOCOL command. See PSI
Network-specific Information for the network value of
this parameter (range: 16 to 4054).

Network Management Utilities (CFE, NCP, VNP)

1·33

MAXIMUM
RECALLS
retry-count

(DEC'net DL~1 circuits only) Specifies the maximum
number of times that D ECnet should attempt to
place a call to establish an SVC (range: 0 to 255; default:
5).

MAXIMU~1

WINDOW
block-count

(DECnet DLM and PSI circuits only) Specifies the
maximum number of blocks allowed to be
outstanding on the circuit for PSI PVCs. For DLM SVCs.
this specifies the maximum number of outstanding blocks
to be negotiated with the network. if allowed. By default.
window size takes the network value specified by the
~IAXIMUM WINDOW parameter in the DEFINE
~10DULE X25-PROTOCOL command. See RSX-l1 PSI
Network-specific Information for the network value of
this parameter (range: 1 to 7).

MULTIPOINT
ACTIVE
active-ratio

(DECnet non-DMP/DMV multipoint control circuits
only) Specifies the rate at which a tributary in
the active multipoint state is polled (range: 1 to 255).

NUMBER
dte-address

(DECnet DLM circuits only) For outgoing calls:
specifies a remote DTE address used by DECnet when
trying to establish an SVC. For incoming calls: specifies
the address the incoming call request must have in order
for DECnet to establish the SVC. An alternate method
is to use the SUBADDRESSES parameter of the
DEFINE EXECUTOR command (if the network supports
subaddresses).

RECALL TIMER
seconds

(DECnet DLM circuits only) Sets the interval to
wait after a failed call before attempting to place another
call to establish an SVC (range: 0 to 65535; default: 30).

ROUTER
PRIORITY
priority

(DECnet Ethernet circuits only) Specifies the
priority that the executor node on this
circuit is to have in selecting a designated router for the
circuit (range: 0 to 255; default: 64).

1·34

DECnet-RSX Guide to Network Management Utilities

SERVICE

(DEener cIrcuits only) Specifies whether the circuit is
enabled or disabled for down-line loading and loop back
testing.

STATE

Sets the circuit's operational state.
OFF

The circuit IS not available for use.

The circuit is available for normal use. For
circui ts owned by the executor. the state of
the corresponding line(s) must be ON.

TRIBUTARY
trib-address

(DECnet multipoint circuits only) Specifies
the data link physical address of the multipoint circuit
(range: 1 to 255).

USAGE

(DECnet DLIVI circuits only) Specifies the availability of
a DLM SVC for either incoming or outgoing switched
calls (default: incoming).

Examples:

CFE>DEFINE CIRCUIT DZ-3 STATE OFF
This command makes circuit DZ-3 unavailable for use.

CFE>DEFINE KNOWN CIRCUITS MAXIMUM RECALLS 10
This command sets to 10 the maximum number of times DECnet should
attempt to place a call on all known circuits.

Network Management Utilities (CFE. NCP, VNP)

1-35

CFE

p
DEFINE EXECUTOR

Use the DEFINE EXECUTOR command to modify executor node parameters
in the permanent database.
Format:

DEFINE EXECUTOR

ADDRESS node-address
AREA MAXIMUM COST number
AREA MAXIMUM HOPS number
BROADCAST ROUT I NG T I MER seconds
HOST node-address
I DENT I F I CAT I ON id-string
INACTIVITY TIMER seconds
INCOMING TIMER seconds
MAX I MUM ADDRESS node-address
MAXIMUM AREAS number
MAXIMUM BROADCAST NONROUTERS number
MAXIMUM COST number
MAX I MUM HOPS number
MAXIMUM LINKS number
MAXIMUM NODE COUNTERS number
NAME node-name
OUTGO I NG T I MER seconds
RETRANSMIT FACTOR number
ROUTING TIMER seconds
SEGMENT BUFFER SIZE number

STATEl{g~F}
where
ADDRESS
node-address

Specifies the address of the executor node.

AREA MAXIMUM
COST
number

Specifies the total path cost allowed to any
remote area (range: 1 to 1022; default: 1022).

1-36

DECnet-RSX Guide to Network Management Utilities

AREA MAXIMU~1
HOPS
number

Specifies the maximum number of routing
hops allowed to any remote area (range: 1 to 30;
default: 10).

BROADCAST
ROUTING
TIMER
seconds

Sets a timer whose expiration forces a routing
update on Ethernet circuits. which produces a
routing configuration message for each adjacent
node (range: 1 to 65535; default: 30)

HOST
node-address

Specifies the host node address for down-line
load. trigger. and up-line dump operations.

IDENTIFICATION
id-string

Specifies the text identification string
for the execl;ltor node (range: 1 to 32 characters).
You must use quotation marks (") to delimit any
string containing blanks or tabs. To indicate a
quotation mark within a quoted string. use a double
quotation mark (to distinguish it from a string
delimiter).

INACTIVITY
TIMER
seconds

Specifies the maximum time the executor will
allow a link to remain idle (no user data traffic)
before it checks to see if the circuit still works (range:
1 to 255).

INCOMING
TIMER
seconds

Specifies the maximum time a process has to
answer an incoming connect request. If the
process does not answer the connect request within
this time interval, the node will reject the connect
request on behalf of the process (range: 1 to 255).

MAXIMUl\1
ADDRESS
node-address

Specifies the maximum node address of the executor
or any remote node known to the executor (range:
1 to 1023).

MAXIMUM
BROADCAST
NONROUTERS
number

Specifies the maximum number of nonrouting nodes
that the executor node can have on all its
Ethernet circuits (range: 1 to 1022;
default: 64).

Network Management Utilities (CFE, NCP. VNP)

1-37

MAXIMUM AREAS
area-number

Specifie~ the maximum area number of the executor
or any remote area known to the executor (range: 1
to 64).

MAXIMU:\tl COST
number

Specifies the maximum total path cost allowed
to any node (range: 1 to 1022; default: 1022).

l\IAXIMUM HOPS
number

Specifies the maximum number of routing hops
allowed from the executor node to any other node
(range: 1 to 30; default: 10).

JVIAXIMUM LINKS
number

Specifies the maximum number of active logical
links for the executor node (range: 1 to 255).

MAXIMUM NODE
COUNTERS
number

Specifies the maximum number of node counters
allowed. If you require more counters, the
existing ones are reassigned on demand in the same
order as they were originally assigned. Use a decimal
integer greater than 1, but not exceeding the executor
maximum address (range: 1 to 170).

N Al\'lE node-name

Specifies the node name of the executor.

OUTGOING
TIMER
seconds

Specifies the maximum time the executor node will
wait for a pending connect request to be answered
at a destination node. If the request is not answered
in this time interval, the source process receives an
error indication (range: 1 to 255).

RETRANSMIT
FACTOR
number

Specifies the number of times the executor will
restart the retransmission timer before the
logical link is disconnected (range: 1 to 255).

ROUTING TIMER
seconds

Sets a timer whose expiration forces a routing
update on non-Ethernet circuits (range: 1 to 65.535).

1-38

DECnet-RSX Guide to Network Management Utilities

SEGMENT BUFFER
SIZE number

Specifies the maximum size of transmit buffers (in
bytes). thereby controlling the size of the NSP
message segment to be sent. This value is the
maximum SIze message that the End
Communications layer can transmit; it does not
include routing or data link overhead (range: 1 to
4096: default: 18 bytes less than the large buffer
size specified in the DEFINE SYSTEIVr command).
The segment buffer size can never be greater than
the large buffer size minus 18 bytes.

SUBADDRESSES
range

Specifies a range of local DTE subaddresses that
are valid on any PSI circuit for incoming calls to
the executor node.

VERIFICA TION
STATE

Sets the logical link access control verification
state for the executor node.
OFF

The executor node does not verify
access control on any incoming
requests.

ON (Default)

The executor node verifies access
control on all incoming conne'ct
requests according to the opt~ons set
for each object (see the discussion of
access control in the DECnet-RSX
Network Management Concepts and
Procedures manual).

Examples:

CFE>DEFINE EXECUTOR ADDRESS 21
This command sets the executor address to 21.

CFE>DEFINE EXECUTOR MAXIMUM LINKS 20
This command sets the maximum number of active logical links to 20.

Network Management Utilities (CFE. NCP, VNP)

1·39

CFE

DEFINE LINE

Use the DEFINE LINE command to modify line parameters in the permanent
database.
Format:

DEFINE JLINE line-id }
lKNOWN LINES

[CONTROLLER]
CONTROLLER

DUPLEX

MULT I PO I NT DEAD, dead-ratio
PR I OR I TY hardware-priority
SPEED baud-rate
STATE {CLEARED}
OFF
ON
UNIT CSR csr-address
VECTOR vector-address

where
LINE line-id

Modifies parameters for the specified line only.

KNOWN LINES

Indicates that parameters for all known lines are to be
modified.

CONTROLLER
CSR csr-address

Specifies the address of the first CSR for the
line controller.

1-40

DECnet-RSX Guide to Network Management Utilities

CONTROLLER

(For Ethernet. Dl\tIC/DMR. DMP. DHU. and DHV lines)
Specifies the controller mode for the line.
LOOPBACK

Internal device loopback mode .

.\iOR:\IAL

Normal operating mode.

COUNTER
TIMER
seconds

(PSI lines only) Sets a timer whose expiration
causes the line counters to be logged and zeroed
(range: 0 to 65.535)

DUPLEX

(DECnet DDCMP lines only) Sets the hardware
transmission mode to full duplex or half duplex.

HOLDBACK

(PSI lines only) Specifies the length of time
that a message acknowledgment can be held back in
order to be included with another data message (range:
o to 65.535).

TI~IER

milliseconds

.MAXIMUM
DATA
byte-count

(PSI lines only) Specifies the maximum frame size
(in bytes) for the line. This value must be at
least 5 bytes larger than the maximum data size specified
for PSI circuits (see the DEFINE MODULE
X25-PROTOCOL command) (range: 21 to 1029).

MAXIMUM
RETRANSMITS
retry-count

(PSI lines only) Specifies the maximum number of
retransmissions of a frame over the specified
line (range: 0 to 255).

MAXIMUlVI
WINDOW
block-count

(PSI lines only) Specifies the maximum number of
frames for which outstanding PSI acknowledgment
messages are allowed (range: 1 to 7).

Network Management Utilities (CFE. NCP, VNP)

1·41

~lUL TIPOINT

DEAD
dead-ratio

(DECnet non-DlVIP/DMV multipoint lines only)
Specifies the polling rate for a tributary in the
dead multipoint state (range: 1 to 255).

PRIORITY
hardware-priority

Specifies the hardware priority of the controller
(range: 4 to 7).

RETRANSl\IIT
TIMER
milliseconds

(PSI lines only) Specifies the time to elapse
before a block is retransmitted.
CFE rounds off all values within this range to the nearest
hundred milliseconds (range: 1 to 10.049).

SPEED baud-rate

Sets the line baud rate to one of the following:
50
75
110
134
150

300
600
1200
1800
2000

2400
3600
4800
7200
9600

To set a high speed device (that is. over 9600 baud).
enter 9600 or the actual baud rate.
STATE

1·42

Sets the line's operational state when the system is
loaded.
CLEARED

The line is not loaded. A DDCMP
controller line may not be set to
CLEARED if any circuits on it are in
the ON state.

OFF

The line is loaded. but not available for
use. A DDCMP controller line may not
be set to OFF if any circuits on it are
in the ON state.

The line is loaded and available for
normal use except during temporary
overrides for service operations. All
PSI lines are set to ON. If the line is
a DDCMP point-to-point line or a
DDCMP tributary. the corresponding
circuit is also set to ON.

DECnet-RSX Guide to Network Management Utilities

UNIT CSR
csr-address

Specifies the address of the first CSR for a
DECnet device controlled by a Kl\t1C-ll.
NOTE

With the KDP. a unit CSR can be specified for any unit on
the controller.
With the KDZ. a unit CSR can be specified only for the first
unit set in the associated DZ multiplex group.
VECTOR
vector-address

Specifies the vector address of the line
controller.

Examples:

CFE>DEFINE KNOWN LINES MAXIMUM DATA 256
This command establishes the maximum frame size for all known lines as 256
bytes.

CFE>DEFINE LINE DZ-3-0 SPEED 3600
This command sets the baud rate of line DZ-3-0 at 3600.

Network Management Utilities (CFE, NCP, VNP)

1·43

CFE
p

DEFINE LOGGING

Use the DEFINE LOGG I~G command to create or modify logging parameters
in the permanent database
Format:

DEFINE

where

NOWN LOGG I NG }
LOGGING CONSOLE
LOGGING FILE
LOGGING MONITOR

rEVENTS event-list]
LKNOWN EVENTS

[STATE {g~F} ]

KNOWN
LOGGING

Indicates that the specified parameters are to be
created or modified for all known logging components.

LOGGING
CONSOLE

Indicates that the specified parameters are to be
created or modified for the console logging component.

LOGGING
FILE

Indicates that the specified parameters are to be
created or modified for the file logging component.

LOGGING
MONITOR

Indicates that the specified parameters are to be
created or modified for the monitor logging component.

EVENTS
event-list

Specifies the event class and type(s) to be
logged.

1·44

DECnet-RSX Guide to Network Management Utilities

KNOWN
EVENTS

Specifies that all events that DECnet-RSX can
generate are to be logged.

STATE

Sets the operational state of the logging component when
the system is loaded.

OFF

The logging component is disabled and
events for that component are
discarded.

The logging component is enabled and
events for that component are sent to
a name currently defined for that
component.

Example:

CFE>'DEFINE LOGGING MONITOR STATE ON
This command changes the state of the logging monitor to ON.

Network Management Utilities (CFE, NCP, VNP)

1-45

CFE
p

DEFINE MODULE
X2S-ACCESS

Use the DEFINE LVIODCLE X25-ACCESS command to specify a destination
name for a remote DTE in the permanent database. Destinations defined in
the permanent database apply to all terminals.
Format:

where
DESTINATION
dest-name

Specifies a destination name for the identified
remote DTE address.

NUMBER
dte-address

Specifies the remote DTE address to be associated
with the specified destination name.

Example:

CFE>DEFINE MODULE X25-ACCESS DESTINATION PRS44 NUMBER 219746
This command establishes remote DTE 219746 as having the name PRS44.

1-46

DECnet-RSX Guide to Network Management Utilities

CFE

p
DEFINE MODULE
X25-PROTOCOL

Use the DEFINE MODuLE X25-PROTOCOL command to create or modify
DTE. group. or protocol module parameters in the permanent database. When
using this command. you can choose one or no DTE component. You can also
choose one or no G ROUP component plus any of the other parameters listed.
such as CALL TIMER seconds.
Format:

Network Management Utilities (CFE, NCP, VNP)

1-47

where
DTE·related parameters:

DTE
dte-address

Defines parameters for the specified local DTE
only. See RSX-ll PSI Network-specific Information for
the address format on your network.

KNOWN DTES

Defines parameters for all local DTEs.

CHANNELS
list

Specifies a list of logical channel numbers to be
used for outgoing calls or to be taken by incoming calls.
Use one or more 1- to 4-digit channel numbers in the
range of 1 to 4095. Use a hyphen (-) to indicate ranges;
use a comma (.) to separate numbers within the list.
Channel numbers are used in the order in which they
are listed.

COUNTER

Sets a timer whose expiration causes a DTE counter
logging event (range: 1 to 65.535).

TI~iER

seconds
LINE line-id

Specifies a particular line for use by the protocol module.

MAXIMUM
CIRCUITS
count

Specifies the maximum number of circuits the
module can use (range: 16 co 512).

STATE

Sets the local DTE's operational state to OFF or ON
when the system is loaded.

1·48

DECnet-RSX Guide to Network Management Utilities

Group-related parameters:

GROUP
group-name

Defines parameters for the specIfied group only.

KNOWN
GROUPS

Defines parameters for all known groups.

DTE
dte-address

Identifies the local DTE associated with the specified
group. This parameter must be used with a group number.

NUMBER
group-number

Specifies a 2-digit closed user group (CUG) number
or a 4-digit bilateral closed user group (BCUG) number
(range: 0 to 9999; you can omit leading zeroes). This
parameter must be used with a DTE address.

TYPE
BILATERAL

Required when the specified group is bilateral
(BCUG).

Protocol-related parameters:

CALL TIlVIER
seconds

Sets a timer that starts when a request is
transmitted to set up a virtual circuit and whose
expiration clears the request if no response has been
recei ved (range: 0 to 255).

CLEAR TIMER
seconds

Sets a timer that starts when a request is
transmitted to clear a virtual circuit and whose expiration
causes a retransmission of the clear request if no response
has been received (range: 0 to 255).

DEFAULT DATA
byte-count

Specifies the default packet size (in bytes) for
all SVCs. This value must not exceed that specified for
the MAXIMUM DATA parameter and must be a power
of 2 (range: 16 to 1024).

Network Management Utilities (CFE, NCP, VNP)

1-49

DEFAULT
WINDOW
block-count

Specifies the default number of data packets that
can be sent over an SVC before you have to wait
for an acknowledgment (range: 1 to 7). This value must
not exceed that specified for MAXIMUM WINDOW.

MAXIMUM
DATA
byte-count

Specifies the maximum packet size you expect to
receive on any SVC. This value must be at least 5
bytes less than the maximum data size specified for PSI
lines (see DEFINE LINE) and must be a power of 2
(range: 16 to 1024).

MAXIMUM
CLEARS
count

Specifies the maximum number of times that the
protocol module can try clearing a virtual circui t
(range: 0 to 255).

MAXIMUM
RESETS
count

Specifies the maximum number of times the protocol
module can try resetting a virtual circuit (range:
o to 255).

MAXIMUM
RESTARTS
count

Specifies the maximum number of times the protocol
module can try restarting a DTE (range: 0
to 255).

MAXIMUM
WINDOW
count

Specifies the maximum number of data packets that
can be sent over an SVC before you have to wait
for an acknowledgment (range: 1 to 7).

RESET TIMER
seconds

Sets a timer that starts when a reset is
transmitted and whose expiration causes a retransmission
of the reset message if no response has been received
(range: 0 to 255).

RESTART
TIMER
seconds

Sets a timer that starts when a restart is
transmitted and whose expiration causes a
retransmission of the restart message if no response has
been received (range: 0 to 255).

1·50

DECnet-RSX Guide to Network Management Utilities

Examples:

CFE>DEFINE MODULE X25-PROTOCOL KNOWN DTES STATE ON
This command sets the "tate of all local DTEs to ON when the system IS
loaded.

CFE>DEFINE MODULE X25-PROTOCOL MAXIMUM RESTARTS 20
This command limits to 20 the number of times the protocol module is to try
restarting a virtual circuit.

Network Management Utilities (CFE, NCP, VNP)

1-51

CFE
p
DEFINE MODULE
X25-SERVER
DEFINE MODULE
X29-SERVER

Use the DEFI:N"E ~'IODCLE X25/X29-SERVER commands to create or modify
server module parameters in the permanent database.
Restriction:
If you specify CALL ~'IASK or CALL VALUE, you must specify both. and
the hex-value of each must contain the same number of digits.
Format:

where
COUNTER TIMER Sets a timer whose expiration causes a
seconds
server module counter logging event (range: 0 to 65,535).
MAXIMUM
CIRCUITS
count

1-52

Specifies the maximum number of circuits that the
module (that is. all destinations) can use (range:
L to 255).

DECnet-RSX Guide to Network Management Utilities

DESTINATIO:\
dest-name

Defines parameters for the specified destination
only

KNOWN
DESTINATIO!\S

Defi nes parameters for all known destinations.

CALL MASK
hex-value

Specifies the mask applied to incoming call data
before it is tested against the call value (default: no
mask). Use a hexadecimal string of 2 to 32 digits (must
be an even number of digits); see restriction.

CALL VALUE
hex-value

Specifies a string of information used to test
incoming call data (default: no test string). Use a
hexadecimal string of 2 to 32 digits (must be an even
number of digits); see restriction.

GROUP
group-name

Specifies the name of a closed user group (Cl:G) or
a bilateral closed user group (BCUG) (default: no group).

NUMBER
dte-address

Identifies the remote DTE that originates the call
for the specified destination (default: no DTE).

OBJECT
ob;ect-id

Specifies the task that runs when an incoming call
activates it; required when creating a destination.

PRIORITY
priority

Specifies the priority of the destination. This
is used to select one of a set of destinations for which
the incoming call may be valid (range: 0 to 255. where
255 is the highest priority; default: 128).

SUBADDRESSES
range

Specifies a range of local DTE subaddresses that
identifies the destination for the incoming calL

Examples:

CFE>DEFINE MODULE X25-SERVER MAXIMUM CIRCUITS 20
This command limits the module to 20 circuits.
CFE>DEFINE MODULE X29-SERVER DESTINATION TKY029 PRIORITY 5
This command sets the priority of destination TKY029 to 5.

Network Management Utilities (CFE, NCP, VNP)

1-53

CFE
p

DEFINE NODE

Use the DEFI0iE ~()DE command to create or modify parameters in the
permanent database for down-line loading and up-line dumping to the specified
node (see the DECllet-RS)( j\ietu}ork i\;[anagement Concepts and Procedures
manual for a discussion of down-line loading and up-line dumping). If you are
not performing service operations on the node. NAME is the only meaningful
parameter.
Restriction:

You must specify the N AM E parameter if a node name has not previously
been defined for the specified node.
Format:

DEF I NE NODE node-id

D I AGNOST I C FILE tete
DUMP ADDRESS address
DUMP COUNT number
DUMP FILE file
HARDWARE ADDRESS E-address
HOST node-id
LOAD FILE file
NAME node-name
SECONDARY [LOADER] tile
SERVICE
CIRCUIT circllit-id
SERVICE DEVICE device-tvpe
SERVICE NODE VERSION"fpHASE III}
"LPHASE IV
[SERVICE] PASSWORD password
TERT I ARY
[ LOADER] file

where
NODE node-id

Specifies the node for which parameters are to be created
or modified. The node-id must be a node address if you
wish to assign a name to an unnamed node.

DIAGNOSTIC
FILE file

(For Ethernet nodes only) Specifies the file to be
read when the node is down-line loaded and requests
diagnos tics.

1·54

DECnet-RSX Guide to Network Management Utilities

DUMP ADDRESS
address

Specifies an octal address in memory at which to
begin an up-line dump of the node; range: 0 to 77777
(octal).

DUMP COUNT
blocks

Specifies the default number of memory units to
up-line dump from the node (range: 0 to 77777)

DUMP FILE file-id Specifies the file that is to receive a copy of the system
at the time of the crash when the node is up-line dumped.
HARDWARE
ADDRESS
E-address

Identifies the Ethernet hardware address that
was originally assigned to the DE UN A controller
for the system on the node. This address is used during
operations such as down-line load to communicate with
the system before it has set up its physical address.

HOST node-id

Specifies a host node for all service operations (default:
executor node).

LOAD FILE file

Specifies a file containing the system software for
down-line loading to the node.

NAME
node-name

Specifies a node name to be associated with the
node ID.

SECONDARY
LOADER
file

Specifies a file containing secondary loader
software for down-line loading to the node.

SERVICE CIRCUIT Specifies the circuit to be used for down-line
circuit-id
loading and up-line dumping. This circuit is the default
value for the VIA parameter of the LOAD command.
SERVICE DEVICE Specifies the node's line controller for the
device-type
service line over which the operation is to take place.
Possible devices are:
DA
DL
DLV

DMC
DMP

DPV

KDZ

DJ\,iV

DUP

DZ
KDP

QNA
UNA

Network Management Utilities (CFE, NCP, VNP)

1-55

SERVICE NODE
VERSION

Specifies the node as a Phase III or Phase IV
(default) node.

SERVICE
PASSWORD
password

Specifies the password ~equired ,to trigger the
bootstrap mechanism on the node.

TERTIARY
LOADER

Specifies a file containing tertiary loader
software for down-line loading to the node.

file
Example:

CFE>DEFINE NODE 205 nAME DALLAS
This command identifies node 205 as DALLAS.

1-56

DECnet-RSX Guide to Network Management Utilities

CFE
p
DEFINE OBJECT

Use the DEFINE OBJECT command to create a new object or to modify
object parameters in the permanent database.
Format:

DEFINE OBJECT type-code

COP I ES Jnumber }
~INGLE

NAME ~;ect-name

USER

DEFAULT
LOGIN
VERIFI ATION

{}INSPECT}
OFF
ON

where
OBJECT
type-code

Specifies the object for which parameters are to
be created or modified.

COPIES
number

Specifies the maximum number of copies of a
task that can be run at once (range: 2 to 64). Use the
keyword SI~G LE (default) if the task is not multicopy.

NAME
object-name

Specifies a name to be associated with the object.
Use any valid RSX task name. If the task is multicopy,
the name must end with $$$.

USER

Specifies the UIC under which a task is to run when
the object"s VERIFICATION option is set to ON or
INSPECT.
DEFAULT

(Default) The task runs under the default
UIC under which it was built or installed.

The task runs under the log-in UIC.

Network Management Utilities (CFE, NCP, VNP)

1-57

VERIFICATION

Specifies the degree of access to the controlled object.
I~SPECT

Allows access to the object while
indicating to it whether or not the access
control information is valid.

OFF

(Default) Allows access to the object
regardless of the validity of the access
control information.

Allows access to the object only for
inbound connections with valid access
control information.

Example:

CFE>DEFINE OBJECT 23 VERIFICATION ON
This command allows access to object 23 only to inbound connections with
valid access control information.

1·58

DECnet-RSX Guide to Network Management Utilities

CFE

P
DEFINE PROCESS

Use the DEFINE PROCESS command to modify process parameters In the
permanent database.
Restriction:

Data space is allocated within the process's addressing space only.
Format:

DEF I NE fPROCESS process-name}
\KNOWN PROCESSES

MAXIMUM CONTROLLERS count
MAXIMUM tINES number

STATE

{~~EARED }

where
PROCESS
process-name

.Modifies parameters for the specified process
only.

KNOWN
PROCESSES

Modifies parameters for all known processes.

MAXIMUM
CONTROLLERS
count

Specifies the maximum number of hardware
controllers (range: 0 to 64) for
which the process is to allocate data space (see restriction).

MAXIMUM
LINES
number

Specifies the maximum number of lines (range: 0 to
64) for which the process is to allocate data
space (see restriction).

STATE

Sets the operational state of the process when the system
is loaded.
CLEARED Not available; must be loaded.
ON Automatically loaded and available.

Network Management Utilities (CFE, NCP, VNP)

1·59

Example:

CFE>DEFINE PROCESS DMC MAXIMUM CONTROLLERS 5
This command specifies that process DMC allocate data space for five
controllers.

1-60

DECnet-RSX Guide to Network Management Utilities

CFE

p
DEFINE SYSTEM

Use the DEFINE SYSTEl\1 command to modify Communications Executive
parameters in the permanent database.
Format:

DEFINE SYSTEM

LARGE BUFFER SIZE number
[LOCATIONJ)FIRSTFIT}
'tr0PDOWN
MAXIMUM CONTROL BUFFERS number
MAX I MUM LARGE BUFFERS !lumber
MAXIMUM SMALL BUFFERS number
MINIMUM RECEIVE BUFFERS !lumber
POOL BYTE-AREA byte-count
POOL NAME pool-name
POOL PARTITION partition-name

where
LARGE BUFFER
SIZE number

Specifies the size (in bytes) of large buffers (range:
for DECnet. 192 to 4096; for PSI only, 128 to
4096).

LOCATION

Specifies the type of dynamic memory allocation
for any process whose state is ON in the
permanent database.

MAXIMUM
CONTROL
BUFFERS number

FIRSTFIT

(Default) Loads the processes at
the first available space that is
large enough.

TOPDOWN

Loads the processes at the top of
the partition.

Specifies the maximum number of control buffers
available for Communications Executive system
use (range: 4 to 200).

Network Management Utilities (CFE, NCP, VNP)

1·61

MAXIMUM LARGE
BUFFERS number

Specifies the maximum number of large buffers
available for Communications Executive system
use (range: 4 to 200).

MAXIMUM SMALL
BUFFERS number

Specifies the maximum number of small buffers
available for Communications Executive system
use (range: 3 to the maximum number of control
buffers).

MINIMUM RECEIVE
BUFFERS number

Specifies the minimum number of receive buffers
available for Communications Executive system
use (range: 1 to n; n is the maximum number of
large buffers minus 1).

POOL BYTE-AREA
byte-count

Specifies the number of bytes needed in the
network pool (range: n to 64.572. where n is
calculated by CFE and includes space for all
currently defined remote nodes. objects, and so
on; default: m, where m is calculated by CFE
and is equal to the value n plus a variable amount
of extra free space).

POOL NAME
pool-name

Specifies the name of the subpartition to be
created. Use a name consisting of 1 to 6 Radix-50
characters.

POOL PARTITION
partition-name

Specifies the name of the partition into which
the network pool is to be loaded. Use a name
consisting of 1 to 6 Radix-50 characters.

Example:

CFE>DEFINE SYSTEM MAXIMUM SMALL BUFFERS 50
This command sets the maximum number of small buffers In the system to
50.

1-62

DECnet-RSX Guide to Network Management Utilities

NCP

P
KMX-DUMP

Use the KMX-DUMP command to dump KMX or Kl\IY microcode to disk
for analysis by the K~IX-Dump analyzer task (KDA). For information on the
KDA utility. see Chapter 4.
NOTE

This command halts all lines on the KlVIX or KMY device. To
bring the device back up after the dump. use the NCP SET
LINE command to set the state of all lines first to OFF and
then to ON.
Format:

where
LINE line-id

Specifies a K~IX or KMY line (see note above). Specify
line-id in the form KMX -c-u or KMY -u.

FILENAME
file

N ames the file to hold the binary dump
(default: LB:[1,6]PSIKMXMEM.SYS).

Example:

NCP>KMX-DUMP LINE KMX-O-l LB: [1,6]KMXMC.DMP
This command dumps the microcode of KMX-O-l to file LB:[1.6]KMXMC.DMP.

Network Management Utilities (CFE, NCP, VNP)

1-63

CFE

p
LIST CIRCUIT

Use the LIST CIRCUIT command to display circuit information stored in the
permanent database.
Format:

LIST f C r'RCU I T Circllit-id}
\KNOWN CIRCUITS
where
CIRCUIT
circuit-id

Displays information for the specified circuit
only.

KNOWN CIRCUITS Displays information for all known circuits.
Example:

CFE>LIST CIRCUIT DMC-O
This command causes the system to display static information for circuit
DMC-O.

1·64

DECnet-RSX Guide to Network Management Utilities

CFE

p
LIST EXECUTOR

Use the LIST EXECUTOR command to display executor node information
stored in the permanent database.
Format:

LIST EXECUTOR

Network Management Utilities (CFE. NCP, VNP)

1-65

CFE
p

LIST LINE

Use the LIST LINE command to display line information stored
permanent database.

ill

the

Format:

LIST JLINE line-id
"lKNOWN LINESJ
where

LINE line-id

Dlsplays information for the specified line only.

KNOWN LINES

Displays information for all known lines.

Example:

CFE>LIST KNOWN LINES
This command causes the system to display static information for every line
attached to the executor node.

1·66

DECnet-RSX Guide to Network Management Utilities

CFE

p
LIST LOGGING

Use the LIST LOGG ING command to display logging information stored ill
the permanent database.
Format:

LIST

KNOWN LOGGING }
LOGGING CONSOLE
LOGGING FILE
LOGGING MONITOR

U
where
KNOWN
LOGGING

Displays information for all known logging
components.

LOGGING
CONSOLE

Displays information for the console logging
component.

LOGGING
FILE

Displays information for the file logging
component.

LOGGING
MONITOR

Displays information for the monitor logging
component.

Example:

CFE>LIST LOGGING MONITOR EVENTS
This command causes the system to display static information for the logging
monitor program.

Network Management Utilities (CFE, NCP, VNP)

1-67

CFE

p
LIST MODULE
X25-ACCESS

Use the LIST l\10DCLE X2!)-ACCESS command to display remote DTE
destination information stored in the permanent database.
Format:

where
DESTINATION
dest-name

Displays information for the specified destination
only.

KNOWN
DESTINATIONS

Displays information for all known destinations.

Example:

CFE>LIST MODULE X25-ACCESS DESTINATION NYC42
This command causes the system to display static information for destination
NYC42.

1-68

DECnet-RSX Guide to Network Management Utilities

CFE

P
LIST MODULE
X25·PROTOCOL

Use the LIST MODULE X25-PROTOCOL command to display protocol module
information stored in the permanent database. The information must be
qualified by either DTE or group.
Format:

where
DTE dte-address

Displays information for the specified DTE only.

KNOWN DTES

Displays information for all known DTEs.

GROUP
group-name

Displays information for the specified group
only.

KNOWN GROUPS

Displays information for all known groups.

Example:

CFE>LIST MODULE X25-PROTOCOL GROUP CUG98

This command causes the system to display static information for group
CUG98.

Network Management Utilities (CFE, NCP, VNP)

1·69

CFE

p
LIST MODULE
X2S-SERVER
LIST MODULE
X29-SERVER

Use the LIST MODULE X25/X29-SERVER commands to display server
module information stored in the permanent database. This information may
be qualified by destination.
Format:

where

DESTINATION
dest-name

Displays information for the specified destination
only.

KNOWN
DESTINATIONS

Displays information for all known destinations.

Example:

CFE>LIST MODULE X29-SERVER DESTINATION PG49
This command causes the system to display static ~erver module information
for destination PG49.

1-70

DECnet-RSX Guide to Network Management Utilities

CFE
p

LIST NODE

Use the LIST NODE command to display node information stored in the
permanent database.
Format:

LIST

NODE node-id
"LKNOWN NODES!

where

NODE node-id

Displays information for the specified node only.

KNOWN NODES

Displays information for all known nodes.

Example:

CFE>LIST NODE BOSS1
This command causes the system to display static information for node BOS5I.

Network Management Utilities (CFE. NCP, VNP)

1·71

CFE

p
LIST OBJECT

Use the LIST OBJECT command to display object information stored in the
permanent database.
Format:

LIST

jOBJECT type-COde}
lKNOWN OBJECTS

where
OBJECT type-code

Displays information for the specified object only.

KNOWN OBJECTS Displays information for all known objects.
Example:

CFE>LIST KNOWN OBJECTS
This command causes the system to display static information for all objects
known to the executor node.

1-72

DECnet-RSX Guide to Network Management Utilities

CFE
p

LIST PROCESS

Use the LIST PROCESS command to display process information stored III
the permanent database.
Format:

LIST

PROCESS process-nam~
{ KNOWN PROCESSES

where
PROCESS
process-name

Displays information for the specified process
only.

KNOWN
PROCESSES

Displays information for all known processe~.

Example:

CFE>LIST PROCESS KDZ
This command causes the system to display static process information.

Network Management Utilities (CFE. NCP, VN P)

1·73

CFE
p
LIST SYSTEM

Use the LIST SYSTE M command to display system information stored in the
permanent database.
Format:

LIST SYSTEM

1-74

DECnet-RSX Guide to Network Management Utilities

NCP

P
LOAD NODE

Use the LOAD NODE command to down-line load a specified RSX-llS remote
node. For more information about down-line loading system images. see the
DECnet-RSX Network Nlanagement Concepts and Procedures manual.
Format:

LOAD

NODE node-id

ADDRESS node-address
FROM lile
HOST node-id
NAME node-name
PHYS I CAL ADDRESS E-address
SECONDARY [LOADER] Ille
SERVICE DEVICE device-type
SERVICE NODE VERSION fPHASE III}
"PHASE IV
[ SERV I CE ] PASSWORD service-passlUord
TERT I ARY
[ LOADER] lile
V I A circuit-id

where
NODE node-id

Specifies the node to be down-line loaded.

ADDRESS
node-address

Specifies the address that the node is to use when
it comes up.

FROM lile

Specifies the file specification of the load file containing
the system software to be down-line loaded.

HOST Ilode-id

Specifies the default host that the node is to use when
it comes up.

NAME
node-name

Specifies the node name that the node is to use
when it comes up.

PHYSICAL
ADDRESS
E-address

(For Ethernet nodes only) Identifies the Ethernet
physical address that the node currently
uses to identify itself. (Required for Ethernet circuits if
the hardware address parameter has not been specified
in the volatile database; see SET NODE.)

Network Management Utilities (CFE, NCP. VNP)

1·75

SECONDARY
LOADER
tlle

Specifies a file contmmng secondary loader
software for down-line loading to the node.

SERVICE
DEVICE
device-type

Specifies the node's line controller for the
service line over which the operation
is to take place. Possible devices are:
DA
DL
DLV

DMC
DMP
DMV

DPV

KDZ

DU
DUP

QNA
UNA

KDP

SERVICE NODE
VERSION

Specifies the node as a Phase III or Phase IV
(default) node.

SERVICE
PASSWORD
servicepassword

Specifies the password required to trigger the
bootstrap mechanism on the node.

NOTE

If you do not want a password echoed to your terminal while
you enter it, press the RETURN key after the keyword
PASSWORD. NCP prompts for the password and turns off
echoing until the next prompt.

TERTIARY
LOADER lile

Specifies a file containing tertiary loader
software for down-line loading to the node.

VIA circllit-id

Specifies the circuit over which the load is to take place.

1·76

DECnet-RSX Guide to Network Management Utilities

Examples:

NCP>LOAD NODE ATL25
This command loads node ATL25. Default load parameters are obtained from
the volatile database.

NCP>LOAD NODE ATL25 VIA DMC-l
This command loads node ATL25 by way of circuit DlV[C-l.

Network Management Utilities (CFE, NCP, VNP)

1-77

NCP
P

LOAD VIA

Use the LOAD VIA command to down-line load an RSX-IIS remote node via
the specified circuit. For more information about down-line loading system
images. see the DECnet-RSX Network Management Concepts and Procedures
manual.
Format:

LOAD V I A circuit-id

ADDRESS node-address
FROM lile
HARDWARE ADDRESS E-address
HOST node-id
NAME node-name
PHYS I CAL ADDRESS E-address
SECONDARY [LOADER] tile
SERV ICE DEV I CE device-type
SERVICE NODE VERSION" JPHASE III}
LPHASE IV
[ SERV I CE] PASSWORD sercice-password
TERT I ARY
[ LOADER] lile

where
VIA circuit-id

Specifies a circuit over which the load is to take place.

ADDRESS
node-address

Specifies the address the node is to use when it
comes up.

FROM lile

Specifies the file specification of the load file containing
the system software to be down-line loaded.

HOST node-id

Specifies the default host that the node is to use when
it comes up.

NAME
node-name

Specifies the node name that the node is to
use when it comes up.

PHYSICAL
ADDRESS
E-address

(For Ethernet nodes only) Identifies the
Ethernet physical address that the node currently
uses to identify itself. Required for Ethernet circuits if
the hardware address parameter has not been specified
in the volatile database; see SET NODE.

1-78

DECnet-RSX Guide to Network Management Utilities

SECONDARY
LOADER tile

Specifies the filt> specification of a secondary
load program to be down-line loaded.

SERVICE
DEVICE
device-type

Specifies the node's line controller for the
service line over which the operation
is to take place. Possible devices are:
DA
DL
DLV

Dl\IC
DMP
Dl\IV

DPV
DU
DUP

DZ
KDP

KDZ
QNA
UNA

SERVICE NODE
VERSION

Specifies the node as a Phase I I I or Phase IV
(default) node.

SERVICE
PASSWORD
servicepassword

Specifies the password required to trigger the
bootstrap mechanism on the node.

NOTE

If you do not want a password echoed to your terminal while
you enter it, press the RETURN key after the keyword
PASSWORD. N"CP prompts for the password and turns off
echoing until the next prompt.

TERTIARY
LOADER
{ile

Specifies the file specification of a third
load program to be down-line loaded.

Example:

NCP>LOAD VIA DMC-O
This command loads the node connected to the executor node via circuit
DMC-O.

Network Management Utilities (CFE, NCP, VNP)

1-79

NCP
P

LOOP CIRCUIT

Use the LOOP CIRt't'IT command to test a DECnet Cln:lHl In lhe m:twork.
See the DECllet-RS'X ,Vetworli lvlanagement Concepts and Pr( I( (,(far(',"" manual
for more information on loop back testing.
When testing an Ethernet circuit. you can specify a destination node using
either its node name or its physical address. You can also use the HFLP
parameter to specify a third node to assist with the test. If you do not sped fy
a destination node. the loop request is sent to the multicast address and the
first node to respond will complete the loop test.

Format:
LOOP C I RCU I T circuit-ld

NODE /lode·name

r~~r~ C{A~~:::Sfi ;:;:~'~:
L TRANSMIT~l(ASSISTANT

CIRCUIT
circuit-id

ANT

NODE nooName)
PHYSICAL ADDRESS

E-addms~]

COUNT count
LENGTH length
WITH{MIXED }
ONES
ZEROES

Specifies the circuit t-o use for the loop back
test.

NODE E-node-name

Specifies the name of an Ethernet node that is
to be the destination of a loop test message.

PHYSICAL ADDRESS

Specifies the physical address (not a multicast
address) of an Ethernet node that is to be the
destination of a loop test message.

E-address

1-80

DECnet-RSX Guide to Network Management Utilities

HELP
help-type

Specifies the degree to which a third node is to
assist with an Ethernet loop circuit test.
FULL

The assisting node is to both
recei ve and transmit the test
packet (see the example).

RECEIVE

The assisting node is only to
recei ve the test packet.

TRANS~lrT

The assisting node is only to
transmit the test packet.

If you specify HELP. you must also specify
either the PHYSICAL ADDRESS and
ASSISTANT PHYSICAL ADDRESS parameters
or. if the addresses are not known. you must
specify the ~ODE and ASSISTANT ~ODE
parameters. If you specify ASSISTANT NODE
or ASSISANT ADDRESS and do not specify
HELP. the default is HELP FULL.

ASSISTANT
NODE
E-node-name

Specifies the name of an Ethernet node that is
to assist in the loop circuit test.

ASSISTANT
PHYSICAL
ADDRESS
E-address

Specifies the physical address (not a multicast
address) of an Ethernet node that is to assist in
the loop circuit test.

COUNT

count Specifies the number of blocks to be sent
during loopback testing (range: 1 to 65535;
default: 1 block is looped).

LENGTH
length

Specifies the length (in bytes) of blocks to be
sent during loop back testing. The length must
be a decimal integer in the range of 1 to n. where
n must be less than the smaller of either the
local looper buffer size or the remote mirror
buffer size (default: 40 bytes).

Network Management Utilities (CFE. NCP. VNP)

1·81

When testing over the Ethernet. the maximum
length of the data pattern varies according to
the level of assistance:

'NITH

Level of Assistance

Allowable Length

No assistance
Transmi t or receive
assistance
Full assistance

32 - 1486 bytes
32 - 1478 bytes
32 - 1470 bytes

Specifies the type of binary information to be
sent during testing (default: MIXED -- a
combination of ones and zeroes).

Example:

NCP>LOOP CIRCUIT UNA-O HELP FULL PHYSICAL ADDRESS AA-OO-04-00-F9-04 -<RET>
NCP>ASSISTANT PHYSICAL ADDRESS AA-OO-04-00-04-A9
This command. shown in continuation format. tests circuit UN A-O with the
assistance of the node specified in ASSISTANT PHYSICAL ADDRESS. The
initiating node sends a test packet to the assisting node. The assisting node
processes the packet and passes the packet to the destination node specified
in PHYSICAL ADDRESS. The destination node receives the packet and
transmits the packet back to the assisting node. The assisting node then
returns the packet to the initiating node.

1·82

DECnet-RSX Guide to Network Management Utilities

NCP
NP
LOOP EXECUTOR/NODE

Use the LOOP ~ODE command to test a node in the network. You can include
access control information if the node requires it. If you are testing the
executor node. you can use the LOOP EXECUTOR command. Either command
causes test blocks of data to be transmitted to the specified node. See the
DECnet-RSX Network lvlanagement Concepts manual for more information on
loop back testing.
Format:

LOOP {NODE flode-id[acc-con-info1lCOUNT COllnt
EXECUTOR
fLENGTH len{?th
WITH{MIXED }
ONES
ZEROES
where

NODE node-id

Specifies a node for loop back testing.

ace-eon-info

Specifies access control information. if required.

EXECUTOR

Specifies the executor node for loopback testing.

COUNT count

Specifies the number of blocks to be sent during loopback
testing (range: 1 to 65535; default: 1 block is looped).

LENGTH
length

Specifies the length (in bytes) of blocks to be sent during
loopback testing. \Nhen testing over the Ethernet. the
length must be a decimal integer in the range of 32 to
1484. Otherwise. the length must be a decimal integer
in the range of 1 to n. where fl must be less than the
smaller of either the local looper buffer size or the remote
mirror buffer size (default: 40 bytes).

WITH

Specifies the type of binary information to be sent during
testing (default: MIXED -- a combination of ones and
zeroes).

Network Management Utilities (CFE. NCP. VNP)

1-83

Example:

NCP>LOOP NODE NYC COUNT 10
This command loops 10 blocks of mixed test messages to remote node NYC.
Each block is 40 bytes.

1·84

DECnet-ASX Guide to Network Management Utilities

NCP
P

LOOP LINE

Use the LOOP LINE command to test a PSI line in the network. This
command causes test blocks of data to be transmitted over the specified line.
See the DECnet-RSX Network Ivlanagemellt Concepts and Procedures manual
for more information on loopback testing.
Format:

where
LINE
line-id

Specifies the line to use for the loopback test.

COUNT count

Specifies the number of blocks to be sent during loopback
testing (range: 1 to 65535; default: 1 block is looped).

LENGTH
length

Specifies the length (in bytes) of blocks to be
sent during loopback testing. The length must be a
decimal integer in the range of 1 to n. where n must be
less than the smaller of either the local looper buffer size
or the remote mirror buffer size (default: 40 bytes).

WITH

Specifies the type of binary information to be sent during
testing (default: MIXED -- a combination of ones and
zeroes).

Example:

NCP>LOOP LINE SDP-O COUNT 10 LENGTH 100
This command loops a 100 byte message over line SDP-O 10 times. The
data consists of mixed ones and zeroes.

Network Management Utilities (CFE, NCP, VNP)

1·85

CFE
P

PURGE CIRCUIT

Use the PURGE CIRCGIT command to clear the specified PSI circuit
counter timer(s) III the permanent database.
Format:

where
CIRCUIT
circuit-id

Clears the counter timer for the specified circuit
only.

KNOWN
CIRCUITS

Clears the counter timers for all known circuits.

Example:

CFE>PURGE KNOWN CIRCUITS COUNTER TIMER
This command clears the counter timers for all known PSI circuits.

1·86

DECnet-RSX Guide to Network Management Utilities

CFE
P
PURGE LINE

Cse the peRCE LINE command to clear the specified PSI line counter
timer(s) in the permanent database.
Format:

where
LINE
Line-id

KNO\VN
LINES

Clears the counter timer for the specified
line only.
Clears the counter timers for all known lines.

Example:
CFE>PURGE LIlm SDP-O COUNTER TIMER

This command clears the counter timer for line SDP-O.

Network Management Utilities (CFE. NCP. VNP)

1-87

CFE
P
PURGE LOGGING

(;se the PURGE LOGGING command to remove the specified logging event
parameters from the permanent database.
Format:

PURGE

KNOWN LOGGING }
LOGGING CONSOLE
{ LOGGING FILE
LOGGING MONITOR

ALL EVENTS
}
EVENTS
event-list
{
KNOWN EVENTS

where
KNOWN
LOGGING

Removes parameters for all known logging
components.

LOGGING
CONSOLE

Removes parameters for the console logging
component.

LOGG ING FILE

Removes parameters for the file logging component.

LOGGING

Removes parameters for the monitor logging
component.

~10NITOR

ALL EVENTS

Removes parameters for all logging event classes and
types.

EVENTS
event-list

Removes the event class and type(s) specified
in event-list for the specified component.

K~OWN

Removes all logging events that DECnet-RSX
can generate for the specified component.

EVE~TS

Example:

CFE>PURGE KNOWN LOGGING ALL EVENTS
This command removes all classes and types of events for all known
logging components.

1·88

DECnet-RSX Guide to Network Management UjjJ1ties

CFE
p

PURGE MODULE
X25·ACCESS

Use the PURGE :MODULE X25-ACCESS command to remove parameters for
the specified destination(s) from the permanent database.
Format:

where
DESTINATION
dest-name

Removes parameters for the specified destination
only.

KNOWN
DESTINATIONS

Removes parameters for all known destinations.

ALL

(Required) Removes all parameters for
destination(s}.

the specified

Example:

CFE>PURGE MODULE X25-ACCESS DESTINATION DALLAS ALL
This command removes destination DALLAS and all associated parameters.

Network Management Utilities (CFE, NCP, VNP)

1·89

CFE
P

PURGE MODULE
X25-PROTOCOl

Use the PURGE MODULE X25-PROTOCOL command to zero the counter
timer(s) for the specified DTE(s) or to remove all parameters for the specified
DTE(s) or group(s) from the permanent database.
Format:

where
DTE
dte-address

Clears the specified DTE only. Be aware that
purging a DTE removes all PVCs and CUGs associated
with it and purges them from the permanent database.

KNOWN DTES

Clears all known DTEs.

GROUP
group-name

Removes parameters for the specified group only.

KNOWN GROUPS

Removes parameters for all known groups.

ALL

Removes all parameters for the specified DTE(s) or
group(s).

COUNTER TIMER Clears the counter timer(s) for the specified DTE(s).
Example:

CFE>PURGE MODULE X25-PROTOCOL GROUP CUGll1 ALL
This command removes parameters for group CUG Ill.

1-90

DECnet-RSX Guide to Network Management Utilities

CFE

P
PURGE MODULE
X2S-SERVER
PURGE MODULE
X29-SERVER

Use the PURGE MODULE X25/X29-SERVER commands to zero the counter
timer or to remove parameters for the specified destination(s) from the
permanent database.
Format:

where
COUNTER

Clears the server module counter timer.

TI~IER

DESTINATION
dest-name

Removes parameters for the specified destination
only.

KNOWN
DESTIN ATIONS

Removes parameters for all known destinations.

ALL

Required when you specify a destination parameter;
removes all parameters for the specified destination(s).

Example:

CFE>PURGE MODULE X25-SERVER DESTINATION ALBANY ALL
This command removes destination ALBANY and all associated parameters.

Network Management Utilities (CFE. NCP. VNP)

1·91

CFE

P
PURGE NODE

Use the PURGE NODE command to remove specified node parameters from
the permanent database on the local node.
Format:

PURGE jNODE node-id }
"\KNOWN NODES

ALL
DIAGNOSTIC FILE
DUMP ADDRESS
DUMP COUNT
DUMP FILE
HARDWARE ADDRESS
HOST
LOAD FILE
SECONDARY [LOADER]
SERVICE CIRCUIT
SERVICE DEVICE
[SERVICE] PASSWORD
TERTIARY [LOADER]

where
NODE node-id

Removes parameters for the specified node only.

KNOWN NODES

Removes parameters for all known nodes.

ALL

Removes all parameters for the specified node(s). If you
specify ALL. you cannot include any other parameters.

DIAGNOSTIC
FILE

Removes the identification of the down-line
load diagnostics file.

1·92

DECnet-RSX Guide to Network Management Utilities

DUn,IP ADDRESS

Removes the node's up-line dump address.

DUMP COUNT

Removes the up-line dump count.

DU~lP

FILE

Removes the up-line dump file identification.

HARD\VARE
ADDRESS

Removes the Ethernet address of the system
hardware.

HOST

Removes the host node identification.

LOAD FILE

Removes the down-line load file identification.

SECONDARY
LOADER

Removes the parameter associated with the file
containing secondary loader software for down-line
loading to the node.

SERVICE
CIRCUIT

Removes the circui t parameter associated wi th
the node for down-line load operations.

SERVICE DEVICE Removes the service device type.
SERVICE
PASSWORD

Removes the password parameter required to
trigger the bootstrap mechanism.

TERTIARY
LOADER

Removes the parameter associated with the file
containing tertiary loader software for down-line loading
to the node.

Example:

CFE>PURGE NODE BOS ALL
This command removes node BOS from the database.

Network Management Utilities (CFE. NCP, VNP)

1·93

CFE

P
PURGE OBJECT

Use the PURGE OBJECT command to remove all parameters for
the specified object(s) from the permanent database.
Format:

PURGE JOBJECT Obicct-type}
l.KNOWN OBJECTS
where
OBJECT
ob;ect-type

Removes ,parameters for the specified object only.

KNOWN
OBJECTS

Removes parameters for all known objects.

Example:

CFE>PURGE OBJECT 200
This command removes all parameters for object 200.

1·94

DECnet-RSX Guide to Network Management Utilities

NCP/VNP IP
NP
SET ALIAS

Use the NCP SET ALIAS command to specify an alias name for a node
in the volatile database. Use the V~P command to do the same
with the system image file.
Format:

SET AL I AS alias-name

DEST I NAT ION dest-node

[ [SCOPE] scope]

where
ALIAS
alias-name

Specifies the alias name to be assigned to the
destination node.

DESTINATIO~

Specifies the destination node and any access
control parameters associated with this alias for that
node. See Section 1.5.2 for access control information
format.

dest-node

SCOPE scope

See definition in Section 1.5.2.

Example:

NCP>SET ALIAS PETSKY DESTINATION MAINE/DAVIES/LESLIE -<RET>
NCP>SCOPE TERMINAL TT22:
This command (shown in continuation format) sets alias PETSKY to terminal
TT22: on node l\'lAINE. DAVIES is the account name. and LESLIE is the
password.

Network Management Utilities (CFE, NCP, VNP)

1·95

NCP/VNP

P
SET CIRCUIT

Use the NCP SET CIRCCIT command to create or modify specified circuit
parameters in the volatile database. Use the VNP command to do the same
with the system image file.
Restriction:

The VNP SET CIRCUIT command is invalid for PSI circuits.
Format:

SET

I RCU I T Circuit-id} COST cost
KNOWN CIRCUITS
HELLO T I MER seconds
MULTIPOINT ACTIVE active-ratio
OWNER JDLX}
'\XPT
SERVICE !DISABLE}
'lENABLE
STATE {g~F

}

SERVICE
TR I BUT ARY trib-address
where
CIRCUIT
circuit-id

Sets parameters for the specified circuit only.

KNOWN
CIRCUITS

Sets parameters for all known circuits.

COST cost

(DECnet circuits only) Specifies the routing cost of the
circuit. ~Iessages will travel between nodes along the
path with the smallest total cost (range: 1 to 25).

COUNTER
TIMER
seconds

(PSI circuits only; invalid for VNP) Sets a timer
whose expiration causes the circuit counters to be
logged and zeroed (range: 1 to 65.535).

1·96

DECnet-RSX Guide to Network Management Utilities

HELLO
TINtER
seconds

(D ECnet clrcuits only) Specifies the frequency of
routing hello messages sent to adjacent nodes over
the circuit (range: 1 to 8191).

:VIUL TIPOINT
ACTIVE
act ive-rat io

(DECnet non-O;\IP/DMV multipoint control circuits
only) Specifies the rate at which a tributary
in the active multipoint state is polled (range: 1 to 255).

OWNER

(DECnet circuits only) Specifies the circuit owner.
DLX

DLX (See the DECnet-RSX Programmer's
Re/,erellce L\Janllal.)

XPT

DECnet

SERVICE

(D ECnet circuits only) Specifies whether the circuit is
enabled or disabled for down-line loading and loopback
testing.

STATE

Sets the circuit's operational state. For circuits owned
by the executor, the state of the corresponding lines
must be ON.

TRIBUTARY
trib-address

OFF

0r ot available.

A vailable for normal use.

SERVICE

Available for service operations only.

(D ECnet multipoint circuits only) Specifies the
data link physical tributary address of the multipoint
circuit (range: 1 to 255).

Example:

NCP>SET CIRCUIT KDZ-1-3 STATE OFF
This command sets the state of circuit KDZ-1-3 to·OFF.

Network Management Utilities (CFE, NCP, VNP)

1·97

NCP/VNP

p
SET EXECUTOR

Use the NCP SET EXECUTOR command to create or modify executor node
parameters in the volatile database. Use the VNP command to do the same
with the system image file.
Format:

SET EXECUTOR HOST node-id
INACTIVITY TIMER seconds
I NCOM I NG T I MER seconds
OUTGOING TIMER seconds
RECE I VE PASSWORD password
RETRANSMIT FACTOR number
ROUT I NG TIMER seconds
SEGMENT BUFFER SIZE number
STATE

{g~F fFIXED

LUNFIXEDJ
SHUT

1J38iltEJ 1HalBIU:.l i !].

TRANSMIT PASSWORD password

VERIFICATION [STATEl.(g~F}
where
HOST node-id

Specifies the host node identification for down-line load,
trigger, and up-line dump.

INACTIVITY
TIMER
seconds

Specifies the maximum time the executor will allow
a link to remain idle (no user data traffic)
before it checks to see if the circuit still works (range:
1 to 255).

INCOMING
TIMER
seconds

Specifies the maximum time a rocess has to answer
an incoming connect request. If the process does
not answer the connect request within this time interval,
the node will reject the connect request on behalf of the
process (range: 1 to 255).

1·98

DECnet-RSX Guide to Network Management Utilities

OUTGOING
TIJ\.IER
seconds

Specifies the maximum time the executor node wIll
wait for a pending connect request to be
answered at a destination node. If the request is not
answered in this time interval. the source process receives
an error indication (range: 1 to ~55).

RECEIVE
PASS\VORD
passu'O!'d

Specifies a 1- to 8-character ASCII password
that the executor expects to receive during
initialization with an adjacent Phase III node.

RETRANSMIT
FACTOR
number

Specifies the number of times the executor will
restart the retransmission timer before the
logical link is disconnected (range: 1 to 255).

ROUTING
TIlVIER
seconds

Sets a timer whose expiration forces a routing
update on non-Ethernet circuits (range: 1 to
65.535).

SEG~IENT

Specifies the maximum size of transmit buffers
(in bytes). thereby controlling the size of the
NSP message segment to be sent. This value is the
maximum size message that the End Communications
layer can transmit; it does not include routing or data
link overhead (range: 1 to 4096; default: 18 bytes less
than the large buffer size specified in the DEFINE
SYSTE~I command). The segment buffer size can never
be greater than the large buffer size minus 18 bytes.

BuFFER
SIZE number

STATE

Sets the operational state of the executor node. This
parameter cannot be specified if you use the TELL prefix.
OFF

Allows no new Logical hnks: terminates
existing links; forces the release of all
mailboxes as quickly as possible.

Network Management Utilities (CFE. NCP. VNP)

1·99

(Invalid for V~P on RSX-lll\1/l\l-PLUS; see
DECnet-RSX Network l\Ianagement Concepts
alld Procedures) Allows normal loglcal link
activity. When using V~P to set the executor
state to ON for DEenet-IIS systems. you can
specify one of the following task states for
~TINIT after it has initialized the node:

FIXED

U~FIXED

(Default) NTINIT remains in
memory.
~TINIT

is removed from

memory.
SHUT

(Invalid for VNP) Allows no new logical links;
does not destroy existing links; goes to the
OFF state when all logical links terminate
and all mailboxes are released.

SUBADDRESSES
range

(Invalid for VNP) Specifies a range of local DTE
subaddresses that are valid on any DLM circuit for
incoming calls to the executor node.

TRANSl\IIT
PASSWORD
password

Specifies a 1- to 8-character ASC I I password that
the executor sends to the adjacent Phase III node
during a node initialization sequence.

1-100

DECnet-RSX Guide to Network Management Utilities

VERIFICATION
STATE

Sets the logical link access control verification
state for the executor node.

OFF

The executor node does not verify access
control on any incoming connect requests.

The executor node verifies access control on
all incoming connect requests according to
the options set for each object (see the
discussion of access control in the
DECnet-RSX Network lvlanagement Concepts
and Procedures manual).

Example:

NCP>SET EXECUTOR HOST 12
This command sets node 12 as the, host node for down-line load. trigger, and
up-line dump operations.

Network Management Utilities (CFE, NCP, VNP)

1-101

NCP
NP
SET EXECUTOR NODE

Use the SET EXECUTOR NODE command to set a default executor for all
commands. This causes subsequent remotely executable NCP commands
to be executed at the specified destination. The DECnet-RSX .Vetll'ork
iVlanagement Reference Card lists all NCP commands and flags those that are
not remotely executable.
~CP

Restriction:

You cannot use the TELL prefix with this command (that is. this command
is not remotely executable).
Format:
SET EXECUTOR NODE node-id [ace-eon-into]

where
NOD E node-id

Specifies the node by address. alias. or name. that is to
serve as the executor for subsequent NCP commands.

ace-can-into

Specifies access control information (if required by the
node).

Example:

NCP>SET EXECUTOR NODE ATL25/NELSON/PAT
This command sets node ATL25 (user NELSON. password P AT) to executor
status. Future commands will be sent to ATL25 for execution.

1·102

DECnet-RSX Guide to Network Management Utilities

NCP/VNP

P
SET KNOWN LINES

Use the NCP SET K~O"VN LINES command either to load all known lines
and create their associated parameters in the volatile database or to create or
modify parameters in the database for all known lines that are already loaded.
Use the VNP command to do the same with the system image file.
Restriction:

Except for STATE. the options allowed when you are loading lines are different
from those used to create or modify parameters for lines that are already
loaded. Any lines that you are loading must be in the CLEARED state. Lines
that are already loaded must be in the ON or OFF states (that is. not
CLEARED).
Format:

SET KNOWN LINES
Loading options:

ALL
DEAD TIMER milliseconds
DELAY T~ER milliseconds
DUPLEX FULL}
HALF
[LOCATIONJJlFIRSTFIT}
'lTOPDOWN

Loaded options:
OWNER
where
STATE

(Invalid for VNP) Sets the operational state for all PSI
lines to either OFF or ON.

Network Management Utilities (CFE, NCP, VNP)

1-103

Loading options:

ALL

Loads the lines with all of the default parameters specified
in the permanent database. If you specify ALL. you
cannot include any other parameters.

DEAD TIMER
millisecond s

(For DECnet DMP/Dl\tlV multipoint control lines
only) Specifies the polling interval for a dead tributary
(range: 1 to 65.535).

DELAY TIl\tlER
milliseconds

(For D ECnet D !\lIPID MV multipoint control lines only)
Specifies the minimum time to delay between polls in
order to limit the effect of a fast control station on a
slow tributary (range: 1 to 65.535).

DUPLEX

(DECnet DDC,\:IP lines only) Sets the hardware
transmission mode to full duplex or half duplex.

LOCATION

(Invalid for VNP) Specifies the type of dynamic memory
allocation.

1·104

FIRSTFIT

(Default) Loads the driver processes at
the first available space that is large
enough in the partition.

TOPDOWN

Loads the driver processes at the top of
the partition.

DECnet-RSX Guide to Network Management Utilities

Loaded options:

COUNTER
TIMER
seconds

(PS I lines only) Sets a timer whose expiration
causes the line counters to be logged and zeroed
(range: 0 to 65.535).

OWNER

Specifies line ownership.
DLX

DLX (See the DECnet-RSX Programmer's
Reference AtJanllal.)

PLI

PSI (Invalid for VNP)

Example:

NCP>SET KNOWN LINES DUPLEX FULL
This command sets all lines known to the system to full duplex.

Network Management Utilities (CFE, NCP, VNP)

1·105

NCP/VNP
P
SET LINE

Use the NCP SET LINE command either to load the specified line and create
its associated parameters in the volatile database or to create or modify
parameters in the database for a line that is already loaded. Use the VNP
command to do the same with the system image file.
Restriction:

Except for STATE, the options allowed when YOLl are loading a line are
different from those used to create or modify parameters for a line that is
already loaded. Any line that you are loading must be in the CLEARED state.
A line that is already loaded must be in the ON or OFF state (that is. not
CLEARED),
Format:

SET LINE line-id

Loading options:

ALL
[CONTROLLER] CSR csr-address
DEAD T I MER milliseconds
DELAY T I MER milliseconds
DUPLEX jFULL}
\HALF
[LOCATIONJjFIRSTFIT}
lTOPDOWN
MULTIPOINT DEAD dead-ratio
PRIOR I TY hardware-priority
UNIT CSR csr-address
VECTOR vector-address

Loaded options:

CONTROLLER

LOOPBACK}
NORMAL

OWNER

1-106

DECnet-RSX Guide to Network Management Utilities

where
LINE line-id

Specifies the line to be loaded and for which parameters
are to be created or modified.

STATE

(Invalid for V~P) Sets a PSI line's operational state to
OFF or ON.

Loading options:

ALL

Loads the line wi th all of the defaul t parameters specified
in the permanent database. If you specify ALL. you
cannot include any other parameters.

CONTROLLER
CSR
csr-address

Specifies the address of the first CSR for the
line controller.

DEAD TIMER
milliseconds

(For DECnet DMP/DMV multipoint control lines only)
Specifies the polling interval for a dead tributary (range:
1 to 65.535).

DELAY TIMER
milliseconds

(For DECnet DMP/DMV multipoint control lines only)
Specifies the minimum time to delay between polls in
order to limit the effect of a fast control station on a
slow tributary (range: 1 to 65.535).

DUPLEX

(D ECnet D DC~1 P lines only) Sets the hardware
transmission mode to full duplex or half duplex.

LOCATION

(Invalid for VNP) Specifies the type of dynamic memory
allocation.
FIRSTFIT

(Default) Loads the driver process at the
first available space that is large enough
in the partition.

TOPDOWN

Loads the dri ver process at the top of the
partition.

Network Management Utilities (CFE, NCP, VNP)

1·107

MULTIPOINT
DEAD
dead-ratio

(DECnet non-DMP/DlVIV multipoint control lines only)
Specifies the polling rate for a tributary in the
dead multipoint state (range: 1 to 255).

PRIORITY
hardware-priority

Specifies the hardware priority of the controller
(range: 4 to 7).

UNIT CSR
csr-address

Specifies the address of the first CSR for a
DECnet device controlled by a KMC-ll.
NOTE

With the KD P. a unit CSR can be specified for any unit on
the controller.
With the KDZ. a unit CSR can be specified only for the first
unit set in the associated DZ multiplex group.
VECTOR
vector-address

Specifies the vector address of the line
controller. You must use the vector address selected on
the device or 0 if the address is unknown (range: 0 to
774 octal).

Loaded options:

CONTROLLER

(For DMC/DlVIR. DMP. DHU. DRV, QNA. and UNA
lines; invalid for VNP) Specifies the controller mode for
the line. The line's circuit must be in the OFF state
LOOPBACK

Internal device loopback mode

NORlVIAL

Normal operating mode

COUNTER
TIMER
seconds

(PSI lines only. invalid for VNP) Sets a timer
whose expiration causes the line counters to be
logged and zeroed (range: 0 to 65.535).

OWNER

Specifies line ownership.

1·108

D LX

D LX (See the DECllet-RSX Programmer's
Reference Manual.)

PLI

PSI (Invalid for VNP)

DECnet-RSX Guide to Network Management Utilities

Example:

NCP>SET LINE SDP-O OWNER PLI
This command sets the owner of line SD P-O as PLI. which assigns the line
for PSI operations only.

Network Management Utilities (CFE, NCP, VNP)

1·109

NCP/VNP
P

SET LOGGING

Use the NCP SET LOGG ING command to create or modify logging component
parameters in the volatile database. Use the VNP command to do the same
with the system image file.
Restriction:

Whenever a circuit. line. module. node. or sink is specified in a SET LOGG ING
command. an event list or KNOWN EVENTS parameter must also be included.
Format:

JSTATE

SET ~NOWN LOGGING
LOGGING CONSOLE
LOGGING FILE
LOGGING MONITOR

NAME name

{g~F}

EVENTS list
KNOWN EVENTS

where
KNOWN
LOGGING

Indicates that the specified parameters are to be
created or modified for all known logging components.

LOGGING
CONSOLE

Indicates that the specified parameters are to be
created or modified for the console logging component.

LOGGING

FILE Indicates that the '3pecified parameters are to be
created or modified for the file logging component.

LOGGING
MONITOR

Indicates that the specified parameters are to be
created or modified for the monitor logging component.

1·110

DECnet-RSX Guide to Network Management Utilities

NAME name

Specifies the name of the console (default: COO:). file
(default: LB:(1.6]EVENTLOG.sYS). or monitor program
(default: ~'lON ... ) to which events are to be logged.

STATE

Sets the operational state of the logging component on
the executor node. When the state is OFF. events are
discarded.

EVENTS
et:ent-list

Specifies the event class and type(s) to be
logged.

KNOWN
EVENTS

Specifies that all events that DECnet-RSX can
generate are to be logged.

CIRCUIT
circllit-id

(Invalid for VNP) Logs the specified event(s)
occurring on the specified circuit (see restriction).

LINE line-id

Logs the specified event(s) occurring on the specified line
(see restriction).

MODULE

(Invalid for VNP) Logs the specified event(s) occurring
on the specified module (see restriction).

NODE node-id

Logs the specified event(s) occurring on the specified
node (see restriction).

SINK

Identifies the node where the specified event(s) are to be
logged (see restriction).
EXECUTOR

(Default) Executor node

NOD E node-id

The specified remote node

NODE $HOST

Host node

Network Management Utilities (CFE, NCP, VNP)

1-111

Examples:

NCP>SET KNOWN LOGGING KNOWN EVENTS CIRCUIT DMC-O SINK NODE BOSTON
This command dictates that known events on circuit DiVIC-O be sent to node
BOSTON.

NCP>SET LOGGING CONSOLE EVENT 2.1 SINK NODE ATL
This command dictates that any occurrence of event 2.1 be logged on the
console at node ATL.

1-112

DECnet-RSX Guide to Network Management Utilities

NCP

p
SET MODULE
X25-ACCESS

Use the SET MODeLE X~5-ACCESS command to specify a destination name
for a remote DTE In the volatile database.
Format:

where
DESTINATION
dest-name

Specifies a destination name for the identified
remote DTE address.

NUMBER
dte-address

Specifies the remote DTE address to be
associated with the specified destination name.

SCOPE scope

See definition in Section 1.5.2.

Example:

NCP>SET MODULE X25-ACCESS DESTINATION RDG724 -<RET>
NCP>NUMBER 41106700200 SCOPE TERMINAL TT51:
This command (shown in continuation format) sets a destination name of
RDG724 for DTE address 41106700200 at terminal TT51.

Network Management Utilities (CFE, NCP, VNP)

1-113

NCP

p
SET MODULE
X25-PROTOCOL

Use the SET MODULE X25-PROTOCOL command to create or modify DTE
or group parameters in the volatile database.
Format:

where
DTE-related parameters:

DTE
dte-address

Sets parameters for the specified local DTE only.
See RSX-l1 PSI Netloork-specific Information for the
address format on your network.

KNOWN DTES

Sets parameters for all local DTEs.

COUNTER
TIMER seconds

Sets a timer whose expiration causes the DTE
counters to be logged and zeroed (range: 1 to 65,535).

STATE

Sets the local DTE' s operational state.
OFF

Nat available.

Available for normal use.

SHUT Not available for new virtual circuit connections;
turns off when the last virtual circuit disconnects.

1-114

DECnet-RSX Guide to Network Management Utilities

Group-related parameters:

GROUP
group-name

Sets parameters for the specified group only.

KNOWN
GROUPS

Sets parameters for all known groups.

DTE
dte-address

Specifies the local DTE associated with the
specified group. This parameter must be used with a
group number.

NUMBER
group-number

Specifies a 2-digit closed user group (CUG)
number or a 4-digit bilateral closed user group (BCUG)
number (range: 0 to 9999; you can omit leading zeroes).
This parameter must be used wi th a DTE address.

TYPE
BILATERAL

Required when the specified group is bilateral (BCUG).

Example:

NCP>SET MODULE X25-PROTOCOL GROUP CUG247 NUMBER 95 -<RET>
NCP>DTE 16175554236

This command (shown in continuation format) assigns group number 95 to
closed user group CUG247 on DTE 16175554236.

Network Management Utilities (CFE, NCP, VNP)

1-115

NCP/VNP

NCP

p
SET MODULE
X25·SERVER

p
SET MODULE
X29·SERVER

Use the NCP SET l\tl0DULE X25/X29-SERVER commands to create or modify
server module parameters in the volatile database. Use the V~P SET MODULE
X25-SERVER command to change the server module state in the system image
file. (There is no VNP SET MODULE X29-SERVER command.)
Restrictions:

• The STATE parameter is valid only for SET lVIODCLE X25-SERVER
commands. It is the only valid parameter for V~P.
• You cannot modify parameters for existing destinations. You can only create
new destinations. Existing destinations can be cleared. then reset with new
parameters. If you specify a destination name. you must also specify the
object.
• If you specify CALL MASK or CALL VALUE, you must specify both, and
the hex-value of each must contain the same number of digits.
Format:

where
COUNTER TIMER Sets a timer whose expiration causes the server
seconds
module counters to be logged and zeroed (range: 0 to
65.535).
STATE

1·116

(Valid only for X25-SERVER commands)
module's operational state.

Sets

the

DECnet-RSX Guide to Network Management Utilities

OFF

Not available.

A vailable for normal use.

SHUT

(Invalid for VNP) Not available for new
virtual circuit connections; turns off when
the last virtual circuit disconnects.

DESTINATION
dest-name

Specifies the destination for which server
parameters are to be created.

OBJECT
ob;ect-id

Specifies the task that runs when an incoming call
activates it. Use either an object name or an object type
code to identify the task. See Section 1.5.2.

CALL MASK
hex-value

CALL VALUE
hex-value

Specifies a string of information used to test
incoming call data (default: no test string). Use a
hexadecimal string of 2 to 32 digits (must be an even
number of digits); see restrictions.

GROUP
group-name

Specifies the name of a closed user group (CUG)
or a bilateral closed user group (BCUG) (default: no
group).

NUMBER
dte-address

Specifies the remote DTE that originates the
call for the specified destination (default: no DTE).

PRIORITY
priority

SUBADDRESSES
range

Specifies a range of local DTE subaddresses that
identifies the destination for the incoming call.

Network Management Utilities (CFE, NCP, VNP)

1-117

Examples:

NCP>SET MODULE X25-SERVER STATE SHUT
This command makes the module unavailable for new virtual circuit connections
and turns it off when the last virtual circuit disconnects.

NCP>SET MODULE X29-SERVER COUNTER TIMER 600
This command sets the module counter timer to 600.

1·118

DECnet-RSX Guide to Network Management Utilities

NCP/VNP
P

SET NODE

Use the NCP SET NODE command to create or modify parameters in the
volatile database for down-line loading and up-line dumping to the specified
node. If you are not performing service operations on the node. N A~IE is the
only meaningful parameter. Use the VNP command to associate a node name
with a node address in the system image file. For more information on down-line
loading and up-line dumping. see the DECnet-RSX Network Management
Concepts and Procedures manual.
Restriction:

NAME is the only valid parameter for VNP.
Format:

SET NODE node-id

DIAGNOSTIC FILE
ADDRESS node-address
DUMP ADDRESS address
DUMP COUNT number
DUMP FILE file
HARDWARE ADDRESS E-address
HOST node-id
LOAD FILE file
NAME node-name
SECONDARY [LOADER] fik
SERVICE CIRCUIT circuit-id
SERVICE DEVICE deuice-tvpe
SERVICE NODE VERSION fPHASE III}
lPHASE IV
[SERV I CE ] PASSWORD service-password
TERT I ARY
[ LOADER] file

where
NODE node-id

Specifies the node for which parameters are to be
created or modified.

ADDRESS

Specifies a node address to be associated with the
name given in node-id.

Network Management Utilities (CFE, NCP, VNP)

1-119

DIAGNOSTIC FILE
file

DUMP ADDRESS
address

DUMP COUNT
number

DUMP FILE
flle-id

HARDWARE
ADDRESS
E-address

(For Ethernet nodes only) Specifies the file to be
read when the node is down-line loaded and requests
diagnostics.
Specifies an octal address in memory at which to
begin an up-line dump of the node (range: 0 to 77777
(octal)).
Specifies the default number of blocks to up-line
dump from the node (range: 0 to 65535 decimal).
Specifies the file that is to receive a copy
of the system when the node is up-line dumped.
Identifies the Ethernet hardware address that was
originally assigned to the DEUN A controller
for the system on the node. This address is used
during operations such as down-line load to
communicate with the system before it has set up
its physical address.

HOST node-id

Specifies (for the executor node) the node from which
the executor receives its services. or represents (for
the adjacent node) the host identification received by
the node when it is down-line loaded (default:
executor node).

LOAD FILE
file

Specifies a file containing the system software
for down-line loading to the node.

NAME

Specifies a node name to be associated with the

node-name

node-id.

SECONDARY
LOADER

Specifies a file containing secondary loader
software for down-line loading to the node.

file

1-120

DECnet-RSX Guide to Network Management Utilities

SERVICE
CIRCUIT
circuit-id

Specifies the circuit to be used for down-line
loading and up-line dumping. This circuit is
the default value for the VIA parameter of the LOAD
command.

SERVICE DEVICE
device-type

Specifies the line controller for the service line
over which the operation is to take place. Possible
devices are:
DA
DL
DLV

DlVIC
DMP
DlVIV

DPV
DU
DUP

KDZ

DZ
KDP

QNA
UNA

(

SERVICE ~ODE
VERSION

Specifies the node as a Phase III or Phase IV
(default) node.

SERVICE
PASSWORD
seruicepassword

Specifies the password required to trigger the
bootstrap mechanism on the node.

TERTIARY LOADER
file

Specifies a file containing tertiary loader
software for down-line loading to the node.

Example:

NCP>SET NODE 12 NAME BLAKE
This command assigns the name BLAKE to node 12.

Network Management Utilities (CFE, NCP, VNP)

1·121

NCP/VNP
P

SET NODE CIRCUIT

Use the NCP SET ~OD~~ CIRCUIT command to associate a DECnet circuit
with a loop node name in the volatile database. Use the VNP command to
do the same with the system image file.
Restriction:

The circuit-id used in this command cannot specify an Ethernet circuit; loop
nodes are not supported for Ethernet circuits. For more details about loop
nodes. see the DECnet-RSX iVetwork Management Concepts and Procedures
manual.
Format:

SET

NODE node-name

C I RCU I T circuit-id

where
NODE
node-name

Specifies the loop node with which the circuit is
to be associated.

CIRCUIT
circuit-id

Specifies a DECnet circuit to be used for
all traffic to the specified loop node.

Example:

NCP>S£T NODE LASVGS CIRCUIT DMP-O.2
This command sets node LASVGS as the loop node name for circuit DMP-O.2.

1·122

DECnet-RSX Guide to Network Management Utilities

NCP/VNP

P
SET OBJECT

Use the NCP SET OBJECT command to create or modify object parameters
in the volatile database. lJ se the VNP command to do the same with the
system image file.
Format:

SET OBJECT type-code

COPIES fnumber
lSINGLEJ
NAME object-name
USER JDEFAULT}
LLOGIN
VERIFICATION {INSPECT}
OFF
ON

where
OBJECT
type-code

Specifies the object for which parameters are to
be created or modified.

COPIES
number

Specifies the maximum number of copies of a task
that can be run at once (range: 2 to 64). Use the keyword
SINGLE (default) if the task is not multicopy.

NAME
object-name

Specifies a name to be associated with the object.
Use any valid RSX task name. If the task is multicopy,
the name must end with $$$.

USER

Specifies the UIC under which a task is to run when
the object's VERIFICATION option is set to ON or
INSPECT.

VERIFICATION

DEFAULT

(Default) The task runs under the default
UIC under which it was built or installed.

The task runs under the log-in UIC.

Specifies the degree of access to the controlled object.

Network Management Utilities (CFE, NCP, VNP)

1·123

INSPECT

Allows access to the object while
indicating to it whether or not the access
control information is valid.

OFF

(Default) Allows access to the object
regardless of the validity of the access
control information.

Allows access to the object only for
inbound connections with valid access
control information.

Example:

NCP>SET OBJECT 19 USER LOGIN VERIFICATION ON
This command specifies that object 19 is to run under the log-in VIC and
that access is to be allowed only with valid access control information.

1·124

DECnet-RSX Guide to Network Management Utilities

NCP/VNP

P
SET PROCESS

Use the NCP SET PROCESS command to load processes and to modify process
parameters in the volatile database. With NCP. a network process remains in
memory until you clear the system or the process (see CLEAR SYSTEM and
CLEAR PROCESS) or until you reboot the system. Us€ the VNP SET
PROCESS command to load processes and to modify process parameters in
the system image file.
Restrictions:

• If you reload NW after clearing it. you must also issue the SET lVIODULE

X25-PROTOCOL command (first with STATE OFF and then with STATE
ON) to update the process pointers to the database.
• Data space is allocated within the process's addressing space only.
Format:

SET PROCESS process-name ALL
[LOCATION]JFIRSTFITl
lTOPDOWN
MAXIMUM CONTROLLERS count
MAXIMUM LINES count
P ART I T ION partition-name

where
PROCESS
process-name

Specifies the process for which parameters are to
be modified.

ALL

Loads the process with all process parameter defaults
specified in the permanent database. If you specify ALL.
you cannot include any other parameters.

Network Management Utilities (CFE, NCP, VNP)

1-125

LOCATION

(Invalid for VNP) Specifies the type of dynamic memory
allocation for the driver process.
FIRSTFIT

(Default) Loads the process at the first
available space that is large enough.

TOPDOWN

Loads the process at the top of the
partition.

MAXIMUl\1
CONTROLLERS
count

Specifies the maximum number of hardware controllers
(range: 0 to 64) for which the process
is to allocate data space (see restrictions).

MAXIMUM
LINES
count

Specifies the maximum number of lines (range:
a to 64) for which the process is to allocate data
space (see restrictions).

PARTITION
partition-name

Specifies the partition name. Use a name
consisting of 1 to 6 Radix-50 characters.

Example:

NCP>SET PROCESS DPV MAXIMUM LINES 2
This command limits process DPV to the control of two lines.

1·126

DECnet-RSX Guide to Network Management Utilities

NCP/VNP

p
seT SYSTEM

Use the NCP or VN P SET SYSTE1\1 command to load the Communications
Executive and the volatile database into the system. The volatile database is
loaded from the permanent database. which includes all the network process.
line. circuit. module. and node defaults that have been set or defined.
Restriction:

On RSX-IIM/1\'I-PLGS systems. you must have installed NTINIT using VMR
before you can execute a VNP SET SYSTE1\'I command.
Format:

SET SYSTEM [TOP]
where

TOP

(Invalid for VNP) Specifies that the system be loaded at
the top of memory.

Network Management Utilities (CFE, NCP, VNP)

1·127

NCP

p
SET TRACE

Use the SET TRACE command to start tracing the specified PSI line(s). For
more information on the trace interpreter task. see Chapter 9. Note that only
one trace file can be active at a time. To turn off tracing. use the CLEAR
TRACE command.
Format:

where
LINE line-id

Sets tracing for the specified line only.

ACTIVE LINES

Sets tracing for all active lines.

BUFFER SIZE
block-count

Specifies the size (in 32-word blocks) of the
trace buffer used to collect trace data (range: 1 to 255;
default: 4).

FILE file

Specifies the name of the file to which trace data is to
be copied (default: LB:[1.6]PSITRACE.SYS).

Example:

NCP>SET TRACE LINE SDP-O STATE ON BUFFER SIZE 10
This command turns tracing on for line SDP-O and allocates a lO-block buffer
in which to collect trace data.

1-128

DECnet-RSX Guide to Network Management Utilities

NCP/VNP
NP
SHOW ALIAS

Use the NCP SHO\V ALIAS command to display alias mformation stored in
the volatile database. Use the VNP command to do the same with the system
image file.
Format:

SHOW {ALL ALIASES ~rCHARACTERISTICSJ [[ SCOPE] scope] [TO/ile]
AL I AS alias-name ~UMMARY
KNOWN ALIASES

where
ALL ALIASES

Displays information for all aliases.

ALIAS
alias-name

Displays information for the specified
alias only.

KNOWN ALIASES

Displays information for all aliases for
the specified scope (default scope is your
terminal).

CHARACTERISTICS

See definitions in Section 1.5.2.

SUM~IARY

SCOPE scope

(Invalid for ALL ALIASES) See definition
in Section 1.5.2.

TO flle

(Valid for Nep only) See definition
Section 1.5.2.

Example:

NCP>SHOW ALIAS SMITH CHARACTERISTICS TERMINAL TT24: -<RET>
NCP>TO LB: [1,9]ALIAS.SYS
This command (shown in continuation format) directs static display information
for alias SMITH on terminal TT24: to file LB:[1.9]ALIAS.SYS.

Network Management Utilities (CFE, NCP, VNP)

1-129

NCP
NP
SHOW AREA

Use the NCP SHOW AREA command to display area information stored In
the volatile database.

Format:

SHOW

AREA area-number
ACTIVE AREAS
KNOWN
AREAS
{
SIGNIFICANT AREAS

CHARACTERISTICS}
STATUS
{ SUMMARY

[TO file]

where

AREAS
area-number

Displays information for the specified area
only.

ACTIVE AREAS

Displays information for all active areas.

KNOWN AREAS

Displays information for all areas.

SIG NIFICANT
AREAS

Dispiays information for all areas for which
information is available.

CHARACTERISTICS
STATUS
SUMMARY

See definitions in Section 1.5.2.

TO file

See definition in Section 1.5.2.

Example:

NCP>SHOW AREA 4 CHARACTERISTICS
This command displays static information for area number 4.

1·130

DECnet-RSX Guide to Network Management Utilities

NCP/VNP
NP
SHOW CIRCUIT

Use the NCP SHOW CIRCUIT command to display circuit information stored
in the volatile database. Use the VNP command to do the same with the
system image file.
Format:

SHOW

where

I RCU I T circuit-id
ACTIVE CIRCUITS
KNOWN CIRCUITS
SIGNIFICANT CIRCUITS

~HARACTER
I ST I CJ
COUNTERS

[TO {ile]

STATUS
SUMMARY

CIRCUIT
circuit-id

Displays information for the specified
circuit only.

ACTIVE
CIRCUITS

(Invalid for VNP) Displays information
for all active circuits.

KNOWN CIRCUITS

Displays information for all known
circuits.

SIGNIFICANT
CIRCUITS

(Invalid for VNP) Displays information
about all circuits for which information is
available.

CHARACTERISTICS
COUNTERS
STATUS
SUMMARY

See definitions In Section 1.5.2.

TO {ile

(Valid for NCP only) See definition in
Section 1.5.2.

Example:

NCP>SHOW ACTIVE CIRCUITS COUNTERS
This command displays circuit error and performance statistics for all active
circ:uits.

Network Management Utilities (CFE, NCP, VNP)

1·131

NCP/VNP
NP
SHOW EXECUTOR

Use the 0JCP SHO\iV EXECGTOR command to display local node information
stored in the volatile database. Use the VNP command to do the same with
the system image file.
Format:

SHOW EXECUTOR

HARACTERISTICSJ

[TO file]

COUNTERS
STATUS
SUMMARY

where
CHARACTERISTICS
COUNTERS
STATUS
SUMMARY

See definitions in Section 1.5.2.

TO file

(Valid for NCP only) See definition
Section 1.5.2.

III

Example:

NCP>SHOW EXECUTOR STATUS

This command displays local node dynamic information.

1·132

DECnet-RSX Guide to Network Management Utilities

NCP/VNP
NP
SHOW LINE

Use the NCP SHOvV LINE command to display line information stored in
the volatile database. Use the VNP command to do the same with the system
image file.
Format:

SHOW {L I NE line-id
}
ACTIVE LINES
KNOWN LINES
SIGNIFICANT LINES
where

HARACTERISTICSJ

[TO lile]

COUNTERS
STATUS
SUMMARY

LINE line-id

Displays information for the specified line
only.

ACTIVE LINES

(Invalid for VNP) Displays information
for all active lines.

KNOWN LINES

Displays information for all known lines.

SIGNIFICANT
LINES

(Invalid for VNP) Displays information
about all lines for which information is
available.

CHARACTERISTICS
COUNTERS
STATUS
SUMMARY

See definitions in Section 1.5.2.

TO file

(Valid for NCP only) See definition in
Section 1.5.2.

Example:

NCP>SHOW LINE DMC-l SUMMARY TO LB: [l,6]LINSUM.SYS
This command directs the most useful information about line D M C-l to a file
named LB:[1,6]LINSUM.SYS.

Network Management Utilities (CFE, NCP, VNP)

1-133

NCP/VNP
NP
SHOW LOGGING

Use the NCP SHOW LOGGING command to display logging mformation
stored in the volatile database. Use the VNP command to do the same with
the system image file.
Format:

SHOW

ACTIVE LOGGING
KNOWN LOGGING
LOGGING CONSOLE
LOGGING FILE
LOGGING MONITOR
SIGNIFICANT LOGGING

HARACTERISTICJ

[TO lile]

STATUS
SUMMARY
EVENTS

rKNOWN SINKS
1
Ls I NK NODE flode.tdJ

where
ACTIVE LOGGING

(Invalid for VNP) Displays all active
logging information.

KNOWN LOGGING

Displays information for all known logging
components.

LOGGING
CONSOLE

Displays information for the console
logging component.

LOGGING FILE

Displays information for the file logging
component.

LOGGING
MONITOR

Displays information for the monitor
logging component.

SIGNIFICANT
LOGGING

(Invalid for VNP) Displays logging
information about all sink types for which
information is available.

CHARACTERISTICS
STATUS
SUl\IMARY

See definitions in Section 1.5.2.

1·134

DECnet-RSX Guide to Network Management Utilities

EVENTS

Displays event class and type information
for the given logging component.

TO file

(Valid for NCP only) See definition in
Section l.5.2.

KNOWN SINKS

(Default) Displays logging information for
all known sink nodes.

SINK NODE
node-id

Displays logging information for the
specified sink node only.

Example:

NCP>SHOW LOGGING FILE EVENTS SINK NODE CHI42
This command displays event class and type information for the logging file
on node CHI42.

Network Management Utilities (CFE, NCP, VNP)

1-135

NCP/VNP
NP
SHOW MODULE
X2S-ACCESS

Use the NCP SHOW MODULE X25-ACCESS command to display remote
DTE destination information stored in the volatile database. Use the VNP
command to do the same with the system image file.
Format:

where
ALL DESTINATIONS

Displays information for all destinations.
regardless of scope.

DESTINATION
dest-name

Displays information for the specified
destination only.

KNOWN
DESTINATIONS

Displays information for all known
destinations within the specified scope.

CHARACTERISTICS
SUMMARY

See definitions in Section 1.5.2.

SCOPE scope

See definition in Section 1.5.2.

TO file

(Valid for NCP only) See definition in
Section 1.5.2.

Example:

NCP>SHOW MODULE X25-ACCESS ALL DESTINATIONS CHARACTERISTICS
This command displays static information for all destinations.

DECnet-RSX Guide to Network Managemem Utilities

NCP/VNP
NP
SHOW MODULE
X25·PROTOCOL

Use the NCP SHOW MODeLE X25-PROTOCOL command to display protocol
module information stored in the volatile database. Cse the v~p command to
do the same with the system image file. Some types of information can be
qualified by either DTE or group.
Format:

where
DTE
dte-address

Displays information for the specified
DTE only.

KNOWN DTES

Displays information for all known OTEs.

GROUP
group-name

Displays information for the specified
group only.

KNOWN GROUPS

Displays information for all known groups.

CHARACTERISTICS
COUNTERS
STATUS
SUMl\IARY

See defimtions in Section 1.5.2.

TO file

(Valid for NCP only) See definition
Section 1.5.2.

Network Management Utilities (CFE, NCP, VNP)

ill

1-137

Example:

NCP>SHOW MODULE X25-PROTOCOL KNOWN GROUPS SUMMARY
This command displays the most useful information about all known groups
in the network.

1·138

DECnet-RSX Guide to Network Management Utilities

NCP/VNP
NP
SHOW MODULE
X2S-SERVER

SHOW MODULE
X29-SERVER

Use the NCP SHOW l\IODULE X25/X29-SERVER commands to display server
module information stored in the volatile database. l'se the VNP commands
to do the same with the system image file. Some types of information can be
qualified by destination.
Format:

where
DESTINATIO~

dest-name

Displays information for the specified
destination only.

KNOWN
DESTINATIONS

Displays information for all known
destinations.

CHARACTE RISTICS
COUNTERS
STATUS
SUMMARY

See definitions in Section 1.5.2.

TO file

(Valid for NCP only) See definition
Section 1.5.2.

Network Management Utilities (CFE, NCP, VNP)

1-139

Examples:

NCP>SHOW MODULE X25-SERVER COUNTERS TO LB: [l,6]X25CTR.SYS
This command directs the error and performance statistics for the module to
a file named LB:[1.6]X25CTR.SYS.

NCP>SHOW MODULE X29-SERVER DESTINATION CHI55 CHARACTERISTICS
This command displays static module information for destination CHI55.

1-140

DECnet-RSX Guide to Network Management Utilities

NCP/VNP
NP
SHOW NODE

Use the NCP SHOW NODE command to display node information stored in
the volatile database. Use the VNP command to do the same with the system
image file. See the SHOW EXECUTOR command for executor node displays.
Restriction:

No information will be displayed for an end node until a link has been
established to it. The node may appear to be unreachable even when it is not.
Format:

SHOW

NODE node-id
ACTIVE NODES
ADJACENT NODES
KNOWN NODES
LOOP NODES
SIGNIFICANT NODES

HARACTERI STI C

COUNTERS
STATUS
SUMMARY

[TO file]

where
NODE node-id

Displays information for
node only.

ACTIVE NODES

(Invalid for VNP) For a routing node,
displays information for all reachable
nodes. For a nonrouting node, displays
information for all nodes that are (1)
adjacent. (2) designated routers, or (3)
connected to the executor by a logical
link.

KNOWN NODES

Displays information for all known nodes.

LOOP NODES

Displays information for all loop nodes.

SIGNIFICANT
NODES

(Invalid for VNP) Displays information
about all nodes for which any information
is available.

Network Management Utilities (CFE, NCP, VNP)

the specified

1·141

See definitions in Section 1.5.2.

CHARACTERISTIC'S
COUNTERS
STATUS
SCMl\IIARY

(Valid for NCP only) See definition in
Section 1.5.2.

TO lile

Example:

NCP>SHOW KNOWN NODES COUNTERS
This command displays error and performance statistics for all known nodes.

1·142

DECnet-RSX Guide to Network Management Utilities

NCP/VNP
NP
SHOW OBJECT

Use the NCP SHOyV OBJECT command to display object information stored
in the volatile database. Use the VNP command to do the same with the
system image file.
Format:

SHOW JOBJECT type-COde}
lKNOWN OBJECTS

CHARACTERISTICS]
[SUMMARY

[TO lite]

where
OBJECT
type-codf?

Displays information for the specified
object only.

KNOWN OBJECTS

Displays information for all known objects.

CHARACTERISTICS
SUMMARY

See definitions in Section 1.5.2.

TO file

(Valid for NCP only) See definition In
Section 1.5.2.

Example:

MCP>SHOW OBJECT 25
This command displays only the most useful information about object 25.

Network Management Utilities (CFE, NCP, VNP)

1·143

NCP/VNP
NP
SHOW PROCESS

Use the NCP SHO\V PROCESS command to display process information stored
in the volatile database. Use the VNP command to do the same with the
system image file.
Format:

SHOW ~PROCESS process-name}
ACTIVE PROCESSES
KNOWN PROCESSES

STATUS 1
[ SUMMARyJ

[TO /'ile]

where

PROCESS
process-name

Displays information for the specIfied process
only.

PROCESSES

(Invalid for VNP) Displays information for all
acti ve processes.

KNOWN

Displays information for all known processes.

ACTIVE

PROCESSES
STATUS
SUMMARY

See definitions in Section 1.5.2.

TO file

(Valid for NCP only) See definition in Section 1.5.2.

Example:

NCP>SHOW PROCESS KDP STATUS
This command displays dynamic information for process KD P.

1·144

DECnet-RSX Guide to Network Management Utilities

NCP/VNP
NP
SHOW SYSTEM

Use the NCP SHOvV SYSTEl\1 command to display system information stored
in the volatile database. Use the VNP command to do the same with the
system image file.
Format:

SHOW SYSTEM

HARACTERISTICJ

[TO lile]

COUNTERS
STATUS
SUMMARY

where

CHARACTERISTICS
COUNTERS
STATUS
SUMl\IARY

See definitions in Section 1.5.2.

TO file

(Valid for NCP only) See definition in
Section l.5.2.

Example:

NCP>SHOWSYSTEM COUNTERS
This command displays system error and performance statistics.

Network Management Utilities (CFE, NCP, VNP)

1·145

NCP
NP
SHOW TRACE

Use the SHOW TRACE command to display trace infornlation stored in the
volatile database (see Chapter 9 for more information on the trace utility).
Trace information is kept only for PSI lines.
Format:

where
STATUS
S UlVllVI AR Y

See definitions ill Section 1.5.2.

TO file

See definition in Section 1.5.2.

Example:

NCP>SHOW TRACE TO LB: [1,6]TRACE.SYS
This command directs a summary (by default) of trace information to file
LB:[ 1.6 ]TRACE .SYS.

1-146

DECnet-RSX Guide to Network Management Utilities

NCP
NP
TELL

Use the TELL prefix to send an NCP command to a remote node for execution.
TELL sets the executor for only one command and must prefix the command
for which it is intended. The TELL part of the command always executes at
the local node. even though the executor may be set to a remote node
identification. You can specify access control information (if required) to connect
to the remote node.
Format:

TELL

node-id [ ace-eon-info]

ncp-command

where
node-id

Specifies the node. by na_me or alias. to receIve and
execute the NCP command.

ace-eon-info

Specifies access control information (if required) to
connect to the node. (See format description in Section
1.5.2.)

ncp-command

Represents any valid NCP command that is remotely
executable. The DECnet-RSX LVetwork Management
Reference Card lists all NCP commands and flags those
that are not executable remotely.

Example:
NCP>TELL BOS LOAD rJODE ALB

This command sends the LOAD NODE command to node BOS. where it
executes.

Network Management Utilities (CFE. NCP, VNP)

1-147

NCP

p
TRIGGER NODE

Use the TRIGGER NODE command to trigger the bootstrap mechanism of
a node so that the node loads itself. This command initiates the loading
sequence for an unattended system. For information on down-line load
operations. see the DECnet-RSX IVetll.)Ork Alanagement Concepts and
Procedures manual.
Format:

TR I GGER NODE node-id

V I A circuit-id
PHYS I CAL ADDRESS E-address
[ SERV I CE] PASSWORD service-passluord

where

NODE node-id

Specifies the node whose bootstrap is to be triggered.

VIA circuit-id

Specifies the circuit over which the operation is to take
place.

PHYSICAL
ADDRESS
E-address

SERVICE
PASSWORD
servicepassword

Specifies the password required to trigger the
bootstrap mechanism on the node.

NOTE

If you do not want a password echoed to your terminal while
you enter it. press the RETURN key after the keyword
PASSWORD. NCP prompts for the password and turns off
echoing until the next prompt.

1·148

DECnet-RSX Guide to Network Management Utilities

Examples:

NCP>TRIGGER NODE NYC
This command triggers the bootstrap mechanism on node ~YC to initiate a
down-line load.

NCP>TRIGGER NODE NYC VIA DMC-O PASSWORD SASASASA
This command provides service password 5A5A5A5A to trigger the bootstrap
mechanism on node NYC and initiate a down-line load over circuit D MC-O.

Network Management Utifities (CFE, NCP, VNP)

1-149

NCP

p
TRIGGER VIA

Use the TRIGGER VIA command to trigger the bootstrap mechanism of a
node so that the node loads itself. This command initiates the loading sequence
for an unattended system by triggering the node via the specified circuit. The
node identification is obtained from the volatile database on the executor node.
For information on down-line load operations. see the DECnet-RSX iVetluork
Management Concepts and Procedures manual.
Format:

TRI GGER VIA circuit-id

PHYS I CAL ADDRESS E-address
[SERVICE] PASSWORD sen' ice-password

where

VIA
circuit-id

Specifies the circuit over which the
operation is to take place.

PHYSICAL
ADDRESS
E-address

SERVICE
PASSWORD
servicepassword

Specifies the password required to trigger the
bootstrap mechanism on the node.

NOTE

If you do not want a password echoed to your terminal while
you enter it. press the RETURN key after the keyword
PASSWORD. NCP prompts for the password and turns off
echoing until the next prompt.

1-150

DECnet-RSX Guide to Network Management Utilities

Examples:

NCP>TRIGGER VIA DMC-O
This command triggers the bootstrap mechanism on the node connected to
circuit DlMe-O.

NCP>TRIGGER VIA DMC-O PASSWORD FFFFFFFF
This command provides service password FFFFFFFF to trigger the bootstrap
mechanism on the node connected to circuit D~iC-O.

Network Management Utilities (CFE, NCP, VNP)

1-151

NCP

p
ZERO CIRCUIT

Use the ZERO CIRCUIT command to zero circuit counters for the specified
circuit(s). The executor node maintains these counters on a per circuit basis.
Format:

ZERO

I RCU I T Circuit-id} [COUNTERS]
lKNOWN CIRCUITS

where
CIRCUIT
circuit-id

Zeroes counters for the specified circuit only.

KNOWN
CIRCUITS

Zeroes counters for all known circuits.

Example:

NCP>ZERO CIRCUIT DMC-O
This command zeroes circuit counters for circuit DMC-O.

1·152

DECnet-RSX Guide to Network Management Utilities

NCP

P
ZERO EXECUTOR

Use the ZERO EXECC"TOR command to zero node counters associated with
and maintained on the executor node.
Format:

ZERO EXECUTOR [COUNTERS]

Network Management Utilities (CFE, NCP, VNP)

1-153

NCP
P

ZERO LINE

Use the ZERO LI~E command to zero line counters for the specified line(s).
The executor node maintains these counters on a per line basis.
Format:

ZERO

f LINE Iine-id l [COUNTERS]
'lKNOWN LINES!

where
LINE line-id

Zeroes counters for the specified line only.

KNOWN LINES

Zeroes counters for all known lines.

Example:

NCP>ZERO LINE DUV-3
This command zeroes line counters for line DUV-3.

1-154

DECnet-RSX Guide to Network Management Utilities

NCP

P
ZERO MODULE
X25·PROTOCOL

Use the ZERO MODULE X25-PROTOCOL command to zero module counters
for the specified DTE(s). The executor node maintains these counters on a per
DTE basis.
Format:

where
DTE
dte-address

Zeroes counters for the specified DTE only.

KNOWN DTES

Zeroes counters for all known DTEs.

Example:

NCP>ZERO MODULE X25-PROTOCOL DTE 123456789

This command zeroes X.25 protocol module counters for DTE 123456789.

Network Management Utilities (CFE, NCP, VNP)

1-155

NCP

p
ZERO MODULE
X25·SERVER
ZERO MODULE
X29·SERVER

Use the ZERO MODULE X25/X29-SERVER commands to zero X.25/X.29
server module counters that are maintained on the executor node.
Format:

1-156

DECnet-RSX Guide to Network Management Utilities

NCP

P
ZERO NODE

Use the ZERO NODE command to zero node counters for the specified node(s).
The executor node maintains node counters un a per node basis.
Format:

ZERO fNODE node-id }[ COUNTERS]
"lKNOWN NODES

where
NODE node-id

Zeroes counters for the specified node only.

KNOWN NODES

Zeroes counters for all known nodes.

Example:

NCP>ZERO NODE GEERT
This command zeroes node counters for node GEERT.

Network Management Utilities (CFE. NCP. VNP)

1·157

NCP

P
ZERO SYSTEM

Use the ZERO SYSTElVI command to zero system counters associated with
and maintained on the executor node.
Format:

ZERO SYSTEM [COUNTERS]

1-158

DECnet-RSX Guide to Network Management Utilities

1.5.4 RSX-11S NCP Command Summary
This section summanZf-'~ flU' \(,P commands that are supported by RSX-llS.
CFE and VNP cannot bt.· u..;pd on an RSX-llS system directly. however. they
can be used to modify ..m R~X-llS system image stored on a host system.
The supported \"CP eommands are a subset of the commands supported on
RSX-lllVI and RSX-ll M-PLUS operating systems. Unless otherwise noted in
the restriction section of an individual command description. all of the following
commands can be initiated both locally (that is. at the RSX -lIS node) and
remotely (not at the RSX-llS node).
The commands are presented in alphabetical order. using the <::;ame definitions
described in Section 1.6.2. To distinguish this subset from the full set. NCP/S
is printed at the top of each page above the command name. In addition, each
command is designated as privileged (P) or nonprivileged (NP).

DECnet-RSX Guide to Network Management Utilities

1-159

NCP/S
NP
LOOP EXECUTOR/NODE

Use the LOOP NODE command to test a node in the network. You can include
access control information if the node requires it. If you are testing the
executor node. you can use the LOOP EXECUTOR command. Either command
causes test blocks of data to be transmitted to the specified node. See the
DECnet-RSX Network l'vlanagement Concepts and Procedures manual for more
information on loopback testing.
Format:

LOOP INODE node-id[acc-con-infoll
lEXECUTOR

COUNT count
LENGTH length
WITH

tMIXED
ONES
ZEROES

where
NODE node-id

Specifies a node for loopback testing.

acc-con-in/o

Specifies access control information. if required.

EXECUTOR

Specifies the executor node for loop back testing.

COUNT count

Specifies the number of blocks to be sent during loopback
testing (range: 1 to 65535; default: 1 block is looped).

LENGTH
length

Specifies the length (in bytes)
of blocks to be sent during loopback testing. When testing
over the Ethernet. the length must be a decimal integer
in the range of 32 to 1484. Otherwise. the length must
be a decimal integer in the range of 1 to n. where n
must be less than the smaller of ei ther the local looper
buffer size or the remote mirror buffer size (default: 40
bytes).

WITH

Specifies the type of binary information to be sent during
testing (default: MIXED -- a combination of ones and
zeroes).

1-160

Network Management Utilities (CFE, NCP, VNP)

Example:

NCP>LOOP NODE NYC COUNT 10

This command loops 10 blocks of mixed test messages to remote node 0JYC.
Each block is 40 bytes.

DECnet-RSX Guide to Network Management Utilities

1-161

NCP/S

P
SET CIRCUIT

Use the SET CIRCCIT command to set the operational state for the specified
circuit in the volattle database
Format:

SET CIRCUIT c/rcui/-Id STATE {~~F}
where
CIRCUIT
circuit-id

Specifies the circuit whose state IS to be set.

STATE

Sets the circuit's operational state to ON or OFF.

Example:

NCP>SET CIRCUIT KDZ-1-3 STATE OFF
This command sets the state of circuit KDZ-1-3 to OFF.

1·162

Network Management Utilities (CFE, NCP, VNP)

NCP/S

p
SET EXECUTOR HOST

Use the SET EXECCTOR HOST command to specify a host node in the
volatile database.
Format:

SET EXECUTOR HOST{llOde-addreSS}
$HOST
$ LOCAL

where
HOST
node-address

Specifies the address for the host node or
the local node to be used for down-line load. trigger. and
up-line dump service operations.

Example:

NCP>SET EXECUTOR HOST 08
This command sets node 08 as the host node for down-line load. trigger. and
up-line dump.

DECnet-RSX Guide to Network Management Utilities

1-163

NCP/S

p
SET LINE

Use the SET LI~E command to set the controller mode for a specified loaded
line in the volatile database
Restrictions:

•

SET LINE cannot be mitiated from a remote node.

•

The specified line must be in the OFF state (that is, not CLEARED).

Format:

SET LINE line-id CONTROLLER fLOOPBACK}
LNORMAL
where
LINE line-id

Specifies the line for which the controller mode is to be
specified.

CONTROLLER

For Ethernet, DJ\IC/DMR. DMP. DHU, and DHV lines;
Specifies the controller mode for the line. The line's
circuit must be in the OFF state.
LOOPBACK

Internal device loop back mode

NOR!tIAL

Normal operating mode

Example:

NCP>SET LINE DMC-O CONTROLLER LOOPBACK
This command sets the operating mode for line DMC-O to loopback mode.

1-164

Network Management Utilities (CFE, NCP, VNP)

NCP/S
P
SET LOGGING CONSOLE

Use the SET LOGG I~G CONSOLE command to modify the operational state
of the logging console in the volatile database.
Format:

SET LOGGING CONSOLE STATE{g~F}
where
STATE

Sets the operational state of the logging console on the
executor node. When the state is OFF. events are
discarded.

Example:

NCP>SET LOGGING CONSOLE STATE OFF
This command sets the state of the logging console to OFF.

DECnet-RSX Guide to Network Management Utilities

1-165

NCP/S
NP
SHOW CIRCUIT

Use the SHOW CIRCUIT command to display circuit information stored in
the volatile database.
Restriction:

ACTIVE, SIGNIFICANT. and KNOWN CIRCUITS cannot be initiated locally.
Format:

SHOW

where

I Reu I T circuit-id
}
ACTIVE CIRCUITS
KNOWN CIRCUITS
SIGNIFICANT CIRCUITS

uOUNTERJ
STATUS
SUMMARY

CIRCUIT
circuit-id

Displays information for the specified circuit
only.

ACTIVE CIRCUITS

Displays information for all active circuits.

KNOWN CIRCUITS

Displays information for all known circuits.

SIGNIFICANT
CIRCUITS

Displays information for all significant
circuits.

COU~TERS

See definitions in Section 1.5.2.

STATUS
SUMMARY
Example:

NCP>SHOW CIRCUIT DMC-O COUNTERS

This command displays error and performance statistics for circuit DMC-O.

1·166

Network Management Utilities (CFE, NCP, VNP)

NCP/S
NP
SHOW EXECUTOR

Use the SHO\V EXECUTOR command to display local node information stored
in the volatile database.
Format:

SHOW EXECUTOR

HARACTERISTICJ

COUNTERS
STATUS
SUMMARY

where
CHARACTERISTICS
COUNTERS
STATUS
SUMMARY

See definitions in Section 1.5.2.

Example:

NCP>SHOW EXECUTOR STATUS
This command displays local node dynamic information.

DECnet-RSX Guide to Network Management Utilities

1·167

NCP/S
NP
SHOW LINE

Use the SHOW LINE command to display line information stored in the
volatile database.
Restriction:

ACTIVE LINES. SIGNIFICANT LINES. and
initiated locally.

K~OW~

LINES cannot be

Format:

SHOW

~~~~V~ne~:NES

{

}

KNOWN LINES
SIGNIFICANT LINES

r~~~~~~Rsl

L~UMMARY

where
LINE line-id

Displays information for the specified line only.

ACTIVE LINES

Displays information for all active lines.

KNOWN LI~ES

Displays information for all known lines.

SIGNIFICANT
CIRCUITS

Displays information for all significant
circuits.

COUNTERS
STATUS
SUMMARY

See definitions in Section l.5.2.

Example:

NCP>SHOW LINE DMC-l SUMMARY

This command displays the most useful information about line DMC-l.

1-168

Network Management Utilities (CFE. NCP, VNP)

NCP/S

NP
SHOW LOGGING CONSOLE

Use the SHOW LOGG ING CONSOLE command to display dynamic logging
console information stored in the volatile database.
Format:

SHOW LOGGING CONSOLE STATUS
where
STATUS

~CP only;

displays dynamic information for the specified

component.

DECnet-RSX Guide to Network Management Utilities

1·169

NCP/S
NP
SHOW NODE

Use the SHOv\' \rODE command to display node information stored in the
volatile database. See the SHOW EXECUTOR command for executor node
displays.
Restrictions:

•

ACTIVE NODES and K~OWN NODES cannot be initiated locally.

•

No information will be displayed for an end node until a link has been
established to it. The node may appear to be unreachable even when it is
not.

•

Only name and address static characteristics kept on lIS.

Format:

SHOW ~NODE node-id
ACTIVE NODES
KNOWN NODES

CHARACTERISTICJ
COUNTERS
[ STATUS
SUMMARY

where
NODE node-id

Displays information for the specified node only.

ACTIVE NODES

Displays information for all active nodes.

KNOWN NODES

Displays information for all known nodes.

CHARACTERISTICS
COUNTERS
STATUS
SUMMARY

See definitions in Section 1.5.2.

Example:

NCP>SHOW NODE LOSANG COUNTERS
This command displays error and performance statistics for node LOSANG.

1-170

Network Management Utilities (CFE, NCP, VNP)

NCP/S
NP
SHOW SYSTEM

Use the SHOW SYSTEl\1 command to display system information stored in
the volatile database.
Format:

SHOW SYSTEM

CHARACTERISTIC
COUNTERS
[ STATUS
SUMMARY

where
CHARACTERISTICS
COUNTERS
STATUS
SUMMARY

See definitions in Section l.5.2.

Example:

NCP>SHOW SYSTEM COUNTERS

This command displays system error and performance statistics.

DECnet-RSX Guide to Network Management Utilities

1-171

NCP/S

P
ZERO CIRCUIT

Use the ZERO CIRCUIT command to zero circuit counters for the specified
circuit(s). The executor node maintains these counters on a per clrcuit basis.
Restriction:

KNO\VN CIRCUITS cannot be initiated locally.
Format:

ZERO

Ic I RCU I T circuit-idl [COUNTERS]

'lKNOWN CIRCUITSj
where
CIRCUIT
circuit-id

Zeroes counters for the specified circuit only.

KNOWN CIRCUITS

Zeroes counters for all known circuits.

Example:

NCP>ZERO CIRCUIT DUP-O
This command zeroes circuit counters for circuit DUP-O.

1-172

Network Management Utilities (CFE, NCP, VNP)

NCP/S
P

ZERO EXECUTOR

Use the ZERO EXECCT()H command to zero node counters associated with
and maintained on the exeCULor node.
Format:

ZERO EXECUTOR [COUNTERS]

DECnet-RSX Guide to Network Management Utilities

1·173

NCP/S

p
ZERO LINE

Use the ZERO LINE command to zero line counters for the specified line(s) ..
The executor node maintains these counters on a per line basis.
Restriction:

KNOWN LINES cannot be initiated locally.
Format:

ZERO JLINE line-id

[COUNTERS]

lKNOWN LINES!
where
KNOW~

LINES

LINE line-id

Zeroes counters for all known lines.
Zeroes counters for the specified line only.

Example:

NCP>ZERO LINE DUV-3
This command zeroes line counters for line DUV-3.

1-174

Network Management Utilities (CFE, NCP, VNP)

NCP/S
P

ZERO NODE

Use the ZERO NODE command to zero node counters for the specified node(s).
The executor node maintains node counters on a per node basis.
Restriction:

This command cannot be initiated locally.
Format:

ZERO

NODE node-id }
LKNOWN NODES

[COUNTERS]

where
NODE Ilode-id

Zeroes counters for the specified node only.

KNO\VN NODES

Zeroes counters for all known nodes.

Example:

NCP>TELL NETllS ZERO KNOWN NODES
This command zeroes node counters for all known nodes.

DECnet-RSX Guide to Network Management Utilities

1-175

NCP/S

P
ZERO SYSTEM

Use the ZERO SYSTEl\I command to zero system counters associated with
and maintained on the executor node.
Format:

ZERO SYSTEM [COUNTERS]

1·176

Network Management Utilities (CFE, NCP, VNP)

2
Console Carrier Requester (CCR)

The console carrier requester (CCR) uses the DLX interface to communicate
with the console carrier server (CCS) residing on a target node to provide
remote access to normal console services. More information about the use of
CCR can be found in the DECnet-RSX Network Management Concepts and
Procedures manual.

2.1 Running CCR
To use CCR use the following command·
CCR NODE node-id

SERVICE CIRCUIT circuit-id
SERVICE PASSWORD password
PHYSICAL ADDRESS E-address

where
NODE node-id

specifies the target node by address (range: 1 to
1023) or name (1 to 6 alphanumeric characters,
including at least 1 alphabetic character).

SERVICE CIRCUIT
circuit-id

identifies the circuit to the target node.
(circuit-id has the format dev-c[-u][.t].)

SERVICE PASSWORD
password

defines the password required to access the target
node. The password is a hexadecimal number in
the range of 0 to FFFFFFFFFFFFFFFF (up to
16 hexadecimal digits).

2-1

PHYSICAL ADDRESS
E-address

identifies the Ethernet physical address that the
node currently uses to identify itself. (Required
It the hardware address parameter has not been
sp~dfied in the volatile database; see the SET
)\JUDE command in Chapter 1.)

The node-id is required. If the other parameters are not specified in the
command line, they must be specified in the down-line load database. If they
are specified in the command line. they override the parameter'; set in the
down-line load database.

2.2 CCR Special Characters
Two special characters are supplied with the CCR software

<CTRL/B) - Operates as a BREAK command to get the attention of the
console on-line debugging tool (ODT).

<CTRL/D) - Initiates an exit from console carrier mode.

2.3 CCR Error Handling
CCR error messages are listed in Chapter 10.

2-2

DECnet-RSX Guide to Network Management Utilities

3
Event File Interpreter (EVF)

The Event File Interpreter (EVF) is part of the event logging facility provided
by DECnet-RSX. This facility enables you to collect events in a
machine-readable file for later formatting by EVF. The event collector and
Event File Interpreter are similar to the Error Logger and Error Report
Generator provided by RSX -11 M/M -PLUS.

3.1 Invoking EVF
Any user can use EVF to create a formatted event listing because EVF is a
nonprivileged task. EVF can be invoked using either the DeL CLI or the
MeR eLI. To invoke EVF using the DeL CLI type the following command:
ANALYZE/EVENT _LOG [qualifiers] [input _fUe]
where qualifiers is a list of command qualifiers and input _file is the name of
the input file.
There are three methods of invoking EVF using the MCR eLI:
1. MCR>EVF

EVF then prompts:
EVF>

Enter an EVF command immediately following the prompt. If the command
executes successfully, the utility will redisplay the prompt on the next line.
If an error occurs, an error message is displayed indicating the reason for the
error followed by a prompt.
3·1

2. MCR>EVF command

where command is a valid EVF command. With this method you will return
to MCR after the command is executed.
3. MCR>EVF @command-/'ile

where command-file is the name of an indirect command file containing valid
EVF commands. Command files can be nested up to six deep. You will return
to MCR after the commands in the file(s) have been executed.

3.2 Exiting EVF
To exit the EVF utility. enter <CTRL-Z> In response to the utility prompt.

3.3 EVF Command Format
The EV F command line has the following format:
DCl format: ANAL YZE/EVENT _LOG [quali/'iers] [in/lie]
MCR format: EVF [out/lle ][olltput-switches ] = [in/lIe ][input-switches]

where:
outfile

is the output file name. If this file is not specified. the output
file defaults to EVENTLOG.LST in the current VIC. This
file will contain the formatted events.

ill file

is the input file name. If this file is not specified. the input
file defaults to LB:[1.6]EVENTLOG.SYS. This file contains
the machine-readable events. The file is generated by using
the NCP SET LOGG ING FILE command. For information
on logging and NCP control of logging see the DECnet-RSX
Netu)orh Management Concepts manual and the NCP
command descriptions in Chapter 1.

qualifiers

is one or more of the command qualifiers shown in Table 3-1
and 3-2. For more information on the use of these qualifiers.
see the description of input-switches.

output-switches

is one or more of the switches shown in Table 3-1. These
switches control the output of the file.

3-2

DECnet-RSX Guide to Network Management Utilities

input-switches

is one or more of the switches shown in Table 3-2. These
switches control which events in the event logging file will
be formatted by EVF. The switches allow for event filtering
based on the time of the event. the entity the event is
associated with. the type of event. and the source node of
the event. Many of the switches have a positive and a negated
form. The positive form (Isw) causes all events specified by
the switch to be formatted. The negated form (/-sw or INOsw)
causes all events EXCEPT those specified by the switch to
be formatted. Most of the filtering switches allow an
argument to be specified with the switch (lsw:argwnent). The
switches can be combined to provide a greater degree of event
filtering; however. care must be taken to avoid specifying
too many event filters in order to avoid generating an empty
report.

3.3.1 Using the EVF Default Command Line

To use the EVF default command line, enter the following command:
DCl format: DCL>ANALYZE/EVENT _LOG
MCR format: EVF> = (RET>

This command causes EVF to use the file specification defaults and qualifier
or switch defaults. In general this command creates a full format report using
all the events in the event log file.
The EVF default command line invokes the following qualifiers or switches:
DCl qualifier:
MCR switch:

IFULL
IFORMAT:FULL

Creates a full format report containing the complete event information for
each event.
DCl qualifier:
MCR switch:

fALL
fALL

Creates a report with all events found In the error log file.

Event File Interpreter (EVF)

3-3

3.4 EVF Option Descriptions
This section describes in detail the EVF options. These options tell EVF the
type of filtering desired on events as well as govern the disposition of the
files used during the operation requested.
When using the MeR eLI. these options are specified as switches that are
appended to either the input or output file name depending on which file the
switch affects. You also have the option of using the default file names by
specifying the switches without any input or output file name. The MeR
swi tches may be abbreviated to the first two letters of the switch name. If
the switch is abbreviated to one letter you will receive the following error
message:
Unknown switch - s

where.') is the one letter switch.
When using the DeL eLI. the options are specified as command qualifiers
and the qualifiers are classified as input or output qualifiers only to indicate
their logical use.
The EVF output options are summarized in Table 3-1. The EVF input options
are summarized in Table ~3-2.
Table 3-1: EVF Output Options
MCR Switch

DCL Qualifier

Function

(specified in command)

IOUTPUT:{ilename

Specifies output file
name

ISPOOL

Controls output file
spooling

IFORMAT:BRIEF

IBRIEF

Specifies brief report

IFORMAT: FULL

IFULL

Specifies full report

3-4

DECnet-RSX Guide to Network Management Utilities

Table 3-2: EVF Input Options
MCR Switch(See Note 1)

DCl Qualifier

Function

IDELETE

Controls input file
disposition

fALL

Selects all events

fDATE:PREVIOUS:n_days
IDATE :RANGE :start:end

IPREVIOUS:n _days

Selects time frame
for formatting

fDATE:TODA Y
IDATE:YESTERDA Y

fTODAY
fYESTERDAY

fENTITY:ALL

fSINCE:start
fTHROUGH:end

fENTITY:AREA[:arca-id]
fENTITY:AREA[:area-id]
IENTITY:CIRCUIT[:cir-id]
IENTITY:C IRCUIT[:cir-id]
IENTITY:LINE[:lille-id]
IENTITY:LINE[:line-id]
IENTITY: MODULE[:mod-id]/ENTITY :MOD ULE[:mod-id]
IENTITY:NODE[:llode-id]
IENTITY:NODE[:llode-idJ

Selects entity
(See Note 2)

IENTITY:NULL

fEVENT:euent-id

IEVENT:euent-id

Selects event types
for formatting (See
Note 2)

fSOURCE :Ilode-id

ISOURCE :node-id

Selects source node
for formatting (See
Note 2)

1. All MCR switches and switch argument keywords must be at least two
letters.
2. The IENTITY, IEVENT, and ISOURCE options can have multiple arguments
as described in Section 3.4.1.

Event File Interpreter (EVF)

3-5

3.4.1 Using Multiple Option Arguments

You can specify each EVF option only once in a command line. However. the
same options provide an alternative syntax that allows you to specify a list
of arguments for the option. The options that support multiple arguments are
shown in Tables 3-1 and 3-2.
To specify more than one argument for an EVF option that allows multiple
arguments, use the following command syntax:
/option:(argument 1 ,argument2.... argumentn)

The parentheses. which are a required part of the command syntax, allow
EVF to use more than one argument for the option. If you do not use the
parenthesis. EVF displays the following error message on your terminal:
Command line syntax error
For example, to specify multiple event types. use the following EVF option:
/EVENT:(4.*,5.*,6.*)

EVF will format all events for event classes 4. 5. and 6.
3.4.2 File Control Options

The file control options determine the disposition of the files after the execution
of the EVF command.

3-6

DECnet-RSX Guide to Network Management Utilities

3.4.2.1 The Output File Option MeR Format:

DeL Format:

(Specified in command)

IOUTPUT:{ilename

Default:

EVENTLOG.LST

IOUTPUT:EVENTLOG .LST

The OUTPUT option is only available when using DCL. This option specifies
the output file name that EVF is to use. When using MCR you specify the
output file name as part of the command syntax.
3.4.2.2 The Spooling Option MeR Format:

DeL Format:

ISP[OOL]
I-SP[OOL]

IS POOL
INOSPOOL

INOSP[OOL]
Default:
I-SP

INOSPOOL

The SPOOL option is used to control the spooling of the resultant formatted
file. If the SPOOL option is used the file will be spooled to the system line
printer.

Event File Interpreter (EVF)

3·7

3.4.2.3 The Delete Option MCR Format:

DCL Format:

IDE[LETE]
I-DE[LETE]
INODE[LETE]

IDELETE
INODELETE

Default:
I-DE

INODELETE

The DELETE option is used to control the disposition of the input file. If
the DELETE option is used the input file will be deleted after formatting is
complete.
3.4.3 Output File Format Control
MCR Format:

DCl Format:

IFO[RMAT]: BR[IEF]
FU[LL]

IBRIEF
IFULL

Default:

IFO:FU

IFULL

The FORMAT option (or BRIEF and FULL option in DeL) is used to control
the format of the output file.
The BRIEF argument (or BRIEF option in DeL) causes an abbreviated event
description to be used for all events formatted in the report. This shortened
form consists of the first three lines of the event text.
The FULL argument (or FULL option in DeL) causes the entire event text
to be included in the report.

3-8

DECnet-R8X Guide to Network Management Utilities

3.4.4 Event Selection Options

The following options are used to make a selection of the events to be formatted.
You can select events based on the time of the event, the entity type, the
event type, and source node of the event. These options can be combined to
further limit the events formatted.
3.4.4.1 The All Event Option MeR Format:

Del Format:

IAL[L]

fALL

Default:

fALL

IAL

The ALL option specifies that all events are to be formatted. This option has
the effect of specifying fDATE:RA::.:. ENT[TY:AL, EVENT::: .*, and
SOURCE:'.':.
3.4.4.2 The DATE Options MeR Format:

Del Format:

IDA[TE]:PR[EVIOUS]:ll_days
RA[NG E]:start:clld

/PREVIOUS:n days
/SINCE :start
fTHROUG H:end
fTODAY
fYESTERDAY

TO[DAY]
YE[STERDA Y]
Default:

IDA:RA:*::'

/SINCE :·',/THROUG H:·::

The DATE option allows you to select events based on the date that an event
occurred. This option includes arguments to specify a range of dates or to
specify a particular day.
The RANGE argument (or SINCE and THROUGH options In DCL) accepts
starting and ending dates in the standard RSX format:
DD-MMM-YY or (DD-MMM-YY HH:MM:SS)

Event File Interpreter (EVF)

3·9

When you use the date only format. EVF uses a starting time of 00:00:00
and an ending time of 23:59:59. If you use the second format. you must
include the parentheses.
In MeR command lines the asterisk (*) can be used at the beginning of a
range specification to indicate any date through the specified ending date. For
example, *:12-MAR-85 specifies all events from the beginning of the event
file through March 12, 1985 are to be formatted.
In MeR command lines the asterisks (*) can be used at the end of a range
specification to indicate any date since the specified starting date. For example.
23-FEB-85:* specifies all events since February 23, 1985 are to be formatted.
You may not combine the arguments of the MCR DATE switch. You can
combine the SINCE and THROUGH qualifiers when using DCL.
3.4.4.3 The Entity Filter Option MCR Format:

DCl Format:

IEN[TITY]:AL[L]

IENTITY:ALL
ARE A[ :area-idJ

AR[EA][:area-id]

CI[RCUIT][:cir-id]
LI[NE][:line-id]
MO[DULE][:mod-id]
NO[DE][:node-idJ

CIRCUIT[:cir-id]
LINE[:line-idJ
MOD ULE[:mod-id]
NODE[:'llode-id]

NU[LL]

NULL

Default:

IENTITY:ALL

IEN:AL

The ENTITY option allows you to select events based on the entity type.
This option includes arguments to specify the entity type desired as well as
the ALL argument. The arguments (with the exception of the ALL argument)
can be negated using the -argument(MCR only) or NOarglllnent syntax. The
arguments can be combined using the syntax described in Section 3.4.1. For
example:

/ENTITY:(CIRCUIT,LINE,NONODE:4.456)
will cause EVF to format all circuit and line events and node events for all
nodes except node 4.456.

3·10

DECnet-R8X Guide to Network Management Utilities

For a list of the entities associated with each event, see the DECnet-RSX
Network Management Concepts manual.
NOTE

Although you may specify multiple option arguments or the
IENTITY option. you cannot specify more than one specific ID

value for anyone of the arguments.
The following is a detailed description of each of the IENTITY option
arguments.
• The ALL argument specifies that there is to be no entity filtering. The
ALL argument cannot be negated.
• The AREA argument allows filtering on area entity events. You can specify
an area ID in the range 0-63. The negated form of this argument
(NOAREA:area-id) will cause all events EXCEPT the specified area events
to be included in the report.
• The CIRCUIT argument allows filtering on circuit entity events. You can
specify a circuit [D of the form deu-etl[-ullit ][.trib] where dcL' is the device
name, etl is the controller number. unit is the unit number. and trib is the
tributary address. When specifying the circuit ID. you can use the wildcard
symbol C) for ctl. unit. or trib. If you specify a wildcard symbol. you cannot
specify any explicit values for the parameters following the wildcard symbol
(ie. PCL-. is correct, PCL-.O is not correct). The negated format of this
argument (NOCIRCUIT:cir-id) will cause all events EXCEPT the specified
circuit events to be included in the report.
• The LINE argument allows filtering on line entity events. You can specify
a line ID of the form del. -etl[-unit] where deu is the device name, ctl is the
controller number. and unit is the unit number. When specifying the line
ID. you can use the wildcard symbol C) for ctl or unit. If you specify a
wildcard symbol for ctt. you cannot specify an explicit value for unit. (ie.
DZ-- is correct, DZ--O is not correct). The negated form of this argument
(NOLINE:tine-id) will cause all events EXCEPT the specified line events to
be included in the report.
1

Event File Interpreter (EVF)

3·11

• The MODULE argument allows filtering on module entity events. You can
specify a module ID where the module ID is an alphanumeric string. The
negated form of this argument (NOMOD ULE :module-id) will cause all events
EXCEPT the specified module events to be included in the report.
• The NODE argument allows filtering on node entity events. You can specify
a node ID where the node ID is of the form [area.]number. The value for
area must be in the range 0-63 and number must be in the range 1-1023.
The node id can also be a node name. The negated form of this argument
(NONODE:node-id) will cause all events EXCEPT the specified node events
to be included in the report.
• The NULL argument allows filtering on events that do not have an entity.
The negated form of this argument (NONULL) will cause all events EXCEPT
the events without entities to be included in the report.
3.4.4.4 The Event Specification Filter Option MCR Format:

DCl Format:

IEV[ENT]: (!Uellt _type

IEVENT: euellt _type

1- EV[ENT]: eL'(!llt _tyP(!

INOEVENT:event _type

INOEV[ENT]:event _type
Default:
IEV:*.'::

IEVENT:'::.::·

The EVENT option allows you to select events based on the event class and
type. If the negated format is used (/NOEVENT:event-type ) all events
EXCEPT those with the specified event ID will be formatted. The event-type
argument is of the form class. type where class is the event class (0-511) and
type is the event type (0-63). This option allows multiple events to be specified
using the syntax described in Section 3.4.1.
If the asterisk (*) is used for type, all events of the requested class are included
in the report.

For a list of the event classes and types associated with each event, see the
DECnet-RSX Networh Management Concepts manual.

3·12

DECnet-RSX Guide to Network Management Utilities

3.4.4.5 The Source Node Filter Option MCR Format:

DCl Format:

ISO[URCE]:node _id
I-SO[URCE]:node _id
INOSO[URCE]:node _id

ISOURCE: node id
INOSOURCE :node _id

Default:
ISO:';:.*

ISOURCE:'j:.*

The SOURCE option allows you to select events based on the source node. If
the negated format is used (/NOSOURCE :Ilode _id). EVF formats all events
EXCEPT those with a source of node _id. The node _id value is a node address
of the form [area.]number where area is in the range 1-63 and number is in
the range 0-102~L The node [D can also be a node name. This option allows
multiple nodes to be specified using the syntax described in Section 3.4.1.
[f area is not specified. only events with an area value of 0 will be formatted.
If the asterisk (:) is used for !lumber. all events in the specified area will be
formatted.

NOTE

The node identified by this option is the node that generated
the event. This node mayor may not be the node entity
associated with the event. The node argument on the ENTITY
option should be used to filter events based on the node entity
associated with the event.
3.4.4.6 ISO Switch - Specify Source Node Filter -

Format:
ISO[URCE]:node _id
I-SO[URCE]:node _id
INOSO[URCE]:node _id

Default:
ISO:*.*

Event File Interpreter (EVF)

3-13

The ISOURCE switch allows you to select events based on the source node.
If the negated format is used (I-SO:node _id or INOSO:node _id), EVF formats
all events EXCEPT those with a source of node _id. The node _id value is a
node address of the form [area.]number where area is in the range 1-63 and
number is in the range 0-1023. If area is not specified, only events with an
area value of 0 or 1 will be formatted.
If the asterisk (*) is used for number, all events In the specified area will be

formatted.
NOTE

The node identified by this switch is the node that generated
the event. This node mayor may not be the node associated
with the event. The node qualifier on the ENTITY switch should
be used to filter events based on the node associated with the
event.

3.5 EVF Error Messages
EVF prints an error message on your terminal when an invalid command
request is detected. EVF error messages are summarized in Chapter 10. EVF
also generates errors if the input file is found to be in an unreadable format.

3-14

DECnet-RSX Guide to Network Management Utilities

4
KMX/KMV Dump Analyzer (KDA)

If the performance of a KMX/KM Y device deteriorates and this cannot be
attributed to a hardware fault. you can dump the KMX/KNIY microcode for
analysis by your local software .,pecialist. The NCP KMX-DUMP command
controls the dumping of the microcode to disk (see Chapter 1). The KMX/KMY
dump analyzer task (KDA) formats and prints the contents of the KMX/KMY
dump disk file.

You must have included both the dump KMX/KMY task (D UK) and the
KMX/KMY dump analyzer task (KDA) in your system during NETGEN if
you want to use this facility. The RSX-ll PSI Generation Guide gives details
of the DUK and KDA tasks.

4.1 Invoking and Exiting KDA
Use any RSX-11 method of invoking tasks to enter KDA. The simplest method
is to type:

MCR>KDA
Once KDA is running, it returns the prompt:

KDA>
Exit from KDA by entering <CTRL/Z>.

4-1

4.2 Using the KDA Command
The KDA command has the following format:
[outfile[switches] =] [in file [switches ]]

where
outfile

IS the file specification for the analyzed dump listing file (default
is SY:[UFD]inputname.LST, where UFD is the user's default user
file directory). The = symbol marks this as the output file
specification.

infile

is the file specification for the binary input file containing the dump
(default is LB:[1,6 ]PSIKMXMElV1.SYS). Specify the same file that
you specified for the output file in the KMX-DUMP LINE
command.

switches

are options to control the listing that KDA produces. Any compatible
combination of the switches shown in Table 4-1 can be specified
for either the input file or the output file.

Table 4·1: KDA Command Switches
Comments

Switch

Meaning

IALL

Analyze and print the control memory

1- ALL

Analyze and print only the data
memory and registers

Default switch

ISP

Spool the output file

Default switch (Output
is spooled unless I-SP
specified.)

I-SP

4·2

Do not spool the output file

Output file is retained
for printing later

DECnet-R8X Guide to Network Management Utilities

Example:

>KDA
KDA>VDRTEX/ALL=DKO: [7,21]FRDGST.DMP
This command uses input file FROGST.DMP from UFD [7.21J on DKO: and
prints an analysis of control memory to output file SY:[UFD]VORTEX.LST.

KMX/KMY Dump Analyzer (KDA)

4-3

5
LAT Control Program (LCP)

This chapter discusses the Local Area Transport process (LAT) used In the
network generation procedure.
LAT control program (LCP) commands enable you to monitor and control the
LAT process on a DECnet-R8XIIM-PLUS or a DECnet-Micro/RSX service
node. Using these commands. you can:

•

CREATE the LAT terminals.

• START the LA T protocol.
• STOP the LAT protocol.
• Modify (SET) the LAT service node characteristics in the volatile database.
• Modify (DEFINE) the LAT service node characteristics in the permanent
database.

• S HO W the LA T service node characteristics in the volatile database.
• LIST the LA T service node characteristics ill the permanent database.

• SHOW the characteristics of a LAT terminal server.
• SHOW the LAT counters on the service node.
• ZERO the LAT counters on the service node.

5·1

5.1 INVOKING and EXITING LCP

You invoke the control program by typing
>LCP

The following pronlpt appears on your screen:
LCP> <RET>

Enter the LCP connnand after the prompt and press RETURN. You can also
invoke LCP and ent~f'r a command on the same line:
>LCP command ~ RET>

To exit from LCP, type EXIT or CTRL/z.
5.2 LAT Characteristics

"\Then you select LAT during the network generation procedure, the procedure
automatically writes the default characteristics to the permanent database.
When the process is started (see the START command in section 5.3.9). LCP
uses the information stored in the permanent database to set up the volatile
database. Characteristics recorded in the volatile database define the LA T
protocol to the running system.
You can make changes to the permanent database using the DEFINE command
(section 5.3.2). These changes take effect the next time the LAT process is
started. Any changes made to the volatile database using the SET command
(section 5.3.6) are effective immediately and are not saved when the LAT
process is stopped

5·2

DECnet-RSX Guide to Network Management Utilities

5.3 LCP COMMANDS: Format and Syntax
The following sections describe the format and syntax of each LCP command
and specify the default values initially assigned to the LAT parameters. For
information on how these commands affect the Ethernet. the service node. and
the LAT terminals. refer to the LAT Terminal Server Network Manager's
Guide.
As shown in Table 5- L LCP command syntax is similar to that of the Digital
Command Language (DCL).
Table 5-1: LA T Command Format

CREATE [/TERMINALS:::n]
DEFINE CHARACTERISTICS IDEVICE :::line-id
IG ROUPS ::: (group 1 ,[group2 ,... ,grollpn D
IMAXIMUM _BUFFERS::: lllllnber
IMULTICAST_ TIMER::: seconds
INODE _ IDENTIF ICATION ::: anllollncement-string
INODE _NAME::: !lode _!lame
IRECEIVE _TIMEOUT::: seconds
IRETRANSMIT _TIMER::: seconds
ISERVICE _ ID ENTIFICATION ::: annoullcement-string
ISERVICE_NAME :::seruice _flame
EXIT
HELP
LIST CHARACTERISTICS]

INODE]

SET CHARACTERISTICS]

IDEVICE :::line-id
IGROUPS::: (grollpl.[group2,,,. ,grollpnD
IMAXIMUM _BUFFERS::: !lumber
IMULTICAST _ TIMER::: seconds
INOD E _ ID ENTIFICATION ::: announcement-string
INODE _NAME::: node _name
IRECEIVE _ TIMEOUT::: seconds
IRETRANSMIT _ TIMER::: seconds
/SE RVICE _ ID ENTIFICATION ::: announcement-string
/SERVICE _NAME::: service _name

LA T Control Program (LCP)

5-3

Table 5-1 (cont.): LAT Command Format

SHOW

{CHARACTERISTICS} [lNODE]
{COUNTERS}
[/SERVER[ = server _name]]

START

IDEVICE =line-id
IGROUPS = (groupl[,group2, ... ,groupn)]

IMAXIMUM _BUFFERS = number
IMULTICAST _ TIMER = seconds
INODE _IDENTIFICATION = announcement-string
INODE_NAME = node _name
IRECE IVE _ TIMEOUT = seconds
IRETRANSMIT _ TIMER = seconds
ISERVICE _ IDENTIFICATION = anllowlcernellt-string
ISERVICE _N AME = service _name

STOP IALL
IDEVICE = line-id

ZERO COUNTERS

INODE

ISERVER[ = server-name]

5-4

DECnet-RSX GuiJje to Network Management Utilities

5.3.1 CREATE

Use the CREATE command to create the system data structures to support
the LAT terminals. Before issuing the CREATE command make sure that the
communication executive is loaded.
NOTE

You must issue the CREATE command before using the START
command.
Once the LA T terminals are added to the system. they cannot be removed
until the system has been rebooted.
Format:

CREATE [/TERMINALS = n]
where:
[/TERMINALS = n]

LA T Control Program (LCP)

Creates n terminals where n is an integer in the
range of 1 to 64. The default is 4.

5-5

5.3.2 DEFINE

Use the DEFINE command to change the LAT process characteristics in the
permanent database. The DEFINE command can execute before or after LAT
is started, but it does not affect the running system.
Format:

DEFINE CHARACTERISTICS IDEVICE = line-id
IGROUPS = (grullpl[,grollp2 ..... groupn))
IMAXIMUM _ BUFFERS = number
IMULTICAST _ TIlVIER = sccunds
INODE _ lDENTIFICATION = anllouNcement-string
INODE _NAME = node _name
IRECE lVE _ TIMEOUT = seconds
IRETRANSMIT _ TIMER = seconds
ISERVICE _ IDE NTIFICATION =allllOllllCetrlCflt-stl
ISERVICE_NAME = service _name
where:
IDEVICE =Iine-id

Specifies the Ethernet device that is to
be used for LAT connections. In a
multi-Ethernet device environment.
specify the Ethernet device to be used
for LAT terminal support. The default
is the first Ethernet line in the system.

IG ROUPS = (group 1

Sets the groups to which the host
belongs. There are 256 groups, numbered
o to 255, decimal. The default is
IG ROUP = (0). For more information on
group and group codes, see the
indi vidual server operations guides and
the LAT Network Manager's Guide.

[,group2 .... grouPll])

5·6

DECnet-RSX Guide to Network Management Utilities

IMAXIMUM _BUFFERS = number

Sets the upper limit for the number of
large data buffers (LDBs) that the LAT
process can have in use at anyone time.
For more information about LDBs and
their use in the system. see the chapter
on system buffers in the DECnet-RSX
Network Management Concepts and
Procedures manual. The default is 3.

IMULTICAST _ TIMER =
seconds

Sets the minimum rate at which the
node will send multicast messages in
seconds. The default is 20.

INODE _ ID ENTIFICATION
= announcement _string

Specifies the announcement string for
the node. It can be up to 32 characters
in length. Nonprintable characters are
translated to spaces. You must enclose
the string in double quotes (") if it
contains one or more spaces.

INODE NAME = node name

Specifies the name by which the service
node is known to the terminal servers.
The name is a string of 1 to 6
alphanumeric characters. The default is
the RSX system name.

IRECEIVE _ TIMEOUT = seconds

Sets the maximum time interval. in
seconds. that the service node waits for
a reply from a terminal server before
declaring to the server that the circuit
is "down". The default is 3.

IRETRANSMIT _TIMER
= seconds

Specifies. in seconds. the interval
between retransmission attempts. The
default is 3. For more information about
this parameter, see the LA T N etlUorh
Manager's Guide.

LA T Control Program (LCP)

5-7

ISERVICE _IDENTIFICATION
= announcement _string

Specifies the announcement string for
the service. It can be up to 32 characters
in length. N onprintable characters are
translated to spaces. You must enclose
the string in double quotes (") if it
contains one or more spaces.

ISERVICE_NAME
=service _name

Specifies the service name for the
service node. Service names allow a
service node to be known by more than
just the node name. The service name is
a string of 1 to 6 alphanumeric
characters. The default is the node name.
NOTE

Terminal server users always connect to service names, NOT
service node names.

5·8

DECnet-RSX Guide to Network Management Utilities

5.3.3 EXIT

Use the EXIT command to exit LCP.
5.3.4 HELP

Use the HELP command for help in LAT control programming.
Format:
CREATE [/terminal = n]
SET [characteristics ]host-characteristics
SHOW CHARACTERISTICS [lNODE]
SHOW COUNTERS [lNODE]
STOP [lALL]
where host characteristics are:
IDEVICE = lineid
IGROUPS = (grpll.grpll [.grpn .... ]

/MAXIMUM_BUFFERS = Il
IMULTICAST _TIMER = II
INODE IDENTIFICATION = "node announcement string"
INOD E NAME =node name
/RECEIVE _TIMEOUT = n
IRETRANSMIT _TIMER = n
ISERVICE _IDENTIFICATION = "service announcement string"
ISERVICE _NAME = servicename
IEXIT
1ST ART [host _ characteristics]

ISHOW CHARACTERISTICS/SERVER
ISHOW COUNTERS/SERVER

LA T Control Program (LCP)

5-9

5.3.5 LIST CHARACTERISTICS

Use the LIST command to display the characteristics of the LAT service node.
The LIST command displays characteristics in the permanent database. You
can use the LIST command before or after LA T is started.
Format:
LIST [CHARACTERISTICS] [lNODEl
where
INODE

Displays the characteristics of the service node.

Example:

LCP>LIST CHARACTERISTICS/NODE

causes the following display:
LCP Static Characteristics
Node name= \Boston\

Service name= \Boston\

Node Identification= \Boston-Home of the Red Sox\
Service Identification= \Boston-Home of the Red Sox\
Groups: (0)
Multicast Timer=20
Receive Timeout=3
Terminals=4

5-10

Maximum Buffers=3
Retransmit Timer=3
Device=UNA-O

DECnet-RSX Guide to Network Management Utilities

5.3.6 SET

Use the SET command to change the LAT process characteristics in the
volatile database. The SET command can execute only after the LA T process
has been started. and while it is active.
Format:

SET CHARACTERISTICS

IDEVICE =line-id
IGROUPS = (groupl.[group2,,,,,groupn)]
IMAXIMUM _BUFFERS = number
IMULTICAST _ TIMER = seconds
INODE _IDENTIFICATION = annollncement-string
INOD E _N AME = node _name
IRECE IVE _ TIMEOUT = seconds
IRETRANSMIT _TIMER = secollds
ISERVICE _IDENTIFICATION = alllwllIlccment-strillg
ISERVICE _NAME = scrvice _name

where:
IDEVICE =line-id

IG ROU PS = (group 1 [,grollp2,

Sets the groups to which the host
belongs. There are 256 groups. numbered
o to 255 decimal. The default is
IG ROUP = (0). For more information on
group and group codes. see the
indi vidual server operations guides and
the LAT Network Manager's Guide.

,,,grollpn])

LA T Control Program (LCP)

5-11

IMAXIMUM BUF·FERS = number

Sets the upper limit for the number of
large data buffers (LDBs) that the LAT
process can have in use at anyone time.
For more information about LOBs and
their use in the system. see the chapter
on system buffers in the DECnet-RSX
Network Management Concepts and
Procedures manual. The default is 3.

IMULTICAST _ TIMER = seconds

Sets the minimum rate at which the node
will send multicast messages in seconds.
The default is 20.

INODE _ IDENTIFICATION

Specifies the announcement string for
the node. It can be up to 32 characters
in length. N onprintable characters are
translated to spaces. You must enclose
the string in double quotes (") if it
contains one or more spaces.

=announcement _string

INODE NAME = node name

Specifies the name by which the service
node is known to the terminal servers.
The name is a string of 1 to 6
alphanumeric characters. The default is
the RSX system name.

IRECEIVE _ TIMEOUT = seconds

Sets the maximum time interval, in
seconds, that the service node wai ts for
a reply from a terminal server before
declaring to the server that the circuit
is "down". The default is 3.

IRETRANSMIT _TIMER
=seconds

Specifies. in seconds. the interval
between retransmission attempts. The
default is 3. For more information about
this parameter, see the LAT Network
Manager's Guide.

5-12

DECnet-RSX Guide to Network Management Utilities

ISERVICE _ IDENTIFICATION
= announcement _string

Specifies the announcement string
for the service. It can be up to 32
characters in length. Nonprintable
characters are translated to spaces. You
must enclose the string in double quotes
(") if it contains one or more spaces.

ISERVICE _NAME
= service _name

NOTE
Terminal server users always connect to serVIce names. NOT
service node names.

LAT Control Program (LCP)

5-13

5.3.7 SHOW CHARACTERISTICS

Use the SHOW command to display the characteristics of the LA T service
node or the LAT terminal server. The SHOW command displays characteristics
in the volatile database. You can use the SHOW command only after LAT is
started and while it is runlllng.
Format:

SHOW CHARACTERISTICS

INODE

ISERVER[ = server _name]
where
INODE

(Default) Displays information about the characteristics
of the service node.

Example:
LCP>SHOW CHARACTERISTICS/NODE

causes the following display:
LCP Characteristics
Node name= \Boston\
Service name= \Boston\
Node Identification= \Boston-Home of the Red Sox\
Service Identification= \Boston-Home of the Red Sox\
Groups: (0)
Multicast Timer=20
Receive Timeout=3
Terminals=4
LAT Protocol is active

5-14

LAT Version=5.0
Maximum Buffers=3
Retransmit Timer=3
Device=UNA-O

DECnet-RSX Guide to Network Management Utilities

ISERVER = server _name

Displays information about the specified server.
If you do not supply a server name, you receive
the characteristics of all servers.
LCP>SHOW CHARACTERISTICS/SERVER=GREENFIELD

causes the following display:
LCP Server Characteristics for GREENFIELD:
Ethernet address=AA-OO-03-01-05-CD
Server is active
Active Users=2

LAT Control Program (LCP)

5-15

5.3.8 SHOW COUNTERS

Use the SHOW command to display the counters which are kept by the LAT
process.
Format:

SHOW COUNTERS

INODE
ISERVER[ = server-name]

where:
INODE

(Default) Shows the counters kept for the service
node.

Example:
LCP>SHOW COUNTERS/NODE

causes the following display:
LCP Node Counters
2052
83
92
5256
3712

o
o
o

5-16

seconds since last zeroed
messages received
messages transmitted
bytes received
bytes transmitted
retransmissions
out of sequence
invalid messages
invalid slots
illegal messages
illegal slots
resource allocation errors

DECnet-RSX Guide to Network Management Utilities

ISERVER = server _name

Displays for the specified server.
If you do not supply a server
name, LCP displays the counters
of all servers.

Example:

LCP>SHOW COUNTERS/SERVER=GREENFIELD

causes the following display:
LCP Server Counter for Greenfield
2052
83
92
5256

3712

o
o

seconds since last zeroed
messages received
messages transmitted
bytes received
bytes transmitted
retransmissions
out of sequence
invalid messages
invalid slots

LA T Control Program (LCP)

5-17

5.3.9 START

Use the START command to start the LAT process and to override parameter
values in the permanent database.
NOTE

Be sure that you have loaded the communications executive and
created the LAT terminals with the CREATE command before
using the START command.
If the LAT process has not been loaded, and you issue the START command.

the following message appears on the screen:
LA T process being loaded
When you issue the START command. it creates the volatile database using
information contained in the permanent database. If you specify parameters
when you issue the START command. they are placed in the volatile database.
Format:

START

IDEVICE =line-id
IG ROUPS = (grollpl[.grollp2 ." ..groupll])

IMAXIl\1UM _BUFFERS = number
1l\1ULTICAST _ TIMER = seconds
INODE _ IDENTIFICATION = announcement-string
INODE _N Al\1E = node _name
IRECEIVE _TIMEOUT = seconds
IRETRANSMIT _ TIMER = seconds
ISERVICE _ ID ENTIFICATION = announcement-string
ISERVICE_NAME =seruice _name
where:
IDEVICE = line-id

5-18

Specifies the Ethernet device that is to
be used for LAT connections. In a
multi-Ethernet device environment,
specify the Ethernet device to be used for
LAT terminal support. The default is the
first Ethernet line in the system.

DECnet-RSX Guide to Network Management Utilities

{GROUPS = (group 1
[.group2 .... groupll])

Sets the groups to which the host
belongs. There are 256 groups, numbered
o to 255 decimal. The default is
/G ROUP = (0). For more information on
group and group codes, see the individual
server operations guides and the LAT
Network Manager's Guide.

{MAXIMUM _BUFFERS =
number

Sets the upper limit for the number of
large data buffers (LDBs) that the LAT
process can have in use at anyone time.
For more information about LD Bs and
their use in the system. see the chapter
on system buffers in the DECllet-RSX
N etu)Ork IvIallagement Concepts alld
Procedures manual. The default is 3.

IMULTICAST _ TIMEIt =
seconds

Node will send multicast messages
in seconds. The default is 20.

INODE

IDENTIFICATION
=announcement _string

Specifies the announcement string for thp
node. It can be up to 32 characters in
length. Nonprintable characters are
translated to spaces. You must enclose
the string in double quotes (") if it
contains one or more spaces.

INODE NAME = !lode flame

Specifies the name by which the service
node is known to the terminal servers.
The name is a string of 1 to 6
alphanumeric characters. The default is
the RSX system name.

IRECEIVE_ TIMEOUT=
seconds

Sets the maximum time interval. in
seconds, that the service node waits for
a reply from a terminal server before
declaring to the server that the cireui t is
"down The default is 3.
II •

LAT Control Program (lCP)

5-19

IRETRANSMIT _ TIMER
=seconds

Specifies. in seconds, the interval between
retransmission attempts. The default is 3.
For more information about this
parameter. see the LAT N eiwork
Manager's Guide.

ISERVICE _ IDENTIFICATION
= announcement _string

Specifies the announcement string for the
service. It can be up to 32 characters in
length. N onprintable characters are
translated to spaces. You must enclose
the string in double quotes (") if it
contains one or more spaces.

ISERVICE_NAME
=service _name

Specifies the service name for the service
node. Service names allow a service node
to be known by more than just the node
name. The service name is a string of 1
to 6 alphanumeric characters. The default
is the node name.
NOTE

Terminal server users always connect to service names. NOT
service node names.

5-20

DECnet-RSX Guide to Network Management Utilities

5.3.10 STOP
Use the STOP command to shut down the LAT process. Active connections
are broken without warning. You can use the RSXIIM-PLUS BROADCAST
command to warn LA T users before this command is used.
Format:

STOP

fALL
fDEVICE = line-id

where:
fALL

(Default) Stops the use of all the
associated with the LAT process.

fDEVICE = line-id

Stops all terminals associated with the particular
line.

terminals

NOTE

To stop the LAT process, use the following procedure:
1. Issue an LCP SET command with the fNODE_IDENTIFICATION
set to a message informing users the server is coming down. For
example,
LCP> SET/NODE IDENTIF[CATION = "LAT shutdown In 10
minutes."
2. Issue a broadcast command.
BROADCAST LOG: LAT shutdown In 10 minutes
3. Issue the LCP STOP command.

LA T Control Program (LCP)

5·21

5.3.11 ZERO [COUNTERS]

Use the ZERO command to zero the counters kept by the LAT process. To
test the performance of the system over a specified period of time. first zero
the counters and then analyze the information that accumulates during the
specified period.
Format:

ZERO [COUNTERS]

INODE
ISERVER[ =server-name]

where:
Zeroes the counters kept for the local node.

INODE

ISERVER

= server-name

Zeroes the counters kept for the specified server.
NOTE

The Ethernet lines that the LAT process uses also have counters.
You can show these counters with the NCP SHOW LINE
COUNTERS command and zero them with the NCP ZERO
LINE COUNTERS command (see Chapter 1 for NCP command
descriptions).

5-22

DECnet-RSX Guide to Network Management Utilities

6
Network Crash Dump Analyzer (NDA)

The Network Crash Dump Analyzer (NDA) utility helps you to determine the
cause of network crashes. NDA is a nonprivileged task for use only with
DECnet-RSX systems. including those with a PSDN capability. If you have
selected crash dump analysis support during RSX system generation, then you
can also select network crash dump analysis support during D ECnet- RSX
network generation. Refer to the RSX-JJ!vr System Generation and Installation
Guide for information on obtaining crash dump support for your operating
system. Refer to the DECllet-RS)( Network Generation and Illstallation Guide
for information on obtaining network crash dump support for DECnet-RSX.
NDA performs crash dump analysis for the network data structures in the
same way that the RSX crash dump analyzer (CDA) analyzes the operating
system data structures. Specifically, NDA compiles and analyzes information
from the system's executive symbol table file, the network symbol table file,
and the crashed system image. The information is then output in a listing
file or at a line printer in a format that is useful to you. Note that an effective
use of NDA requires an extensive knowledge of DECnet-RSX internal data
structures.
Command switches provide you with the means to control NDA operation.
There are two types of switches: analysis control switches and function control
switches. Analysis control switches determine which NDA analysis routines
are applied to the input file for analysis. These switches provide such options
as:
• Dumping the contents of a specified octal address range of memory
• Listing general system data (time of crash, registers in use. and so forth)
• Listing the routing parameters and databases
6-1

• Listing the remote node names and alias node names
• Listing PSI data structures (local and remote DTE descriptor blocks. NW:
database and window blocks. and so forth)
• Listing the network services protocol (ECL) databases
Function control switches provide a number of NDA control options. such as:
• Identifying the starting block number of the secondary storage device
• Terminating the analysis after a specified number of errors has been
encountered
• Limiting the number of pages of analysis output
• Creating a save file and transferring a specified amount of the crash dump
to it
You can type NDA commands at a terminal. or you can place them In an
indirect command file.

6.1 NDA Operation
ND A operates in the following manner:
1. First. it reads the contents of the memory dump created by the executive
crash dump routine.
2. Next. it analyzes the dump in, accordance with information contained in a
combined executive/network symbol table file.
3. Finally. it formats and outputs the dump to a line printer or a listing file
for your evaluation.

6-2

DECnet-RSX Guide to Network Management Utilities

6.2 System Requirements
To obtain a crash dump that can be handled by ND A, you must first build
the executive crash dump routine into your system during phase 1 of an
RSX -11 SYSGEN. This is accomplished by entering B in response to the
query:
50. Crash dump analysis: A- PANIC B- Crash dump analysis (CDA)

If you select this option. code is included in your system to dump memory
to a secondary storage device following a system crash. Your secondary storage
device can be anyone of a number of different types of disk units, a magtape
unit. or a DECtape unit. You can find complete information on RSX-ll
SYSGEN in the RSX-JJ M System Generation alld Installation Guide.

6.3 Obtaining a Crash Dump
To obtain a crash dump, control of the processor must be transferred to the
executi ve crash dump routine following a system crash. How this control is
transferred depends on the way in which the crash occurred and whether or
not you have built the executive debugging tool (XDT) into your system at
SYSGEN.
System crashes occur In three ways:
• The processor encounters an unintentional halt instruction (000000).
• An infinite loop condition occurs .
• The processor encounters a program condition causing it to trap.
When a system crash is the result of an unintentional halt instruction or an
infinite loop condition, you must restart your processor at location 40.
When a program condition causes a processor trap and XDT is included In
your system, control transfers automatically to XDT. When you type X at
your terminal, XDT transfers control to the executive crash dump routine.
When XDT is not included in your system, a processor trap causes control
to be transferred to the crash dump routine. Refer to the RSX-JJ ft.,1 Guide to
Writing an lIO Driver for a description of XDT.

Network Crash Dump Analyzer (NDA)

6·3

Regardless of the manner in which control is transferred, once the executive
crash dump routine is entered, it prints the following message on the crash
notification device specified during SYSGEN:

CRASH - CONT WITH SCRATCH MEDIA ON xxx
where xxx is the mnemonic for the device that is to receive the crashed system
image.
You can then put the secondary crash dump device on line and depress the
CONT switch on the CPU console. The executive crash dump routine dumps
memory to the crash dump device and halts the processor upon completion.

6.4 Running NDA
You can run NDA as either an installed or an uninstalled task.
6.4.1 Running NDA as an Installed Task

When you run ND A as an installed task, the command format that you u~e
determines where control is returned upon completion of the analysis:
• To return control to the executive:
>NDA command string
• To return control to NDA:
>NDA
NDA) command string

6.4.2 Running NDA as an Uninstalled Task

When you run NDA as an uninstalled task, control is always returned to NDA
upon completion of the analysis. The commands for running NDA are:
RUN $NDA
NDA>cornmand string

This requires NDA.TSK to be present in the user
file directory corresponding to the system UIC on
device LB:.

RUN NDA
NDA>command string

This requires NDA.TSK to be present in the user
file directory corresponding to the current UIC on
device SY:.

6-4

DECnet-RSX Guide to Network Management Utilities

6.5 NDA Command Syntax
Use the following format to input commands to NDA:
[analysis[lswl ]],[saue[lMEMSIZ:n]] = [symbols/STB][,input[lsw2]J

where
analysis

is the crash dump analysis listing file. If a file extension is
not specified. the default extension is .LST. [f an analysis file
is not specified, no analysis list file is created.

Iswl

consists of the IEXIT:n, ILIMIT:n, and I-SP function control
switches for the analysis file. A description of each switch
and its default value are given in Table 6-3.

saue

is the crash dump save file. This file is a copy of the binary
data that was written to the dump device by the dump routine.
[t allows you to create a historical record of crash dumps.

1M ElVISIZ:ll

is the number of K words of information to be transferred to
the save file. A description of the AtIEMSIZ:1l function control
switch and its default value is given in Table 6-3.

symbols/STB

is the symbol table file for the crashed system. This file must
define all executive and network symbols. A description of
ISTB and its default value is given in Table 6-3.

input

is the binary input to ND A. This specification can be ei ther
a device name (your secondary storage device) or the name of
a crash dump save file.

Isw2

consists of all the analysis control switches and three function
control switches -- IKMR, ISYl\l, and IBL:n. A description of
the analysis control switches is provided in Section 6.7.1. A
description of the IKMR, ISYM. and IBL:1l switches and their
default values is given in Table 6-3.

Output specifications (to the left of the equal sign) are position dependent.
Therefore, when you include both output specifications (analysis, save). you
must place them in the command string in the positions shown. If you do
not enter a specification for the analysis file, you must place a comma before
the save file specification. The comma can appear only if a save file is specified.

Network Crash Dump Analyzer (NOA)

6-5

Input specifications (to the right of the equal sign) are position independent
and can appear in either order.
Any of the specifications in the command string can appear in the complete
FILES-II format -- that is. complete with device. UIC. file name. file type.
and version number. When you omit any of the command specifications, NDA
uses the defaults shown in Table 6-1.
Table 6-1: NDA File Default Values

File

Device

User File
Directory Default
(UFO)
File Name

Analysis file

SY:

Current

None

.LST

Save file

SY:

Current

None

.COA

11 MIS

SY:

Current

CEX

.STB

11M-PLUS and
Micro/RSX

SY:

Current

RSXIIM

.STB

Input file

SY:

Current

None

.CDA

Value
Type

Symbols files:

6-6

DECnet-RSX Guide to Network Management Utilities

The following examples illustrate the NDA file default values. Assume that
the user in these examples is logged in under UIC [301,356] and that the
secondary storage device is DKl:. Also assume that NDA is being operated
as an installed task.
Example 1:

>NDA
NDA>18APR85,18APR85=CEX.STB/STB,DK1:/ALL
This command string creates an analysis file. IBAPR85.L8T, and a save file,
18APR85.CDA. The binary input is read from RK05 disk unit 1. NDA analyzes
it in accordance with the information contained in the symbol definition file
CEX.8TB under UFD [301.356].
Example 2:

>NDA
NDA>,13JAN85=DK1:
This command string creates a save file, 13JAN85.CDA. In this case, NDA
performs no analysis, since there is no analysis listing file. The binary input
is read from RK05 disk unit 1.
Example 3:

>NDA
NDA>13JAN85=13JAN85/ALL
This command string produces an analysis output listing using the fALL
analysis switch (see Table 6-2 for a complete description of this switch). The
binary input is read from the previously created save file (13J AN85.CDA).
NDA analyzes it in accordance with the information contained in the symbol
definition file CEX.8TB under UFD [301.356J.
Example 4:

>NDA
NDA>13JAN85,13JAN85/MEMSIZ:512=DK1:/ALL
This command string creates an analysis file named 13J AN85.LST and a save
file named 13.TAN85.CDA. The number of words of information to be
transferred is 512K words. The input file is located on RK05 disk unit l.
NDA produces an analysis output listing using the fALL analysis switch.

Network Crash Dump Analyzer (NDA)

6·7

6.6 Indirect Command Files
You can enter command strings to NO A directly from the keyboard or indirectly
through the use of the indirect command file facility. NDA indirect command
files must not contain a reference to another command file.

6.7 NDA Switches
Switches provide you with the means to control NDA operation. There are
two types: analysis control switches and function control switches.
Analysis control switches determine which NDA analysis routines are to be
applied to the input file. Some switches apply only to the DECnet software.
while others apply only to the PSI software running with DECnet on a
DECnet-RSX system with a PSDN capability.
Function control switches provide a number of NDA control options. For
example. such switches might terminate an analysis after ND A has encountered
a specified number of errors. Or, a switch might limit the number of pages
of output listing.
6.7.1 Analysis Control Switches

Table 6-2 provides a list of the analysis control switches and a brief description
of their use. More than one analysis control switch can be specified. [f none
are specified. the default is /SYS/CEX.

6-8

DECnet-RSX Guide to Network Management Utilities

Table 6-2: NDA Analysis Control Switches
Switch

Description

IALL

Executes the following switches (each IS defined later in this
table):
ICEX
ICTB
ICUG
IDST

ILDTE IOBJ
ILLS IPDV
INSP IPHB
INW IPLI

IPRO
IPSV
IPVC
IQUE

IRDTE ISYS
IREM
ITSK
IROU
IXACP
ISLT

DECnet, PSI, and X.25 Gateway components are analyzed only
if the respective software was in the system that was dumped.
IALL is the recommended switch to use. If problems occur. then
try using specific switches.
ICEX

Lists general Communications Executive data. This includes the
node name and number. the current network process, and the
current state of buffer usage.

ICTB

Prints information on all controller blocks assigned to network
devices. (This is printed only on RSX-IIM-PL US systems.)

ICUG

Prints the PSI/X.25 Gateway closed user group name blocks.

IDST

Prints the PSI/X.25 Gateway X.25 and X.29 destination blocks.

IDMP:a:b
IDUMP:a:b

Lists the contents of physical memory from octal address a
through octal address b. Both a and bare 32-bit addresses.

ILDTE

Prints the PSI/X.25 Gateway local DTE descriptor blocks.

ILlS
ILIST
ILISTS
IFREE

Scans the CCB. SDB, and RDB free lists for errors and
prints the results.

INSP

Prints the DECnet ECL databases, including the logical link
blocks.

INW

Prints the PSI NW: database and window blocks.
(continued on next page)

Network Crash Dump Analyzer (NDA)

6-9

Table 6·2 (cont.): NDA Analysis Control Switches

IOBJ
IOBJECT

Lists the network task object types.

IPDV

Prints interpreted contents of the process description vectors.

IPHB

Prints the contents of the PSI/X.25 Gateway PLI home block.

IPLI

Prints the PSI PLIIX.25 Gateway database and the X.25 circuit
blocks.

IPRO

Dumps the line tables for all loaded network processes.

IPROC
IPS V

Prints the X.25 Gateway PSV process databases,
databases, and buffer chains.

IPVC

Prints the PS IIX.25 Gateway permanent virtual circuit (PVC)
name blocks.

IQUE
IQUEUE

Lists the contents of the fork process queue.

IRDTE

Prints the PS [ remote DTE descriptor blocks.

IREM
IREMOTE

Lists the DECnet remote node names and alias names.

IROU

Lists the DECnet routing parameters, including the physical
link blocks.

IROUT
IROUTING

circuit

ISLT

Prints interpreted contents of the system line tables.

ISYS

Lists general system data. This includes the time of the crash.
the current task, and the registers in use.

ITSK
ITASK

Prints the network mailbox, window blocks, and I/O packets
for each task using the network.

IXACP

Prints the CCBs and I/O packets waiting to be processed by
the PSI X25ACP.

6·10

DECnet-RSX Guide to Network Management Utilities

6.7.2 Function Control Switches

Table 6-3 provides a list of the function control switches and a brief description
of their use. More than one function control switch can be specified. If switches
are not specified, the default values listed in Table 6-3 are assumed. Note that
when a switch requires a numeric argument. the argument is considered to be
octal unless followed by a decimal point.
Table 6-3: NDA Function Control Switches
Switch

File

Description

Default

IBL:n

Input file

Identifies the starting
block number of the
secondary storage device.
The value of n must be less
than 65535.

IBL:l

ND A reads the dump from

the input device beginning
at logical block fl. I f the
crash dump device is not a
disk or DECtape, NDA
ignores this swi tch.
IEXIT.n

Analysis file

Terminates analysis after
encountering n analysis errors.

I-EXIT

maintains an error
count. If you specify the
IEXIT:n switch. NDA
terminates analysis after It
errors. If you specify IEXIT
but do not specify fl, ND A
exits after one error.
NDA

(continued on next page)

Network Crash Dump Analyzer (N DA)

6-11

Table 6·3 (cont.): NDA Function Control Switches

IKMR

When ND A reads incorrect
page address register (PAR)
values from the crash stack,
it prints an error message
on the user's terminal and
attempts to continue with
the analysis. In this event,
you can use the IKMR
switch when you restart the
analysis.

Input file

IKMR forces NDA to use
standard mapping values to
con vert kernel virtual
addresses to physical
memory addresses.
ILIMIT:n

Analysis file

Limits the number of pages
of analysis output. When
NDA has generated fl pages,
it terminates the analysis
and prints a message on the
user terminal indicating that
it has done so.

ILIMIT:50

(continued on next page)

6·12

DECnet-RSX Guide to Network Management Utilities

Table 6-3 (cont.): NDA Function Control Switches

IMEMSIZ:n

Save file

Creates a save file 4xn
blocks long and transfers
fiK words to it from the
input file. The valid range
of decimal values for n is
from 16 to 4096.

IMEMSIZ:124

This switch is necessary
only when sa ving dumps
from secondary storage
devices that have no EOFs
(disk or DECtape). When
the crash input resides on
magtape. the save file is
zero filled if the EOF is read
before It K words have been
transferred.
I-SP

Analysis file

Causes NDA to not spool
the analysis output
listing file to the line printer.

ISP

(continued on next page)

Network Crash Dump Analyzer (NDA)

6-13

Table 6-3 (cont.): NDA Function Control Switches

ISTB

Symbols file

Identifies the file that
contains both the executive
and the network symbol
tables for the crashed
system. NDA opens the
specified file and
extracts the necessary
symbol values. If it fails
to find any required symbol
values. NDA aborts the
analysis and prints an error
message on the terminal.

CEX.STB in
the current
UIC for RSX11M;

RSXIIM.STB
in the current
UIC for RSX11M-PLUS

If no symbol is specified via
the 18TB switch. CEX.STB
under the current VIC is used.
ISYM

If any required symbols
are not found in the symbol
table file, set their values to
zero and proceed with the
analysis. Normally. this
condition would cause NDA
to abort the analysis.

Input file

I-SYM

6.8 NDA Error Messages
ND A prints an error message on your terminal when it detects an error
condition. NDA error messages are summarized in Chapter 10. Do not confuse
these messages with the diagnostic analysis messages that ND A generates
during the analysis and prints in the analysis listing.

6-14

DECnet-RSX Guide to Network Management Utilities

7
Network Display Program (NTO)

The Network Display Program (NTD) can provide three types of displays:
• A resource display of the current status of the host node or any specified
remote RSX/IAS DECnet node in the network. 1'here are two formats for
this display:
Default resource display for current DECnet-RSX systems (see Example
7-1)
Old resource display for connections to DECnet-RSX systems having
previous versions of the software (see Example 7-2)

• A node summary display of all reachable nodes or a user-specified range
of nodes in the network (available on routing nodes only -- see Example
7-3)

• An area summary display of all reachable areas in the network (available
on level 2 routing nodes only -- see Example 7-4)
You can review a continuously updated screen display on any VT100, VT52,
VT220, or VT240 terminal, or you can use NTD with a hard-copy terminal
to ~btain a listing of the display information. The displayed information is
collected by NTDEMO, a task that runs on the system for which you are
displaying information.
This chapter describes the displays and outlines the commands required to
invoke and customize the displays.

7·1

7.1 Invoking NTD
Use the following command to invoke NTD:
NTD [node-llame][/PAGE =s]
where
node-name

is a name consisting of 1 to 6 numeric or alphabetic characters,
including at least 1 alphabetic character. If you do not specify
node-name, NTD displays the status of the local node.

/PAGE =s

is a switch that specifies the display type, where s is one of
the following:
R

o
N
A

Default resource display
Old resource display
N ode summary display
Area summary display

This switch is most useful when running NTD from a hard-copy
terminal. Without this switch, you will always get a resource
display. NTD automatically checks the version of the specified
node to determine whether to display the default resource display
or the old resource display. From a VT100 or a VT52. you can
switch to a node summary display simply by entering <ESC).
Error messages that can be generated when you invoke NTD are listed in
Chapter 10.

7-2

DECnet-RSX Guide to Network Management Utilities

7.2 NTD Commands
NTD commands control various aspects of the real-time NTD displays. There
are two modes of operation for NTD commands:
• Immediate mode. With the NTD display on your screen, you enter commands

to directly manipulate the display -- for example, to control scrolling of
display information or to change to a different display.
• Command mode. When you swi tch from immediate mode to command mode.
NTD displays the commands that you can enter to customize the display
-- for example, to change the frequency of display updates or the range of
nodes for which NTD is to display information. In this mode. NTD prompts
for commands. You must return to immediate mode to view the displays.
The use of each mode and its commands is defined in the following sections.
7.2.1 Immediate Mode Commands

When you invoke NTD. you automatically enter immediate mode. Enter any
of the commands described in Table 7-1 to directly manipulate the screen
display. The terminal's bell will ring if you enter an unrecognized command.
Table 7·1: Immediate Mode Commands
Character Key

Function

Changes to default resource display

Changes to old resource display

Changes to node summary display

Changes to area summary display

Refreshes the currently selected display

Selects scrolling of node/circuit information only
(default)

Selects scrolling of task information only
(continued on next page)

Network Display Program (NTD)

7·3

Table 7·1 (cont.): Immediate Mode Commands

Selects simultaneous scrolling of node and task
information

Scrolls currently selected information forward 5
items at a time for resource displays or 10 nodes
at a time for node summary displays '"
Scrolls currently selected information backward
5 items at a time for resource displays or 10
nodes at a time for node summary displays '"

Sorts selected information in ascending order by
node address instead of alphabetically by node
name

Displays help information for immediate mode
commands for 5 seconds, then redisplays the
currently selected NTD status information

<ESC)

Enters command mode

Exits NTD

Scrolling causes information to be displayed for a range of nodes, beginning
with the next available node that is five reachable addresses ahead of (or
behind) the currently specified starting node. On the node summary display,
a maximum of H4 nodes can be displayed on the screen at once. Unless
you enter the S command (see above), nodes are displayed in alphabetic
order by name. Therefore. scrolling by node address will cause the order
to change.

7·4

DECnet-RSX Guide to Network Management Utilities

7.2.2 Command Mode Commands

When you enter (ESC> to switch from immediate mode to command mode.
the possible commands you can enter are displayed on your screen. followed
by a command prompt. Valid commands are described in Table 7-2. Enter one
command for each prompt.
Table 7·2: Command Mode Commands
Command

Function

NTIME=n

Sets the time (in seconds) between display updates for
remote nodes (default: 10 seconds)

TTIME =11

Sets the time (in seconds) between display updates for
network tasks and circuits (default: 5 seconds)

ADDRESS =11

Sets the lowest node address for which information is to
be displayed (range: 1 to 1023; default. node 1) i·

MAXIMUM=1l

Sets the highest node address for which information is
to be displayed (range: 1 to 1023; default: node 102~~) ;

HOPS = II

Sets the maximum number of hops allowed to a remote
node to be displayed (default: 31) "

COST=n

Sets the maximum cost allowed for a remote node to be
displayed (default: 1023) '::

<RET>

Reverts to the currently selected display and immediate
mode

Exits NTD

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

If you specify 0 for n, the value will revert to the specified default.

When entering these commands. you need only use a single character to
designate the command. For example, the commands ADDRESS = 4 and A = 4
both set 4 as the lowest node address for which information is to be displayed.

Network Display Program (NTD)

7·5

7.3 NTD Resource Display Format
Examples 7-1 and 7-2 are examples of the default resource display and the
old resource display, respectively. The display information fields are described
below.
Top of the screen

• The current date and time at the node where NTDEMO runs. This is updated
approximately every second.
• The name and identification of the node being displayed. For VT100
terminals, NTD uses the VT100 graphics capability to highlight the name
of the node.
• Bar graphs for the following resources:
Logical links (LNKS)
Communication control buffers (CCBs)
NOTE

Because CCBs can be allocated dynamically, the total number
of CCBs available can vary.
Small data buffers (SDBs)
Large data buffers (LDBs)
The first set of numbers for each resource indicates the number of that resource
currently in use and the total number generated into the system. For example,
12/50 in the LDB line in Example 7-1 indicates that 12 out of 50 generated
large data buffers are currently being used.

7·6

DECnet-RSX Guide to Network Management Utilities

The actual graphs represented by Xs in the examples illustrate the percentage
of each resource currently in use. The vertical bars on the graph (represented
by ! in the examples) illustrate the highest percentage of each resource used
during the current invocation of NTD. For example. in Example 7-1. roughly
25 percent of the LDBs are currently in use, but the position of the ! shows
that approximately 50 percent of the generated buffers have been in use at
once during the current invocation of NTD. Bar graphs for each resource are
scaled independently; for example, an X on one graph may represent usage
of one of that resource. while an X on another graph may represent usage of
five of that resource. Actual graphic representations can differ depending on
terminal type.
At the end of the line. NTD displays the number of allocation failures for
each resource type since network startup. On the LDB line. the second
allocation failure field refers to receive data buffers.
The bar graph display is updated approximately every second.
Lower left of the screen. This data differs with the two resource display

types. as described below. For either type. this information is updated at the
interval specified by the NTIlVIE command (default: every LO seconds) .
• Default resource display (see Example 7-1). NTD displays the following
information for all known circuits:
The circuit name.
The cost to reach the adjacent node.
The maximum buffer size of network messages to the adjacent node (not
applicable for Ethernet circuits, since each node on the Ethernet may have
a different size).
For point-to-point circuits. the name and address of the adjacent node on
the circuit. if it is reachable; otherwise. the status of the circuit .

• Old resource display (see Example 7-2). NTD displays the following
information for any node that is currently reachable:
The remote node name and its node address.
The name of the circuit over which packets are sent to the node.

Network Display Program (NTD)

7-7

The minimum number of hops required to reach the node and the minimum
cost to reach the node. These numbers may correspond to different routes,
as the least costly route may not necessarily have the fewest hops.
The number of active logical links to that node and the current round trip
delay in seconds. If the number of logical links is shown as 0, it indicates
that a link has been active to that node since the network was loaded.
Lower right of the screen. NTD displays the following information for currently
active network tasks (that is, those tasks that have issued an OPN$ to the
network):

• The task name .
• The TI: device associated with the task. Tasks requested through the network
normally run with a TI: of COO: for RSX-IIM and M-PLUS.
• The number of logical links that are active on the task, including any
outgoing connect request that has not yet completed .
• The number of entries on the task's mailbox. Entries can include:
Incoming connect requests
Interrupt messages
Disconnect notifications
Link abort notifications
Network abort notifications
Network events
Refer to the DECnet-RSX
information about mailboxes.

Programmer's

Reference

Manual

for

• The number of outstanding logical link transmit requests.
• The number of outstanding logical link receive requests.
This information is updated at the interval specified by the TTIME command
(default: every 5 seconds).

7-8

DECnet-RSX Guide to Network Management Utilities

Example 7·1: Sample Default Resource Display

6-MAR-84
LNKS
CCB
SDB
LDB

17:20:25
Node: BIGBOY(4.8) FINANCE SYSTEMS ROUTER
RSX-11M-Plus, Area Routing Node, DECnet V2.0
Alloc Fails:
3 / 10 XXXXXXXXXXXX!--------------------------0
30 /100 XXXXXXXXXXXX!--------------------------0
6 / 22 XXXXXXXXXX!----------------------------0
0
23 /130 XXXXXXX!--------------------------------

Circuit

Known Circuits:
Cost Size Adj Node/Status

UNA-O
UNA-l
DMC-O
DMC-l
DMC-2
DMC-3
DMC-4
DMC-5

3
3
11
11
11
11
4
4

ACCNTS( 4.126)
Off
On-starting
On-starting
On-starting
On-starting
On-starting
On-starting

Task

Network Tasks:
TI Links MBX XMT RCV

NTD. ..
NTDTl

COO:
TTl:

100

Example 7·2: Sample Old Resource Display

6-MAR-84
LNKS
CCB
SDB
LDB

17:20:43
Node: BIGBOY(4.8) FINANCE SYSTEMS ROUTER
RSX-llM-Plus, Area Routing Node, DECnet V2.0
3 / 10 XXXXXXXXXXXX!--------------------------Alloc Fails:
29 /100 XXXXXXXXXXX!---------------------------0
6 / 22 XXXXXXXXXX!----------------------------~
0
22 /130 XXXXXX!--------------------------------0
0

Node

Remote Nodes:
Circuit Hop/Cst Lnk/Dly

TULSA ( 4.6)
MIAMI ( 4.10)
BOSTON( 4.11)
HARTFD( 4.17)
NEWYRK( 4.18)
SEA TTL ( 4. 19)
CHICAG ( ,4.21)
DENVER( '4.22)
SANFRN( 4.17)

UNA-O
UNA-O
UNA-O
UNA-O
UNA-O
UNA-O
UNA-O
UNA-O
UNA-O

2/6
1/3
2/6
1/3
3/15
1/3
1/3
2/7
2/6

Network Display Program (NTD)

0/10
0/10

Task

Network Tasks:
TI Links MBX XMT RCV

NTD ...
NTDTl

COO:
TTl:

2
1

0
0

1
0

0
1

0/5
0/4
1/4

7·9

7.4 NTD Node Summary Display Format
Example 7-3 is an example of a node summary display. The display information
fields are described below.
Top of the screen

• Node name or address. By default, named nodes are listed alphabetically,
followed by nodes that are identified by address only (in ascending order).
You can use the immediate mode S command to order all nodes by ascending
node address (see Table 7-1).
• The minimum number of hops required to reach the node and the minimum
cost to reach the node. These numbers may correspond to different routes,
as the least costly route may not necessarily have the fewest hops.
• The number of active logical links to the node. If the number of logical
links is shown as O. this indicates that a link has been active to that node
since the network was loaded.
• The total number of nodes actually displayed. Since the screen cannot display
more than B4 nodes at once, this number may not necessarily reflect the
total number of nodes in a large network. You will have to use scrolling
to display additional nodes. This number also does not include any nodes
that have been excluded because of filtering commands (see ADDRESS,
MAXIMUM, HOPS, and COST in Table 7-2).

7-10

DECnet-RSX Guide to Network Management Utilities

Example 7-3: Sample Node Summary Display

Node: BIGBOY(4.8) FINANCE SYSTEMS ROUTER
17:20:43
RSX-11M-Plus, Area Routing Node, DECnet V2.0
Node Hop/Cst Lnk Node Hop/Cst Lnk Node Hop/Cst Lnk Node Hop/Cst Lnk
DENVER 4/20
0
OMAHA
1/3
[ 21] 2/6
ATLANT 4/20
FRISCO 2/6
QUEBEC 4/20
1
[25] 4/20
ALBERQ 5/24
1
HARTFD 5/22
RICHMN 1/3
[ 16] 3/15
BOSTON 2/6
JACKVL 1/3
SEATTL 4/20
0
-Total Nodes: 19
CHICAG 5/23
2
NEWYRK 4/20
3
TULSA
4/20
DALLAS 5/23
6-MAR-84

7.5 NTD Area Summary Display Format
Example 7-4 is an example of an area summary display. The display information
fields are described below.
Top of the screen

• Area ID. The ID of the area.
• The circuit name of the circuit being used to communicate with the area.
• The minimum number of hops required to reach the area and the minimum
cost to reach the area. These numbers may correspond to different routes,
as the least costly route may not necessarily have the fewest hops.
• The next node on the path to the area. This node may be another level 2
router within the local area or a level 2 router in another area. In either
case, it should always be a level 2 router if the network was configured
properly.
• The total number of areas actually displayed.

Network Display Program (NTD)

7-11

Example 7-4: Sample Area Summary Display

6-MAR-84

17:20:43
Node: BIGBOY(4.8) FINANCE SYSTEMS ROUTER
RSX-llM-Plus, Area Routing Node, DECnet V2.0
Area Circuit Hop/Cst
Next Node
Area Circuit Hop/Cst
2 UNA-O
4/20 DALLAS( 4.12)
20 DMC-O
2/6
3 UNA-O
3/15 DALLAS( 4.12)
21 UNA-O
1/5
5 DMC-l
2/9
HARTFD( 4.8)
25 UNA-O
2/9
10

7-12

Next Node
OMAHA ( 4.18)
DALLAS( 4.12)
DALLAS( 4.12)

DECnet-RSX Guide to Network Management Utilities

8
Queue Manager (QUE)

The Queue Manager (QUE) utility is the interface to the RSX-1IM V 4.2,
RSX-11M-PLUS V3.0. and Micro/RSX V3.0 queue manager. Any privileged
user can employ QUE to initialize the File Transfer Spooler (FTS) queue and
processor and to manipulate user-queued FTS requests. FTS is a D ECnet- RSX
utility that allows you to transfer files in much the same way as the Network
File Transfer (NFT) utility. with the additional queue feature.
This chapter outlines components required by FTS and QUE and describes
how to invoke and use QUE. For more information on both utilities. including
error messages, see the following manuals:

• DECnet-RSX Guide to User Utilities. Contains a complete description of
FTS
• RSX-llMIM-PLUS Batch and Queue Operations Manual.
description of QUE user commands and error messages

Contains

• RSX-ll MIM-PLUS System Nlallagement Guide. Contains a description of
QUE system manager commands

8.1 FTS and QUE Components
Table 8-1 lists the components required by FTS and QUE and describes their
relationship to queue management. Figure 8-1 diagrams the relationships among
these components.

8-1

Table 8-1: FTS and QUE Components
Component

Description

FTS

The user interface that spools requests and places them on
a queue.

QUE

The system manager interface that processes queue
management commands.

QMG

The RSX-ll queue manager task.

FTSDEQ

The processor task that services the queue.

FAL

The File Access Listener that handles file access and transfer
requests over a line at the remote node.

FTSQUE

The queue of FTS jobs that the queue manager stores In a
disk area.

URBs

User request block files that contain details of the FTS
requests corresponding to FTS jobs on the queue. This
information contains names that FTSD EQ needs to process
the requests. FTS prints this information in response to the
ILIST command.

FTSSYS.LOG

The log file that contains a record of both completed and
uncompleted FTS jobs.

FAL.LOG

The log file that contains a record of completed FAL jobs.

8-2

DECnet-RSX Guide to Network Management Utilities

SYSTEM MANAGER

QUE

FTS USER

FTS
FAL

TW145

Figure 8-1: FTS and aUE Components

8.2 Invoking QUE
To invoke QUE, enter the following command in response to an MCR) prompt:
QUE command
where command IS any valid QUE command (as described in the following
sections). After the QUE command executes, you are returned to MCR.

8.3 QUE Command Syntax
QUE supports three command formats. Each format allows you to perform
various queue management functions. These functions include:
• Initializing/deleting and starting/stopping the queue and the processor
• Assigning/deassigning the processor to/from the queue
• Holding, releasing, or deleting FTS user jobs on the queue

Queue Manager (QUE)

8·3

The following sections describe the three command formats and their functions
and give examples of their use.
8.3.1 Initializing/Deleting and Starting/Stopping the Queue and the Processor

Use the following QUE command syntax and the appropriate switch to cause
the queue or the processor to be initialized, deleted, started, or stopped:
QUE name/switch
where
name

is either the queue name (FTSQUE) or the processor's installed name
(FTSDEQ).

switch

is one of the following switch options:
CR
SP/EX

STA
STO:QUE
STO
DEL:Q
UNSP

creates, names, and starts the FTS queue
creates, names, and starts the FTS processor
starts the FTS queue or processor
stops the FTS queue
stops the FTS processor
deletes the FTS queue
deletes the FTS processor

In an emergency situation, delete either the queue or the processor. Users can
delete their jobs from the queue using FTS.
NOTE

If FTS was selected during NETGEN, the FTS queue and
processor will already be set up when the network is loaded.
If they were not set up by commands in file NETINS.CMD,
you must create the queue and start the processor to make the
FTS queue available for users.
Example

MCR>QUE FTSQUE/CR
MCR>QUE FTSDEQ/SP/EX
The first command creates the FTS queue. The second command starts the
FTS processor task.

8-4

DECnet-RSX Guide to Network Management Utilities

8.3.2 Assigning and Deassigning the Processor

Use the following QUE command syntax to assign and deassign the processor
to and from the queue:
QUE FTSDEQ:lswitch:FTSQUE
where
FTSDEQ

is the processor name.

FTSQUE

switch

is one of the following switch options:

assigns the processor to the queue. You must assign the processor
upon initializing it in order to enable FTS operations.

DEA

deassigns the processor from the queue. Deassigning the processor
prevents it from performing any functions (for example,
transferring files. despooling). However, jobs can be added to the
queue when the processor is deassigned. You may need to
deassign the processor in special situations (for example, to
prevent jobs from being completed). To reactivate the processor,
use the assign switch (I AS).

the queue name.

There are cases where a queue must be inspected, but you do not want any
of the jobs processed before listing the queue's contents. In this case, deassign
the processor before listing the queue. Refer to Section 8.4 for information on
related queue management functions.

Queue Manager (QUE)

8·5

8.3.3 Holding, Releasing, and Deleting FTS User Jobs

Use the following QUE command syntax to hold, release, or delete FTS user
jobs on the queue:
QUE IENT:entry-numberlswitch
where
entry-number

is the number assigned to the queue entry by the queue
manager. The entry number is obtained by listing the contents
of FTSQUE (see Section R.3.2).

switch

is one of the following switch options:
HO
REL
DEL

holds the specified job
releases the specified job from the hold state
deletes the specified job

Ordinarily, you do not delete or hold jobs. FTS users can delete their own
jobs. You need to use these commands only in special situations (for example.
when you want to delay a job that is about to begin).
Example:

MCR>QUE /ENT:857/DEL
This command deletes the job with entry number 857 from the queue.

8-6

DECnet-RSX Guide to Network Management Utilities

8.4 Related Queue Management Functions
In addition to using QUE for queue management, you should periodically
perform other related queue management functions. These functions include:
• Purging the FTS system log file (FTSSYS.LOG) and the FAL system log
file (F AL.LOG)
• Listing the contents of FTSQUE and of FTS jobs
• Listing and purging the user request block (URB) files
The following sections describe procedures for performing these functions.
NOTE

FTS will retry requested file operations if they fail due to
network problems. After a number of unsuccessful retries
(default = 5). the FTS job will be put into the hold state in
FTSQUE. The user must decide whether to release the job for
one more retry or to delete (abort) it.
8.4.1 Purging FTSSYS.LOG and FAL.LOG

Periodically. you should purge the FTS system log file (FTSSYS.LOG) and
the FAL system log file (FAL.LOG). FTSSYS.LOG contains a record of every
job FTS has received. along with coded status information. time of receipt.
and time of completion. The file is useful for statistical purposes. F AL.LOG
records network file transfer information for each file copied over the network.
FTSDEQ automatically deletes URB file entries as jobs complete. However.
it does not delete FTS system log file entries. Use the Peripheral Interchange
Program (PIP) to purge these files when necessary. (See the RSX-/l MIM-PLUS
Utilities Manual for more information.) The following PIP command displays
the FTS system log file:

>PIP TI:=[1,4]FTSSYS.LOG
Refer to the DECnet-RSX Guide to User Utilities for a description of the
system log file display.

Queue Manager (QUE)

8-7

During network generation, you can choose to create the system log file in
UFD [1,4] with no file protection. Optionally, log entries are copied to a log
file in the UFD of the user who queued the request. The user is expected to
maintain this file.
8.4.2 Listing FTSaUE and FTS Jobs

Periodically, or when necessary, list the contents of FTSQUE and of FTS
jobs. The following command lists the contents of FTSQVE:

MCR>QUE FTSQUE:/LI:P
A sample system display follows:

** PRINT QUEUES **
FTSQUE =>FTSDEQ
[1,1]
223771 ENTRY:857
PRINT AFTER 2-FEB-85 11:37
1 DBO: [l,4]FTS4166.URB;1
The FTSQUE contains one job, number 223771. Note that FTSDEQ is the
processor for FTSQUE. This field appears only when the processor has been
assigned to the queue. If this field does not appear. the processor is deassigned,
but there can still be entries in the queue. The job was originally queued from
the VIC [4,166]. After it failed. the job was requeued by the FTSDEQ task
from UIC [1,1]. The queue manager entry number is 857. The job is to be
printed (in this case retried) at 11 :37.
Note the format of the VRB file specification:
device:[ufd]FTSnnnnnn. URB;xx

where
nnnnnn is the user's current UIC (with leading zeroes suppressed).
XX

8-8

If multiple jobs are queued from a single VIC.
this number is greater than 1.

IS the request number.

DECnet-RSX Guide to Network Management Utilities

If, after inspecting the FTS queue, you want more information on a user's

job on the queue, enter the following commands:
>SET /UIC= [user uie]
>FTS /LI

The following is a sample system display:
FTS USER REQUEST LISTING
/IM/LO
223553 TLR/50
Queued 2-FEB-85 11:45
Source File -- DBO: [4,122]NODES.SYS;4
Destination File
XYZ:: [4, 131]NODES.SYS

2-FEB-85 11:45
Retried 0 times

/IM/LO
223573 TLR/50
Queued 2-FEB-85 11:45
Retried 0 times
Source File -- DBO: [4,122]NODFIL.MAC;10
Destination File
XYZ:: [4, 131]NODFIL.MAC
223507 TLR/50
/IM/LO
Queued 2-FEB-85 11:45
Retried 0 times
Source File --DBO: [4,122] PRMFIL. MAC; 1
Destination File -- XYZ:: [4, 131]PRMFIL.MAC

The job numbers at the beginning of each entry are the only cross-reference
you have to the system queue list. For more information on the FTS ILl
switch, see the DECnet-RSX Guide to User Utilities.
8.4.3 Listing and Purging URB Files

Periodically, or when necessary, list and purge the URB files. The following
PIP command produces a display of the URB directory:
>PIP [1,4]*.URB;*/LI
If you have deleted a job with QUE, you must also delete its associated URB

file or files. QUE does not do this automatically. However, when an FTS user
deletes a job, it also is deleted automatically from its URB file.

Queue Manager (QUE)

8·9

9
Trace Interpreter Task (TRI)

The X.25 trace interpreter task (TRI) is part of the trace facility provided for
RSX-ll PSI users. This facility enables you to diagnose software problems
on a PSI line connected to a device. The facility traces message frames passing
between the X.25 level 2 protocol and the device driver and copies the traced
frames to a disk file. The contents of this file can then be analyzed and
printed.
Use NCP TRACE commands to control the tracing of frames and to create
the file (see the CLEAR TRACE, SET TRACE, and SHOW TRACE commands
in Chapter 1). Then use TRI to analyze the contents of the trace disk file.

9.1 Invoking TRI
There are three methods of invoking TRI:
1. MeR> TRl

TRI then prompts
TRl>

Enter your TRI command immediately following the prompt. If the command
executes, the utility prompt is displayed on the next line. If the command is
unsuccessful, an error message is displayed on the next line indicating the
reason for the error followed by the utility prompt.

9-1

2. MCR>TRI command

where command is any valid TRI command. With this method, you return to
MCR after the TRI command is executed.
3. MCR>TRI @command-file

where command-file is the name of an indirect command file containing TRI
commands. You can nest command files.

9.2 Exiting TRI
To exit TRI. enter <CTRL/Z> or <RET>.

9.3 TRI Command Format
The TRI command line has the following format:
[outfile[/switches] = ][infile[lswitches]]

where
outfile

is the listing file. If not specified, this defaults to the input file
name with file type .LST.

infile

is the name of the file containing the tracing data. If this name
is not specified. this file defaults to LB:[1.6]PSITRACE.SYS.

switches

are the options available for controlling the form and content of
the listing produced by TRI. Any compatible combination of the
switches shown in Table 9-1 can be specified on either the input
file or the output file.

9-2

DECnet-RSX Guide to Network Management Utilities

Table 9-1: Trace Interpreter Switches
Switch

Meaning

Comments

ISP

Spool the output file

Default switch. Output is
spooled unless I-SP is
specified.

I-SP

Do not spool the output
file

IOC *

Output user data in octal

Cannot be specified with I-IN.

lAS :::

Output user data in ASCII

Cannot be specified with I-IN.

lIN

Interpret trace data

Default switch. (Data is
interpreted unless I-IN
specified.)

I-IN

Do not interpret trace data

Only ISP or I-S P can be specified
with this switch.

ILI:n

Output trace data for system
line n only

The Il is octal. If you
want to specify a decimal
number, use Il. instead. The
default for Ii is O. Cannot be
specified with I-IN.

ICH:n

Output trace data for channel
number Il only

The n is octal. If you
want to specify a decimal
number use It. instead. The
default for n is o. Cannot be
specified with 1- IN.

:I:

If you specify both IOC and lAS, trace data is printed in octal bytes with
the corresponding ASCI I characters underneath.

Trace Interpreter Task (TRI)

9-3

Examples:
MCR> TR.l =/DC/ AS

This command uses the IOC and I AS switches to output user data In octal
and ASCII characters.
MCR> TR.l =/Ll: 1/DC

This command uses the IOC switch to output octal user data for system line
1 only.

9.4 Contents of Trace Output
TRI reads the trace file created by the tracing facility and lists the following
information (depending upon the frame type) for each traced frame:
• Any error status from the CCB
• The system line num ber
• The direction of transfer (Rx or Tx)
• The frame address byte
• Setting of the P/F bit
• N(S) andlor N(R) numbers
• The frame type as text (for example, SABM)
• The logical channel identifier
• Settings of the Q. D, and M bits
• The packet type as text (for example, Call Req.)
• P(S) and/or P(R) numbers
• Cause and diagnostic fields
• The first few bytes of user data

9-4

DECnet-RSX Guide to Network Management Utilities

9.5 TRI Error Messages
TRI prints an error message on your terminal when it detects an operating
error. All TRI error messages are listed in Chapter 10.

Trace Interpreter Task (TRI)

9-5

10
Utility Error Messages

This chapter list~ the error messages sent by the following utility programs'
• Console carrier requester (CCR)
• Configuration File Editor (CFE)
• Event File Interpreter program (EVF)
• Host Task Loader (HLD)
• Network Control Program (NCP)
• Network Crash Dump Analyzer (NDA)
• Network Display Program (NTD)
• Network initializer (NTINIT)
• Network loader (NTL)
• X.25 trace interpreter task (TRI)
• Virtual Network Processor (VNP)

10·1

You would not be surprised to receive a CFE error message if you had just
invoked a CFE command. However. NCP. VNP. and CFE use the NTINIT
and NTL utilities to process your commands. Therefore. an error could occur
in one of those utilities instead of in the one that you invoked. You will
receive an error message from the utility in which the error occurred. Each
error message has a prefix that identifies the utility that sent it.
In this chapter. error messages are arranged in alphabetical order by utility
and message text. Variable fields within messages are ignored for purposes of
alphabetization.

10-2

DECnet-RSX Guide to Network Management Utilities

CCR
Error Messages

10. 1 CCR Error Messages
CCR -- Component in wrong state, xxx

The specified component was not in the correct state to proceed with the
operation of console carrier (xxx = circuit or system).
CCR -- File 1/0 error, xxx

An I/O error occurred while trying to read the specified file File I/O (xxx
secondary loader or load file).
CCR .- File open error, xxx

CCR was unable to open the specified file (xxx
file).

secondary loader or load

CCR -- Invalid file contents, xxx

The contents of the specified file are not in the required format (xxx
secondary loader or load file).

CCR _. Invalid identification format, xxx

The format for the specified parameter is invalid (xxx
hardware address. or service password).

node. service circuit.

CCR _. Line communication error

The operation failed due to a communication error on the line.

Utility Error Messages

10-3

CCR
Error Messages
CCR •• Line protocol error

The operation failed due to a protocol error.
CCR •• Management programming error

An internal programming error has been detected.
CCR •• Message format error

The format of a received protocol message was invalid.
CCR •• Parameter missing, xxx

The required parameter was not defined in the command line and the down-line
load database (xxx = node, service circuit, hardware address. or service
password).
CCR •. Privilege violation

The user does not have sufficient privileges to run CCR.
CCR •• Protocol/address pair in use

The protocol/address pair used to communicate with the target system is
already in use.
CCR •• Remote console already in use

Another user on another node has already reserved the remote console on the
target system.

10-4

DECnet-RSX Guide to Network Management Utilities

CFE
Error Messages

10.2 CFE Error Messages
All CFE error messages documented in this chapter are classified according
to severity and cause. Both classifications are described below and are noted
at the beginning of each error description.
Severity cl assifi cati 0 ns

Informational

There is a minor problem. but it does not affect the task's
exit status.

Warning

Minor error. Processing continues.

Error

Major error. The command was accepted. but failed to execute
completely. The system waits for a new command.

Severe Error

The command was not accepted. Processing stops and control
returns to the monitor.

Cause classifications

CETAB Parse

These errors occur during the parsing of CETAB.MAC. They
usually occur when someone has edited CETAB using a text
editor. Restore CETAB to its original content.

CETAB

These errors are generated in response to valid commands.
They usually occur when someone has edi ted CET AB using
a text editor. Restore CETAB to its original content.

Configuration

These errors are generated by valid commands that refer to
features or components that are not in the CET AB file being
edited. Check the CETAB file and enter the correct command.

Command

These errors usually are caused by a mistyped command or
by an incorrect or inapplicable parameter. Correct the
command and reenter it.

General

These errors usually indicate a problem with the CFE
installation or with the HELP or CET AB files. The cause is
probably an invalid UIC or something similar.

Utility Error Messages

10-5

CFE
Error Messages
CFE •• Access verification not supported

(Error/Configuration) You do not have access verification supported ill your
system. so you cannot change the verification state.
CFE •. Bad port value

(Severe Error/CETAB Parse) The number of ports on the PSN$DF macro is
out of range or contains nonnumeric characters.
CFE •. Bad transport subaddress value

(Severe Error/CETAB Parse) The transport subaddress values on the PSN$D F
macro are out of range or contain invalid characters.
CFE •. Buffer allocation failure

(Error/Command) CFE tried to allocate an internal buffer to complete the
command but failed. If you must make a new entry in CET AB. then remove
CFE and reinstall it with an increment.
CFE •. Call mask and call value are different lengths

(Error/Command) The call mask and call value of a destination must be of the
same length.
CFE •. Circuit not in configuration

(Error/Configuration) The circuit in the command IS not In the database.
CFE •. Command line error

(Error/Command) The command has a bad character or equivalent.
CFE •. Consistency error

(Severe Error/General) There is an internal consistency error in CFE. Please
contact your software specialist to determine the cause of this error.

10·6

DECnet-RSX Guide to Network Management Utilities

CFE
Error Messages
CFE -- Destination not in configuration

(Error/Configuration) The d~stination in the command is not in the database.
CFE -- DTE not in configuration

(Error/Configuration) The DTE in the command is not in the database.
CFE -- DTE number missing from outgoing SVC: DLM-ll.t

(Severe Error/CET AB Parse) The DTE number is required for outgoing SVCs.
Reenter the command with the DTE number.
CFE -- DTE with DLM circuits not purged: DTE-address

(Error/Command) The indicated DTE was not purged because some of its
circuits are data-link-mapping circuits. Data-link-mapping circuits may not be
purged.
CFE -- Duplicate PSN$DF in CETAB

(Severe Error/CETAB Parse) There is more than one PSN$DF macro in the
CETAB.MAC file. Remove one of the PSN$DF macros.
CFE -- Error in call mask or call value

(Error/Command) The format in the call mask or call value ill the command
is invalid.
CFE -- Error in channel list

(Error/Command) The format of the channel list in the command is invalid.
CFE -- Error in channel number

(Severe Error/CETAB Parse) The channel number on a CHN$DF macro is out
of range or contains nonnumeric characters.

Utility Error Messages

10-7

CFE
Error Messages
CFE .- Error in controller number

(Severe Error/CET AB Parse) The controller number on an SLT$D F macro IS
invalid.
CFE .- Error in OOM name

(Severe Error/CETAB Parse) The DDM name on an SLT$DF macro is too
long.
CFE .- Error in OLC name

(Severe Error/CET AB Parse) The DLC name on an SLT$DF macro is too
long.
CFE .- Error in OTE address

(Severe Error/CETAB Parse) The DTE address field on an SVC$DF macro is
out of range.
CFE .- Error in flags

(Severe Error/CETAB Parse) The flags field on a CUG$DF. PSN$DF.
PVC$DF. SLT$DF. or SVC$DF macro is unrecognized or invalid.
CFE .- Error in line 10

(Severe Error/CETAB Parse) The line identification on a DTE$D F macro is
of an invalid format.
CFE .. Error in line type

(Severe Error/CET AB
unrecognized.

Parse) The line type on an SLT$D F

macro is

CFE _. Error in LLC name

(Severe Error/CETAB Parse) The LLC name on an SLT$DF macro is too long.

10·8

DECnet-RSX Guide to Network Management Utilities

CFE
Error Messages
CFE -- Error in maximum circuits

(Severe Error/CET AB Parse) The maximum circuits value on an X2 P$D F
macro is out of range or has an invalid format.
CFE -- Error in maximum recalls

(Severe Error/CETAB Parse) The maximum recall field on an SVC$D F macro
is out of range.
CFE -- Error in network name

(Severe Error/CETAB Parse) The network name on a DTE$DF or PSN$DF
macro is too long or contains invalid characters.
CFE -- Error in opening file

(Severe Error/General) CFE could not open the specified CET AB source file.
Make sure that the file is where you specified. that the file is not locked. and
that you have write privileges to the file.
CFE -- Error in owner

(Severe Error/CET AB Parse) The owner process field on an SLT$D F macro
is unrecognized.
CFE -- Error in packet size

(Severe Error/CETAB Parse) The packet size field on an SVC$DF or X3P$DF
macro is out of range.
CFE -- Error in recall timer

(Severe Error/CETAB Parse) The recall timer value field on an SVC$DF macro
is out of range,.

Utility Error Messages

10-9

CFE
Error Messages
CFE .• Error in SVC name

(Severe Error/CETAB
an invalid format.

Pars~)

The SVC circuit ID on an SYC$DF macro has

CFE .• Error in unit number

(Severe Error/CETAB Parse) The unit number on an SLT$DF is invalid.
CFE .• Error in window size

(Severe Error/CETAB Parse) The window size on an SVC$DF or X3P$DF
macro is out of range.
CFE .• Error writing file

(Severe Error/General) CFE was unable to write a record to the output file;
therefore the CET AB source file was not updated. Check to make sure that
the disk is not full.
CFE .• Executor node not allowed

(Error/Command) An attempt has been made to define the executor node as
a remote node.
CFE .• Executor node not allowed with command

(Error/Command) The command parameters specified in the command are not
permitted on the executor node.
CFE .• Group not in configuration

(Error/Configuration) The closed user group in the command is not in the
database.

10-10

DECnet-RSX Guide to Network Management Utilities

CFE
Error Messages
CFE -- Illegal baud rate

(Error/Command) The baud rate specified in the command is out of range or
not in the table of valid baud rates. Reenter the command with a legal baud
rate.
CFE -- Illegal call mask

(Severe Error/CETAB Parse) The call mask on a DSC$DF macro is too long
or contains invalid characters.
CFE -- Illegal call value

(Severe Error/CETAB Parse) The call value on a DSC$DF macro is too long
or contains invalid characters.
CFE _. Illegal circuit type

(Error/Command) The circuit type in the command is illegal for the requested
operation. For example. it is illegal to purge a DDCl\IP circuit.
CFE •• Illegal command

(Error/Command) The command you gave to CFE is incorrect.
CFE •• Illegal CUG name

(Severe Error/CETAB Parse) The user group name on a CUG$D F or DSA$D F
macro is too long or contains invalid characters.
CFE •• Illegal destination address

(Severe Error/CETAB Parse) The destination address on a DSA$D F macro is
not a valid DTE address.

Utility Error Messages

10-11

CFE
Error Messages
CFE •• Illegal destination name

(Severe Error/CET AB Parse) The destination name on a DST$D F macro is
too long or contains invalid characters.
CFE •. Illegal destination priority

(Severe Error/CETAB Parse) The list insertion pnonty on a DST$DF macro
is out of range or contains nonnumeric characters.
CFE .• Illegal destination type

(Severe Error/CET AB Parse) The destination type on a DST$D F macro is not
legal for PSI.
CFE •• Illegal device priority

(Error/Command) The device priority specified in the command is out of range.
CFE •• Illegal DTE name

(Severe Error/CETAB Parse) The DTE name on a RDT$DF macro is too long
or contains invalid characters.
CFE •• Illegal executor node address

(Error/Command) An attempt was made to define the executor node address
to greater than the maximum address for the network.
CFE .• Illegal group number

(Severe Error/CETAB Parse) The group number on a CUG$DF macro is out
of range or contains nonnumeric characters.

10-12

DECnet-RSX Guide to Network Management Utilities

CFE
Error Messages
CFE _. Illegal logical channel number

(Severe Error/CET AB Parse) The logIcal channel number on a PVC$D F macro
is out of range or contains nonnumeric characters.
CFE -- Illegal maximum data size

(Severe Error/CET AB Parse) The maximum data size on a PVC$D F macro is
out of range or contains nonnumeric characters.
CFE -. Illegal object number

(Severe Error/CETAB Parse) The object number on a DST$DF macro IS out
of range or contains nonnumeric characters.
CFE -- Illegal owner process

(Severe Error/CET AB Parse) The owner process identification field on a
PVC$DF macro is not a recognized owner.
CFE _. Illegal PVC name

(Severe Error/CETAB Parse) The circuit identification on a PVC$DF macro
is too long or contains invalid characters.
CFE •• Illegal state

(Severe Error/CETAB Parse) The state on a PVC$DF macro is not a recognized
state.
CFE .- Illegal subaddress high range

(Severe Error/CETAB Parse) The indicated subaddress on a DSA$D F macro
is out of range or contains nonnumeric characters.
CFE •• Illegal subaddress low range

(Severe Error/CET AB Parse) The indicated subaddress on a DSA$D F macro
is out of range or contains nonnumeric characters.

Utility Error Messages

10·13

CFE
Error Messages
CFE _. Illegal task name

(Severe Error/CETAB Parse) The task name on a DST$DF macro is too long
or contains invalid characters. This message is also generated if a task name
is included and the destination object number is not zero.
CFE •• Illegal window size

(Severe Error/CETAB Parse) The window size on a PVC$DF macro IS out of
range or contains nonnumeric characters.
CFE _. Insufficient buffer space

(Severe Error/General) CFE was not built with enough buffer space to
accommodate the CETAB source file information. Remove CFE and reinstall
it with an increment.
CFE _. Invalid block size

(Severe Error/CETAB Parse) The block size on an X2P$DF macro is out of
range or of an invalid format.
CFE -. Invalid call timer value

(Severe Error/CET AB Parse) The call timer field on the X3P$D F macro is
out of range or is of an invalid format.
CFE _. Invalid circuit identification

(Error/Command) The format of the circuit ID in the command is invalid.
CFE _. Invalid clear timer value

(Severe Error/CETAB Parse) The clear timer field on the X3P$DF macro is
out of range or is of an invalid format.

10-14

DECnet-RSX Guide to Network Management Utilities

CFE
Error Messages
CFE -- Invalid counter timer value

(Severe Error/CETAB Parse) The counter timer value on a DTE$DF. PVC$DF.
or SL T$D F macro is out of range or contains invalid characters.
CFE -- Invalid default block size

(Severe Error/CETAB Parse) The default block SIze on the X3P$DF macro is
out of range or is of an invalid format.
CFE -- Invalid default window size

(Severe Error/CETAB Parse) The default window SIze field on the X3P$DF
macro is out of range or is of an invalid format.
CFE -- Invalid destination sequence

(Error/CETAB) An invalid destination sequence has been detected. This usually
indicates a corrupt CETAB.~IAC file.
CFE -- Invalid OTE address

(Severe Error/CETAB Parse) The DTE address on a DTE$DF or RDT$DF
macro is too long or contains invalid characters.
CFE -- Invalid OTE state

(Severe Error/CETAB Parse) The state on a DTE$DF macro is not a recognized
DTE state.
CFE -- Invalid hash table size

(Severe Error/CETAB Parse) The hash table size on a DTE$DF macro is out
of range, is not a power of 2. or contains invalid characters.
CFE -- Invalid holdback timer value

(Severe Error/CETAB Parse) The holdback timer value on an X2P$DF macro
is out of range or is of an in valid format.

Utility Error Messages

10-15

CFE
Error Messages
CFE .• Invalid line identification

Two error conditions can display this message:
• (Severe Error/CETAB Parse) CFE found an X2P$D F macro containing an
error in the line identification. This error occurs during the initial scan of
the CETAB file when CFE is invoked.
• (Error/Command) The line ID specified in the command is incorrect.
CFE .• Invalid maximum block size

(Severe Error/CETAB Parse) The default block size on the X3P$D F macro is
out of range or is of an in valid format.
CFE .• Invalid maximum clears value

(Severe Error/CETAB Parse) The maximum clears field on the X3P$DF macro
is out of range or is of an invalid format.
CFE .• Invalid maximum resets value

(Severe Error/CETAB Parse) The maximum resets field on the X3P$DF macro
is out of range or is of an invalid format.
CFE .• Invalid maximum restarts value

(Severe Error/CETAB Parse) The maximum restarts field on the X3P$DF
macro is out of range or is of an invalid format.
CFE .• Invalid maximum window size

(Severe Error/CETAB Parse) The maximum window size field on the X3P$DF
macro is out of range or is of an invalid format.

10-16

DECnet-RSX Guide to Network Management Utilities

CFE
Error Messages
CFE -- Invalid multicopy task name

(Error/Command) The task name of a multicopy object must be of the format
.xxx$$$, where xxx is 1 to 3 alphanumeric characters. This message is
generated when an attempt is made to define a multi copy object without a
multicopy name or a single copy object with a multicopy name.
CFE -- Invalid number

(Error/Command) The command has a number out of range.
CFE -- Invalid process identification

(Error/Command) The process name specified III the command is too long.
CFE -- Invalid reset timer value

(Severe Error/CETAB Parse) The reset timer field on the X3P$DF macro is
out of range or is of an invalid format.
CFE -- Invalid restart timer value

(Severe Error/CETAB Parse) The restart timer field on the X3P$D F macro is
out of range or is of an invalid format.
CFE -- Invalid retransmit count

(Severe Error/CET AB Parse) The retransmit count on an X2 P$D F macro is
out of range or is of an invalid format.
CFE -- Invalid retransmit timer value

(Severe Error/CETAB Parse) The retransmit timer value on an X2P$DF macro
is out of range or is of an invalid format.

Utility Error Messages

10-17

CFE.

- . 0 . < . _ _ _ _ __

Error Messages
CFE .• Invalid wildcard Sy'fci d~·

(Error/Command) The wildeard line or tircu:; ID In the command
invalid format.

1'.'

of an

CFE .• Line not in configuration

(ErrOI/Conllguration) The line specified in the command is not in the CET AB
,:,oun.·p ftle.

CFE .- Logging monitor not supported

(Error/Configuration) The logging monitor i~ not .,upported
configuration.

?OlH

sy.;;;tem

CFE .• Missing LLC$OF for NW

(Error/CETAB) The LLC$DF macro for NW is missing from the database.
This usually indicates a corrupt CETAB.lVIAC file.
CFE .• Missing parameter: parameter

(ErrurJComm(md) The indicated parameter is required for the type of operation
requestt'd and b missing from the command. Correct the command and reenter
it.
CFE .• Missing X2P$OF for line line-id

(Error/CETAB) There is no X2P$DF macro for the indicated line. This usually
indicates a corrupt CETAB.lVIAC file.
CFE .• No buffer definition
(Error/CETAB) The CETAB source file does not contain a BUF$DF macro
defining your buffers.

10·18

DECnet-RSX Guide to Network Management Utilities

CFE
Error Messages
CFE -- No HELP available

(Informational/General) CFE could not find the help file.
CFE -- No node defi nition

(Error/CETAB) The CETAB source file does not contain a NOD$DF macro
defining the local node.
CFE -- No partition definition

(Error/CETAB) The CETAB source file does not contain a PAR$DF macro
defining the network pool.
CFE -- No PSI support in system

(Error/Configuration) The CETAB being processed does not include support
for PSI.
CFE _. No routing definition

(Error/CETAB) The CETAB source file does not contain a ROU$DF macro
defining the routing parameters.
CFE _. No station template for line-id

(Error/CET AB) There are no station templates for the indicated line. This
usually indicates a corrupt CETAB.MAC file.
CFE -- No unit CSR on this line

(Error/Command) An attempt was made to change the unit CSR for a line
that does not have a unit CSR. This part of the command was ignored.

Utility Error Messages

10-19

CFE
Error Messages
CFE •. No XPT features macro

(Error/CET AB) The CET AB source file does not contain an FEA$D F macro
defining the XPT features. You will not be able to modify any of the states
defined by this macro.
CFE •. No XPT process macro

(Error/CETAB) The CETAB source file does not contain an LLC$DF macro
defining the XPT process.
CFE •. No X.29 support in configuration

(Error/Configuration) The CET AB.MAC file being processed does not contain
the X29$DF macro.
CFE •• No X3P$OF in database

(Error/CETAB) The X3P$D F macro is not in the database. This usually
indicates a corrupt CETAB.MAC file.
CFE •. Node address already in use

(Error/Command) The address you want to give this node is already in use.
CFE •• Node name already in use

(Error/Command) The name you want to give this node is already in use.
CFE •. Node not in configuration

(Error/Configuration) The node specified in the command is not in the CET AB
source file.

10·20

DECnet-RSX Guide to Network Management Utilities

CFE
Error Messages
CFE •• Number of SOBs exceeds number of CCSs

(Warning/CETAB) The maximum number of SDBs specified in the BUF$DF
macro exceeds the number of CCEs specified in the BUF$DF macro.
CFE •• Object not in configuration

(Error/Configuration) The object specified in the command is not in the CET AB
source file.
CFE .. Object task name must be specified

(Error/Command) An attempt was made to create an object type entry without
an associated task name. Reenter the command with the task name supplied.
CFE •• Operation invalid for line type

(Error/Command) The requested operation is not applicable to the line type
indicated in the command.
CFE •• Parameter applicable to PSI systems only

(Error/Configuration) One or more of the parameters in the command is
inapplicable to systems without PSI. and the CETAB being processed is for
a non-PSI system.
CFE •• Parameter illegal for circuit type

(Error/Command) One or more of the parameters in the command cannot be
set for the type of circuit indicated.
CFE •• Parameter illegal for wildcard operation

(Error/Command) One or more of the parameters in the command is not allowed
for wildcard or KNOWN operations.

Utility Error Messages

10-21

CFE
Error Messages
CFE •. Parameter not applicable

(Error/Configuration) One or more of the parameters in the command is not
applicable to the CET AB configuration (for example, routing parameters for
an end node).
CFE •. Pool byte extension less than minimum
Defaulting to nnn.

(Warning/Command) The pool byte extension on the command is less than the
minimum required for structures defined in the CETAB. The minimum value
nnn. is being used ins tead.
CFE •. Process not in configuration

(Error/Configuration) The process name specified in the command is not in the
CETAB source file.
CFE •. Routing parameters not applicable

(Error/Command) The routing parameters in the command are not applicable
to an end node.
CFE •. Syntax error

(Severe Error/CET AB Parse) The indicated macro contains an invalid or
unrecognized value.
CFE •. Task name not allowed with object type zero

(Error/Command) An attempt was made to force a single task to be associated
with the general task connect (type zero). This part of the command was
ignored.
CFE -. Too many stations

(Severe Error/CET AB) There are more stations on a particular line than CFE
is prepared to handle. This message is followed by the syntax error message
and the entry read from CETAB that caused the station number overflow.

10-22 •

DECnet-RSX Guide to Network Management Utilities

CFE
Error Messages
CFE .• Unknown HELP qualifier

(Informational/General) CFE has no help on the qualifier requested.
CFE .• Usage cannot be permanent

(Error/Command) The usage of an SVC must be either incoming or outgoing.
CFE •• XPT not allowed to load line tables in process space

(Error/Configuration) The command included an extension for line tables for
XPT. Since XPT cannot have line tables in process space. this part of the
command was ignored.
CFE •• X25-SERVER not in configuration

(Error/Configuration) There is no support for the X.25 server module in the
system.
CFE •• X29-SERVER not in configuration

(Error/Configuration) There is no support for the X.29 server module In the
system.

Utility Error Messages

10-23

EVF
Error Messages

10.3 EVF Error Messages
EVF .- Argument specified multiple times . xxx

An IENTITY argument is used more than once. xxx is the argument found
more than once.
EVF .. Command line syntax error

You have entered an invalid command.
EVF .. Error in get command line - reason

An error occurred in getting the command line. Reason is either a text string
or a decimal error number.
EVF .. Failed to close input file· reason

The input file could not be closed. Reason is either a text string or a decimal
error number.
EVF .. Failed to close output file . reason

The output file could not be closed. Reason is either a text string or a decimal
error number.
EVF .. Failed to delete input file . reason

The input file could not be deleted. Reason is either a text string or a decimal
error number. Possible text strings include:
1. Privilege violation

10-24

DECnet-RSX Guide to Network Management Utilities

EVF
Error Messages
EVF •• Failed to open input file • reason

The input file could not be opened. Reason is either a text string or a decimal
error number. Possible text strings include:
1. Accessed for wri te

2. Bad version number
3. Bad file name
4. Bad device name
5. Invalid device or unit
6. No such file
7. Privilege violation
EVF .• Failed to open output file . reason

The output file could not be opened. Reason is either a text string or a decimal
error number. Possible text strings include:
1. B ad file name
2. Bad device name
3. Device full
4. Invalid device or unit
5. Privilege violation
EVF •• Failed to spool output file • reason

The output file could not be spooled. Reason is either a text string or a
decimal error number.

Utility Error Messages

10·25

EVF
Error Messages
EVF -- Illegal argument combination

You have used the ALL argument in the IENTITY option along with another
entity argument.
EVF _. Illegal data range

You have entered a start date that is greater than the end date in the
IDATE:RANGE or ISINCE and ITHROUGH option.
EVF -- Illegal switch combination

You have used the ALL option along with another option.
EVF _. Input file format error

The input file you specified is not a binary event log file.
EVF _. Invalid area number

You have specified an area number in the IENT~TY:AREA option that is not
in the allowed range or is not a number.
EVF -- Invalid circuit-id

You have specified a circuit-id in the IENTITY:CIRCUIT option that is not
a valid circuit identifier. If the error occurred because of an incorrect use of
the wildcard character (*), the error is qualified with' - illegal use of wildcard'.
EVF _. Invalid date format

You have specified a date and time in the IDATE:RANGE or ISINCE and
ITHROUG H options is in the wrong format.

10-26

DECnet-RSX Guide to Network Management Utilities

EVF
Error Messages
EVF -- Invalid euellt-id

You have specified an event-id in the IEVENT option that is not a valid event
identifier. If the error involved the incorrect use of wildcards. this error is
qualified wi th '- illegal use of wildcard'. If too many events were specified
(more than 6). this error is qualified with '- too many event-ids declared'.
EVF -- Invalid line-id

You have specified a line-id in the IENTITY:LI!'iE option that is not a valid
line identifier. If the error occurred because of an incorrect use of the wildcard
character C:), the error is qualified with ·- illegal use of wildcard'.
EVF -- Invalid module-id

You have specified a module-id in the IENTITY:MODULE option that is not
a valid module identifier. The module identifier is not alphanumeric.
EVF -- Invalid node-id

You have specified a node-id in the IENTITY:NODE or ISOURCE option that
is not a valid node identifier. The node-id was not in the correct format. the
address is out of range. or the node name is greater than 6 characters.
EVF -- Switch specified multiple times - xxx

You have used an option more than once in the command. xxx is the option
found more than once.
EVF -- Too few arguments - xxx

You have used an option that required an argument but no argument was
found. xxx is the option.

Utility Error Messages

10-27

EVF
Error Messages
EVF .. Unknown argument . xxx

You have used an argument after the DATE. ENTITY or FORwIAT option
that was not recognized. xxx is the unrecognized argument.
EVF .. Unknown switch . xxx

You have used an unrecoglllzed option. If you abbreviate options to one letter
you will receive this error message. xxx is the option that was in error.

10-28

DECnet-RSX Guide to Network Management Utilities

HLD
Error Messages

10.4 HLD Error Messages
Some of the HLD error messages include strings that are replaced with run-time
variables. A list of these strings and the type of information they contain is
shown below.
(-nnn.)

A DSW or lOSE error code (always negative).

(nnn.)

A network code (always positive).

node

The name of the remote RSX -lIS node.

task

The installed task name received from SLD.

filespec

A copy of the file specification from the HT ASK$ macro. This is
followed by (File) to indicate that HLD found a match from the
external mapping tables. or by (G-P) to indicate that the task was
found on the general purpose list. or by (File. G-P) to indicate that
both conditions were satisfied.

Variable fields are ignored in the alphabetization of error messages in this
chapter.
HLD
HLD

nodeltask - Base address not a multiple of 4K
filespec

The file was not built with the IMM switch. Rebuild the file.
HLD -- node/task - Connect accept failure (-nnn.)
HLD -- filespec

The attempt to accept a connection from a remote SLD has failed. rrhe remote
node may have become unreachable.

Utility Error Messages

10-29

HLD
Error Messages
HLD -- node/ta-sk - Disk read failure (-nnn.)
HLD -- filespec

This error message indicates a disk error while readIng the file (ini tial load
or checkpoint read). Validate the integrity of the file and the disk. The second
error message line mayor may not appear.
HLD -- node/task - Disk write failure (-nnn.)

This error message indicates a disk error while writing to the file (checkpoint
write). Validate the integrity of the file and the disk.
HLD -- node/task - File has never been installed

The task file has not been installed (via VMR) into the RSX-llS system. This
error message appears if you rebuild the task file but neglect to install it.
Use VlVIR to install the task into the RSX-llS system.
HLD -- node/task - File has no task header
HLD -- filespec

The file was built with the /-HD switch. It is not a valid RSX-llS task image.
Rebuild the file.
HlD
node/task· File is larger than partition
HLD •. filespec

The initial load size of the file is larger than the partition size in the RSX-llS
system. Either make the partition larger or rebuild the file to use a smaller
partition size.
HlD
node/task - File is not contiguous
HLD -- /llespec

The file is not contiguous. Either rebuild the file or use PIP to make the file
contiguous (see example below).
>PIP /NV /CO=/llespec
>PIP /'ilespec/pu

10-30

DECnet-RSX Guide to Network Management Utilities

HLD
Error Messages

nodeltask - File spec parse error
HLD
HLD -- filespec
The file specification for the file has an in valid format. Rebuild the HLD
database.
HLD
HLD

nodeltask - G-P tasks may not be checkpointed
filespec

A checkpoint operation was attempted for an HT ASK$ macro from the general
purpose list. Edit and rebuild the appropriate mapping table to move the
HTASK$ macro from the general purpose list into a node-specific list.
HLD -- Invalid connect request from node-id

A task attempted to connect to HLD but did not supply a valid optional
connect data message. Refer to your object type tables within NETACP. HLD
is connected to by the object NO.RTL and not by the installed task name.
NO.RTL is defined in the NSSYM$ macro. Its object type number is 18.
HLD -- nodeltask - Invalid data type in mailbox (nnn.)

A network data type was found in the mailbox that is not used by HLD/SLD.
If the data type is a connect. NSP has tried to place more connects onto the
mailbox than HLD can handle.
HLD -- nodeltask - Label block read failure (-nnn.)
HLD -- filespec

The label block (TKB information) could not be accessed successfully. Rebuild
the file.

Utility Error Messages

10-31

HLD
Error Messages
HLD -- node/task - LUN fixing not supported
HLD -- filespec

The remote SLD was not built with the LUN-fixing module. Either rebuild
the remote SLD, or edit and rebuild the appropriate mapping table to move
the HTASK$ macro from general purpose list into a node-specific list. This
error also occurs if the HT ASK$ macro is already in a node-specific list but
uses the LUN control argument.
HLD -- Mailbox LUN assignment failure (-nnn.)

HLD could not successfully assign the network mailbox LUN to the NS:
device. Check to see if the local node's state is ON.
HLD .. nodeltask - Mapping file base address not zero

This error is caused by an incorrect TKB command file. Edit the TKB command
file, add the /-:MM switch to the output file specifier, and then add or modify
the PAR statement to read PAR = ANY:O:20000. Then rebuild the file.
HLD -- nodeltask - Mapping file contains a task header

This error is caused by an incorrect TKB command file. Edit the TKB command
file and add the /-HD switch to the output file specifier. Then rebuild the file.
HLD -- node/task - Mapping file contains garbage

HLD can successfully read the external file.
inconsistent. Rebuild the file.

but the file is internally

HLD .- node/task - Mapping file is larger than HLDFIL buffer space

The external mapping file is larger than the buffer space available. Merge the
external table into the internal table. Discontinue use of the external table.

10-32

DECnet-RSX Guide to Network Management Utilities

HLD
Error Messages
HLD •• node/task . Mapping file is not contiguous

The file is not contiguous. Either rebuild the file or use PIP to make the file
contiguous (see example below).
>PIP /NV/CO=HLDTAB.TSK
>PIP HLDTAB.TSK/PU
HLD •• node/task· Mapping file label block read failure (onnn.)

HLD could not read the file's label block (which contains TKB descriptive
information). Rebuild the file.
HLD •• nodeltask • Mapping file open failure (·nnn.)

HLD could not open the file. Rebuild the file.
HLD .• node/task • Mapping file read failure (·nnn.)

HLD could not read the external mapping file. Rebuild the file.
HLD .• Network data queue empty

HLD found nothing in the network data queue. This error occurs if you issue
MCR>RUN HLD ... or if the connection times out before HLD can remove the
connect request from the network data queue. Increase the connect timeout
period.
HLD .• node/task • Network disconnect (nnn.)

NSP has broken the logical link before the transfer has been completed.
HLD -- Network open failure (-nnn.)

HLD could not successfully issue the OPN$ macro. Check to see if the local
node's state is ON.

Utility Error Messages

10·33

HLD
Error Messages
HLD .• node/task • Network read failure (·nnn.)

A communication error has occurred at the remote SLD. The logical link IS
broken.
HLD .• Network SPA failure (·nnn.)

HLD could not successfully issue the SP A$ macro.
HLD .• node/task . Network write failure (·nnn.)

A communication error has occurred at the remote SLD. The logical link IS
broken.
HLD •• nodeltask . No entry in nodeltask tables

Your mapping tables do not contain an HT ASK$ macro that corresponds to
the task name from the error message.
HLD .• NS: Work LUN assignment failure (·nnn.)

HLD could not successfully assign one of its nonmailbox LUNs to the NS:
device.
HLD .• node/task· Open failure (·nnn.)
HLD •• filespec

The file named by the HT ASK$ macro could not be opened successfully. If
there is an FCS problem. you must rebuild the file. If not. change either the
file or the mapping table. If you change the file name. make it match the
mapping table. If you change the mapping table, make it match the file name.

10·34

DECnet-RSX Guide to Network Management Utilities

HLD
Error Messages
HLD
HLD

nodeltask· Partition is larger than CHKPT space
(ilespec

The partition size in the RSX-llS system is larger than the checkpoint space
inside the file. Typically. this indicates that the partition size in your PAR =
statement is smaller than the partition's real size in the RSX-llS system.
Although the load size of a task can be much smaller than its partition. the
entire partition is transferred during checkpoint operations. Rebuild the file
with the same partition size as the RSX-llS system.
HLD .. nodeltask • SLD abort/disconnect

This error message indicates that SLD detected a file error during an initial
load or checkpoint read. Reinstall the task into the RSX-llS system.
HLD .. nodeltask • SLD premature disconnect

SLD has disconnected during a checkpoint write before the transfer is complete.

Utility Error Messages

10-35

NCP
Error Messages

10.5 NCP Error Messages
There are two sets of error messages for NCP: a full set for RSX-IIM and
RSX-I1M-PLUS systems and a subset for RSX-llS systems. There are two
groups of messages within the full set: one group is RSX system-specific. and
the other is standard for all DECnet systems. The error message descriptions
below identify each message as being RSX-specific. RSX-llS. or standard
DECnet.
10.5.1 RSX·11 M/M-PLUS Error Message Format

The general format for an RSX-IIM/M-PLUS ~CP error message is:
NCP .- [<component>,]<command> <diagnostic>. (error message>
[.<-error detai!>] [<extra text>]

where
component

is the affected component (for example. LINE line-id). Appears
only in a command affecting multiple components.

command

is the command that caused the error.

diagnostic

is one of the following values:
FAILED
This command was accepted by NCP. but execution failed.

10-36

DECnet-RSX Guide to Network Management Utilities

NCP

Error Messages

NOT ACCEPTED
NCP would not accept the command. and execution was not
attempted. When NCP rejects a comnland. it displays the
command line with two right angle brackets at the point where
NCP stopped parsing. If NCP was parsing a pair of words.
it points to the first word of the pair even if the second word
was incorrect -- for example.
SET EXECUTOR »ROUTING RIMER 50

NCP does not recognize ROUTING RIMER. Since both words
make up one parameter. NCP rejects the parameter and places
brackets in front of it.
error message

is the major reason for the failure. In most cases. these reasons
are identical for all DECnet implementations (see the DNA
Network Management Functional Specification).
If NCP cannot interpret an internal error code. the error
message field contains one of the following:
Management return #n

An error code of n (decimal) was returned by network
management software.
System return #n

An error code of n (decimal) was returned by the RSX operating
system software.

Utility Error Messages

10-37

NCP
Error Messages

error detail

is a detailed explanation of the failure (for certain error
messages). All DECnet implementations have the same
definitions for these messages. See the DNA .'Vetll'ork
A1anagement Fllnctional Specification for detail~
If NCP cannot interpret an error detail code, the error detail

field contains detail #n, meaning that an error detail of fl
(decimal) was returned by network management software.
extra text

is an additional system-specific explanation of the error
condition. For a description of the contents of this field in an
error from a non-DECnet-RSX implementation, consult the
documentation for that system.

10.5.2 RSX·11S Error Message Format

The general format for an RSX-IIS NCP error message is:
NCP -- <error message>
where
error message

See description given above for RSX-IIM/M-PLUS.

10.5.3 NCP Error Messages
NCP == Bad loopback response

(Standard D ECnet) The message that was returned in a loopback test did not
match the message that was sent. This can be due to a loopback protocol
violation, bad data returned. or bad message length returned.
NCP .. Bad management response

(Standard DECnet) The information returned to NCP either from its internal
network management functions or from the network management listener was
improperly formatted or contained an invalid value. This error condition implies
a programming error in the module that responded to NCP.

10-38

DECnet-RSX Guide to Network Management Utilities

NCP
Error Messages
NCP •. Circuit in wrong state

(Standard DECnet) The current operational state of the circuit precludes the
requested operation. When this message is received on an end node, it usually
means that a circuit is already active. There can be only one circuit active on
an end node at a given time.
NCP •• Component in wrong state

(Standard DECnet) The current operational state of the component precludes
the requested operation (for example, you cannot down-line load a line that is
off). The error detail included with this message identifies the component (for
example. circuit. line, node. and so on).
When a LOOP CIRCUIT command is given on an RSX system. one of the
following RSX system-specific extra text messages may be included:
Circuit is loopback node

The circuit is currently associated with a loop node name. and its state
cannot be changed to do the circuit test.
Circuit not restarted

An attempt was made to return the circuit to normal use before the
circuit had been restarted.
Device off line

The circuit is no longer on the I/O bus. This message is specific to
RSX-IIM-PLUS.
Other management circuit service active

The circuit is currently being used to perform some other network
management circuit service function. such as an up-line dump or a
down-line load.

Utility Error Messages

10·39

NCP
Error Messages
Reassign circuit to former owner failed

At the completion of the test. the owner attempted to return the circuit
to normal use. The attempt failed because the circuit could not be
gi yen back to the owner.
NCP _. Error reading command

(RSX-specific) NCP could not read a command from either the terminal or a
command file because of a hardware error or an unrecognized command read
error.
NCP _. Exceeded command file nesting depth

(RSX-specific) A command file attempted to start another command file when
there were already six command files nested.
NCP _. File 1/0 error

(Standard DECnet) A hardware error was encountered while reading or writing
one of the files necessary to the requested operation. The error detail included
with this message identifies the type of file:
Dump file

Output file for an up-line dump

Load file

Input file for a down-line load

Permanent database

File containing default parameters

Secondary dumper

Input file for the secondary dumper program that runs
in the target node

Secondary loader

Input file for the secondary loader program that runs
in the target node

Tertiary loader

Input file for the tertiary loader program that runs in
the target node

10·40

DECnet-RSX Guide to Network Management Utilities

NCP
Error Messages
NCP -- File open error

(Standard DECnet) One of the files necessary for the requested operation could
not be reserved for use. The error detail is the same as that described above
for the File 110 error message.
NCP -- File privilege violation

(RSX-specific) The file specified with the TO option in a SHOW command is
not available to the user of NCP.
NCP -- Hardware failure

(Standard DECnet) The requested operation could not be performed because a
related hardware component failed to function as needed.
NCP -- Incompatible management version

(Standard DECnet) The network management listener version is incompatible
with NCP.
NCP -- Invalid device name syntax

(RSX -specific) The device name in a command file or TO specification did not
have legal syntax.
NCP -- Invalid directory syntax

(RSX-specific) The directory identification (UIC) in a command file or a TO
specification did not have legal syntax.
NCP -- Invalid file contents

(Standard DECnet) The requested operation could not be performed because
the files contained data of an invalid form or value. The error detail is the
same as that described previously for the File 110 error message.

Utility Error Messages

10-41

NCP
Error Messages
NCP .• Invalid file name syntax

(RSX-specific) The file name in a command file or a TO file specification did
not have legal syntax.
NCP -- Invalid identification format

(Standard DECnet) The identification of the component involved in the
requested operation did not have proper syntax (for example. a numeric
character in a node name). The error detail included with this message identifies
the type of component (for example. line. node. circuit. and so on).
NCP .• Invalid length value, maximum loop length

= 128

(RSX-IIS) The value of the length parameter in a LOOP NODE command
exceeds the buffering capability of subset XPT. Use a smaller value for the
length parameter.
NCP -. Invalid message format

(Standard DECnet) The information sent by NCP either to its internal network
management functions or to a network management listener was improperly
formatted or contained an invalid value. This error condition implies a
programming error in NCP.
NOTE

This error message is also used to indicate standard DECnet
options not supported by D ECnet-RSX.
NCP •• Invalid parameter grouping

(Standard DECnet) The parameters furnished by the user for the requested
operation cannot be included in a single command.

10-42

DECnet-RSX Guide to Network Management Utilities

NCP
Error Messages
NCP •• Invalid parameter value

(Standard DECnet) The value of a parameter furnished by the user for the
requested operation was not acceptable (for example, a numeric parameter out
of range). The error detail included with this message identifies the type of
parameter.
In the case of the events parameter for the LOGG ING command. the following
RSX system-specific extra text message may be provided:
Event cannot be filtered

The ability to enable or disable one of the specified events
implemented.

not

In the case of the length parameter for a LOOP command, one of the following
RSX system-specific extra text messages may be included. In each of these
cases, the length was more than could be handled. and the maximum length
will be included with the error message.
Active looper size exceeded

The requested length exceeds the buffering capability of the active
looper task. Reduce the looper's size or reinstall the looper with a
memory increment.
Mirror size exceeded

The requested length exceeds the buffering capability of the network
management loopback mirror. Either use a smaller length or (on an
RSX system) reinstall the mirror with a memory increment.
NCP •• Line communication error

(Standard DECnet) The requested operation failed because of communication
errors on the involved line. This error condition applies only to functions that
involve direct use of a line. such as down-line load and line loop tests.

Utility Error Messages

10-43

NCP
Error Messages

In the case of a LOOP LINE command, one of the following
system-specific extra text messages may be included:

RSX

Receiver

The looper failed to receive a message that should have been looped
back on the line.
Transmitter

The looper failed to transmit a message on the line. This is specifically
a failure of the transmit function.
NCP -- Line protocol error

(Standard DECnet) The requested operation failed because of protocol errors
on the involved line. This usually implies either incompatible line protocols or
protocol-programming errors. There is a possibility that the condition is caused
by a line hardware error that was not detected by the line protocol.
Line protocol can mean either the Data Link Protocol or the service operation
protocol.
This error condition applies only to functions involving direct use of a line,
such as down-line load and line loop tests.
NCP _. Listener connect failed

(Standard DECnet) The logical link from NCP to the network management
listener could not be connected. This error message generally has one of the
following error details:
Access control rejected

The remote node or the network management listener could not
understand or would not accept the access control information.

10-44

DECnet-RSX Guide to Network Management Utilities

NCP

Error Messages
Invalid node name format

The executor rejected the format of the remote node name (for example.
the name contained illegal characters or was too long).
Invalid object name format

The remote node did not understand the object name format used by
NCP to identify the network management listener.
Local node shut down

The executor node is in the process of shutting down and will not
accept logical link connections.
Network resources

Either the local or the remote network management listener had
insufficient network resources to handle the connect request.
No response from object

The network management listener did not respond. This could be. for
example. due to its responding too slowly or terminating abnormally.
Node unreachable

No path exists to the remote node.
Object too busy

The remote node had insufficient resources available to forward the
connect request to the network management listener.
Remote node shut down

The remote node is in the process of shutting down and will not accept
logical link connections.

Utility Error Messages

10-45

NCP
Error Messages
Unrecognized node name

The destination node name does not correspond to any known node
address.
Unrecognized object

The remote node does not have a network management listener.
NCP .• Listener link disconnected

(Standard DECnet) The logical link from NCP to the network management
listener was unexpectedly disconnected. This error message will have one of
the following error details:
Abort by management

An operator or program used network management to abort the logical
link. NCP recognizes this condition, although DECnet-RSX does not
support the ability to cause it.
Abort by object

The network management listener aborted the logical link. This indicates
a programming error in the network management listener.
Disconnect by object

The network management listener disconnected the logical link. This
indicates a programming error in the network management listener.
Node or object failed

The network aborted the logical link for one of the following reasons:
The remote node terminated abnormally, or the network management
listener terminated abnormally.

10·46

DECnet-RSX Guide to Network Management Utilities

NCP
Error Messages
Node unreachable

The network aborted the logical link because it could no longer find a
path to the remote node.
NCP -- Management program error

(Standard 0 ECnet) The network management software has detected an internal
programming error.
NCP -- Mirror connect failed

(Standard DECnet) The logical link to the network management loop back
mirror could not be connected. This error message generally has one of the
following error details:
Access control rejected

The remote node or the network management loopback mirror either
could not understand or would not accept the access control information.
Invalid node name format

The executor rejected the format of the remote node name (for example,
the name contained illegal characters or was too long).
Invalid object name format

The remote node did not understand the object name format used to
identify the network management loopback mirror.
Local node shut down

The executor node is in the process of shutting down and is accepting
no more logical link connections.

Utility Error Messages

10-47

NCP

Error Messages
Network resources

Either the local or the remote node had insufficient network resources
to connect the logical link.
No response from object

The network management loop back mirror did not respond. This could
be. for example. due to its responding too slowly or terminating
abnormally.
Node unreachable

No path exists to the remote node.
Object too busy

The remote node had insufficient resources available to forward the
connect request to the network management loopback mirror.
Rejected by object

The logical link could not be connected because the network
management loopback mirror rejected the connection. This most likely
implies that the loopback mirror is too busy to accept another logical
link.
Remote node shut down

The remote node is in the process of shutting down and will accept
no more logical link connections.

10-48

DECnet-RSX Guide to Network Management Utilities

NCP

Error Messages
Unrecognized node name

The destination node name does not correspond to any known node
address.
Unrecognized object

The remote node does not have a network management loopback mirror.
NCP -- Mirror link disconnected

(Standard DECnet) The logical link from NCP to the network management
listener was unexpectedly disconnected. This error message generally has one
of the following error details:
Abort by management

An operator or program used network management to abort the logical
link. NCP recognizes this condition. although DECnet-RSX does not
support the ability to cause it.
Abort by object

The network management loop back mirror aborted the logical link. This
indicates a programming error in the network management loopback
mirror.
Disconnect by object

The network management loop back mirror disconnected the logical link.
This indicates a programming error in the network management
loopback mirror.
Node or object failed

The network aborted the logical link because either the remote node
or the network management loopback mirror terminated abnormally.

Utility Error Messages

10-49

NCP
Error Messages
Node unreachable

The network aborted the logical link because it could no longer find a
path to the remote node.
NCP .- NCP program error

(RSX-specific) NCP detected an internal programming error.
NCP -- No room for new entry

(Standard DECnet) The requested operation could not be performed because it
required the addition of a new entry in some database and that database was
full.
NCP -- Not remotely executable

(Standard DECnet) The requested operation cannot be sent to a remote node.
NCP -- Operation failure

The requested operation failed for one of the following reasons: a circuit was
not owned by XPT or could not be turned off. a node was not in the XPT
database. or XPT was not loaded.
NCP _. Operation failure

(Standard DECnet) The requested operation failed. For some RSX
system-specific failures. one of the following extra text messages may be
included:
DLX error #11

A direct line control (DLX) function failed with decimal error code n.
Consult DLX documentation for an explanation of the error code.

10-50

DECnet-RSX Guide to Network Management Utilities

NCP

Error Messages
Insufficient buffer space for additional aliases

The network management software could not internally buffer all the
aliases that could have been displayed.
Insufficient buffer space for additional nodes

The network management software could not internally buffer all the
nodes that could have been displayed.
Insufficient buffer space for additional objects

The network management software could not internally buffer all the
objects that could have been displayed.
Network initializer function failed

The network initializer (NTI!'rIT) failed to perform its part of the
requested operation. The network initializer will write an error message
to the requesting terminal or. in the case of a remotely executed
command. to the system console.
Network initializer not installed

The network initializer could not run because it is not properly installed.
Network loader function failed

The network loader (NTL) failed to perform its part of the requested
operation. The network loader will write an error message to the
requesting terminal or. in the case of a remotely executed command,
to the system console.
Network loader not installed

The network loader could not run because it is not properly installed.

Utility Error Messages

10-51

NCP
Error Messages
Node in wrong state

The requesting operation could not be performed because the executor
node is in the wrong state.
PSI not generated

An attempt was made to perform a PSI operation on a system that
does not support PSI.
Server task not installed

The separate task needed to perform the requested operation is not
properly installed. This could be the active looper for a loop test. the
down-line loader for a down-line load or trigger, or the up-line dumper
for an up-line dump.
NCP .. Oversized management command response

(Standard DECnet) The command message sent by NCP was too big for the
network management listener.
NCP .. Oversized management response

(Standard DECnet) The response message returned by t~e network management
listener was too big for NCP.
NCP .. Parameter missing

(Standard 0 ECnet) The user did not supply a parameter that is necessary for
the requested operation. The error detail included with this message identifies
the type of the parameter.
NCP .. Parameter not applicable

(Standard 0 ECnet) The user supplied a parameter that is not applicable to
the requested operation on the specified component. The error detail included
wi th this message identifies the type of parameter.

10·52

DECnet-RSX Guide to Network Management Utilities

NCP
Error Messages
NCP -- Parameter value too long

(Standard 0 ECnet) The user supplied a parameter value that was too long to
be accepted by the network management listener. The error detail included
with this message identifies the type of the parameter.
NCP -- Privilege violation

(Standard DECnet) The user does not have sufficient privilege to perform the
requested operation.
In the case of a LOOP LINE or LOOP CIRCUIT command. the following
RSX system-specific extra text message may print out:
Service access denied

The line or circuit is not in SERVICE state and the nonprivileged user
cannot perform a line or circui t test.
NCP -- Resource error

(Standard DECnet) Network management had insufficient internal resources to
perform the requested operation.
NCP -- System in wrong state

(RSX-specific) NCP cannot perform the requested function because the DECnet
system (the Communications Executive) has not been properly initialized.
NCP -- System-specific management function not supported

(Standard DECnet) The requested operation is system specific to some 0 EC
systems and is not supported by the network management listener.
NCP -- Unrecognized circuit identification

(RSX-IIS) The circuit specified by the user does not exist or did not contain
necessary information (such as a tributary number).

Utility Error Messages

10-53

NCP
Error Messages
NCP .• Unrecognized command

(Standard DECnet) NCP does not have the command the user entered.
NCP .. Unrecognized command

(RSX-llS) NCP does not have the command that the user entered. or the
command contained an unrecognized keyword or an invalid parameter value
(for example. a node name contained 7 characters instead of the allowed
6-character name).
NCP .. Unrecognized component

(Standard DECnet) The component specified by the user does not exist. The
error detail included with this message identifies the type of component (for
example. line. node. circuit. and so forth).
In the case of the LOOP LINE command. the following RSX system-specific
extra text message may be displayed:
Or line cleared

The line may be defined in the system configuration. but it is in the
CLEARED state.
NCP •. Unrecognized device or unit

(RSX-specific) The device name or unit number in a command file or a TO
file specification could not be found by the RSX operating system.
NCP •. Unrecognized file, device, or directory

(RSX-specific) The file name. device name. or directory (DIC) in a command
file or a TO file specification could not be found by the RSX operating system.
NCP •. Unrecognized function or option

(Standard DECnet) The requested operation is not implemented by the executor.

10-54

DECnet-RSX Guide to Network Management Utilities

NCP
Error Messages
NCP -- Unrecognized keyword

(Standard DECnet) One of the keywords In a command is unknown to NCP.
NCP -- Unrecognized line identification

(RSX-llS) The line specified by the user does not exist or did not contain
necessary information (such as a tributary number).
NCP -- Unrecognized node identification

(RSX-llS) The node specified by the user does not exist.
NCP -- Unrecognized parameter type

(Standard DECnet) One of the parameters given by the user is not implemented
by the executor. The error detail included with this message identifies the
type of parameter.
NCP -- Unrecognized value

(Standard DECnet) A parameter value given by the user was unknown to
NCP.
NCP -- Value out of range

(Standard D ECnet) A parameter value given by the user is out of the range
implemented in NCP.

Utility Error Messages

10-55

NDA
Error Messages

10.6 NDA Error Messages
NDA prints an error message on your terminal when it detects one of the
error conditions described below. These error messages reflect operational
conditions and must not be confused with the diagnostic analysis messages
that NDA generates during the analysis and prints in the analysis listing.
Note that a few of the messages listed below are informational in nature.
while most are fatal errors resulting in termination of the analysis.
NDA -- Analysis output must be directed to an explicit device or file

(Fatal) NDA requires an explicit output file specification. There are no default
output file names.
NDA -- Analysis terminated after n pages

(Informational) ~DA terminated the analysis after generating n pages of
analysis output.
NDA -- Command 110 error

(Fatal) The system returned an error when NDA attempted to read a command
line.
NDA -- Command line syntax error

(Fatal) NDA detected an error in the syntax of an NDA command line. NDA
points to the error within the command line.
NDA -- Crash dump must be input from an explicit device or file

(Fatal) The crash dump input file specification must be explicit. There is no
default file specification for the crash dump input.
NDA -- Device driver missing

(Fatal) You have not loaded the driver for the crash dump input device.

10-56

DECnet-RSX Guide to Network Management Utilities

NDA
Error Messages

NDA -- Error reading crash dump

(Fatal) NDA either could not read or could not access the crash dump input
device. The device may not be properly allocated or may contain bad blocks.
NDA -- Error reading file filename

(Fatal) The system returned an error when )JD A attempted to read the crash
dump file. This could be caused by a device error or a bad block on the
volume.
NDA -- Error reading symbol file filename

(Fatal) The system returned an error when ~DA attempted to read the symbol
table definition file.
NDA -- Error writing analysis file

(Fatal) The system returned an error when NDA attempted to write a line
into the analysis listing file. This could be caused by a problem with the
device. a full volume. or a bad block on the volume.
NDA -- Error writing dump file filename Error =n DSW =Il

(Fatal) The system returned an error when NDA attempted to write into the
binary output file. This condition could be caused by a problem with the
device. a full volume. or a bad block on the volume.
NDA -- Errors detected: n

(Informational) ND A detected n analysis errors during the run.
NDA -- Failed to assign LUN to input device ddu

(Fatal) A directive to assign a LUN failed when NDA attempted to use it to
attach the specified input device before reading the crash dump from the
device. The directive to assign a LUN fails if the device name in the NDA
command line is in valid.

Utility Error Messages

10-57

NDA
Error Messages
NDA •. Failed to extend page buffer • n pages available

(Informational) A directive to extend the task failed when NDA attempted to
use it to expand the page buffer. This problem causes the analysis to take
longer. but the analysis continues with a buffer of 11 pages. each 266 words
long.
NDA •. Failed to open input file filename

(Fatal) One of the following conditions exists:
• The specified device does not exist.
• The volume is not mounted.
• A problem exists with the device.

• The specified UFD does not exist.
• The specified file does not exist.
• You do not have read access privileges.
NDA •. Failed to open output file filename

(Fatal) One of the following conditions exists:
• The specified device does not exist.
• The volume is not mounted.
• A problem exists with the device.

• The specified UFD does not exist.
• The volume is full or the device is write protected.
• You do not have write access privileges to UFD.

10·58

DECnet-RSX Guide to Network Management Utilities

NDA
Error Messages
NDA .• Illegal switch

(Fatal) You have specified an unknown switch or have used a valid switch
after the wrong file specification.
NDA •• Illegal trap . snapshot dump being attempted

(Fatal) NDA has aborted after detecting an odd address or some other type
of fault. This message indicates a software problem.
NDA .- Indirect command syntax error

(Fatal) The name of the indirect command file (@/'ilename) is syntactically
incorrect.
NDA -- Indirect file open failure

(Fatal) NDA could not open an indirect command file specified as @filename
in the NDA command line.
NDA -- Maximum indirect file depth exceeded

(Fatal) You have exceeded the maximum allowable number of nested indirect
command files (only one level of indirection is permitted in NDA). The rest
of the top level command file is executed.
NDA -- No input file specified

(Fatal) You did not supply an input file specification for the crash dump.
NDA -- No output file specified

(Fatal) You have not specified an output file.
NDA -- Output dump file name must be explicit

(Fatal) You have not specified an output dump file.

Utility Error Messages

10-59

NDA
Error Messages
NDA .- Premature end of dump input • /llename being zero filled

(Informational) NDA reached the end of the medium (or end-of-file mark. if a
magnetic tape) before the crash dump output file had been completely filled.
If you expected the file to be completely filled by the dump. this condition
could indicate a problem.
NDA .- Symbol file /llename has illegal format

(Fatal) The specified executive symbol table file has an improper format.
probably caused by entry of the wrong file name. However. this message could
also indicate a problem with the device or medium on which the file is located.
NDA .- Symbol symbol-name not defined in symbol file

(Fatal) NDA did not find a symbol it required for the analysis in the specified
executi ve symbol table file. The analysis may be restarted specifying the ISYM
switch. forcing NDA to continue with the analysis. using a zero value for all
undefined symbols.
NDA .- Transfer complete - ddu may be unloaded

(Informational) The transfer of the crash dump to the output file is finished;
you may unload the crash dump device. This message occurs only when you
have specified a binary save file in the command string to NDA.
NDA .- Unknown get command line error

(Fatal) Unrecognized error has occurred when NDA attempted to read a
command line.
NDA .- Warning kernel PARs do not contain proper values

(Informational) This message indicates that the values contained in the page
address registers are invalid. ND A attempts to finish the analysis using the
indicated values. When restarting the analysis. you must specify the IKMR
switch (Section 6.7.2). This switch forces NDA to use standard mapping values
when converting kernel virtual addresses to physical memory addresses.

10-60

DECnet-RSX Guide to Network Management Utilities

NTD
Error Messages

10.7 NTD Error Messages
NTDEMO prints an error message on your terminal if it detects one of the
conditions described below when you invoke the NTD utility.
NTDEMO .. Network not loaded

The network at the node is not loaded (that is. no network software is running
at the local. node).
NTDEMO .. Unable to connect to remote server

NTD is unable to communicate with NTDEMO on the node you requested
(that is. the host node if you typed >NTD. or the node you specified if you
typed> NTD node-id). This could be due to anyone of the following conditions:
• The node is unreachable.
• The node does not support the NTDEMO server. (This software runs only
on DECnet-RSXIIAS nodes.)
• The node does not have NTDEMO installed.
• The maximum number of links to NTDEMO are busy. (This value is defined
during network generation.)
NTDEMO .. Unable to open network

The network at the node is loaded. but not currently available for network
operations.

Utility Error Messages

10-61

NTINIT
Error Messages

10.8 NTINIT Error Messages
The network initializer (NTINIT) is used with either ~CP or VNP to initialize
the network software. All NTINIT errors are fatal. The attempted operation
cannot succeed unless the problem identified in the message is corrected.
When an ~CP or a VNP command executes locally. error messages are
displayed at the requesting terminal. When the command executes remotely.
error messages are displayed on the remote system console.
Some of the error messages include words printed in italics. The italicized
words are variables. NTINIT replaces them with a specific term. For example.
in the message NTINIT -- Failed to load line line-id. the initializer replaces
line-id with the actual line identification.
NTINIT _. Clearing system

NTINIT is removing the network software from the system because of a
failure on the marked-for-Ioad scan. To recover. use CFE to correct the condition
that caused the failure. Then execute another SET SYSTEl\l command and
try to load again. If the failure recurs. shut down more lines and circuits
before loading again. Repeat this procedure until the load is successful or until
all lines and circuits are shut down.
If the error continues after all lines and circuits are shut down. one of the
processes is at fault. Set one process to the CLEAR state and try the SET
SYSTEM command again. Repeat this action using a different process until
the SET SYSTEM command is successful. The last process to be cleared is
the faulty one. Then use CFE DEFINE commands to reload the lines. circuits.
and processes (except the erring one).
NTINIT _. Comm Exec not loaded

The Communications Executive is not loaded in main memory. Use the NCP
SET SYSTEM command to load the network software.

10-62

DECnet-RSX Guide to Network Management Utilities

NTINIT
Error Messages
NTINIT -- Device controller-id offline

The CSR address for the device does not exist on the bus. Use CFE to change
the CSR value in the configuration file or use the CSR keyword when issuing
the NCP SET LINE command. If the line is set to Of\i during NETGEN,
you must use the following NCP commands to clear the line and reload it:
NCP> CLEAR LINE fine-id ALL
NCP> SET LINE line-id CSR deuice-id STATE ON

NTINIT -- Failed to load line line-id

A SET LINE request failed. You will also receive an NTL error messsage
that gives a more detailed description of the cause of the error (for example,
NTL -- Device off line).
NTINIT -- Failed to load process process-id

A SET PROCESS request failed. You will also receive an NTL error message
that gives a more detailed description of the cause of the error (for example,
NTL -- Process not in system).
NTINIT -- Illegal function

An attempt to reprogram the network software resulted in a programmIng
error.
NTINIT -- Incompatible with RSX-l1 M system

The initializer was built with the wrong RSX IlM.STB file. Rebuild the network
software with the correct RSXIIM.STB file.

Utility Error Messages

10-63

NTINIT
Error Messages
NTINIT •• Incompatible with RSX-11 S system

The initializer was built with the wrong RSXIIS.STB file. Rebuild the network
software with the correct RSX 11S.STB file.
NTINIT •. Network ACP (NET ACP) not installed

NETACP must be installed to perform the SET EXECUTOR STATE ON
operation. To clear the problem. use the MCR INSTALL NETCAP command
to install the network ACP.
NTINIT .- Network loader (NTL. .. ) not installed

NTL must be installed to perform the NCP SET SYSTEl\I! operation. To clear
the problem, use the MCR INSTALL NTL command to install the network
loader.
NTINIT .- NS: assignment failure

The initializer could not assign one of its LUNs to the network device. There
is no recovery procedure from this failure.
NTINIT •• NW: assignment failure

The initializer could not assign one of its LUNs to the PSI network device.
There is no recovery procedure from this failure.
NTINIT .- PLB allocation failure

There is not enough free space in the dynamic storage region (DSR) to allocate
the XPT physical link block database. You must run a system generation
again, allocating enough free space in the DSR.
NTINIT .- Router priority database allocation failure

There is not enough free space in the dynamic storage region (DSR) to allocate
the router priority database.

10-64

DECnet-RSX Guide to Network Management Utilities

NTINIT
Error Messages
NTINIT -- Routing control task not installed

The routing control task must be installed to perform the SET EXECUTOR
STATE ON command. Gse the :MCR INSTALL <netuic> RCPl command to
install the task.
NTINIT -- X25 ACP (X25ACP) not installed

The X25ACP must be installed to set module X25-SERVER to ON. Use the
lVICR INSTALL X25ACP command to install the X25ACP.

Utility Error Messages

10-65

NTL'
Error Messages

10.9 NTL Error Messages
The network loader (NTL) loads and unloads network software in response to
NCP commands. When an NCP command executes locally, NTL error messages
are displayed on the requesting terminal. When the command executes remotely.
NTL error messages are displayed on the remote console terminal.
There are ten types of NTL error messages. The format of each is outlined
below. The term message-text used in these sample formats is replaced with
the actual message in tHe error message descriptions that follow. The italicized
word uar is replaced with a run-time variable in the actual message. Some of
the variables are network processes, device driver names, controller names.
line names, partition names, file names. vector values. and RSX device names.
Variable fields are ignored in the alphabetization of error messages in this
chapter.
NTL

message-text

NTL

var message-text

NTL

Config File •• message-text

NTL

uar: Device Tables .• message-text

NTL

var Image File •• message-text

NTL

uar Microcode File .- message-text

NTL

oar Process File •. message-text

10-66

DECnet-RSX Guide to Network Management Utilities

NTL
Error Messages
NTL

var Symbol Name -- message-text

NTL

var Template -- message-text

NTL

var Template File -- message-text
NOTE

Only recoverable NTL errors are listed in this guide. Any
unlisted error message that you receive reflects an unrecoverable
error. Call your Digital representative for assistance.
NTL -. deu-id: allocation failure

There is not enough space to allocate the RSX -111\-1 device data structures
(DCB. DCB. and SCB) for one of the network "devices." In this case. device
does not refer to hardware. It refers to a software structure to which the user
program assigns its LeNs and directs its QIOs.
NTL -. CCB allocation failure

There is not enough space for all the CCBs. It is not known how many were
successfully allocated.
NTL _. CETAB allocation failure

There is not enough dynamic memory to allocate the CET AB database.
NTL -- Channel var still active

An attempt was made to issue a CLE AR PROCESS command for an LLC
before all its lines were set to OFF. Set all the lines to OFF and repeat the
command.

Utility Error Messages

10·67

NTL
Error Messages
NTL •. Circuit not in system

An attempt was made to load a circuit that is not in the system.
NTL •. Comm Exec has been deallocated

The space for the Communications Executive has been deallocated.
NTL •. Comm Exec incompatible with RSX·11 M system

The Communications Executive was built with the wrong RSXIIM.STB file.
NTL .• Comm Exec not loaded

An attempt was made to perform an operation that requires the
Communications Executive (CEX) to be loaded and it is not. Load the CEX
with the ~CP SET SYSTEM command.
NTL .• Config File •. Binary buffer overflow

The NTL end-of-task buffers are not large enough to hold the input. Install
NTL with an INC option.
NTl .• Config File •• Device uar UNIBUS run mask missing

The UNIBUS run mask is missing for the specified device.

10·68

DECnet-RSX Guide to Network Management Utilities

NTL
Error Messages
NTL -- Config File -- Event filter control block allocation failure

There is not enough network pool and DSR to allocate an event filter block.
NTL -- Config File _. Illegal CSR address

The specified CSR address is not a legal value. Use the correct CSR address.
NTL -- Config File -. LLC$OF process extension too big

One system process has an extension that makes it larger than the allowed
4K maximum.
NTL -- Config File -- Non-UMR-mapped area is too large

The non- CMR-mapped area specified in the P AR$D F macro is too large for
the network pool partition.
NTL -- Config File -- Not enough contiguous UMRs

Contiguous UM Rs are needed to map the network buffer pool. Issue the SET
SYSTEM command before you begin fragmenting the GIVIRs by running other
jobs. If this fails. you can use VNP to load the network software into the
operating system file instead of using NCP on the in-core image. VNP is not
available on RSX-IIM-PLUS systems.

Utility Error Messages

10-69

NTL
Error Messages
NTL .• Config File .• Object or remote block allocation failure

There is not enough network pool or DSR to allocate the object or remote
block. The line from CET AB where the failure occurred is displayed so that
you can determine which object or remote block was not allocated.
NTL •• Config File .• Open failure (·error code.)

The system was unable to open the CETAB.MAC file. See the RSX system
documentation for the meaning of the ~SX I/O error code.
NTL •. Config File .. Partition uar busy

The partition name specified for the network pool is busy.
NTL •• Config File .• Partition uar not common

The partition specified for the network pool is not a common partition. Remove
that partition and re-create it with the system-controlled attribute:
MCR>SET /NOMAIN=partition-name
MCR>SET /MAIN=partition-name:aaaa:bbcOM

NTL •• Config File •• Partition var not in system

The partition specified for the network pool is not in the system.
NTL •• Config File •• Partition var not system controlled

NTL requires the partition to be system controlled. This error indicates that
the partition was created as a task or common partition. Remove that partition
and re-create it with the system-controlled attribute:
MCR>SET /NOMAIN=partition-name
MCR>SET /MAIN=partition-name:aaaa:bbSYS

10-70

DECnet-RSX Guide to Network Management Utilities

NTL
Error Messages
NTL -- Config File -- Partition val' too fragmented

There is not enough contiguous space in the partition to load a process.
NTL -- Config File -- Partition car too small for ROBs/SOBs

This error pertains only to the network buffer pool partition. The network
buffer pool is not large enough for the large and small data buffers. C se CFE
to reduce the buffer counts and/or sizes or to re-create a larger partition.
NTL -- Config File -- Read failure (-error code.)

The system was unable to read the CETAB.MAC file. See the RSX system
documentation for the meaning of the RSX I/O error code.
NTL -- Config File -- Secondary CSR off line

The specified secondary CSR (from CETAB.M:AC) is off line.
NTL -- Config File -- Sub-PCB allocation failure

There is not enough space for a parti tion control block for the network buffer
pool.
NTL -- Config File -- SVC descriptor allocation failure

There was not enough DSR or network pool to allocate the SVC descriptor.
NTL -- Config File -- UMR block allocation failure

There is not enough space for a UMR assignment block.

Utility Error Messages

10-71

NTL
Error Messages
NTL •• Config File -. Vector not in system

The controller's vector address specified in the configuration file does not exist
in your system's vector space.
NTL .• val' Device 1/0 error, CSR
var was read

= val', RAM address = l..'ar was written.

An attempt to load microcode for a KMC device failed due to an input/output
failure. One possible cause could be a hardware failure.
NTL •. Device off line

An attempt was made to load a device that is off line.
NTL •. Device uar off line

An attempt was made to load a device that is off line.
NTL •. Device dCl.'-id: still active

An attempt was made to clear an LLC process when the associated device is
still active.
NTL _. Device dev-id: still mounted

An attempt was made to clear an LLC process when the device associated
with it is still mounted.
NTL •• dev-id: driver already resident

The executive data structure for the driver associated with the LLC process
being loaded already exists.
NTL •• val' Ica allocation failure

There is not enough space in the dynamic storage region (DSR) to allocate an
interrupt control block (ICB).

10-72

DECnet-RSX Guide to Network Management Utilities

NTL
Error Messages
NTL _. var Image File _. Label block read failure (-error code.)

The system is unable to read a label block. See the RSX system documentation
for the meaning of the RSX I/O error code.
NTL •• var Image File _. Open failure (-error code.)

The attempt to open the specified file failed. See the RSX system documentation
for the meaning of the RSX I/O error code.
NTL _. var Image File .• Read failure (·error code.)

The attempt to read a record from a specified file failed. See the RSX system
documentation for the meaning of the RSX I/O error code.
NTL _. Incompatible with Comm Exec

NTL has been built with the wrong CEX.STB file. Rebuild NTL with the
correct CEX.STB file.
NTL _. Incompatible with RSX·11 M system

NTL has been built with the wrong RSX 11M.STB file. Rebuild NTL with the
correct RSX I1M.STB file.
NTL _. e'ar KRB allocation failure

There is not enough space in either the network pool or the dynamic storage
reg-ion for the controller request block (KRB).
NTL _. Line not in system

An attempt was made to set a line that does not exist.

Utility Error Messages

10-73

NTL
Error Messages
NTL .• Line still active

An attempt was made to clear a line that was still Ol'i. Set the line to OFF
and reenter the command.
NTL .• Line car still ready

An attempt was made to perform a CLEAR PROCESS on a DLC or a DDM
controller before all of its circuits were turned off and unloaded. Set the circuits
to OFF and reenter the command.
NTL .• var Line table allocation failure

There is not enough space in DSR for either a device line table or an LLC
process database.
NTL •• MUX update only

This is a reminder that the vector and the CSR for the device specified in
the command line have not been changed. All lines on a multiplexer device
are loaded when any line on the device is loaded. Therefore. all subsequent
loads for other lines on this device do not change the vector or the CSR.
NTL .. uar Process File •• Incompatible with Comm Exec

The process has been built with the wrong CEX.STB file.
NTL •• var Process File •• Label block read failure (·error-code.)

An attempt to read a label block for a process task image file failed due to
an input/output error. See the RSX system documentation for the meaning of
the RSX I/O error code.

10-74

DECnet-R8X Guide to Network Management Utilities

NTL
Error Messages
NTl -- l.'ar Process File •. Open failure (·error-code.)

An attempt to open the task image file for the specified process failed due
to an input/output error. See the RSX system documentation for the meaning
of the RSX I/O error code.
NTl •• var Process File •. Partition uar busy

The partition is occupied by either another network process or an RSX-lll\1
resident library. The current occupant must be unloaded.
NTl •• car Process File •• Partition val' not common

NTL requires the partition to be common. The partition has been created as
either task or system controlled. Remove the partition and re-create it with
the common attribute:
MCR>SET /NOMAIN=partition-name
MCR>SET /MAIN=partition-name:aaaa:66b : COM

NTl .• car Process File •. Partition uar not in Exec space
The Communications Executive (CEX) partition must be contained completely
in the first 20K words of physical memory. This error indicates that the
ending address of the CEX partition is larger than this limit. The CEX contains
an end-of-partition buffer pool. If you exceed the limit by a small amount (100
or 200 octal), you can try to reduce the CEX' s partition size. Otherwise, you
should repeat the NETGEN.
NTl .. val' Process File •• Partition val' not in system
The partition specified in your command does not exist. Either create the
partition that NTL is seeking, or rebuild the component to change the partition
assignment.

Utility Error Messages

10·75

NTL
Error Messages
NTL .• var Process File .• Partition car sub·PCB allocation failure

There is not enough space for a partition control block (PCB) for the named
process.
NTL .• uar Process File •• Partition uar too fragmented

This error pertains to system~controlled partitions only. The size of the largest
free space in the partition is smaller than the size of the process being loaded.
The current occupants of the partition must be rearranged to make a free
space of the size needed. NTL does not activate the RSX-IIM shuffler task.
Manual recovery is necessary.
NTL .• var Process File •• Partition var too small

This error pertains to the common partition only. The partition is smaller
than the size of the process being loaded. The partition must be created with
a larger size. Refer to the TKB map for the process to determine the size
needed.
NTL .• var Process File •. Read failure (·error-code.)

An attempt to read a record from the process task image file failed due to
an input/output error. See the RSX system documentation for the meaning of
the RSX I/O error code.
NTL .• Process may not be unloaded

An attempt was made to unload a process that is required for network operation
and cannot be unloaded.
NTL .• Process not in system

An attempt was made to set a nonexistent process.
NTL .• Reconfiguration device not in system

The reconfiguration device for the network devices
device with the DECnet process called DLX.

10·76

DECnet~RSX

not loaded. Load the

Guide to Network Management Utilities

NTL
Error Messages
NTL -- var Symbol Table File -- Open failure (-error-code.)

An attempt to open the system table file for the specified process failed due
to an input/output error. See the RSX system documentation for the meaning
of the RSX I/O error code.
NTL -- uar Symbol Table File -- Read failure (-error-code.)

An attempt to read a record from the specified system table file failed due
to an input/output error. See the RSX system documentation for the meaning
of the RSX I/O error code.
NTL .. System not built with network support

This message needs no explanation.
NTL .• uar Template .- Library block allocation failure

There is no space in the network buffer pool.
NTL _. uar Template -- Resource allocation failure

There is not enough space for the allocation size needed. (Another error message
follows that contains the allocation type being attempted.)
NTL .- uar Template _. Vector var not available

The indicated vector is assigned to another user. The vector must be deassigned
from the curren t user.
NTL -- va,. Template -- Vector var not in system

The vector specified in the command exceeds the maximum value assigned at
NETGEN.

Utility Error Messages

10-77

NTL
Error Messages
NTL .- uar Template File _. Open failure (-error-code.)

An attempt to open the template file for the specified process failed due to
an input/output error. See the RSX system documentation for the meaning of
the RS X I/O error code.
NTL .- uar Template File -- Read failure (-error-code.)

An atternpt to read a record from the specified template file failed due to an
input/output error. See the RSX system documentation for the meaning of the
RSX I/O error code.
NTL .- Timer cells not found

NTL could not find the process timer cells in the A UX process.
NTL .- Vector not in system

The vector specified in the command line does not exist in your system' s
vector space. The upper limit of the vector space is determined during
SYSGEN. Repeat both SYSGEN and NETGEN.
NTL .- var Vector set-up error

Some other user has stolen one or more of the interrupt vectors. This occurred
after NTL first verified that the interrupt vectors were available. but before
NTL built the line table and pointed the vector at the table. The vector must
be deassigned from the other user.
NTL .- * WARNING * -- Failed to reinitialize HRC

The network loader was unable to successfully reinitialize HRC after loading
a network device. This could affect the use of the system utility ... CON.
NTL -- * WARNING * -- System name changed to "name"

The system name specified during SYSGEN does not match the node name
specified during NETG EN. The system name has been changed to the node
name in NETG EN and will remain so until the system is rebooted.

10-78

DECnet-RSX Guide to Network Management Utilities

TRI
Error Messages

10.10 TRI Error Messages
TRI displays an error message on your terminal when It detects one of the
errors described below. These messages reflect operational conditions. While
most result in termInation of the trace interpreter task. a few are for
information only.
TRI .. All frames were excluded by III or ICH

(Informational) There were no frames traced on the lines or channels that you
specified with the ILl or ICH switch.
TRI .. Cannot open input file

(Fatal) One of the following conditions exists:
• The specified device does not exist.
• The volume is not mounted.
•

A problem exists with the device.

•

The specified UIe does not exist.

•

The specified file does not exist.

•

You do not have read access privileges.

Utility Error Messages

10·79

TRI

Error Messages
TRI .. Cannot open output file

(Fatal) One of the following conditions exists:
• The specified device does not exist.
• The volume is not mounted.
• A problem exists with the device.
• The specified UIC does not exist.
• The volume is full or the device is write protected.
• You do not have write access privileges to the VIC.
TRI .. Command I/O error

(Fatal) The system returned an error when TRI attempted to read a command
line.
TRI .. Error closing output file

(Fatal) TRI failed to close the trace-listing file.
TRI .. Error reading input file

(Fatal) The system returned an error when TRI tried to read the trace input
file. This could be caused by a device error or a bad block on the volume.

10-80

DECnet-RSX Guide to Network Management Utilities

TRI
Error Messages
TRI -- Error writing output file

(Fatal) The system returned an error when TRI attempted to write a line into
the trace-listing file. This could be caused by a problem with the device. a
full volume. or a bad block on the volume.
TRI -- Failed to spool output file

(Fatal) The system failed to spool the trace-listing file.
TRI -- Illegal character in filespec

(Fatal) One of your file specifications IS incorrect.
TRI -- Illegal command stri ng

(Fatal) TRI detected an error in the syntax of the TRI command string.
TRI _. Illegal switch or switch value_

(Fatal) You have specified an invalid switch in the TRI command string, or
you have given an invalid value to a switch.
TRI .- Incompatible switches

(Fatal) You have specified an illegal combination of switches. Check that you
have not specified any switches other than ISP or I-SP with the I-IN switch.
TRI _. Input file is not a trace dump file

(Fatal) The input file you have specified is not a trace dump file produced as
output from an NCP SET TRACE command.
TRI _. Trace file is empty

(Informational) The trace file specified as the input file IS empty.

Utility Error Messages

10-81

VNP
Error Messages

10.11 VNP Error Messages
VNP .. Account field too long

The account field is limited to 16 characters.
VNP .. Alias not in system

An attempt was made to reference an alias that is not in the system.
VNP .. Attempt to reference block number that is not within the system
image file block-number SIAS:ll ADDRESS:m

An attempt was made to reference the specified block number. which is not
in the system image file. This error is often caused by building a system
image file that is smaller than the real memory size while top-down loading.
Use CFE to disable top-down loading.
VNP .. CET AS data structures are inconsistent

The data structures in the Communications Executive configuration file
(CETAB) are inconsistent. Possibly the CET AB.TSK file is corrupt. Perform
another NETGEN to obtain an uncorrupt CETAB.TSK file.
VNP .. Circuit not in system

The specified circuit is not in the system.
VNP .. COMEXEC symbol missing from symbol table symbol-id

The specified symbol is not in the Communications Executive symbol table.
VNP .. Communications Executive load failed

VNP could not successfully load the Communications Executive.

10·82

DECnet-RSX Guide to Network Management Utilities

VNP
Error Messages
VNP .. Communications Executive symbol table file open failure error-code
/'ilename

The Communications Executive symbol table file (filename) failed to open. The
error code is returned by the operating system' s file services. All the network
files must reside in the UIC defined by the NETUIC in the system image
file. Check the NETUIC in the system image file by using the VMR SET
INETUIC command.
VNP .. Configuration file read error

VNP could not read a record from the CETAB source file.
VNP .. Controller number too large

The controller number on the line identification is illegal.
VNP .. Error parsing file name . /llename

The file name of the operating system disk lmage file is invalid.
VNP .. Event cannot be filtered

This message indicates that the ability to enable or disable one of the specified
events is not implemented.
VNP .. Executive symbol missing from symbol table symbol-id

The specified symbol is not in the Communications Executive symbol table.
VNP .- Executive symbol table file open failure error-code /rlename

The RSX executive symbol table file (filename) failed to open. The error code
is returned by the operating system's file services. The system image file. its
symbol table. and all network files must reside under the same UIC.

Utility Error Messages

10-83

VNP
Error Messages
VNP .• Failed to close system image file error-code

The system image file failed to close. The error code
operating system's fil~ services.

returned by the

VNP .• Failed to get command line

VNP could not read a command line.
VNP .. Failed to load a process

VNP did not successfully load a process that was marked for load. You can
list all processes to find out which process did not load.
VNP .. Failed to load a system line

VNP did not successfully load a line that was marked for load. You can list
all lines to find out which line did not load.
VNP .• Function not implemented

An attempt was made to execute an unimplemented VNP function.
VNP .• Illegal event code

The event code given is invalid.
VNP .• Illegal executive size nnn

The executive size (nnn) is illegal. This is probably caused by a corrupt system
image file.
VNP .• Illegal line cost

The line cost must be in the range of 1 to 1022.
VNP .• Illegal multipoint active ratio

The mUltipoint active ratio must be in the range of 1 to 255.

10·84

DECnet-RSX Guide to Network Management Utilities

VNP
Error Messages
VNP -- Illegal multipoint dead ratio

The multipoint dead ratio must be in the range of 1 to 255.
VNP .. Illegal node address

The node address must be in the range of 1 to 1023.
VNP .- Illegal object type

The object type numbers must be in the range of 1 to 255.
VNP .- Illegal tributary address

The tributary addresses must be in the range of 1 to :255.
VNP .- Illegal unit CSR address

The unit CSR address is invalid.
VNP -- Insufficient space in template-processing buffer (TMP$$A psect)
Current size is Il bytes. but it should be expanded to at least m bytes

VNP's processing buffer is n bytes long, but it requires m bytes for the
configuration. Edit VNPGEN.GMD and extend the buffer size. Then perform
another task build on VNP and try again.
VNP -- Invalid hello timer value

The value specified for the hello timer is invalid. The value must be within
the range of 1 to 65.535.
VNP -- Invalid line identification

The line identification is not in the proper format.

Utility Error Messages

10-85

VNP
Error Messages
VNP .• Invalid node option

Certain node options are valid only on the executor node. while others are not
allowed. You must verify that all options selected are valid for the node
specified.
VNP .• Invalid parameter grouping

The combination of parameters specified is invalid. For example.
VNP>SET LOGGING CONSOLE EVENTS 2.0 CIRCUIT DMC-O NODE A
is invalid because you cannot specify two entities to qualify events that are
to be logged. You can specify the circuit or the node. but not both. If you
want two entities to be logged, you must enter two separate commands.
VNP .• 1/0 error accessing system image file error-code

A disk I/O error occurred when VNP accessed the system image file. The
error code is returned by the operating system's file services.
VNP .• KMC microcode load failed

VNP failed to load the KMC microcode.
VNP .• Line name too long

Line names must be 1 to 3 Radix-50 characters.
VNP .• Line not assigned to XPT or DLX

An attempt was made to access a line that is not on a network communications
device assigned to X PT or D LX.
VNP .• Line not in system

The specified line is not in the system.

10·86

DECnet-RSX Guide to Network Management Utilities

VNP
Error Messages
VNP •• Line parameter not applicable

The line option is valid on SET NOD E requests only if the node identification
is a name.
VNP .. Maximum controllers limited to 64

The maximum controller count for the SET PROCESS request is limited to
64.
VNP .• Maximum lines limited to 64

The maximum line count for the SET PROCESS request is limited to 64.
VNP .• NETACP must be "fixed" in RSX·11S systems

NETACP is not fixed in an RSX-llS System. Fix NETACP using VMR before
starting VNP.
VNP .• NETACP not installed

NETACP is not installed. Install NETACP using V~IR before restarting VNP.
VNP •• Network buffer pool is too small

The network buffer pool is not large enough to load the system software. You
will have to use V~IR on your system image to change the size of the network
pool partition.
VNP .• Network initializer not installed

The network initializer (NTINIT) is not installed. Install NTINIT with VMR
before restarting VN P.
VNP .• Network pool partition not in the system

VNP could not find the network pool partition as specified during NETGEN.

Utility Error Messages

10-87

VNP
Error Messages
VNP .• Node in wrong state

The node is not in the proper state to perform the requested function.
VNP .• Node name too long

Node names are limited to a maximum of 6 character').
VNP .- Node not in system

An attempt was made to reference a node that is not in the system.
VNP .• Non·UMR·mapped area is too large

The non-UMR-mapped portion of the network pool is larger than the entire
network pool.
VNP .• Not enough contiguous UMRs to map network pool

The network pool needs too many UMRs to be loaded. You should try to
reduce the size of the network pool.
VNP .• NTINIT must be "fixed" in RSX·11S systems

NTINIT is not fixed in an RSX-llS system. Fix NTINIT using VMR before
restarting VNP.
VNP .• Object not in system

An attempt was made to reference an object that IS not contained in the
system.
VNP .• Object/remote block allocation failure

There is not enough network pool or dynamic storage space to allocate a
remote name block or an object block.

10-88

DECnet-RSX Guide to Network Management Utilities

VNP
Error Messages
VNP •. Object task name too long

Object task names must be 1 to 6 Radix-50 characters.
VNP •• Open failure on configuration file

VNP could not open the CET AB source file.
VNP •. Open failure on system image file error-code lilename

The system image file (filename) cannot be opened. The error code is returned
by the operating system's file services.
VNP •• Owner process name too long

Process names must be 1 to 3 Radix-50 characters.
VNP •• Partition name too long

The partition name must be 1 to 6 Radix-50 characters.
VNP •• Password field too long

The password field is limited to 8 characters.
VNP •• PLB allocation failure

VNP was not able to allocate enough space for the XPT databases.
VNP •• Process name too long

Process names must be 1 to 3 Radix-50 characters.
VNP •• Resource error trying to allocate CCBs

There is not enough dynamic storage space in your system to allocate the
control buffers.

Utility Error Messages

10-89

VNP
Error Messages
VNP .. Reverse mapping table inconsistent

The reverse mapping table has been corrupted.
VNP .. RSX·11 M system pool allocation failure

The system pool is empty. Use VMR to increase the size of the system pool.
VNP .. Supposed system image file not actually a system image filename

The indicated file is not a system image file.
VNP .. Syntax error

The command line is not correct.
VNP .. System image does not contain a GEN partition

The default partition for network software is GEN. The system image file
does not contain a G EN partition.
VNP .. System image file corrupted because VNP was terminated abnormally
filename

A previous execution of VNP terminated abnormally and may have corrupted
the system image file (filename). Recopy the system image file before restarting
VNP.
VNP .. System image must be extended to n blocks if the GEN partition is
to be contained within the image

The default partition GEN is not within the system image. Use the PIP
command for copying files with the IBL:n. switch to enlarge the output file.

10·90

DECnet-RSX Guide to Network Management Utilities

VNP
Error Messages
VNP -- The Communications Executive data structures are too large for VNP's
internal buffer. The buffer (CET$$A psect) can be expanded to 2776
bytes maximum (from the current n bytes), but this configuration
needs m bytes. This error is not recoverable without source
modifications.

VNP's internal buffers cannot accommodate the Communications Executive
configuration file (CETAB). Reduce the size of the configuration.
VNP -- Too many object task copies

A maximum of 63 object task copies IS allowed.
VNP -- Tributary number too large

Tributary numbers must be in the range of 1 to 255.
VNP -- UMR block allocation failure

There is not enough dynamic storage space to allocate a UMR block.
VNP -- Unable to dynamically allocate network buffer pool

VNP could not allocate enough partition space to load the network pool.
VNP -- Unit number too large

The unit number on the line identification is illegal.
VNP -- Unspecified error during CON FIG file scan

VNP could not successfully parse all the definitions in the CET AB source file.
VNP -- User identification field too long

The user identification field is limited to a maximum of 16 characters.

Utility Error Messages

10-91

VNP
Error Messages
VNP •• XPT channel table inconsistent

The XPT channel table has been corrupted.
VNP •• XPT database not allocated

The XPT process is loaded but the data structures are not.
VNP •• XPT process not loaded

The XPT process is not loaded.

10-92

DECnet-RSX Guide to Network Management Utilities

A
Process Names

Table A-I lists processes alphabetically by type. including device driver
processes and software protocol-related processes for OECnet and PSI.
Table A-1: DECnet-RSX Processes
Process Name

Function

Communications Executive processes

AUX
DLX
EVL

Auxiliary process
Direct Line Access Controller
Event Logger process

OECnet device drivers

DHV
DL
DLV
DMC
DMP

DMV
DPV
DU
DUP

DUV

o HU-l1 driver
o HV-l1 driver
OL-11 driver
OLV-ll driver
DMC-111DMR-l1 driver
DMP-l1 driver
OMV-Il driver
DPV-II driver
D U-II driver
DUP-II driver
OUV-II driver

A-1

Table A-1 (cont.): OECnet-RSX Processes
Process Name

Function

DV
DZ
DZV
KDP (KMC/DUP)
KDZ (KMC/DZ)
PCL
UNA
QNA

DV-ll driver
DZ-ll driver
DZV-Il1DZQ-ll driver
KD p.: 11 driver
KDZ-ll driver
peL driver
DEUNA driver
OEQN A driver

OeCnet processes

DCP

EPM
ECL
XPT
NCT
RTH
LAT

Implements ODCMP; included for all systems with devices· other
than DMC-ll, DMP-Il, OMR-ll, DMV-ll, PCL-lIB. DEUNA,
and DEQNA
Ethernet Protocol Manager; included for all systems with
Ethernet devices
End Communications layer process
Routing layer process
Network Command Terminal process
Remote Terminal Host process
LA T device driver process

PSI device drivers

KMX
KMY
SDP
SDV

KMX-ll driver
KMY-II driver
DUP-ll driver
DPV-ll driver

PSI processes

DLM
LAB
NW
PLI

A-2

Data-link-mapping process
X.25 level 2 LAPB protocol process
PSI user interface process
X.25 level 3 (packet level) process

DECnet-RSX Guide to Network Manag0ment Utilities

B
Object Type Codes

Table B-1 defines valid object type code values and describes their process
type for network management. The values are expressed as decimal byte values.
Digital reserves the right to add object types or to make changes to the
descriptor formats used by the object types.
Table B·1: Object Type Codes
Object Type
Code

Process Type

General task, user program
File Access Listener -- FAL/DAP, Version
Resflrved for D ECnet use
RSX -1 1LVI Task Control -- Version 1
Reserved for DECnet use
RSX-IIM Task Control -- Version 2
TLK utility
File Access Listener -- F AL/D AP, Version 4
Host Task Loader
Network Information and Control Exchange
RSTS/E media transfer program
Reserved for D ECnet use
Network terminal handler
Reserved for D ECnet use
Network management loop back mirror

1
2-4
5
6-14
15
16
17
18
19
20
21-22
23
24

(continued on next page)

B·1

Table B-1 (cont.); Object Type Codes
Object Type
Code

Process Type

26
27-28
29
30-28
42
43-62
63
64-127
128-255

Network management event receiver
Reserved for DECnet use
PHON E utility
Reserved for D ECnet use
Heterogeneous terminal host
Reserved for DECnet use
RSX DECnet test tool
Reserved for D ECnet use
Reserved for customer extensions

B-2

DECnet-RSX Guide to Network Management Utilities

Index

A
Abbreviating command keywords,
1-7
Access control information,
to specify for remote node,
1-102
Access control verification,
to specify in permanent
database, 1-36, 1-57
to specify in volatile database,
1-98, 1-160, 1-162, 1-166
Alias node name,
to display alias information,
1-129
to remove, 1-14
to specify, 1-95
Areas,
to display area information,
1-130

B
Buffers,