Digital PDFs

AA-H504C-TC

January 1987

142 pages

Original

39MB

view download

OCR Version

15MB

view download

Document:	DECnet/E Utilities Guide
Order Number:	AA-H504C-TC
Revision:	0
Pages:	142
Original Filename:

OCR Text

DECnet/E
Utilities Guide
Order No. AA-H504C-TC

January 1987

The DECnet/E utilities allow a terminal user to: talk to a user locally
or at another node, log in at and use another DECnet/E node, manipulate files between nodes, copy the contents of storage devices between
DECnet/E nodes, and shut down the network.

OPERATING SYSTEM AND VERSION:

RSTS/E

V9.3

SOFTWARE VERSION:

DECnet/E

V4.0

digital equipment corporation, maynard, massachusetts

The information in this document is subject to change without notice
and should not be construed as a commitment by Digital Equipment
Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document.

The software described in this document is furnished under a license
and may be used or copied only in accordance with the terms of such
license.

No responsibility is assumed for the use or reliability of software on

equipment that is not supplied by DIGITAL or its affiliated
companies.

The postage-paid READER’S COMMENTS form on the last page of

this document requests your critical evaluation to assist us in preparing future documentation.

The following are trademarks of Digital Equipment Corporation:

Bnanan TM

DECUS
DECwriter

Rainbow
ReGIS

DATATRIEVE
DEC

DIBOL
FMS-11

RSTS
RSX

DECmail
DECmate
DECnet
DECsystem-10
DECSYSTEM-20
DECtape

LA
MASSBUS
PDP
P/OS
Professional
Q-Bus

RT
UNIBUS
VAX
VMS
VT
Work Processor

CONTENTS
PREFACE

SUMMARY OF TECHNICAL CHANGES

CHAPTER

Introduction

CHAPTER

TLK: Terminal Communication Utility
.

Output
. . . .

.
.
.
.

.
.
«
.

.
.
.«
.

.
.
.
.

Interaction

Input

Initiator’s
Receiver’s
Dialog Mode
Initiator’s

Receiver’s
TLK

2-2
2=2
2-4
2-5
2-5
2-7
2-10

.
.
.
.
.
.

3-2
3-4
3-6
3-7
3-8
3-9
3-10

NET: Network Command Terminal Utility
.
=

.
«

.
+

.
+«

CONTINUE Command
CTRL/P Command .
DETACH Command .
EXIT Command . .
HELP Command . .
NORMAL Command .
. .
ODT Command

.
.
.
«
.
.
.

.
.
.
«
.
.
«

.
.
.
«
.+
.
«

.
.
.
«
+
.+
«

.
.
.
«
=«
«
o

.
.
.
=
.
=
o

Messages

NET

Messages

Running NET
NET Commands

CHAPTER

Input

.
.
.
.
.
.

Error

.
.

3-11

3-12
3-13

NFT: Network File Transfer Utility
The Relationships Between NFT,
FAL Access to ISAM Files . .
.

FAL,

Running

NFT

Node

Names

.
«
.
.
.
.
.
.

.
o
.
.
.
.
.
.

.
«
.
.
.
.
.
.

.
o=
.
.
.
.
.
.

General Format of NFT Commands
File

Specifications

Wildcards

Quoted Strings . . .
NFT Commands . . . « «
AP[PEND] Command . .
cCo[PY] Command . . .
DE[LETE] Command . .
DI[RECTORY] Command
EXI[T] Command . . .
HE[LP] Command . . .

1ii

o«

CHAPTER

Error

One-Line Mode

G
s

NOD[ESPECIFICATION]
PR[INT]

SU[BMIT]

TY[PE]

Command

Switches

4-34

4-36

Switch

/BL[OCK]

Switch

/BR[IEF]

Switch

/DE[LETE]

/FU[LL]
/IM[AGE]
/LI[ST]

4-36

4-37

Switch

4-38

Switch

4-38

4-39

4-39
4-40

Switch

.
.

4-40

Switch

4-41

/)NOA[TTRIBUTES]

Switch

4-42

/NOCO[NTIGUQUS]

Switch

/)NOSU[PERSEDE]

Switch

/POS

Switch

/RWO

Switch

/TO[TAL]

/VA[RIABLE)])
NFT

Error

Switch

Switch
Messages

"NETCPY:

Network

Running

NETCPY

General

Format

NETCPY

Switches

/BL[OCK]:n

Copy

Switch

4-44

Command
s

e
.

. .

Switch

.
.

NETOFF:

4-44

Error

NETCPY

/VE[RIFY]

4-43

/PA[RITY]:n

4-43

Switch

/FC

/NC

Switch

4-43

Devices

/DE[NSITY]:n

/HE[LP]

Between

NETCPY
c

4-42
4-43

/RWC

/SU[PERSEDE]

Switch

Messages

Network

Shutdown

4-42
4-42

Utility

oronoTOnOTOTOUYOY
O N

|
O\
OOUOT U b NN

Switch

/NOHE[ADING]

Switch

/NODE[LETE]

CHAPTER

Switch

/NA[TIVE]

Switch

/)MO[RE]

Coe
.

/CTG

Switch

/IN[QUIRY]
/LO[G]

Switch

/ID[ENTIFY]

4-31

4-33

Switch

/CO[NTIGUOUS]

CHAPTER

4-29

Command

/AP[PEND]

/ASCII

4-25

4-27

Command

VE[RSION]

NFT

Command

==, APPENDIX A

NSP Reason Codes for Connect Reject and Link Abort
Error Messages Generated by RMS and DAP

APPENDIX B

NFT Error Messages from RMS-11

NFT Error Messages from DAP
.
Macro (aa) Field Values
"Micro (nnnn) Field Values

.
.
.

.
«
.

B-1l1
B-1l1
B-13

.
.
.

INDEX

FIGURES

. . . . .
DECnet/E Features for the Terminal User
. . . .
.
Sample Network Composed of Seven Nodes.
The TLK Utility: TLK and LSN Provide Communication
e e e e .
. . . . . « . . .
Between Terminals
NET Provides Access to Another DECnet/E Node . . .

1-1
1-2
2-1

3-1

NFT Transfers Files to,

4-1

4-2

4-3

4-4
4-5
4-6
4-7
4-8
4-9
4-10
5-1

from,

and between Remote

1-2
1-4
2=2
3-2

+ + ¢« o o o o « o o o o o o o« o« o o o« + o« . 4-2
NOAES
At DECnet/E Nodes, NFT, FAL, and RMS Work Together
to Allow File Operations . . . . . . . . . . . . . 4-4
Sample Network Showing Transfers Between Nodes
. . . « « v o « « « « +« « « « . 4-8
with DECnet/E NFT
4-15
. . . . . . .
Example of the NFT APPEND Command
4-18
. . . . . . . .
Example of the NFT COPY Command
4-20
.
.
.
.
.
.
.
Command
DELETE
NFT
the
of
Example
4-22
.
.
.
.
.
.
Command
DIRECTORY
Example of the NFT
4-28
.
.
.
.
.
.
.
.
Example of the NFT PRINT Command
4-30
.
.
. . . . .
Example of the NFT SUBMIT Command
4-32
.
.
. . . .
Example of the NFT TYPE Command
NETCPY Copies an Entire Device from One DECnet/E
. . . . . . . . « . 5-1
Node to Another DECnet/E Node

TABLES

2-1
3-1
3-2
4-1
4-2
4-3
5-1
5-2
A-1
B-1
B-2
B-3
B-4
B-5

TLK Error Messages . . « « « + « o+
NET CommandsS . « « « « o« « « o o« o
NET Error MessSages . . . « « « s+ «
NFT CommandsS . « « « o « « « o o« o«
NFT Switches . . « + & v v ¢ « « «
NFT Error MessagesS . . . . « « « «
. . . . ¢« « ¢« « «
NETCPY Switches
. . « « « «
NETCPY Error MeSSageS
NSP Reason Codes . . . + « « « « o
e e e 4 e
. . .
RMS Error Codes
.t e e e e
Macro (aa) Field Values
. . . .
Micro (nnnn) Field values
Micro (nnnn) Format
. . . . « « «
Micro (nnnn) Values for Macro (aa)

o o« o
o« « o
« « o«
o o o«
o« « «
o« « «
¢« o +
« o o+
o « o
e e e
e 4 e
. . .
+« « «
Value

« « «
« « o«
o« « «
o« + «
« « «
« « «
o« « «
o o« o
« « o«
e e« «
e e «
. . .
« « «
Octal

2-10
o
o« « 3-5
3-13
4-13
4-34
.
4-45
.
« . 0-4
« « 29
« « A-1
+« . B=2
B-12
«
B-13
.
« 'B-20
12 B-28

Preface

Objectives

This guide describes the DECnet/E utilities that allow you to:
o

Talk to a user locally or at another node

Manipulate files between nodes

Copy the contents of entire disks and tapes between devices

Shut down your network in an orderly fashion

at different DECnet/E nodes

Audience

This guide is for any RSTS/E terminal user who wants to use the
DECnet/E utilities to perform any of the DECnet/E functions previously
listed.

You should understand the operation of the local RSTS/E

Document

Structure

system and the

remote system you want to access.

This guide has six chapters and two appendixes:

Chapter 1

Introduces the DECnet/E utilities and summarizes their
use.

Chapter 2

Describes the TLK Terminal Communication utility.

Chapter 3

Describes the NET Network Command Terminal utility.

Chapter 4

Describes the NFT Network File Transfer utility.

Chapter 5

Describes the NETCPY Network Copy Device utility.

Chapter 6

Describes the NETOFF Network Shutdown utility.

Appendix A

Lists the NSP Reason Codes.

Appendix B

Lists the error messages that RMS and DAP generate.

vii

Related
This

Documents

guide

references

The

following

DECnet/E Network

DECnet/E

start

System

system

documents:

Installation

Manager’s

Guide

system,

control

DECnet/E

The

the

system,

and

give

and

tell

other

Update
how

and

RSTS/E

Quick Reference
Command Procedures

The

RSTS/E

use

monitor

information

The

RSTS/E

System

RSTS/E

User’s

for

the

Utilities

Guide

tell

Guide

general

and

how

the

Introduction

concepts

The

and

the

and

running

useful

and

describes

Reference

DECnet

capabilities

Manual

Phase
of

RSTS/E

use

DCL

the

Guide

commands.

functions

and

user.

tells

utilities.

Phase

Guide

generate

manager.

Writing

The

gives

DECnet

how

use

overview

networks

RSTS/E

implemented

1IV.

DECnet

DIGITAL

Description

Network

describes

Architecture

(DNA)
implementations.

the

that

Architecture

design

serves

(Phase

DIGITAL

model

IV)

the
by

General

Network

for

Phase

DECnet

Conventions

This

guide

<RET>

<LF>

CTRL/x

uses

the

following

conventions:

Represents

the

RETURN

the

RETURN

key

Represents

the

LINE

Indicates
CTRL/P.

CTRL
The
a

key

down

you

the

combinations

echo

key

press
an

You

commands.

your

terminal.

such

combination,

the

character

use

CTRL/Z
hold

the

key.

uppercase

character

indicates

example,
"2

indicates

the

character

and

key

CTRL/Z.

your

viii

terminal.

and

combination,

For

CTRL

your

lines

key

preceding

expressed

control

character.

combination
also

key

while

circumflex

contrel

FEED

control
enter

key

complete

and

the

All

terminal

control

key

screen

" x.

can

[]

Square brackets in a command format mean the bracketed

parts are optional.

For example:

CEX[IT]

The characters IT in the EXIT command are optional.

Braces around two or more items in a command format mean
that you must select one of the bracketed items.

For

example:

:
{/FC}
dstdevice:=srcdevice
{/NC}

You must include either /FC or /NC in the command.

UPPERCASE

Uppercase letters indicate keywords you must enter as
shown.

Unless shown otherwise, spaces or tabs must separate items in a
command string.

The system treats a tab or more than one space

between items as a

single space.

Most examples in this guide do not show the RETURN key symbol, <RET>.
If you try examples at your terminal, always press the RETURN key at
the end of a command line unless the example indicates otherwise.

summary of Technical Changes

The following changes apply to the DECnet/E V4.0 utilities:
o

You cannot use alias node names.

You can use long passwords of up to 14 alphanumeric

The account from which NFT and FAL run must have total job

characters.

and detached job quotas of one or more.

DECnet/E no longer supports the NETACT remote database.

NFT and FAL support the Print/Batch Services (PBS) package
for remote PRINT and SUBMIT commands:

The NFT PRINT command sends a print job to the NETSPRINT

gueue if PBS is running.

The NFT SUBMIT command submits a file having a .COM type
to the PBS batch server and the NETSBATCH queue if PBS 1is
running.

FAL can perform record-level access to ISAM (RMS-indexed)
files.

The NETCPY /DENSITY switch accepts densities of 800, 1600,

You must have the SHUTUP privilege to use the NETOFF utility.

6250,

6667,

and 8000 bpi.

Chapter

Introduction

This chapter introduces some basic network concepts.

DECnet is the collective name for the software and hardware products
that allow various DIGITAL operating systems to participate in a
DECnet/E is the implementation of DECnet that allows a
network.
RSTS/E operating system to function as a network node.
A DECnet/E node can communicate with other DECnet/E nodes in the
network or with any other DIGITAL operating system that supports
DECnet.

Using DECnet/E utilities,

you can:

Communicate with someone at a terminal on another DECnet/E
Each person can type messages that display at the
system.
other’'s terminal

(see Chapter 2).

Do work on another DECnet/E system as if your terminal were
connected directly to the other system (see Chapter 3).

Copy files to or from other DECnet/E systems, submit command
files to other DECnet/E systems, and delete files at other
DECnet/E systems

(see Chapter 4).

Copy the contents of an entire storage device to or from

Shut down your DECnet/E software in an orderly fashion (see

another DECnet/E system (see Chapter 5).
Chapter

6).

Figure 1-1 shows the DECnet/E utility functions.

Introduction

BANGOR

LOG INTO AND

MANIPULATE

NETWORK FILES

$NFT DENVER::FILE
= MYFILE

$NFT DENVER::HELLO
TRNTO

KANSAS

DENVER

TALK TO

BOSTON

DALLAS

REMOTE USERS

TLK>MURRAY-MOUNT A TAPE

NYC

Figure

l-1:

DECnet/E

Features

MK-02316-00

for

the

Terminal

User

The term DECnet network refers to two or more computer systems running
some

and

version

sharing

DECnet

system

need

not

that

DECnet/E

all

running

nodes

DECnet-VAX

DECnet-RSX

DECnet-RT

DECnet-IAS

DECnet-10

DECnet-20

PRO/DECnet

software,

resources.

can

connected

The

DECnet/E

computer

software.

communicate

with

communications

systems,
Some

are:

called

other

links,

nodes,

DECnet

systems

Introduction

Although all DECnet systems use the same network concept defined by
the DIGITAL Network Architecture (DNA), all do not support the same
set of network functions (see the DECnet DIGITAL Network Architecture
(Phase IV) General Description). You can use the DECnet/E utilities
described in this guide with other DECnet systems as long as those
systems support compatible functions. The communications links,
called physical

links,

Cable

Microwave

Satellite

can be:

DIGITAL has developed DECnet products over several years and has
introduced new network features periodically through the process of
phases. DECnet/E v4.0 is a Phase 1V DECnet product, which (with some
restrictions) can communicate with earlier DECnet/E Phase III products
(see the DECnet/E System Manager’s Guide). Note that DECnet/E V4.0
cannot communicate with DECnet/E Phase II products.

In the sample network shown in Figure 1-2, a user at node BOSTON can
refer to BOSTON as the local node and to nodes DENVER, DALLAS, NYC,

BANGOR, LONDON, and KANSAS as remote nodes. At node BOSTON, the nodes
DENVER, DALLAS, and LONDON are physically adjacent nodes. That 1is,
there is a direct physical link to these nodes with no intervening
nodes. To a user at node KANSAS, BOSTON is the only adjacent node.

Introduction

AREA 1

AREA 2
«

BANGOR

LONDON

(2.15)

TRNTO

(1.5)

| DMC-1
|

KANSAS
1.13

DENVER |

(1.13)

(1.14)

(2.14)

}

PACKET

SWITCHING

DATA
NETWORK

|
N\

o @

\ L
I

"BOSTON
(2.11)

VMS
ROBIN

(2.20)

THRUSH
(2.21)
LARK
|

DALLAS

DMC-2

(1.9)

|
i

LOON
(2.24)

NYC

Physical line

(2.17)

e e e e s (G PG UL

Figure

1-2:

DOVE

(2.23)

MK-02300-00

Sample

Network

Composed

Seven

Nodes.

*‘%%

Chapter

TLK:

Terminal Communication Utility

The TLK (Talk) utility lets you send messages to another person at a
terminal, including the Operator Services Console (0SC), on any

DECnet/E node in the network.
o

One-line mode--Allows transmission of a one-line message to
another

Two communication modes are available:

terminal.

Dialog mode--Allows two-way communication between two

terminals.

any

The person at either terminal can stop the dialog

time.

In the RSTS/E environment, the talk utility actually consists of two
The sample conversation 1in
TLK (talk) and LSN (listen).
programs:
dialog mode in Figure 2-1 shows the general relationship of TLK and
At the receilver
As the initiator, you run TLK at your terminal.
LSN.
l, completes the communications circuit.
terminaLSN

TLK:

Terminal

Communication

Utility

BANGOR

TRNTO

$ RUN DECNETS$:TLK
DALLAS::KB41:

> HELLO DALLAS

KANSAS

> DID YOU GET THE TAPES YET?
>

DENVER

BOSTON

YES, GOT THEM YESTERDAY
> GREAT, BYE FOR NOW

—,

<TLK> End of Dialog

DALLAS
<TLK> in Dialog with DENVER::KB2:
>

HELLO DALLAS
-

DID YOU GET THE TAPES YET?
> YES, GOT THEM YESTERDAY

NYC

GREAT, BYE FOR NOW
<TLK> End of Dialog
MK-02317-00

Figure

2-1:

The

TLK

Utility:

Between

One-Line

Using

the

TLK

input

utility

receiver’s

send

LSN

Provide

another
to

one-line

terminal.
initiate

mode,

The
a

you

can

transmit

one

following

sections

describe

the

displayed

message

and

V4.0

the

output

terminal.

Input

one-line

message

another

terminal,

SRUN DECNETS:TLK
TLK

Communication

required

Initiator’s

and

Mode

information
user

TLK

Terminals

RSTS

V9.3

Timesharing

*[target-node::][target-terminal:]

'message

type:

line

TLK: Terminal Communication Utility

target-node::

is the one- to six-character alphanumeric node
name to which the message is to be sent. If the
target node is your local node, you can omit the
node name. If you specify a node name, you must
include the two colons (::). You can determine
the names of nodes currently active on the
network by using the NCP command, SHOW ACTIVE

See the DECnet/E System Manager’s Guide

NODES.

for a discussion of the SHOW commands.

target-terminal:

is the device designation of the terminal to
which the message is to be sent (for example,
TTS: or KB4l:). If you omit target-terminal,

TLK sends the message by default to the currently

assigned OSC at the specified node or to your
Under the RSTS/E system, the system
local node.

manager can assign the OSC to different physical
devices at different times.

I1f the node you specify is your local node, TLK

checks to make sure the target terminal is a

terminal known to the system. The usual RSTS/E
designation for terminals is KBn: or TTn:, where

n is the physical terminal number. However, you
can also use logical target terminal names for
your local node, after assigning them using the
ASSIGN command. See the RSTS/E System User’s
Guide for a discussion of logical device names.

If the node you specify is a remote node, TLK
uses only the decimal terminal number from the
target terminal specification and forwards that
number to the TLK (or LSN) program at the remote
node.

The remote node’s TLK (or LSN)

program

returns an error message if the device number 1is

invalid
message

for that node.

is any ASCII string that is the message you want

to send. You must begin the message with a single
|
guotation mark (’). The entire line, including
cannot
,
message
the
the target specifications and
be longer than 132 characters. TLK deletes any
leading and trailing spaces and tabs.

If your system manager has defined a Concise Command Language (CCL)

command for TLK (TLK for example), you can type the CCL command, the
target specifications, and the message all on one line:
TLK {targetmnode::][targetmterminal:]

'message

TLK:

Terminal

The

following

MAYNRD::

Communication

Utility

example

shows

terminal

KB5:

command:

one-line
remote

message

node

sent

SANFRN::

from

local

using

the

node
RUN

SRUN DECNETS$:TLK
TLK

V4.0

RSTS

V9.3

*SANFRN::KB5:

The

following

local

node

STLK

example

using

the

calls

(617)

shows

a one-line
command TLK:

CCL

123-4567.

message

Sheldon.

sent

the

message

this

0SC

the

’'MOUNT TAPE MM(015 ON MM1:

Receiver’s
The

Timesharing

’'Relay

Output

receiver’s

<TLK>

terminal

source-node::

displays

one-line

source-terminal:

format:

message

where:
source-node::

the

name

originated.
when
source-terminal:

the

which
message

The

TLK

target

program

terminal.

message

but

example

shows

does

the

target

device

the

node

the

target

not

stop

the

displayed

terminal

message

Services
OPSER

MAYNRD::

KB4:

arrives

(OPSER)

'Relay

for

program

sends

the

terminal

message

'MOUNT

calls

local

running,

24-Sep-86

KB4:
TAPE

the

program.

node’s
TLK

busy,

MM1:

name

node

source

node.

terminal

from

OSC

12:45 PM JOB:13

RSTS/E

The

following

KB4:

(617)123-4567.

while

displays

the

displays

terminal

the

LSN[1,2]
|

MMO1l5

the

LSN

SMESSAGE 23402
<TLK>

message

sent

the

format:

message

sent.

executing

the

display

originated.

MAYNRD:
:

<TLK>

where

not

designation

message

source

node

does

message

1If

the

TLK

the

node

Sheldon.

Operator

message

the

TLK: Terminal Communication Utility

I1f OPSER is not installed on the local node, or if for some reason it
is not running, TLK displays the message on the OSC in the TLK format:
S<TLK> KB4:

’'MOUNT TAPE MMOl1l5 ON MMl:

Dialog Mode

when you use TLK in the dialog mode, you can exchange messages with a
user

at another

Initiator’s

terminal.

Input

To initiate a dialog with a person at another RSTS/E terminal, type:
SRUN DECNETS:TLK
TLK V4.0 RSTS V9.3 Timesharing

*x[target-node::][target-terminal:]
>message

where:

target-node::

is the one- to six-character alphanumeric node

name to which the message is to be sent. If the
target node is your local node, you can omit the

node name.

If you specify a node name, you must

include the two colons (::). You can determine
the names of nodes currently active on the

network by using the NCP command,

NODES.

SHOW ACTIVE

See the DECnet/E System Manager’s Guide

for a discussion of the SHOW commands.

target-terminal:

is the device designation of the terminal to

which the message is to be sent (for example,
TTS5: or KB4l:). If you omit target-terminal, the
default target is OSC. (TLK automatically sends
the message to the OSC at the specified node or
to your local node.) Under the RSTS/E system, the
system manager can assign the OSC to different
physical devices at different times.

If the node you specify is your local node, TLK
checks to make sure the target terminal is a
terminal known to the system. The usual RSTS/E
designation for terminals is KBn: or TTn:, where
n is the physical

terminal number. However,

you

can also use logical target terminal names for
your local node, after assigning them using the

ASSIGN command.

2-5

See the RSTS/E System User’s

TLK:

Terminal

Communication

Guide
If

for

TLK

the

right

you

the

node.

The

the

type.

Either

dialog

for

the

target

the

remote

specification

TLK

(or

LSN)

and

program

the

TLK

(or

LSN)

the

device

invalid

for

that

you

entire

(>)

continues

(the

line

cannot

has

for

from

the

defined

one

before

number

longer

for

typing

new

the receiver

or
>

example),

specifications

prompt

prompting

initiator)

CTRL/Z

program
is

node.

characters.

messages

that

remote

string that is the message you want

The

bracket

the

forwards

node’s

TLK

from

message

send.

