Digital PDFs

AA-J517D-TC

2000

37 pages

Original

1.3MB

Document:	DECnet-RSX Release Notes Sep85
Order Number:	AA-J517D-TC
Revision:	0
Pages:	37
Original Filename:

OCR Text

Networks· Communications

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

-----

DECnet-RSX
Release Notes

~D~DD~D

ware

DECnet-RSX
Release Notes
Order No. AA-J517D-TC

September 1985
DECnet-RSX Release Notes inform the user of updated information not
included in the manual set. This information covers software and/or documentation errors or changes made late in the development cycle, plus
installation and operation information. This manual should be read
before others in the manual set.

Supersession/Update Information: This is a new manual.
Operating System and Version:

RSX-11 M V4.2
RSX-11S 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-J517D-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

~DmDDmD

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

1.0
1.1
2.0
2.1
2.2
2.3

3.0
4.0
4.1
4.2
5.0
5.1
5.2

5.3
5.4
5.5
5.6
5.7
5.8
6.0
6.1
6.2
6.3

6.4
6.5
7.0
7.1
7.2
7.3

7.4
7.5
8.0
8.1
8.2
8.3
8.4
8.5
8.6

8.7
9.0
9.1
9.2
9.3

9.4
9.5
9.6

9.7
9.8
10.0
10.1

Release DescrIption
... .
New Features . . . . . . .
Reporting and Isolating Problems .
Reporting a User Problem . . . .
Investigating and Correcting Serious Error s
Reporting a Documentation Problem
Documentation Errors . .
NETGEN Notes . . .
Prerequisites
Micro/RSX
pregenerated M-PLUS Systems
System Selection . . . . . .
Processor Type in RSXMC.MAC
Startup File Customization .
Device Questions . . . . . .
Swapping NETGEN Input Disks
Post NETGEN Suggestions
Abnormal NETGEN Termination
Generation on VMS Hosts
Device notes . . . . . .
DEUNA/DEQNA . . . . .
DMP and DMV Multipoint Controllers .
Powerfail Recovery . . . . . . .
. ...
Error Counters . . . . . . . . .
Device CSRs for Down-line Loaded Systems
System Notes . . . . . . . . .
System Pool Usage
... . .
Network Resource Problems
Tuning . . . . . .
Powerfail Recovery .
Running SHUTUP . . .
Utility notes
NCP, CFE, and VNP
CFE
NCP
VNP
· .
NFT
FTS
FAL
MCM
· .
NFARs
· .
NCT
RMT
· .
Use of RMT from Command Files
Terminal Characteristics . . . . .
Aborting RMT . . . . . .
· .
NETACP . . . . . . . . . . . . .
· .
NTDEMO .
LAT Control Program (LCP)
LDB Size . . . . . . . . .

1
L.

2
2
~

...

iii

.
.

·
•

.
.

·
·

.
.
.

4
4
5
5
5
5
5
6
7
7
7
7
8
8
8
9

10
10
10
10
11

._
. .
..

..
. .
..

11
12
12
12
12
13
13
14
14
14
15
16
17
17
18
18
18
19
19
19
19
20

10.2
11. 0
11.1
12.0
12.1
12.2
12.3
12.4
12.5
12.6
13.0
13.1

13.2
13.3
13.4
13.5
13.6
13.7
14.0

Permanent Database .
LCP Error Messages .
PHONE
. . . . . .
Cross-system File Transfer Notes.
RSX-llM/M-PLUS File Transfer Capabilities
VAX/VMS V4.0 File Transfer Capabilities
....
RSTS DECnet/E V2.0 File Transfer Capabilities
RT-ll V2.0 File Transfer Capabilities
lAS V3.0 File Transfer Capabilities
..... .
TOPS-20 Fl~e Transfer Capabilities . .
unsupported Software . . . . . . . . . . .
CEDUMP - Communication Executive Database Dump
Program . . . .
CEDUMP Switches
General Switches
....... .
/HE - List the CEDUMP Switch Descriptors .
/AL - Dump All Available Data Structures .
Comm/Exec Specific Switches
DECnet Specific Switches . . . . . .
RVT . . . . . . . . . . . . . .

20
20
23
23
23
23
24
25
25
25
26

26
26
27
27
27
27
28
28

DECnet-RSX Release Notes
1.0

Release Description

These are the DECnet-RSX Release Notes for DECnet-llM/S V4.2,
DECnet-llM-PLUS V3.0,
and DECnet-Micro/RSX Vl.G.
This release
supports hierarchical
routing,
heterogeneous command terminals
using the CTERM protocol.
This release also supports host support
for
LAT-based
terminal
servers
for
DECnet-lIM-PLUS
and
DECnet-Micro/RSX only.
NOTE
This
kit must be generated and run only on
RSX-llM/S V4.2, RSX-IIM-PLUS V3.0, Micro/RSX V3.0
or VMS V4.0 systems with VAX-II RSX V2.0.
DECnet
and PSI kits distributed on magnetic tape or RLOls
contain identical NET kits.
Therefore, users who
have ordered both DECnet and PSI software will
receive two NET kits, either of which can be used.

1.1

New Features

The following items are the major new features in this release:
o

Hierarchical (area) routing.
This
feature
allows
the
network
to be divided into a number of areas with a
maximum of 63. A detailed explanation of area
routing
can
be
found in the DECnet-RSX Network Management
Concepts and Procedures manual.

Heterogeneous command terminal
(CTERM)
support.
This
feature
provides a virtual terminal connection to remote
Phase IV DECnet systems which provide similar support.
A
detailed explanation of CTERM support can be found in the
DECnet-RSX Guide to User utilities manual.

Nonrouting node support for Micro/RSX.
DECnet-Micro/RSX
Vl.O
is a new product which allows Micro/RSX systems to
participate in DECnet phase IV networks as end nodes.

Streamlined NETGEN procedures.
The
time
required
generate
the
DECnet software has been
reduced
prebuilding some of the DECnet tasks and processes.

LAT host support for
terminal servers.
This
feature
allows
terminals connected to LAT terminal servers to
establish a virtual
connection to an RSX-lIM-PLUS or
Micro/RSX host system.

)

to
by

DECnet-RSX Release Notes
o

TK50 distribution.

Executive vectoring.
DECnet
privileged
tasks
and
processes
take
advantage
of the RSXll-M-PLUS and
Micro/RSX executive vectoring feature.
This
allows
privileged tasks to be transported between like systems.
It also means that it is not necessary to rebuild the
network
if a new SYSGEN has been performed.
The device
drivers DU, DUV, and PCL have not been vectored.
If
these
devices are included in the network,
it
is
necessary to do a NETGEN when a new SYSGEN is formed.