names.

node,

number

error

the

Concise

line

first

lines

with

»>.

with

the

lines

end

receiver

the

than

can

terminate

prompt.

you

prompt:

STLK

terminal

remote

angle

(TLK

device

manager

TLK

logical

returns

pressing

system

specify

decimal

returned

the

command

only

number

message.

alternates

your

node

is any ASCII

you

discussion

terminal

132

line

target

Wait

for

the

uses

message

Utility

can

and

Command

type

then

Language

the

CCL

type

your

(CCL)

command

message

and

[target-node::][target-terminal:
]

>message

The

following

terminal

the

and

example
how

the

shows

how

the

conversation

dialog

looks

proceeds.

The

dialog:

the

initiator’s

receiver

terminates

SRUN DECNETS:TLK
TLK

V4.0

RSTS

V9.3

Timesharing

*MAYNRD: : KB4 :

>Sheldon--a

call

came

long-distance;

couldn’t

transferred.

Oh.

Who was

it?

>Yes--Gladys

Did

they

Freen.

>(415)987-6543

leave

back

Call

after

10:00

OK--thanks
<{TLK>

End

again.
of

Dialog

Sheldon.

(1:00

number

call

|
pm

your

time).

back?

TLK: Terminal Communication Utility

Receiver’s Interaction

If the target terminal is not busy (no one is logged in), the LSN
program displays the first line of a dialog-mode message as follows:
<TLK> in Dialog with source-node::source-terminal:
>

message-1
>

where:

source-node

source-terminal
message-1

is the name of the node from which the dialog

originated.

is the terminal designator that originated the

dialog.

is the first message line of the dialog.

The receiver then continues the dialog by pressing RETURN at the >

prompt.

For example:

<TLK> in dialog with NOD5::KB12:

If the target terminal is busy (someone is logged in at the terminal),

the LSN program displays a message in the following format:
' ¢TLK> in Dialog with source-node::source-terminal:

Type ’'TLK/n source-node:: source-terminal:’ to continue dialog

where:

source-node

source-terminal

is the name of the node from which the dialog

originated.

is the terminal designator that originated the

dialog.

is the job number of the receiver’s LSN program.

Include at least one space between the job number

and the source node.

the receiver must
The text enclosed in single guotation marks is what
to two minutes for the
type to continue the dialog. LSN then waits up
the dialog. The receiver can stop any active
receiver to continue

2-17

TLK:

Terminal

work

dialog

the

command

The

terminal

and

to another
continue the

TLK/6

Communication

Utility

type

the

terminal,
dialog.

indicated

command

type

continue

the

indicated

the

NOD5::KBl2:

receiver

DECNETS:TLK
(asterisk)

can

also

command

choose

and

then

continue

typing

the

DECNETS :TLK

TLK

V4.0

*/6

NOD5::KB12:

RSTS

After

the

first

message

either

user

V9.3

receiver

and

<TLK>

End

dialog

using

the

command

RUN
at

the

displays

the

Timesharing

types

the

presses

connection

the

continuation

prompt:

RUN

the

dialog

CTRL/Z

displays

the

continuation

command,

continues

the

prompt.

following

LSN

usual
LSN

manner

until

then

breaks

running,

the

message:

Dialog

$
If

the

target

display

for

terminal

0OSC

busy

is the local
terminal is made

SMESSAGE

nnnnn:date

<TLK>

Dialog

Type

‘TLK/n

Operation

The

following

*I/And
Type

so,

user

the

shows

source-terminal:’to

same

how

the

logged

and

for

busy

with

dialog
is

*exit
exits

from

the

and

starts

SANFRN: :KB5:

editor

TLK)

continue

looks

using

SANFRN: :KB5:

SANFRN::KB5:’

(user

the

format:

Dialog

terminal.

after/

Dialog

’'TLK/13

STLK/13

OPSER

JOB:nn jobname[ppn)]
source-node:: source-terminal:

proceeds

example

The

and

the

time

with

source-node::

then

terminal.

<TLK>

dialog

at
text

the

receiver’s

editor:

TLK:

Terminal Communication Utility

Sheldon--a call came long-distance; couldn’t be transferred.
>Oh. Who was it, did they leave a number to call back?
.

Yes--Gladys Freen.
>

Call back at

(415)987-6543 after 10:00

>OK--thanks again.
>CTRL/2Z

<TLK>
$

End of

Dialog

(1:00 pm your time).

Sheldon.

TLK:

TLK

Terminal

Error

2-1

Table

2-1:

‘

lists

COMMAND

The

Utility

Messages

Table

Communication

the

TLK

Error

SYNTAX

job

TLK

error

messages.

Messages

ERROR-ILLEGAL

number

JOB

NUMBER

you

typed

continue

dialog

the

display

RSTS/E

job

number.

Check

retype

the

line

continue

COMMAND

SYNTAX

You

tried

line

for

prints

to
-

ILLEGAL

MESSAGE

type

message

continuing
>

prompt,

dialog.
you

can

TLK

the

same

Retype
then

line

the

TLK

SYNTAX

does

~line.
COMMAND

ERROR

not

Retype
SYNTAX

The

terminal

the

command

COMMAND

You

type

the

l1s

not

and

You

retype

COMMAND

ERROR

job

ERROR

job

correct

connection
in
See

further

MEET

job

display

MESSAGE

TOO

LONG

that

using

TLK

TEXT

logical

messages,

request.
to

its

DECnet/E

description

but

with
it

text

attempt

Network

the

SPEC

command

Retype

but

the

TLK

printed

job

REQUIREMENTS

dialog
the

and

same

TLK

132

one

the

job

that

printed

and

characters.

lines.

link

The

that

accepts

shorter

dialog

DIALOG

not

dialog.

response
the

the

want

RECEIVER

continue

the

initial

NOT

TLK

dialog.

the

ERROR

set

the

When

you

name.

display

Check

exchange

received

DOES

the

COMMAND

line.

incorrect.

MESSAGE

continue

Message.

number

length

message

continue

JOB

the

SPECIFICATION

continue

Check

dialog.
to

specified

node

(spec)

NOT

number

valid
and

NODENAME

you

TERMINAL

shown

but

ERROR

INITIATE

receiver,

line

the

valid

program

for

with

JOB

line

SYNTAX

tried

name

receiver.

maximum

CONNECT

NAME

node

ILLEGAL

valid

line

the

NODE

the

specification

the

Retype

TLK

ERROR

message

initiated

The

line

the

SYNTAX

typed
a

the

message

retype

COMMAND
is

ILLEGAL

printed

message

line.

SYNTAX

typed

recognize

not

command

sent.

COMMAND

dialog.

ERROR

the

that

the

remote

TLK

LSN

error

the

error

text

TLK

received

is
to

the
send

Programmer’s

error

text.

Connect

Initiate

Reference

Manual

TLK: Terminal Communication Utility

Table 2-1:

TLK Error Messages

—— — ————
- ———————

Message and Meaning
—————
[

CONNECTION REJECTED BY NSP -

(Cont.)

,
——— -+

CODE:N

TLK tried to set up a logical link with the remote TLK or LSN
program to exchange messages but the connection was rejected by
the remote NSP. The code n is the reason code that the remote

NSP returned. See Appendix A for a list of the NSP reason code

meanings.

CONNECTION REJECTED BY REMOTE TLK - CODE:N

§
by
rejected
program to exchange messages but the connection was
the remote TLK or LSN program. The remote TLK then returned the |
é
code n. Contact a DIGITAL Software Support representative if
;
|
this error occurs often.
TLK tried to set up a logical link with the remote TLK or LSN

%
é

CONNECTION REJECTED BY REMOTE TLK - ILLEGAL VALUE IN TLK MODE BYTE
TLK tried to set up a logical link with the remote TLK or LSN
program to exchange messages but the connection was rejected by
the remote TLK or LSN program. Contact a DIGITAL Software
Support representative if this error occurs often.

CONNECTION REJECTED BY REMOTE TLK - TERMINAL IS BUSY

You initiated a dialog and the remote terminal is busy, but no
one has responded to continue the dialog. The remote user has
two minutes to respond and continue the dialog; 1in this

|
’

instance,

no one

responded.

CONNECTION REJECTED BY REMOTE TLK - TERMINAL IS NONEXISTENT
The remote terminal you requested does not exist at the remocte
node. Check for possible error in the command line.
.

|
;

|
|

CONNECTION REJECTED BY REMOTE TLK - TEXT

The remote TLK or LSN program did not accept the logical link
connection that allows the one-line or dialog exchange. The
text is the error message that the remote TLK or LSN program

received in trying to issue its connect confirmation. Contact a
DIGITAL Software Support representative if this error occurs
often.

CONNECTION REJECTED BY REMOTE TLK - UNKNOWN FORMAT

The remote TLK program did not recognize the parameters passed
in the request to set up a logical link that allows the
one-line or dialog exchange. This occurs when the remote TLK
program is part of an earlier DECnet implementation such as
DECnet Phase II. Contact a DIGITAL Software Support
representative.

TLK:

Terminal

Table

2-1:

Communication

TLK

Error

Messages

DECLARE RECEIVER ERROR -

The

exchange

message

local

TLK

Utility

TEXT

program

facilities

received

could

not

the

local

(Cont.)

its

Declare

begin

node.

set

The

Receiver

message

text

system

the

error

function

call.

DIALOG
You

dialog

ALREADY
or

number

has

allows

JOB

You

the

error

continued

dialog

code

this

error

NOT

name.

the

LINK

DIALOG

Contact

Link

NSP

Abort

the

NOT

minutes

message

dialog

the

for

was

The

f
a

and

dialog

and

link

that

from

The

remote

TLK

Software

program

Support

often.

TRANSFER ERROR

this

node

transferring

Contact
error

SPECIFIED
you

DIGITAL

occurs

|
a

message

Software

often.

TARGET

typed

the

wrong

that

TLK

displayed

message

terminal

and

number

retype

the

CODE:N

allowing

code

Message
NSP

number

the

DIGITAL

occurs

remote

WITH

KBN:

requesting

logical

exchange.

terminal.

dialog,

link

aborted.

COULD

Two

Check

logical

list

remote

the

line.

ABORTED

been
@

continuing

The

the

representative

command
LINK

account

FROM

CODE:N

disconnected

the

line

who

TLK

You

[PPN],

the

determine

program

occurred

from

Support

node

typed

the

one-line

returned

ACCOUNT

use

DISCONNECTED BY REMOTE TLK -

already

time.

can

REMOTE

TLK

representative

JOB

functions.

terminal.

remote

then

else

continuation.

DISCONNECTED

The

CONTINUED

someone

terminal

which

network

installation

—————w.

any

system

execute

cannot

installed

INSTALLED
not

the

code

ESTABLISHED

elapsed

after

continuing

terminated.

one-line

the

reason

terminating

reason

NOT
was

———

DECnet

DECNET

dialog

code

the

link.

exchange

returned
See

has

NSP

Appendix

printed

its

meanings.

TIMEOUT

the

remote

dialog

and

TLK
no

program
one

responded.

The

in
for

TLK:

- Table

2-1:

LINK

|
fi
;
|
i
i

TLK

COULD

Error

NOT

Messages

ESTABLISHED

Terminal

Communication Utility

(Cont.)

TEXT

The local TLK program received an error in the Connect Confirm
message from the remote TLK or LSN program. The logical link
that allows the one-line or dialog exchange was not set up. The
text is the NSP error message that the local TLK program
received in response to its Receive system function call.
Contact a DIGITAL Software Support representative.

MESSAGE

TOO

|
.
|
|
f

LONG

a line in dialog mode that was longer than 132
You typed

characters.

NSP

g
|

Retype

the message using

shorter

lines.

ENABLED

NOT

NSP, the part of DECnet that allows the logical link
connections providing the one-line or dialog exchange,
enabled

the

local

node.

See your

was not

system manager.

.
|
|

RECEIVE ERROR - TEXT
The local TLK or LSN program received an error while processing
a message from the remote node. The text is the error message

SEND

:
|

received in response to the Receive system function call.
Contact a DIGITAL Software Support representative.
DATA

ERROR

received

response

function call.

}

Software

TEXT

The local TLK or LSN program received an error while sending a
message to the remote node. The text is the error message

for

further

to the

Send Network Data message

system

See the DECnet/E Programmer’s Reference Manual

details

Support

the

error

representative.

text,

and
|

contact

DIGITAL

E
|
|

|
i

e iy

Chapter

NET:

Network Command Terminal Utility

The NET utility lets you access another DECnet/E system in the network

/TM and do work there as if your terminal were directly connected to that
system.

NET and NPKDVR (Network Pseudo
NET is implemented as two programs:
Figure 3-1 shows a user running NET at node DENVER.
Keyboard Driver).
NET requests that a logical link be set up with NPKDVR at the remote
NPKDVR is a job that opens a pseudo keyboard at node
node BOSTON.
After NET
the logical link connection request.
accepts
and
BOSTON
type at node
you
n
informatio
the
relays
NET
link,
sets up the logical
the pseudo
to
it
relays
which
NPKDVR,
to
DENVER over the logical link
pseudo
a
treats
BOSTON
node
The RSTS/E system at remote
keyboard.
keyboard as a normal keyboard.

(“W%

when the remote node RSTS/E monitor receives information from the
pseudo keyboard (whatever you type at node DENVER), the monitor
The remote node
creates a job and runs LOGIN to process the input.
and any
LOGIN,
monitor,
the
by
generated
system directs responses
keyboard.
pseudo
the
to
node
remote
the
other programs you run at
NPKDVR,

turn,

passes

responses

directed

the

PSQUdO

over the logical link to the NET program at node DENVER.

displays the responses on your terminal.

keyboard

NET then

back

NET passes your input directly through to NPKDVR at the remote node,
NET makes no attempt to
except for CTRL/P and its related commands.
Thus, if you type a
through.
passes
it
data
the
interpret any of
system executes the
remote
the
system-level command, for example,
command and the command has no effect on your system.

To reduce overhead, system managers can install more than one
Each permanently installed copy
permanent copy of NPKDVR at a node.
can handle multiple logical links. When all permanently installed
copies are busy, an incoming connection request makes the system start

a temporary copy.

See the discussion of the SET/DEFINE OBJECT command

in the DECnet/E System Manager’s Guide for more information about

installing programs

for automatic

start-up.

NET:

Network

Command

Terminal

Utility

BANGOR

TRNTO

$ RUN DECNETS:NET

Node Name:
BOSTON
Connection Established to RSTS/E node BOSTON
RSTS v9.3
.
133-JUN-86
4 PM
03:47
DENVER

KANSAS
BOSTON

System Password:

Password:
$

DALLAS

NYC

MK-02318-00

Figure

3-1:

Running

NET

You

run

can

NET

Provides

from

RUN

DECNETS:NET

SET

HOST

NET

[node-name]

where

[node-name]

any

Access

terminal

Another

DECnet/E

Node

system

typing:

[node-name]

the

name

the

remote

node

you

want

access.

—

NET: Network Command Terminal Utility

If you do not include the node name on the command line, NET will
prompt you for it. NET displays a connection message, the remote node
For example:
system banner, and prompts for login information.
SRUN DECNETS:NET

NET V4.0
Node

RSTS V9.3 DECnet

System

BOSTON

name?

Connection established to RSTS/E Node BOSTON

RSTS V9.3 Timesharing Job 31 KB33 24-Sep-86 8:00AM

User: 2,250
Password:

If you include the node name on the command line, NET displays 1its
banner, a connection message, the remote system banner, and prompts
for the login information.

$ SET HOST BOSTON
NET V4.0 RSTS V9.3 DECnet

For example:
System

Connection established to RSTS/E Node BOSTON

RSTS V9.3 Timesharing Job 31 KB33 24-Sep-86 8:00AM

User:

2,250

Password:

If the remote node requires a system password, you can optionally
include only the node name on the command line. You must include a
In this case, NET
space or tab between the command and the node name.
displays its banner, a connection message, the remote system banner,
and prompts for the login information.
S RUN DECNETS:NET BOSTON
NET V4.0 RSTS V9.3 DECnet

System

For example:
f

Connection established to RSTS/E Node BOSTON

RSTS V9.3 Timesharing Job 31 KB33 24-Sep-86 8:00AM
System password:
User: 2,250
Password:

If the remote node requires a system password and you do not include
the node name on the command line, NET displays its banner and prompts
for

the node name.

$ RUN DECNETS:NET

NET V4.0
Node

RSTS V9.3

Name?

BOSTON

For example:

DECnet

System

NET:

NET

Network

then

prompts

Command

displays
for

the

Connection

RSTS

V9.3

System

User:

Terminal

Utility

connection

log-in

message,

information.

established

Timesharing

RSTS/E

Job

password:

the

For

Node

KB33

remote

system

example:

banner,

and

BOSTON

24-Sep-86

8:00AM

2,250

Password:

$
If

your

for

system

example),

NET

manager

you

can

has

run

defined

NET

CCL

command

for

DECNETS:NET

typing:

(NET

[node-name]

then

your

proceeds

node

remote

RSTS/E

described

running

DECnet/E

Quick

the

node

Reference

DCL

the

Run-Time

using

Guide

and

the

paragraphs.

System,

you

DCL

command

RSTS/E

System

can

SET

also

HOST

User’s

connect

(see

the

Guide).

NET Commands
After

last

running

remote

NET,

node

remote

node.

remote

node

and

you

that

node.

remote

Your

node

your

you

local

you

can

ODT

Before

you

your

can

use

local

any

node

command

mode.

You

CTRL/P,

then

RETURN.

for

you

type

system

may

want

send

node

and

the

last

one

you

may

want

use

the

You

use

the

NET

and

the

NET

indicate

communicate

NET

the

NET

that

this

displays

command.

system

For

its

you

want

your

the

that
for

that

available

commands
in

prompt

commands
the

directly

chain

single-character

commands

commands,

connected

directly

perform

must

local

first

enter
node

nodename: :NET>

these

communicate

the

NET

pressing

prompt

and

waits

example:

RUN DECNETS:NET

NET

v4.0

Node

RSTS

name?
V9.3

System
User:

V9.3

DECnet

System

BOSTON

Connection

RSTS

established

Timesharing

password:

(Not

Job

RSTS/E

KB33

Node

BOSTON

24-Sep-86

8:00AM

echoed)

2,250

Password:

displays

you

functions.

with

logically

commands

the

your

mode.

any

sends

However,

between

and

terminal

type

connections,

transmission

terminal

specified

(Not

" P<KRET>

DENVER: :NET>

echoed)

NET:

Network Command Terminal Utility

=, In this example, you run NET from your local node DENVER and log in to
You then enter the NET command mode by pressing
remote node BOSTON.
'
CTRL/P,
now

then RETURN.

Table 3-1 lists all seven NET commands you can

type.

Table

3-1:

NET Commands

CO[NTINUE]}

Return to terminal mode.

~
!

CT[RL/P]

-~
.

Send a "P to the next remote node 1in a
chain of remote nodes.

DE[ TACH]

- Abort link (detaching remote job) and exit.

. EX[IT]

é Kill remote job, disconnect the link, and
|

exit.

HE[LP]
or ?

.
|

Display the help text.

NO[RMAL]

Exit ODT mode.

OD[T)

o ——————— o

Enter ODT mode.
e

——————————

|
|
|

——— = — +

NET: Network Command Terminal Utility
CONTINUE

CONTINUE

Command

Use

the

its

nodename::NET>

local
at.

CONTINUE

terminal
After

command

over

typing

However,

the

commands

RUN

DECNETS:NET
V4.0

RSTS

name?
V9.3

System

User:

the

cursor

not

display

For

example:

DECnet

NET

program

stop

the

data

you

remote

node

you were

sending

drops

its

down

prompt.

to
You

the
can

displaying
type

next
type

your

last
line.
system

System

BOSTON

Connection

RSTS

does

V9.3

the

resume

connection

point.

NET

Node

the

cause

and

CONTINUE,

system

this

prompt

established

Timesharing

RSTS/E

Job

KB33

Node

BOSTON

24-Sep-86

10:00AM

password:

3,247

Password:

S " P<KRET>
DENVER: :NET>HELP

(Help

display

for

NET

commands)

DENVER: :NET>CONTINUE
<RET>

DIRECTORY

(Directory
at

$
In

listing

node

for

user

BOSTON)

(system prompt at node
this

prompt.

example,
You

then

you
ask

use
the

BOSTON)

the

CONTINUE

Boston

node

command
for

stop

directory

the

DENVER::NET>

display.

Network Command Terminal Utility

NET:

CTRL/P

Command

Use the CTRL/P command to pass a CTRL/P character to an intermediate
This command is useful when
remote node in a chain of remote nodes.
you have set up a chain of three or more remote nodes and you want to
operate in the NET command mode at one of the intermediate

remote

nodes.

To use this command you must type the characters CTRL/P, then press
NET then displays
RETURN while you are at the nodename::NET> prompt.
the nodename::NET prompt of the next remote node in the chain.

Note

This command is spelled C T R L / P .
To enter this
command, you must type the characters "CTRL/P" rather
than pressing the CTRL key and then pressing P.

By repeatedly using the CTRL/P command you can logically connect your
local terminal to any intermediate remote node in the chain.
For
example:

S RUN DECNETS:NET

NET V4.0 RSTS V9.3
Node Name? BOSTON

DECnet

System

Connection established to RSTS/E Node BOSTON

RSTS V9.3 Timesharing Job 31

KB33

24-Sep-86 8:00AM

System password:
User: 2,250
Password:

S RUN DECNETS:NET

NET v4.0
Node

RSTS

Name?

V9.3

DECnet

TULSA

Connection established
RSTS V9.3

System

to RSTS/E Node TULSA

Timesharing Job

KB33

24-Sep-86

9:01AM

System password:
User: 3,120
Password:

S " P<KRET>
/P
DENVER::NET>CTRL
BOSTON: :NET>

In this example, you run NET at your local node DENVER to set up a
connection with BOSTON.
At node BOSTON, you run NET to set up a

While logically connected to node TULSA, you
connection with TULSA.
You
press CTRL/P and RETURN to enter the NET command mode at DENVER.
then type out CTRL/P to enter the NET command mode at node BOSTON.
Now you can use any of the NET commands at BOSTON.

3-7

NET:

Network

Command

Terminal

Utilit

DETACH

Command

Use

the

link

DETACH

program.

command

For

your

continue

attach

For

example:

detach

node

and

the

remote

you

can

use

the

example,

procedure

and

command

between

work.

remote

Later

the

job

you

the

job

can

and then
set up the

detached

DECnet

System

remote

DETACH

node

that

node,

when

and

command

return
remote

you

node,
exit

used

disconnect

the

NET

run

large

to your local node
connection again

the

DETACH

command.

RUN DECNETS:NET

NET

V4.0

Node

RSTS

Name?

BOSTON

Connection

RSTS

V9.3

System

User:

V9.3

established

Timesharing

RSTS/E

Job

Node

KB33

BOSTON

24-Sep-86

8:00AM

password:

2,250

Password:

$ " P<KRET>
$ @BIGJOB.COM
$ " P<KRET>
DENVER: :NET>DETACH

Remote

job

Control

detached...

returned

node

DENVER

(continue

work

node

DENVER)

RUN

NET

DECNETS:NET

V4.0

Node

RSTS

Name?

Connection
RSTS

V9.3

System

User:

V9.3

DECnet

System

BOSTON
established
Timesharing

RSTS/E

Job

Node

KB33

BOSTON

24-Sep-86

8:00AM

password:

2,250

Password:

Jobs

detached

Job

18
Job

What

DCL

number

Attaching

S
In

(do work
this

DETACH
you

under

this

Size

State

attach
job

reconnect

RTS

3.8

to?

DCL

BOSTON)

you

submit

to
to

Run-time

node

example,
command

account:

disconnect
BOSTON

and

BIGJOB
and

attach

the

back
to

3-8

BOSTON
to

the

BIGJOB's

node,

then

DENVER

node.

job

number

use

the

Later,

again.

NET: Network Command Terminal Utility

EXIT

EXIT Command

Use the EXIT command to break the connection with the remote node.
There are two ways to terminate the NET program:

Simply log out at the remote node.

Use the EXIT command.

In the second case, NPKDVR at the remote node automatically terminates
the job to which you are connected. NET then displays the following
Control

message:

returned to node nodename

The following example shows how to log out and use the EXIT command to
terminate

NET program:

the

$ RUN DECNETS:NET

Node

Name?

BOSTON

Connection established to RSTS/E Node BOSTON

RSTS V9.3 Timesharing Job 31 KB33 24-Sep-86 8:00AM
System password:

User: 2,613
Password:

S RUN DECNETS:NET

Node

Name?

TULSA

Connection established to RSTS/E Node TULSA

RSTS V9.3 Timesharing Job 22 KB17 24-Sep-86 9:01AM
System password:

User: 2,210
Password:
S

(do work

node

TULSA)

BYE

Control returned to node BOSTON
$ " P<RET>
DENVER: :NET>EXIT

Control

returned to node DENVER

In this example, you net over from Denver to the Boston node and then
to the Tulsa node. Later, you log off the Tulsa node, then use the
EXIT command to stop the NET program and leave the Boston node for the
Denver node.

3-9

NET:

Network

Command

Terminal

command

Utility

HELP

Use

Command

the

HELP

display

question

help

the

mark

NET
(?)

information,

the

commands
obtain

NET

nodename::NET>

your

the

returns

help

example:

prompt

terminal.
display.

its

You

get

can

After

nodename: :NET>

the

also

NET

help

type

displays

prompt.

the

For
|

RUN DECNET:SNET

NET

v4.0

Node

RSTS

name?

Connection
RSTS

V9.3

System
User:

V9.3

DECnet

System

BOSTON
established
Timesharing

to
Job

RSTS/E
25

Node

KB27

BOSTON

24-Sep-86

10:23AM

password:

1,221

Password:

$ " P<RET>
DENVER: :NET>HELP

NETWORK

commands

CO[NTINUE]

Return

DE[ATCH]

Abort

link

EX[IT]

Kill

remote

job,

HE[LP]

help

text.

OD[T]

Enter

CT[RL/P]

Send

NO[RMAL)

Exit

ODT

to terminal

ODT

mode.

(detaching

remote

disconnect

job)

and

exit.

link,

and

exit.

“

mode.

""P"

other

end.

mode.

DENVER: :NET>

this

CTRL/P

example,
to

produces

return

the

help

you
to

net
the

over
NET

display

from

Denver

program

and

use

back

and

goes

the
the

the

Boston
HELP

node,

command.

nodename::NET>

use
NET

prompt.

—~

NET:

Network Command Terminal Utility
NORMAL

NORMAL

Command

Use the NORMAL command immediately after exiting from a program that
needs single-character input, such as ODT (Octal Debugging Tool).
For
example:
S

RUN

DECNET:SNET

NET V4.0
Node

RSTS V9.3

name?

DECnet

System

BOSTON

Connection established to RSTS/E Node BOSTON
RSTS V9.3
System
User:

Timesharing

Job

KB27

24-Sep-86

10:23AM

password:
1,221

Password:

$ " P<RET>
DENVER: :NET>ODT
-

(do

ODT work

node

BOSTON)

$ " P<KRET>
DENVER: :NET>NORMAL

" P<RET>

)