Following are the major features in this release:
o

utility to interpret binary event logging file (EVF)

DCL support for NFT and EVF

NFT/FAL
support

Ability to modify down-line load
with NCP

DHU/DHV comm device support

PHONE is a supported utility

named

directory

and

2.0

Reporting and Isolating Problems

2.1

Reporting a User Problem

decimal

number

version

parameters

(SET/CLEAR)

(
\

A separate Software Problem Report (SPR) should be used for
each
problem.
This simplifies record keeping for quick responses.
User problems are often difficult to reenact.
In an SPR,
please
describe the system state when the problem occurred.
Keep the
description simple and accurate.
Illustrate a general problem
with several examples.
When an SPR contains concise information
about a problem, the problem is easier to
reenact and correct.
Please ensure that questions are direct and simple.

2.2

Investigating and Correcting Serious Errors

This section contains information that should be used
isolating problems and reporting problems to Digital.

for

both

(

DECnet-RSX Release Notes
To investigate and correct problems such as system
crashes, the following information is essential:

hangs

A description of the events leading to the problem

Console dialog or output, if appropriate

A machine-readable copy of:

Crash dump file

RSX symbol table file (RSXIlM.STB) M-PLUS only

CEX symbol table file (CEX.STB) llM/S only

CEX database file (CETAB.MAC)

Any user task involved (source copy)

The task build command files or parameters used
NETGEN for the appropriate network tasks involved

The task build map files created during NETGEN for the
appropriate network tasks involved

Suggestions for problem isolation

NOTE

If the problem is device
related,
type of local connection being
identified.
Al~

the modem
used must

or
be

media sent to Digital will be returned to the sender.

If the problem occurs when the network is running and the software
that does not use the network is involved, unload the network
software and try to reproduce the problem without the software.
If the problem occurs during periods of high interrupt loading,
try to
reproduce the problem without the load.
Examples of high
interrupt loading include many active high-speed communications
lines, many active terminals, and any process I/O.
If the problem involves file
transfer or file access,
please
include a DAP trace of the situation.
See the following sections
on NFT, NFARs and FAL for information on creating DAP traces.

)
3

DECnet-RSX Release Notes
2.3

Reporting a Documentation Problem

When describing a problem in a manual, specify the full
title of
the manual and identify the appropriate section, table, and/or
page number.
Describe what the manual says and suggest a
correction.

3.0

Documentation Errors

This section describes information that is documented
in the DECnet-RSX V4.2/3.0 manual set.

incorrectly

The SHOW LINE section of RSX-llS NCP command summary in the
DECnet-RSX Guide to Network Management utilities states that the
commands SHOW LINE line-id SUMMARY and SHOW LINE line-id STATUS
will work when locally initiated.
These commands will only work
when given from a remote node.
The command SHOW LINE line-id
COUNTERS is the only local command valid for lines on DECnet-llS
systems.

4.0

(

NETGEN Notes

On RSX-lIM-PLUS systems,
the slow task builder is no longer
required for NETGEN to build any network tasks.
NETGEN will not
function properly if you use the small indirect command processor.
When tasks are linked to one of the FCS
resident libraries,
the
three letter mnemonic corresponding to the
resident library
selected during NETGEN is appended to the task name.
For example,
if FCSRES is selected, the task name for CFE is CFERES.TSK.
If
FCSFSL is selected, the task name is CFEFSL.TSK.
The three letter
mnemonic is only appended to the tasks which are linked to the
resident libraries.

4.1

Prerequisites

This release of DECnet-RSX will run on an RSX-llM/S Version 4.2
system, an RSX-llM-PLUS Version 3.0 system, or a Micro/RSX Version
3.0 system.
It will not run with earlier versions of the RSX
systems.
The NETGEN is also intended to run with these versions
of the RSX-llM/M-PLUS and Micro/RSX software and will not generate
properly with earlier versions of the RSX operating system.
This
includes earlier versions of TKB and MAC.

(

\
4

DECnet-RSX Release Notes
Saved response files from DECnet-llM Version 4.0 can be used with
DECnet-RSX-llM Version 4.2.
Saved response
files from DECnet
RSX-llM-PLUS Version 2.0 can be used with DECnet-llM-PLUS Version
3.0.
When using saved responses from a previous release, certain
sections may be automatically repeated to obtain information not
provided by the previous release saved responses.

4.2

Micro/RSX

The TK50 distribution for DECnet-Micro/RSX consists of 1 tape.
The tape contains the same 3 kits that the 9 diskettes contain.
When you invoke OPTION.CMD with this tape, you can install either
DECnet, DECNETAPO or DECNETSSC.
The default for event logging for
DECnet-Micro/RSX is File Event Logging.

5.0

pregenerated M'PLUS Systems

5.1

System Selection

On the RSX-llM-PLUS pre-SYSGENned distribution kit, there are two
system images.
Before doing a full NETGEN you should use the
procedure provided with the RSX-IlM-PLUS distribution kit to
delete the system that you will not be using.
If you do not use
the procedure that was provided, there may be some libraries left
on your target disk that should not be there and NETGEN may give
you the option of using them (for example,
supervisor mode
FCS
library).

5.2

Processor Type in RSXMC.MAC

It is no longer necessary to modify the processor type
in
RSXMC.MAC.
NETGEN allows any device to be generated during NETGEN
which allows for portability of systems between UNIBUS and QBUS
systems.

5.3

Startup File Customization

The RSX-llM-PLUS pregenned system that supports only instruction
space
now comes with a
startup file
that deal locates the
Communications Executive (CEX) space in the executive, unless the
file LB:[l,2]SYSPARAM.DAT is modified.
You must change the line
5

DECnet-RSX Release Notes
in this file from DECNET=NO to DECNET=YES and
before you can load your network software.

reboot

the

system

The startup file then displays:

Step 2 - DeaLLocating DECnet communications executive
System configuration incLudes DECnet
If the second line is displayed as shown, the CEX
been deallocated.

5.4

space

has

not

Device Questions

NETGEN questions 3.01, 3.02, 4.03, and 4.04 ask about device CSR
and vector addresses.
Typically, each device has several device
registers and vector addresses associated with it.
'You must
specify the lowest device register and vector address when
answering the questions.
This is also true when specifying CSR
and vector addresses to NCP, CFE, or VNP.
NETGEN question 2.04 asks for the line speed for the device.
The
speed of a synchronous line is determined by the modem.
The line
speed specified in NETGEN is used to calculate timing criteria for
the line and buffer requirements.
If the line speed specified is
incorrect, the timing will be incorrect and the large data buffer
allocation may be incorrect.
If the line speed is set higher than
the actual line speed, there may be errors on large data blocks or
there may be allocation failures of large data buffers.
Errors on
large data blocks usually appear as data CRC errors.
If the
actual
line speed is higher than the specified line speed, there
is a long delay on timeouts.
Use CFE to reset the specified line
speed if the modem speed is changed.
NETGEN question 4.02 asks if the device is a DLll-E.
You should
answer this question NO if your DLII or DLVII is anyone of the
following:
DLll-A,
DLll-S,
DLll-C,
DLll-D,
DLll-WA,
DLll-WS,
DLVll-F
DLVll-J
The DECnet-RSX Network Generation Manual
lists the PCL as a
supported device
for
the pregened end node.
The PCL is not a
supported device
for
the pregened end node.
None of these
specified devices support the Clear to Send (CTS) signal.

I
\

DECnet-RSX Release Notes
NETGEN questions 4.05 and 4.06, in NETGEN Section 3,
ask about
modem signal monitoring and whether or not the modem switches
carrier with Request to Send (RTS).
Bell 202 modems
(or their
equivalents)
provide this.
If the device
is a DLII-E or a
DLVII-E, and the modem provides switch carrier with RTS,
you
should answer NO to question 4.05. Answering YES would require
the monitoring of Data Set Ready (DSR), and this signal
is not
available from the DL or DLV device.
If the modem does not switch
carrier (such as the Bell 103 or the Bell 113), you may answer YES
to question 4.05, since Carrier (CAR) will be monitored, and this
signal is available from the DL or DLV device.
If these questions are both answered YES for a DL or
NETGEN will reset the answers to NO automatically.

5.5

DLV

device,

Swapping NETGEN Input Disks

Question 1.00 in NETGEN Section 9 asks for the object disk device
for
the next CEX product to be built, such as DECnet or PSI.
If
you plan on using a disk drive which currently contains another
disk,
do not
replace the disk until you have typed the <RET> to
question 1.00. At this point, question 1.01 asks if the disk
is
ready.
You may now change disks, and, when the proper disk is
spinning and ready, type YES to question 1.01.
Following this procedure guarantees that NETGEN dismounts the
first disk before the second disk is accessed.
If the second disk
is spun up before NETGEN checks to see if the first disk should be
dismounted,
a disk directory problem could
result.
FCS may
indicate that some of the files NETGEN requires are on the disk,
while not finding others.
This causes NETGEN to attempt using the
disk without dismounting and remounting it, and causes the build
procedures to fail.

5.6

Post NETGEN Suggestions

For RSX-llM/M-PLUS
the MCR command
UIC, using the VMR
the network UIC to
may load the wrong

5.7

systems, before bringing your network up using
file NETINS.CMD, you may first set the network
or MCR command SET /NETUIC=[x,54j.
If you set
the wrong UIC, NETINS.CMD will use that UIC and
network.

Abnormal NETGEN Termination

If NETGEN terminates abnormally with an AT.
error message,
such
as
... AT.
-- File read error, or if it stops prematurely with an

DECnet-RSX Release Notes
indirect command
end-of-file (@<EOF>l on the command file,
the
file processor
(AT.)
most likely encountered a disk error.
Restarting NETGEN from the beginning and using a different disk
drive may alleviate the problem.

5.8

Generation on VMS Hosts

The VAXII-RSX V2.0
release on VMS V4.0 supports all of the
features
necessary to perform a DECnet-llM,
DECnet-llS,
or
DECnet-llM-PLUS network generation.
See
DECnet-RSX
Network
Generation and Installation Guide sections 3.3.6 and 4.2.2 for
more details.
When doing a PREGEN or a NETGEN on a VMS host, do not allocate the
disks before starting the procedure.
Use the RSX syntax when
specifying a disk.
Use the syntax DLO instead of DLAO.

6.0

Device notes

6.1

DEUNA/DEQNA

ignore
When running a UNA/QNA on a network with foreign devices,
and disable event type 5.15.
This is the result of the UNA/QNA
it
in.
receiving a message larger than the buffer it has to put
This is most often seen when sharing an Ethernet with a XEROX
system that sends a lot of broadcast messages.

6.2

(
\

DMP and DMV Multipoint Controllers

If you use a DMP or DMV device as a multipoint controller,
there
are parameters that you should ensure are set properly.
If these
parameters are not set properly, the performance of the
line may
be degraded.
For a complete description of these parameters,
consult the DMPII Synchronous Controller Manual
or
the DMVll
Synchronous Controller Technical Manual.
Set the DEAD TIMER parameter using the following NCP commands:

(
8

DECnet-RSX Release Notes

>NCP SET LINE DMP-cnt DEAD TIMER msc
>NCP SET LINE DMV-cnt DEAD TIMER msc
Where

cnt
msc

is the controller.
is the dead timer value in milliseconds.

This may be calculated as follows:
maximum delay in seconds before
a node is recognized
1000
maximum number of dead tributaries
NOTE
For best results the dead timer should be
high as possible.

set

Set the DELAY TIMER parameter using the following NCP commands:

>NCP SET LI NE DMP-cnt DELAY TIMER msc
>NCP SET LI NE DMV-cnt DELAY TIMER msc
Where

cnt

is the controller number.

msc

is the delay timer value in milliseconds. This
may be calculated as follows:

a
50
200

for coax.
for multipoint EIA lines.
if any software implementations

DDCMP
are on the multipoint line.
NOTE
If more than one value
larger value.

could

apply,

choose

the

You should also note that dead tributaries are always polled if
they are set ON.
If any tributaries are known to be in a dead
state, (either permanently or temporarily)
for
some significant
amount of time, it is suggested that they be turned off.
This may

DECnet-RSX Release Notes
significantly improve performance for
the tributaries
truly on.
To do this, use the following command:

that

are

>NCP SET CIRCUIT DMP-cnt.tri STATE OFF
Where
cnt

tri

6.3

is the controller number.
is the tributary number.

Powerfail Recovery

If a power failure occurs while a DMC-ll line is active,
the DMC
may corrupt memory before the network software is signaled of the
recovery.
This situation can cause the system to crash.

6.4

Error Counters

If a header CRC error occurs as a result of line interference, the
Header
Format Error and Buffer Too Small error counter flags may
be incremented instead of the Header CRC Error.
This is a
result
of the device drivers checking these conditions before calculating
the header CRC.

6.5

Device CSRs for Down-line Loaded Systems

It is important to have the "floating" device CSRs at the proper
addresses on the
system to be loaded.
The proper addresses are
determined according to the standard UNIBUS and Q-BUS
ranking of
the devices,
as when setting up the CSRs for a system which will
auto-configure to determine the devices on the system.
has been provided on the
A command file,
[200,200]FLOAT.CMD,
DECnet distribution kit to help you determine what these CSR
addresses should be.

7.0

System Notes

7.1

System Pool Usage

The installation and operation of
significantly
to
the system pool

DECnet
usage,

software can
depending on

add
user

DECnet-RSX Release Notes
requirements.
To help in minimizing the system pool usage,
a
general breakdown of pool requirements for various DECnet features
is given here.
Network parameters that use pool include:
o Number of control buffers
buffer

17. words/control

o Incoming network command
terminal links
driver

30. words/allowed link
for HT: and RT:
data structures

o Maximum logical
links al~owed

2. words/allowed link

o Number of
circuits defined

21. words/circuit

Loading and starting the network can use a wide range of values of
system pool,
depending on your specific system configuration.
During network load and start-up, control buffers and common areas
for DECnet processes are allocated.
When running network tasks, the first logical link adds 18. words
to pool usage and each additional logical link adds 11.
words.
This does not include the pool required for any QIOs issued on the
logical unit.

7.2

Network Resource Problems

When running your system, periodically check the
using the NCP SHOW SYSTEM COUNTERS command.

system

counters

In many cases of apparent network problems, the difficulty can be
traced to
insufficient network resources.
If there are receive
buffer allocation failures, increase the minimum number of receive
buffers with the CFE DEFINE SYSTEM MINIMUM RECEIVE BUFFERS
command.
Increasing the minimum number of receive
buffers
effectively decreases the number of large buffers that can be used
for transit messages.
Therefore, you may need to increase the
number of large buffers.
Use the CFE DEFINE SYSTEM MAXIMUM ~ARGE
BUFFER command to increase the number of large buffers.
If there are large buffer allocation failures,
11

increase the number

DECnet-RSX Release Notes
of large buffers with the CFE DEFINE SYSTEM MAXIMUM LARGE BUFFER
command.
Alternately, you can decrease the minimum number of
receive buffers with the CFE DEFINE SYSTEM MINIMUM RECEIVE BUFFER
command, since this will effectively increase the number of large
buffers that can be used for transit messages.
If you do this,
however, watch for receive buffer allocation failures.
For further information involving receive buffer and large buffer
allocation
failures,
see the DECnet-RSX Network Management
Concepts and Procedures manual.

7.3

Tuning

When tuning your system, you should periodically check the
counters using the command NCP SHO SYS COU.

system

If there are allocation failures for receive buffers, increase the
minimum number of
receive buffers using the CFE command DEF SYS
MIN REC BUF.
You may also wish to increase the number of large
buffers using the CFE command SET SYS MAX LARGE BUF, since
increasing the minimum number of receive buffers will effectively
decrease
the number of large buffers that can be used for transit
messages.
If there are allocation failures for large buffers,
increase the
number of large buffers using the CFE command DEF SYS MAX LARGE
BUF. Alternately, you may decrease the minimum number of
receive
buffers,
using the CFE command DEF SYS MIN REC BUF, since this
will effectively increase the number of large buffers that can be
used for
transit messages.
If you do this, however, you should
then watch for allocation failures on receive buffers.

7.4

Powerfail Recovery

If a power failure occurs during the operation of network
software,
logical
links may be aborted and switched lines are
disconnected.
Circuits are restarted upon recovery.

7.5

Running SHUTUP

The SHUTUP procedures used under RSX-llM
and
RSX-llM-PLUS
correctly dismount the network~during the dismount phase.
If you
wish to clear the network from memory during SHUTUP,
include the
following in LB:[l,2]SHUTUP.CMD:

.IFINS LCP LCP STOP
NCP SET EXECUTOR STATE OFF
.WAIT NETACP
NCP CLEAR SYSTEM
12

(M+ only)

DECnet-RSX Release Notes
OFF
completes
Because
the NCP command SET EXECUTOR STATE
asynchronously,
immediate issuance of a CLEAR SYSTEM command
causes the following error message to be displayed.

NTL -- Device NS:
To avoid this,

StiLL Active

.WAIT NETACP must be included.

8.0

utility Notes

8.1

NCP, CFE, and VNP

Networks which do not include hierarchical
routing will display
all node numbers with the area 1 designation.
Phase III nodes and
Phase IV to Phase III compatibility are not affected by this
change.
Named directories may not be used as the locations for the Logging
File Component,
which defaults to LB:[1,6]EVENTLOG.SYS.
Named
directories may not be used as the location for the output of the
KMX-DUMP command, which defaults to LB:[1,6]PSIKMXMEM.SYS.
Named
directories may not be used as the location for the output of the
PSI TRACE command, which defaults to LB:[1,6]PSITRACE.SYS.

8.2

CFE

If you have a very large CETAB.MAC you may get the error message:

CFE -- Insufficient Buffer Space
while CFE is attempting to read in the CETAB.MAC.
If this
happens,
run or install CFE with an increment large enough to fit
your CETAB.
See the RSX-IIM/M-PLUS MCR Operations manual
for
details of the RUN and INS commands.

8.3

NCP

NCP now allows you to change the down-line load parameters in the
volatile network database.
Parameters may be set or changed with
or the default parameters may be
the NCP SET NODE command,
overridden when the NCP LOAD NODE, LOAD VIA, TRIGGER NODE, or
TRIGGER VIA commands are given.
The parameter values may be
13

DECnet-RSX Release Notes
cleared with the NCP CLEAR NODE commands.
These parameters are
described in the DECnet·RSX Guide to Network Management utilities
and Network Management Concepts and Procedures manuals.
The up-line dump parameters may also be set and cleared with NCP.
When a satellite node requests an up-line dump, the host node will
look for these parameters in its remote node database if they are
not supplied in the request.
See the DECnet-RSX Guide to Network
Management utilities and
Network
Management
Concepts
and
Procedures manuals for details.
Support has been added to NCP to allow it to change the executor
parameters:
Incoming Timer, Outgoing Timer, Inactivity Timer, and
Retransmit Factor.
All NCP commands that are not system-specific to systems other
than RSX are now parsed.
When DECnet-RSX does not support a
command, NCP will
fail with the message <command> failed
invalid message format.
These commands are parsed so that the
local node may be used as a network control center.
For example,
TELL <VMS node> SHOW SIGNIFICANT NODES COUNTERS will be parsed and
passed to the named node.
If the
remote node supports the
command,
it will
be executed there, and any messages or display
will be shown on
the originating terminal or written to the
specified local file.
The Phase II node name delimiter" " (underscore) is no longer a
valid node name delimiter.
It may now be used in passwords and in
the RSX-specific form:
NODE/user/password::. Also, NCP no longer
converts characters within quoted strings to uppercase.
This
allows
better
communication
with
systems
that
require
case-sensitive passwords.
Three special alias names are now allowed by NCP.
These are
$HOST, $LqCAL, and an alias name consisting of from 1 to 6 blanks.
Any number of blanks in the valid range will map to the
same
alias.

8.4

VNP

The VNP command SET EXECUTOR STATE ON is illegal for RSX-IIM and
RSX-IIM-PLUS systems.
The reason for this restriction is that the
operating system startup command
procedure
must
establish
checkpoint allocation space on disk before the network state is
changed to ON.
The NCP SET EXECUTOR STATE ON command should be
added to the startup command file.
RSX-11M and RSX-11M-PLUS systems must be saved using the RSX
command before the network is loaded with VNP.

SAVE

DECnet-RSX Release Notes
Loading network software into a system image file with greater
than 124KW address space is supported for RSX-llS and RSX-llM-PLUS
systems only.

8.5

NFT

When reporting problems with NFT, a
DAP message trace of your
particular problem will help isolate the problem quickly.
Please
submit trace output with any NFT related SPR.
NFT must be rebuilt
to enable message tracing.
To add trace support, modify [137,24]DECPRM.CMD to change
to true and rebuild NFT using the NETGEN component mode.

$DNFTR

To activate tracing, assign the TR:
logical device
desired trace, using the ASN ddn:=TR:
command.

name

the

If the trace output device is a disk, the output will be placed in
the file NFARS.TRC under the current UIC.

8.6

FTS

Each FTS job is scheduled by sending one or more user
request
block
(URB) files to the system queue manager.
The queue manager
dequeues the job from the FTS queue and activates the FTS dequeue
task
(FTSDEQ)
to process the URB files describing the job.
The
job UIC, jobname and URB files associated with a given request may
be displayed by issuing SHOW QUEUE
(DCL)
or QUE /LI (MeR).
Several changes to the FTS/FTSDEQ/queue manager interface will be
apparent.
The naming convention for URB files has been changed to support
named directories of up to 9 characters.
Formerly, if an FTS job
was submitted by a user whose default directory was [g,m],
a URB
file describing that request would be created with the filespec
LB:[workuic]FTSgggmmm.URB, where workuic is set to [1,4] at FTSGEN
time and where gggmmm is the user's directory name, with comma and
leading zeros suppressed.
For instance,
a
job requested under
[5,11] would result in LB:[1,4]FTS51l.URB being sent to the queue
manager.
NOw, the URB file
is named LB:[workuic]directory.U~B,
where directory is the user's default directory string if named or
is the user's numeric directory,
with comma
(but not leading
zeroes)
suppressed if numeric.
The above job, for instance, will
now result in LB:[1,4]0050l1.URB being queued, while a
job
requested
under
[ANDERSON]
will
queue
the
URB
file
LB:[1,4]ANDERSON.URB.
Formerly, FTSDEQ always ran under

[1,1],
15

which

caused

problems

DECnet-RSX Release Notes
when a
job originally requested by a user under a different UIC
failed and was requeued by FTSDEQ.
When the' failed
job was
requeued by FTSDEQ,
the queue manager set the UIC of the job to
[1,1] and would report a privilege violation if the original user
attempted to use FTS to kill the job.
The job could be killed
only by issuing the FTS kill command under the UIC
[1,1],
which
was not available to a nonprivileged user.
FTS now dynamically
changes its current UIC to the UIC of the current user
job being
processed.
When FTSOEQ requeues a failed user job', the queue
manager assigns the job its original UIC,
allowing the user to
kill or otherwise access the job.

8.7

FAL

There are two versions of FAL:
one which supports
basic
sequential
FCS
file access and which can be subsetted for use on
RSX-llS nodes, and one which supports RMS-ll file access.
FAL allows network file access to occur only to or from public
devices.
If a device is to be accessed by a remote user, using
either NFT, FTS, or any task which is linked to the NFARS,
then
the device must be made public using the SET /PUB=ddu:
MCR
command before the disk is mounted.
Note that magtapes can be set
public but must be mounted for use by a single user.
Since FAL
cannot mount the tape, magtapes cannot be accessed by FAL.
FAL has the ability to provide logging of file
accesses.
To
enable logging,
you must provide the empty file LB:[l,4]FAL.LOG.
If this file exists, an entry will be appended to it for each file
access request.
The system manager should take care that the file
is emptied often enough so that it does not overload with
continued use.
When reporting problems with FAL or NFT, a OAP message
trace of
your particular problem will help isolate the problem quickly.
please submit trace output with any FAL related QAR.
FAL must be
rebuilt to enable message tracing.
To add trace support, modify [l37,24]DECPRM.CMO to change
to true and rebuild FAL using the NETGEN component mode.

$OFLTR

TO activate tracing, assign the FT:
logical device name
desired trace, using the ASN ddn:=FT:/TERM=CO:
command

the

If the trace output device is a disk, the output will be placed in
the file [l,4]FAL.TRC.
If the RMSRES version of FAL is improperly installed,
it will
The
abort
(T-BIT TRAP or BPT EXECUTION) during file transfer.
following is a list of the correct install commands:
16

\
\

DECnet-RSX Release Notes
INS
INS
INS
INS
INS
INS
INS

LB:[3,54]RMSRES.TSK/PAR=GEN/RON=YES
LB:[1,1]RMSLBL.TSK/PAR=GEN/RON=YES
LB:[1,1]RMSLBB.TSK/PAR=GEN/RON=YES
LB:[1,1]RMSLBC.TSK/PAR=GEN/RON=YES
LB:[1,1]RMSLBD.TSK/PAR=GEN/RON=YES
LB:[1,1]RMSLBE.TSK/PAR=GEN/RON=YES
LB:[1,1]RMSLBM.TSK/PAR=GEN/RON=YES

NOTE
RMSRES is installed from [3,54]. There is also a
file [l,l]RMSRES.TSK, which is not used by the RMS
based FAL.

9.0

MCM

The MCM utility submits command files for execution by invoking
either the indirect command file processor or, if the system
supports batch, the batch file processor.
Only one type of
submission will be supported by MCMi the type of submission is a
generation option.
If command files are to be submitted to the indirect command file
processor ( ... AT.), MCM will initiate the processing by executing
a command line at a specified terminal (the default is TTO:).
This default may be changed by reassigning LUN 1 of the MCM task
(installed with the task name .CMTS.), or by editing the file
[x,24]MCMBLD.CMD,
changing the appropriate ASG option, and then
rebuilding the MCM task using the following commands:
SET
ASN
ASN
ASN
ASN
TKB

IUIC=[x,24]
aau:=IN:
bbu:=OU:
ccu:=MP:
ddu:=LB:
@MCMBLD

Where
x:
aau:
bbu:
ccu:
ddu:

is
is
is
is
is

the
the
the
the
the

group code for the network UIC.
DECnet object disk.
output disk, where the network tasks reside.
map disk, where the network maps reside.
library disk, where the system files reside.

On systems which support multi-user protection, the specified
terminal must be logged on for MCR to accept the commands. Since
the system and file access privileges will be determined by the
17

DECnet-RSX Release Notes
account used
to login the
terminal,
should be used or any network user could
privileged context.

a non-privileged account
execute commands
in a

The tasks MCM and AT.
cannot be permitted to checkpoint each
other and should never be installed in the same partition unless
it is in a large system-controlled partition.
Due to MCM's
small
task size, consider installing it in the SYSPAR partition.

9.1

NFARs

This release includes no major changes to the NFARs.
You may wish to use the DAP trace module to debug user programs
that use
the NFARS.
To add trace support, explicitly include in
the task image the NFATRC module from the DAPTRC object library.
The reference
to NFATRC must come before any references to the
DAPFOR library in the task build command file.
To activate tracing, assign the TR:
logical device name
to the
desired trace device.
If the trace output device is a disk, the
output will be placed in the file NFARS.TRC under the current UIC.

(
\

9.2

NCT

The following items should be noted when using NCT.
There is a
problem with the VMS terminal server;
terminal
characteristics may be incorrectly reported.
An example is:
upon
exiting EDT the terminal characteristics will be set to
NOLOWER and NOSCOPE. A temporary workaround to this is
to type
SET /INQUIRE = TI:.
This will set the characteristics correctly
even though a DEV TI:
will still
report the characteristics
incorrectly.
This is a known problem, and a fix to the VMS server
is forthcoming.
VMS V4.0 treats escape differently than RSX.
Thus when
remoted
from VMS
to RSX, escape will not be recognized as a terminator.
This can be prevented by setting NOLINEEDIT on the VMS
system
BEFORE remoting to the RSX system.
When remoted from VMS to RSX, certain control characters may echo
differently than on RSX:
for example, <CTRL/Z> echoes as EXIT.
When remoted from RSX to VMS there may be some screen formatting
differences
as
compared
to a
local VMS terminal.
These
differences do not affect EDT or screen display programs, but may
affect read-with-prompt operations.

(

DECnet-RSX Release Notes
Some non-English LK201 keyboards do not have a backslash character
(\).
To generate the CTERM enter-control-mode sequence, on an
LK201 keyboard, press the CTRL key, and then the numeral 4 <RET>,
instead of pressing the CTRL key and a backslash (\) <RET>.
A task issuing output
control and vertical
CTERM link.

to a
forms

terminal using embedded carriage
control
(VFC) will not work over a

9.3

RMT

9.4

Use of RMT from Command Files

It is recommended that you do not invoke the RMT utility from an
indirect command file or
from a batch job.
The results are
unpredictable and depend much upon the system and upon the timing
involved.

9.5

Terminal Characteristics

When using RMT, the characteristics of your terminal depend on two
things:
o

The local node terminal driver features.

The local device characteristics that were set before the
RMT session using the MeR SET command.

Any optional features not supported at the
local node are not
supported during the RMT session.
However, the characteristics
ANSI, DEC, AVO, EDT, BLK, RGS, and SFC are user selectable on a
remote host,
even when unsupported on the local node.
These
characteristics are implicitly set, based on the local
terminal
type at the start of the RMT session, and by changing the terminal
type during the session.
DECnet-IIM-PLUS V2.0 and DECnet-llM/S
V4.0 nodes do not support these characteristics and will ignore
them if received.

9.6

Aborting RMT

On DECnet-llM-PLUS systems, the Remote Terminal task
(RMTACP)
is
made abortable through an Executive feature.
Since this feature
19

DECnet-RSX Release Notes
does not exist on RSX-IIM or RSX-IIS,
it is possible for a
privileged user to abort the task while it is in use.
If RMTACP
or any other privileged task is aborted,
the system
data
structures may be left corrupted.
If such an abort occurs, the users connected through RMT can enter
a "garbage" line.
The line causes RMTACP to be invoked again, and
resets their terminals to the original state.
If RMTACP is aborted, it should not be removed from the system
until
all
terminals are
reconnected to the local
system.
Prematurely removing RMTACP after an abort may lead to a
system
crash.

9.7

NETACP

NETACP has been modified to accept ASCII node address in the
connect block and node names.
The ASCII node address must be in
the form aannnn where aa is the area number and nnnn is
the node
address within the area.
The node address must be six characters
long.
Use leading zeros where required.
For example 030022 would
be the representation for node 3.22. All of the DECnet utilities
allow ASCII node addresses as well as node names except for SET
HOST.

9.8

NTDEMO

NTDEMO has been modified to include a
which use hierarchical routing.

10.0

new

display

for

networks

LAT Control Program (LCP)

The LAT Control Program (LCP)
controls the LAT process
DECnet-llM-PLUS or a DECnet-MicrojRSX service node.

10.1

LDB Size

The LAT process requires a minimum buffer size of 576 bytes to
start a
circuit.
If the buffer is too small, LCP rejects the
START command.

DECnet-RSX Release Notes
10.2

Permanent Database

The LAT permanent database is stored in the LAT process template
file
LAT.DAT in the network UIC.
This file should only be edited
with LCP.

11.0

LCP Error Messages

Following is a
complete
list of LCP error messages with an
explanation for
each error condition.
Corrective measures are
suggested where possible.
LCP -. Command not accepted, privilege violation
The user does not have sufficient privilege to perform
the requested command.
LCP - FATAL Camm Exec not loaded
The Comm Exec must be loaded before
can be started.

the

LAT

process

LCP - FATAL error allocating resources
There are not enough system resources to allocate
the
data structures necessary to add the LAT terminals to
the system.
LCP - FATAL error in system data structures
While linking the LAT terminal data structures into
the system data structures, LCP detected an error. A
detailed error message can be acquired by running HRC.
LCP '. FATAL error loading LAT process
NTL not installed
process.

NTL

could

not

load

the

LAT

LCP - FATAL error reading permanent database
This message indicates an error while accessing the
permanent database.
Check the LAT.DAT file in the
network UIC and ensure that the network UIC is set
properly.

DECnet-RSX Release Notes
NOTE
If this error results from using the CREATE
command,
you can use the /TERMINAL=n switch
because the permanent database does not need
to be accessed.
LCP - FATAL error starting LAT process
The LAT process returned an error when initializing.
LCP - FATAL error stopping process
The LAT process returned an error when stopping.
LCP - FATAL error updating permanent database· no update
The error occurred while creating a new file
for the
updated permanent database.
The original database is
unaffected.
LCP - FATAL HRC error
HRC detected an error in the system data structure
while CONing the LAT terminals ONLINE. A detailed
error message can be acquired by running HRC.

!
\

LCP - FATAL LAT process not in system
The LAT process is not in the network configuration.
LCP - FATAL LOB too small to start LAT
The LAT process requires a minimum buffer size of
to start a circuit.
LCP .. FATAL parameters missing from

perma.~fent

576

database

There is an error in the permanent database.
The
permanent database LAT.OAT in the network urc must be
restored to its original context.
LCP - FATAL syntax error in permanent database
The error occurred while parsing
the
permanent
database.
The permanent database,
LAT.DAT, in the
network UIC must be restored to its original context.
LCP - FATAL terminal driver does not support LAT
The terminal driver does not contain support for LAT.
22

DECnet-RSX Release Notes
LCP - LAT process already started
The LAT process has already been started.
LCP .. LAT process not active· issue START command
The LAT process is not active.
LCP - LAT terminals already created
The LAT terminals
system.

have

already

been

added

the

LAT

LCP - LAT terminals not in system· issue CREATE command
The LAT process cannot be
terminals have been created.

started

until

LCP - Line error, line in wrong state
The line specified in the /DEVICE switch or in the
permanent database is in the wrong state to execute
the command.
LCP - Line error, line not ready
The line specified in the /DEVICE switch
permanent database is not ready to START.

the

was

not

the

LCP - Line error, no such line
The line specified in the permanent database
found in the system.
LCP - Process not started
The LAT process has not been started.
LCP - Syntax error
An invalid command has been issued.
A detailed explanation of the LCP utility can be found
DECnet-RSX Guide to Network Management utilities manual.

11.1

PHONE

On DECnet-Micro/RSX systems, the initial size of Secondary Pool
provided by the operating system may not provide sufficient space
to allocate enough Accounting Blocks for users.
This will
result
23

DECnet-RSX Release Notes
in the Phone utility not being able to find the accounting
information for a logged-in user.
If this condition occurs, phone
will not allow the user to initiate a conversation with another
user since the accounting information is required.
If this problem is found, edit the LB:[1,2]SYSPARAM.DAT file
to
increase the size of Secondary Pool.
Refer to Chapter 6 of the
DECnet-RSX Micro/RSX System Manager's Guide
for more detailed
information.

12.0

Cross-system File Transfer Notes

12.1

RSX-IIM/M-PLUS File Transfer Capabilities

Support of the DAP Rename operation is currently limited
RSX-llM/M-PLUS NFT and RMS-ll based FAL utilities.

the

Support of the DAP Change Protection operation is currently
and to the
limited
to
the
RSX-llM/M-PLUS
NFT
utility,
RSX-IIM/M-PLUS and VMS RMS based FAL utilities.
Neither the RMS-ll based nor the FCS-ll based RSX-llM/M-PLUS FAL
will support the
FOP delete-on-close option bit in combination
with the ~pool-on-close option.
The file will be spooled but not
deleted.

12.2

VAX/VMS V4.0 File Transfer Capabilities

VAX/VMS supports a
transparent remote file access interface
integrated with the RMS file system.
For more information see the
VAX/VMS VAX-II RMS manuals and the VAX/VMS Cross
System Notes.
The VMS FAL supports most of the capabilities of VAX-II RMS.
Many text files on VMS systems use the Print File Carriage Control
Attribute
(RAT=PRN).
In particular VMS Batch log files and files
created by VMS DCL default to Print File Carriage Control.
This
is now a
supported record format for the RSX-llM/M-PLUS RMS-ll
based FAL, but not for most RSX text editors and utilities.
Users
must be careful when transferring files from a VMS system to an
RSX system.
If the file is to be used on the RSX system it must
be converted by the RMS CONVER~utility.
RSX-IIM/M-PLUS and VAX/VMS have differing meanings for the E
protection category.
On RSX, E means extend file access.
On VMS
it means execute (run) file access. When transferring files to a
VMS system, the extend protection setting will be lost and execute
access will be allowed. When transferring from a VMS system,
the
execute protection setting will be lost and extend access will be
allowed.
24

DECnet-RSX Release Notes

Space for VAX/VMS files
is always allocated according to
the
disk's cluster size. When transferring files from a VMS system to
an RSX system using the VMS COPY command,
the extra blocks
allocated due
to cluster round-up will not be truncated.
When
this happens, you may truncate the file on the RSX node using PIP
file/TR command.
In particular RSX task image files transferred
from a VMS system must be truncated, because the INSTALL command
on the RSX system will not install a file whose high block is not
the same as the End-of-File block.
The VAX-II RMS file system supports a superset of the RMS-II V2.0
capabilities.
Some of the capabilities are suppressed or modified
by the VAX-II RMS network access code when working against an RSX
system and some are not.
See the VAX/VMS Cross System Notes for
more detail.
In particular,
the
following capabilities
or
attributes are not supported by the RSX RMS-II based FAL:

12.3

Stream-CR or Stream-LF Record Format (RFM) types.

The Contiguous-Best-Try Allocation option (fop or
CTB).
VMS suppresses this option.

Numerous fop options including Truncate-On-Close.

Prologue Version 3 indexed sequential files.
You must
use CONVERT to change the file to prologue Version I or
2.

$RELEASE and record locking:
bucket level locking.

RMS-II V2.0

only

aop

supports

RSTS DECnet/E V2.0 File Transfer Capabilities

RSTS now supports an RMS-I1 based FAL and NFT.
For information on
the RSTS DAP utilities, consult the RSTS DECnet/E Guide to User
utilities and the RSTS DECnet/E Release Notes.
Most text files on RSTS systems are in Stream ASCII record format.
This is now a
supported record format for the RSX-IIM/M-PLUS
RMS-II based FAL, but not for most RSX text editors and utilities.
Users must be careful when transferring files from a RSTS system
to an RSX system.
RSTS NFT will translate stream ASCII files into
variable length record format if the IVA switch is specified.
RSX
NFT will translate variable length record files into stream ASCII
if the /AS switch is specified.

DECnet-RSX Release Notes
RSTS NFT cannot copy sequential files in block mode from an RSX
RMS-ll based FAL
that have an FFB value of other than 0 or 512.
RSTS RMS-Il currently restricts block 1/0 writes to units of
512
bytes.
Such sequential files must be transferred in record mode.
The RSTS FAL only supports block mode transfer of indexed files.

12~4

RT-11 V2.0 File Transfer Capabilities

The RT-Il FAL supports only sequential files and a basic set of
file operations.
For more information see the RT-ll DECnet Guide
to User Utilities and the RT-ll DECnet Release Notes.
Most text files on RT-ll
systems are
in stream ASCII
record
format.
This
is
now a supported record format
for
the
RSX-IIM/M-PLUS RMS-ll based FAL, but not for most RSX text editors
and utilities.
Users must be careful when transferring files from
an RT-Il system to an RSX system.
RT-li NFT will tr.anslate stream
ASCII files
into variable length record format if the lAS switch
is specified.
RSX NFT will translate variable length record files
into stream ASCII if the lAS switch is specified.
The RT-ll FAL does not support the following:

12.5

Relative and indexed file organizations.

Variable and VFC record formats.

FORTRAN and implied LF-CR record attributes.

IAS V3.0 File Transfer Capabilities

The IAS FAL is FCS-li based and supports only basic FCS
file
transfer services.
It is essentially the same as the RSX-IIM
DECnet V3.1 FAL.

12.6

TOPS-20 File Transfer Capabilities

The TOPS-20 FAL supports only sequential files and a basic set of
file operations.
For more
information see the TOPS-20 DECnet
Guide to User utilities and the TOPS-20 DECnet Release Notes.
Most text files on TOPS-20 systems are
in Stream ASCII
record
format.
This
is
now a
supported
record format for
the
RSX-IlM/M-PLUS RMS-li based FAL, but not for most RSX text editors
26

DECnet-RSX Release Notes
and utilities.
Users must be careful when transferring files from
a TOPS-20 system to an RSX system.
TOPS-20 NFT will
translate
stream ASCII
files into variable length record format if the /AS
switch is specified.
RSX NFT will
translate variable length
record files into stream ASCII if the /AS switch is specified.
TOPS-20 does not support the following:

13.0

Relative and indexed file organizations.

Fixed, variable and VFC record formats.

FORTRAN and implied LF-CR record attributes.

Random record and block I/O access modes.

Unsupported Software

The UFD [200,200] on the distribution media contains unsupported
software provided by Digital as a courtesy to customers.
These
utilities are not supported by Digital.
All unsupported software can be generated by
[200,200]UNSGEN.CMD on the distribution disk.

13.1

invoking

the

file

CEDUMP - Communication Executive Database Dump Program

CEDUMP is a utility for dumping the internal data structures in
formatted text.
This utility is not supported by Digital, but is
provided for use by Digital Software Specialists and as a courtesy
to our customers.

13.2

CEDUMP Switches

The functions of CEDUMP are controlled by a number
The switches are divided into four categories:
o

General

Comm/Exec

DECnet

PSI

switches.

DECnet-RSX Release Notes
The operations of these
sections.

13.3

switches

are

listed

the

General Switches

For ease of use, two switches are provided which are
use for all Comm/Exec based communications products.

13.4

following

general

/HE - List the CEDUMP Switch Descriptors

The switches which are listed by the /HE switch are the valid
switches at the time the /HE switch is invoked.
For instance, if
DECnet is available but not currently active
(Executor state
ON), the DECnet specific switches will not be listed.

13.5

/AL' Dump All Available Data Structures

Note that the data structures that will be dumped by the /AL
switch depends upon the support built into the program at
generatio~ time and also the state of the network software at
the
time the switch is invoked.
For instance, if the Comm/Exec is not
loaded (via SET SYSTEM), no data structures will be dumped.

13.6

Comm/Exec Specific Switches

The basic network data structures are those which are present for
all products layered upon the Comm/Exec and are dumped by the
following switches.
o

/CM - Dump the Comm/Exec common database

/FR - Dump the free resource list status

/LT - Dump
databases

/NL - Dump the network loader information

/PD - Dump the process descriptors

/PO - Dump the pool statistics

/RV - Dump the reverse mapping table

the

DLC/DDM

process

line

tables

and

LLC

DECnet-RSX Release Notes
o

13.7

ISL - Dump the system line table

DECnet Specific Switches

DECnet specific data structures are
switches:

14.0

dumped

using

the

IDH

- Dump the DECnet home block

IGE

- Dump the DECnet general delivery queue

110

- Dump the NETACP 1/0 queue

ILl

- Dump the active line count

ILL

- Dump the logical links

ILN

- Dump the physical link blocks

1MB

- Dump the DECnet mailbox queue

following

RVT

RVT cannot be run under a terminal connected via RMT.
There are
some features which used to work when connected to VMS systems
using RVT which no longer work with VMS V4.0.

DECnet-RSX
Release Notes
AA-JS17D-TC

READER'S COMMENTS
What do you think of this manual? Your comments and suggestions will help us to improve
the quality and usefulness of our publications.

Please rate this manual:
Accuracy
Readability
Examples
Organization
Co m pleteness

Poor
1
1

Excellent

2
2
2
2
2

3
3
3
3
3

4
4
4
4
4

5
5
5
5
5

Did you find errors in this manual? If so, please specify the error(s) and page number(s).

General comments:

Suggestions for improvement:

Name _____________________________________ Date _____________________
Title
Company

Department
Street ______________________

City _____________________ State/Country _______ Zi P Code _______

DO NOT CUT

FOLD HERE AND TAPE

111111

NO POSTAGE
NECESSARY
IF MAILED
IN THE
UNITED STATES

BUSINESS REPLY LABEL
FIRST CLASS PERMIT NO. 33 MAYNARD MASS.
POSTAGE WILL BE PAID BY ADDRESSEE

SOFTWARE DOCUMENTATION
1925 ANDOVER STREET TWO/E07
TEWKSBURY, MASSACHUSETTS 01876

DO NOT CUT

FOLD HERE