DENVER: :NET>EXIT

Control

returned

node

DENVER

In this example, you net over from the Denver node to the Boston node
and use ODT there.
You then use CTRL/P to return to the NET program,
then use the NORMAL command to leave the single-character mode, then
use

another

CTRL/P

return

the

DENVER::NET>

3-11

prompt.

NET:

Network

Command

oDT

Terminal

Utility

ODT

Command

Use

the

ODT

command

that

not

wait

when

for

you use
entire

programs

line

but

such

process

RSTS/E

ODT

characters

them.
Normally,

entire

RSTS/E

line

programs

time

terminated

However,

forth.

process

characters

node,

you

local

node

the

RETURN/LINE

remote

forwards

receiving

where

few

line

FEED

first

(and

characters

from

terminals

string

combination,

programs

immediately.

must

input

of
an

and

EDT

you

type

characters
escape

character,

not

wait

for

entire

When

you

run

such

program

line
at

and

but

issue

any

the ODT command to the NET program
intermediate remote nodes).
NET then

the

remote

node

you

type

them.

For

example:

RUN DECNETS:NET

NET

v4.0

Node

RSTS

name?

Connection

RSTS

V9.3

System

User:

V9.3

DECnet

System

BOSTON
established

RSTS/E

Timesharing
Job

Node

KB27

BOSTON

24-Sep-86

10:23AM

password:

1,221

Password:

S
*

RUN AUXLIBS:0DT
" PCRET>

DENVER: :NET>ODT

210/

1077

this

example,

connection

node

BOSTON

RETURN

and

when
to

responds

with
the

ODT

its

NET

ODT
the

the

local

You

then

run

displays
NET

ODT

and

its

command

nodename::NET>

command

command,

continues

run

BOSTON.

return

processes

you

node

you

BOSTON

and

(DENVER),

RSTS/E

prompt,

level

prompt

returns

node
the

you
node

requesting

utility

press

ODT

CTRL/P,

DENVER.

you

type

ODT.

node

BOSTON.

and

processing

it,

NET

normal.
Note

Using

this

because
link

feature

DECnet/E

than

discretion.

places

must

would

send

heavy
many

normally.

load

Use

the

messages
ODT

mode

network
over
with

then

NET

remote

receives

the

You

type

NET: Network Command Terminal Utility

NET Error

Messages

Table

3-2 lists the NET error messages.

Table

3-2:

NET Error Messages

|
|
ME
| 2CONNECT FAILURE - INVALID NODE NAME NODENA
prompt is
name?
Node
The node name you gave in response to the
|
NET again,
Run
.
not valid. There is no such node in the network
|
specifying a valid node name.
|
|
| 2CONNECT FAILURE - NODE SHUTTING DOWNed for shutdown. No new
The node you requested is schedul
|
logical links to the node are allowed. Try again later.
|
|
LINKS TO NODE NODENAME
| 2CONNECT FAILURE - TOO MANYnode
you requested is too heavy at this
Network traffic to the
|
l link. Try again later.

time to establish another logica

|
|
|
|
|
|

Try again later.

|
|
|
|
|
|
|
|
|
|
|
|

|
| 2CONNECT REJECT - DESTINATION NODE IS UNREACHABLE
le.
reachab
ly
current
|
not
is
access
to
The remote node you tried
|
?CONNECT REJECT - NSP REASON CODE = N

The remote mode rejected NET's request for a logical link. See

appendix A for a list of the NSP reason code meanings.

?ILLEGAL

COMMAND

The NET utility does not recognize the command you typed in

l
|

response to a nodename::NET)> prompt. Type HELP or ? to see a

|
|

display of valid NET commands.
?NETWORK NOT AVAILABLE

|
|
|
1
|
|

|
|

NET is unable to make a logical link to the node you requested. |
For example, the node may be shut down for maintenance, or the |

|
physical links may be out of order. Try again later.
+
—
-e
o

Chapter

NFT:

Network File Transfer Utility

The main function of the Network File Transfer utility (NFT) 1is to
move files from one node to another (see Figure 4-1). You can run NFT
from a terminal to perform the following functions:

Copy files from a storage device at one node to a storage

Copy and append one or more files stored at one node to a

Copy and submit a command file stored at one node to another

device or output device at another node.
file stored at another node.

node’s batch processor or DCL command interpreter for
execution. On RSTS/E nodes, NFT or FAL submits such files to
the

batch

processor.

Execute an existing command file at a remote node.

Delete files stored on disk at a remote node.

Copy and spool print files from one node to another node’s

Display a directory listing of files stored on disk at a

printer.

remote

node.

NFT:

Network

File

Transfer

Utility

BANGOR

TRNTO

$ RUN DECNETS$:NFT

NFT> COPY DALLAS::NEW.BAS =TRNTO::MY.BAS
NODE: TRNTO

Password:
Account: (Not echoed, needed if system password

NODE: DALLAS

DENVER

verification is on.)

BOSTON

User: 104,160
Password:
Account: (Not echoed, needed if system password
verification is on.)

DALLAS

NYC
MK-02319-00

Figure

4-1:

NFT

Transfers

Files

to,

from,

and

between

Remote

Nodes

Note

Although

NFT

Protocol

(DAP),

during

file

protection
NFT

written
it

codes.

Thus,

have

depending

conform

supports

transfers;

commands

<124>,

only

does
files

protection

the

not

Relationships
1s

easier

description

Between

NFT,

understand

how

DECnet/E

what

Data

pass

either

FAL,

and

NFT

does

Access

the

bit

file

created

presence

implements

the

executable

code

bit.

The

the

result
<60>

of
or

executable

RMS
by

the

beginning

file

with

transfer

brief

capability.

NFT: Network File Transfer Utility
The NFT functions listed at the beginning of this chapter are the
of

result

the

relationship between:

NFT

File Access

Record Management

Listener

(FAL)

Services

(RMS)

NFT establishes a logical link with the FAL program at the remote

node.

NFT then accepts commands typed at the local node and transmits

The FAL program, a part of DECnet/E, executes the
them to FAL.
and FAL communicate with each other in a language
NFT
commands.
Thus, even though the user
defined by the Data Access Protocol (DAP).
implementations of NFT,
DECnet/E
various
for
commands can be different
to do file
communicate
can
all DECnet/E systems having NFT and FAL
handling.

You must make sure that the account from which NFT and FAL run have
detached job and total
sets

these

job quotas of one or more.

Your system manager

quotas.

RMS is an operating system file service feature used by NFT and FAL at
DECnet/E nodes to execute input and output to the local I/O devices.
This is of interest mainly because non-RSTS/E nodes can use other
means to do their local file I,/0 and can require some of the NFT
These switches ensure that
switches (see the "NFT Switches" section).
operating systems
different
having
nodes
between
files
transfers
NFT
the
shows
4-2
Figure
format.
usable
a
in
and file handlers
nodes.
DECnet/E
two
at
RMS
and
interaction between NFT, FAL,

NFT:

Network

File

Transfer

Utility

C >
D)sKk

RMS

USER RUNS
NFT

NFT

‘

O s¥

NFT CONNECTS WITH REMOTE FAL

FAL

THEY COMMUNICATE ACCORDING

TO DAP PROTOCOL

NFT USES

FAL USES

RMS TO DO
LOCAL I/0

RMS TO DO
LOCAL 170
MK-02320-00

Figure

4-2:

FAL

Access

You

can

File

ISAM

Files

access

the RMS-11
o

ISAM

Nodes,

(RMS-indexed)

access

Create

Open

Record

NFT,

and

RMS

Work

Together

files

nodes

FAL can perform the

running

DECnet/E

following:

(see

operations:
an

FAL,

Operations

documentation).

File

DECnet/E

Allow

indexed

access

file

for

read

write

access

operations:

Delete the current record

FAL

has

messages

Find

Write

(flush)

out

all

Unlock

(free)

all

locked

records

Get

record

using

keyed

access

Put

record

using

keyed

Update

limited

and

record

the

amount

Allocation

using

current

keyed

sequential

modified

access

buffers

sequential

access

record

memory

Attribute

for

Key

messages.

4-14

Definition

FAL

Attribute

runs

out

memory

NFT: Network File Transfer Utility

for message storage (probably due to the file having too many keys
FAL issues a

defined),

file open error message.

'FAL does not support multiple data streams on a single file.

The

FAL cannot
maximum record length that FAL can process is 512 bytes.
you
However,
records.
larger
have
that
files
for
use record access

can copy larger records from one RSTS/E system to another by using the

NFT /BLOCK switch (see the "NFT Switches" section).

Running

NFT

You can run NFT from any terminal in a DECnet/E system by typing:
RUN DECNETS:NFT

If your system manager has installed NFT as a Concise Command Language
(CCL)

command,

you

can

type:

NFT

In either case, NFT responds with the NFT> prompt and accepts one
command per line until you press CTRL/Z or type EXIT in response to
the

prompt:

NFT>

NFT>
NFT>

command-1
command-2
»

NFT>
NFT>

command-n
" Z

If your system manager has installed NFT as a CCL command and you want
to use a single NFT command, you can type NFT and the NFT command on
one

line:

NFT

command

NFT executes the command and returns control to the RSTS/E monitor.
Note

If you are running under the DCL Run-Time System, you
can duplicate the NFT functions by issuing the
appropriate DCL commands (for example, COPY, DELETE,
Because the DCL command syntax
PRINT, and so forth).
differs significantly from the NFT command syntax (see

Table 4-1), check the RSTS/E Quick Reference Guide and
the RSTS/E System User’s Guide for details about using
DCL

commands.

NFT:

Network

To protect

log-in
are

File

files

Transfer

from

information

four
O
©

unauthorized

for

any

for

supplying

You

can

use

the

You

can

supply

use

the

information

You

can

the

these

NFT

that

information
change

rejects
In

that

the

NFT

cases

goes

for

how

one

you

command

specify

you

specify

you

1if

you

log-in

General

gain

valid,
were

DECnet/E

NFT

and

must

extension

request

that

the

remote

NFT

prompt

you

prompt

for

the

refer to a remote
specified the log-in

not

for

command

current

NFT

using

overridden,

the

log-in

extension

NFT

each

time

and

uses

information

the

override

prompting),

node,

session,

and

particular

remote

node

/IDENTIFY

the

action).

action.

1In

For

you
unless

switch),

existing

log-in

file

the
at

can

information,

remote

the

remote

access

logged

file

any

node.

files

NFT

system

the

1If

that

uses
the

you

remote

the

before

executing

information

could

node

normally

using

the

Commands

command

variable

node

only.

directly

NFT

supply

There

information.

Format

action)

you

command.

basis.

NFT

you

specify

the

access

NFT

way.

name

you

consists

parameters

command

(defining

additioyou
n,

can

use

the

keyword

nodes

switches

(defining

and

files

further

example:

involved

define

DENVER::FILE.LST/SU=DALLAS::MYFILE.TXT

COPY

file

MYFILE.TXT

sign,

force

your

(node

information

affecting

COPY

switch

have

command.

one-time

other

information,

command

the

you

NFT

any

and

throughout

two

the

matter

the

information

information:

(NODESPECIFICATION

information

same

prompts

any

log-in

node.

the

other

uses

access

destruction,

it.

information
No

and

cases

specify

/IDENTIFY

nothing

command

you

reference

this

information

can

once

you

the

for

information
two

NODESPECIFICATION

You

use

referred

specification.

information.

node

methods

node
©

Utility

the

node

indicates
DENVER,

command

that

you

keyword,

node

DENVER

want

and

indicating

DALLAS,
name

that

specified

the

file

called

NFT

supersede

file

you

want

NFT

the

right

the

The

/SU

FILE.LST.

FILE.LST
the

already

file.

exists

copy

the

equal

switch

node

e
=

NFT: Network File Transfer Utility

You can abbreviate command and switch keywords. 1In general, you need
to specify only the first two characters of the keyword (for example,
Some switches, however,
co for CcopY, DI for DIRECTORY, TY for TYPE).
(for example, /NOHE for
switch
the
require four characters to identify
See the
).
/NODELETE
/NOHEADING, /NOSU for /NOSUPERSEDE, /NODE for
"NFT Commands" and "NFT Switches" sections for more information.

Most of the arguments you specify identify nodes and file

specifications, which can contain wildcards and quoted strings.
following sections describe

Node

these arguments.

The

Names

You can use DECnet/E NFT to manipulate files to, from, and between
nodes. NFT also works with files at the local node, although it 1is
more efficient to use RSTS/E utilities and DCL commands to manipulate
files at the local node. See the RSTS/E Utilities Reference Manual
and the RSTS/E Quick Reference Guide for more information.
This chapter uses the sample network shown in Figure 4-3 as an

example. To illustrate file transfers between DECnet nodes having
different operating systems; BOSTON and TRNTO are DECnet/E nodes,
DALLAS is a DECnet/11M node (RSX-11lM operating system), and KANSAS is
a DECnet/RT node

(RT-11 operating system).

NFT:

Network

File

Transfer

Utility

BANGOR

TRNTO

LOCAL TO/FROM REMOTE
OPERATION

KANSAS
DENVER

BOSTON

REMOTE-TO-REMOTE
OPERATION

DALLAS

NYC
MK-02322-00

Figure

4-3:

Sample

identify

alphanumeric
name

from

currently

NFT

remote

node,

node

the

Network

DECnet/E

name.

file

active

Showing

specify

Use

nodes

NODES

(see

the

specify

the

local

node

the

one-

colon

You

network

DECnet/E

name

double

specification.

ACTIVE

Transfers

can

Between

with

six-character,

(::)

separate

determine

using

System

Manager’s

command,

NFT

Nodes

the

NCP

the

names

command

Guide).

1If

run

node

SHOW

you

FAL

the

you

can

specify

the

remote

node

local

node.
As

mentioned

information
extension

the

section

required
the

node

NFT

name.

"Running

access

Enter

NFT,"

files

this

information

format:

nodename"[user-id]

[password]

[sys-password]"::

the

log-in

following

NFT:

nodename

Network File Transfer Utility

is the name of the node at which you want to be
validated as an established user. If you omit the node
name, NFT lists the nodes you have already specified
(if any), along with the log-in information you
specified

for

the

nodes.

If you specify a node name only,
log-in

NFT prompts for

information.

is the project-programmer number or PPN (sometimes

user-id

called a user identification code or UIC).
be up to sixteen characters long.

can

If the remote node permits alphanumeric named
directories in addition to or in place of numeric
PPNs, you can specify the user-id in that form.
password

is the 6- to l4-alphanumeric character string that 1is
your

sy5wpassword

password.

is the system password for the remote node.

up to 16

characters

It can be

long.

are double guotation marks that must enclose the
log-in

information.

NFT removes the quotation marks and passes the
characters they enclose directly to the remote node
without examination. In some instances, this means
that the remote node processes the log-in information
differently than if you specify the information using
the NODESPECIFICATION command or through prompting.
For example, consider the case where the remote node
Because VMS does
is running the VMS operating system.
not permit non-octal user identification codes, NFT
normally converts the specified user-id to the VMSHowever, if you include
compatible octal equivalent.
node name enclosed in
the
the log-in information with
quotation marks, NFT does not perform the conversion
and errors may

You must separate theuser-id,
either

File

space

result.

the password, and the sys-password by

tab.

Specifications

The way you identify files depends on the operating system at the node
For file specification formats used with
where the file is located.
4-9

NFT:

Network

non-RSTS/E

File

Transfer

nodes,

see

the

Utility

documentation

for

the

system.

For

full
‘The

files

RSTS/E
file

RSTS/E

file

nodes, the
specification

specification

used

appropriate

file

specification

(see

the

operating

is a subset of the
System User’s Guide).

RSTS/E

is:

dev:[PPN]filename.typ
where:

dev:

the

device

assumes

the

designation.

system

Although

you

local

remote

can

ensuring

that

magnetic

tapes

disk

refer

nodes,

you

someone
and

busy,

4-1).

You

can

the

local

commands

you

omit

specific

are

the

device,

NFT
use

mounts

other

returns
the

node

DCL

devices

responsible

properly

performs

device

Table

NFT

(SY:).

and

positions

necessary

error

ASSIGN

reserve

the

for
functions.

message

and

(see

DEASSIGN

local

devices.

Note
Use

NFT

files

between

disk

public

normally

mounted

node.

you

each

one

type

device

one

node

first

the

local

node

file

the

NFT

then

use

tape

the

you

brackets

DIGITAL

file

specify
(or

(from

your

PIP
the

disks)

files
a

local
the

disk

node

file

transfer

RSTS/E

from
on

for

the

Utilities

refer

code,

user-id

number

identifying

located
PPN,

you

the

([100,201]
must

for

include

the

parentheses).

systems

identification
the

type

transfer

(see

project-programmer

example).

uses

and

transfer

another

tape

structures

private

Manual.)

where

Some

use

magnetic

directory
square

want

magnetic

example),

Reference

[ PPN
]

move

(either

you

UIC.

the

specified

PPN

you

omit

during

user

the

PPN,

NFT

log-in

sequence.

Access

remote

node.

Some

another

DIGITAL

PPN

systems

depends

allow

alphanumeric

directory

the

PPN.

the

you

can

1If
use

them

users

names

that

remote

system

file

the

your

privilege

assign

are

permits

equivalent
to
such

specification.

names,

the

NFT: Network File Transfer Utility

filename.typ

is the file name and type.

For files on RSTS/E nodes,

the filename can be up to six alphanumeric characters,
and the type can be up to three alphanumeric

characters.

1If a command accepts both an input and an

output file specification and you omit the output

specification, NFT uses the input file specification.
If you omit the file type, NFT does not supply a

default.

Wildcards

NFT permits wildcard characters in file specifications.

You can use

wildcards to select a set of files for sequential file retrieval, file

deletion, file spooling, directory listings, oOr command file
/TM execution. The format of the wildcard syntax depends on the
capabilities of the remote node to process the file specification.
In an input file specification, any valid wildcard that is acceptable
the
to the remote or local system 1s acceptable. For example, if of
n
icatio
specif
remote system is a RSTS/E system, an input file
and a
A?27272.LST selects as input all those files with an type ofPPN.LST
an
in
file name beginning with the letter A. You can enter the
input specification as either [*], for named directories, or [*,*],
for numeric project-programmer numbers.

The only valid wildcard character you can use in an output file
sk
specification, however, is the asterisk (*). You can use an asteri
in
7.LST
A??2?22
to replace one entity in the file specification. Thus,
but
n
icatio
the previous example is invalid as an output file specif
* LST is valid.

certain
When you use wildcards in the output file specification of during
the
basis
-one
one-to
a
on
commands, NFT duplicates file names
er
consid
e,
exampl
For
use.
you
operation depending on the wildcards
»

the following COPY commands:

COPY *.DAT=DALLAS::[COWBOY]*.LST

COPY *.DAT=DENVER::[1,34)FILEA.LST,[3,12]FILEB.LST

On receiving the first command, NFT copies every file from the
directory COWBOY on node DALLAS with the type .LST to a file on the

a
local node in the current directory with the same file name but with

type

.DAT.

[1,34]
The second command causes NFT to copy FILEA.LST from directory
node
local
on node DENVER to FILEA.DAT in the current directory on the
also
and FILEB.LST from directory [3,12] on node DENVER to FILEB.DAT,
in the current directory on the local node.

In most cases where the input file specification contains wildcards
4-11

NFT:

Network File Transfer Utility

but

the

files

output

file specification does not, NFT concatenates the
output file.
For example, consider the previous
slightly modified:

into

example,
COPY

This

command

current

causes

COWBOY

directory

located

NFT

copy

every

DALLAS

the

local

node.

with

node

the

type

.LST

file

with

single
1In

into

the

you

use

wildcard

characters

example,

you

individual
an

depending
an

input

executable
error

files

file

how

message

that

and

you

use

when

must

NFT

single

you

input

aware

file

output

concatenate

you

know

/INQUIRY
NFT

prompts

that

file.

Quoted
You

you

switch
you

are

going

the

and

gives

can

use

quoted

the

characters

paired
the

remote

system

include

quotes

that

example,
want

specific

trying

The

the

problem,
As

NFT

the

option

commands

the

concatenating

may

results,

not

return

different

you

can

locates
copying

include

each
or

the

file

NFT
you

want

storage

prevent

single

quotes

characters
This

copy

for

local

they

the

input

not

file,

copying

the

from

its

one

quotes

follows:

NFT

(’'text’),

enclose
when

you

remote,

DECnet/RT

a
for

must

command.
node

switch

interpreting

own,

you

the

allocating

This

NFT

non-RSTS

not

when

part

file.

NFT

switch

local

general,

useful

for

switch

the

specification

file

system’s

space

the

1In

recognize

file

tell

quotes.

specification

would

the

examination.

RT-11

("text")

passes

the

process

can

has

the

and

the

slash

enclose

and

the

RTNODE::"FILE.LST/B:200"=LOCFIL.1

local

RSTS/E

parentheses

does

suppose

amount

/B:n.

local

use

format

guotes

without

the

For

COPY

this

line.

enclosed

and

characters

you

file

you

characters

double

removes

system

have

Strings

examine

finds

command

may

the
each

named

unpredictable

having

attributes.

file

example,

NFT

files

from

appends

attributes

cause

file.

.LST

specifications

the

For

can

NFT

output

file

type

MASTER.DAT

sequence,

selects.

ASCII

the

file

MASTER.DAT.

When

TM
'

MASTER.DAT=DALLAS::[COWBOY]*.LST

directory
file

input

one

not

(),

remove

characters

characters
DECnet/E

for

node,

NFT
and

also
angle

these
they

pairs.

enclose,

access
NFT

treats

passes

pairs

brackets

without

the

of
in

However,

either
the

square
a

passes

examination.

local

enclosed

4-12

brackets

similar

them
You

remote

characters

[],

manner.

on,

RSTS/E

with

use

these

any

]

can

node.

directly

NFT

along

At
to

RMS.

NFT: Network File Transfer Utility

/TM

NFT

Commands

Table 4-1 lists the eleven NFT commands available.
following discuss

Table 4-1:

The sections

these commands.

NFT Commands

+
————— — =
e

Meaning

Command

———— == +
— -e e e
o

|
- Append file(s) from one node to a file on
- another.

AP[PEND]
|

|
|
|

CO[PY]

. Copy file(s) from one node to another.

DE[LETE]

. Delete file(s) at a remote node.

DI[RECTORY]

. Displays a directory listing of files at a

EXI[T]

. Exit from NFT.

remote node.

i HE[LP]

. Obtain information on available commands and i

. NOD[ESPECIFICATION]
%

| Enter or change remote node log-in
- information.

g
|

PR[INT]

§ Spool file(s) from one node to the line
- printer of another node.

SU[BMIT]

~ Submit file(s) from one node for execution

TY[ PE]

- Display file(s) on the terminal console.

switches.

on another node.

Display the local NFT or remote FAL version

VE[RSION]
eo

number.

—————_—

e
Note

You cannot use NFT to access a file that another user
has open for read/write access. NFT shares read
access only (not read/write access) and returns the
error message 2File 1s protected,
Table

4-3).

skipping -- (see

NFT:

Network

File Transfer

Utility

APPEND

AP[PEND]

Use

the

Command

APPEND

another,

command

appending

them

transfer

the

end

node.

one
of

or
an

files

existing

from

file

one

node

the

target

Note

When
of

you

the

files

use

the

APPEND

files

you

want

are

compatible.

variable-length
records

can

may

receive

AP[ PEND]

Command

not

have

command,

append

For

record

file

one

error

the

make

example,

unpredictable
an

note
and

attributes
sure

that

the

appending a
with

fixed-length

results.

You

may

message.

[dstnode::}outfilem[srcnode::]file[,,..file}

Parameters

dstnode::
Specifies

the

which

NFT

appends

the

other

files.

you

name,

NFT

assumes

the

local

node.

You

must

the

name

destination

the

destination

node

containing

omit

the

include

the

file

destination
two

colons

node
after

node.

outfile

Specifies
appends

the

Separates

file

other

the

specification

existing

file

which

NFT

files.

destination

and

source

specifications.

srcnode:
:

Specifies
other

node.

the

files.

name
If

you

the

omit

source
the

node

source

from which

node

name,

NFT

copies

assumes

the
the

local

NFT: Network File Transfer Utility
APPEND

file

specifies the file specifications for the files NFT transfers and
appends. NFT appends the files, in the order specified, to the end
of

outfile.

For

example:

NFT> APPEND DALLAS::ACCT.BAS=AACCT.BAS,BACCT.BAS

NFT copies files AACCT.BAS and BACCT.BAS from the local node and
appends them to the file ACCT.BAS at node DALLAS (see Figure 4-4).

BANGOR

TRNTO

$ APPEND DALLAS::ACCT.BAS = AACCT.BAS, BACCT.BAS

KANSAS

DENVER

| BOSTON

DALLAS

NYC
MK-02321-00

Figure 4-4:

Example of the NFT APPEND Command

NFT:

Network

File

Transfer

Utility

COPY

CO[PY]

Use

Command

the

COPY

files

source

command

node.

another

COPY

command

keyword

Command

Parameters

COPY

copy

node.

the

one

NFT

does

default

files

not

from

delete

command

for

one

the

NFT;

node

files

you

can

one

omit

the

—

entirely.

the

dStnode::
Specifies

the

node

transfers

the

file(s).

assumes

the

local

name

of
If

the
you

destination
omit

the

node

destination

which

NFT

node

name,

NFT

node.

outfile
Specifies

the

concatenates

you

file

specification

destination
use

the

node.

input

wildcards,

files,

each

destination

node
wildcards in

has

the

input

NFT

creates

the

file

attributes.

(see

the

RSTS/E

Separates

include

the

copies

the

files

you

include

not

specified,

creates

the

you

the

remove

outfile.

specified

with

outfile

the

always

file

has

RMS

attributes

Manual).

specifications.

you
you

include
omit

terminal.

equal

file(s)

NFT

thus

1If

your

NFT

transferred

wildcards,

specification

source

only

the

order

the

names.

RMS,

and

use

file

Reference

(=)

gives

the

PIP

command.

input

but

file

use

destination

output

using

can

sign

NFT

outfile

Utilities

equal

specification

outfile

You

you

sign

outfile.

all

You

need

dstnode

outfile

three

items,

dstnode

you

omit

(=),

NFT

assumes

*.*

NFT

and

for

srcnode::
Specifies

the

file(s).

node.

node

you

name

omit

the

source

node

from

name,

which

NFT

assumes

copies

the

local

NFT:

Network File Transfer Utility
COPY
|

specifies the file specifications of the files NFT copies from the
source

node.

For

example:

NFT>

AFIL.BAS=TRNTO::AFIL.BAS

NFT>

BFIL.BAS=TRNTO::BFIL.BAS

NFT>

CO DKl1:MYFILE.BAS=TRNTO::AFIL.BAS,BFIL.BAS

NFT> COPY DALLAS: :NEWFIL..BAS%TRNTO: :AFIL.BAS,BFIL.BAS
In all these examples, NFT copies files AFIL.BAS and BFIL.BAS from the
1In the first two commands, NFT
node named TRNTO (see Figure 4-5).
system disk as separate files
node’s
\ copies the files to the local
named AFIL.BAS and BFIL.BAS, the same names they had at node TRNTO.
In the third command, NFT copies and concatenates the files to form a
1In the fourth
file named MYFILE.BAS on disk DKl at the local node.
command, NFT copies the files to form a file named NEWFIL.BAS on the
public disk

at node

DALLAS.

NFT:

Network

File

Transfer

Utility

COPY

BANGOR

TRNTO

$ AFIL.BAS = TRNTO::AFIL.BAS
$ COPY DK1: * =DALLAS:AFIL.BAS BFIL.BAS

KANSAS

DENVER

BOSTON

DALLAS

NYC
MK-02315-00

Figure

4-5:

Example

the

NFT

COPY

Command

Mm%

NFT: Network File Transfer Utility
DELETE

' DE[LETE]
Command

Use the DELETE command to delete the specified disk files on remote
nodes or the local one.

You cannot delete tape files.

|
.

DE[LETE]

[dstnode::]file[,...file]

{

Command Parameters
dstnode::

specifies the node name of the remote node at which NFT deletes the
files. If you omit the node name, NFT assumes the local node.
file

specifies the file specifications for the disk files NFT deletes.

You cannot delete tape files.

For example:

NFT> DELETE DENVER::FIL.RNO,BINFIL.SAV,RM.BAS

NFT deletes files FIL.RNO, BINFIL.SAV, and RM.BAS from the public disk
at node DENVER (see Figure 4-6).

NFT:

Network

File

Transfer

Utility

DELETE

BANGOR

TRNTO

KANSAS

DENVER

BOSTON

$DELETE DENVER:AFIL.BAS, BFIL.BAS

DALLAS

NYC
MK-02323-00

Figure

4-6:

Example

the

NFT

DELETE

Command

NFT: Network File Transfer Utility

DIRECTORY

Use the DIRECTORY command to display a directory listing of files
located at a

remote node.

Format

DI[RECTORY] [dstnode::][outfile][m}[srcnode::]file[,.‘,file]
Y

Command

Parameters

dstnode::

Specifies the name of the node on which NFT creates the directory
listing. If you omit the node name, NFT assumes the local node.
outfile

specifies the file specification of the file to which NFT writes the
directory listing. 1If you omit outfile, NFT sends the listing to
the terminal at the specified node. If the file currently exists,
NFT overwrites its contents, unless you use the /APPEND switch.

Separates the destination and source specifications. Use the equal

sign (=) only if you include a destination node or outfile
specification in the command. If you omit the destination node,
the outfile, and the equal sign (=), NFT sends the listing to your
terminal.

srcnode::

Specifies the name of the node where the files you want to list-are
located.

file

Specifies the file specifications of the files on the source node

you want to list.

For example:

DIRECT KANSAS::[7,214]*.%

NFT displays a complete listing of all files in account [7,214] on the
system disk of node KANSAS on the local terminal (see Figure 4-7).

NFT:

Network

File

Transfer

DIRECTORY

Utility

BANGOR

$DIRECT KANSAS:[7,214]".*
(Directory listing of all files

in[7,214Jon node KANSAS.)

TRNTO

KANSAS

DENVER

BOSTON

DALLAS

NYC
MK-02324-00

Figure

4-7:

Example

the

NFT

DIRECTORY

Command

NFT: Network File Transfer Utility

EXIT

EXI[T]

Command

Use the EXIT command to terminate execution of NFT.
to

pressing

Format

EXI[T)

It 1s equivalent

CTRL/Z.

|
|

|
%

NFT:

Network

File

Transfer

Utility

HELP

HE[LP]

Use

Command

the

HELP

switches
network

command

available

with

display

NFT.

information

The

HELP

access.

about

command

the

does

commands

not

and

involve

St
ik

Qualifiers

Command

o
s

[qualifier)

odkit;

HE[LP]

Format

COMMANDS

SWITCHES

Command

Qualifiers

COMMANDS

Specifies

that

commands.

the

help

you

text

want

for

not

both

display

the

help

text

for

include

any

qualifier,
NFT

commands

and

switches.

all

NFT

displays

SWITCHES

Specifies

that

you

want

display

the

help

qualifier,

NFT

displays

switches.
If

you

both

not

commands

include

and

any

switches.

text

for

the

all

NFT

help

text

for

NFT: Network File Transfer Utility

NODESPECIFICATION

' NOD[ESPECIFICATION] Command

Use the NODESPECIFICATION command to enter or change the log-in

information required to establish you as a valid user at a remote

NFT keeps this information for use in later references to the

node.

node during your current NFT session.

You do not have to use this command to define initial log-in values.
However, NFT prompts for log-in information each time you refer to a
node for which you have not yet given any log-in information. NFT
keeps this log-in information during your current NFT session or until
you

change

it.

You can alter log-in information on a one-time basis for a single
command by using either the node name extension or the /IDENTIFY
switch.

Format

NOD[ESPECIFICATION]

[nodename::]

Command Parameters
nodename:
:

specifies the name of the node where you want the system to

validate you as an established user. If you omit the node name,
NFT lists the nodes you have already specified, if any, along

with the log-in information you gave for the nodes.

If you specify a node name, NFT prompts for log-in information,

after first displaying the node you specified:
Node:
User:

Password:

System Password:

nodename
[ PPN

password

sys-password

where:

nodename

is the name of the node you specified.

[ PPN ]

is the project-programmer number (sometimes
called a user identification code or UIC) used

for logging in at the remote node. It can be up
to 16

characters

long.

NFT:

Network

File

Transfer

Utility

NODESPECIFICATION

If the remote node allows alphanumeric
directories in addition to or in place
PPNs,

password

sys-password

you

your

the

remote
a

specify

the

PPN

l4-alphanumeric

password.
6-

node.

system

NFT>

can

DIR

l4-character
If

the

password,

that

character

system

remote
press

named
of

numeric

form.

string

password

node

does

RETURN.

For

not

that

for

the

require

example:

BOSTON::

Node:

BOSTON

User:

4,120

Password:
System

Password:

<RET>

NFT>

After

accepting

command.

the

log-in

information,

NFT

ready

another

NFT: Network File Transfer Utility

{

"PR[INT] Command

Use the PRINT command to copy one or more disk files at one node to
one or more temporary files at another node for input to the line
printer. After printing, NFT deletes the temporary file from the
destination node, unless you use the /NODELETE switch.

If the Print/Batch Services package (PBS) is active on the destination
RSTS/E node, the PRINT command sends the print job to the NETSPRINT
queue, rather than sending it to the LPO queue or the default queue.
If PBS is not active, the PRINT command sends the job to the

OPSER-based print

spooler.

Format

PR[INT] [dstnode::][outfile][=][srcnode::]file[,...file]
Command

Parameters

dstnode::

Specifies the name of the node to which NFT copies the files for
printing. If you omit the node name, NFT assumes the local node.
outfile

Specifies the name of the temporary file at the destination node.

If you do not use wildcards in the outfile specification, NFT
concatenates the input files into a single output file before
printing. If you do use wildcards, NFT creates multiple temporary
files,

depending on the wildcards you use.

I1f the destination node is a RSTS/E node, outfile must be a disk

file.

Separates the destination and source specifications. Use the equal
sign (=) only if you include a destination node or outfile
specification in the command.

srcnode::

Specifies the name of the source node from which NFT copies the

files. If you omit the source node name, NFT assumes the local node.

NFT:

Network

File

Transfer

Utility

file

Specifies

the

source

NFT>

file

node.

specifications

For

the

disk

example:

files

NFT

copies

from

TRNTO: : TEXT.DOC=BOSTON: :

BOOK?.DOC

NFT takes all files at node BOSTON that have file names
beginning with
BOOK and
the

TEXT.DOC

.DOC

node

type,

TRNTO

and

copies

them

(see

Figure

4-8).

temporary

file

named

BANGOR

$PRINT TRNTO::TEXT.DOC = BOSTON::BOOK?.D0C

TRNTO

KANSAS
DENVER

BOSTON

DALLAS

NYC

Figure

4-8:

omit

you

NFT

sends

case,

NFT

/DELETE

NFT>

Example

the

destination

NFT

input

files

does

not

delete

the

For

node,

the

switch.

the

Command

ocoutfile,

printer

file

after

and

your

the

egual

sign

local

node.

this

use

the

printing,

unless

example:

you

(=),

BOSTON::BOOK?.DOC

NFT

takes

all

BOOK

and

prints

temporary

MK-02325-00

file

files

them
and

node

BOSTON

node

does

that

BOSTON.

not

delete

have

does

them.

file

not

names

beginning

transfer

them

with

NFT: Network File Transfer Utility

SUBMIT

SU[BMIT]

Command

from one node to one
Use the SUBMIT command to copy one Or moOre files tion.
After
or more temporary files at another node for execu
the destination
execution, the system deletes the command file from natio
node must
node unless you use the /NODELETE switch. The desti be inn the
proper
be able to execute command files and the files must , the syste
m
format for execution at that node. For RSTS/E nodes
E
RSTS/
the
See
ssor.
proce
submits the files to BATCH, the batch
format
Utilities Reference Manual for a discussion of the| command file
|
for BATCH.
ces package (PBS) 1s
If the file type is .COM and the Print/Batch Servi
command sends the
active on the destination RSTS/E node, the SUBMIT queue
. Otherwise,
file to the PBS batch server and to the NETSBATCH
it sends the file to the OPSER-based batch processor.

Command Parameters
dstnode::

NFT copies the
Specifies the name of the destination node to which
the command files for execution and deletion. If you omit the node
name, NFT assumes the local node.

outfile

es at the
Specifies the name of the temporary file NFT creat
file
destination node. If you do not use wildcards ina the
single output file.

specification, NFT concatenates the files into
rary files at the
If you use wildcards, NFT creates multiple tempo
oOn the wildcards you

destination node, with file names depending
use.

ions. Use the equal
Separates the destination and source specinficat
node or outfile
sign (=) only if you include a destinatio
specification in the command.

srcnode::

Specifies the name of the source node where the files are located.
4-29

NFT:

Network

File

Transfer

SUBMIT

you

omit

the

source

Utility

node

name,

NFT

assumes

the

local

node.

file
-

Specifies
NFT>

the

SUBMIT

file

specifications

the

input

files.

For

example:

KANSAS::RBAT.CTL=*.CTL

NFT

copies into a temporary file called
RBAT.CTL
files at the local node having a .CTL
type.
NFT
deletes the files (see Figure 4-9),.

BANGOR

node

then

KANSAS

submits

all

and

$SUBMIT KANSAS::RBAT.COM =*.COM

TRNTO

KANSAS
DENVER

BOSTON

DALLAS

NYC

Figure

4-9:

omit

the

submits

destination

the

files

you

NFT

this

you

use

NFT>

NFT

case,
the

NFT

the

does

/DELETE

SUBMIT

takes

batch

Example

the

NFT

the

not

switch.

MK-02326-00

SUBMIT

node,

the

batch

delete
For

the

Command
outfile,

and

processor

files

the

after

equal

your

sign

source

execution,

example:

(=),

node.

unless

KANSAS::RBAT.CTL

file

processor

RBAT.CTL

the

node

KANSAS.

KANSAS

and

does

not

delete

submits

the

file

4-30

the

afterward.

NFT: Network File Transfer Utility

TYPE

TY[PE]

Command

node
the input files from the sourcecomm
Use the TYPE command to display and
and
COPY
the
to
nt
vale
equi
on your terminal. The TYPE comm left isside of (and including) the equal
when you omit everything on the
sign.

~~,

Command

Parameters

scrnode::

from which NFT retrieves the
Specifies the name of the source node
the source node name, NFT assumes
file(s) it displays.
the

local

node.

If you omit

file

specifies the file specifications of the input files. For example:
NFT> TY DENVER::DAILY.SUM

from the public disk on remote node
NFT retrieves the file DAILY.SUM term
inal. See Figure 4-10.
DENVER and displays them on your

NFT:

Network

File

TYPE

Transfer

Utility

BANGOR

TRNTO

KANSAS

BOSTON

DENVER

$TYPE DENVER::DAILY.SUM

DALLAS

NYC
MK-02327-00

Figure

4-10:

Example

the

NFT

TYPE

Command

NFT: Network File Transfer Utility

VERSION

VE[RSION] Command

version numbers of the local
Use the VERSION command to displaye the
program, as well as the version
DECnet/E NFT program or the remot FAL
(DAP) being used.
number of the Data Access Protocol

Format
|

VE[RSION] [srcnode::]

Command Parameters
srcnode::

h the version number of FAL
Specifies the name of the node at whic
name, NFT displays the
is to be examined. 1If you omit the node
local node.

version numbers of NFT and DAP on the

switch

description

and

long

1In

applies
as

follows

that

are

you

file

to
append

only.

mutually

4-2.

Switches

T p—— F o

RTe

Switch

Fm o b

Meaning

———o

/AS[CII]

Append

input

output

file.

Data

ASCII

being

file(s)

data.

Transfer

image

512-byte

blocks.

Generate

directory

/BR[IEF]

data

abbreviated

Allocate

contiguously.

/CTG

/ID[ENTIFY]

Special-case -delete

SUBMIT and

Generate

directory

Have

log-in

NFT

Data

extended

8-bit

for

PRINT,

data.

SUBMIT,

TYPE

APPEND,

COPY

Verify

function

file

Generate
directory

before

execution.

normal
listing.

4-34

4-36

DIRECTORY

4-37

SUBMIT

All

PRINT,

4-38

|
4-38

|
DIRECTORY

All

4-38

|
|

APPEND,

COPY

4-39

|
|

APPEND,

COPY,

DELETE,

PRINT,

SUBMIT,

TYPE

4-39

4-38

input

4-36

transferred

APPEND,

COPY,

/IN[QUIRY]

information.

being

DIRECTORY

commands.

/IM[AGE]

listing.
prompt

for

Page

o it

/FU[LL]

space

/DE[LETE]

COPY,

listing.

/CO[NTIGUOUS]

|
e

Commands

. COPY,

/BL[OCK]

NFT

transferred

7-bit

Applicable

/AP[PEND]

/JLI[ST]

they

Table

general,

5o A

one

in NFT commands.
Most of
commands; some can apply only

specification.

specification

than

Further

NFT

file

use

4-2:

file

compatible.

Table

destination

can
certain

to
use

you

can

only

e o

switch

You

switches

0wt ermnnss

source

the

apply

the

lists

switches

S i

4-2

these

Table

Utility

Switches

Transfer

NFT

File

Network

DIRECTORY

|
|
|

NFT:

4-40

NFT: Network File Transfer Utility
Table

4-2:

NFT

Switches

(Cont.)
- $———————

—— — T
e

fmm

Switch
—

/LO[G]

/NA[TIVE]

/NOA[TTRIBUTES]

. /NOCO[NTIGUOUS]
|
|

. /NOD[ELETE]

/NOH[EADING]

|
|
'
|

Meaning

Applicable
NFT Commands

|
!

|
|

Page

}
|

/MO[RE]
or -

g
|

/NOSU[ PERSEDE]

/POS
|

.
'

Continue command input on
next line.

| All
?

|
]

4-40

Reformat file to stream

| APPEND,

4-41

|
.
|
.
.
|

|
|
|
|
|

ASCII.

Ignore RMS attributes.

@ Allocate space
- noncontiguously.
|

Do not delete temporary

~ files.
|

-~Generate directory
~listing with no header.
1
- Do not supersede an
. existing file.

COPY, PRINT,
SUBMIT, TYPE

.
.

COPY

COPY, PRINT,
SUBMIT

PRINT,

|
|

4-42

. SUBMIT

| DIRECTORY
i
|
i COPY, PRINT,
| SUBMIT

.
|
|
|
|

. Position magnetic tape to | COPY
.

end of volume.

COPY

4-42
4-43

. 4-43

‘

4-43

|
|

|
|
|
|
5
%

|
|

|
|
!

/RWC

Rewind magnetic tape on
close.

/RWO

Rewind magnetic tape on

COPY

4-43

.
|

/SU[PERSEDE]

|
-

Supersede an existing
file.

.
|

COPY, PRINT,
SUBMIT

|
|

4-44

|
|

DIRECTORY

4-44

| APPEND,
| COPY, PRINT,
| SUBMIT

|
|
|

4-44

|
|
|

| open.

/TO[ TAL]

Qutput directory size

|
|
|

/VA[RIABLE]

.
~
f

Reformat file to variable
format.

|
|

~ only.
;

—-e
e

|
|

e - $m—————— +

NFT:

Network

/AP[PEND]
Use

the

File

Utility

Switch

/APPEND

COPY

and

COPY

command,

NFT

Transfer

switch

DIRECTORY

appends

the

with

the

commands.

the

input

destination

When

same

files

you

using
the

use
the

file
the

specification

/APPEND

APPEND

output

switch

command

the

with

the

itself:

file.

Note

When

you

use

note

the

attributes

the

make

sure

that

appending

When

you

output

the

may

use

file

output

the

COPY

NFT>

DIRECTORY

/ASCII
Use

/ASCII

ASCII

For

record

file

error

the

appends

and

example,

one

with

results.

message.

DIRECTORY
the

command,

For

unpredictable

with

NFT

COPY

appended

new

command

directory

and

listing

COPY

/BL[OCK]

the

APPEND

DIRECT.LST/AP=[7,214]*.BAS

switch

data.

You

the

indicate

can

use

APPEND,

that

transmitted

file

the

/ASCII

switch

with

the

COPY,

PRINT,

SUBMIT,

TYPE

contains
source

file

commands.

NYC::MEMO.DOC=[7,214)NOTES.TXT/ASC

Switch

/BLOCK
COPY

source file

switch

when

commands.

specification

transferring image (binary) files
can use the /BLOCK switch with

You

NFT

transfers

the

files

systems

using
the

512-byte

blocks.
In

example:

NFT>

Use

switch

exists,

the
be

compatible.

have

receive

TEXT.DOC/APP=DALLAS::BOOK??.DOC

specification
For

are

can

with

files

Switch

the

7-bit

not

/APPEND

file.

switch

the

files

records

may

already

NFT>

the

variable-length

fixed-length
You

/APPEND

general,

support

the

binary

/BLOCK
block

switch

only

transfers.

applies

that

fully

the

NFT:

Network File Transfer Utility

You must use the /BLOCK switch when transferring non-ASCII files that
On RSTS/E systems, this includes:
do not have recorded attributes.
o

Files compiled by BASIC-PLUS

Record-I/0

Virtual

Binary

On RSTS/E

files

array data

files

systems

(.BAC file type)

this

and

(.0OBJ

.SAV file

types)

includes:

Files generated by the MACRO assembler

Compiled

Compiled DIBOL-11

Files generated by the RT-11

Files

FORTRAN

files

generated by the RT-11

librarian
linker

You cannot use the /BLOCK switch to transfer ASCII stream files or
files that contain valid RMS attributes (for example, object modules
Using the /BLOCK switch with these files
created using MAC.TSK).
results in a BLOCK image copy of the file, with the original
attributes being changed to RMS attributes for a stream file of zero
For example:
record length and fully used blocks.
NFT>

COPY

STORBN.BAC=BOSTON::COMP.BAC/BL
Note

Do not use
switch or

/BR[IEF]

the /BLOCK

switch with either

the /VARIABLE

the /NATIVE

switch.

Switch

Use the /BRIEF switch at the end of the DIRECTORY command to display a
brief directory listing including device, directory, file name, and
This listing is similar to the listing the RSTS/E PIP
file type.
program generates.

NFT>

For

example:

DIR QUICK.DIR=NYC::[7,214]*.DOC/BR

NFT:

Network

File

/CO[NTIGUOUS]

Use

the

COPY,

the

destination

command
NFT>

this

PRINT,

fails.

the

The

Switch

switch

with

SUBMIT

commands

file(s).
For

example,

/DE[LETE]

Use

allocates

the

binary

from

the

primary

with

after

the

use

file

destination

printed

desired

node.

this

the

With

temporary

destination

causes

files

For

example:

Switch

Use

/FULL

the

switch

listing
size,

for

space,

the

node

consisting

DALLAS

(an

file

the

that

are,

is,

two
in

Using

deleted

source

commands

these

they

any

command

done.

when

the

not

files

already

exist

commands,

the

files

fact,

the

file
you

the

source

/DELETE

the

are

files

switch

conclusion

supply

not

and

this

the

end

includes

code,

attributes.

that

the

DIRECTORY

device,

command
to

directory,

creation

date

file

and

time,

This

listing

PIP

program

generates.

RSTS/E

display

name,

similar

well

the

For

information.
only

switch

any

NFT

uses

for

the

once

command

the

with
to

both

the

source

cause

NFT

information

you

give

NFT

does

current

operation.

4-38

and

prompt

example:

destination

for

log-in

response
not

keep

full

Switch

/IDENTIFY

file

DALSYS.DIR=DALLAS::SY:[1,2]*.*/FULL

specifications
prompting

contiguous

specification

SUBMIT

files.
be

protection

listing

DIR

that

symbolic

/ID[ENTIFY]

Use

space

ROUGH.DRF/DELETE

/FU[LL]

file

since

the

file

batch processor

form

case

NFT>

space

FILEl.TSK,

applies

and

the

this

not

directory

allocate

specification

node.

specification

submitted

operation.

any

switch

deleted

type,

contiguous

allocate

contiguous

file

command

automatically

listing

file

cannot

local

switch

file

specification

the

NFT

destination

Switch

/DELETE

directory

the

example:

NFT

for

copied

that

NFT>

Utility

DALLAS::FILEl.TSK/CO=MYFILE.TSK

node)

MYFILE.TSK

delete

/CTG

/CONTIGUOUS

COPY

RSX-11M

Transfer

this

the

NFT: Network File Transfer Utility

information for the remainder of the session. After the execution of
a command with this switch, the log-in information goes back to what

was previously specified for

the node,

if any.

I1f you use the /IDENTIFY switch with both the source and destination
specifications, NFT prompts for information for the source node first.
NFT uses a second set of prompts to obtain information concerning the
destination node.

For example:

NFT> COPY BOSTON::FILEl.TXT/IDmDALLAS::FILE3.TXT,FILE4.TXT/ID
Node:

User:

DALLAS

120,150

Password:

System Password:
Node:

User:

BOSTON

30,117

Password:

System Password:
NFT>

NFT uses the log-in information to copy the files and then deletes the
log-in information from its internal records. Previously specified
log-in information for BOSTON and DALLAS, if any, is restored for use
in later commands.

/IM[AGE]

Switch

Use the /IMAGE switch to indicate that a transmitted file contains
8-bit image data. You can use the /IMAGE switch with the source file
For example:
specification of the APPEND and COPY commands.
NFT> APPEND DALLAS::TOTALS.DAT=BOSTON::[1,34]JDAILY.SUM/IMAGE

/IN[QUIRY)]

Switch

Use the /INQUIRY switch with the source file specification of the
APPEND, COPY, DELETE, PRINT, SUBMIT, and TYPE commands. Use the
/INQUIRY switch to reguest NFT to display the name of each input file
for verification before it opens the file and performs the indicated
function. After NFT displays the name, you can respond to the prompt
with either YES or NO to indicate whether or not NFT performs the
operation on that particular file. 1If you respond with NO, NFT skips
the file and displays the next file name.

The /INQUIRY switch is useful when you do not use wildcards in the
destination file specification and you want to concatenate the source
4-39

NFT:

Network

files

into

File

one

Transfer

file.

1In

this

represented

attributes,

unpredictable

the

final

the

Utility

wildcard

destination

circumstance,

specification

results

file.

NFT

can

may

occur,

the

have

may

source

files

incompatible

depending

not

using

the

/INQUIRY

file-by-file
operation.
NFT>

basis,
For

DELETE

/LI[ST]

switch,

you

can

make

the

whether

you

want

you

generate

error

decision,

message.

how

include

the

example:

file

use

the

NYC::[7,214]1*.DOC/INQ

Switch

Use

the /LIST switch at the end of the DIRECTORY command to display a
directory listing that includes:
device, directory, file name, file
type,

file

size,

protection

listing

program

generates.

you

default.

similar

use

For

example:

DIRECT

/LO[G]

Switch

the

COPY,

the

/LOG

indicated
in

NFT>

COPY

also

file

date

that

DIRECTORY

and

the

time.

RSTS/E

command,

This

PIP

/LIST

the

source

file

The

and

/LOG

file

TYPE

your

specification

commands

terminal

switch

For

after

useful

reqguest

NFT

when

the

APPEND,

that

NFT

performs

you

use

log

the

wildcards

example:

BOSTON::[1,230]*.*=DENVER::[3,45]*.MAC/LOG

supperts

the

not

/MO[RE]

Switch

Use

/NOLO[G]

actually

/MORE

the

terminal

line

indicate

NFT

prompts

CTRL/Z

creation

listing

the

specification.

then

and

with

SUBMIT,

input

therefore,

the

switch

with

PRINT,

function.

input

code,

directory

DENVER::[100,57])*.*/LIST

each

the

NFT

any

switch

DELETE,

name

the

not

NFT>

Use

while

hyphen

for

typing

switch,

character

that

the

continuation

which .is

the

default,

and

required.

continuation

(-)

switch

command
lines

line,

continues

the

end

the

you

press

with

MORE>.

NFT

deletes

the

whole

a
line.

command

NFT: Network File Transfer Utility

times as you want.

For example:

DALLAS::DKO0:[120,153]FILE.RNO=BOSTON::[30,205]DK1/MORE

NFT>
MORE>

:FILE.RNO,-

MORE>

FILE3.RNO

NFT>

You cannot use the /MORE switch when you include a command on the same
line as the NFT CCL command.

/NA[TIVE]

Switch

Use the /NATIVE switch with the destination file specification in the
APPEND, COPY, PRINT, SUBMIT, or TYPE commands when the destination
node is a RSTS/E node. The /NATIVE switch converts files stored at
the source node (in either of two ASCII formats) to stream ASCII files
at the destination node.

The two source formats are:

RMS-11 variable-length records with implied carriage control

Variable-length records with embedded carriage control
characters

This conversion is useful when you transfer ASCII files from an RSX or
VAX/VMS node that does not process stream ASCII to a RSTS/E node that
does.

For example:

NFT)> COPY TEST.MAC/NA&DALLAS::FIL.MAC

You can also use the /NATIVE switch with the source file specification
in the APPEND, COPY, PRINT, SUBMIT, or TYPE commands when the source
node is either a TOPS-20 or an RT-11 node and you want to transfer the
files as stream ASCII

files.

Because RT-11 and TOPS-20 files do not contain file attributes, NFT at
the source node has no way of knowing that the file is stream ASCII
unless you use the /NATIVE switch.

For example:

NFT> COPY PROGA.MAC=NYC::PROGA.MAC/NA
Note

You cannot use the /NATIVE switch with the /BLOCK
switch.

NFT:

Network

File

/NOA[TTRIBUTES]

Use

the

want

ignore

the

destination

you

use

the

use

source
For

switch

RMS

the

source

RMS

file

but

file

you

the

ignores

the

RSTS-to-RSTS

the

output

source

file

attributes

example:

Use

both.

destination

file

without
any

and

you

switch

However,

file

RMS

specification,

copy

/NOATTRIBUTES

specification,

switch

creates

switch

when

attributes.

/NOATTRIBUTES

specification,

Utility

Switch

/NOATTRIBUTES

the

you

Transfer

exist

attributes.

RMS

for

opens

that

the

file.

NFT> COPY TEST.MAC=DALLAS::FIL.MAC/NOA
In

this

opens

the

example,

file

has

the

for

COPY

this

PRINT,

example,

the

switch with

the

destination

SUBMIT

commands

file(s).

For

allocates

the

binary

NFT>

SUBMIT

the

switch

SUBMIT

created

/NOHE[ADING]

attributes.
the

RMS

also

attributes

to allocate
example:

file

specification
noncontiguous space
|

noncontiguous

space

file

FILEl1.TSK,

which

consists

the

destination

file

node

DALLAS
of

(an

the

Switch

NFT>

with

commands

the

suppress

destination

node.

BOSTON::RBAT.CTL/NOD=*,CTL

deletion

For

specification
of

the

in
temporary

example:
|

TEXT.DOC/NODELETE=DALLAS: :BOOK??.DOC

Switch

/NOHEADING

switch at the end of the DIRECTORY command to
listing that does not include the header line across the top.
directory listing includes a complete file specification for each

obtain
The

NFT

for

/NODELETE

file(s)

RMS

ignores

MYFILE.TSK.

Use

with

and

DALLAS::FILEl.TSK/NOCO=MYFILE.TSK

node)

/NODE[LETE]

Use

TEST.MAC

DALLAS

Switch

destination

RSX-11M

file

node

/NOCONTIGUOUS

COPY,

the

NFT>

creates

any.

/NOCO[NTIGUOUS]

Use

NFT

FIL.MAC

NFT:

Network File Transfer Utility

The /NOHEADING
entry (device, PPN, number, file name and file type).
For example:
switch is useful in batch command files.
NFT>

DIRECT LIBRY.CTL=DALLAS::[2,173]*.SAV/NOHEAD

/NOSU[PERSEDE]

Switch

Use the /NOSUPERSEDE switch with the destination file specification in
If a file already exists at the
the COPY, SUBMIT, or PRINT commands.
destination node with the same name as that given in the command, the
command

fails.

when NFT finds that the specified output file name already exists, 1t
The
prompts you, asking whether you want to supersede the file.
useful
is
This
feature.
automatic
this
/NOSUPERSEDE switch disables
For
prompting.
unexpected
handle
in batch command files that cannot
example:

NFT>

/POS

COPY

FILE.LST/NOSU=BOSTON::FILE.TXT

Switch

Use the /POS switch with the destination file specification in the
Using the /POS
COPY command when the device is a magnetic tape.
switch causes NFT to position the file at the current end of volume
before making the transfer.

For example:

NFT> COPY MT2:HPFIL.BAC/POS=BOSTON: :HPRTN.BAC

/RWC

Switch

Use the /RWC switch with any file name in the COPY command when the
device is magnetic tape. Using the /RWC switch causes NFT to rewind
the tape after making the transfer.
NFT>

For example:

COPY MT1:RMAX.BAS/RWC=BOSTON: :RMAX.BAS

/RWO Switch

Use the /RWO switch with any file name in the COPY command when the
Using the /RWO switch causes NFT to rewind
device is magnetic tape.
the tape before making the transfer.
NFT>

For example:

COPY MTO:FILEX.RNO/RWO=BOSTON: :TEXT.RNO

4-43

NFT:

Network

/SU[PERSEDE]

Use

the

COPY,

replaces

node

the

/TO[TAL]

total

the

individual

/TOTAL

size

DIR

Use

the

APPEND,

file

you

specify

the

new

file.

with

switch

directory.

the

directory

COPY,

ASCII

with

process

transfer

the

end

the

1In

entries.

switch

with

PRINT,

the

source

implied
stream

specification

already
in

the

For

DIRECTORY

this

exists

command,

the

NFT

example:

For

command

instance,

NFT

display

does

not

list

example:

COPY

the

destination

SUBMIT

commands

node

carriage
ASCII

stream ASCII

VAX/VMS

this

name

/VARIABLE

stream

same

file

Switch

format

RSX

the

destination

NYC::[1,2]*.%/TOTAL

/VA[RIABLE]

NFT>

with

the

commands.

Switch

the

with

FILE.LST/SU=BOSTON::FILE.TXT

the

RSX

switch

existing

Use

not

Utility

Switch

SUBMIT,

COPY

NFT>

Transfer

/SUPERSEDE

destination

NFT>

File

files,

files

node.

For

RMS-11

control.
from

file

specification

convert

file

variable-length

Because

you

mainly

use

DECnet/E

from

record

RSX

and

the

/VARIABLE

VMS

nodes

switch

DECnet/RT

node

DECnet/E

node

the

example:

DALLAS::FIL.MAC/VA=TEST.MAC

example,

NFT

copies

MACRO

file

from

node.
Note

You

cannot

use

the

/VARIABLE

switch

with

the

/BLOCK

switch.

NFT

Error

Table

4-3

mistake

during

Messages

lists

typing

NFT

the
an

error

NFT

messages

command

initialization.

that

(syntax

NFT

prints

errors)

when

you

make

error

ocCcCurs

NFT: Network File Transfer Utility
Table 4-3:

NFT Error Messages

+
S et ;
Message and Meaning
|
ttke— +
t
e —————B i
fmm

There are too many guotes, commas, underscores, and equal signs
in the command. The current limit on these special characters
per command is 40.

2NFT -- FILE PROTECTED, SKIPPING

The file you attempted to access 1s open for read/write access

by another user.

|
|
-

>NFT -- BREAK BUFFER OVERFLOW

—

You cannot continue a one-line
switch.

ILLEGAL
?NFT -- ATTEMPTED CONTINUATION IS CCL
command with the /MORE or -

|
|

?NFT -- FILE SPECIFICATION TOO LONG

The file specification you typed 1is too long to fit in an
internal buffer used by NFT.

?NFT -- GMCRS DIRECTIVE FAILURE

1M
Tell your DIGITAL Software Support Specialist that the RSX-1
Then
.
failed
has
line
d
directive used to read the CCL comman
retype the command, starting NFT with RUN SNFT.

?NFT -- INVALID COMMAND FORMAT

|
Can be caused by one of several errors:
name in a
node
a
than
other
ing
someth
o Trying to type
d.
NODESPECIFICATION comman
o Typing a double colon (::) 1in a NODESPECIFICATION command
o

o
o
o

o
2NFT --

without any node name.
Using any switch other than /IDENTIFY or /INQUIRY in a

DELETE ot EXECUTE command.
Not typing an equal sign (=) 1in an APPEND command.
Typing an equal sign (=) in a DELETE, TYPE, or EXECUTE
command.
Typing anything but COMMANDS or SWITCHES after a HELP

|
|
%

é
|

;
|

?
|
2
i

command.

Not typing a node name in an EXECUTE command.
INVALID NETWORK NODE NAME

valid node names are from one- to six characters that are
uppercase, alphanumeric, and must contain at least one letter.

?NFT -- INVALID NODE NAME SPECIFICATION

Either the node name is not in the right place or it contains
nonalphanumeric characters.

‘

|
|
,

%
*

NFT:

Network

Table

4-3:

NFT

Transfer

Error

Utility

Messages

(Cont.)

?NFT -- MORE THAN ONE INPUT NODE SPECIFICATIO
N

JNFT

NODE

NAME

name

was

RMS

error

GIVEN

given

software

The
ZNFT

SWITCHES
switch

sign.

TOO

MANY

OUTPUT
file

FILE

name

are

line.

Quote

the

retype

the

QUOTE

odd

retype

the
the

the

left

side

switch

operate

on.

was

given

the

error

one

persists,

side

given

the

left

than

one

egual

side

equal

characters

spelling

quote

must

command.

characters

paired.

(=).

the

command

COMMAND

the

command

keyword

command

switch

commandg.

spelling

sign

CHARACTERS

number

UNRECOGNIZABLE

Check

SPECIFICATIONS

was

contains

UNRECOGNIZABLE

- Check

?NFT

side

SIGNS

typed

UNMATCHED

There

JNFT

RMS.

specialist.

/IDENTIFY

one

right

FAILURE

initializing

/IDENTIFY

MANY

name

/IDENTIFY

one

than

the

/IDENTIFY

the

MANY

TOO

SPECIFICATION
node

than

command

FOR

for

INITIALIZATION
occurred

sign.
?NFT

one

TOO

equal
?NFT

NODE

than

sign.
NO

call

OUTPUT

node
--

ONE

type

name

?NFT

THAN

node

one

asie

MORE
cannot

equal
?NFT

than

You

?NFT

type

sign.

cannot

equal

You

(see

Table

4-1)

and

SWITCH

the

(see

Table

4-2)

and

File

Chapter

NETCPY:

Network Copy Between Devices

The NETCPY utility allows you to copy all of the information on a
DECtape, magnetic tape, flexible diskette, or disk from one DECnet/E
node to a like device on another DECnet/E node. See Figure 5-1. One
of the nodes must be the local node. NETCPY is a DECnet/E utility;

there is no general DECnet utility to copy the contents of devices

between

nodes.

BANGOR

TRNTO

$ RUN DECNET$:NETCPY

#MT3:=TRNTO: MT2/FC
Node::TRNTO

KANSAS

PPN:: 120,153
Password:

System Password:

100 BLOCKS TRANSFERRED
200 BLOCKS TRANSFERRED
TIME TO COPY =5.31217 MIN

BOSTON

DENVER

COPY COMPLETE

DALLAS

NYC
MK-02314-00

Figure 5-1:

NETCPY Copies an Entire Device from One DECnet/E Node to

Another

DECnet/E Node

NETCPY:

Network

protect

Copy

devices

information

for
informatio
and
n
proceed.
remote

you

You

run

can

node

(see

NETCPY

unauthorized

use,

specified remote node.
checks its validity before

Then

Running

from

Devices

the

DECnet/E

preparations

Between

use

Chapter

NETCPY

the

mount

from

TLK

you

utility

tapes

must

supply

ask

other

the

operator

the

preliminary

2).

any

log-in

NETCPY prompts for the
allowing the transfer to

terminal

DECnet/E

system

typing:

$SRUN DECNETS:NETCPY
NETCPY

V4.0

RSTS

¢ command

V9.3

DECNET/E

described

Node:
PPN:

Password:

System

Password:

where:

$command:

PPN:

Password:

General

The

Password:

Format

general

following

the

Project-Programmer

the

remote

the

use

the

NETCPY

format

the

you

System

section.

Number

you

use

log

node.
l4-alphanumeric

log

system

the

password

character

remote

(if

password

node.

required)

Command

the

NETCPY

command

is:

{dstnode::]dstdevice:[dstsw}m[srcnode::]srcdevice:{/FC}[srcsw]

{ /NC}
where:

dstnode::
is

the

node

one-

copied.

omit

the

dstnode

local

which
The

node

node.

six-character
the

not

contents
name

name,

the

Dstnode

must

NETCPY

local

must

5-2

node

name

assumes

device

begin with

node,

the

then

your

the
are

letter.

local

srcnode

DECnet/E

destination
to

node.

must

you

1If

the

NETCPY:

Network Copy Between Devices

dstdevice:

is the destination device.
MTn:

Magnetic

DKn:

Disk

DXn:
DTn:

The

tape

unit

Allowable devices are:

Flexible diskette unit n

unit n
DECtape unit

destination device must

the

same

type

srcdevice. You can use NETCPY to copy larger disks but
the speed of most transmission lines usually makes such
operations impractical for remote transfers.

dstsw

is either
See

the

or both of

following

the optional /PA and /DE switches.

section.

separates the destination description from the source
description.
srcnode:

is the node from which the information is to be copied.
If you omit srcnode, NETCPY assumes your local node.
I1f srcnode is not the local node, then dstnode must be
the local node. Srcnode must be a DECnet/E node.
srcdevice

is the source device.
specified

that you
/FC

You must specify the same device

for dstdevice.

/NC

specifies whether you want to copy (/FC) or verify only
(/NC). You must specify one of the switches, which are

described

in the

following

section.

SICcsw

one

the

optional

switches:

/VERIFY
/BLOCK

/PARITY
/DENSITY

See

the

following

section.

5-3

NETCPY:

Network

NETCPY

Switches

Table

5-1

following

Copy Between Devices

lists

the

discuss

seven

these

optional

NETCPY

switches.

The

sections

switches.
Note

can

two

characters.

NETCPY
WG,

the

first

Switches

WSS

NGNS

SEMS WOA

SRS

SRR

NANEN

/BL[OCK]

Specifies

the

block

/DE[NSITY]

Specifies

the

density

J/FC

Specifies

that

/HE[LP]

Displays

help

Specifies

/NC

switches

device

you
for

DRGNS

WENGE

NSNS

ORI

NERR RDRWN

size

for

want

you

not

verify

HOENE

NGRS

GRS

tape.

tapes.

device.

want

copy

the

device.

Specifies the parity for a magnetic tape.

/VE[RIFY]

Specifies

/PA[RITY]

soidmni
i

WGGR BRISK

NETCPY.

want

magnetic

copy

information

WSS

magnetic

that

but

NETCPY

183
o
i

all

5-1:

abbreviate

evonks o

Table

You

that

information
B

on
B

you

want

verify

the

a device.

—————,

NETCPY:

Network Copy Between Devices

#, /BL[OCK]:n Switch
Use the /BLOCK switch to specify the block size that NETCPY uses to

allocate buffers for magnetic tapes written with nonstandard record
Block sizes must
The default block size is 2048-byte blocks.
sizes.
and writes
srcdevice
buffers
NETCPY
bytes.
512
of
be in multiples
For example:
size.
block
specified
the
at
and/or verifies dstdevice
$#MT0:=BOSTON: :MT1:/BL:4096/FC

This command causes NETCPY to copy magnetic tape unit 1 at node BOSTON
to magnetic tape unit 0 at the local node in 4096-byte blocks.

/DE[NSITY]:n

Switch

Use the /DENSITY switch to set the density for either source or
Depending on the tape drive you use, you
‘destination magnetic tapes.
can set the density for either 800, 1600, 6250, 6667, or 8000 bpi.
For

example:

$MTO: /DENSITY:1600=BOSTON: :MT1:/DENSITY:800/FC

NETCPY reads a 9-track magnetic tape on unit 1 at node BOSTON at 800
bpi and writes in 9-track format on magnetic tape unit 0 at the local
node

1600

bpi.

NETCPY:

/FC

Network

Between

Devices

Switch

Use

the

/FC

the

/FC

switch,

both

switch

switches,

NETCPY

Copy

lists

the

time

you

NETCPY

took

error

the

copy

total

When

copy.

the

tape.

the

device

include

returns

for

and

For

must

progress

units

transferred.

request

then

the

100-record

you

(see

100-block

copy

switch.

message

the

number

1If

/NC

blocks

sign

(#)

not

1If

Table
units

omit

5-2).
for

complete,

include

you

disk

NETCPY

and

lists

records

example:

SRUN DECNETS:NETCPY
NETCPY

V4.0

RSTS

V9.3

DECNET/E

$BOSTON: :DT0:=DT2:/FC
PPN:1,222

Password:

100

BLOCKS

TRANSFERRED

200

BLOCKS

TRANSFERRED

300

BLOCKS

TRANSFERRED

400

BLOCKS

TRANSFERRED

500

BLOCKS

TRANSFERRED

TIME

COPY

COMPLETE

BLOCKS

/JHE[LP]

Type

COPY

5.11111

TRANSFERRED

MIN
578

Switch

/RELP

NETCPY.

For

response

the

number

example:

SRUN DECNETS:NETCPY
NETCPY

V4.0

RSTS

#/HE

(Help

Display)

V9.3

DECNET/E

prompt

get

help

about

NETCPY: Network Copy Between Devices

/NC

Switch

switch
Use the /NC switch to reguest no copy. YOu always useIf this
not
do
you
run.
y
with the /VE (verify) switch for a verify-onl
the
after
include the /NC switch you must include the /FC switcht by itself.
srcdevice specification. The /NC switch has no effec
J/PA[RITY]:n Switch

to set the parity
Use the /PARITY switch when copying magnetic tapes
y can be either
parit
for either the source or destination device. The the syste
m manager
ODD or EVEN. The default is whatever was set by
for that device at the specified node. For example:
$#MTO: /DENSITY:1600/PARITY: EVEN=BOSTON: :MT1:/DENSITY:800/FC

JVE[RIFY]

Switch

h to verify
Use the /VERIFY switch with either the /FC or /NC switc
d exactly. NETCPY
that the information on a device unit has been copie
time as the
performs a block-by-block verification, taking as much
copies the
first
Y
NETCP
h,
copy operation. When you use the /FC switc
device
n
natio
information from the source device to the desti used with ,theand/NCthen
sends the information back and verifies it. When
switch, NETCPY only verifies the information.

5-7

NETCPY:

NETCPY

Network

lists

Copy

the

Between

progress

Devices

the

verification

procedure.

For

example:

SRUN DECNETS :NETCPY
NETCPY

V4.0

RSTS

V9.3

DECNET/E

#BOSTON: :DT0:=DT2:/NC/VE

PPN:1,222

Password:
BEGINNING

100

VERIFICATION

BLOCKS

VERIFIED

200

BLOCKS

VERIFIED

300

BLOCKS

400

BLOCKS

VERIFIED
VERIFIED

VERIFICATION

OUT

492

COMPLETE

BLOCKS

PASS

BAD

BLOCKS

VERIFIED

the

information

decimal
The

number

numbers

disk

and

has

printed

DECtape

not been

blocks

correspond

blocks

copied

records

512

magnetic

bytes.

#DXI:#BOSTON::DXZ/FC/VE
PPN:102,50
Password:

100

BLOCKS

200

BLOCKS

300

TRANSFERRED
TRANSFERRED

BLOCKS

TRANSFERRED

400

BLOCKS

TRANSFERRED

TIME

COPY

COMPLETE

BLOCKS

COPY

7.56667

TRANSFERRED

BEGINNING
THE

BLOCKS

MIN

492

VERIFICATION

FOLLOWING

PASS

ARE

BAD

31
89
100

BLOCKS

200

BLOCKS

VERIFIED

300

BLOCKS

VERIFIED

400

BLOCKS

VERIFIED

VERIFICATION

COMPLETE

OUT

492

VERIFIED

BLOCKS

BAD

VERIFIED

correctly,

BLOCKS

NETCPY prints the
inconsistencies appear.
tape record numbers and to

in which
For

example:

NETCPY: Network Copy Between Devices

NETCPY

Error Messages

Table 5-2
Table 5-2:

lists the NETCPY error messages.
NETCPY Error Messages

| CANNOT SPECIFY BOTH /FC AND /NC /FC or /NC switch, but not both.
You must specify either the
|
|
| ERROR IN SPECIFYING DENSITY
The density you specified is not one of the valid values of
|
|
800, 1600, 6250, 6667, 8000, or DUMP.
|
|
|

ERROR IN SPECIFYING PARITY

The parity you specify must be either ODD or EVEN.
|
|
| /FC OR /NC MUST BE SPECIFIEDthe /FC or /NC switch.
You must specify either
|
|
| ILLEGAL BLOCK SIZE
The block size you select must be a multiple of 512.
|
|

| INVALID NODE SPECIFICATION
Either the nodes you specified did not include the local node,
|
or NETCPY did not recognize the node name.
|

i\ MUST HAVE SAME TYPE DEVICE

|
z
|
|
|

Both the source device and the destination device must be
either MTn: (magnetic tapes), DTn: (DECtape), DXn: (flexible
diskettes),

or DKn:

(disks).

-- ABORT
(NSP COMMAND)

|
|
|
|
|
|

|
|

|
|
|
|
|
|
|
|

|
|
1

5
|
s
|

NETCPY sets up a logical link to the remote node to effect the }
|
transfer requested. If any network error occurs during
.
message
this
s
display
|
and
program
the
execution, NETCPY aborts
execute
to
trying
|
was
NETCPY
one
The NSP command shown is the
to
trying
was
|
NETCPY
if
,
when the error occurred. For example
the
s
display
i
receive a message from the remote node, NETCPY
"
|
message "RECEIVE NETWORK ERROR -- PROGRAM ABORT.

|
|
|
|
|
|
| TYPE /HE FOR HELP
NETCPY does not recognize the command you typed. Use the /HE
|
switch for help.
|

5-9

i
|
|
3

Chapter

NETOFF:

Network Shutdown Utility

The NETOFF utility lets you shut down your network in an orderly
It
fashion without shutting down the entire RSTS/E operating system.
causes a gradual shutdown rather than an immediate disconnect. You
must have the SHUTUP privilege to use NETOFF.

NETOFF performs a similar operation to the NCP SET EXECUTOR STATE SHUT

command (see the DECnet/E System Manager’s Guide). Both permit
existing logical links to complete before ending network operations,

but only NETOFF warns users that the network will close down in some

determined period of time. This gives network users an opportunity to
respond to the warning message by finishing up network processing or
by requesting that network operations be extended.

You can run NETOFF from any terminal in a DECnet/E system by typing:
S RUN DECNETS:NETOFF

NETOFF responds by asking how many minutes it should wait before new
network links are prohibited (that 1is, until it effects.a SET EXECUTOR

STATE SHUT command) and how many minutes it should wait until actual

network

shutdown.

After this, the following sequence of operations occurs:

NETOFF broadcasts a message to all system terminal users.
For

example:

THE NETWORK IS SHUTTING DOWN IN [variable] MINUTES

NETOFF then stops execution for the appropriate number of

minutes, as determined in the dialogue. When it resumes
execution, it sends the SET EXECUTOR STATE SHUT message toO
If no logical links are open, NSP terminates network
NSP.
Otherwise, NSP
operations and the NETOFF program completes.
but allows
links,
logical
new
any
of
prohibits the forming
links.
existing
on
continue
normal operations to

NETOFF:

Network

NETOFF
the

Shutdown

again

period

execution,

Utility

stops

before
it

execution,
final

sends

the

NSP

aborts

"Set

this

point,

sends

links

open.

Network

network

Abort

NSP

then

any

down

Finally,

NETOFF

sends

and displays

SHUTDOWN

a
the

STOP

command

following

the

off"

logical

local

remainder

When

message

links

the

message

thus

Event
on

the

You

can

and

ending

Logger
terminal:

COMPLETE

the

SET

shutdown

interrupt

this

CTRL/C.

EXECUTOR

STATE

procedure

operations.

sequence

NETOFF

and

resumes

point

execution

command

resuming

any

NSP,

normal

and

sends

aborting

network

with

Note

pressing

resumes

programs

Transport,

operations.

program

for

state

existing

message

shuts

time

shutdown.

executor

NSP.

this

network

the

APPENDIX

NSP REASON CODES FOR CONNECT REJECT AND LINK ABORT

Table A-1 lists the Network Service Protocol reason codes and their
meanings.

associated

NSP Reason Codes

Table A-1l:

— e ———— —— - = +
$———————— e
Reason
|
Code
|

tomTmmT YoTTTTTTTTTTTTTTTTTTTTTTI T ¥

| 000

% 001
i 002
003

% No error -- user-initiated reject or abort

i Resource allocation failure
| Destination node does not exist
| 2 Node shutting down

004

i Destination program does not exist

005

Invalid destination name or source name field
full

006

Destination program’s queue

007

Unspecified error

0C8

Third party aborted logical

009

User-initiated

016-020

Reserved

021

Tnvalid destination address in Connect Initiate
Message

condition

link

abort

2
%
§

NSP

REASON

CODES

FOR

NSP

Reason

Table A-1:

CONNECT

REJECT

Codes

AND

LINK

ABORT

(Cont.)

mmnmm—mmmmm”ww

mmmwmmwm“m‘u—u

mmn—””mnwv—wmm

u“_v—--nkummmm

”

“m_mmmm-—nwwm'u“mmwmmwwmwwum

wmmmmm“”—nmmmmmm—m-mmm“nm‘fi

Invalid

destination

address

Connect

Confirm

Message

023

Source

address

Connect

024

Flow

zero

Confirm

control

Link

Connect

Initiate

violation

Service

invalid

Reserved

| 032

Too

many

connects

node

033

Too

many

connects

destination

034

Access

count

program

permitted

omm—

5. v

request

Message

% 025-031

not

Message

035

link

036

Invalid

accounting

037

Segment

size

038

User

039

040

Flow

Logical

path

too

aborted,
to

mismatch
\41,51,»“%

information

small

timed

out,

canceled

data

link

node

control

request

041

services

failure

count

current

received

when

zero

link

(cannot

recognize

destination

system

Disconnect

address)
Confirmation

from

remote

message

Image
R

RRNS

GRS

VOGN

GGEAC

data
WGSRC

WSMUS

GGG

field
S

SNSOS

SWEN

GHSS.

WMWS

too
GOSN

WRSW

long
GO

JREGH

GIEN

NSV

SENGR

ROWAL

BROGN GNRRR

SRS

Goee

BRORe

WRGOR

MGRGY

NAOR WGNGS EWNEN mAGN

GEWIN

WOW

Wew

WEHee SNOR

SRS

APPENDIX

ERROR

This

appendix

using

the

contains

Network

appear

for

(RMS),

used

File

conditions

violations

by
of

NFT
the

across

NFT

Messages

NFT prints

the

and

the

GENERATED

non-NFT

error

Transfer

FAL

Access

RMS

messages

(NFT)

diagnosed

Data

transfers

Error

MESSAGES

the

local

Protocol

AND

DAP

that

can

appear

while

messages

can

program.

These

Record

Management

input
(DAP),

and

output,

Services
or

for

used

remote

response

detected

file

network.

from RMS-11

following

error

message

RMS-11

errors:

?NFT

RMS

ERROR

nnnnnn

The

errors that can occur when you use NFT should be understandable,
such as error 176440, File not found.
However, Table B-1 lists all
possible RMS errors.
Some descriptions will be obscure to all but
those familiar with RMS.
If you get one of these errors repeatedly,
call a DIGITAL Software Support Specialist and report the error.
Note

The following
Version 1.8.
for

list reflects errors generated by RMS
See the RMS-11 MACRO-11 Reference Manual

descriptions.

ERROR

MESSAGES

Table

B-1l:

GENERATED

RMS

Error

RMS

AND

DAP

Codes

Fmm e
—— - e
— -

Octal
Value

(nnnnnn)

Description

o
——— - e e
-

177760

Operation aborted: Stack save area exhausted or in-core

data

177740

177720

structures

Files-11

ACP

corrupted.

could

not

access

the

file.

File activity precludes action (for example, attempting
.~

file

with

outstanding

asynchronous

record

operation).

177700

Bad

area

identification

allocation

XAB

(out

number

(AID)

field

sequence).

177660

% Invalid value in alignment boundary type (ALN) field of

177640

| Value in allocation quantity (ALQ) field in FAB (or

allocation

XAB.

-~ allocation XAB)
-

SEXTEND

exceeds maximum or,

operation,

equals

during an explicit

zero.

177620

. Records in a file on ANSI-labeled magnetic tape are
~

variable

177600

Invalid value

length

allocation

177560

Read

error

177530

Invalid

177520

Write

error

177500

Bucket

size

maximum.

177440

not

in ANSI-D

allocation

format.

options

(AOP)

field

XAB.

Invalid operation at AST level: Attempting
synchronous operation from an asynchronous
operation completion routine.

177540

177460

but

file

header

to 1ssue
record

attributes.

ID.

file

(BKS)

header

attributes.

field in FAB contains value

exceeding

Bucket size (BKZ) field in allocation XAB contains

value

exceeding

maximum.

| Block length (BLN) field in a FAB, RAB, or XAB is
incorrect.

ERROR

Table

B-1:

RMS

Error

Codes

MESSAGES

GENERATED

RMS

AND

DAP

(Cont.)

tmm - o - +

Octal
i

Value

(nnnnnn)

Description

Fmm——————— e
e LR

177430

Beginning

magnetic

tape

177420

'
-

Private

177400

Private

177360

177300

detected

$SPACE

operation

buffer

pool

address

|
|

buffer

pool

size

not

double

multiple

word

boundary.

Internal error detected in RMS-11. No recovery
contact

software

specialist.

% Cannot connect RAB (only one record access stream
-

177320

file

file.

pcssible;

177340

permitted

for

sequential

files).

SUPDATE attempting to change a key field that does not

have

Index

been

the

change

file

bucket

corrupted.
Moving

check-byte

mismatch.

Recovery can be

disk

process

attribute.

pack

The

bucket

has

attempted by:

another

device

and

trying

RMSCNV

|
the

again.

Recreating

|
|
|

file

using

either

RMSIFL

utility.
0o

Restoring

file

from

last

backup.

177260

: SCLOSE function failed.

177240

Invalid COD field in XAB or XAB type 1s invalid for the %
-~

organizaticn

operation.

177220

Files-11 ACP could not create file.

177200

? No current record: Operation not immediately preceded

;

177160

a successful

Files-11

ACP

Invalid

area

SGET

deaccess

SFIND.

error

during

SCLOSE.

177140

177120

numker

DAN

field

key

definition

XAB.

Record accessed by RFA access mode has been deleted.

ERROR

MESSAGES

Table

B-1:

b ——————— o

GENERATED

RMS

Error

RMS

Codes

AND

DAP

(Cont.)

e e
— —

Octal
Value

(nnnnnn)

Description

tmmmm————
-o

e e
— — — —

177100

aAny
0o
o

of the following:
Syntax error in device
No such device.

name.

Inappropriate device for operation (for example,
attempting to create an indexed file on magnetic
tape).

177070

Files-11 ACP could not write bucket. RMS-11 deferred
the I,/0 operation until it needed the I/0O buffer for
another bucket because the user program specified
deferred writes.
in

error

directory

name.

177060

Syntax

177040

Dynamic memory exhausted:

177020

Directory not

177000

Device

not

176770

Device

positioning

176760

DTP

176740

Duplicate key detected,

176720

Files-11 ACP enter

function

176700

Environment error:

Operation or file organization not

or private buffer pool.

space pool

not

field

set

found.

ready.

invalid

for

specified

Insufficient space in central

error.

(STV=EXAB).

one or more

in ORGS

"duplicates allowed"

attribute

key fields.

failed.

macro.

176660

End

file.

176640

Expanded string area in NAM block too short.

176630

File

expiration date not

176620

File

extend

176600

Not a valid FAB: BID field does not contain FBSBID.

reached.

failure.

ERROR

"Table
dmm

B-1l:

——

RMS

Error

Codes

MESSAGES

GENERATED

RMS

AND

DAP

(Cont.)

L
T T T
———— +

Octal

Value

(nnnnnn)

|
i
|

fmm————— i

Description

T ——— +

176560

Any

the

following:

Record
field

operation
of

Invalid

FBSPUT

FAB

attempted was
open

contents
not

present

not

declared

FAC

time.

FAC
in

field.

FAC

for

|
SCREATE

operation.

176540

% File already exists (attempted SCREATE operation).

176530

176520

Invalid

file

Invalid

combination

definition

176500

1ID.

XAB

"changeable

(for

values

example,

in
"no

FLG

field

duplicates"

key

and

keys").

é File locked by another user: Cannot access the file

because

176460

Files-11

ACP

176440

!
.

File

found

176420

; Syntax error in file name.

176400

Invalid file options.

176370

System

error

code).

sharing

not

specification

SFIND

function

during

cannot

met.

failed.

|
;

S$OPEN.

FNA/DNA

string

parse

(STV

176360

Device full: Cannot create or extend file.

176340

176320

176300
176260

176240

system

Invalid area number in IAN field of key definition XAB.

Index not initialized. This code can only occur in the

STV

Invalid IFI field in FAB.

Maximum

XABs

exceeded

XABs

present

field

SINIT

when

number

STS

contains

(254)
or

during

SINITIF

key

multiple

ERSRNF.

definition

summary,

operation.

macro

call

never

allocation

protection,

date

|
|

;

issued.

ERROR

MESSAGES

Table

B-1l:

Fmm

—

Octal

GENERATED

RMS

Error

RMS

Codes

AND

DAP

(Cont.)

e e

Value
(nnnnnn)

Description
e

e oo

cme

tmm—m——————
- e

file.

Attempting

$SERASE

Issuing
or

tape

mmem

Gee

SEXTEND

operation

file.

block

SWRITE)

owsmts

include:
operation

nonsequential

magnetic

Examples
STRUNCATE

MeoMASE

s
d

operation.

Attempting

mesdot

mode

operation

stream

not

(for

example,

connected

for

SREAD

block

Issuing a record operation (for
to a stream connected for

v
a s

operations.

o
i

Invalid

176220

example, S$SGET,
mode

SPUT)

block

operations.
176200

Invalid
count

176160

record

encountered

sequential

file:

Invalid

field

field.

Invalid

(field

may

internal

have

stream

issued

for

stream.

been

identifier

altered

(ISI)

user)

RAB

S$SCONNECT

never

176140

| Key buffer address (KBF) field equals 0.

176120

é Record identifier (the 4-byte location addressed by
-

KBF)

for

random

operation

relative

file

1is

negative.

Invalid key of reference (KRF) in RAB:
o

During

random SGET or S$FIND operation,

During

SCONNECT or

S$REWIND.

this

case,

ERSKRF

record operation
SREWIND.

not

é 176040

f Invalid area number in LAN field of key definition XAB.

: 176020

é Magnetic tape is not labeled in accordance with ANSI
-

standards.

176000

Z Logical channel busy.

175760

é Invalid value in logical channel number (LCH) field of
-

FAB.

Sppppon—| S

file)

(indexed

large

iy S

or too
file).

equals zero
4 (relative

Key size
egual to

~
~

176060

is returned for the first
following the SCONNECT or

176100

ERROR

Table
e

B-1:
T

RMS
—"

Error

Codes

Invalid

value

In-core

data

extend

corrupted.
when

STS

175700

Files-11

175660

Either

e
e
wa
emmemny

LOC

field

code

containing

(for

can

unused

allocation
example,

only

occur

not

Record

File

Odd

mark

number

SCREATE

identifier
to

file

for

field

deletion.

specified

size

format
is

KBF)

exceeds

file

created.

field

contains

fixed,

negative

for

random

maximum

record

during

relative.

Name

Block

SERASE.

SCREATE,

file.

file

when

(MRS)

contains

relative

(pointed

relative

organization

address

SOPEN,

STV

following:
record

record

buffers)

the

XAB.

I/0

extent.

ERSARBO.

during

number

Maximum

area

could

the

Record

3o
s
s

ACP

”mmwmmm“*mmm”mmmm

contains

operation

DAP

mmmmmmmmm“”mm“w”m

structures

Maximum

This

value

address

(NAM)

field

FAB

Not at end-cf-file: Attempting a SPUT operation to a
sequential

175560

AND

m“mmwmmmmmm“mmw“”m“m

175740

175600

RMS

(Cont.)

Hnmmmwmmmmmmm“mm"mmm

175620

mmwm”mmmmmmmmmmmmmm”

Attempt

175640

GENERATED

”m”mmmm“mmmmmmmmmm““

175750

175720

MESSAGES

Cannot
room

file

when

allocate

space

stream

internal

pool

while

index

not

positioned

descriptor:

attempting

EOF.

Insufficient

open

1ndexed

file.
175540

primary

indexed

175520

SOPEN

175500

XABs

XAB

Invalid

XAB

present

during

SCREATE

chain

failed.
not

Allocation

or
175460

deflnltlon

function

(or

key

file.

densely

another

type

XAB

file

order:

definition

ascending)

allocation
value

correct

key

XABs

not

key

definition

ascending

order.

intervenes

sub-chain.
organization

B-7

(ORG)

field

FAR.

GENERATED BY

ERROR MESSAGES

Table

B-1l:

RMS

Error

RMS AND DAP

Codes

(Cont.)

- =
— e —
== e e
e

Octal

Value

Description

(nnnnnn)

———— i —— o ————
—
e e(S

175440

Error in file'’'s prologue:

can be

|
§

recovery

attempted by:

o
o

Moving disk pack to another device.
Recreating file using either the RMSIFL or RMSCNV

Restoring file from latest backup.

utility.

field in key definition XAB contains

175420

Key position (POS)

175400

.
|
~

File header contains bad date and time information
(retrieved by RMS-11 because a date and time XAB 1is
present during an S$OPEN or S$SDISPLAY operation). File

. 175360

a value exceeding maximum record size.

may be

{

175340

175320

operating

system.
,

' Not a valid RAB: BID field does not contain RBSBID.

Either of the following:
o

‘

o
175300

corrupted.

Privilege violation: Access to the file denied by the

File is corrupted;

Invalid values in record access mode (RAC)

;

|
|

RAB.

Illogical value in RAC field (for example, RBSKEY

with a

Either

field

sequential

the

file).

following:

1Invalid values in record attributes (RAT) field of

FAB during SCREATE.

Illogical combination of attributes (for example,
FBSCR and FBSFTN) in RAC field during SCREATE.

175260

. Record address (RBF) field in RAB contains an odd

% 175240

§ Files-11 ACP error:

address

175220

(block mode access only).

1In record processing -- read failure on file

block.

In block

I/0 -- VBN=0.

. Record already exists: During a $PUT operation in

random mode to a relative file, an existing record

found in the target record position.

ERROR

Table

B-1l:

RMS

Error

Codes

MESSAGES

GENERATED

RMS

AND

DAP

(Cont.)

$-—mmm—————
-e
e -+

Octal

Value

(nnnnnn)

Description

Fmmmm—————— e
e+

175200

§ Invalid RFA in RFA field of RAB during RFA access.

175160

é Either of the following:

Invalid

record

SCREATE.
Specified

format

in RFM field of

FAB during

record

format

invalid

for

file

organization.

175140

1 175120
|
i
|

175100

2 Target bucket locked by another task or another stream
'

the

same

program.

%
|
|
!

§ Files-11 ACP SREMOVE function failed.

. Record identified by KBF/KSZ fields of RAB for random

.
-

SGET or SFIND operation does not exist in relative or
indexed file (for indexed files only, STV may contain
ERSIDX). Record may never have been written or may have

been

- 175060

§~$FREE operation issued but no bucket was locked by

s
|

deleted.

stream.

175040

Record options (ROP) field contains invalid values or

175020

§ Error while reading prologue.

;

175000

Invalid RRV

may

Record stream active:
attempting to issue a

174760

illogical

has

174740

combination

values.

record encountered

indexed

file.

File

corrupted.

request

size

In asynchronous environment,
record operation to a stream

Record

not

that

outstanding.

specified

equal

in RSZ

of RAB during

record

size

(MRS)

S$SPUT or

specified
|

RSZ

o
o

RSZ does not equal MRS (for fixed format records).
RSZ not large enough to contain Primary Key of
indexed file.

SUPDATE operation to a

Current

sequential

Record

for

file on disk.

;
|

ERROR

MESSAGES

Table

B-1l:

GENERATED

RMS

Octal

Value

(nnnnnn)

Error

RMS

Codes

AND

DAP

(Cont.)

%
;
Description

‘

ee
-+

174720

Record

too

big

entire

record

area

the

for

retrieved

(UBF/USZ).

current
is

user’s

Note

context
updated

buffer:

that

of
as

S$GET
this

the

could

operation

error

stream.

possible

174710

RRV

174700

§ During SPUT operation, key of record to be written is

update

error

not

equal

(and

RAC

field

user

operation

much

had

stream’s

completely

destroy

the

context

moved

the

not

move
work

1is

does

Rather,

not

user

successful

and

RMS-11

the

been

record

buffer.

insert.

greater

contains

than

key

record

RBSSEQ).

174660

|
|

FBSWRI specified for sequential file).

174640

Invalid SI1IZ field 1in key definition XAB during SCREATE

size).

During

174620

Illogical value in SHR field of FAB (for example,

(for example,

specified

asynchronous

that

the

stack

only

occur

size

record

exceeds

maximum

operation,

tooc

big

the

STV

field

saved.

when

STS

RMS-11

has

This

code

contains

174600

? System directive error.

174560

. Index tree error: Indexed file is corrupted.

174540

174520

174440

174430

found

can

ERS$ABO.

Syntax

characters

Invalid

174500

record

error

file

address

UBF

contains
0,

UBF

not

Invalid

user

example,

USZ

Invalid

does

not

VOL

(for

example,

than

word

contain

(UBF)

field

block

mode

RAB:

size

contains
field

buffer

aligned

buffer

|
l

user

type

specified).

(for

(USZ)

access

field
in RAB

only).

(for

0).
allocation

?
XAB

(for

example,

0).

VOL

; Wildcard encountered during FNA/DNA string parse.
B-10

ERROR

~, Table

B-1l:

Error

Codes

———— e

Octal

RMS

MESSAGES

GENERATED

RMS

AND

DAP

—— +

(Cont.)

ettt

Value
(nnnnnn)

Description

. 174420

File write error.

174410

é Device 1s write locked.

= Error while writing prologue.

174400

Di
e
T+

174360

XAB field in FAB (or NXT field in XAB) contains an odd

address.

Extraneous

174340

NFT

Error

NFT

prints

TM NFT/FAL
?2NFT

The

error.

Messages

the

from

DAP

value

ERROR

gives

The

nnnn

Macro

(aa)

Field

Table

B-2

error

during

message

violating

FNA/DNA

string

parse.

the

Data

response
Access

error

Protocol:

macro
gives

or
the

functional
micro,

group

reason

specific,

for

reason

the
for

error.

lists

Values

the

possible

values

for

the

macro

(aa)

field.

the

result

Note

This

list

violation

DIGITAL

reflects

Network

Functional

aannnn

the

value

detected

DAP

following

communication,
--

field

the
DAP

errors
Version

Architecture,

Specification,"

generated
5.6,

"Data

released

described

Access
in

the

Protocol

October,

1980.

the

ERROR MESSAGES GENERATED BY RMS AND DAP

Table

B-2:

Macro

(aa)

Field

Values

ee
e e
o-+

Octal

Value

(aa)

Name

t—————— o

Unsupported

Operation

Returns

success.

This

support

the

File

|
|

Open

Transfer

Error

Transfer Warning

Access

Format

Termination

Errors

file

that

and

occur

before

file

not

occur

before

after

opening

closing

with

complete

Error
not

that

parsing

message.

Field

message

meant

mutually

exclusive

are

set,

undefined

bit

out

range,

N
|
|

16-17

of
a

DAP

synchronization.

User-defined

field.

set,
or

field.

[

Format

invalid.
are

f
l

|
|

message

|
3

that

13-15

correct.

bits

example,

file.

terminating

Sync

success.

associated with

access

;

opened.

| Errors

request.

but

Invalid

that

not

does

For operations on open files,
indicates the operation completed,

specified

DAP

|
|

successfully

indicates

Reserved.

|
|

that

implementation

}

Errors

progress.

information

Meaning

e oe+

Successful

Pending

received

For
to

{
be

field
invalid

[

value
string

out

[

[
|
{

Reserved.

|
STATUS

message

MACCODE

|
{
|

+—————— e ittt e
e
+
el

B-12

ERROR MESSAGES

Micro

(nnnn)

GENERATED BY

RMS

AND

DAP

Field Values

Table B-3 lists the micro (nnnn) values for use with macro (aa) values
of 2, 10, and 11 octal.
These refer to the macro Unsupported, Format,
and

Invalid

categories.

Note

Micro (nnnn) Format:
message type number.
field

Table B-3:

Bits
Bits

6-11 specify the DAP
0-5 specify the DAP message

number.

Micro

(nnnn)

Field Values

———————— e - +

|
§

Code
(Octal)

|
|

1
1

Reason

o ————
-ee
--+

Miscellaneous

errors

--+

|
|

00
00

00
10

|
|

Unspecified DAP message error
DAP message type field (TYPE)

(catch all)
error

l
t

$m——m———— e
+

CONFIGURATION message errors by field:

4-—m—————— e
———— +

01
01

00
10

|
|

Unknown field
DAP message flags

01 12

Length field

01
01

13
14

01
01
01
01
01
01
01

22
23
24
25
26
27
30

|
|

Data

field (FLAGS)
stream identification field

(LENGTH)

|
]

(STREAMID)

Length extension field (LEN256)
Bit count field (BITCNT)

Buffer size field (BUFSIZ)
| Operating system type field (OSTYPE)
" File system type field (FILESYS)
| "DAP version number field (VERNUM)
|| ECO version number field (ECONUM)
| USER protocol version number field (USRNUM)
| DEC software release number field (SOFTVER)
| User software release number field (USRSOFT)
| System capabilities field (SYSCAP)

|
|

|
|
|
|

|
|

ERROR

MESSAGES

Table

B-3:

GENERATED

Micro

+—mmm———— e

(nnnn)

RMS AND

Field

Values

p—— +

(Octal)

tmmm

(Cont.)

Code
.

DAP

Reason

- Pe+

ATTRIBUTES

message

errors

field:

tmmm
e
——— e kT
T
+

Unknown field
DAP message flags

Data

Length

field

Length

extension

Bit

System

Attributes

Data

02
02

22
23

Record

Block

Maximum

Allocation

Bucket

size

Fixed

control

Maximum

Run-time

system

Default

extension

File

options

Byte

size

Device

stream

count

field

(STREAMID)

(LENGTH)

field

menu
field

(LEN256)

(SYSPEC)

field (ATTMENU)
(DATATYPE)

File organization field (ORG)
- Record format field (RFM)
attributes

size

field

Spooling

Longest

Highest

First

Starting

field

(MRS)

;

quantity

field

(ALQ)

field

(BKS)

area

field

(FSZ)

(MRN)

(RUNSYS)

quantity

field

(DEQ)

(FOP)

(BSZ)

device

%
field

(DEV)

characteristics

record

length

virtual

block

file block

byte

LBN

size

number

field

free

(RAT)

(BLS)

characteristics

:
|

size

record

End

field

record

(BITCNT)

specific

|
|

(FLAGS)

identification

field

type

field

(SDC)

(LRL)

allocated

field

for

field

(HBK)

(EBK)

(FFB)

contiguous

file

(SBN)

———— i
et
+

ACCESS

message

errors

——— e

Unknown

DAP

message

03 11

Data

stream

Length

field

Length

extension

Bit

System

field:

kbt

field

count

flags

field

(FLAGS)

1i1dentification

field

(LENGTH)

field

specific

field

(LEN256)

(STREAMID)

;

(BITCNT)

field

(SYSPEC)

ERROR

(nnnn)

Field Values

GENERATED

RMS

Table

B-3:

——— e
e
e L+

,
.

Micro

MESSAGES

Code
(Octal)

(Cont.)

|
|

Reason

————- +

ACCESS message

errors by field:

e ee+

03
03
03
03

20
21
22
23

.
~
~

Access function field (ACCFUNC)
Access options field (ACCOPT)
File specification field (FILESPEC)
File access field (FAC)

|
1
@
|

.
-

03
03

24
25

|
|

File sharing field (SHR)
Display attributes request field
File password field (PASSWORD)

(DISPLAY)

- ——_———— e

CONTROL message errors by

field:

- ————— ettt
et e
+

04
04

00
10

- 04
04

11
12

~
-

Length

04
04

14
15

Bit count field
System specific

04
04

20
21

04
04
04
04

24
2
26
27

Unknown field
DAP message flags

field (FLAGS)
Data stream identification field
Length field (LENGTH)
field

(STREAMID)

(LEN256)

§
|

function field (CTLFUNC)
menu field (CTLMENU)
Record access field (RAC)
Key field (KEY)
Key of reference field (KRF)
Record options field (ROP)
Hash code field (HSH)
Display attributes request field

(DISPLAY)

by field:

m ee
=+

Unknown

05
05
05
05

10
11
12
13

DAP message flags field (FLAGS)
Data stream identification field
Length field (LENGTH)
Length extension field (LEN256)

05
05

14
15

~
~

|
?

e-+

CONTINUE TRANSFER message €rrors

e —————— o

|
Q
|

(BITCNT)
field (SYSPEC)

Control
Control

————— e

‘

extension

;
|

field

Bit count field
System specific

(STREAMID)

(BITCNT)
field (SYSPEC)

|
|
|
|

|
|
|

Continue

transfer

function

(CONFUNC)

AND

DAP

ERROR

MESSAGES

Table B-3:

GENERATED

Micro

(nnnn)

RMS

AND

DAP

Field Values

(Cont.)

Code

pp—p—— +

(Octal)

Reason

it
i
T
—+

ACKNOWLEDGE

message

e e

06
-

errors

Unknown

field:

;
T

field

message

DAP

06
06

11
12

Data stream identification
Length field (LENGTH)

Length

Bit

flags

System

extension

count

—— +

field

specific

field

(FLAGS)

field

(STREAMID)

(LEN256)

;
|
5

(BITCNT)

field

(SYSPEC)

;

ee+

ACCESS

COMPLETE

message

errors

field:

o
——
e et +

Unknown

DAP

message

Data

stream

Length

field

extension

Length

Bit

System

Access

field

count

identification

(LENGTH)

field

(LEN256)

complete

function

File

Checksum

field

options

field

(SYSPEC)

field

(CMPFUNC)

(FOP)

|
|

(CHECK)

DATA message

errors

field:

———— o - +

Unknown

DAP

message

Data

stream

field
flags

Length

field

Length

extension

Bit

System

10 20
21

count

field

(FLAGS)

identification

(STREAMID)

field

————— e

(FLAGS)

specific

field

(BITCNT)

07
07

flags

field

(LENGTH)

field

specific

field

(LEN256)

(BITCNT)

field

(SYSPEC)

Record number field (RECNUM)
~

File

data

field

(FILEDATA)

(STREAMID)

ERROR

Table B-3:

MESSAGES

Micro (nnnn) Field Values

Code

(Octal)

GENERATED

RMS

(Cont.)

ete

—————————————

|
1

Reason

STATUS message

errors

field:

———— o

Unknown

DAP

message

Data

stream

Length

field

Length

extension

field

count

flags

field

(FLAGS)

identification

field

(STREAMID)

(LENGTH)

field

(LEN256)

;

Bit

System

Macro status

code

field

(MACCODE)

Micro

status

code

field

(MICCODE)

Record

file

address

Record

number

Secondary

specific

(BITCNT)

field

status

(SYSPEC)

(RFA)

(RECNUM)

field

(STV)

———— et
e
ettt +

KEY DEFINITION message

|
l

field

|
+

errors

field:

———— e +

Unknown

DAP

message

field

Data

stream

Length

field

Length

extension

Bit

System

Key

definition

Key

option

count

flags

field

(FLAGS)

identification

field

specific

Data

Index

Key

12
12

Key

data

type

Root

VBN

for

Hash

algorithm

(LEN256)

field

(SYSPEC)

field

(KEYMENU)

(FLG)

quantity
guantity

segment

repeat

count

segment

position

Key

segment

size

field

(SIZ)

Key

reference

field

(REF)

Key

name

Null

key

Index

(DFL)

field

(SEGCNT)

(POS)

number

field
field

(NUL)
(IAN)

Lowest level area number field (LAN)
level area number field (DAN)

Data

(IFL)

(KNM)

character

First

data

field

this

(DTP)

key

value

bucket

VBN

field
field

field

B-17

|
E

field

fill

field

(BITCNT)

fill

bucket

:
!

field

flags

area

(STREAMID)

(LENGTH)

field

bucket

;

(RVB)
(HAL)

(DVB)

AND

DAP

ERROR

Table

B-3:

Micro

(nnnn)

MESSAGES

Field Values

GENERATED

RMS

AND

DAP

(Cont.)

Code

Data

bucket

size

Index

bucket

Level

Total

key

Minimum

field

size

root

field

(TKS)

size

record

stream

size

field

Length

extension

count

System

volume

Alignment
Starting

field

(ALLMENU)

number

field

(VOL)

(ALN)

field
field

(AOP)
(LOC)

identification

field

quantity

field

(ALQ)

identification

field

(AID)

Bucket

Default

size

field

Length

field

Length

extension

count

System

quantity

field

(DEQ)

(STREAMID)

(LENGTH)

field

Number

keys

Number

areas

(LEN256)

(BITCNT)

specific

Summary menu

(RFI)

(BKZ)

extension

Unknown field
DAP message flags field (FLAGS)
Data stream identification field

Bit

(STREAMID)

(LEN256)

(SYSPEC)

options

file

field

location

Allocation
Area

field

options

Allocation

(FLAGS)

(BITCNT)

specific

Relative

field

(MRL)

(LENGTH)

field

Allocation

field

(LVL)

identification

Length
Bit

(IBS)

bucket

Unknown field
DAP message flags
Data

(DBS)

field

(SUMENU)

field

Number of record
Prologue version

(SYSPEC)

field

(NOK)
(NOA)

descriptors field
number (PVN)

(NOR)
TM

ERROR MESSAGES GENERATED BY

Micro

Table B-3:

fmm——————— e

;

Code
(Octal)

(nnnn)

RMS AND DAP

Field Values

(Cont.)

————— e———————— +

!
-

|
|

Reason

+
—————
oe

DATE AND TIME message errors by field:

fmm——————— o

15
15
15
15

12
13
14
15

15
15
15
15
15

20
21
22
23
24

15 10
15 11

Unknown

field

DAP message flags field (FLAGS)
Data stream identification field (STREAMID)

~
~
.

|
|

Length field (LENGTH)
Length extension field (LEN256)
Bit count field (BITCNT)
System specific field (SYSPEC)

|
|
i
|

Date and time menu field (DATMENU)
Creation date and time field (CDT)
Last update date and time field (RDT)
Deletion date and time field (EDT)
Revision number field (RVN)

|
|
|
|
|

ittt +

dmm—————— e

PROTECTION message errors by field:

;

— +
- ————— o

16 11

Unknown

field

flags field (FLAGS)
Data stream identification field

DAP message

field

(LENGTH)

Length

16
16

14
15

.
'

Bit count field
System specific

16
16
16
16

20
21
22
23

~
-

Protection menu field (PROTMENU)
File owner field (OWNER)
System protection field (PROTSYS)
Owner protection field (PROTOWN)

16 24
16 25

Length extensicon field

(LEN256)

(BITCNT)
field (SYSPEC)

Group protection field
World protection field

.
-

(STREAMID)

|
|

(PROTGRP)
(PROTWLD)

— — +
fmmm—————— e
e

17
17
17

00
10
11

NAME message errors by field:

Unknown field
DAP message flags field (FLAGS)
Data stream identification field

|
|
|

—+
—————e

17 15
17 20
17 21

Length

field

(LENGTH)

Length extension

Bit

count

field

System specific field

~
~

(LEN256)

(BITCNT)

(SYSPEC)

Name type field (NAMETYPE)
Name field (NAMESPEC)
B-19

(STREAMID)

;

|
|
|

ERROR

Table

B-3:

Micro

(nnnn)

Field

MESSAGES

Values

GENERATED

Reason

{

ACCESS CONTROL LIST message errors by field:
for
eo

future

Unknown

DAP

message

stream

Data

Length

field

extension

Length

Bit

count

B-4

field

specific

Access

control

(ACLCNT)

control

the

micro

and

field

(STREAMID)

|
|

field (LEN256)
(BITCNT)

i
:

field

(SYSPEC)

list

repeat

list

entry

count

field

lists

(FLAGS)

(LENGTH)

System

Access

field

identification

e ——— e

}

flags

Table

field

(reserved

use)

e -+

DAP

(Octal)

AND

(Cont.)

Code

tmm

RMS

(nnnn)

values

for

field

(ACL)
Sy

use

with

macro

(aa)

values

octal.

Note

Micro

(nnnn)

number.

the
here

corresponding
for

meaning

Table

B-4:

Format:

Symbolic

ease
for

Micro

RMS

0-11

codes,

status

reference

contains
where

codes.

only

(nnnn)

Value

They
they

are

have

see

included
no

Status

{Octal)

Code

T+

|
Reason

e Fmm————— e e

0000

0001

ERSABO

0002

ERSACC

0003

ERSACT

0004

ERS$SAID

Bad

0005
0006

~
-

ERSALN
ERSALQ

'
.

Alignment options error
Allocation quantity too

0007

ERSANI

Not

code

Format
R

Symbolic

error

supplied,

DAP.

- Rt

Bits

status

Unspecified

Operation aborted
F1l1-ACP could not

code)

File

error

activity

area

(STV=ERSSTK/MAP)
access file (STV=sys

precludes

|
|

err

operation

large

|
|

ANSI-D

format

B-20

equal

ERROR MESSAGES GENERATED BY RMS AND DAP

Micro

TMTM, Table B-4:

(nnnn)

Format

——————

——— e
fmm——————— o

|
I

Value
(Octal)

'
!

fmmm——————— fmm

Symbolic
Status
Code

0010

0011

|
|
I
.
.
-

|
|
|

—————

——————

Reason

————————
e ———— e
b

(Cont.)

ERSAOQOP

ERSAST

Allocation options error

.
-~

AST levelk
Attribute read error
Attribute write error
Bucket size too large
Bucket size too large
BLN length error

Invalid (for example, synch) operation at

0012
0013
0014
0015
0016

ERSATR
ERSATW
ERSBKS
ERSBKZ
ERSBLN

0020
- 0021
| 0022

ERSBPA
ERSBPS
ERSBUG

Private pool address not multiple of 4
Private pool size not multiple of 4
Internal RMS error condition detected

0024

ERSCHG

SUPDATE changed a key without having

0017

0023

0025
0026
0027

.
i
|

Beginning of file detected

ERSBOF

Cannot connect RAB

ERSCCR

ERSCHK
ERSCLS
ERSCOD

attribute of XBSCHB set

. Bucket format check-byte failure
.~ RSTS/E close function failed
~ Invalid or unsupported COD field
f

F11-ACP could not create file (STV=sys err

0030

ERSCRE

0031

ERSCUR

.~ No current record (operation not preceded by

- 0032
0033
- 0034
0035

ERSDAC
ERSDAN
ERSDEL
ERSDEV

0037

ERSDME

Dynamic memory exhausted

0040

ERSDNF

Directory not found

0042

ERSDPE

Device has positioning error

0036

0041

0043

0044
. 0045
- 004¢6
-

0047

1
.

0050
0051

0052

0053

ERSDIR

ERSDNR

ERSDTP

ERSDUP
ERSENT
ERSENV
ERSEOF

code)

SGET/SFIND)

F11-ACP deaccess error during close
Data area number invalid
RFA-Accessed record was deleted
Bad device or inappropriate device type
Error

in directory name

Device not

ready

DTP field invalid

Duplicate key detected, XBSDUP not set
RSX-F11ACP enter function failed
Operation not selected in ORGS macro
End of

file

ERSESS
ERSEXP

Expanded string area too short
File expiration date not yet reached

ERSFAB

Not a valid FABR (BID field not = FBSBID)

ERSEXT

File extend failure

B-21

ERROR

Table
e

|
|
|
tmm

B-4:

Micro

(nnnn)

Format

|
|

Symbolic
Status

|
|

(Octal)

Code

ERSFAC

|
|

Invalid FAC
for SCREATE

for

|
|

ERSFEX
ERSFID

|
|

File already
Invalid file

0057

ERSFLG

Invalid

flag-bits

File

locked

|
.

ERSFLK

REC-OP:

0056

by .other

ERSFND

RSX-F11lACP

ERSFNF

File

not

found

0063

ERSFNM

Error

file

0064

ERSFOP

Invalid

|
.

0065
0066

.
.

ERSFUL
ERSIAN

|
|

Device/file full
Index area number

invalid

0067

ERSIFI

Invalid

|
|

0070
0071

|
|

ERSIMX
ERSINI

0072

ERSIOP

0073

0074

ERSIRC

Invalid

ISI

buffer

|
|

Invalid
Invalid

|
|

|
|
|

0106
0107
0110
0111
0112

.
|

|
|
|
|
|

0115

key

encountered

value

address

field (KEY=0
key-of-reference

ERSLBL

Lowest level index area
Not ANSI labeled tape

ERSLBY
ERSLCH
ERSLEX

|
|
|

Logical
Logical
Logical

valid

'
|

too

large

negative)
($SGET/SFIND)

for

relative

ERS$SNAM

NAM

block

accessible)

ERSNEF

Not

ERSNID

only)

(IDX/NOT=:(REL))

;

invalid

|
|

still

LOC field invalid
Buffer mapping error

|
|
|

number

|
|

files

positioned

Cannot

allocate

B-22

|
|
t

F11-ACP could not mark file for deletion
MRN value = negative or relative key > MRN
MRS value = 0 for fixed length records or 0
address

RAB

channel busy
channel number too large
extend error, prior extend

ERSMKD
ERSMRN
ERS$SMRS

files

(KBF=0)

|
|

ERSLOC
ERSMAP

[
|

(sequential

unconnected

key

size

for

}

record

Key

0114

invalid

0113

;

}

only)

ERSKRF

file

ERSKEY

|
.
.

unopened

Invalid

0103
0104
0105

value

|
{

|
|
|

file

0077

}

options

0076

0102

|
name

organization

Operation unknown

ERSLAN

failed

Bad

function

ERS$KSZ

exceeded

ERSKBF

file

|
|

areas/key XABS
issued

find

0075

0100
0101

set

Maximum NUM (254)
$INIT macro never

ERSISI

|
|

not

|
|

——— +

user

0062

FBSPUT

combination

0061

|
|

IFI

exists
1ID

DAP

0055

0060

AND

Reason
e

RMS

(Cont.)

|
]

e ——— o L

0054

GENERATED

——— i e
T T T T
—+

Value

MESSAGES

{
|
|
|

invalid

(NAM =

not

|
|

EOF

(sequential

internal

index

files

descriptor

]

ERROR MESSAGES GENERATED BY RMS AND DAP

Micro

Table B-4:

(nnnn)

Format

(Cont.)

——————— —— = +
dmm——————— fmmm———————— e

Symbolic |
Status |
l
Code

|
|
Vvalue
(Octal) |

t
|
|

Reason

l
|
i

————————— — =}
$mm——————— Fmm———————— e

| 0116
| 0117

| ER$NPK
| ERSOPN

| 0120
| 0121
| 0122
| 0123

|
|
|
|

|
|
|
|
|

0124
0125
0126
0127

ERSORD
ERSORG
ERSPLG
ERSPOS

| No primary key defined for indexed file
| RSTS/E open function failed

XABs not in correct order
Invalid file organization value
Error in file’'s prologue (reconstruct file)
POS field invalid (POS>MRS, STV=XAB

|
|
|
|

ERSRAT
ERSRBF

0132
0133
0134
0135
0136
0137

|
|
|
|
|
|
|
|
|

ERSRER
ERSREX
ERSRFA
ERSRFM
ERSRLK
ERSRMV

|
|

0140
0141

|
|

ERSRNF
ERSRNL

|
|

Record not found
Record not locked

|
|

0143
0144

|
|

ERSRPL
ERSRRV

|
|

Error while reading prologue
Invalid RRV record encountered

ERSRTB

|
|
.

Bad record size (RSZ>MRS, or not=MRS 1if
fixed length records)
Record too big for user’s buffer

ERSSEQ

|
|
|
|
|
|
|
|
|

0130
0131

0142

0145

0150

0153
0154
0155
0156
0157

ERSRSA

0147

| 0151
|
0152
|
|
|
|
|

ERSROP

.
|
|

0146

|
|
|

ERSRSZ

t
|
l
}
|

l
&
|
i
1
1
l
}
|

|
|

RAB stream currently active

Primary key out of sequence (RAC=RBSSEQ for

| SPUT)

|
|
|
|
|

;
|
|
|

. ERSSHR
|
| ER$SSIZ

ERS$SSTK
ERSSYS
ERSTRE
ERSTYP
ERSUBF

Invalid record options

| SHR field invalid for file (cannot share
| sequential files)
. SIZ field invalid

|
|
|
|
|

l
i

|
1

|
|
|

]
|
}

1
END_ROW Stack too big for save area
|
System directive error
|
Index tree error
Error in file type; extension on FNS too big |
|
Invalid user buffer address (0, odd, or if
BLK-I0 not word-aligned)

ERROR

Table

B~4:

Micro

tmmmmm———— e

(nnnn)
iR

Symbolic

Value
(Octal)

Code
e e

ERSUSZ

0161

ERSVER

é
e

—— +

Invalid
~

Error

user

buffer size
version number

ERSVOL

Invalid

ERSWER

File

0164

ERSWLK

Device

1is

0165

ERSWPL

Error

while

0166

writing

ERSXAB

Not

valid

XAB

indicator)

Default

0167

BUGDDI

0170

CAA

volume

write

Cannot

access

Cannot

deliver

CDA

Cannot

0173

CHN

Channel

code)

CNTRLO
CNTRLY

|
i

Terminal
Terminal

.
|

write

CCF

err

code)

prologue

(_@XAB=odd,

|
STV=XAB

|
|

invalid

list

AST

failure

(STV=sys

err

|
|

output ignored due to Control-0
input aborted due to Control-Y

DNA

Default

file

DVI

Invalid

device

|
|

ESA

0201

FNA

0202

FSZ

0203

IAL

name

Expanded

string

File

name

string

FSZ

field

invalid

Invalid

KFF

Known

LNE

Logical

0206

NOD

Node

0207

NORMAL

Operation

OK_DUP

Record

0211

OK_IDX

Index

0212

OK_RLK

Record

0213

RFAOK_RRV

Record

accessible

File

file

{

error

address

error

|
|

list

error

successful

inserted

update

had

error

duplicate

occurred;

key

record

locked but read anyway
inserted in primary, but

was

error

found

name

address

{
t

field

address

argument

0204

string

0205

secondary

created,

but

keys

not

CREATE

0215

PBF

0216

PNDING

Bad prompt buffer address
Asynchronous operation pending

0217

QUO

Quoted

string

error

0220

|
.

RHB

i
~

Record

header

buffer

0221

RLF

0222

RSS

0223
.
0224

.
-

RST
8Q0

inserted

not

|
|

RFA

opened
completion

|
|
|

|
invalid

Invalid
Invalid

Invalid

Operation

resultant string
not seqguential

file
resultant string

B-24

may

0214

locked

assignment

0210

argument

|
|

(STV=sys

file

0176

(USZ=0)

number

error

directory

0172

0174
0175

e e+

L0177

Reason
e e

DAP

|
f

;

0162

0171

AND

0160

0200

RMS

(Cont.)

0163

i
-

GENERATED

Status

-P

Format

MESSAGES

size

address

|
|
|
|

|
1

ERROR MESSAGES GENERATED BY RMS AND DAP

Micro

Table B-4:

(nnnn)

Format

(Cont.)

+
———— ——
t-—m—————— fmm————————— o e

Symbcllc

Status
Code

Value
(Octal)

0225

0227

. SYN

|
g

Reason

— +
fmmm—————— o ——————— e e

0226
0230
0231

0232
0233
0234
0235
0236

0237

0240

sucC

SPRSED

TMO
ERSBLK

.
.

ERSBSZ
ERSCDR
ERSCGJ
ERSCOF
ERSJFN

.
.
.
.

ERSTRU

0242

0246

Created file superseded existing version

| File name syntax error

ERSUDF

ERSXCL

|
|
|

Time-out period expired
FBSBLK record attribute not supported

.
.

Bad byte size
Cannot disconnect RAB
Cannot get JFN for file
Cannot open file
Bad JFN value

.
.

Cannot position to end of file

ERSPEF

0241

0243
0244
0245

Operation successful

Cannot truncate file

access is denied

.
|
|

Directory full
Handler not in system
Fatal hardware error

Hardware option not present

File is currently in an undefined state;

File must be opened for exclusive access

. Attempt to write beyond EOF

0247

0250
0251
0252
0253
0254

Device not attached
Device already attached
Device not attachable
Shareable resource in use
Invalid overlay request

0256

Caller’s nodes exhausted

0255

Block check or CRC error

0257

Index file full

File header full
Accessed for write

0260
0261

0262
0263
0264

File header checksum failure
Attribute control list error
File already accessed on LUN

0266

Invalid operation on file descriptor block

0265

0267

Bad tape

format

Two different devices specified on a rename

0270

0271
0272

;
s

- New file name specified in rename already in
.

use

Cannot rename old file system
File already open
B-25

ERROR MESSAGES GENERATED BY RMS AND DAP

‘Table B-4:

Micro (nnnn) Format

e Fmm

Symbolic

Value

Status

(Octal)

Code

tmmm e

(Cont.)

e -e +

i
|

Reason

et o eR T
T pp——— +

0273

Parity

error

0274

End

volume

0275

Data

0276

Bad

block

0277

End

0300

;

0301

File

device

detected

over-run

device

|
|

space

exceeds

;

Specified

Unlock

Send/receive

0306

SPL

0307

NMF

0310

CRC

0311

file

Spool

DAP

Quota

not

installed

LUN

command

file

failure

transfer

checksum

error

exceeded

BUGDAP

Internal

CNTRLC

Terminal

Data

network

error condition detected
input aborted due to Control-C
bucket fill size > bucket size in XAB

0314

DFL

0315

ESL

Invalid

expanded

0316

IBF

Invalid

bucket

0317

IBK

Bucket

size

string length

LAN

IDX

Index

IFA

Invalid

header)

attributes
,

fill

0322

IFL

Index

0323

KNM

Key

bucket

name

IAN

XAB

buffer

size

not

(corrupt

bucket

readable

file

size

j
|

XAB

writeable

XAB

KSI

Index

Multibuffer count
Network operation

invalid (negative value)
failed at remote node

locked

initialized

file

|
|

not

- 0320

not

format

blocks

failure

submit

file

0313

files

0312

0324

space;

}

accessed

file

allocated

task

0304

for

error

0305

|
|

buffer

0303

0321

tape detected

0302

|
|

bucket

will

not

hold

two

keys

for

key

reference

0325

MBC

0326

NET

0327

CK_ALK

Record

already

0330

OK_DEL

Deleted

0331

OK_LIM

Retrieved

0332

OK_NOP

Key

0333
0334

|
-~

OK_RNF
PLV

Nonexistent
Unsupported

REF

Invalid

key-of-reference

XAB

0336

RSL

Invalid

resultant

length

0337

RVU

0335

XAB

Error
~

record
not

exceeds

filled

accessed

specified

key

value

record successfully
prologue version

updating

lost

successfully

record

string

RRVs;

some

paths

accessed

data

;
|

may

|
|

GENERATED BY RMS AND DAP

ERROR MESSAGES

Table

B-4:

Micro

(nnnn)

Format

(Cont.)

— - — +
-oe
$m—mmmm———— fmmm———————

Value
(Octal)

Symbolic

Status
Code

|
|

%
5

Reason

——— o —————————— e +
e
fmm——————— fmm—m

0340
|
0341
0342
0343
0344
0345

0346

0347
0350
0351

0352
0353

~ SEG
L
@
. SUP
~ WBE
. WLD
. WSF

Directory listing; error in reading volumeset name, directory name, or file name
Directory listing; error in reading file
attributes

|
;
|
E
1
|

working set)

.~
~
.
w
~

i
§
o
|
|
;

Directory listing; protection violation in
read the volume-set,

directory or

trying to

Directory listing; protection violation in

Directory listing;

exist

file

SNE

0360
0361
0362
0363
0364
0365

TNS
BES
- PES
WCC
IDR
STR

0366

SPE
UPI
ACS

~
|

FTM

.
~

~
~

6000
7777

t-m—————— fmm

file attributes do not
|

Directory listing; unable to recover

name

trying to read file attributes

|
|
}
4
|
|
|

0354

0355
0356
0357

'~ Data types other than string limited to one
- segment in XAB
~ Reserved
. Operation not supported over network
.~ Error on write behind
. Invalid wildcard operation
. Working set full (cannot lock buffers in

—-e

|
|
|
|

directory list after Continue Transfer

Sharing not enabled

(Sk1ip)

Sharing page count exceeded
UPI bit not set when sharing with BRO set
Error in access control string

|
|
|
|

Terminator not seen
Bad escape seguence
Partial escape segquence
Invalid wildcard context value
Invalid directory rename operation
User structure (FAB/RAB) became invalid

|
|
|
|
|
i

Network file transfer mode precludes

during operation

;

operation

User defined errors

————— - +
ee

Table B-5 lists the micro (nnnn) values for use with macro (aa)
value of 12 octal. This refers to the macro Synchronization category.
B-27

ERROR

MESSAGES

GENERATED

RMS

Note

Micro

(nnnn)

Format:

Bits

0-11

contains

message

type

number.

Table

B-5:

Micro

(nnnn)

Values

for

Macro

(aa)

Value

Octal

tmmm—————— o
-+

Value

(Octal)

Reason

- ——— e et
it +

0000

Unknown

0001

Configuration

0002

Attributes

0003

Access

0004

Control

0005

Continue

0006

Acknowledge

0007

Access

0010

Data

0011

Status

0012

Key

0013

Allocation

0014

Summary

0015

Date

transfer

complete
;

definition

and

time

Protection

0017

Name

0020

Access
I

attributes

0016

attributes

extension

attributes

;

extension

;

attributes extension

|
1

control
T

list
I

extended
L

attributes
R

|
|

AND

DAP

INDEX

CTRL/P

-A-

Active

node,

Active

nodes,

Adjacent
APPEND

2-3
4-8

node,

1-3

command

NFT,

4-12,

/APPEND

NFT,
/ASCII

4-14,

4-15f

switch

4-12,

Appending

4-36

files,

DAP, 4-2, 4-3
version number, 4-33
DCL Run-Time System, 3-4,

4-5

DECnet/E

4-14,

switch

NFT,

command

4-36

definition,
node,

1-1

1-2

sample

4-36

network, 1-3f
1-1
command
4-19, 4-20f%f

utilities,
DELETE

NFT,
/DELETE

BATCH

submitting files,
Binary files, 4-36
/BLOCK

4-29

switch

4-38

Deleting
/DENSITY

switch

files,
switch

DETACH

command

NET,

verification,

3-8

Device

5-7

specification

switch

NETCPY,

4-37

NFT,

4-42

NETCPY, 5-5

NETCPY, 5-5
NFT, 4-36
Block transfer
/BRIEF

NFT,

5-2,

5-3

4-10

Devices

busy,

Carriage control, 4-41
CCL command formats, 2-4
4-5

TLK,

2-3,

Concise
See

3-5t,

4-13t,

files

/CONTIGUOUS

5-4t

Language

allocation,

4-38
switch

verification

4-16,

5-7

(TLK),

2-3,

2-4,

transfer,

5-7

4-40,

4-42,

4-44

Directory names,
me

4-18f

Copying

devices,

Copying

files,

5-1

Error

4-16

switch

NFT,

4-43,

DIRECTORY command
NFT, 4-21, 4-22f
Directory listings
NFT, 4-37, 4-38,

command

NFT,

4-10,

5-7

»Dialag mode (TLK), 2-5

4-38

CONTINUE command
NET, 3-6

CTG

5-1
tape,

2-5

Command

Contiguous

COPY

parity,

2-6

CCL

NFT,

copying,
magnetic

specification

NFT,

Commands,

4-10

messages

DAP,

B-11

NET,

3-13

NETCPY,

4-38

Index-1

5-9t

4-10,
p

4-26

Error

messages

NFT,

4-44t

RMS,

B-1,

TLK,

2-10

EXIT

(Cont.)

B-11t

/IDENTIFY

NFT,

command

Image

3-9

See

NFT,

4-23

/IMAGE

Binary

NFT,

4-39

NFT,

switch

NFT,

NETCPY,

5-3,

File Access
See

File

5-6,

5-7

FAL

Line

input

NET,

4-9

logical,

appending

with

attributes,

4-39,

binary,

block

NFT,

4-12,

4-41,

transfer,

copying

4-14,

4-42,

4-36

4-36,

4-44

allocation,

with

NFT,

4-19,

directory

listings,

Binary
and

4-21

NFT,

submitting

superseding

4-44

BATCH,

4-25,

2-7

4-44

field

Magnetic

4-43,

records,

data,

-M-

Macro

4-29

existing,

array

2-4,

4-42

Micro

4-44

virtual

2-1,

4-10,

4-3

4-27

4-41,

variable-length

/FULL

4-8,

link,

4-11

printing

with

5-2

4-6,

Logical

allocation,

ASCII,

information

NFT,

LSN,

1-3

4-40

NETCPY,

noncontiguous
stream

switch

NFT,

files

type,

/LOG

Log-in

See

node,

4-42

image

4-40

Local
4-38

1-3

switch

NFT,

4-16

4-3

physical,
/JLIST

4-36

deleting,

name

4-14,

4-36

contiguous

4-41,

values,

tape,

field

values,

Micro

format,

B-20t

Micro

values,

B-28t

/)MORE

4-37

NFT,

B-11lt

4-10,

4-43
B-13t

switch

4-40

switch

NFT,

4-38

-N
-

Named
-H-

directories,

/NATIVE
NFT,

command

NET,

3-10

NFT,

4-24

/HELP

3-11

Link

Files

HELP

switch

4-39

Listener

specification

NFT,

switch

4-12

INQUIRY

/FC

files

switch

/INQUIRY

4-3

4-38

files

NET,

FAL,

switch

4-6,

/NC

5-6

4-41

switch

NETCPY,

switch

NETCPY,

switch

NETCPY,
NCP,

Index-2

5-7

switch
4-8

5-7

4-10,

4-26

.
.

NFT utility, 4-1
APPEND command,

3
J

commands,
providing

3-5t
access,

NET utility,

3-1

capabilities,
commands,

3-2f

3-1

3-4

CONTINUE command
CTRL/P command, 3
DETACH command, 3
error

EXIT

messages,

command, 3-9
command, 3-10
input, 3-11

HELP
line

NORMAL command, 3-11
ODT command, 3-12
running, 3-2
single-character input,

3-11

NETCPY

allowable devices, 5-3
capabilities, 5-1
command format, 5-2
device specification, 5-2, 5- 3
error messages, 5-9t
log-in information, 5-2
node specification, 5-2, 5-3
running, 5-2
switches, 5-4t

switches /BLOCK switch, 5 -5
switches /DENSITY switch, 5— 5
switches /FC switch, 5-3, 5- 6,

4-12, 4-14
appending files, 4-14, 4-36
capabilities, 4-1
CCL command format, 4-5
command format, 4-6
commands, 4-13
continuing command line, 4-40
COPY command, 4-16
copying files, 4-16
DELETE command, 4-19
deleting files, 4-42
device specification, 4-10
DIRECTORY command, 4-21
directory listings, 4-21, 4-37,
4-38, 4-40, 4-42, 4-44
EXIT command, 4-23
file specification, 4-9
HELP command, 4-24
log-in information, 4-6, 4-8,
4-10, 4-25, 4-38
node

printing files,
quoted strings,
running, 4-5
SUBMIT command,
switches

5-7

/HELP switch, 5-6
/NC switch, 5-7
switches /PARITY switch, 5-7
switches /VERIFY switch, 5-7
verifying transfer, 5-7
switches
switches

NETOFF,

6-1

Network

Pseudo

See

See
See

Protocol

NSP

Network

4-12,

/ASCII,

4-36

/BLOCK,

4-36

/BRIEF,

4-37

4-29

4-36

/LOG,

4-40
-, 4-40
or
/MORE
/NATIVE, 4-41

shutdown

NETOFF

NFT

commands, 4-13t
error messages, 4-44t
error messages from DAP,
error messages from RMS,
sample network, 4-8f
switches, 4-34t

/APPEND,

4-27
4-12

4-38
4-38
/CTG,
/DELETE, 4-38
/FULL, 4-38
/IDENTIFY, 4-6, 4-38
/IMAGE, 4-39
/INQUIRY, 4-12, 4-39
/LIST, 4-40

Keybocard Driver

Services

4-7

/CONTIGUOUS,

NPKDVR

Network

specification,

NODESPECIFICATION command,
PRINT command, 4-27

/NOATTRIBUTES,
/NOCONTIGUOUS,

4-42
4-42

/NODELETE, 4-42
/NOHEADING, 4-42
/NOSUPERSEDE, 4-43

B-1ll
B-1

/POS,
/RWC,

Index-3

4-43.
4-43

4-25

NFT

utility

switches
/RWO,

(Cont.)

/TOTAL,

4-44

password,

VERSION

PARITY

4-33

4-9,

4-26

Peripheral
See

4-42

adjacent,

4-8

/POS

switch

NFT,
PPN,

(NETCPY) ,

5-2

specification

(NFT),

4 -7

specification

(TLK),

2 -3,

4-25

4-27,

DAP,

Pseudo

5-3

See

4-2

keyboard

driver

NPKDVR

switch

4-42

.-.Q.....

NODESPECIFICATION

command

Quote

4-25

NODESPECIFICATION

command

(NFT),

4-6

characters

NFT,

Quoted

/NOHEADING
NFT,

4-28f

Protocols

2-5

NFT,

4-11

command

NFT,

specification

4-40

4-43

4-10,

2-4,

Program

1-3

4-38,

wildcarding,

specification

NFT,

link,

4-37,

1-3

/NODELETE

Interchange

PIP,

1-3

4-26

PIP

Physical

2-3,

NETCPY,

5-7

system,

switch

Node

switch

NETCPY,

4-42

remote,

2-8

Password,

switch

/NOCONTIGUOUS

local,

2-4,

2-2

program

4-26

4-11

/NOATTRIBUTES

active,

OPSER

(TLK),

-pP
-

4-31

command,

wildcards,

NFT,

See

OPSER,

4-44

command,

NFT,

Services

4-44

/VARIABLE,

system

mode

4-43

/SUPERSEDE,

TYPE

One-line
Operator

switch

NFT,

4-12

strings
4-12

4-42

Noncontiguous

files

allocation,
NORMAL

-]R
-

4-42

command

NET,

Record

3-11

/NOSUPERSEDE
NFT,

switch

Remote

RMS,

4-3,

3-9

/RWC

switch

4-43

NPKDVR,

3-1,

NFT,

NSP

reason

Management

codes,

A-1t

/RWO

Services

RMS

See

node,

1-3

4-41,

4-44

4-43

switch

NFT,

4-43

el O
-

Octal
See

ODT

Debugging

Tool
SHOW ACTIVE

ODT

(Octal

Debugging

command
NET, 3-12

Tool),

3-12

Single-character

ODT

single-character

ODT
|

NODES,

command,

3-12

3-11

Index-4

input

3-12

Single-character
input,

4-8

input

(NET),

Stream ASCII,

TYPE command
NFT, 4-32f

4-44

4-41,

Strings

guoted
NFT, 4-12
SUBMIT command
NFT, 4-29, 4-30f
/SUPERSEDE switch
NFT, 4-44

Superseding files,
Switches
NETCPY, 5-4
NFT, 4-34

Utility
NET

3-1

introduction,

4-43,

4-44

NFT

CCL command format,
introduction,

TLK

4-9,

System password,

CCL command format,
introduction, 2-1

4-26

4-5

4-1

2-3

-T
-

Terminal
TLK,

Listener

/VARIABLE switch
NFT, 4-44

LSN

See

2-1

capabilities,

2-1

CCL command format, 2-3, 2-6
device specification, 2-3, 2- 4,
2-5

dialog mode, 2-5
error messages, 2-10t

node

specification,

2-3,

terminal
2-4,

2-2

listener
2-7

utility with LSN,
/TOTAL
NFT,

switch
4-44

4-41, 4-44
/VERIFY switch
NETCPY, 5-7

VERSION command

2-4,

2-5

one-line mode,

Variable-length record files,

NFT, 4-33
Version number
DAP, 4-33

Virtual array data files,

(LSN),

2-1,
-W-

2-2f

Wildcards, 4-39
NFT commands,

Index-5

4-11

4-37

HOW TO ORDER ADDITIONAL DOCUMENTATION
DIRECT TELEPHONE ORDERS
In Continental USA
and Puerto Rico
call 800-258-1710

In Canada
call 800-267-6146

In New Hampshire,
Alaska or Hawaii
call 603-884-6660

DIRECT MAIL ORDERS (U.S. and Puerto Rico*)
DIGITAL EQUIPMENT CORPORATION
P.O. Box CS2008
Nashua, New Hampshire 03061

DIRECT MAIL ORDERS (Canada)
DIGITAL EQUIPMENT OF CANADA LTD.
940 Belfast Road
Ottawa, Ontario, Canada K1G 4C2
Attn: P&SG Business Manager

ELECTRONIC ORDERING
Dial 800-DEC-DEMO with any VT100 or VT200
compatible terminal and a 1200/2400 baud modem.
If you need assistance, call 800-DEC-INFO.

INTERNATIONAL
DIGITAL EQUIPMENT CORPORATION
P&SG Business Manager
c/o Digital’s local subsidiary
or approved distributor

Internal orders should be placed through the Software Distribution Center (SDC), Digital
Equipment Corporation, Northboro, Massachusetts 01532

*Any prepaid order from Puerto Rico must be placed
with the Local Digital Subsidiary:
809-754-7575

DECnet/E
Utilities Guide
AA-H504C-TC

Reader's Comments
Note: This form is for document comments only. DIGITAL will use comments submitted on this form at
the company’s discretion. If you require a written reply and are eligible to receive one under
Software Performance Report (SPR) service, submit your comments on an SPR form.

Did you find this manual understandable, usable, and well-organized? Please make suggestions for
improvement.

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

Please indicate the type of user/reader that you most nearly represent.
[0

[

Assembly language programmer

Higher-level language programmer

Occasional programmer (experienced)

[]

User with little programming experience.

Student programmer

Other (please specify)

Date

Name
Organization
Street

City

State |

Zip Code

c&fiw

mem“mwmmmm

m”mmmmmmmm

mmmmmmmm”m

No Postage
|

Necessary

if Mailed in the

United States

BUSINESS REPLY MAIL
FIRST CLASS PERMIT NO.33 MAYNARD MASS.

POSTAGE WILL BE PAID BY ADDRESSEE

ATTN: Office Systems Documentation MK0O1-2/E02
DIGITAL EQUIPMENT CORPORATION

Continental Boulevard
Merrimack N.H. 03054

Cut Along Dotted Line

a_
'-flh-nnfiunfii_*”“”-‘”‘“-““‘““‘n”-“*--

|
|
I
|

i
n
:
l
|
e
s

|
|
|
u
|
|
|
|
:
1
|
|
|
|
u
|
|
|
;

9
=]
Q.

hxy

| ad

[

n
s
u
|
|

“llllll“l'IHIl'tl"IIi"l'l!'ll”'dflfl'l“l'lll