Digital PDFs

AA-H223D-TC

2000

261 pages

Original

7.1MB

Document:	DECnet-RSX Guide to User Utilities Sep85
Order Number:	AA-H223D-TC
Revision:	0
Pages:	261
Original Filename:

OCR Text

Networks· Communications

.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .... .... .. .. .. .. .. .. .. .. .. ..
--------DECnet-RSX
Guide to User Utilities

~D~DDmD

wore

DECnet-RSX
Guide to User Utilities
Order No. AA-H223D-TC

September 1985
This DECnet-RSX Guide to User Utilities instructs the terminal user in
the use and application of the DECnet-RSX user utilities. This manual
also describes 010 functions supported by local and host terminal
drivers for the user/programmer.
Supersession/Update Information:

This is a new manual.

Operating System and Version:

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

Software Version:

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

AA-H223D-TC
First Printing, September 1985

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

The postage-prepaid Reader's Comments form on the last page of this document requests
the user's critical evaluation to assist us in preparing future documentation.

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

~D~DDmD

MASS BUS
PDP
P/OS

Professional
Rainbow
RSTS
RSX

RT
UNIBUS
VAX
VAXcluster
VMS
VT
Work Processor

Ethernet is a trademark of Xerox Corporation.
This manual was produced by Networks and Communications Publications.

Contents
Preface

Introduction
1.1
1.2

Capabilities ofDECnet-RSX User Utilities .......................... , 1-1
Sample Session with the DECnet-RSX User Utilities ...... , ......... , 1-2

The Network Control Program (NCP)
2.1
2.2
2.3
2.4
2.4.1
2.4.2
2.4.3
2.4.4
2.4.5
2.4.6
2.4.7
2.4.8
2.5
2.5.1
2.5.2
2.5.3
2.6
2.7
2.7.1
2.7.2
2.7.3
2.8
2.8.1
2.8.2

Invoking and Exiting NCP ........................................... 2-1
Abbreviating NCP Commands ....................................... 2-2
Obtaining Assistance in Selecting NCP Commands ................. , 2-2
Obtaining Node Information ........................................ 2-3
Directing NCP Command Output to an Output File ................. , 2-3
Node Identification .................................................. 2-4
Node States .......................................................... 2-5
Obtaining Local Node Information .................................. 2-5
Determining if a Specific Remote Node Is Reachable ................ , 2-6
Determining All Reachable Nodes .................................. , 2-7
Determining the Nodes Known to Your System .................... , 2-8
Determining Adjacent Nodes ....................................... , 2-9
Obtaining Line and Circuit Information ............................ 2-11
Line and Circuit Identification ..................................... 2-11
Line and Circuit States .............................................. 2-11
Determining Line and Circuit States ................................ 2-13
Executing NCP Commands at Remote Nodes ....................... 2-15
Setting and Obtaining Information about Alias Node Names ....... 2-16
Setting Alias Node Names ........................................... 2-16
Changing and Removing Alias Node Names '" ..................... 2-18
Displaying Alias Node Names ....................................... 2-19
NCP Error Messages .................................................. 2-2
RSX System-specific Error Messages ................................ 2-21
Standard DECnet Error Messages ................................... 2-22

Contents-1

The Network File Transfer Utility (NFT)
3.1
3.1.1
3.1.2
3.1.3
3.1.4
3.2
3.2.1
3.2.2
3.2.3
3.2.4
3.2.5
3.2.6
3.2.7
3.2.8
3.2.9
3.2.10
3.2.11
3.2.12
3.2.13
3.2.14
3.2.15
3.3
3.3.1
3.3.2
3.3.3
3.3.4
3.3.5
3.3.6
3.3.7
3.3.8
3.3.9
3.3.10
3.3.11
3.3.12
3.3.13
3.3.14
3.4
3.5
3.5.1
3.5.2
3.5.3

Contents-2

NFT File Descriptor Syntax .......................................... 3-3
Node Specification .................................................. 3-3
File Specification .................................................... 3-5
Wildcards in NFT File Specifications ............................... 3-10
Foreign File Formats ............................................... 3-12
NFT Operations for MCR Users ..................................... 3-14
Rules for Specifying MCR Switches in a Command Line ............ 3-14
NFT Command Line Continuer ..................................... 3-14
Definition of MCR Qualifying Switches ............................ 3-17
The Append Operation ........................................... " 3-20
The Copy Operation (File Transfer) ................................ 3-22
The Delete Operation .............................................. 3-26
The MCR Directory Operations .................................. " 3-27
The Execute Operation ............................................. 3-31
The Help Operation ................................................ 3-32
The Identify Operation ............................................. 3-33
The Rename Operation ............................................. 3-34
The Set Default Operation .......................................... 3-36
The Set Protection Operation ...................................... 3-38
The Spool Operation ............................................... 3-41
The Submit Operation .............................................. 3-43
NFT Operations for DCL Users ..................................... 3-44
Rules for Specifying DCL Qualifiers in a Command Line .......... " 3-45
DCL Command Line Continuer ..................................... 3-45
Definition of DCL Qualifiers ....................................... 3-48
The Append Operation ............................................. 3-53
The Copy Operation (File Transfer) ........... ' ............ " .... " 3-55
The Create Operation ............................................ " 3-58
The Delete Operation ............................................ " 3-59
The DCL Directory Operations ................................... " 3-60
The Print Operation ................................................ 3-64
The Rename Operation ............................................. 3-66
The Set Protection Operation ...................................... 3-68
The Set File Operation .............................................. 3-70
The Submit Operation ............................................ " 3-72
The Type Operation ................................................ 3-74
Exit with Status ................................................... " 3-75
NFT Error Messages ................................................ 3-76
Command Error Messages .......................................... 3-77
Primary Error Messages ............................................ 3-78
Secondary Error Messages .......................................... 3-79

The File Transfer Spooler Utility (FTS)
4.1
4.1.1
4.1.2
4.1.3
4.2
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.2.6
4.2.7
4.2.8
4.2.9
4.2.10
4.2.11
4.2.12
4.2.13
4.2.14
4.2.15
4.3
4.4

The Network Command Terminal Utility (NCT)
5.1
5.2
5.2.1
5.2.2
5.3
5.4
5.4.1
5.4.2

FTS File Descriptor Syntax ........................................... 4-3
Node Specification .................................................. 4-3
File Specification .................................................... 4-5
Wildcards in FTS File Specifications ................................. 4-6
FTS Operations ...................................................... 4-7
Rules for Specifying FTS Switches in a Command Line ............... 4-7
FTS Command Line Continuer ....................................... 4-7
Definition of FTS Qualifying Switches ............................. 4-10
The Append Operation ............................................. 4-21
The Copy Operation (File Transfer) ................................ 4-22
The Delete Operation .............................................. 4-24
The Edit Operation ................................................. 4-26
The Execute Operation ............................................. 4-27
The Help Operation ................................................ 4-28
The Identify Operation .................... , ............ " .......... 4-29
The Kill Operation ................................................. 4-29
The List Operation ................................................. 4-31
The Set Default Operation ................................ , ......... 4-35
The Spool Operation ............................................... 4-37
The Submit Operation .............................................. 4-38
FTS Error Messages ................................................. 4-40
Queue Manager Error Codes ........................................ 4-45

Connecting to a Host System ........................................ 5-3
DisconnectingfromaHostSystem .................................. 5-4
Logging Off a Host System ........................................... 5-4
Entering Terminal Management Mode ............................... 5-5
Sample NCT Session ................................................. 5-6
NCT Error Messages ................................................. 5-7
Connect Errors ...................................................... 5-7
Disconnect Errors .................................................. 5-10

The Remote Terminal Utility (RMT)
6.1
6.2
6.3
6.4
6.5
6.6

Connecting to a Host Node .......................................... 6-3
Disconnecting from a Host Node .................................... 6-4
AbortingRMT ....................................................... 6-5
RMT Control Character Handling ..... , .... , ............. , ........... 6-6
Sample RMT Session ................................................. 6-7
RMT Error Messages ................................................. 6-8

Contents-3

The Phone Communications Utility (PHO)
7.1
7.2
7.3
7.3.1
7.4
7.4.1
7.4.2
7.4.3
7.4.4
7.4.5
7.4.6
7.4.7
7.4.8
7.4.9
7.4.10
7.5
7.5.1
7.5.2

The Terminal Communications Utility (TLK)
8.1
8.2
8.2. 1
8.3
8.3.1
8.3.2
8.3.3
8.3.4
8.3.5
8.3.6
8.4
8.4. 1
8.4.2
8.5
8.6

TLK Communication Modes ......................................... 8-1
Single Message Mode ................................................. 8-3
Format for Sending Messages in Single Message Mode ................ 8-3
Dialog Mode ......................................................... 8-5
Format for Sending Messages in Dialog Mode ........................ 8-6
Sending and Receiving Dialog Messages ............................. 8-7
TerminatingDialogMQde ........................................... 8-8
Dialog Mode Failure Messages ....................................... 8-9
Sample Dialog Mode Exchange ..................................... 8-10
Video Screen Dialog ................................................ 8-11
Executing TLK Command Files ..................................... 8-15
Executing Single Message Command Files .......................... 8-16
Executing Dialog Command Files .................................. 8-17
Exit with Status ..................................................... 8-18
TLKErrorMessages ................................................ 8-19

QIO Functions Supported by the HT: Driver
A.l

A.2

A.3

Contents-4

PHO Screen Format .................................................. 7-1
Conference Calls .................................................... 7-4
Invoking Phone ...................................................... 7-4
Exiting from PHO .................................................... 7-4
PHO Commands ..................................................... 7-8
ANSWER Command ................................................. 7-8
DIAL Command ..................................................... 7-9
DIRECTORY Command ............................................ 7-10
EXIT Command .................................................... 7-11
FACSIMILE Command .............................................. 7-11
HANGUPCommand ................................................ 7-12
HELP Command .................................................... 7-12
HOLD/UNHOLDCommands ....................................... 7-12
MAIL Command .................................................... 7-13
REJECT Command ................................................. 7-13
PHO Diagnostic Messages .......................................... 7-14
Informational Messages ............................................ 7-14
Error Messages ..................................................... 7-16

HT: QIO Subfunctions ............................................... A-I
Restrictions on Half Duplex Terminal Drivers ....................... A-4
HT: Status Returns ................................................... A-5

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

The NFT Utility: File Transfer ....................................... 3-2
The FTS Utility: Queuing File Transfer Requests ..................... 4-2
The NCT Utility: Access to Remote Host Operating System
Resources ............................................................ 5-2
The RMT Utility: Access to Remote DECnet-RSX Node Resources ... 6-2
The PHO Utility: Sample Screen Format ............................. 7-2
The PHO Utility: Sample PHO Conversation ......................... 7-3
The TlK Utility: Communication between Terminals ............... 8-2
The TlK Utility: Sample Split Screen Video Display ................ 8-13

2-1
3-1
3-2
3-3
4-1
4-2
4-3
7-1
7-2
7-3
8-1
A-I
A-2
A-3

Line and Circuit States .............................................. 2-12
Summary ofDECnet-RSX NFT File Descriptor Defaults ............. 3-7
Summary of NFT Operations for MCR Users ........................ 3-15
Summary ofNFT Operations for DCl Users ........................ 3-46
Summary of FTS Operations ......................................... 4-8
Summary ofFTS Function Codes ................................... 4-34
Queue Manager Error Codes ........................................ 4-45
Summary of PHO Qualifiers ......................................... 7-5
Summary of PHO Commands ........................................ 7-6
Summary of PHO Control Characters ................................ 7-7
Special Terminal Keys for TlK Video Dialog Mode ................. 8-15
HT: QIO Functions .................................................. A-2
HT: SET Command Support ......................................... A-4
HT: Status Returns ................................................... A-5

Tables

Contents-5

Preface

The DECnet-RSX ([alde til User Utilities describes procedures for determining
node, line. and circuit states, for setting alias node names, for transferring
files, for accessing the resources of remote DECnet nodes, and for
communicating with other terminal users. This manual also discusses QIO
functions supported by the HT: driver.
Intended Audience

This manual is intended for the DECnet-RSX terminal user. Appendix A
applies, more specifically. to the user/programmer and lists the QIO functions
supported by the HT: driver.
Structure of This Manual

Chapter 1

Outlines the D ECnet-RSX user utili ties and presents a sample
application of the utilities in a terminal session.

Chapter 2

Describes the Network Control Program (NCP) which allows
you to display node, line, and circuit information at your
terminal and to set alias node names.

Chapter 3

Describes the Network File Transfer utility (NFT) which allows
you to perform remote file operations such as file transfers
between your local DECnet-RSX node and any other DECnet
node that supports file operations.

Chapter 4

Describes the File Transfer Spooler utility (FTS) which allows
you to perform the same file transfer and manipulation
operations as NFT. while queuing and processing your requests
according to specified dates and times.
Preface-1

Chapter 5

Describes the Network Command Terminal utility (N CT) which
allows you to log on to any host operating system that supports
network command terminals and use the host system's resources

Chapter 6

Describes the Remote Terminal utility (RMT) which allows you
to access the resources of a remote D ECnet-RSX node

Chapter 7

Describes the Phone Communications utility (PHO) which allows
you to engage in an interactive dialog with a remote user on
a DECnet-RSX, DECnet-VAX, or PRO/DECnet system. (PHO
is available only for RSX-IIM-PLUS and Micro/RSX users)

Chapter 8

Describes the Terminal Communication~ utility (TLK) which
allows you to send single line or dialog messages to other
terminal users that support the TLK utiht\.

Appendix A

Describes the QIO functions that can be executed over an RMT
line with the HT: driver.

Associated Documents

To supplement the DECnet-RSX Guide to User Utilities, you should refer to
the following DECnet-RSX and RSX-IIM/M-PLUS documents:

• DECnet-RSX User's Pocket Guide
• DECnet-RSX Programmer's Reference Manual
• DECnet-RSX Programmer's Pocket Guide
• DECnet-RSX Network Management Concepts and Procedures
• DECnet-RSX Guide to Network Management Utilities
• IASIRSX-l1 lID Operations Reference Manual

Preface-2

Graphic Conventions
Convention

Meaning

Monospace

Monospace type depicts examples of user input or system
output. User input is shown in red; system output is shown
in black. For example,

HCP> HELP SHOW NODE
UPPERCASE

Uppercase letters indicate characters that you must type exactly
as shown.

italics

Italics represent variables for which you must supply actual
values.

[opt-argument]

Square brackets enclose optional argument,,_ You can either
include the item shown in brackets or omit it. DO NOT type
the brackets in a command line.

JoPt~onl}

Braces indicate that you must choose ONE of the options
contained within them. DO NOT type the braces in a command
line.

<CTRL/x)

<CTRL/x) indicates a control character keying sequence. The
CTRL key on your keyboard and the appropriate character
key should be pressed simultaneously. For example, to enter
a <CTRL/C), hold down the CTRL key and type a C at the
same time. In displays, control characters are shown as "x.
For example, when you press <CTRL/C), ... c is displayed on
your terminal.

<KEY)

This symbol indicates that you should type the specified key.
For example, the <RET) symbol indicates that you should
type the RETURN key.

>HCP <RET>
HCP>

Most examples in this manual represent terminals in MCR
mode. However, you need only type a utility name in response
to an MCR or DCL prompt in order to invoke the utility and
have it prompt you for input.

loptlOn2

Preface-3

1
Introduction

1.1 Capabilities of DECnet-RSX User Utilities
The DECnet-RSX user utilities provide the following capabilities:
• Examination of node, line, and circuit states. The Network Control Program

(NCP) allows you to display node, line, and circuit information at your
terminal. The information available for a local node includes the current
state of the node and the name and address of the node. The information
available for a remote node includes the type of node. the current status of
the node, and the identification of all lines and circuits associated with the
node. NCP also provides information on the state of a specific line or circuit.
Chapter 2 explains ~CP.
• Specification of alias node names. NCP also allows you to assign or change

alias node names. Alias node names are abbreviated pseudonyms that you
can specify in order to simplify a node name or to simplify node name and
access control specification (see Section 2.7).
• File transfer and manipulation. The Network File Transfer (NFT) and the

File Transfer Spooler (FTS) utilities allow you to transfer files to another
user either on the same node or on a remote node. In addition. NFT and
FTS provide a variety of file transfer and manipulation capabili ties. such
as transferring local command files to a remote node for execution, spooling
files to a line printer, and appending files to an existing file. (The basic
difference between NFT and FTS is that FTS queues and processes user
requests according to user-supplied dates and times, while NFT executes
user commands interactively.) Chapters 3 and 4 contain complete
explanations of NFT and FTS capabilities, respectively.

Introduction

1·1

NFT is accessible to both ~fCR and DeL users. FTS has support for MCR
users, only.
• Access to remote host node resources. The Network Command Terminal

utility (NCT) allowc;; you to ac(~ess the resources of remote nodes which
support the Terminal Services Architecture (TSA). NCT enables you to log
on to remote systems and communicate with all programs run under the
host operating system ~CT is available on RSX-IIM-PLUS systems.
RSX-I1M/RSX-11S V4.2 (or greater) systems, and Micro/RSX systems.
Chapter 5 explains the NCT utility.
The Remote Terminal utility (RMT) allows you to access the resources of
remote DECnet-RSX nodes. RMT logically connects your terminal to a
specific remote node that supports the RMT host facility . You can then use
your terminal as though it were physically connected to the remote host
node. Chapter 6 explains the RMT utility.
• Communication with DECnet-RSX, DECnet-VAX, and PRO/DECnet users.

The Phone Communications utility (PHO) allows you to engage in an
interactive dialog with up to six users, concurrently. PHO allows you to
"phone" any user on your local node, or on a remote DECnet-RSX,
DECnet-VAX. or PROIDECnet node. PHO provides many advanced features
that are not available with the TLK utility (see the description which
follows). PHO is available only on RSX-IIM-PLUS and Micro/RSX systems.
Chapter 7 explains the PHO utility.
The Terminal Communications utility (TLK) allows you to send a single line
message or to engage in a dialog with another terminal user. TLK enables
you to communicate with another user on your local DECnet-RSX node or
on a remote node that supports the TLK utility. Chapter 8 explains the
TLK utility.

1.2 Sample Session with the DECnet-RSX User Utilities
The following sample terminal session presents a sequence of operations that
use the utilities described in this manual. In this session. HOME is your local
node name, and YUKON is the remote node name. You are user Jones on
node HOME. MCR is the command line interpreter.
Initially, you use NCP to confirm that remote node YUKON is
from your node.

1-2

reachable"

DECnet-RSX Guide to User Utilities

>NCP<RET>
NCP>SHOW NODE YUKON<RET>
Node summary as of 14-JAN 84 13 12
Remote
Node

State

Active
Links

Delay

Circuit

Next
Node

4.19 (YUKON)

Reachable

DMC-1

8.22 (MAYHEM)

NCP> <CTRL/Z>
>

Then, you use PHO to see if user Smith is available on node YUKON. You
perform a phone directory of all users on node YUKON to see if user Smith
is available. and if so, to obtain his TTn (target terminal identification).
> PHONE <RET>
RSX-llM PLUS Phone Facility

15-AUG-84

%DIRECTORY YUKON <RET>
Press any key to cancel directory listing and continue.
Process Name

User Name

Terminal

Phone Status

BRAUNSTEIN
Larry
Joe Smith
DALEY
Dave Garrod
IAN
Terri Buckley
Bob Fraser

BRAUNSTEIN
AUGUSTUS
SMITH
DALEY
GARROD
IAN
BUCKLEY
FRASER

unusable
TT2
TT4
TT7
TT9
TT12
TT18
TT13

available
available
available
available
/nobroadcast
available
available

8 persons listed
<CTRL/Z>
>

After typing <CTRL/Z> to exit from PHO, you use TLK in dialog mode to
converse with user Smith on node YUKON (another option would have been
for you to "phone" Smith while you were still using the PHO utility, see
Chapter 7). Once TLK successfully connects with YUKON and user Smith
indicates a willingness to talk" with you, you receive the (TLK> - START
OF DIALOG message on your terminal. You can then engage in a dialog with
Smith, instructing him to load pack FRED onto drive DRO:.
II

Introduction

1·3

>TLK YUKON ·TT4:<RET>
<TLK> - START OF DIALOG
TLK>HELLO, IS AN RK06 DISK DRIVF AVAtLABLE?<RET>
<TLK> YES.

YOU CAN USE DR0

TLK> PLEASE LOAD PACK FRED ONTO DRIVE DRO:.
TLK> <CTRL/Z>
<TLK> - END OF DIALOG

BYE. <RET>

N ow you use NCT to logically connect your terminal to YUKON. With NCT
you can log on to the YUKON host operating system and use your terminal
as if it were physically connected to YUKON. You can then mount pack FRED
on YUKON.

>SET /HOST=YUKON <RET>
Connected to YUKON, System type = RSX-11M-Plus
System ID: Distributed Systems 11/70
>HELLO<RET>
ACCOUNT OR NAME: JEFF<RET>
PASSWORD:
<RET> (the password does not echo)
RSX-11M-PLUS V3.0 [1,54] SYSTEM
GOOD MORNING
14-SEP-84 11:18 LOGGED ON TERMINAL RTO:
>MOUNT DRO:FRED<RET>
You can then use NCP to set the alias (H) for your original node name,
HOME, and your password and account information, JEFF/SECRET. Use of
the alias will simplify node and access control specification in the NFT
command line used to transfer files to YUKON.

>NCP SET ALIAS H DESTINATION HOME/JEFF/SECRET<RET>

1-4

DECnet-RSX Guide to User Utilities

N ext, you use NFT to transfer ftIe!'. fron. your original node, HOME, to your
current node. YUKON. so that the files can be task built there. (You need
not specify any output node name or directory; the output files will default
to your current node and directory.) Then. you check the YUKON directory
for the existence of the special Ii brary files used for assembling and task
building files.

>NFT<RET>
NFT>=H: :TEST1.MAC,TEST2.MAC,*.CMD<RET>
NFT><CTRL/Z>
>PIP DRO: [1,l]SPCLIB.OLB/LI<RET>
DIRECTORY DRO:[l,1]
14-JAN-84 13:18
SPCLIB.OLB

31.

C 22-NOV-84

Now you are ready to assemble and task build the files. (Remember. with
NeT. your terminal is logically connected to YUKON.)

>MAC @TESTASM<RET>
>TKB @TESTBLD<RET>
When the job is done. you dismount the disk, DRO: and log off of the YUKON
operating system. This action causes NeT to exit and returns control to your
local operating system. completing the session.

>DISMOUNT DRO:<RET>
DMO -- RTO: DISMOUNTED FROM DRO: *** FINAL DISMOUNT ***
>BYE<RET>
CONNECT TIME:
1 MINS.
CPU TIME USED: 1 SECS.
TASK TOTAL:
1
NCT -- Control returned to node "HOME"
>

Introduction

1·5

2
The Network Control Program (NCP)

The Network Control Program (NCP) allows you to obtain node, line, and
circuit information and to set alias node names. NCP is a DECnet utility
program that is normally used by the system manager to control the network.
This chapter describes a subset of NCP commands that may be useful to
RSX-IIM/M-PLUS terminal users. RSX-llS users should refer to Chapter 1
of the DECnet-RSX Guide to Network Management Utilities for a description
of NCP support for RSX-l1S systems. For a complete discussion of all NCP
capabilities refer to the DECnet-RSX Network Management Concepts and
Procedures manual.
NCP now offers DCL support for the SHOW ACTIVE NODES command (see
Section 2.4.6 for the DCL command syntax).

2.1 Invoking and Exiting NCP
To invoke NCP, type ~CP after the MCR or DCL prompt and NCP will
prompt you for command input:
>NCP <RET>
NCP>command

Where command is any NCP command verb or command string.
To exit from NCP, type a <CTRL/Z> or specify the EXIT command:
NCP> <CTRL/Z>

NCP>EXIT <RET>

The Network Control Program (NCP)

2-1

2.2 Abbreviating NCP Commands
Most NCP commands CUIlSl&L ot a command name. a component upon which
the command acts, and selected parameters for that component> When you
type NCP commands. you can dbbreviate any keyword to the first three letters.
For example. the format for the NCP command used for obtaining node
information is:
SHOW NODE node-id
or
SHO NOD node-id
where node-id specifies the name or address of the node. The node ID cannot
be abbreviated in NCP commmands (see Section 2.4.2).

2.3 Obtaining Assistance in Selecting NCP Commands
If you need assistance in selecting NCP commands, use the HELP command.
If you want to obtain a summary of all NCP commands. type

NCP>HELP<RET>
The HELP command can be used with a specific NCP command or component
to display the relevant information about that command or component. for
example:

NCP>HELP SHOW<RET>
NCP>HELP SHOW NODE<RET>
For the HELP command to work, the NCP HELP files must be located on
LB:[l,2). If they are not in the proper place, you will get the following message:

NCP - No HELP Available
If you get this message. ask your system manager to place the HELP files
on the correct directory.

2·2

DECnet-RSX Guide to User Utilities

For additional assistance, NCP ptoVld~s command prompting. At any point
where you can type a space and where another argument must follow. type a
carriage return instead. NCP will plompt you for the required information as
shown here:
Example:

NCP>SHOW<RET>
Show component: NODE<RET>
Node identification: YUKON<RET>

If you need more assistance about the choices available to you, press the
<ESC> key in response to any of the NCP prompts, and relevant information
will be displayed.

2.4 Obtaining Node Information
To display local or remote node information. use the appropriate NCP SHOW
command. as descri bed in the sections that follow.
All NCP SHOW commands cause output to be displayed at your terminal.
However, you can direct command output to an output file at your local node
(see Section 2.4.1. which follows).
2.4.1 Directing NCP Command Output to an Output File

To direct command output to an output file at your local node, append the
keyword TO, followed by the output file specification. to the NCP command.
For example, to direct the SHOW NODE YUKON command output to the
file YUKON .LST, type
NCP>SHOW NODE YUKON TO YUKON.LST<RET>

If the specified output file does not already exist. NCP will create a new file.
If the specified file already exists, NCP will append the output to that file.
NCP does not create a new version of the existing output file.
You can also use the Network Display utility (NTD) to display information
about local or remote RSX nodes. The NTD utility is described in the
DECnet-RSX Guide to Network Management Utilities.

The Network Control Program (NCP)

2·3

2.4.2 Node Identification

Node names are unique names that your system uses to refer to other nodes.
A node name is a 1· to 6- character alphanumeric string containing at least
1 alphabetic character. Node names may not be abbreviated in NCP commands.
(However, you can create alias node names. which can simplify node name
specification, as described in St'ction 2.7.1 )
The format for a node address depends on whether or not a node has multiarea
support. If a node has multiarea support. the node address consists of an area
number identifying that node's area within the multi area network. and a unique
decimal integer assigned to the node at network generation (for example. 4.19
YUKON). If a node does not have multi area support, the node address consists
of an area number of 1 and a unique decimal integer (for example. 1.18
BASIN). ~[ultiarea support is described in the DECnet-RSX Network
Management Concepts and Procedures manual.
NOTE

Most of the examples in this chapter contain node addresses
for single area network nodes. However. for those users with
mulbarea networks. the examples for the NCP SHOW ACTIVE
NODES and SHOW KNOWN NODES commands contain
multiarea node addresses.
In NCP commands, if you specify a node address for a multiarea
node but do not supply a specific area number for that node.
the area number that is returned defaults to the area of the
executor node to which the command is issued.
To obtain information about your own node (the executor node), follow the
instructions given in Section 2.4.4. To obtain information about remote nodes.
refer to Sections 2.4.5. 2.4.6. and 2.4.7.

2-4

DECnet-RSX Guide to User Utilities

2.4.3 Node States

The executor (local) node can be in one of three states:
ON

In this state, communications paths (logical links) can be established
with other nodes. This is the normal operating state.

SHUT

When the system manager (or any other privileged user) sets the
executor to this state, the network closes down gracefully. This
means that no new logical links are permitted. but existing links
are allowed to complete. When all links are complete and
disconnected. the node is set to the OFF state.

OFF

In this state, your node is isolated from the network. No logical
links can exist and any previous links have been destroyed.

2.4.4 Obtaining Local Node Information
If you want to know the name of the node on which you are operating (the
executor node), along with the node address and state and the system
identification. use the SHOW EXECUTOR command. as shown here:

NCP>SHOW EXECUTOR<RET>
Example of a display:

Node summary as of 23-NOV-84 10:36
Executor node = 1.18 (HIRDAL)
State = On, Identification = HIRDAL DISTRIBUTED SYSTEMS

The Network Control Program (NCP)

2-5

2.4.5 Determining if a Specific Remote Node Is Reachable

If you want to' know Ii a "pee-ifk node is reachable (that is, whether a
communication path can be est.ablished between that node and your node), use
the NCP SHOW NODE comnland ,\II the SHOW NODE commands display
node state information for remote nodes (see the following text and Section
2.4.6). The format for the ~CP SHO\V NODE command is:

SHOW NODE node-id
where node-id specifies the name or address of the remote node.
For example, if you plan to send a TLK message to remote node YUKON or
to use NFT to transfer files to YUKON, you can first check to see if YUKON
is reachable. To do so, enter
NCP>SHOW NODE YUKON<RET>
Example of a display:
Node summary as of 23-NOV-84 10:46
Remote
Node

State

Active
Links

Delay

Circuit

Next
Node

1. 19

Reachable

DMC-1

1.22 (YENHAM)

(YUKON)

This display example reveals that YUKON is reachable, meaning that
connections to YUKON can be attempted.

2·6

DECnet-RSX Guide to User Utilities

If your node is a non routing node. remote node state information is not
available. You must have the SHO\iV ~ODE command executed at a reachable
full-routing node (in a multiarea network, the full-routing node must reside in
the same area as thp node for which you are requesting information). To do
so, use the TELL command shown below and detailed in Section 2.6. (See
Section 2.4.8 for information on determining adjacent nodes and adjacent node
types.) The format for the NCP TELL command is:

TELL routing-node-id SHOW NODE node-id
where
routing-node-id

specifies the name or address of a reachable full-routing
node at which the SHOW NODE command is to be executed.

node-id

specifies the name or address of the node for which you
want information displayed.

In the following example, your node (HOME) is a non routing node, and you
want to determine if remote node YUKON is reachable. Therefore. you must
have the SHOW NODE command executed at node NEXT. a full-routing node
accessible to node HOME:

NCP>TELL NEXT SHOW NODE YUKON<RET>
The information displayed at your terminal will reveal whether YUKON can
be reached by your node.
2.4.6 Determining All Reachable Nodes

A reachable node is a node to which the executor node can establish a
communication path. NCP will display names, addresses, and other information
for all reachable nodes in the network. The SHOW ACTIVE NODES command
is useful when you are planning to access several nodes (for example, when
using NFT to make transfers to several nodes). This command displays
information regarding all reachable nodes so that you do not have to use the
SHOW NODE command separately for each node. (However. if your network
is large, you may prefer to use the SHOW NODE command only for those
specific nodes that you are interested in.)

The Network Control Program (NCP)

2-7

NCP offers MCR and DeL support for the SHOW ACTIVE NODES command.
Both the MeR and DeL command syntax are shown below:
MCR Command Syntax:

DCl Command Syntax:

NCP>SHOW ACTIVE NODES <RET>

$ SHOW NETWORK <RET>

Example of a display:

Active nodes summary as of 23-NOV-84 11:02
Executor node = 6.18 (HIRDAL)
State = On, Identification = HIRDAL DISTRIBUTED SYSTEMS
Active links = 2
Remote
Node

State

2.2 (GRIBEL)
2.3 (YUKON)
4.7 (WOLERY)
4.8 (GAMMA)
4.9 (MARVIN)
6.10 (FORD)
9.15 (QUASAR)

Reachable
Reachable
Reachable
Reachable
Reachable
Reachable
Reachable

Active
Links
2
0
0

Delay

Circuit

Next
Node

4
4
18

DMC-2
DMC-l
DMC-O
DMC-O
DMC-O
DMC-O
DMC-O

6.17 (REXHUB)
8.22 (YENHAM)
4.7 (WOLERY)
9.21 (ROCK)
11. 30 (SCRIBE)
8.24 (CHIPS)
11.16 (WAREN)

2.4.7 Determining the Nodes Known to Your System

NCP will display all nodes whose names are known to your node and whether
or not these nodes are currently reachable (or active. as defined in Section
2.4.6). The known nodes display format is identical to the display generated
by the SHOW ACTIVE NODES command. To determine the nodes known to
your system, enter
NCP>SHOW KNOWN NODES<RET>

2·8

DECnet-RSX Guide to User Utilities

Example of a display:

Known nodes summary as of 23-NOV 84 14:21
Executor node = 6.18 (HIRDAL)
State = On, Identification - HIRDAL DISTRIBUTED SYSTEMS
Active links = 0
Remote
Node

State

2.1 (ORION)
2.2 (GRIBEL)
2.3 (YUKON)
4.6 (ZEUS)
4.7 (WOLERY)
4.8 (GAMMA)
4.9 (MARVIN)
9.10 (FORD)
9.12 (KREMIT)

Unreachable
Reachable
Reachable
Unreachable
Reachable
Reachable
Reachable
Reachable
Unreachable

Active
Links

Delay

Circuit

0
2
0

6
4
4

DMC-2
DMC-l

DMC-O
DMC-O
DMC-O
DMC-O

Next
Node
2.1 (ORION)
6.17 (REXHUB)
8.22 (YENHAM)
8.26 (RDVAX)
4.7 (WOLERY)
9.21 (ROCK)
11. 30 (SCRIBE)
8.24 (CHIPS)
8.23 (VAXWRK)

Note that nodes 9.12 (KREMIT), 4.6 (ZEUS). and 2.1 (ORION) are unreachable.
2.4.8 Determining Adjacent Nodes

An adjacent node is a node that is either physically connected to your node
or on the same Ethernet as your node. (All nodes on an Ethernet are considered
adjacent to one another.) To determine all nodes adjacent to your node. use
the NCP SHOW ADJACENT NODES command:
NCP>SHOW ADJACENT NODES<RET>

The Network Control Program (NCP)

2·9

Example of a display:

Adjacent nodes status as of 10-NOV-84 15:22:07
Remote
Node

State

Active
Links

1.6 (GRIBEL)
1. 9 (ORI)
1.20 (REX)
1.22 (YENHAM)
1.24 (CHIPS)
1.30 (SCRIBE)
1.32 (VAX4)

Reachable 1
Reachable
Reachable
Reachable
Reachable
Reachable 1
Reachable

Delay

Circuit

Next
Node

UNA-O
UNA-O
UNA-O
DMC-2
UNA-l
DMC-O
UNA-O

1.6 (GRIBEL)
1.9 (ORI)
1. 20 (REX)
1 22 (YENHAM)
1.24 (CHIPS)
1. 30 (SCRIBE)
1.32 (VAX4)

To determine the node type for all nodes adjacent to your node. use the N~P
SHOW ADJACENT NODES STATUS command:
NCP>SHOW ADJACENT NODES STATUS<RET>
Example of a display:

Adjacent nodes status as of 10 AUG 84 16 23 07
Remote
Node

State

Active
LInks Delay

Reachable
1.3
Next node
Reachable
1. 6 (GRIBEL)
1.6 (GRIBEL)
Next node
Reachable 1
1.8 (GAMMA)
1. 8 (GAMMA)
Next node
Reachable
1.16 (WAREN)
1.16 (WAREN)
Next node
Reachable 1
1.19 (RONDEL)
Next node = 1.19 (RONDEL)
Reachable
1.22 (YENHAM)
1.22 (YENHAM)
Next node
RN1chable
1. 24 (CHIPS)
1. 24 I(,HIPS)
Next node
1.3

2·10

Type

Cost

Hops

Circui

Routing IV

UNA-1

Nonrouting IV

UNA-O

Area

UNA-O

Routing lV

DMC-2

Nonrouting ]V

UNA-l

Routing IV

DMC--O

Nonrouting IV

lH1A-0

DECnet-RSX Guide to User Utilities

2.5 Obtaining Line and Circuit Information
The following sectIOns contaIn InformatlOn pertaining to DDCMP and Ethernet
lines and circuits. For lnformatIon on LAPB (X.25) lines and circuits. refer to
the DECnet-RSX Netll'Ork Wallagetnent Concepts and Procedures manual.
If you want to obtain information regarding lines and circuits. you can use
the NCP SHOW LINE and SHOW CIRCUIT commands. You can request
information for a specific line or circuit. for all active lines and circuits, or
for all known lines and circuits. Section 2.5.1 discusses line and circuit
identification.
2.5.1 Line and Circuit Identification

A line or circuit is identified by a unique identification that is assigned to
the line or circuit during network generation. Examples of line or circuit
identification are DMC-O. DZ-I-O, and DV-O-3. If you do not know a line or
circuit identification. you can type the NCP SHOW KNOWN LINES (or
CIRCUITS) command. The identification of all lines (or circuits) known to
your node will be displayed.
Using the KNOWN LINES or KNOWN CIRCUITS keywords with the SHOW
command is one method of identifying more than one line or circuit. You can
also use the ACTIVE LINES and ACTIVE CIRCUITS keywords with the
SHOW command. Active lines or active circuits are all those lines and circuits
known to your node that are currently turned on (in the ON state). Section
2.5.2 identifies the line and circuit states.
2.5.2 Line and Circuit States

Table 2-1 lists and defines some of the line and circuit states that may be of
interest to you. For a discussion of all possible line and circuit states, see the
DECnet-RSX Network Management Concepts and Procedures manual.

The Network Control Program (NCP)

2·11

Table 2·1: Line and Circuit States

State

Line

Circuit

At least one of the
circuits associated with
the line is in the ON or
the ON-STARTING state.

The circuit is connected to
another active node. available
for use.

ON-STARTING

Not applicable.

The circuit is ready to be used
at this end, but there is no
acti ve node connected at the
other end of the circuit.

SERVICE

The line is reserved for
testing.

The circuit is reserved for
testing.

OFF

None of the cIrcuits
associated with the line
is in the ON state.

The circuit has not been
turned on.

CLEARED

The software line
controller databases
are not loaded.

Associated software line
controller databases are
not loaded.

2-12

DECnet-RSX Guide to User Utilities

2.5.3 Determining Line and Circuit States

If you want to know the state of a specific line or circuit. use the appropriate
NCP command format. shown below'
SHOW LINE line-id
SHOW CIRCUIT circllit-id

where line-id and circllit-id specify the line or circuit whose status you want
to determine.
For example. to determine the states of line DMC-O and circuit PCL-O.I. enter
the following commands:
NCP>SHOW LINE DMC-O<RET>
Example of a display:

Line summary as of 23-NOV-84 16:15
Line
DMC-O

State
On

NCP>SHOW CIRCUIT PCL-O.1<RET>
Example of a display:

Circuit summary as of 23-NOV-84 16:43
Circuit = PCL-O.l
State = On
Adjacent node

1. 8 (SHELOB)

The Network Control Program (NCP)

2·13

If you want to know the "tate of all lines or circuits known to the executor
node and currently working, use the SHOW ACTIVE LINES or SHOW
ACTIVE CIRCUITS command for example.
NCP>SHOW ACTIVE CIRCUITS<RET>
Example of a display:

Active circuits summary as of 23-NOV-84 17:09
Circuit = DMC-O
State = On
Loopback name = A, Adjacent node

1.17 (ARWEN)

Circuit = DMC-1
State = On
Adjacent node = 1.13 (SAM)

If you want to know the state of all lines or circuits known to the executor
node, use the SHOW KNOWN LINES or SHOW KNOWN CIRCUITS
command:
NCP>SHOW KNOWN LINES<RET>
Example of a display:

Known lines summary as of 23-NOV-84 17:31
Line

State

DMC-O
DMC-l
DMC-2
KDP-O-O
DUP-O

On
On
On
Cleared
Cleared

2-14

DECnet-RSX Guide to User Utilities

2.6 Executing NCP Commands at Remote Nodes
You can have an NCP command executed at a remote node by using the
TELL prefix with the command. For example. if you want to know the network
status of your node (that is, if you want to know how another node "sees"
your node), you can have the NCP SHO\" NODE command executed at another
node (specifying your node name with the SHOW NODE command). The
information displayed at your terminal would be the same as the information
displayed at the remote node. The format for using the TELL prefix is:
TELL node-id command
Example:

NCP>TELL YUKON SHOW LINE DMC-3<RET>
In this example, the NCP SHOW LINE command is executed at the remote
node named YUKON. but the resulting information is displayed at your
terminal. The display lists the line information as maintained by YUKON.
The remote node at which the command is to be executed may require that
you specify access control information. Access control information should follow
the node identification, as shown in the following format:
TELL node-id[/user-idlpasswdlacent]eommand
where
user-id

is a 1- to 16-character string identifying the user at the remote
system.

passwd

is a 1- to 8-character password needed to gain access to the remote
system.

aeent

is a 1- to 16-character string used to specify an account at the
remote system. (This field is not used by RSX systems.)

You can use an alias to represent the full node name specification (including
access control information). The next section describes how to set an alias.

The Network Control Program (NCP)

2-15

2.7 Setting and Obtaining Information about Alias Node Names
An alias node name is a user-assigned logical name for a network node that
allows you to refer to a node independently of the actual node name. You
assign an alias to a specific node by entering a command at your terminal.
as described in the following sections.
You can increase the flexi bili ty of your programs by using logical node names
that will also be assigned as alias node names. Therefore, each time you run
a program, you can interact with a different node without having to modify
the node name within the program. and therefore, without having to rebuild
the program. Before run"ning the program. you enter a command at your
terminal to assign to the desired node an alias node name that is identical to
the logical node name used within the program.
You can also use alias node names to abbreviate node specificat ions by
specifying the node name and access control information within the alias.
The following sections describe the commands used to set. change. and remove
alias node names and to obtain information about aliases. Further information
on aliases is provided in the DECnet-RSX Network Management Concepts and
Procedures manual.
2.7.1 Setting Alias Node Names

To specify an alias for a node name. use the SET ALIAS command. The
format for the NCP SET ALIAS command is:
SET ALIAS alias DESTINATION destination-node
where

alias

consists of 1 to 6 alphanumeric characters. with at least 1
alphabetic character.

destination-node

is the name of the node to which the alias is to refer. plus
any network access control parameters associated with this
alias for that node.

N onpri vileged users can set aliases to apply to their own terminal only.
Privileged users can set aliases to apply to all users and tasks (see the
DECnet-RSX Network l'vlanagement Concepts and Procedures manual for more
details).

2·16

DECnet-RSX Guide to User Utilities

Example 1:

The following command causes all rf:lferences to node name l\IE to apply to
node YUKON:

NCP>SET ALIAS ME DESTINATION YU~ON<RET>
In this example, all connect requests to node ME from programs associated
with your terminal will go to node YUKON.
Example 2:

In this example, without the use of alias node names. you would have to type
the following command lines, each of which includes the node name MEXICO
and access control information:

>NFT MEXICO/[l,l]/SECRET: :DTO:BUENO.MAC=GOOD.MAC<RET>
>NFT MEXICO/[l,l]/SECRET: :DTO:DULCE.MAC=YUKON: :SWEET.MAC<RET>
>NFT MEXICO/[l,l]/SECRET: :DTO:VERDE.MAC=QUEBEC: :GREEN.MAC<RET>
To simplify data entry. you can set an alias node name (M) and specify the
access control information as follows:

NCP>SET ALIAS M DES MEXICO/[l,l]/SECRET<RET>
Now. using the alias node name M. you can type these shorter versions of
the same three lines shown above:

>NFT M: :DTO:BUENO.MAC=GOOD.MAC<RET>
>NFT M: :DTO:DULCE.MAC=YUKON: :SWEET.MAC<RET>
>NFT M: :DTO:VERDE.MAC=QUEBEC: :GREEN.MAC<RET>

The Network Control Program (NCP)

2·17

Example 3:

By using aliases,. you can creatf3 .:1 command file that will apply to any node
you choose. All you have to do is use a logical node name in the command
file (REM, in this example) and. before running the command file. specify the
logical node name as the alias of the node for which you want the command
file to apply. The following sample command file can be used to transfer test
files to any remote node and to send a message to the remote node's operator.

; TXFER.CMD
,

NFT REM: :=DM1: [l,10]TEST1,1ES12,TES13<RET>
TLK REM: : 'RUN TEST FILES, PLEASE.<RE1>
.EXIT
To transfer all test files to node YUKON. you would assign alias REM to
YUKON before executing the command file:

NCP>SET ALIAS REM DES YUKON<RET>
2.7.2 Changing and Removing Alias Node Names
To change the current definition of any alias. simply enter a new SET ALIAS
command using the old alias name. The new alias overrides the previous alias.
For example. if in Example 3 (in Section 2.7.1) you later want the test files
transferred to another node (for example. to one named QUEBEC). you can
use the same command file without having to modify it: just assign alias node
name REM to QUEBEC
To remove a particular alias or all aliases known to your terminal. use the
CLEAR ALIAS command. The format for the NCP CLEAR ALIAS command
is:
CLEAR ALIAS alias
For example. to remove the alias ME. enter

NCP>CLEAR ALIAS ME<RET>
To remove all aliases known to your terminal, enter

NCP>CLEAR KNOWN ALIASES<RE1>

2-18

DECnet-RSX Guide to User Utilities

2.7.3 Displaying Alias Node Names

You can display information about aliases with the NCP SHOW ALIAS
command.
Displaying Your Alias Node Names

To display all your alias nod~ names, enter

NCP>SHOW KNOWN ALIASES<RET>
Example of a display:
Known aliases summary as of 27-NOV-84 16:17
Alias
Name

Scope

Destination

Terminal TT2:

HIRDAL

Displaying All System Alias Node Names

To display all aliases system wide. enter

NCP>SHOW ALL ALIASES<RET>

The Network Control Program (NCP)

2·19

Example of a display:

All aliases summary as of 27-NOV 84 16:25
Alias
Name
ME

B
EF
H
W

HIRDAL
YEN HAM
KRYPTN
WOLERY
KREMIT
QUASAR

Scope

Destination

Terminal TT2:
Terminal TT4:
Terminal TT4:
Terminal TT4:
Terminal TT4:
Terminal TT10:
Terminal TT10:
Terminal TT10:
Global
Global
Global

HIRDAL
GRIBEL/MILGROM/ ...
YUKON/FAL
HIRDAL/PHILPOTT/ ...
WOLERY/DECNET/ ...
HIRDAL/MILGROM/ ...
YENHAM/MILGROM/ ...
KRYPTN/MILGROM/ ...
WOLERY/DECNET/ ...
KREMIT/DECNET/ ...
QUASAR/DECNET/ ...

Global aliases (such as WOLERY. KREMIT, and QUASAR in the preceding
display) are aliases set by the system manager that can be used by all tasks
and users. Local aliases are those set by nonpri vileged users and apply only
at the usert s terminal (for example. alias ME may be used only at terminal
TT2:).
Displaying Information about a Particular Alias

To display information about a particular alias, use the following format:
SHOW ALIAS alias
where

alias

identifies a particular alias for which information is to be displayed.

For example t if you want information about the alias ME, enter
NCP>SHOW ALIAS ME<RET>
Example of a display:

Alias summary as of 27-NOV-84 17:07
Alias
Name

Scope

Destination

Terminal TT2:

HIRDAL

2-20

DECnet-RSX Guide to User Utilities

2.8 NCP Error Messages
Some common NCP error message~ are listed on the following pages in two
categories: those that are specific to DECnet-RSX and those that are standard
for all DECnet implementations. For a complete list of NCP errors. refer to
the DECnet-RSX Guide to Network Management Utilities.
2.8.1 RSX System-specific Error Messages
NCP - Error reading command

NCP could not read a command from either the terminal or a command file
because of a hardware error or some other unrecognized command read error
condition.
NCP - File privilege violation

The file specified with the TO option in a SHOW command is write protected
against the user of NCP.
NCP - HELP file error -nn

An error occurred while reading one of the NCP HELP files from LB:[1.2].
The variable nn is an FCS error code.
NCP - Invalid device name syntax

The device name in a command file or a TO file specification did not have
valid syntax.
NCP - Invalid directory syntax

The directory identification (UIC) in a command file or TO file specification
did not have valid syntax.
NCP - Invalid file name syntax

The file name in a command file or a TO file specification did not have valid
syntax.

The Network Control Program (NCP)

2-21

NCP - No HELP available

NCP could not find the HEI P file. ~ormally, the HELP files for NCP are
copied to LB:[1,2] as a result of network generation (see the DECnet-RSX
Network Generation and Installation Guide).
NCP - Unrecognized device or unit

The device name or unit number in a command file or TO file specification
could not be found by the RSX operating system.
NCP - Unrecognized file, device, or directory

The file name, device name, or directory (UIC) in a command file or a TO
file specification could not be found by the RSX operating system.
2.8.2 Standard OECnet Error Messages
NCP - Invalid identification format

The identification of the component involved in the requested operation did
not have proper syntax (for example. a nonalphanumeric character was used
in a node name).
This message will include the type of component in error (for example, line,
node, and so forth).
NCP - Invalid parameter grouping

The parameters furnished by the user for the requested operation cannot be
included in a single command.

2-22

DECnet-RSX Guide to User Utilities

NCP • Listener connect failed

The logical link from NCP to the network management listener could not be
established. This error message generally will have one of the following
secondary messages:
Access control rejected

The remote node or network management listener either could not
understand or would not accept the access control information.
Invalid node name format

The executor rejected the format of the remote node name (for example,
the name contained illegal characters or was too long).
Local node shut down

The executor node is in the process of shutting down and will not
accept any more logical link connections.
Network resources

Either the local or the remote node had insufficient network resources
to connect the logical link.
No response from object

The network management listener did not respond. This could be due,
for example, to its responding too slowly or terminating abnormally.
Node unreachable

No path exists to the remote node. or the remote node is not currently
on the network.

The Network Control Program (NCP)

2·23

Object too busy

The remote network management listener had insufficient resources
available to handle the connect request.
Remote node shut down

The remote node is ill the process of shutting down and will accept
no more logical link connections.
Unrecognized node name

The destination node name does not correspond to any known node
address.
Unrecognized object

The remote node does not have a network management listener.
NCP . Listener link disconnected

The logical link from NCP to the network management listener was
unexpectedly disconnected. This error message will have one of the following
error details:
Node or object failed

The network aborted the logical link because either the remote node
or the network management listener terminated abnormally.
Node unreachable

The network aborted the logical link because it could no longer find a
path to the remote node.

2·24

DECnet-RSX Guide to User Utilities

NCP - Operation failure

The requested operation failed For somt: RSX system-specific failures. one of
the following extra text messages may be included.
Insufficient buffer space for additional aliases

The network management software could not internally buffer all the
aliases that could be displayed.
System not loaded

NCP cannot perform the requested function because the DECnet system
has not been installed and the network has not been loaded. See the
system manager to make sure that the system is loaded.
NCP - Parameter missing

The user did not supply a parameter that is necessary for the requested
operation. This message will include the type of parameter missing.
NCP - Parameter not applicable

The user supplied a parameter that is not applicable to the requested operation
on the specified component. This message will include the type of parameter
in error.
NCP - Privilege violation

The user does not have sufficient privilege to perform the requested operation.
NCP - System-specific management function not supported

The requested operation is RSX system specific and is not supported by the
network management listener.

The Network Control Program (NCP)

2-25

NCP . Unrecognized command

NCP does not have the command that the user typed.
NCP . Unrecognized component

The component specified by the user does not exist. This message will include
the type of component in error (for example, line, node. and so forth).
NCP . Unrecognized function or option

The requested operation is not implemented by the executor.
NCP . Unrecognized keyword

One of the keywords in a command is not known by NCP.
NCP . Unrecognized parameter type

One of the parameters given by the user is not implemented by the executor.
This message will include the type of parameter in error.
NCP . Unrecognized value

A parameter value given by the user is not known to NCP.
NCP . Value out of range

A parameter value given by the user is out of the range accepted by NCP.

2·26

DECnet-RSX Guide to l)ser Utilities

3
The Network File Transfer Utility (NFT)

The Network File Transfer utility (NFT) allows you to perform file operations
on accessible network nodes. Certain NFT operations are speciflc to either the
MCR or DCL command language interpreters (CLls). (Users wlth DECnet11M-PLUS and DECnet-Mirco/RSX software now have access to ~FT functions
through DCL.)
Because the NFT utility addresses two types of users (MCR and DCL users).
this chapter is divided into three major sections:
• Section 3.1 describe.;; the NFT file descriptor syntax. the use of wildcards
in file specification~. foreign file formats. and NFT file descriptor defaults.
Both }\IICR and DCL users should read this section.
• Section 3.2 describes. in detail. the NFT operations that can be performed
through the MCR command language. MCR users should read this section.
(Table 3-2 summarizes the NFT operations for MCR users.)
• Section 3.3 describes. in detail. the NFT operations that can be performed
through the DCL command language. DCL users should read this section.
(Table 3-3 summarizes the NFT operations for DCL users.)
In DECnet-RSX systems. the NFT server task is called the File Access Listener
(F AL). F AL performs whatever actions are required of the remote node to
execute the file-handling requests that it receives from NFT (see Figure 3-1).
NOTE

Refer to the DECnet-RSX Release Notes for information
regarding cross-system file operations in the heterogeneous
DECnet environment.
The Network File Transfer Utility (NFT)

3·1

LOCAL

USER
REQUESTING
REMOTE
FILE ACCESS

.-----

LOGICAL LINK

o:::l

*
JJ

CJ)

NFT~DENVER::DATA.NEW=BOSTON::PROGRAM.DAT

(j)

c
0:
<D

o
cCJ)
<D
~

NOTE: NFT and FAL transfer file PROGRAM.DAT from node BOSTON to node DENVER to
create file DATA.NEW. In this example, access control information does not appear in
the NFT command line, since it has previously been entered in an alias node name
block.

;;:

(i)"
CJ)

Figure 3-1: The NFT Utility: File Transfer

TW137

3.1 NFT File Descriptor Syntax
NFT commands operatf: on tHe descriptors that identify files in the network
A file descriptor consists of a node specification and a file specification The
format for a file desc:riptor IS.
[node specification .][file specificatIOn]

3.1.1 Node Specification

A node specification consists of the name of the node and optional access
control information for that node, followed by two colons:
nodename[access-control]: :

where
nodename

IS a 1- to 6-alphanumeric character name that lllcludes at
least 1 alphabetic character. If a node name is an alias that
includes associated access control information, you can omit
all access control fields, as they will default to the Information
associated wIth the alias. For information on how to specify
alias node names, see Section 2.7

access-control

is a user Identification, password, and account specification
(appended to a node name) used to gain access to a remote
file system. Access control information can be specified using
one of the two following formats.
Format 1:

/userid/passwd/accnt: :
Format 2:

"userid passwd accnt"::

where
use rid is a 1- to 16-character string identifying the user at

the remote system.

The Network File Transfer Utility (NFT)

3·3

passwd IS a) to ~ character password needed to gain access
to the rernot.f'. file sy<:;tem
accnt IS a I. to 16-character string used to specify an account
at the remote svstpm. (This field is not used by RSX systems.)
NOTE

When passing access control information to case 'sensitive
systems (for example. ULTRIX-32/ULTRIX-32m systems), you
must use Format 2. shown here. (Format 1 passes access control
information in UPPERCASE.) The embedded spaces in Format
2 are mandatory
Both the interpretation of the access control fields and the access control
mechanism depend on the type of remote system used. If the remote system
is a DECnet-RSX node supporting access control verification. the userid field
is used to specify a valid account by last name or UIC. The passwd string
must be the password for that account. and the accnt field is ignored. For
additional information on access control, see the DECnet-RSX lVetwork
Management Concepts and Procedures manual.
If the remote node does not support access control verification, its File Access
Listener (FAL) will permit either privileged or nonprivileged access control.
For privileged access. use the privileged password that was specified for FAL
during generation of the remote node (the default password is PRIV) and any
desired UIC for the user ID. For nonprivileged access, use the guest UIC and
nonprivileged password specified for F AL during generation of the remote
node. The default nonprivileged user ID and password are [200.200] and
GUEST, respectively. The accnt field can be omitted for both privileged and
nonprivileged access.

3-4

DECnet-RSX Guide to User Utilities

Examples of Node Specifications:

Examples of valid node specIfications follow. l\lissing fields can be omitted
from the right. For example. the nude specification QUEBEC/[310,2]1I can be
written QUEBEC/[310.2]. Missing fields on the left must be marked as missing
by a slash or a blank (depending upon the format used), as shown in the
fourth example.
NOTE

The use of brackets ([]) around the user ID is optional (as shown
in the last two examples). if the user ID is supplied in the
form of a UIC.
NOD E4/[7. 7]/SECRET/ACCNT::
YUKON"5.10 LEFT"::
BOSS/EVERY/ONE::
BOSTONII/ACCNTNE::
NODEl"RMES"::
BILBO/1.lIPRIV::
SHELOB/200,200/GUEST::
3.1.2 File Specification

A file specification identifies either the local or the remote file on which ~FT
is to operate. ~FT can parse many foreign file specifications (see Section
3.1.4). RSX file specifications have the following format:
dev: [ufd]filename. type;ver
NOTE

When you enclose a file specification in quotes. the file spec
string is passed to the remote system in a case sensitive manner.
This is necessary for transferring files to and from case sensitive
systems such as ULTRIX-32/ULTRIX-32m systems.

The Network File Transfer Utility (NFT)

3·5

RSX-l1M-PLUS and Vhcro/RSX system~ support the definition of logical
names for all or part of a file <;pecification The DECnet-RSX FAL can translate
ouly global logical namps. For a di~cussion of logical names and how to define
them, refer to the RSX 11l\;[/M PDUS I/O Operations Reference Manual.
For additional information on RSX files, refer to the RSX-l1 Utilities Manual
For information on how to specify file names that do not conform to RSX
conventions. see Section 3.1.4. For a description of the use of wildcard
characters within file specifiers, see Section 3.1.3.
Depending upon its position in a command string. a file specification is either
an input (source) or an output (destination) file specification. Furthermore. the
node names define the file specification as local or remote. Therefore, NFT
files can fall into four categories:
• Local output files
• Remote output files
• Local input files
• Remote input files
Local or remote output files are files that receive data from an NFT operation,
and local or remote input files are files that contain the data to be operated
on and/or transmitted.
Defaults for DECnet-RSX NFT file descriptors are summarized in Table 3-l.
You can change default values listed in Table 3-1 by using the set default
operation (/DF). See Section 3.2.12.

3·6

DECnet-RSX Guide to User Utilities

Table 3·1: Summary of DECnet·RSX NFl File Descriptor Defaults
Field

Conditions

Default Value

nodename

The file is the first Ol
only file in the input list
or the output list

Local node name.

The file is a subsequent
file In a given list

Preceding node name
specified in the list (including
access control information).

The use rid has been assigned
using an alias node name.
(See Chapter 2 for
information on the NCP SET
ALIAS command.)

Value of userid specified
with the alias node name.

A node name with access
control information has
been specified to NFT using
the IDF (default) switch.

Value of use rid given for
the node name.

The pas,)lI.'d value has been
preassigned using an alias
node name. (See Chapter 2
for information on the NCP
SET ALIAS command.)

Value of passwd specified
with the alias node name.

A node name with access
control information has
been specified to NFT using
the IDF (default) switch.

Value of passwd given for
the node name.

userid

passwd

(continued on next page)

The Network File Transfer Utility (N FT)

3·7

Table 3·1 (cont.): Summary of DECnet·RSX NFT File Descriptor Defaults
Field

Conditions

Default Value

accnt

The accounting number has
been preassigned using an
alias node name. (See
Chapter 2 for information
on the NCP SET ALIAS
command.)

Value of accnt specified
wi th the alias node name.

A node name with access
control information has
been specified to NFT using
the IDF (default) switch.

Value of accnt given for
the node name.

The file is the first or
only file in an input list
or an output list
associated with a
particular node.

SY: device associated with
the access control given
wi th the specified node
name. If no node name is
given, it defaults to the user's
current SY: device.

The file is a subsequent
file in a given list, as
defined above.

Preceding device specified
in the list.

A device has been specified
to NFT using the ID F
(default) switch.

Device specified in the 10 F
command.

The file is the first or
only file in an input
list or an output list
associated with a
particular node.

Directory associated with
the access control given
with the specified node
name. If no node name is
given, it defaults to the user's
current directory.
(RSX-I1M-PLUS and
Micro/RSX systems now
support named directories.)

del)

ufd

(continued on next page)

3·8

DECnet-RSX Guide to User Utilities

Table 3·1 (cont.): Summary of DECnet·RSX NFT File Descriptor Defaults
Field

Conditions

Default Value

filename

The file is the fi rst or
only file in the input list.

None.

The file is a subsequent
file in the input list.

Preceding file name
specified in the list.

The file is an output file.

N arne of
input file.

The file is the first or
only file in the input list.

None.

The file is a subsequent
file in the input list.

Previous type specified in the
list.

The file is an output file.

Type of corresponding input
file.

The version number is
omitted for any input file.

Highest version of file.

The version number is
omitted for an output file.

If a version number was
specified for the input
file (either wild or explicit), the
output file will have the
corresponding version number.

type

ver

the corresponding

If a version number was not
specified for the input file,
then no version is used on the
output file. On RSX systems
this results in the highest
version being used.

The Network File Transfer Utility (NFT)

3-9

If you are using a format that IS not described here, you should enclose the
foreign file directory and file specification with double quotes, for example.
"filespecification". This directs NFT to transmit the file specification to the
foreign node without checkIng its syntax or applying defaults for missing
fields. File specifications within double quotes are not used in determining
, default values for output files
NOTE

When you enclose a file specification In quotes. the file spec
string is passed to the remote system in a case sensitive manner.
This is necessary for transferring files to and from case sensitive
systems such as ULTRIX-32/ULTRIX-32m systems.
The use of wildcards in foreign file specifications is subject to the restrictions
of the foreign operating system. The use of wildcards in RSX -11 file
specifications is described in the following section.
3.1.3 Wildcards in NFT File Specifications

NFT allows you to type wildcards (asterisks and/or percent signs), within file
specifications for existing local or remote files located on DECnet-RSX systems.
Wildcard specifiers that are not accepted by NFT can be used for remote files
if they are enclosed in quotes (as described in Section 3.1.2).
An asterisk C') inserted in a field means that any value will be accepted wi thin
that field. Allowable wildcard field specifiers are listed below:
[*.m ]filename. type ;ver

means all group numbers will be accepted.

[g, *]filename.type;ver

means all member numbers will be accepted.

[*]filename,type;uer

means all named directories will be accepted.

[g,m ]*.type;ver

means all file names will be accepted.

[g,m]filename. *;uer

means all file types will be accepted.

[g ,m ]filename. type; *

means all version numbers will be accepted.

3-10

DECnet-RSX Guide to User Utilities

In addition, except when renaming files (see the rename operation, Section
3.2.11), NFT permits wildcard specifiers for part of a field in the file name
and file type, as defined here'
• An asterisk in a portion of a field means that that part of the field can
be replaced with any characters of any length (including none). For example,
SOME*.TYP will accept:

S01iE.TYP
SOMETHG.TYP
SOMEBODY.TYP
SOMEBZ.TYP

• A percent sign (%) in a character position means that anyone character
will be accepted in that position (nulls are not permitted). RSTS/E uses the
question mark (?) rather than the percent sign to indicate a single position
wildcard. For example.
MAIL%.MAI will accept:

MAlL1.MAI
MAIL2.MAI
MAlL3.MAl
MAIL4.MAI

IMV%l%%.TXT will accept:

l11V1I22.TXT
IMV2130.TXT
111V3I45.TXT

Multiple wildcard specifiers can be combined in a single file specifier. as shown
in the following examples:
* *.*

means all versions of all files under the same DIC.

TEST.*;*

means all versions and all types of files named TEST.

TEST*.DAT;*

means all versions of files having names beginning with
TEST and being of type D AT.

TEST%.*

means the most recent version of all file types for files with
5-character names beginning with TEST.

The Network File Transfer Utility (N FT)

3·11

Sample command line:

NFT>ELROND/TERRI/ACCT

DBO' [100 1]=D~1 [*.10]FIL%%.MAC<RET>

In this sample. all files that meet, the following qualifications are transferred
to node ELROND'
• Files located on device DM 1: on the local node
• Files listed under any group number for UFD member 10
• Files having a 5-character file name beginning with the characters FIL
• Files having the file type MAC

3.1.4 Foreign File Formats

Files that reside on non-RSX nodes are referred to as foreign files and must
use syntax compatible with the systems on which they are located, NFT has
the ability to parse the foreign file formats listed here:
Directory formats:

File specification formats:

[ufd]

lAS

[directory]

VMS

filename,type;ver lAS, VMS
filename,type ver TOPS-20,

VMS
[ppnJ or (ppn)

RSTS/E

filename,type RT-11. RSTS/E

TOPS-20. VMS

Ipathnamelfilename

ULTRIX-32, ULTRIX-32m
(not applicable)

RT-ll

Ipathname

UL TR I X-32/ULTRIX -32m

3-12

DECnet-RSX Guide to User Utilities

NOTE

An ULTRIX-32/UL TRIX-:~2m directory is specified by a path
name. such as lusr/users/buckley where "/" denotes the root.
An ULTRIX-32/ULTRIX-32m file specification must be enclosed
in quotation marks in order to be passed to a remote system
in a case sensi ti ve manner.
Examples
VMS:

SYS$SYSDISK:[MITTON .DAP]DAPV70.MEl\f;69
TOPS·20:
PS:[~IITTON]MAIL.TXT.1439

RSTS/E:

SY :(1,4)SYSTEM .HLP
RT·11:

DK:TECO.SAV
UL TRIX·32/UL TRIX·32m

II/usr/users/buckley/main.c"

The Network File Transfer Utility (N FT)

3·13

3.2 NFT Operations for MeR Users
MeR NFT operations act on primary switches which specify the operation to
be performed (for example. lAP specifies the append operation). Some MeR
NFT operations have optional qualifying switches that further define the action
of the primary switch (for example, when IAS/AP are appended to an input
file specification, the lAS qualifying switch causes the input file to be appended
to an output file in ASCII record mode). The ~ICR NFT operations are
summarized in Table 3-2. Sections 3.2.4 - 3.2.15 describe each MCR NFT
operation in detail.
3.2.1 Rules for Specifying MCR Switches in a Command Line

MCR primary switches can be inserted anywhere in a command line.
MCR qualifying switches fall into one of two categories, each having different
rules for insertion in a command line:
1. Command Qualifying Switches. Command qualifying switches do not affect
input or output files and, therefore, can be specified anywhere III a command
line.
2. File Qualifying Switches. File qualifying switches apply only to each specific
input file to which they are appended. When file qualifying switches are
specified for an output file, the switch (or switches) achieves global status,
and becomes the default for all input file(s) in the command, unless overridden
on a per file basis.
3.2.2 NFT Command Line Continuer

You can continue an NFT command line onto an additional input line by using
a hyphen (-) before the line terminator (see the example below). The hyphen,
followed by the terminator «RET», acts as a command line continuer. A
command line continuer causes NFT to prompt you for the remainder of the
command line. You can insert a continuer at any point in a command line,
and you can use any number of continuing lines within a command.
Example:

NFT>NODEX/[200,30]/DECNET: :DTO: [BUCKLEY]MAGIC.MAC;3=-<RET>
NFT>NODEY/200,10/PASME: :SYO:[30,60]MYSTIC.MAC;2<RET>

3-14

DECnet-RSX Guide to User Utilities

Table 3-2:

Summary of NFT Operations for MeR Users

NFT
Operation

MCR Primary
Switch

MCR Qualifying
Switches

(Scope of

Append: The append operation

lAP

lAS
lAX
IBK
11M
IPRISY lOW IGR/WO
IPR/FO:[uic]
lRAT:MACYll
IRC
ISP
ILO
INM

(file)
(file)
(file)
(file)
(file)
(file)
(file)
(file)
(file)
(cmd)
(cmd)

default

lAS
lAX
IBK
ICO
11M
INV
IPRISY lOW IGR/WO
IPR/FO:[uic]
lRAT:MACYll
lRAT:NOSPAN
IRC
ISB
ISP
ISU
ILO
INM
IME

(file)
(file)
(file)
(file)
(file)
(file)
(file)
(file)
(file)
(file)
(file)
(file)
(file)
(file)
(cmd)
(cmd)
(cmd)

Delete: The delete operation
deletes one or more files.

IDE

ILO
INM

(cmd)
(cmd)

Directory: The directory

III
IBR
IFU
IAT
ILO
INM

(cmd)
(cmd)

adds files to the end of an
existing file.

Copy: The copy operation

transfers one or more existing
files to one or more files on
the local or remote node.

operations list a directory of one or more files.
Execute: The execute operation
executes a command file stored on
a remote or local node.

lEX

Qualifier)

(continued on next page)

The Network File Transfer Utility (NFT)

3·15

Table 3-2 (cont.):

Summary of NFT Operations for MeR Users

NFT
Operation

MCRPrimary
Switch

Help: The help operation

IHE
HELP [subject]

(Scope of

MCR Qualifying
Switches

Qualifier)

INV
ILO
INM

(file)
(cmd)
(cmd)

IPR[:n]

ISY
lOW
IGR
IWO
IFO:[uic]
ILO
INM

(file)
(file)
(file)
(file)
(file)
(cmd)
(cmd)

Spool: The spool operation
spools files to a line printer
for printing.

ISP

lAS
lAX
IBK
11M
INV
IRC
ISU
ILO
INM

(file)
(file)
(file)
(file)
(file)
(file)
(file)
(cmd)
(cmd)

Submit: The submit operation

15B

lAS
lAX
IBK
11M
INV
IRC
ILO
INM

(file)
(file)
(file)
(file)
(file)
(file)
(cmd)
(cmd)

displays a descriptive message
about switches and commands.
Identify: The identify

110

operation identifies the version
of NFT being used.
Rename: The rename operation

IRE

changes the name of an existing file.
Set defaults: The default

10F

operation sets certain default
values for input and output files.
Set protection: The protect

operation sets or changes a
file's protection status
depending on the qualifying
switch (lSY:p, IOW:p,
IGR:p, IWO:p) and its
setting (p = R, W, E, D).
The IFO qualifying switch
specifies the file owner.

copies a command file to a
local or a remote node,
executes the file, and then
deletes it.

3·16

DECnet-RSX Guide to User Utilities

3.2.3 Definition of MeR Qualifying Switches
lAS

The ASCII switch transfers files in ASCI I record mode. For remote
output files. NFT translates the records in the file into an appropriate
format for the remote system For local output files. the file is created
as a variable length format implied LF-CR attribute file.
The lAS switch should be used only if translation is desired. File
transfers to remote nodes that have similar file systems (for example.
VMS) are more efficiently handled in image block mode (the default
transfer mode).

lAX

The automatic transfer selection switch causes NFT to use its default
algorithms in selecting the mode in which to transfer a file to a remote
node. NFT will try to select either block mode or record mode to
transfer a file, based on the remote FAL capabilities. Since automatic
transfer selection is the default mode of transfer, you will want to use
the lAX switch to override a specified mode of tr'ansfer.

IBK

The block mode switch transfers files using 5I2.-byte blocks, which is
a more efficient method than the usual record mode transfer, Block
mode can be used with any file organization type on transfers to other
Files-II or RMS-Il systems that support block mode transfers (for
example. RSX. VMS. or the RSTS/E RMS F AL). When transferring
files to or from a foreign file system using block mode. there is no
guarantee that the files will be usable. since all systems do not store
records compatibly.

ICO

The contiguous output switch creates an output file with contiguous
allocation.

11M

The image switch transfers files while retaining their current format
and attributes. Some remote systems may not support the transfer.
causing an error message to be displayed. If the file is ASCII text.
you can recover by using the lAS switch. If the transfer was aborted
due to unsupported file organization. you can retry the transfer using
the IBK switch.

The Network File Transfer Utility (NFT)

3·17

INV

The new version switch specifipf., that an output file will have the same
or latest version number, whichever is higher. However. the effect of
the INV switch depends on the version number support on the remote
system. For example, RT-ll and RSTS/E do not support version
numbers. and therefore, this switch would be -ignored on those systems.
The negative version of the INV switch (I-NV) specifies that an output
file will retain the current version number. If another file with the
same version number already exists, an error may result

IPRISY IOW/GR/WO

The protection switch (/PR) allows a file's protection
status to be set or changed. File protection is
provided at four levels (/SY:p. IOW:p. IGR:p. IWO:p):

• ISY: (System) specifies file access that you allow to the system UIes (that

is. UICs with group numbers of 10 octal or less).
• lOW: (Owner) specifies file access that you allow to yourself.
• IGR: (Group) specifies file access that you allow to other members of your

group.
• IWO: (World) specifies file access that you allow for all other UICs.

The p variable signifies the protection settings R. W. E. and D. The R. W.
E, and D protection settings specify whether each level can read. write. extend,
or delete a file, respectively. (See Section 3.2.13 for a full description of the
set protection operation.)
IFO:[uic]

The file owner switch allows you to specify the owner
of an output file.

IRAT:MACY11

The l\IACYll switch causes a file to be stored in
MACYll format on a TOPS-10 or TOPS-20 system.

IRAT:NOSPAN

The no span blocks switch specifies that the ouput
file will not span block boundaries.

IRC

The record mode transfer switch directs NFT to transfer a file one
record at a time, instead of using block mode. You would use the IRC
switch when copying to unit record equipment or to override NFT's
default selection of the transfer mode.

3·18

DECnet-RSX Guide to User Utilities

Isa

The submit switch submit~ a file to a batch or indirect command file
processor on a local or a remote node, executes the file, and then
deletes it.

ISP

The spool switch directs a file to a line printer on a local or remote
node for printing. When a file is spooled to a remote node, its format
must be compatible with the remote system. (See Section 3.2.14 for a
full description of the spool operation.)

ISU

The supersede switch transfers one or more files to a file whose file
name, type, and version number already exist in a user file directory
(UFD). The existing file is deleted, and a new file is created with the
data from the input file(s). The new file retains the current file name,
type, and version number that are in the directory, but the file ID is
new.
If an error occurs during the file transfer, both the new output file
and the one it is replacing will be lost.

ILO

The log switch displays the names of files (copied. deleted. and so
forth) as the operation is performed. The log switch applies to all files
involved in the current command.

INM

The no messages switch suppresses output messages that would
otherwise display at your terminal during NFT operations.

IME

The merge switch merges two or more input files into one output file.
If you specify wildcards in one or more fields of the output file
specification, the IME switch causes the resulting output file
specification to contain the information found in the corresponding
fields of the first input file specification in the command line.

The Network File Transfer Utility (NFT)

3-19

3.2.4 The Append Operation
MeR Primary Switch: lAP

The append operation adds the contents of one or more input files to the end
of an existing output file. The output file retains its original attributes
independent of the attributes of the input file(s). However. if the attributes
of the input files are different from the attributes of the output file, the
append operation will appear to succeed, but the resulting output file may not
read correctly.
Format:

NFT>outfile[/sw] = infile(s)[/sw]/AP

where
outfile

is the output file descriptor. No wildcard specifiers are allowed in
the output file descriptor. The file type and record attributes are
taken from the existing file. The file name and file type for the
output file must be explicitly specified.

infile(s)

is one (or more) input file descriptor(s).

3·20

DECnet-RSX Guide to User Utilities

Isw

is one (or more) of thf> following qualifying switches (defined in
Section 3.2.3):
File Qualifying Switches

Command Qualifying Switches

lAS
lAX
IBK

ILO
INM

11M
IPRISY/OW/GR/WO
IPR/FO:[uic]
IRAT:MACYll
IRC
ISP
NOTE

Refer to Section 3.2.1. which contains the rules for
specifying both file and command qualifying switches
in a command line.
Example:

NFT>LOWELL: :DK1:FIL1.DAT;1=ESTER: :FIL2.DAT;1/AS,YUKON: :-<RET>
NFT>FIL3.DAT;1/AS/AP<RET>
In this example. FIL1.DAT;l, which is stored on DKl: at node LOWELL, is
opened. FIL2.DAT;1, located at node ESTER, and FIL3.DAT;1. located on
node YUKON. are then appended to FIL1.DAT;l in ASCII record mode.

The Network File Transfer Utility (NFT)

3-21

3.2.5 The Copy Operation (File Transfer)
MCR Primary Switch: (delault operation)

The NFT copy operation can transfer files in the following ways:
• Single file transfer. Transfers a single file from one node to another.
• File transfer with concatenation. Transfers more than one input file. from
the same or different nodes, to create a single output file.

The attributes of the output file are determined by the attributes of the
first input file that you specify in the command line. If the attributes of
the input files differ, the concatenation may appear to succeed, but the
output file may not be correctly readable.
• Multiple file transfer. Transfers more than one input file to the same number
of output files so that each input file has a corresponding output file.

If an error occurs during transfer, NFT or the remote FAL (File Access
Listener) attempts to delete the output file.
Format:

NFT>[outfile][/sw] = infile(s)[lsw]
where
outfile

is an optional output file descriptor to which the input file(s) are
copied.

infile(s)

is one (or more) input file descriptor(s).

3-22

DECnet-RSX Guide to User Utilities

Isw

is one (or more) of the following qualifying switches (defined in
Section 3.2.3):
File Qualifying Switches

Command Qualifying Switches

lAS
lAX
IBK
ICO
lIM
INV
IPRISY/OW/GR/WO
IPR/FO:[uicj
IRAT:MACY11
IRAT:NOSPAN
IRC
ISB
ISP
ISU

ILO
INM
IME

NOTE

Refer to Section 3.2.1, which contains the rules for
specifying both file and command qualifying switches in
a command line.
Example 1: Single file transfer

NFT>=YUKON: : THURS. TXT<RET>
In this example, the file THURS. TXT, located on remote RSX node YUKON,
is transferred to the local node. Because no output file name is specified, the
output file name will be THURS.TXT. Access control information is not
specified for either the local node or node YUKON. Therefore, missing fields
are assumed to be defined either in the respective default node names or in
alias node names.

The Network File Transfer Utility (N FT)

3-23

Example 2: Single file transfer between remote nodes

NFT>NODEX/[200,30]/DECNET: :DKO: [BUCKLEY]MAGIC.MAC;3=-<RET>
NFT>NODEY/200,10/PASME: :SYO: [30,60]MYSTIC.MAC;2<RET>
In this example, the file MYSTIC.MAC;2, located on NODEY, an RSX-ll
node, on the system device under UFD [30,60] is transferred to NODEX. also
an RSX-ll node. The file is renamed MAGIC.MAC;3. and is stored on DKO:
in the UFD [BUCKLEY]. Access control information is passed in the input
file specifier to allow access to MYSTIC.MAC. Access control information is
required for the creation of output file MAGIC.MAC. (Note the use of the
command line continuer for the additional input line.)
Example 3: Single file transfer using a foreign file

NFT>NODEA: :MARY.MAC=NODEB: :SYS$SYSTEM:BOOTS.EYE<RET>
In this example, the foreign file BOOTS.EYE, located on NODEB, a VMS
node. is sent to NODEA, an RSX-ll node. On NODEA. the file is named
MARY.MAC (latest version) and is stored on NODEA's system device (SYO:)
under the current UIC. Because access control information is not specified for
either NODEA or NODEB. the default values for these missing fields are
assumed to be defined for each node in an alias node name or to be previously
defined by the set default operation (/DF).
In addition to the access control information, the dev. ufd. and ver arguments
are also omitted for NODEB. Their default values are determined by the syntax
conventions of NODEB's operating system. Keep in mind that NODEB is a
foreign node. Therefore, it is possible that much of the file descriptor
information discussed is not even required by NODEB. (You should refer to
Section 3.1.4 to determine what foreign file specification format is required.)
If, however. you omit any required argument in the command line and do not
adhere to default regulations. you will receive an error message.

3-24

DECnet-RSX Guide to User Utilities

Example 4: Transfer with file concatenation

NFT>NODEA: :DT1: [SO,10]SUM.TIM=NODEY :DKO: [SO,10]-<RET>
NFT>SAM.LIT,ONE.WAY<RET>
In this example, SAM.LIT and ONE.vVAY located on RSX NODEY. are
transferred to RSX NODEA. The two input files are concatenated into a single
output file named SUM.TIM. which is stored on DECtape under UFD [50,10].
Notice how ONE.WAY inherits default values from the information specified
for SAM.LIT. (ONE.WAY and SAM.LIT are located on NODEY on DKO:
under UFD [50.10).) Access control information for both NODEA and NODEY
is assumed to be defined in either the respective default node names or in
alias node names.
Example 5: Multiple file transfer

NFT>NODEA: :=NODEB/[FRASER]/MULTI: :-<RET>
NFT>DXO:BEE.FIL/AS,CEE.FIL/AS,DEE.FIL/AS<RET>
In this example. BEE.FIL. CEE.FIL, and DEE.FIL are transferred to NODEA
in ASCII record mode and stored under their original names (the output file
names default to the input file names). Specifying an output file name would
cause concatenation rather than multiple file transfer (see Example 4).
When you transfer multiple files, all input files must be sent to the same
node. However, the input files can be accessed from different nodes.
Example 6: Multiple file transfer using wildcards

NFT>=BOSTON/310,2/MGR: :*.*<RET>
In this example, all files on RSX node BOSTON, in the account associated
with UFD [310.2] and password MGR, are transferred to the local node. All
files retain their original names.
NOTE

The use of brackets ([]) around the user ID is optional (as shown
in the preceding example). if the user ID is supplied in the
form of a UIe.

The Network File Transfer Utility (N FT)

3-25

3.2.6 The Delete Operation
MCR Primary Switch: IDE

The delete operation delete~ one or more specified files. located on the same
or different nodes.
Format:
NFT>filedescriptor(s)[1 sw ]/D E

where
filedescriptor(s)

is any valid file descriptor(s), as defined in Section 3.1. The
version number must always be specified for files deleted
on RSX nodes.

/sw

is one (or both) of the following qualifying switches (defined
in Section 3.2.3):

File Qualifying Switches

Command Qualifying Switches

(Not Applicable)

ILO
INM

NOTE

Command qualifying switches do not affect input or output files and,
therefore, can be specified anywhere in a command line.
On RSX systems, if there is a wildcard (* or %) in the file name or type, the
version number must be explicit or wildcard (that is, it cannot be 0 or -1).
Example:

NFT>MAIN: :DK: [100,10]TAX.LST;5,BUDGET.LST;1/DE<RET>

This command line deletes the files TAX.LST;5 and BUDGET.LST;1.

3·26

DECnet-RSX Guide to User Utilities

3.2.7 The MeR Directory Operations
Directory Switches:

ILI[ :width]
IFU[:width]
fAT
IBR

MeR has four types of file directory listings. The ILL fFU, fAT, and fBR
switches are used to obtain each type of directory listing and are described
here:
• fLI (list switch) lists a directory consisting of the name, size. creation date.

and optional contiguous and locked indicators for files on a remote node.
• fBR (brief listing switch) lists a directory containing only the names of files
located on a remote node.
• fFU (full directory listing switch) lists a full directory for files on a remote
note. This list consists of name, size, creation date, optional contiguous and
locked indicators. owner. protection, data last modified. and revision number.
• fAT (attributes listing switch) displays the attributes for each file in a
directory listing. This display includes the file organization, record format,
and record attributes. as well as the information included in a full (lFU)
directory listing.
Format:

NFT> [outfile = ]infile(s)

LI[:Width]}
fFU[:width]
fBR
{ fAT

where
outfile

is the optional file descriptor to which the directory will be written.
If omitted, the output defaults to TI:.

infile(s)

is the file descriptor for each file for which you want directory
listings. If no file name or type is specified in the descriptor. you
will receive a directory listing of all files.

The Network File Transfer Utility (NFT)

3·27

ll'idth

is a decimal nUlnber that specifies the width of the listing. The
default value is 72. At least one field is always displayed per line,
even if that field exceeds the maximum width specified.

Example 1: The List Switch (ILl)

NFT>X: :DBO: [SMITH]/LI<RET>

The directory of DBO:[SMITH] on node X is displayed on TI: as shown here:
Directory X: :DBO: [SMITH]
3-FEB-83 13:26:02
X.MAC;3
X.OBJ;4
X.TSK;2
Y.TSK;3

2./2.
1./1.

4./4.
0./0.

29-JAN-83 17:46:23
29-JAN-83 17:46:34
C 29-JAN-83 17:46:51
CL 29-JAN-83 17:47:08

where the ordering of the fields from left to right is file name, blocks
used/allocated, [contiguous indicator], [locked indicator], and creation date and
time. All fields may not be displayed for all systems.
Example 2: The Brief Listing Switch (/BR)

NFT>X: :DBO: [7,7]/BR<RET>

The directory of DBO:[7,7] on node X is displayed on TI: as follows:
Directory X: :DBO: [7.7]
3-FEB-83 13:21:22
X.LST;3
X.MAC;3
X.OBJ ;4
X.TSK;2

Foreign file name formats may differ; for example, RT-ll file names do not
have version numbers.

3-28

DECnet-RSX Guide to User Utilities

Example 3: The Full Directory Listing Switch (IFU)

NFT>X: :DBO: [7,7]/FU<RET>

The directory of DBO:[7,7] on node X is displayed on TI: as shown here:
Directory X: :DBO: [7,7]
3-FEB-83 13:27:39
X.DBJ; 4
[7,7]

1./1.

[RWED,RWED,RWED,R]

29-JAN-83 17:46:34
01-FEB-83 09:58:32(2.)

where the ordering of the fields from left to right by line is:
First Line

Second Line

file name
blocks used/allocated
creation date and time

file owner (DIC)
file protection
last modified date and time revision number

If the file is stored on contiguous blocks, an uppercase character C appears
to the left of the creation date, as shown in the example below.
X.TSK;2
[7,7]

4./4.

[RWED,RWED,RWED,R]

29-JAN-83 17:46:51
01-FEB-83 09:58:36(2.)

If the file is locked, an uppercase L appears to the left of the creation date
(see previous example for the /LI switch). (Not all fields are displayed for all
file systems; for example, RT-ll directories do not include the file owner and
the modification date and time.)

The Network File Transfer Utility (NFT)

3·29

Example 4: The Attributes Listing Switch (fAT)

NFT>ELROND: :LOGIN.CMD/AT<RET>

The attributes of the file LOG IN .CMD:22 on node ELROND are displayed:
Directory DBO: [DALEY]
15-JUN-83 12:00:06
LOGIN.CMD;22
Size:
Owner:

File protection:
File organization:
File attributes:
Record Format:
Record attributes:

3-30

2./2.
[DALEY]

Created: 15-JUN-1983 10:40
Revised: 15-JUN-1983 10:41 (2.)
Expires: 31-DEC-1983
System: RWED, Owner:RWED, Group:R, World:
Sequential
Allocation=2, Extend=O
Variable length, no maximum defined
Carriage return

DECnet-RSX Guide to User Utilities

3.2.8 The Execute Operation
MCR Primary Switch: lEX

The execute operation executes the contents of a command file located on a
local or remote node. For RSX systems. the command file can be submitted
to either a command file processor or a batch file processor. depending on
how the destination node's command file submission task (MCM) was generated
during NETGEN. If you want to execute a command file that does not already
exist on a remote node. you must use the submit operation (see Section 3.2.15)
to copy the command file to the remote node. and subsequently submit the
file for execution.
The success of the execute operation does not guarantee that the batch or
command file was executed successfully, only that the execution request was
given successfully to the MCM.
Format:
NFT>commandfile(s )[/sw j/EX

where
commandfile(s)

is the output file descriptor(s) for each remote node command
file that you want to execute. Command files are not deleted
after execution.

Isw

is one (or both) of the following qualifying switches (defined
in Section 3.2.3):

File Qualifying Switches

Command Qualifying Switches

(N ot Applicable)

ILO
INM
NOTE

Command qualifying switches do not affect input or output files
and. therefore. can be specified anywhere in a command line.
Example:

NFT>WASH: :DBO:[200.200]NAMES.CMD/EX<RET>
In this example, the command file NAMES.CMD is to be executed on node
WASH.

The Network File Transfer Utility (NFT)

3·31

3.2.9 The Help Operation

MeR Primary Switch:

IHE
HELP[sub;ect]

The NFT help operation displays information on how to use NFT. To print
the list of subjects for which there is help information available. type either
version of the switch:
Format:

NFT)/HE
NFT)HELP

To obtain information about one of the subjects listed. type
NFT) HELP[sub;ect]
Example:

NFT>HELP TRANSFER<RET>
This help request displays text describing the syntax for transferring files.
Help files must be located on device LB:[1,2]. If they are not on this device,
you will get the following message:

NFT - No HELP Available

If your help files are not on the proper device, consult your system manager.

3-32

DECnet-RSX Guide to User Utilities

3.2.10 The Identify Operation

MeR Primary Switch: liD

The identify operation displays the current NFT and NF ARs version numbers
on your terminal. The type of operating system and file support for your node.
as well as the DAP buffer size. are also displayed. If a remote node is specified
in the command, information is displayed for the remote F AL.
Format:

NFT>[node specification::]/ID
where

node specification is a remote node name and access control information (see
Section 3.1 for information on specifying node names and access control
information).
Example 1: Local Node

NFT>/ID<RET>
NFT - Version 4.1
Local NFARs V4 DAP V7.0

Buffer size=528.

OS=RSX-11M-PLUS

FS=FCS-11

OS=RSX-11M-PLUS
OS=RSX-11M-PLUS

FS=FCS-11
FS=RMS-11

Example 2: Remote RSX Node

NFT>ELROND: :/ID<RET>
NFT - Version 4.1
Local NFARs V4 DAP V7.0
Remote FAL V2 DAP V7.0

Buffer size=528.
Buffer size=550.

Example 3: Remote VMS node

NFT>BERGIL: :/ID<RET>
NFT - Version 4.1
Local NFARs V4 DAP V7.0
Remote FAL V4 DAP V6.0

Buffer size=528. OS=RSX-11M-PLUS FS=FCS-l1
Buffer size=4160. OS=VAX/VMS FS=RMS-32

The Network File Transfer Utility (N FT)

3·33

3.2.11 The Rename Operation
MeR Primary Switch: IRE

The rename operation changes the name(s) of the input file(s) to that of the
output file specifier. The new file name is entered into the new directory and
the existing or current file name(s) are deleted from the old directory. Because
no data is transferred on a rename operation, both directories must be on the
same node and same device. Since the operation is performed on the source
node. access control information need be given for the input file(s) only. If
the rename is to a different directory, the target directory must also allow
access. (Some systems do not support the D AP rename operation. Refer to
the Introduction to DEenet or to the individual system documentation for
more information.)
Format:
NFT>outfile[1sw] = infile(s)[1sw ]/RE

where
outfile

is the file specification to be given to the new file. (See Section
3.1.2 for a description of the file specification format.) Each
individual file name, type. and version number can be explicit,
wildcard (*), or defaulted (null), with two restrictions:
• If there is a wildcard (*) in the file name or type. the version
number must be explicit or wildcard (that is. it cannot be 0 or
-1).

• Partial field or single character wildcard specifiers are not allowed
for outfile.
When a field is wildcard or defaulted, the corresponding field of
the input file is used. Thus, one or more fields can be changed
while preserving the others. (See Section 3.1.3 for more
information on wildcard specifications.)

3·34

DECnet-RSX Guide to User Utilities

infile(s)

is the file descriptor of the file(s) to be renamed.

Isw

is one (or more) of the following qualifying switches (defined in
Section 3.2.3):

File Qualifying Switch

Command Qualifying Switches

INV

ILO
INM
NOTE

Refer to Section 3.2.1. which contains the rules for specifying
both file and command qualifying switches in a command line.
Example 1:

NFT>REM: :DB3:[100,l]NEWNAME,FIL=REM/ACCOUNT/PASS: :-<RET>
NFT>DB3: [100.1]OLDNAME.FIL/RE<RET>

The example changes the name only. from OLD NAME .FIL to
NEWNAME.FIL.
Example 2:

NFT>BILBO: :DL1: [FRASER]SONGS.OLD=BILBO: :-<RET>
NFT>DL1:[BUCKLEY]SONGS.NEW/RE<RET>

This example changes both the name and the directory; no file data is moved.

The Network File Transfer Utility (NFT)

3-35

3.2.12 The Set Default Operation
MeR Primary Switch: IDF

The set default operation allows you to define your own default values for
various arguments in a file descriptor. Using the IDF switch. you can set
default values for node names (complete with access control information),
devices, and UIes. However. the file name, type, and version number cannot
be assigned default values. Default values can be set for input files by
specifying IN, and for output files by specifying OUT. You can define the
same default values for both input and output files by using one command
and omitting the IN/OUT arguments. Defaults remain in effect for subsequent
files until they are changed or until you exit from NFT.
Format:

:IN

NFT>[defaults]/DF
:OUT
where

defaults

is any string of default argument values that you wish to define
in the command line. If omitted, NFT displays the last defaults
set.

:IN

is the input file specifier. When appended to the IDF switch,
:IN indicates that all default values defined by the command
apply to input files only.

:OUT

is the output file specifier. When appended to the IDF switch,
:OUT indicates that all default values defined by the command
apply to output files only.

3~36

DECnet-RSX Guide to User Utilities

Any file descriptor arguments that are not set with the IDF switch are defined
by the standard NFT defaults listed in Table 3-1. If you want to know which
defaults are currently defined, type the- .following command:
NFT>/DF<RET>

NFT will display the current default values at your terminal.
Example:

NFT>MASTER/GUMBO/BLUE:: [4,5]/DF:IN<RET>
NFT>TI:/DF:OUT<RET>
NFT>=TIN.MAN<RET>

In this example, input arguments (node name, access control, and UIC) and
an output argument (device) are defined for subsequent files. The command
NFT> =TIN.MAN assumes the following input and output file descriptors:
NFT>TI: = MASTER/GUMBOIBLUE::[4,5]TIN.MAN
If you wished to know the defaults set in this example, IDF would print the
following itemization in response to NFT>/DF<RET>:

Input defaults = MASTER/GUMBO/ ... : [4,5]
Output defaults =TI:

Notice that the default password is printed out as ellipses (... ) to maintain
security.

The Network File Transfer Utility (N FT)

3·37

3.2.13 The Set Protection Operation

MeR Primary Switch:

IPR[:n]
[/SY:p]
[I0W:p]

[IGR:p]
[IWO:p]

The set protection operation sets or changes a file's protection status. File
protection is provided at four levels (/SY:p, IOW:p, IGR:p, IWO:p):
• ISY:p (System) specifies file access that you allow to the system VIes (that

is, DIes with group numbers of 10 octal or less).
• IOW:p (Owner) specifies file access that you allow to yourself.

• IGR:p (Group) specifies file access that you allow to other members of your

group.
• IWO:p (World) specifies file access that you allow for all other VIes.

The p variable signifies the protection settings R, W, E, and/or D. The R,
W, E, and D protection settings specify whether each level can read, write.
extend, or delete a file. respectively. The R, W, E, and/or D protection settings
apply to all input files in a command line. unless overridden.
To alter the protection level of a file, you can use either the IPR qualifying
switches (/SY:p, IOW:p, IGR:p. IWO:p) or an octal representation (lPR:n). In
either case. if you are the file owner or have a system level VIC, you can
alter the protection level without having read or write access. However, because
the protection level of a file is a protected attribute, you cannot alter the
protection level if you are in the group or world category for the file owner's
VIC. (You can read protected attributes if you have read access.)

3-38

DECnet-RSX Guide to User Utilities

Format:
NFT>filedescriptor(s )/PR[:n ][/SY:p ][/OW:p ][/G R:p ][/WO:p ][/FO:uic][1 sw]

where
filedescriptor(s)is the file descriptor(s) for each file it" the command line.
IPR

is the protect switch.

is an optional octal value that can be used to specify the
protection status. (For a list of the possible octal codes and
their meanings, refer to the RSX-IIM or RSX-llM-PLUS
Pocket Guide.)

ISY:

is the system level protection qualifying switch (defined here
and in Section 3.2.3).

lOW:

is the owner level protection qualifying switch (defined here and
in Section 3.2.3).

IGR:

is the group level protection qualifying switch (defined here and
in Section 3.2.3).

IWO:

is the world level protection qualifying switch (defined here and
in Section 3.2.3).

is R. W. E. and/or D, signifying the type of access that is to
be allowed. R, W, E, and D signify the following types of
access:
R - read allowed

E - extend allowed

W - write allowed

D - delete allowed

Only those types of access that you specify (R. W. E. andlor
D) will be allowed; all others remain protected. If you specify
one of the four qualifying switches. (/SY:p, IOW:p, IGR:p,
IWO:p), but do not specify a value for p. no access is allowed
at the level of that qualifying switch.

The Network File Transfer Utility (NFT)

3·39

IFO:[uic)

is the file owner qualifying switch which allows you to set the
owner of a file to a specified UIC, in the form: [g,m).

Isw

is one (or both) of the following qualifying switches (defined in
Section 3.2.3):
File Qualifying Switches

(N ot Applicable)

Command Qualifying Switches
ILO

INM
NOTE

Command qualifying switches do not affect input or output files
and. therefore, can be specified anywhere in a command line.
Example 1: Changing protection status on a transfer operation

NFT>HALDIR: :ALIAS.CMD=ALIAS.CMD/PR/SY/WO/GR/OW:RWD<RET>
File ALIAS.CMD allows read. write, and delete operations to the owner only.
Example 2: Changing protection status on an existing file

NFT>HALDIR: :ALIAS.CMD/PR/OW:R<RET>
File ALIAS.CMD allows the owner to read only.

3-40

DECnet-RSX Guide to User Utilities

3.2.14 The Spool Operation
MCR Primary Switch: ISP

The spool operation directs a file to a line printer on a local or remote node
for printing. When a file is spooled to a remote node, its format must be
compatible with the remote system. When format conversion is necessary, use
the lAS and IRe switches.
Format:
NFT>[outfile[/sw] = ]infile(s)[/sw]/SP

where
outfile

is an optional file descriptor that specifies the output file to
which the file will be copied and the system on which it will
be spooled. If outfile is omitted, the file(s) specified by infile(s)
is spooled on the input node.

infile(s)

is the file descriptor for each file to be spooled for printing.

Isw

is one (or more) of the following qualifying switches (defined in
Section 3.2.3):

File Qualifying Switches

Command Qualifying Switches

lAS
lAX

ILO
INM

IBK
'11M
INV

IRe
ISU
NOT.E

Refer to Section 3.2.1, which contains the rules for specifying
both file and command qualifying switches in a command line.

The Network File Transfer Utility (NFT)

3·41

Example 1:

NFT>SITKA: : COLD. FIL ;-t, HOME: : SNOW. FIL; l/SP<RET>

In this example, one copy of the file COLD.FIL;l is spooled to the line printer
on node SITKA, and one copy of the file SNOW.FIL;l is spooled to the line
printer on node HOME.
Example 2:

NFT>HOME: :SITKA: :COLD.FIL;l,HOME: :SNOW.FIL;l/SP<RET>
In this example, one copy each of file COLD.FIL;l and file SNOW.FIL;l is
spooled to the line printer on node HOME. The input file names default to
the output file name.

3·42

DECnet-RSX Guide to User Utilities

3.2.15 The Submit Operation

MeR Primary Switch: ISB

The submit operation transfers a command file to a remote node and submits
the file to either a remote command file processor or a batch file processor
for execution. The command file is deleted (by the remote node) after the file
executes. The remote node must support command file submission and execution
(for example, RT-II nodes do not support command file submission). When
you perform a submit operation. remember that the syntax of the command
lines within the command file must conform to the syntax standards of the
remote system on which the file is to be executed. To execute a command file
that is already on the remote node, you can use the execute (lEX) operation
(see Section 3.2.8).
For RSX systems, the command file can be submitted to either a command
file processor or a batch file processor depending on how the destination node's
command file submission task (MCM) was generated during NETGEN.
The success of the submit operation does not guarantee that the batch or
command file was executed successfully, only that the file was transferred and
that the execution request was successfully given to the MCM.
Format:
NFT>outfile[lsw] = commandfile[/sw]/SB

where
outfile

is the file descriptor of the temporary file that is created
on the destination node. This temporary file receives the
command file's contents and is deleted after execution.

commandfile

is the input file descriptor of the file containing the
commands to be executed by the destination node's operating
system. Only one command file can be specified.

Isw

is one (or more) of the following qualifying switches (defined
in Section 3.2.3):

The Network File Transfer Utility (N FT)

3·43

File Qualifying Switches

Command Qualifying Switches

lAS
lAX
IBK

ILO
INM

11M
INV
IRC
NOTE

Refer to Section 3.2.1, which contains the rules for specifying
both file and command qualifying switches in a command line.
Example:

NFT>DENVER: :DBO:[100,100]SVEFIL.CMD=INST.CMD/SB<RET>
In this example, file INST.CMD is transferred to DENVER as SVEFIL.CMD.
SVEFIL.CMD is then executed and is deleted after execution is complete.

3.3 NFT Operations for Del Users
DCL NFT operations act on DCL command verbs which specify the operation
to be performed (for example, the APPEND command specifies the append
operation). Most DCL NFT operations have optional qualifiers that can further
define the action of the command verb (for example,
APPENDIDATA_ TYPE = ASCII causes an input file to be appended to an
output file in ASCII record mode). The DCL NFT operations are summarized
in Table 3-3. Sections 3.3.4 - 3.3.14 describe each DCL NFT operation in detail.

3·44

DECnet-RSX Guide to User Utilities

3.3.1 Rules for Specifying DCl Qualifiers in a Command Line

An NFT peL command line consists of a command verb, one or more input
and/or output file specifications. and optional qualifiers (see Section 3.3). The
optional qualifiers fall into two categories:
1. Command Qualifiers. A command qualifier does not affect input or output

files and. therefore, can be specified anywhere in a command line.
2. File Qualifiers. A file qualifier applies only to each specific input file to

which it is appended.
A file qualifier achieves global status, and becomes the default for the rest
of the command line when:
• a file qualifier IS appended to an output file specification.
• a file qualifier is appended to a command verb.
A global qualifier can be overridden on a per file basis.
3.3.2 DCl Command Line Continuer

You can continue a DCL command line onto an additional input line by using
a hyphen (-) before the line terminator (see the example below). The hyphen,
followed by the terminator «RET», acts as a command line continuer. A
command line continuer causes DCL to prompt you for the remainder of the
command with an underscore followed by an angle bracket (_». You can insert
a continuer at any point in a command line, and you can use any number of
continuing lines within a command.
Example:

$COPY NOOEY/200,10/PASME: :SYO: [BUCKLEY]MYSTIC.MAC;2-<RET>
> NOOEX/[200,30]/OECNET: :OTO: [OALEY]MAGIC.MAC;3<RET>

The Network File Transfer Utility (NFT)

3·45

Table 3-3: Summary of NFT Operations for Del Users
NFT
Operation

DCl
Command

DCl
Qualifiers

(Scope of
Qualifier)

Append: The append operation
adds files to the end of an
existing file.

APPEND

IDAT ~TYPE = ASCII

(file)
(file)
(file)
(file)
(file)
(file)
(file)
(file)
(file)
(cmd)
(cmd)

ITRANSFEIL-MODE = AUTO
ITRANSFEIL-MODE = BLOCK
IDAT~TYPE = IMAGE
IMACYll
IPROTECTION = level
IOWNER = [uic]
IPRINT

ITRANSFEIL-MODE = RECORD
ILOG
INOWARNINGS

Copy: The copy operation
transfers one or more existing
files to one or more files on
the local or remote node.

COpy

ITRANSFEIL-MODE = ASCII
ITRANSFEIL-MODE = AUTO
ITRANSFEIL-MODE = BLOCK
ICONTIGUOUS
IDAT~TYPE

= IMAGE

IMACYll

INEW_VERSION
INO_SPAN

IPROTECTION = level
IOWNER = [uic]
IPRINT

ITRANSFEIL-MODE = RECORD
IREPLACE
ISUBMIT

ICONCATENATE
ILOG
INOWARNINGS

Create: The create operation
creates an output file that
previously did not exist.

CREATE

ISUBMIT
ILOG

(file)
(file)
(file)
(file)
(file)
(file)
(file)
(file)
(file)
(cmd)

ILOG
INOWARNINGS

(cmd)
(cmd)

ICONTIGUOUS
IMACYll

INEW_VERSION
INO_SPAN
IPROTECTION = level
IOWNER = [uic]
IPRINT

IREPLACE

Delete: The delete operation
deletes one or more files.

DELETE

(file)
(file)
(file)
(file)
(file)
(file)
(file)
(file)
(file)
(file)
(file)
(file)
(file)
(file)
(cmd)
(cmd)
(cmd)

(continued on next page)

3·46

DECnet-RSX Guide to User Utilities

Table 3-3 (cont.):

Summary of NFT Operations for Del Users

NFT
Operation

DCl
Command

DCl
Qualifiers

(Scope of
Qualifier)

Directory: The directory
operation lists a directory of
one or more files.

DIRECTORY

IBRIEF
IFULL
IATTRIBUTES

(cmd)
(cmd)
(cmd)
(cmd)
(cmd)
(cmd)

IWIDTH=n
IOUTPUT = outfile
INOWARNINGS

Print: The print operation
directs files to a line printer
for printing. (PRINT!REMOTE
prints a file located on a remote
node.)

PRINTIREMOTE

IDAT-L-TYPE = ASCII
ITRANSFEIL-MODE = AUTO
ITRANSFEIL-MODE = BLOCK
IDAT-L-TYPE = IMAGE

INEW_VERSION
ITRANSFEIL-MODE = RECORD
!REPLACE
ILOG
INOWARNINGS

Rename: The rename
operation changes the name of
an existing file.

RENAME

Set protection: The protect
operation sets or changes a
file's protection status.

ILOG
INOWARNINGS

(file)
(cmd)
(cmd)

SET PROTECTION

IOWNER = [uic]
ILOG
INOWARNINGS

(file)
(cmd)
(cmd)

Set file: The set file
operation sets the owner and
protection status for a file.
(Set file is an alternative
to the set protection
operation. )

SET FILE

ILOG
INOWARNINGS

(cmd)
(cmd)

Submit: The submit operation
submits a command file for execution. (SUBMIT IREMOTE
submits a file located on a remote node for execution.)

SUBMIT/REMOTE

ILOG
INOWARNINGS

(cmd)
(cmd)

Type: The type operation
types the contents of a file to
your terminal screen.

TYPE

IMACYll
ILOG
INOWARNINGS

(file)
(cmd)
(cmd)

The Network File Transfer Utility (NFT)

INEW_VERSION

(file)
(file)
(file)
(file)
(file)
(file)
(file)
(cmd)
(cmd)

3-47

3.3.3 Definition of DCl Qualifiers

NOTE

There are abbreviated synonyms for the data type and transfer
mode qualifiers which you can substitute in order to simplify
a command line. The qualifiers and their respective synonyms
are listed below:
• IDATA_ TYPE = ASCII:

IASCII

• IDATA_TYPE=IMAGE:

IIMAGE

• /TRANSFER_MODE = AUTO:

IAUTO

• ITRANSFER_MODE = BLOCK:

IBLOCK

• ITRANSFER_MODE = RECORD:

IRECORD

IDATA_ TYPE=ASCII
(/ASCII)

The ASCII qualifier transfers files in
ASCII record mode. For remote output
files, NFT translates the records in the file
into an appropriate format for the remote
system. For local output files, the file is
created as a variable length format, implied
LF-CR attribute file.
The IDATA_ TYPE = ASCII qualifier
should be used only if translation is
desired. File transfers to remote nodes that
have similar file systems (for example,
VMS) are more efficiently handled in image
block mode (the default transfer mode).

3·48

DECnet-RSX Guide to User Utilities

IDATA_ TYPE=IMAGE
(/IMAGE)

The image qualifier transfers files while
retaining their current format and
attributes. Some remote systems may not
support the transfer. causing an error
message to be displayed. If the file is
ASCII. you can recover by using the
IDATA_ TYPE = ASCII qualifier. If the
transfer was aborted due to unsupported
file organization, you can retry the transfer
using the ITRANSFER_MODE = BLOCK
qualifier.

ITRANSFER_MODE=AUTO
(/AUTO)

The automatic transfer selection qualifier
causes NFT to use its default algorithms
in selecting the mode in which to transfer
a file to a remote node. NFT will try to
select either block mode or record mode to
transfer a file. based on the remote F AL
capabilities. Since automatic transfer
selection is the default mode of transfer.
you will want to use the
ITRANSFER_MODE = AUTO qualifier to
override a specified mode of transfer.

ITRANSFER_MODE=BLOCK
(/BLOCK)

The block mode qualifier transfers files
using 5I2.-byte blocks. which is a more
efficient method than the usual record
mode transfer. Block mode can be used
with any file organization type on transfers
to other Files-II or RMS-ll systems that
support block mode transfers (for example.
RSX, VMS, or the RSTS/E RMS F AL).
When transferring files in block mode
either to or from a foreign file system.
there is no guarantee that the files will be
usable, since all foreign systems do not
store records compatibly.

The Network File Transfer Utility (N FT)

3·49

ITRANSFER _ MODE =RECORD
(/RECORD)

The record mode transfer qualifier directs
~FT to transfer a file one record at a time.
instead of using block mode. You would
use this qualifier when copying to unit
record equipment or to override NFT's
default selection of the transfer mode.

ICONTIGUOUS

The contiguous output qualifier creates an
output file with contiguous allocation.

IMACY11

The MACYll qualifier causes a file to be
stored in MACYll format on a TOPS-IO
or a TOPS-20 system.

INEW _ VERSION

The new version qualifier specifies that an
output file will have the same or latest
version number, whichever is higher.
However. the effect of the
INEW _VERSION qualifier depends on the
version number support on the remote
system. For example. RT-ll and RSTS/E
do not support version numbers; therefore,
this qualifier would be ignored on those
systems.
There is no negative version of the
INEW _ VERSION qualifier. However, you
can use the REPLACE command to specify
that an output file will retain the current
version number. If another file with the
same version number already exists, an
error will result.

INO_SPAN

3-50

The no span blocks qualifier specifies that
an ouput file will not span block
boundaries.

DECnet-RSX Guide to User Utilities

fPROTECTION =level

The protect qualifier allows a file's
protection status to be set or changed. File
protection is provided at four levels
(SYSTEM: RWED, OWNER:RWED,
GROUP:RWED, WORLD:RWED):

• SYSTEM: specifies file access that you allow to the system VIes (that is,

UIes with group numbers of 10 octal or less).
• OWNER: specifies file access that you allow to yourself.
• GROUP: specifies file access that you allow to other members of your group.
• WORLD: specifies file access that you allow for all other UIes.

RWED specifies whether each level can read, write. extend, or delete a file,
respectively. (See Section 3.3.11 for a full description of the set protection
operation.)
fOWNER =[uic]

The owner qualifier allows you to specify
the file owner for an output file.

fSUBMIT

The submit qualifier submits a file to a
batch or indirect command file processor
for execution.

IPRINT

The print qualifier directs a file to a line
printer for printing.

The Network File Transfer Utility (NFT)

3-51

fREPlACE

The replace qualifier transfers one or more
files to a file whose f.ile name, type, and
version number already exist in a user file
directory (UFD). The existing file is
deleted, and a new file is created with the
data from the input file(s). The new file
retains the current file name, type, and
version number that are in the directory,
but the file ID is new.
If an error occurs during the file transfer,
both the new output file and the one it is
replacing will be lost.

fCONCA TENA TE

The concatenate qualifier merges two or
more input files into one output file.

flOG

The log qualifier displays the names of files
(copied, deleted, and so forth) as the
operation is performed. The log qualifier
applies to all files involved in the current
command.

fNOWARNINGS

The no warnings qualifier suppresses
output messages that would otherwise be
displayed at your terminal during NFT
operations.

3·52

DECnet-RSX Guide to User Utilities

3.3.4 The Append Operation
DCl Command: APPEND

The append operation adds the contents of one or more input files to the end
of an existing output file. The output file retains its original attributes
independent of the attributes of the input file(s). However, if the attributes
of the input files are different from the attributes of the output file, the
append operation will appear to succeed, but the resulting output file may not
read correctly.
Format:
$APPEND[lqualifier(s)] infile(s)[lqualifier(s)] outfile[lqualifier(s)]

where
outfile

is the output file descriptor. No wildcard specifiers are allowed
in the output file descriptor. The file type and record attributes
are taken from the existing file. The file name and file type
for the output file must be explicitly specified.

infile(s)

is one (or more) input file descriptor(s).

Iqualifier(s)

is one (or more) of the following qualifiers (defined in Section
3.3.3):

File Qualifiers

Command Qualifiers

IDATA_TYPE = ASCII
IDATA_TYPE = IMAGE

fLOG
INOWARNINGS

~RANSFER_MODE=AUTO

flRANSFER_MODE=BLOCK
flRANSFER_MODE=RECORD
IMACYll

IPROTECTION = level
IOWNER = [uic]

IPRINT
NOTE

Refer to Section 3.3.1. which contains the rules for specifying
both file and command qualifiers in a command line.

The Network File Transfer Utility (NFT)

3·53

Example 1:

$APPEND/ASCII/LOG ESTER: :FIL2.DAT;1,YUKON: :FIL3.DAT;1-<RET>
_> LOWELL: :DK1:FIL1.DAT;1<RET>
In this example, the IASCII qualifier has been appended to the command
verb. Therefore, both input files in the command line (FIL2.DAT;1 located on
node ESTER, and FIL3.DAT;l located on node YUKON) are appended to
FILl.DAT;l stored on DKl: on node LOWELL, in ASCII record mode. The
command qualifier, ILOG, causes the names of the two files being appended
to FIL l.D AT to be displayed at your terminal as each append operation takes
place.
Example 2:

$APPEND ESTER: :FIL2.DAT;1,YUKON: :FIL3.DAT-<RET>
_> LOWELL: :DK1:FIL1.DAT/ASCII/LOG<RET>
In this example, the IASCII qualifier has been appended to the output file.
Therefore. both input files in the command line (FIL2.D AT; 1 located on node
ESTER. and FIL3.DAT; 1 located on node YUKON) are appended to
FILl.DAT;l stored on DKl: on node LOWELL. in ASCII record mode. The
command qualifier. ILOG, causes the names of the two files being appended
to FILl.DAT to be displayed at your terminal as each append operation takes
place.
Example 3:

$APPEND ESTER: :FIL2.DAT;1/ASCII/LOG,YUKON: :FIL3.DAT;1-<RET>
_> LOWELL: :DK1:FIL1.DAT;1<RET>
In this example, the IASCII qualifier has been appended to the FIL2.DAT;1
input file. Therefore. although both input files in the command line
(FIL2.DAT;l located on node ESTER, and FIL3.DAT;1 located on node
YUKON) are appended to FILl.DAT;l stored on DKl: on node LOWELL,
only FIL2.DAT;1 is transferred in ASCII record mode. The command qualifier,
ILOG. causes the names of the two files being appended to FILl.DAT to be
displayed at your terminal as each append operation takes place.

3·54

DECnet-RSX Guide to User Utilities

3.3.5 The Copy Operation (File Transfer)

Del Command: COpy
The NFT copy operation can transfer files in the following ways:
• Single file transfer. Transfers a single file from one node to another .
• File transfer with concatenation. Transfers more than one input file, from

the same or different nodes. to create a single output file.
The attributes of the output file are determined by the attributes of the
first input file that you specify in the command line. If the attributes of
the input files differ. the concatenation may appear to succeed. but the
output file may not read correctly.
• Multiple file transfer. Transfers more than one input file to the same number

of output files so that each input file has a corresponding output file.
If an error occurs during transfer, NFT or the remote F AL (File Access
Listener) attempts to delete the output file.
Format:
$COPY[lqualifier(s)] infile(s)[lqualifier(s)] outfile[lqualifier{s)]

where
infile(s)

is one (or more) input file descriptor{s).

Iqualifier{s)

is one (or more) of the following qualifiers (defined in Section
3.3.3):

The Network File Transfer Utility (NFT)

3·55

File Qualifiers

Command Qualifiers

IDATA_TYPE = ASCII
IDATA_TYPE = IMAGE
ITRANSFER_MODE = AUTO

ICONCATENATE
ILOG
INOW ARNINGS

flRANSFER_MODE=BLOCK
ITRANSFER_MODE = RECORD
ICONTIGUOUS
IMACY11
INEW _ VERSION
INO_SPAN
IPROTECTION = level
IOWNER = [uic]
IPRINT
IRE PLACE

ISUBMIT
NOTE

Refer to Section 3.3.1, which contains the rules for specifying
both file and command qualifiers in a command line.
Example 1: Single file transer

$COPY YUKON: :THURS.TXT THUR.TXT<RET>

In this example, THURS.TXT located on remote node YUKON, is transferred
to the local node and renamed THUR.TXT.
Example 2: Single file transfer between remote nodes

$COPY/NEW_VERSION YUKON: : THURS. TXT RASTOR: :DR5: [MITTON] <RET>

In this example, THURS.TXT located on node YUKON, is transferred to node
RASTOR, to be stored on DR5: under UFD [MITTON]. Once THURS.TXT
is transferred to RASTOR, the file will have the same or latest version number,
whichever is higher.

3·56

DECnet-RSX Guide to User Utilities

Example 3: Single file transfer using a foreign file

$COPY YUKON: :THURS.TXT/MACYll THUR TXT<RET>

In this example. THURS.TXT located on remote node YUKON. is transferred
in MACYll format to the local TOPS-20 node and renamed THUR.TXT.
Example 4: Transfer with file concatenation

$COPY/CONCATENATE YUKON: :THURS TXT,FRI.TXT WEEK.TXT<RET>

In this example, THURS.TXT and FRI.TXT located on remote node YUKON,
are transferred to the local node and concatenated to a single output file named
WEEK.TXT.
Example 5: Multiple file transfer

$COPY YUKON: :THURS.TXT/REPLACE,RASTOR::FRI.TXT-<RET>
_> ALEN: :DRA1: [DATES]/NEW_VERSION<RET>

In this example. THURS.TXT located on node YUKON, and FRI.TXT located
on node RASTOR. are transferred to node ALEN, and stored on DRAl: in
the UFD [DATES]. Both files will have the same or latest version number,
whichever is higher.
The version of the file THURS.TXT that is being transferred in this example
will replace any existing version of THURS.TXT that already exists on ALEN
in DRAl:[DATES). (Any existing file is deleted and a new file is created with
the data from the file being transferred.)
Example 6: Multiple file transfer using wildcards

$COPY/NEW_VERSION RASTOR: :DR5: [MITTON]*.OBJ,FILES.*;*-<RET>
_> KREMIT: :DB3:[ALBANESE]<RET>

In this example, the latest version of all files having the file type. OBJ and,
all versions of all files having the filename, FILES that are stored on
DR5:[MITTON] on node RASTOR, are transferred to node KREMIT, and
stored on DB3:[ALBANESE]. The resulting output files will have the same
names as the input files. The resulting output files will have the same or
latest version number, whichever is higher.

The Network File Transfer Utility (NFT)

3-57

3.3.6 The Create Operation
DCl Command: CREATE

The create operation creates an output file that previously did not exist. The
output file is created (using ASCII record mode), from data that you enter at
your terminal. The data that you enter is copied into the file until you type
a <CTRL/Z> (end-of-file indicator).
Format:

$CREATE outfile[lqualifier(s)]
where
outfile

is the name of the output file to be created.

Iqualifier(s)

is one (or more) of the following qualifiers (defined in Section
3.3.3):

File Qualifiers

Command Qualifier

ICONTIGUOUS

ILOG

IMACYll

INEW _ VERSION
INO_SPAN
IPROTECTION :: level
fOWNER:: [uic]
IPRINT
IRE PLACE
ISUBMIT
NOTE

Refer to Section 3.3.1. which contains the rules for specifying
both file and command qualifiers in a command line.
Example:

$CREATE RASTOR: :DR5:[7,132]MYFILE.TXT<RET>
This example creates the output file, MYFILE.TXT, on node RASTOR.

3-58

DECnet-RSX Guide to User Utilities

3.3.7 The Delete Operation
DCl Command: DELETE

The delete operation deleLes one or more specified files. located on the same
or different nodes.
Format:
$DELETE[fqualifier(s)] filedescriptor(s)[fqualifier(s)]

where
filedescriptor(s)

is any valid file descriptor(s), as defined in Section 3.1. The
version number must always be specified for files deleted
on RSX nodes.

fqualifier(s)

is one (or both) of the following qualifiers (defined in Section
3.3.3):

File Qualifiers

(Not Applicable)

Command Qualifiers

fLOG
fNOW ARNINGS
NOTE

Command qualifiers do not affect input or output files. and
therefore, can be specified anywhere in a command line.
On RSX systems, if there is a wildcard (* or %) in the file name or type. the
version number must be explicit or wildcard (that is, it cannot be 0 or -1).
Example:

$DELETE MAIN: :DK: [100,10]TAX.LST;5,BUDGET.LST;1<RET>
This command line deletes the files TAX.LST;5 and BUDGET.LST;1.

Tne Network File Transfer Utility (NFT)

3·59

3.3.8 The DCl Directory Operations
DCl Command: DIRECTORY

DCl Directory Qualifie,rs
[/FULL]
[/ATTRIB UTES]
[/BRIEF]
[/WIDTH =n]
[lOUT PUT =ollt/lie]

DCL has four types of file directory listings. The DIRECTORY command
(specified alone. or in conjunction with the IFULL. IATTRIBUTES, or IBRIEF
qualifiers) is used to obtain each type of directory listing as 'described here:
• The DIRECTORY command (when specified without any of the optional
qualifiers), lists the name. size. creation date, and optional contiguous and
locked indicators for the files specified in the input file descriptor (which
consists of a remote node specification and associated file specification).
• The IFUll qualifier lists the name. size, creation date, optional contiguous
and locked indicators, owner, protection. data last modified. and revision
number for files on a remote node.
• The IATTRIBUTES qualifier lists the attributes for each file in a directory
listing. This display includes the file organization. record format, and record
attributes, as well as the information included in a full (/FU) directory
listing.
• The IBRIEF qualifier lists only the names of files located on a remote node.

3-60

DECnet-RSX Guide to User Utilities

Format:

$DIRECTORY

FULL

infile(s)

IATTRIBUTES
IBRIEF
IWIDTH =n
IOUTPUT = outfile

where
IOUTPUT = outfile

is an optional file descriptor (that consists of a node
specification:: and associated file specification, see Section
3.1), to which the directory listing will be written. If
omitted, the output defaults to TI:.

IWIDTH=n

is a decimal number that specifies the width of the
listing. The default value is 72. At least one field is
al ways displayed per line. even if that field exceeds the
maximum width specified. The IWIDTH = n qualifier
cannot be used in conjunction with either the
IATTRIBUTES or the IBRIEF qualifiers.

infile(s)

is the input file descriptor (that consists of a remote
node specification:: and associated file specification, see

Section 3.1), for each remote file for which you want
directory listings. If no file name or type is specified in
the descriptor, you will receive a directory listing of all
files in the specified directory.

The Network File Transfer Utility (N FT)

3·61

Example 1: A Sample DIRECTORY Listing

$DIRECTORY WASH: :DBO:[BUCKLEY]<RET>

The directory of DBO:[BUCKLEY] on node WASH is displayed on TI: as
shown here:
Directory DBO:[BUCKLEY]
7-AUG-84 22:06
REMINDER.CMD;1
MASTERINI.CMD;l
TELI.CMD;l
TESTFILE.COM;l
LOGIN.CMD;l
PEOPLE.LST;1
NULLTEST.LST;l
COPY.LST;1
NFTTEST.LOG;l
TSETCMP.LOG;1
SETCMP.LOG;l

3. 07-AUG-84 22:02
11. 07-AUG-84 22:02
2. 07-AUG-84 22:02
O. 07-AUG-84 22:02
1. 07-AUG-84 22:02
1. 07-AUG-84 22:02
2. 07-AUG-84 22:02
5. 07-AUG-84 22:02
13. 07-AUG-84 22:04
10. 07-AUG-84 22:04
07-AUG-84 22:04
9.

Example 2: A Sample DIRECTORY IFULL Listing

$DIRECTORY/FULL WASH::DBO: [200,200]*.LST<RET>

The directory of all files having the file type .LST that are located on
DBO:[200.200] on node WASH, are displayed on TI: as shown here:
Directory DRO:[200,200] 7-AUG-84 22:07
PEOPLE.LST;l
(40345,1) 1./1.
NULLTEST.LST;1 (40356,1) 2./2.
COPY.LST;l
(40375,1) -5./5.

3·62

07-AUG-84 22:02 [7,132]
07-AUG-84 22:02 [7,132]
07-AUG-84 22:02 [7,132]

[RWED,RWED,RWED,R]
[RWED,RWED,RWED,R]
[RWED,RWED,RWED,R]

DECnet-RSX Guide to User Utilities

Example 3: A Sample DIRECTORY/ATTRIBUTES Listing

$D1RECTORY/ATTR1BUTES/OUTPUT=D1R.LST-<RET>
_> WASH: :DBO: [BUCKLEY]LOGIN.CMD,TESTF1LE.CMD<RET>

The attributes of the files LOGIN.CMD and TESTFILE.CMD located on
DBO:[BUCKLEY] on node WASH. are written to the file DIR.LST.
DBO: [BUCKLEY]LOG1N.CMD;l

File protection:
File organization:
File attributes:
Record format:
Record attributes:

Size:
1./1.
Created: 7-AUG-1984 22:02
Owner:
[BUCKLEY]
Revised: 7-AUG-1984 22:02
File 10: (40320,1,0)
Expires: <nonespecified>
System: RWED , Owner: RWED, Group:RWED, World:R
Sequential
Allocation=l, Extended=O
Variable length, no maximum defined
Carriage return

DBO: [200,200]TESTF1LE.CMD;1
Size:
0./0.
Created: 7-AUG-1984 22:02
Owner:
[007,132]
Revised: 7-AUG-198422:02
File 10: (40302,1,0)
Expires: <nonespecified>
File protection:
System:RWED, Owner: RWED, Group:RWED, World:R
File organization:
Sequential
File attributes:
Allocation=O. Extended=O
Record format:
Variable length. no maximum defined
Record attributes:
Carriage return
Example 4: A Sample DIRECTORY/BRIEF Listing

$D1RECTORY/BR1EF BOSTON: :DR5:[305,344]*.LOG<RET>

The directory of all files having the file type .LOG that are located on
DR5:[305,344] on node BOSTON, are displayed on TI: as shown here:
Directory DR5: [305,344]
NFTTEST.LOG;l
TSETCMP.LOG;l
SETCMP.LOG;l

The Network File Transfer Utility (N FT)

3·63

3.3.9 The Print Operation
DCl Command: PRINT/REMOTE

The print operation prints a file which exists on a remote node on that remote
node's line printer. When you specify the PRINT/REMOTE command. the
input file(s) are printed on the remote node that you specify in the command
line. (To copy a file to a remote node and have it printed, you would have to
specify the COPY/PRINT command. See Section 3.3.5 for a description of the
cogy operation. listing /PRINT as a valid qualifier.)
Format:

$PRINT/REMOTE [/qualifier(s)] infile(s)[Iqualifier(s)]
where
/REMOTE

is the qualifier used to print a file on a remote node.

infile(s)

is the file descriptor for each file to be printed.

/qualifier(s)

is one (or more) of the following qualifiers (defined in Section
3.3.3):

3·64

DECnet-RSX Guide to User Utilities

File Qualifiers

Command Qualifier

IDATA_ TYPE = ASCII

fLOG

nRANSFER_MODE=AUTO
nRANSFER_MODE=BLOCK
IDATA_ TYPE = IMAGE
INEW _VERSION
nRANSFER_MODE=RECORD
IRE PLACE
NOTE

Refer to Section 3.3.1, which contains the rules for specifying
both file and command qualifiers in a command line.
Example:

$PRINT/REMOTE HOME: :SNOW.FIL;1,COLD.FIL;1<RET>

In this example, one copy each of file COLD.FIL;l and file SNOW.FIL;l is
spooled to the line printer on node HOME. The output file names default to
the input file names.

The Network File Transfer Utility (N FT)

3-65

3.3.10 The Rename Operation

Del Command: RENAME
The rename operation changes the name(s) of the input file(s) to that of the
output file specifier. The new file name is entered into the new directory and
the existing or current file name(s) are deleted from the old directory. Because
no data is transferred on a rename operation, both directories must be on the
same node and same device. Since the operation is performed on the source
node. access control information need be given for the input file(s) only. If
the rename is to a different directory, the target directory must also allow
access. (Some systems do not support the Data Access Protocol (DAP) rename
operation. Refer to the Introduction to DECnet or to the individual system
documentation for more information.)
Format:
$RENAME[lqualifier(s)] infile(s)[lqualifier(s)] outfile[lqualifier(s)]

where
outfile

is the file specification to be given to the new file. (See Section
3.1.2 for a description of the file specification format.) Each
individual file name. type, and version number can be explicit.
wildcard (*), or defaulted (null), with two restrictions:
• If there is a wildcard (*) in the file name or type. the version

number must be explicit or wildcard (that is, it cannot be 0
or -1).
• Partial field or single character wildcard specifiers are not
allowed for outfile.
When a field is wildcard or defaulted, the corresponding field
of the input file is used. Thus, one or more fields can be
changed while preserving the others. (See Section 3.1.3 for
more information on wildcard specifications.)
infile(s)

is the file descriptor of the file(s) to be renamed.

Iqualifier(s)

is one (or more) of the following qualifiers (defined in Section
3.3.3):

3-66

DECnet-RSX Guide to User Utilities

File Qualifier
fNEW _ VERSION

Command Qualifiers

fLOG
fNOW ARNINGS

NOTE

Refer to Section 3.3.1. which contains the rules for specifying
both file and command qualifiers in a command line.
Example:

$RENAME WASH: :DBO: [200.200]*.MAR.*.MAL *.MAC<RET>
This example renames all .MAR and .MAL files located on node
WASH::DBO:[200.200], to .MAC files. Note that a space must separate the
input file(s) from the output file(s).

The Network File Transfer Utility (N FT)

3·67

3.3.11 The Set Protection Operation

Del Command:
SET PROTECTION =
[(SYSTEM:RWED,OWNER:RWED,GROUP:RWED,WORlD:RWED)]
[fOWNER [uic]]

The set protection operation sets or changes a file's protection status. File
protection is provided at four levels (SYSTEM:RWED, OWNER:RWED,
GROUP:RWED. WORLD:RWED):
• SYSTEM: specifies file access that you allow to the system VIes (that is.

VICs with group numbers of 10 octal or less).
• OWNER: specifies file access that you allow to yourself.
• GROUP: specifies file access that you allow to other members of your group.
• WORLD: specifies file access that you allow for all other VICs.

The R, W, E. and D protection settings specify whether each level can read,
wri te, extend, or delete a file, respectively. The R. W, E. andfor D protection
settings apply to all input files in a command line, unless overridden.
To alter the protection level of a file. you specify the SET PROTECTION =
command along with any/all of the four protection level qualifiers that you
choose (SYSTEM:RWED. OWNER:RWED. GROVP:RWED. WORLD:RWED).
If you are the file owner or have a system level VIC, you can alter the
protection level of a file without having read or write access. However, because
the protection level of a file is a protected attribute, you cannot alter the
protection level if you are in the group or world category for the file owner's
VIC. (You can read protected attributes if you have read access.)

3·68

DECnet-RSX Guide to User Utilities

Format:

$SET PROTECTION = -',RET>
_)[(SYSTEM:RWED,OWNER:RWED,GROUP:RWED,WORLD:RWED)]-<RET)
_ )filedeseriptor(s)[/qualifier(s)][/OWNER = [uie]]

where
filedeseriptor(s)

is the file descriptor(s) for each file in the command line.

SYSTEM:RWED

is the system level qualifier (defined here and in Section
3.3.3).

OWNER:RWED

is the owner level qualifier (defined here and in Section
3.3.3).

GROUP:RWED

is the group level qualifier (defined here and in Section
3.3.3).

WORLD:RWED

is the world level qualifier (defined here and in Section
3.3.3).

RWED

are the protection settings allowing read. write, extend,
and/or delete privileges. respectively.

/OWNER = [uie]

is the file owner qualifier which allows you to set the
owner of a file to a specified UIC, in the form: [g,m].

/qualifie r( s)

is one (or both) of the following qualifiers (defined in
Section 3.3.3):

File Qualifiers

Command Qualifiers

(N ot Applicable)

/LOG
/NOW ARNINGS

Example:

$SET PROTECTION=(SYSTEM:RWED,WORLD:RWED,GROUP:RWED,OWNER:RWD)-<RET>
_> HALDIR: :ALIAS.CMD<RET>
File ALIAS.CMD allows complete file access on the system, world, and group
levels, and allows the owner only to read, write, and delete the file.

The Network File Transfer Utility (N FT)

3·69

3.3.12 The Set File Operation
Del Command: SET FilE

The set file operation allows you to set the owner and protection for a file.
The set file operation is an alternative method of specifying owner and
protection values for a file. (Owner and protection values can also be specified
with the set protection operation; see Section 3.3.11.)
Format:

$SET FILE[lqualifier(s)) infile(s)[/qualifier(s))-<RET>
_>[/PROTECTION::: level] [/OWNER::: [uic]
where
infile(s)

is one (or more) input file(s) for which protection
and/or owner values are specified.

fPROTECTION :::

is the protect qualifier which allows a file's
protection status to be set or changed. File
protection is provided at four levels; SYSTEM:
RWED. OWNER:RWED, GROUP:RWED.
WORLD:RWED, where RWED specifies read.
write. extend. and delete privileges, respectively.
(See the set protection operation. Section 3.3.11,
for more information.)

level

fOWNER::: [uic]

is the file owner qualifier which allows you to
set the owner of a file to a specified DIC, in the
form: [g,m].

f qualifie r( s)

is one (or both) of the following qualifiers (defined
in Section 3.3.3):

3-70

DECnet-RSX Guide to User Utilities

File Qualifiers

(Not Applicable)

Command Qualifiers

fLOG
fNOW ARNINGS
NOTE

Command qualifiers do not affect input or output files and.
therefore. can be specified anywhere in a command line.
Example:

$SET FILE RASTOR: :DR5: [MITTON]MY.FIL/PROTECTION=(GR:RW) ,-<RET>
_>HIS.FIL/OWNER=[MITTON] <RET>

This command sets GROUP protection on MY.FIL to READ and WRITE (all
other protection levels. SYSTEM, OWNER, and WORLD, remain unchanged).
This command also sets the owner of HIS.FIL to [MITTON].

The Network File Transfer Utility (NFT)

3·71

3.3.13 The Submit Operation
Del Command: SUBMIT/REMOTE

The submit operation executes the contents of a command file located on a
remote node. You must specify the SUBMIT command along with the
IREMOTE qualifier for all network file specifications. If you specify only the
SUBMIT command and omit the IREMOTE qualifier. you will receive the
following error message:
Must supply REMOTE qualifier with DECnet node specification

For RSX systems, the command file can be submitted to either a command
file processor or a batch file processor. depending on how the destination
node's command file submission task (MCM) was generated during NETGEN.
If you want to execute a command file that does not already exist on a remote
node, you must use the COPY/SUBMIT command to copy the command file
to the remote node. and subsequently submit the file for execution. See Section
3.3.5 for a description of the copy operation listing ISUBMIT as a valid
qualifier.

The success of the submit operation does not guarantee that the batch or
command file was executed successfully, only that the execution request was
given successfully to the MeM.
Format:

$SUBMIT/REMOTE [Iqualifier(s)] commandfile(s)
where
IREMOTE

is the qualifier which executes a command file
on a remote node.

commandfile (s)

is the output file descriptor(s) for each remote
node command file that you want to execute.
Command files are not deleted after execution.

I qualifie r( s)

is one (or both) of the following qualifiers (defined
in Section 3.3.3):

3·72

DECnet-RSX Guide to User Utilities

File Qualifiers

Command Qualifiers

(N ot Applicable)

fLOG
fNOW ARNINGS
NOTE

Command qualifiers do not affect input or output files and,
therefore, can be specified anywhere in a command line.
Example:

$SUBMIT/REMOTE/NOWARNINGS WASH: :DBO:[200,200]NAMES.CMD<RET>
In this example, the command file N AMES.CMD located on node WASH, is
executed (while suppressing the display of any output messages to your
terminal).

The Network File Transfer Utility (NFT)

3·73

3.3.14 The Type Operation
DCl Command: TYPE

The type operation types the contents of a file to your terminal screen.
Format:
$TYPE[/qualifier(s)] infile(s)[/qualifier(s)]

where
infile(s)

is one (or more) input file descriptor(s) for file(s)
that will be displayed on your terminal screen.

Iqualifier(s)

is one (or more) of the following qualifiers (defined
in Section 3.3.3):

File Qualifier

Command Qualifiers

IMACYll

ILOG
INOW ARNINGS
NOTE

Refer to Section 3.3.1, which contains the rules for specifying
both file and command qualifiers in a command line.
Example:

$TYFE WASH: :DBO: [ALBANESE]FIL2.DAT<RET>
This command causes the contents of FIL2.DAT located on node WASH, to
be displayed on your terminal screen.

3-74

DECnet-RSX Guide to User Utilities

3.4 Exit with Status
NFT exits with a status code that may be useful in the following circumstances:
• In an indirect command file
• In a batch stream job (for RSX-IIM-PLUS systems only)
• When spawned by a parent task or connected to a parent task
NFT can issue two exit status codes:
Status

Code

NFT exited without error.

1 (EX$SUC)

NFT exited with an error.

2 (EX$ERR)

Status code 2 (EX$ERR) is returned if you make a syntax error or an
operational error. Also. if any command in an indirect command file fails. an
exit with status code 2 (EX$ERR) is issued when NFT exits.
You can test the status code returned by NFT and, on the basis of the results.
specify alternative procedures as shown in the following examples.
Example 1: Indirect command file

.IF <EXSTAT> = 2 .GOTO JUNO
Example 2: Batch job

$IF ERROR = 2 THEN STOP
Consult the operator's procedures manual for your system for additional
information about testing status in batch stream jobs and indirect command
files. For information on testing return status in a parent task. refer to your
system's executive reference manual.

The Network File Transfer Utility (NFT)

3·75

3.5 NFT Error Messages
When an NFT error occurs. you should receive one or more of the error
messages listed in the following sections. (For DCL users, NFT parsing and
syntax errors will generate appropriate DCL error messages.) NFT error
messages fall into three categories:
• Command error messages pertain to the NFT interface (network or
operating system interface), including I/O errors to the command device and
errors caused by trying to run NFT on a system without network support
enabled (see Section 3.5.1).
• Primary error messages pertain to I/O errors that occur when you transfer
or submit a file to another node. When NFT encounters a file I/O error, it
prints an error message specifying the name of the file and the operation
that NFT was performing when the error occurred (see Section 3.5.2). A
secondary message generally follows. giving the cause of the error.

When a command line specifies multiple operations, NFT tries to execute
subsequent operations, even after the error has been detected. In cases
involving file transfers (except when appending files). NFT deletes the output
file being created if an error occurs.
• Secondary error messages print out following primary error messages to
provide specific information on the nature of the error. Error types fall into
two categories: network errors and file I/O errors, (see Section 3.5.3). The
message may be text, or it may be a DAP. FCS, or NSP error code. For
example. the following error messages were returned in response to a
command line in which an incorrect node name was specified in the input
file specification:
NFT - Error in opening input file YOKON::FIL.CMD
Unrecognized node name

The second line is the secondary error message, which helps isolate the cause
of the error.
The NFT error messages are listed alphabetically in the following sections.
which correspond to the three error categories described here.

3·76

DECnet-RSX Guide to User Utilities

3.5.1 Command Error Messages
NFT . Command file error

An error occurred when N FT retrieved a command line from an indirect
command file. The command line might have exceeded the SO-character limit.
NFT . Get command line error

NFT encountered an error while retrieving a command line from a terminal
or in opening a command file specified from a terminal. The command line
might have exceeded the SO-character limit.
NFT . Help file error: n

An error has occurred while attempting to use the help operation (see Section
3.2.9). The variable n is a standard RSX I/O error code.
NFT . No help available

NFT could not find the help files. Normally. the help files for NFT are copied
to LB:[1,2] as a result of network generation (see the DECnet-RSX Network
Generation and Installation Guide).
NFT . No such command file

The specified command file cannot be found.
NFT . Syntax error

Either NFT cannot determine the operation being requested. or the command
line is ambiguous. Reenter the faulty command line echoed after the error
message, using the proper syntax.
NFT . Syntax error in file name filedescriptor

The specified file name did not conform to RSX syntax for file specifiers.
NFT . Unable to access network

NFT was invoked. but did not find network support.

The Network File Transfer Utility (NFT)

3·77

3.5.2 Primary Error Messages

Whenever one of the primary error messages listed below is issued. it is
followed by a secondary error message. which further defines the nature of
the error (see Section 3.5.3).

NFT - Error in changing file protection filedescriptor
NFT - Error in closing input file filedescriptor
NFT

Error in closing output file filedescriptor

NFT

Error in deleting file filedescriptor

NFT

Error in getting record from file filedescriptor

NFl

Error in opening input file filedescriptor

NFl

Error in opening output file filedescriptor

NFl

Error in purging output file filedescriptor

When an error occurs in an NFT file operation, NFT attempts to delete the
output file being created. If that attempt fails, NFT displays the preceding
message.

NFT

Error in putting record in file filedescriptor

NFT

Error in reading directory filedescriptor

NFT - Error in renaming file filedescriptor
This message is displayed if there is a problem with either an input or an
output file name. On local operations. NFT will display the erring file
descriptor. For remote rename operations. NFT will display only the input file
descriptor (even though it may be the output file name that is in error).

NFT - Error in spooling file filedescriptor
NFT - Error in submitting file filedescriptor

3-78

DECnet-RSX Guide to User Utilities

3.5.3 Secondary Error Messages

Secondary error messages provide additional information on the nature of an
error reported by a preceding primary error message. The primary error
message indicates the source of the error. Secondary error messages fall into
two categories: network errors and file I/O errors.
Network errors pertain to network operation failures or rejections. For example,
connect requests can be rejected by the network due to insufficient network
resources or due to an invalid node name format being specified in the file
descriptor.
File I/O errors pertain to file input or output errors on the local or the remote
node. Examples of file I/O errors are an improper file descriptor specification
or a file read error.
Network Error Messages
Aborted by network management

Either the network (NSP) rejected an attempted connect. or an operator
or program used network management to abort the connected logical links.
Access control rejected

The network (NSP) rejected an attempted connect because either the
remote node or the object could not understand or would not accept the
access control information (that is, the access control information -- user
ID, password. and account -- does not match a valid account on the
remote node),
Channel already active

The specified channel is already in use.

The Network File Transfer Utility (NFT)

3·79

Connection rejected by network

NFT's attempt to connect to the remote server task was rejected Oy the
network.
Connection rejected by remote FAL

NFT's attempt to connect to the remote server task was rejected by the
remote server task.
Data overrun

A protocol err9r. Either the remote FAL sent a packet too large for the
NFT buffer, or NSP delivered a packet too large for the allocated buffer.
The received data was truncated to fit in the available buffer space.
Insufficient network resources

The network (NSP) rejected an attempted connect due to insufficient
network resources on either the local or the remote node.
Internal consistency error

NFARs error occurred within NFT. Submit a software performance report
(SPR) documenting the error. See the DECnet-RSX Release Notes for
instructions on filing an SPR.
Internal inconsistency

An error occurred during error processing. Submit a software performance
report (SPR) documenting the error. See the DECnet-RSX Release Notes
for instructions on filing an SPR.
Invalid node name format

The network (NSP) rejected an attempted connect because of an invalid
remote node name format (for example, the name contained illegal
characters or was too long).

3-80

DECnet-RSX Guide to User Utilities

Invalid object name format

The network (NSP) rejected an attempted connect because the node did
not understand the object name format.
Network already open

The user is attempting to access the network for a second time.
Network error code: n

The specified error occurred during a network operation. The value
reported (n) is a signed octal number. If this error occurs. file a software
performance report (SPR) documenting the error. See the DECnet-RSX
Release Notes for instructions on filing an SPR.
Network not open

The issuing task is not part of the network (that is, it was never opened).
NFT buffer allocation failure

NFT's dynamic buffer space ($$FSRI) was exhausted during the operation.
NFT must be relinked with a larger $$FSRI section.
No more connections at remote FAL

The maximum number of connections has been made at the remote node.
Reissue the command after waiting for other connections to finish.
No response from remote FAL

Either the network (NSP) rejected an attempted connect because there
was no response from the object. or a connected logical link was aborted
because the remote node or object terminated abnormally.
Node unreachable

Either the logical link could not be connected, or the connected logical
link was aborted because no path existed to the remote node.

The Network File Transfer Utility (NFT)

3·81

Remote disconnect or line failure

A file transfer operation failed because the line to the remote node was
disconnected (or never established).
Remote FAL not found

The File Access Listener (F AL) is not installed on the remote node.
Remote node shut down

The logical link could not be connected because the remote node was in
the process of shutting down and would not accept any more logical link
connections.
Request terminated

The logical link was disconnected with the request outstanding.
Resource allocation failure

Resources needed for the requested operation are not available.
Tasks out of synchronization

A problem has developed in communications between NFT and the remote
server task (F AL), causing F AL to send N FT an unexpected message.
Unrecognized node name

The network (NSP) rejected an attempted connect because the destination
node name did not correspond to any known node address.

3·82

DECnet-RSX Guide to User Utilities

File 1/0 Error Messages

These file I/O messages can originate from either the local or the remote node.
Allocation failure on device

No room was found in which to create the specified file. The cause of
this error pertains to the method of file allocation. For example, there
may not be enough room for allocation of a contiguous file. In contrast.
a device full error (described in this section) occurs when there is no
room available. regardless of how the file is to be allocated.
Bad device name

The specified device name does not conform to the syntax of the target
system.
Bad directory syntax

The specified directory does not conform to the syntax of the target
system.
Bad file name

The specified file name does not conform to the syntax of the target
system.
Bad record size

The specified record size is either invalid or illegal for the specified
operation.
Bad version number

Either the version number is out of range, or it has been illegally specified
in a delete (see Section 3.2.6) or a rename (see Section 3.2.11) operation.

The Network File Transfer Utility (NFT)

3-83

CAP error code (macro:micro)
message

= xx:yyyy [STV =n] secondary error

This message appears when no other specific error message can be
provided. The specified error code (xx:yyyy) is reported as unsigned octal
numbers, as defined in Appendix C of the DECnet-RSX Programmer's
Reference ftrlanual.
The STY (secondary status value) may be returned by the remote RMS
FAL, depending upon the system, to provide additional information about
the error. The variable n is an octal number. (See the RMS reference
manual for the appropriate system to determine the meaning of the n
values.)
The secondary D AP error message further defines the type of error
indicated by the macrocode xx and can be one of the following:
Data transfer error

An error occurred on a data transfer operation.
File close error

An error occurred on a file close operation.
File open error

An error occurred on a file open operation.
Function not supported by remote FAL

The remote F AL does not support the requested operation.
Invalid message field

There is an error in the contents of the DAP message field. Refer to
the microcode for more information.
Message format error

There is an error in the D AP message format. Refer to the microcode
for more information.

3-84

DECnet-RSX Guide to User Utilities

Message out of sync

There is an error in the DAP message sequence. Refer to the microcode
for more information.
Operation successful

The operation succeeded, but with a microcode of other than 225 (octal).
Data overrun

A protocol error. Either the remote FAL has sent a packet too large for
the NFT buffer, or NSP delivered a packet too large for the allocated
buffer.
Device full

The specified output file cannot be created because no room is available
on the output device or there is not enough contiguous space to contain
a contiguous file. (In the latter case, some systems will respond with the
allocation failure on device message.)
Device off line

The specified file cannot be accessed because the device on which it
resides is either off line or not mounted.
Device write locked

The specified output file cannot be created because the output device is
write locked.
Directory not found

The specified directory does not exist on the node/device that was specified
or defaulted in the file specification.
End of file detected

An unexpected end of file (EOF) has been detected.

The Network File Transfer Utility (N FT)

3·85

Fatal hardware error

The specified file transfer was terminated due to an unrecoverable
hardware error.
FCS error code: -no

The specified local file system error occurred during an operation to a
local file. The number reported is a signed decimal value (see the
IAS/RSX-ll I/O Operations Reference Manual).
File access failed

The specified file cannot be opened; it is probably locked.
File accessed for write

The specified file cannot be opened because it is in the process of being
modified.
File already exists

The specified file name is already assigned to an existing file.
File already open

The specified file is already open.
~ile improperly closed

The specified input file is locked.
File locked by other user

Another user currently has the specified file locked or open for write.
File read error

An irrecoverable error has occurred while reading on the device.

3·86

DECnet-RSX Guide to User Utilities

File write error

An irrecoverable error has occurred while writing on the device.
Illegal record encountered

A record has been encountered that is illegal for this operation.
Invalid device or unit

The specified device or unit is not known to the target system.
Invalid or unsupported file organization

The file organization value (that is. sequential. relative, or indexed) is
invalid or unsupported by NFT or the remote F AL.
Invalid or unsupported record attributes

The file's record attributes (that is, FORTRAN, implied LF-CR, embedded.
or VMS print file) are invalid or unsupported by NFT or the remote
FAL.
Invalid or unsupported record format

The file's record format (that is. fixed, variable. VFC, or stream) is invalid
or unsupported by NFT or the remote F AL.
Invalid wildcard operation

The wildcard specification is inappropriate for the specified operation (for
example, a wildcard specifier has been included for a partial field on a
IRE operation). See Section 3.1.3 for a description of wildcard usage.
No such file(s)

The specified file or files do not exist.
Privilege violation

An operation was specified for which the user does not have privileges.

The Network File Transfer Utility (NFT)

3·87

Rename using two different devices

An attempt has been made to rename a file on two different devices..
This is an illegal operation.
Request terminated

An I/O operation has been prematurely terminated.
Resource allocation failure

Resources needed for the requested operation are not available. The
primary error indicates whether the error is on the input or the output
file.
Send/receive error

A network error occurred during a transfer operation.
Spool or submit command file failure

An error has occurred on a spool (/SP), submit (lSB), or execute (lEX)
operation when an error has occurred between the remote F AL and the
print spooler or the command filelbatch submission task. A possible cause
of this error is that the spooler or the command submission task is not
installed.
System directive error

A system directive failed while trying to perform an 110 operation.
Unsupported access function

The requested D AP access function is not supported by the remote F AL.
Valid D AP access functions are open, create, rename. delete. directory,
submit, and execute.

3·88

DECnet-RSX Guide to User Utilities

Unsupported file access request

The value of the file access field (F AC) is not supported. The F AC field,
contains the block I/O access request bit. which may not be supported
by the remote F AL.
Unsupported file option

The value of the file options field (FOP) is not supported by the remote
F AL. Some of the FOP field values that may not be supported by the
remote F AL are those that represent the following options: contiguous
file, maximum version, spool on close, submit on close, and delete on
close.
Unsupported file organization

The file organization value (that is, sequential. relative. or indexed) is
valid. but is unsupported by either NFT or the remote F AL.
Unsupported record attributes

The file's record attributes (that is. FORTRAN. implied LF-CR. embedded,
or VMS print file) are valid. but are unsupported by either NFT or the
remote FAL.
Unsupported record format

The file's record format (that is, fixed. variable, VFC, or stream) is valid,
but is unsupported by either NFT or the remote F AL.
Wildcard syntax error

There is an error within a wildcard specification (see Section 3.1.3).

The Network File Transfer Utility (NFT)

3·89

4
The File Transfer Spooler Utility (FTS)

Th .. , Filf' Transfer Spooler (FTS) utility has a set of fIle transfer and
marupuiation capabilities that are the same as those provided by NFT (see
Ch.lpter 3). However. unlike NFT, FTS supports only the MCR Command
Language Interpreter (CLI). Those file operations that are valid for both NFT
and FTS are:
• Append files to an existing file
• Transfer files between two nodes
• Delete files
• Execute command files located on a remote node
• Spool files to a line printer
• Submit local command files to a remote command file processor for execution
and subsequent deletion
In addition. FTS provides the following control functions not available in
NFT:
• Queue and process user requests according to user-supplied dates and times
• List pending user requests
• Kill pending requests
• Log user request completion

The File Transfer Spooler Utility (FTS)

4·1

~
~

LOCAL
LOGICAL LINK

~
GTAONE0
o
m
o::l

*
:D

(f)

c
0:

FTS DATA.NEW=BOSTON::PROGRAM.DAT

o
cCJ)

...

NOTE: FTSDEQ establishes a logical link to FAL on
remote node BOSTON and transfers file PROGRAM.DAT
to node DENVER to create file DATA.NEW .

C
!:!'"

;:::;:

(i)"
(J)

Figure 4-1: The FTS Utility: Queuing File Transfer Requests

When you type commands to FTS. it builds a queue entry for the FTS dequeuer
task on your local node. The FTS dequeuer communicates with the DECnet
server task File Access Listener (FAL) on the remote node (see Figure 4-1).

4.1 FTS File Descriptor Syntax
FTS commands operate on file descriptors that identify files in the network.
A file descriptor conSIsts of a node specification and a file specification. The
format for a file descriptor is:
[node specification

Hfilf' specification]

4.1.1 Node Specification

A node specification consists of the name of the node and optional access
control information for that node, followed by two colons.
nodename[access control]::

where
nodename

is a 1- to 6-alphanumeric character name that includes
at least 1 alphabetic character. If the node name is an
alias that includes associated access control information,
you can omit all access control fields. as they will default
to the access control information associated with the
alias. For more information on aliases, refer to Section

2.7.
access control

is a user identification, password, and account
specification (appended to a node name) used to gain
access to a remote file system. Access control information
can be specified using one of the two following formats.
NOTE

When passing access control information to case sensitive
systems (for example. ULTRIX-32/ULTRIX-32m systems), you
must use Format 2. shown here. (Format 1 passes access control
information in UPPERCASE.) The embedded spaces in Format
2 are mandatory.

The File Transfer Spooler Utility (FTS)

4·3

Format 1:

luseridlpasswdlaeent.
Format 2:

"userid passwd aeent".
userid is a 1- to 16-character string identifying the user at the remote system.
passwd is a 1- to 8-character string password needed to gain access to the
remote file system.
accnt is a 1- to 16-character string used to specify an account at the remote
system. (This field is not used for RSX systems.)
The interpretation of both the access control fields and the access control
mechanism depends on the type of remote system used. If the remote system
is a DECnet-RSX node supporting access control verification. the use rid field
is used to specify a valid account by last name or UIC. The passwd string
must be the password for that account, and the acent field is ignored For
additional information on access control, see the DECnet-RS ~ .\'etll'ork
lvIanagement Concepts and Procedures manual.
If the remote node does not support access control verification. its File Access

Listener (FAL) will permit either privileged or nonprivileged access control.
For privileged access, use the privileged password that was specified for FAL
during generation of the remote node (the default password is PRIV) and any
desired UIC for the user ID. For nonprivileged access, use the guest UIC and
nonprivileged password specified for F AL during generation of the remote
node. The default nonprivileged user ID and password are [200,200] and
GUEST, respectively. The acent field can be omitted for both privileged and
nonprivileged access.

4-4

DECnet-RSX Guide to User Utilities

Examples of Node Specifications:

Examples of valid node specIfIcations follow. Missing fields may be omitted
from the right. For example, the node specification QUEBEC/[310.2]1I can be
written QUEBEC/[310.2]. Missing fields on the left must be marked as missing
by a slash or a blank (depending upon the format used), as shown in the
fourth example. which follows.
NOTE

The use of brackets ([]) around the user ID is optional (as shown
in the last two examples. which follow), if the user ID is
supplied in the form of a UIC.
NODE4/[7.7]/SECRET/ACCNT::

YUKON"5,lO LEFT"::
BOSS/EVERY/ONE::
BOSTONIIIACCNTNE::

NODEl"RMES"::
B ILBOIl.lIPRIV::
SHELOB/200.200/GUEST::

4.1.2 File Specification

A file specification identifies either the local or the remote file on which FTS
is to operate. FTS can parse the same foreign file specifications as NFT (see
Section 3.1.4). RSX file specifications have the following format:
dev: [ufd]filename. type; ver

RSX-IIM-PLUS and Micro/RSX systems support the defintion of logical names
for all or part of a file specification. The D ECnet- RSX F AL can translate
only global logical names. For a discussion on logical names and how to define
them. refer to the RSX-ll MIM-PLUS I/O Operations Reference Manual.

The File Transfer Spooler Utility (FTS)

4-5

Depending upon its POSItIon in a command string, a file specification is either
an input (source) or an output (destination) file specification. Furthermore. the
node names define the file specification as local or remote. Therefore. FTS
files can fall into four categories:
• Local output files
• Remote output files
• Local input files
• Remote input files
Local or remote output files are files that receive data from an FTS operation.
and local or remote input files are files that contain the data to be operated
on and/or transmitted. FTS always verifies the existence of local input files
before allowing a specified request to be queued. For additional information
on RSX files. refer to the RSX-JJ Utilities Manual.
NOTE

When you enclose a file specification in double quotes. the file
spec string is passed to the remote system in a case sensi ti ve
manner. This is necessary for transferring files to and from
case sensitive systems such as ULTRIX-32/ULTRIX-32m
systems.
Defaults for FTS file descriptors are the same as those for NFT file descriptors,
which are summarized in Table 3-1. You can change the default values listed
in Table 3-1 by using the FTS set default operation (/DF) (see Section 4.2.13).
4.1.3 Wildcards in FTS File Specifications

FTS permits the use of wildcards in local input file specifications only (see
the allowable wildcard field specifiers defined for NFT in Section 3.1.3). FTS
differs from NFT in that it looks up wildcards immediately and records
applicable files in the user request block (URB) file for subsequent execution.
Therefore, files that meet the wildcard classification, but that are created after
the FTS wildcard request, cannot be included in the URB.

4·6

DECnet-RSX Guide to User Utilities

4.2 FTS Operations
FTS operations act on primary switches which specify the operation to be
performed (for example. I AP specifies the append operation). Some FTS
operations have optional qualifying switches that can further define the action
of the primary switch (for example. when IAS/AP are appended to an input
file specification. the lAS qualifying switch causes the input file to be appended
to an output file in ASCII record mode). The FTS operations are summarized
in Table 4-1. Sections 4.2.4 - 4.2.15 describe each FTS operation in detail.
4.2.1 Rules for Specifying FTS Switches in a Command Line

Primary switches can be inserted anywhere in a command line.
Qualifying switches, however, apply only to each specific input file to which
they are appended. When qualifying switches are specified for an output file.
the switch (or switches) becomes the default for all input file(s) in the command.
unless overridden on a per file basis.
When a switch modifies a file specification. the switch cannot appear before
the file name, type, version, or VIC of the file specification.
4.2.2 FTS Command Line Continuer

You can continue a command line onto an additional input line by using a
hyphen (-) before the line terminator (see the example which follows). The
hyphen. followed by the terminator «RET», acts as a command line continuer.
A command line continuer causes FTS to prompt you for the remainder of
the command line. You can insert a continuer at any point in a command
line. and you can use any number of continuing lines wi thin a command. The
maximum length of a command string is 256 characters.
Example:

FTS>DALLAS::DKO: [BUCKLEY]TAXES.LST=FICA.LST,-<RET>
FTS>FEDERAL,STATE<RET>

The File Transfer Spooler Utility (FTS)

4-7

Table 4·1: Summary of FTS Operations

Operation
Append: The append
operation adds files to the end
,of an existing file.

Primary
Switch

Qualifying
Switches

lAP

IAF
lAS

11M
ILO
IPR
ISE

Copy: The copy operation

default

transfers one or more
existing files to one or more
files on the local or remote
node.

IAF
lAS

11M
ILO
IPR
ISE

Delete: The delete operation
deletes one or more files.

IDE

IAF
ILO
IPR
ISE

Execute: The execute
operation executes a
command file stored on a
local or remote node.

lEX

IAF
ILO
IPR
ISE

Help: The help operation
displays a descriptive
message about switches and
commands.

IHE
HELP[subiect]

(continued on next page)

4-8

DECnet-RSX Guide to User Utilities

Table 4·1 (cont.): Summary of FTS Operations

Operation

Primary
Switch

Identify: The identify

lID

Qualifying
Swithces

operation identifies the
version of FTS being used.
Kill: The kill operation
removes a request from the
FTS queue.

*/KI

List: The list operation
lists your pending user
requests.

*/LI

Set default: The set default
operation sets certain default
values for input and output
files.

IDF

Spool: The spool operation
spools files to a line
printer for printing.

ISP

IAF
ILO
IPR
ISE

Submit: The submit operation
copies a command file to a
local or remote node.
executes the file. and then
deletes it.

ISH

IAF
ILO
IPR
ISE

*Switches supported by FTS that are not supported by NFT or that
have functions different from those for NFT.

The File Transfer Spooler Utility (FTS)

4·9

4.2.3 Definition of FTS Qualifying Switches

lAS The ASCII switch transfers files in ASCII record mode. The switch
applies only to the current command line and must be reset. if desired.
for each command.
For remote output files. FTS translates the records in the file into an
appropriate format for the remote system. For local output files. the file
is created as a variable length format. implied LF-CR attribute fiie.
The lAS switch should be used only if translation is desired. File transfers
to remote nodes that have similar file systems (for example. VMS) are
more efficiently handled in image record mode.
11M

The image switch transfers files while retaining their current format and
attributes. Some remote systems may not support the transfer. causing
the transfer to be aborted and an error message to be displayed. If the
file is ASC I I. you can recover by using the I AS switch.

IAF The after switch queues a user request for execution after a specified
date and time.

4·10

DECnet-RSX Guide to User Utilities

Format:
FTS>commandlineIAF[:dd-mmm-yy):hr:mn

where
commandline

is the user request that is queued for execution at the
specified time.

dd-mmm-yy

is the day. month. and year on which the user request is
to occur. If you omit this argument. the current date is
used.

hr:mn

is the time after which the user request is to occur. Use
the 24-hour format to specify hours (hr) and minutes (mn).

Example 1:

FTS>DALLAS: :DK1: [200,201]=LONDON: :SY: [200,200]-<RET>
FTS>PAYROLL.TSK;4/AF:21-MAY-83:15:30<RET>
File PAYROLL.TSK;4 will transfer from node LONDON to node DALLAS on
May 21, 1983, after 3:30.
Example 2:

FTS>LONDON: :DK1: [200,200]SALES.LST=SALES.LST;2/AF:17:15<RET>
File SALES.LST;2 will transfer from the local system to LONDON after 5:15
P.M. on the current date.
ILO

The log switch returns a completion message into your file area after
processing your request. (A separate message is logged for each file in
a multiple file transfer.) FTS logs completion messages by default and
stores messages in a user log file. The ILO switch allows you to redefine
the user log in which messages are to be placed. If you do not want a
completion message to be returned for a user request, disable logging by
negating the ILO switch (using INOLO or I-LO) for each command line.

The File Transfer Spooler Utility (FTS)

4-11

Format:

FTS)/LO:filespec

This format allows you to enter a file specification for
the user log file. The specification you enter overrides
the default file specification that FTS uses to store
completion messages when logging is enabled by the
system manager. (This format also causes logging when
logging is not enabled.) Any log file specification that
you enter with this format defines the user log file only
for the current command line. Subsequent lines will use
the default or an entered file specification. (The default
file type is .LOG.)

FTS)/LO

This format causes logging to default to the default file
specification SYO:FTS.LOG when logging is enabled by
the system manager.

FTS)/-LO
or
FTS)/NOLO

These negative formats are used to disable
logging for the current request when logging is enabled.
FTS creates a user log file if the specified file does not
exist. If the user log file does exist, FTS appends
completion messages to it.
You can use fLO in conjunction with a sequence of user
requests (see the ISE switch. which follows). However.
you must place the fLO switch on the first command
line of the sequence.

Examples:

FTS>=TACOMA: :DK1: [200,200]BANK.LST<RET>
FTS>=DALLAS: :DK1: [200,200]TAXES.LST/LO<RET>
FTS>DENVER: :SYO: [200,200]=PAYROLL.CBL, . LST/LO:PAYROLL.LOG<RET>
FTS>BOSTON: :DKO: [200,200]=MISC.DOC;4/NOLO<RET>
FTS>GENEVA: :DBO: [100,100]NEWSOFT.MAC=RELEASE.MAC/LO:CO:<RET>
FTS>LONDON: :DB2: [100,100]=REALTIM.MAC/LO:TI:<RET>

4·12

DECnet-RSX Guide to User Utilities

The first command logs a message by default to the common system user log
file on LB:[1.4)FTSSYS.LOG. The second command logs a message by default
to the user's own log tile. FTS.LOG. The third command defines the user log
file with the specification P A YROLL.LOG. The fourth command line suspends
logging for this request only with the INOLO switch. The fifth and sixth
commands illustrate the use of logical device names in the user log file
specification. FTS directs the completion message to the console pseudodevice
(CO:) in the fifth command and to the user's terminal (TI:) in the sixth
command.
Completion Message Format:
A completion message has the following format:

nodename type Job = queue job number
Time: dd-mmm-yy start time end time
User: userid Blocks: size
Status: status [error code disposition]
File: file
Input: input

where
nodename

identifies the remote node. If there is no remote node.
nodename identifies the local node. If the user request was
a remote-to-remote file transfer. nodename identifies the
destination node.

type

is a character code that identifies the type of user request
issued. The codes are summarized in Table 4-2 in Section
4.2.12.

The File Transfer Spooler Utility (FTS)

4·13

queue job number

is the job number of the user request as listed by the ILl
switch (see Section 4.2.12).

dd-mmm-yy

is the day, month. and year when the processing of the
user request started.

start time

is the time in hours, minutes. and seconds (hr:mn:ss) when
the processing of the user request started.

end time

is the time in hours. minutes. and seconds (hr:mn:ss) when
the processing of the user request completed.

userid

is a 1- to 16-character string that identifies the owner of
the processed user request.

size

is the number of user blocks transferred over the logical
link. The value for size is 0 for execute and delete
operations or for instances when errors occurred to prevent
file transfer. For a concatenation request. size is the sum
of the input file sizes.

status

indicates whether or not the user request completed
successfully. If the request did complete with success. the
message success is printed in the status field. and the
error code and disposition field are omitted. If the request
did not complete successfully. the status field contains the
phrase error = nodename. The node on which the error
occurred can be indicated in one of two ways:
LOCAL
LOCAL is printed to indicate that the error occurred at
the local node.
errnodnam
The actual name of the remote node on which the error
occurred is printed.

The unsuccessful completion of a queued user request
returns information in the error code and disposi tion fields
as well.

4·14

DECnet-RSX Guide to User Utilities

error code

is a 6-character DAP. NSP, or FCS error code that is
returned on an unsuccessful operation. Error codes fall into
one of the categories described in the following paragraphs.
In each case. nnn is a positive decimal number that defines
a specific set of error codes that each program returns.

FCSnnn
describes an error that occurred while accessing the local
file. In this case, nnn is the positive decimal value of the
F.ERR byte in the local FDB. See the IASIRSX-ll I/O
Operations Reference Manual for a list of these codes.
NETnnn
descri bes an error that occurred while accessing the remote
node. For NET, nnn refers to the low-order byte of the
second word of the network I/O status block. Refer to
Appendix C of the DECnet-RSX Programmer's Reference
Manllal for a list of these codes.
Nnnn07
returns when the network rejected an attempted connect.
For this category, nnn is the value of the NSP rejection
code. 07 signifies that the connection was rejected. See
Appendix A of the DECnet-RSX Programmer's Reference
Manual for a list of disconnect or reject reason codes.
SND002
is the network send/receive error. For example, the system
is unable to request execution 0'£ an indirect command file
because the task that submits the file to the system
command handler is not installed or is not available.

The File Transfer Spooler Utility (FTS)

4·15

FSBnnn
indicates that an FTS buffer allocation error occurred. For
FSB. nnll refers to the number of the file descriptor that
would have caused the file specification block buffer to
overflow. had it been stored. The disposition code is F2.

The number of files per user request is set to 20(decimal).
This size can be increased by rebuilding the task FTSDEQ
and extending the $$FSBI PSECT in NFT's data area.
xxyyyy

describes the DAP errors. The value xx is the octal value
of the macro error code. maccode. Maccode is the global
code specification for the error. The value yyyy is the
miccode. which provides the specific code for the error.
See Appendix C of the DECnet-RSX Programmer's
Reference Manual for the values and meanings of xxyyyy.
REMnnn
describes all other errors that can occur. For REM. nnn
is the value of the low-order byte of the first word in the
network I/O status block. See Appendix C of the
DECnet-RSX Programmer's Reference Manual for the
values and meanings of nnn. (Note that nnn is never 003
or 004, since 003 is recorded as a D AP error and 004 as
an NSP error.)

4·16

DECnet-RSX Guide to User Utilities

disposition

is a short message that summarizes the completion status
of an unsuccessful request. When returned, this field will
contain one of the following messages:
Discarded
The request was discarded. but not requeued.
Requeued
The request was requeued with an IAF time value (see
preceding description).
Queue hold
After being requeued a maximum number of times. a
request was placed in a hold queue for manual release or
abort.
W orkfile access
The request failed because an error occurred while accessing
the user request file from the queue entry.
Pri vileged information access
The request failed due to an error while accessing
information to check the user's access privileges to the
local file specifications.
Buffer allocation
The request failed due to a lack of buffer space to store
the file specifications (see the preceding FSBnnn error
code).

The File Transfer Spooler Utility (FTS)

4·17

(ile

identifies the output file (or the only file in the request in
cases where input and output have no distinction). The file
descriptor is in the form
nodename::dev:[uic](ilename.type;version
If the user request is a delete or execute request, this is
the only file descriptor that is printed (that is. the input
field is omitted). The node name is omitted in local file
descriptors.

input

identifies the input file in the form
nodename::dev:[uic](ilename.type:version
The input file descriptor is repeated for concatenation
requests that involve multiple input files. The node name
is omitted if the descriptor is for local files.

The following examples show the command lines and resulting completion
messages for a single file transfer, concatenation transfer. and remote-to-remote
transfer requests.
Example 1: Single file transfer

FTS>=DENVER: :DK5: [200, 200] INVENTORY. LST;4/Lo<RET>
DENVER TRL Job=217444
Time: 19-APR-83 17:36:54 17:50:05
User: [200,200] Blocks: 0
Status: error=DENVER N03907 Requeued
File: DBO: [200, 1] INVENTORY. LST;4
Input: DENVER: :DK5: [200.200]INVENToRY.LST;4

One file was queued to transfer to the local system. FTS will use the local
user's current log-in defaults to store the file. The completion message shows
that the request was requeued because of an error that occurred on the remote
system. The error code, N03907, identifies the error as no path to destination
node.

4·18

DECnet-RSX Guide to User Utilities

Example 2: Concatenation transfer

FTS>DALLAS: :DKO: [225,225]TAXES.LST=FICA.LST,FEDERAL,STATE/LO<RET>
DALLAS
CLR
Job=382077
Time: 28-JUN-83 11:05:03
11:35:03
User: [224.1] Blocks: 25
Status: Success
File: DALLAS: :DKO: [225,225]TAXES.LST
Input: DBO: [224,1]FICA.LST
DBO: [224,1]FEDERAL.LST
DBO: [224,1]STATE.LST

Three input files were transferred and concatenated to form the output file.
The absence of a disposition code tells you that the transfer was successful.
A file descriptor appears for each input file.
Example 3: Remote-to-remote transfer

FTS>BOSTON: :DK2: [224, 223]=DENVER: :DK3: [200,1]PEN.INV<RET>
BOSTON
TRR Job=217526
Time: 12-DEC-83
13:15:04 13:45:05
User: [200,1] Blocks: 0
Status: error=BOSTON N03407 Discarded
File: BOSTON: :DK2:[224,223]PEN.INV
Input: DENVER: :DK3: [200,1]PEN.INV

This example illustrates a completion message for a remote-to-remote transfer
that terminated in an error. The error code. N03407. indicates that the network
rejected the connection.

The File Transfer Spooler Utility (FTS)

4-19

IPR

The priority switch directs FTS to queue a user request at a given
priority.

Format:

FTS>/PR:priority

where
priority is a decimal number from 1 to 250.

If you do not specify the priority switch, FTS queues the user request at the
priority of the running task. which is FTS at default priority 50.
Example:

FTS>MAIN: :LB: [200,202]=FISCAL.DOC;1/PR:65<RET>
The user request to transfer FISCAL.DOC; 1 to l\IAIN is placed in the queue
with a priority of 65.
ISE

The sequence switch processes requests on the current command line
and on subsequent command lines in the order in which you input
them. You can use the ISE switch to ensure that FTS processes requests
in the proper order.

Format:

FTS>commandline 1 <RET>
FTS>commandline2ISE< RET>
FTS >commandline8lSE <RET>
FTS >commandline4/SE <RET>
FTS >commandline5 <- RET>
FTS>commandline6<RET>

The requests specified in command lines 2 through 5 will be processed in the
order that they are input. (Command line 5 is the line subsequent to command
line 4 and is, therefore, included in the sequence even though there is no ISE
switch typed for command line 5.) If an error is found at any point in the
sequence, FTS stops and will not queue the requests for processing. In the
above sequence, command lines 1 and 6 are processed independently.

4·20

DECnet-RSX Guide to User Utilities

Example:

FTS>DALLAS: :DK2: [200,202]INVENTORY.LST=*.LST/AS<RET>
FTS>BOSTON: :SY: [200,200]PAYROLL.LST=DALLAS: :DKO: [200,200] - <RET>
FTS>WAGES.LST;5/AS/SE<RET>
FTS>BOSTON: :DK1: [200,200]TAXES.LST;4/DE/SE<RET>
FTS>BOSTON: :DK1: [200,200]TAXES.LST=LB:TAXES.CBL, .TSK, . TXT<RET>
FTS>DENVER: :DBO:: [200,200]PATCH.TSK=FIX.*;*/IM<RET>

The commands for transfers to node BOSTON will be processed in the order
in which they are input.
4.2.4 The Append Operation
FTS Primary Switch: lAP

The append operation adds the contents of one or more input files to the end
of an existing output file. The output file retains its original attributes
independent of the attributes of the input files. However. if the attributes of
the input files are different from the attributes of the output file. the append
operation will appear to succeed. but the resulting output file may not read
correctly.
Format:
FTS>outfile = infile(s)[fswJfAP

where
outfile

infile(s)

is one (or more) input file descriptor(s).

The File Transfer Spooler Utility (FTS)

4·21

Isw

is one (or more) of the following qualifying switches (defined in
Section 4.2.3):
IAF
lAS

11M
ILO
IPR
ISE

Example:

FTS>LOWELL: :DK1:FIL1.DAT;1=ESTER: :FIL2.DAT;1/AS,YUKON: :-<RET>
FTS>FIL3.DAT;1/AS/AP<RET>
In this example, FIL1.DAT;1. which is stored on DKl: at node LOWELL, is
opened. FIL2DAT;1. located at node ESTER, and FIL3.DAT;1, located on
node YUKON, are then appended to FIL1.DAT;l in ASCII record mode.
4.2.5 The Copy Operation (File Transfer)
FTS Primary Switch: (default operation)

The FTS copy operation can transfer files in the following ways:
• Single file transfer. Transfers a single file from one node to another.
• File transfer with concatenation. Transfers more than one input file. from

the same or different nodes, to create a single output file.
The attributes of the output file are determined by the attributes of the
first input file that you specify in the command line (see the command
format, which follows). If the attributes of the input files differ. the
concatenation may appear to succeed, but the output file may not be correctly
readable.
• Multiple file transfer. Transfers more than one input file to the same number

of output files. so that each input file has a corresponding output file.
If an error occurs during transfer. FTS or the remote F AL (File Access
Listener) attempts to delete the output file.

4-22

DECnet-RSX Guide to User Utilities

If you specify a name and type III the output file specification and there is
more than one input file. the input files will be concatenated to form the
output file. If an error occurs while processing a concatenation file transfer
request. FTS stops processing the request without transferring any of the
files.

To specify a multiple file transfer (more than one output file and more than
one input file). omit the output file name and type. A node name. device. and
UIC may be specified.
Format:
FTS)outf'ile = infile(s)[lsw]

where
infile(s)

is one (or more) input file descriptor(s).

Isw

is one (or more) of the following qualifying switches (defined in
Section 4.2.3):
IAF
lAS

11M
fLO
IPR
ISE

Example 1: Single file transfer from a remote node to the local node

FTS>=DENVER: :DK5: [BUCKLEY]INVENTORY.LST;4<RET>
In this example, INVENTORY.LST;4 stored on node DENVER is transferred
to the local node and stored under the same file name in the UFD [BUCKLEY].
Example 2: Concatenation transfer from the local node to a remote node

FTS>DALLAS: :DKO: [225,225]TAXES.LST=FICA.LST,-<RET>
FTS>FEDERAL,STATE<RET>
In this example. FICA.LST. FEDERAL.LST, and STATE.LST are transferred
and concatenated to form TAXES.LST on DALLAS.

The File Transfer Spooler Utility (FTS)

4·23

Example 3: Multiple transfer from the local node to a remote node

FTS>DENVER: :DK3: [221,221]=PENS.INV,PAPER,PENCILS<RET>

In this example. PENS.INV. PAPER.INV. and PENCILS.INV are transferred
to node DENVER and retain the same file names.
Example 4: Single file transfer between two remote nodes

FTS>BOSTON: :DK2: [FRASER]=DENVER: :DK3: [DALEY]-<RET>
FTS>COMPUTERS.LST;4<RET>

In this example. COMPUTERS.LST;4 is transferred to node BOSTON from
node DENVER. and is stored under the same file name and type. If a file of
the same name and type exists on BOSTON, a new version of the file is
created.
4.2.6 The Delete Operation
FTS Primary Switch: IDE

The delete operation deletes a list of files (see Format A) or a single input
file after it has been transferred (see Format B). The Format B (transfer and
delete) option is not offered by NFT.
Format A:

Use the following format to delete one or more files when no transfer operation
is being performed:
FTS>filedescriptor(s)[/sw]/DE
where
filedescriptor(s)

is any valid file descriptor(s), as defined in Section 4.l.
The version number must always be specified for files
deleted on RSX nodes.

Isw

is one (or more) of the qualifying switches listed under
Format B.

4-24

DECnet-RSX Guide to User Utilities

If there is a wildcard
or %) in the file name or type, the version number
must be explicit or wildcard (that is, it cannot be 0 or -1). (See Section 3.1.3
for more information on wildcard specifications.)

Other systems may have different requirements for delete requests. Check the
user documentation for each operating system to determine its requirements.
Format B:

Use the following format to transfer a single input file and then delete it
from the source. (If the file transfer fails, the input file is not deleted.) Multiple
file transfers are not accepted in this format.
FTS>outfile = infile[lsw]/DE

where
outfile

is a file descriptor for the file receiving the data.

in file

is a file descriptor for the file that initially contains the data. FTS
deletes the input file after it is transferred.

Isw

is one (or more) of the following qualifying switches (defined in
Section 4.2.3):
IAF
ILO
IPR
ISE

Example 1: Request to delete a list of files

FTS>DALLAS: :DK1: [FRASER]TAXES.LST;4,DK2: [BUCKLEY]-<RET>
FTS>FICA.LST;3/DE<RET>
In this example, FICA.LST;3 and TAXES.LST;4 on node DALLAS are deleted.
Example 2: Request to delete a file after transfer

FTS>LYNN: :DK1: [200,200]=USELESS.LST;4/DE<RET>
In this example. USELESS.LST:4 is deleted locally after it successfully
transfers to node LYNN.

The File Transfer Spooler Utility (FTS)

4·25

4.2.7 The Edit Operation
FTS Primary Switch: lED

The edit operation inhibits the queuing of user requests. In this state, FTS
accepts and checks your command lines for syntax but does not queue them
for execution. To return to queuing mode, enter a <CTRL/Z>.
When in edit mode. FTS does detect nonexistent local input files or illegal
local input file descriptors. However. when FTS checks the syntax of a user
request, it makes no attempt to validate the remote file descriptors. Therefore.
an error in the remote file descriptor will go undetected until execution time.
Example:

FTS>/ED<RET>
FTS - Entering Edit mode
FTS> <CTRL/Z>
FTS - Leaving Edit mode

4·26

DECnet-RSX Guide to User Utilities

4.2.8 The Execute Operation
FTS Primary Switch: lEX

The execute operation executes the contents of a command file located on a
local or remote node. For RSX systems, the command file can be submitted
to either a command file processor or a batch file processor, depending on
how the destination node's command file submission task (MCM) was generated
during NETGEN. If you want to execute a command file that does not already
exist on a remote node. you must use the submit operation (see Section 4.2.15)
to copy the command file to the remote node, and subsequently submit the
file for execution.
The success of the execute operation does not guarantee that the batch or
command file was executed successfully, only that the execution request was
given successfully to the MCM.
Format:
FTS>commandfile(s)[/sw ]/EX

where
commandfile(s)

is the output file descriptor(s) for each remote node command
file that you want to execute. Command files are not deleted
after execution.

fsw

is one (or more) of the following qualifying switches (defined
in Section 4.2.3):
IAF

fLO
IPR
ISE

Example:

FTS>BOSTON: :SYO: [100.100]RETRIEVE.CMD/EX<RET>
In this example, the command file RETRIEVE.CMD is to be executed on
node BOSTON.

The File Transfer Spooler Utility (FTS)

4-27

4.2.9 The Help Operation
FTS Primary Switch:

IHE
HELP

The help operation displays information on how to use FTS. To print the list
of subjects for which there is help information available. type either version
of the switch:
FTS)/HE
FTS)HELP
To obtain information about one of the subjects listed. type:
FTS) HELP[sub;ect]
Example:

FTS>HELP SWITCHES<RET>

This help request lists the valid FTS switch options.
Help files must be located on device LB:[1.2]. If they are not on this device.
the following message will appear on your terminal:
FTS - No help available

If your help files are not on the proper device. consult your system manager.

4·28

DECnet-R8X Guide to User Utilities

4.2.10 The Identify Operation
FTS Primary Switch: liD

The identify operation displays the current FTS version number on your
terminal.
Example:

FTS>/ID<RET>
FTS - VERSION 4.1
4.2.11 The Kill Operation
FTS Primary Switch: IKI

The kill operation deletes a pending user request or aborts a request already
in progress. Use the kill switch in any of the following forms:

FTS>job#IKI

deletes the specified user request.

FTS>nodename::/KI

deletes all user requests involving the specified node.

FTS>*/KI

deletes all user requests you have queued.

where

job#

is a 6-digit numbe~ that FTS assigns to a user request when it is
issued. To find the FTS job number, inspect output initiated by
ILl (see Section 4.3.12).

nodename is the name of the node for which the request(s) should be killed.
The kill switch deletes or aborts only requests that you have specified. If you
attempt to kill a request from a UIC other than the requesting UIC. you will
receive an error message.

The File Transfer Spooler Utility (FTS)

4·29

Killing a job entry involves sending a message to the queue manager to kill
the queue entry and deleting the user request file which defines the job to
FTSDEQ. When the FTS IKI command is issued. FTS attempts to delete the
user request file and to send a request to the queue manager to kill the queue
entry. If the request has not been requeued by FTSDEQ due to some failure,
the kill request will work. However, when a job has been requeued by FTSDEQ,
the queue request is entered under the owner VIC [1.1]. FTS can no longer
request the queue manager to kill the queue entry because the queue entry is
now owned by [1.1] and not by the original user. FTS may still delete the
user request file.
If the queue entry is not in the HELD state and the user request file has
been deleted, the entry is deleted the next time FTSDEQ is invoked. However.
if the queue entry has been placed in the HELD state. the entry must be
killed by a privileged user running under the VIC [1.1]. To kill the queue
en try, issue the queue manager command

QUE IDEL/EN:entry
Example 1: Delete a single user request

FTS>162880/KI<RET>

Removes user request with job number 162880 from the queue.
Example 2: Delete all user requests involving a specific node

FTS>BOSTON: :/KI<RET>

Removes all your user requests involving node BOSTON from the queue.

4·30

DECnet-RSX Guide to User Utilities

4.2.12 The List Operation
FTS Primary Switch: /LI

The list operation displays all pending user requests from your UIC on your
terminal.
Format:

FTS> [node name:: ]/L I
where
nodename specifies that only user requests for that node be listed. If nodename
is omitted. all user requests from your UIC are listed.

When FTS lists pending requests. it prints two header lines. The first contains
the message FTS user request listing. the current date, and the time. The
second contains the job number. type/priority. and options headings. If there
are no queued requests. FTS prints the message no requests found. If there
are requests in the queue. but they do not involve the node name specified
in your command. FTS prints the headings and the message no requests found.
On the first line of each request description. FTS prints the job number.
followed by the code for the function to be performed. (Function codes are
defined in Table 4-2.) The function code is followed by a slash and the request's
priority. Following the priority are the options the user specified. 11M and
/LO are printed by default if logging has been enabled by the system manager
and the user did not use the /AS switch to define ASCII transfer mode. The
IAF switch with a date and time appears under the options header when a
request has been requeued or the user has specified the switch.

The File Transfer Spooler Utility (FTS)

4-31

The second tine of the request description contains the date and time that the
request was queued and the number of times that the request was tried. (The
value of times tried is greater than 0 when an attempted request has failed
and been automatically requeued with the I AF switch for execution at a later
time.) Under the request description are two lines describing the input (source)
file and the output (destination) file. A third line describing the user log file
is printed if the user has specified a user log file with the ILO:{ilespec switch.
Example 1: Print user requests involving specified node name

FTS>DALLAS: :/LI<RET>
FTS USER REQUEST LISTING
Job #
Type/Priority

28-Jun-83

11:30

Options

141954
TLR/50
/IM/LO
Queued 28-Jun-83 10:45
Active
Source File - DBO: [224,l]FICA.LST;1
Destination File - DALLAS: :DK1: [200, 200] TAXES.LST
382077
/AF:28-Jun-83:11:35/IM/LO
TLR/50
Queued 28-Jun-83 10:50
Tried 1 Time
Source File - DBO: [224,l]STATE.LST;1
Destination File - DALLAS: :DK1:[200,200]TAXES.LST
Log File - DBO:DALLAS.LOG

4·32

DECnet-RSX Guide to User Utilities

Example 2: Print all user requests

FTS>/LI<RET>
FTS USER REQUEST LISTING
Job #
Type/Priority

28-Jun-83

11:45

Options

234892
DR/50
/IM/DE/LO
Queued 28-Jun-83 9:00
Active
Source File - BOSTON:DBO: [224,l]USELESS.LST;4
415121
TLR/50
/AF:28-Jun-83:11:50/IM/LO
Queued 28-Jun-83 9:15
Tried 2 Times
Source File - DBO:[224,l]PAYROLL.CBL
Destination File - DENVER: :SYO: [200,200]PAYROLL.CBL
Log File - PAYROLL. LOG
415220
TRR/50
/AF:28-Jun-83:11:55/IM/LO
Queued 28-Jun-83 9:20
Tried 1 Time
Source File - BOSTON: :DBO: [200,1]TAXES.CBL
Destination File - LONDON: :DK4: [221,221]TAXES.CBL
410455
SLR/50
/AF:28-Jun-83:12:00/IM/LO/SB
Queued 28-Jun-83 9:25
Tried 1 Time
Source File - DBO:[372,l]SALES.LST
Destination File - GENEVA: :SALES.LST
463340
ER
/AF:28-JUN-83:15:30/IM/EX/LO
Queued 28-Jun-83 9:30
Tried 0 Times
Source File - BURMA: :COMMANDS.EXE

The File Transfer Spooler Utility (FTS)

4·33

Table 4·2: Summary of FTS Function Codes
Function
Code

Description

CLL

Concatenate local files to a local file

CLR

Concatenate local files to a remote file

CRL

Concatenate remote files to a local file

CRR

Concatenate remote files to a remote file

Delete file(s) on local node

Delete file(s) on remote node

Execute command file(s) issued for the local node

Execute command file(s) issued for a remote node

Print a file on the local node

Prin t a file on the remote node

SLL

Submi t a command file from a local node to a local node

SLR

Submit a command file from a local node to a remote node

SRL

Submit a command file from a remote node to a local node

SRR

Submit a command file from a remote node to a remote node

TLL

Transfer local file(s) to local file(s)

TLR

Transfer local file(s) to remote file(s)

TRL

Transfer remote file(s) to local file(s)

TRR

Transfer remote file(s) to remote file(s)

4-34

DECnet-RSX Guide to User Utilities

4.2.13 The· Set Default Operation
FTS Primary Switch: IOF

The set default operation allows you to define your own default values for
various arguments in a file descriptor. Using the IDF switch. you can set
default values for node names (complete with access control information).
devices, and UIes. However. the file name. type, and version number cannot
be assigned default values. Default values can be set to affect input files only
(by specifying :IN) or output files only (by specifying :OUT). You can define
the same default values for both input and output files by using one command
and omitting the :IN/:OUT specifiers. Defaults remain in effect for subsequent
files until they are changed or until you exit from FTS.
Format:

:IN
FTS>[defaults]/DF

:OUT
where
defaults

is any string of default argument values that you wish to define
in the command line. If omitted, FTS displays the last defaults set.

:IN

is the input file specifier. When you add this to the end of the
command line, :IN indicates that all the default values in the
command apply to input files only.

:OUT

is the output file specifier. When you add this to the end of the
command line, :OUT indicates that all default values defined in the
command apply to output files only.

Any file descriptor arguments that are not set with the IDF switch take the
standard defaults defined in Table 3-1. To determine what default values are
in effect at a given time. type the following command:
FTS>/DF<RET>
FTS will display the current IDF default values at your terminal.

The File Transfer Spooler Utility (FTS)

4·35

Example:

FTS>INVENT/STATUS/GEARS.: [224,l]/DF:IN<RET>
FTS>DBD:/DF:DUT<RET>
FTS>=INVENTDRY.LST<RET>
In this example, the first command line defines the input file defaults for
node name. access control information (luserid and Ipassword). -and VIC. The
second command line defines the device for output files. The transfer command
FTS> = INVENTORY.LST assumes the following input and output file
descriptor fields:
DBO: = INVENT/STATUS/GEARS::[224,l]INVENTORY.LST
If you wished to know the default values set in this example. IDF would print
the following itemization in response to FTS>/DF<RET>.

Source defaults = INVENT/STATUS/ ... : :[224.1]
Destination defaults = DBD:
Notice that the default password is printed in ellipses (... ) to maintain security.

4-36

DECnet-R8X Guide to User Utilities

4.2.14 The Spool Operation
FTS Primary Switch: ISP

The spool operation directs a file to a line printer on a local or a remote node
for printing. When a file is spooled to a remote node. its format must be
compatible with the remote system.
Format:

FTS>[outfile = ]infile(s)[/sw]/SP
where
olltfile

is an optional file descriptor that specifies the output file to which
the file will be copied and the system on which it will be spooled.
If outfile is omitted. the file specified by infile is spooled on the
source node.

infile(s)

is the file descriptor for each file to be spooled for printing.

fsw

is one (or more) of the following qualifying switches (defined in
Section 4.2.3):
fAF
fLO
IPR
ISE

The File Transfer Spooler Utility (FTS)

4·37

Example 1:

FTS>SITKA: :GOLD.FIL;l,HOME· :SNOW FIL;l/SP<RET>

In this example, one copy of the file COLD.FIL;l is spooled to the line printer
on node SITKA. and one copy of the file SNOW.FIL;l is spooled to the line
printer on node HOME.
Example 2:

FTS>HOME: :=SITKA: :CDLD.FIL;l,NOME: :SNDW.FIL;l/SP<RET>

In this example. one copy each of file COLD.FIL; 1 and file SNOW.FIL;l is
spooled to the line printer on node HOME. The input file names default to
the output file name.
4.2.15 The Submit Operation
FTS Primary Switch: ISB

The submit operation transfers a command file to a remote node and submits
the file to either a remote command file processor or a batch file processor
for execution. The command file is deleted (by the remote node) after the file
executes. The remote node must support command file submission and execution
(for example, RT-ll nodes do not support command file submission). When
you perform a submit operation, remember that the syntax of the command
lines within the command file must conform to the syntax standards of the
remote system on which the file is to be executed. To execute a command file
that is already on a remote node, you can use the execute (lEX) operation (see
Section 4.2.8).
For RSX systems, the command file can be submitted to either a command
file processor or a batch file procesor, depending on how the destination node's
command file submission task (MCM) was generated during NETGEN.
The success of the submit operation does not guarantee that the batch or
command file was executed successfully, only that the file was transferred and
that the execution request was successfully given to the MCM.

4·38

DECnet-RSX Guide to User Utilities

Format:

FTS)ollt/'ile = commandfile(lsw]/SB

where
outfile

is the file descriptor of the temporary file that is created on
the destination node. This temporary file receives the command
file's contents and is deleted after execution.

commandfile

is the input file descriptor of the file containing the commands
to be executed by the destination node's operating system. Only
one command file can be specified.

Isw

is one (or more) of the following qualifying switches (defined
in Section 4.2.3):
IAF
ILO
IPR
ISE

Example:

FTS>GENEVA: :DK1: [BUCKLEY] NEWFILE.CMD=COMMANDS.CMD; 5/SB<RET>

File COMMANDS.CMD;5 is transferred to GENEVA as NE\\7FILE.CMD and
is executed, and NEWFILE.CMD is deleted after execution.

The File Transfer Spooler Utility (FTS)

4·39

4.3 FTS Error Messages
If an error occurs during the processing of a user request, FTS prints one of
the following messages:
FTS -- Bad indirect file name

The indirect file name did not conform to the conventions used by the operating
system. RSX-IIM systems use the at sign (@). followed by the file specification.
FTS -- Command line too long

An FTS command line cannot exceed 256. characters. You can continue the
physical input line with the RSX-I1M continuation marker (-), but the actual
command cannot exceed the limit.
FTS _. Error in accessing work area

FTS was unable to open or write user request files to the work file area (see
Figure 4-1). Notify the system manager to set the work area directory to
unprotected.
FTS _. Error in communicating with alias task

FTS attempted to translate an alias node name to a real node name by issuing
a QIO to the network management driver. and the QIO failed.
FTS -- Error in date-time value

One or more of the values that you specified with the IAF switch is illegal.
Check your switch specification for an incorrect time or date argument. (IAF
is described in Section 4.2.3.)
FTS -- Error in destination file filedescriptor

An error occurred in accessing the specified local file. Check the output file
descriptor to see if it is correct. The variable filedescriptor specifies the incorrect
string.

4-40

DECnet-RSX Guide to User Utilities

FTS -- Error in getting command line

FTS found an error while retrieving a command line from the terminal. Retry
the command. and notify the system manager if repeated failures occur.
FTS -- Error in parse

A system error occurred while FTS was trying to check a command line for
syntax. Retry the command, and notify the system manager if repeated failures
occur.
FTS -- Error in source file filedescriptor

An error occurred in accessing the specified local file. Check the input file
descriptor to see if it is correct. The variable filedescriptor specifies the incorrect
string.
FTS -- File 1/0 error -- * FATAL *
secondary error message

FTS encountered an error in processing a local file. The secondary error
message gives the cause of the error. Possible secondary error messages are:
FCS error code: -no

A local file system error occurred during an operation involving a local file.
The number reported is a signed decimal value (see the IASIRSX-ll lIO
Operations Reference Manual).
No such file

The specified local input file does not exist.
Privilege violation

An operation was specified for which the user does not have privileges.

The File Transfer Spooler Utility (FTS)

4-41

QMG error code: n

The error specified in the primary error message occurred during an operation
involving the queue manager (QMG). See Section 4.4 for a listing of the
values for n, and refer to the RSX-JJ Utilities Manual for more detailed
information.
FTS -- Help file error: n

An error has occurred while attempting to use the help function (see Section
4.2.9). The variable n is a standard RSX I/O error code.
FTS -- Illegal command

A command line without file descriptors must have one of the following options
specified: lID, IHE, ILL lED, or IDF.
FTS -- Illegal equals sign

FTS format allows only one equals sign in a command line.
FTS -- Illegal use of switch

A command line contains a switch that IS incompatible with the command
type.
FTS -- Illegal wildcard

FTS allows wildcard specifications only for local input files.
FTS -- Incompatible switches

A command contains incompatible options.
FTS -- Initialization error -- * FATAL *

FTS failed to start up due to error responses to executive or network directives.

4-42

DECnet-RSX Guide to User Utilities

FTS •• Job does not exist

The specified FTS job number does not represent a job currently in the pending
request queue.
FTS •• Maximum indirect file depth exceeded

FTS allows only three indirect files to be specified in an indirect file. Check
your indirect file to see if you have exceeded the maximum.
FTS •• No help available

FTS could not find the help file. Normally, the help files for FTS are copied
to LB:(1.2] as a result of network generation (see the DECnet-RSX lVetwork
Generation and Installation Guide).
FTS •• No input files

FTS transfer command format requires at least one input file.
FTS •• No queue file space available

The FTS queue is temporarily full.
FTS •• No requests found

No user requests are queued for the node name and/or UIC indicated by a
ILl switch (see Section 4.2.12).
FTS .• Open failure on command file

FTS could not open the specified command file.
FTS •• QMG communication error
QMG error code: n

FTS has encountered an unexpected error while attempting to communicate
wi th the queue manager. Notify the system manager.
This error message is accompanied by the secondary error message QMG error
code: n. This message indicates that the specified queue manager error (n)
occurred during the queuing of an FTS user request. The number reported is
an unsigned decimal value. Possible values are listed in Section 4.4.

The File Transfer Spooler Utility (FTS)

4·43

FTS •• QMG marked for exit

The system manager has begun shutting down the queue manager. disabling
the queuing of FTS requests.
FTS .. QMG not installed

FTS was unable to communicate with the queue manager. Notify the system
manager.
FTS .- Queue does not exist

The FTS queue has not been properly initialized. Notify the system manager.
FTS .• Syntax error

The command line is not in a legal FTS format.
FTS -- Syntax error in option argument

A switch argument does not conform to legal FTS format.
FTS -- Too many files for command type

Certain FTS commands do not allow multiple input files.
FTS -- Too many files in command

FTS failed to find sufficient dynamic work space to process the command.
FTS -- Too many output files

FTS transfer command format allows only one output file. To specify multiple
file transfers. omit the file name and type.
FTS .. Unable to access network -- *FATAL *

FTS was started up and did not find network support.

4-44

DECnet-RSX Guide to User Utilities

FTS •• Unable to communicate with alias task

FTS attempted to translate an alias node name to a real node name by issuing
a QIO to the network management driver. and the QIO failed.

4.4 Queue Manager Error Codes
When a queue manager error occurs during the queuing of an FTS user request.
the following message prints out:
QMG error code: n
The value of n can be any of the decimal values listed in Table 4-3.
Table 4·3: Queue Manager Error Codes
Error Code

Meaning

l.
43.
63.
64.
65.
66.
67.
68.
69.
70.
7l.
72.
73.
74.
75.

Illegal function code
Pri vilege violation
Bad processor name
Queue exists already
Processor exists already
Queue does not exist
Processor does not exist
Queue marked for delete
Processor mar ked for delete
Queue directory full
Processor directory full
Queue and processor are not the same type
Job exists already
Job does not exist
No queue file space available
(continued on next page)

The File Transfer Spooler Utility (FTS)

4·45

Table 4·3 (cont.):Queue Manager Error Codes
Error Code

Meaning

76.
77.
78.
79.
80.
8l.
82.
83.
84.
85.
86.
87.
88.
89.
90.
91.
92.
93.-99.
100.
101.
102.
103.
104.
105.

I/O error on queue file
Redundant operation
Illegal argument value
Executive directive failure
Spooled device bad type
Spooled device does not exist
Spooled device driver off line
Spooled device not loaded
Spooled device redirected
Spooled device not available
Reserved
No pool space
Prototype processor task not installed
Request failure on processor task
QMG marked for exit
Immediate device busy
Bad queue name
Reserved
Virtual terminals not supported
Entry is not a job entry
Operation inconsistent with job state
Reserved
Illegal or nonexistent intermediate device
Intermediate device not mounted

4·46

DECnet-RSX Guide to User Utilities

5
The Network Command Terminal Utility (NCT)

The Network Command Terminal utility (NCT) allows you to log on to a host
system and communicate with all programs that are run under that remote
operating system. When using NCT. your terminal is physically connected to
the host system (see Figure 5-1). Once you connect to a host. NCT requires
that you specify system-specific commands.
NCT functions using the heterogeneous command terminal protocol, CTERM.
NCT. or the network command terminal server process. resides on your local
node and allows you to logically connect your terminal to any host node which
supports the Terminal Services Architecture (TSA). (RTH. the remote command
terminal host process on RSX nodes. will also reside on your local node. so
that remote users can connect to your local node. via NCT.)
NCT is availablt.> on RSX-11M-PLUS. RSX-IIM/RSX-llS V 4.2 (or greater).
and IVlicro/RSX systems. You should note that NCT is not supported on
DECnet-11M-PLUS versions prior to V3.0. DECnet-ll~l/11S versions prior to
V 4.1. or VMS versions prior to V 4.0.

The Network Command Terminal Utility (NCT)

5·1

(J1

LOGICAL LINK
DECNET-VAX
NODE VAX5

o::J

~
I
:D

en
x

a:
CD

o
c
C/)

NOTE: ONCE CONNECTED to the remote VMS host operating system. you must specify
operating system level commands to the host

....

::+
(D"
C/)

Figure 5·1: The NCT Utility: Access to Remote Host Operating System
Resources

TW139

5.1 Connecting to a Host System
To connect to a VMS or RSX host operating system. you must set host to
the host node. using the appropriate command format for your local eLI shown
here:
MCR Format for DECnet·11M/M·PlUS Systems:

>SET IHOST =hostnode[::]
MCR Format for DECnet·11 S Systems:

>RUN SETHST <-RET>
Host:
hostnode[::]
Where

hostnode is the 1- to 6-alphanumeric-character node name (containing
at least 1 alphabetic character) of the VMS or RSX host node.

MCR Example (Connect to RSX Host):

>SET /HOST=RAISIN <RET>
Connected to "RAISIN", System type
System 10: RSX-l1M-PLUS V3.0

RSX-l1M-PLUS

>HELLO FRASER <RET>
Password:
<RET> (the password does not echo)
GOOD AFTERNOON
>

DCl Format:

$SET HOST hostnode
Where

hostnode is the 1- to 6-alphanumeric-character node name (containing
at least 1 alphabetic character) of the VMS or RSX host node.

The Network Command Terminal Utility (NCT)

5-3

DCl Example (Connect to VMS Host):

$SET HOST VAX5 <RET>
Username: FRASER <RET>
Password:
<RET> (the password does not echo)
Welcome to VAX/VMS V4.0 on node VAX5
$

5.2 Disconnecting from a Host System
There are two methods of disconnecting from a host system. You can either
log off the host system or enter terminal management mode and use the
CLEAR HOST command. Both methods are described below.
5.2.1 Logging Off a Host System
If you are connected to an RSX host system. type BYE to log off the host.

For example:
>BYE <RET>
>

Connect time: 1 minute
CPU time: 1 second
Task total: 1
Have a good afternoon
7-AUG-84 22:02 RT2: logged off RAISIN
>

NCT -- Control returned to node "local node"

>
Where

local node is the name of your local DECnet-RSX node.
NOTE

If you are connected to an RSX host node. you also have the
option of specifying BYE/HOLD. Typing BYE/HOLD will
return you to the CLI prompt, and although you are still
connected to the host. you must log back in if you still want
to use the host system resources.

5·4

DECnet-RSX Guide to User Utilities

If you are connected to a VMS host system. type LOGOUT to log off the
host. For example:
$LOGOUT <RET>
FRASER logged out at 7-AUG-84 22:02:58.31
NCT -- Control returned to node "local node"
)

Where

local node is the name of your local DECnet-RSX node.

5.2.2 Entering Terminal Management Mode

Terminal management is a control task which resides on your local node.
Terminal management mode allows you to:
• Continue your session on the host node.
• End your session on the host node.
Type <CRTLI\) <RET) to enter terminal management mode. «CTRLI\) means
that you type the <CTRL) key and the back slash (\) key, simultaneously.)
When you enter terminal management mode. your local node prompts you for
input. as shown in the example below:
$<CTRL/\> <RET>
RAISIN>

If you want to continue your session on the host node. type CONTINL'"E
<RET) in response to your local node prompt.
If you want to end your session on the host node, type CLEAR HOST <RET)
in response to your local node prompt. When you enter the CLEAR HOST
command. you will receive a disconnect message from NCT confirming that
control has been returned to your local node. as shown in the example below:
RAISIN> CLEAR HOST <RET>
NCT -- Control returned to node "RAISIN"
>

The Network Command Terminal Utility (NCT)

5·5

5.3 Sample NeT Session
In the following NCT session. you connect from your local DECnet-RSX node.
RAISIN, to a remote VMS host node. VAX5. Once logged on to the VMS
host. you specify the DIRECTORY command to obtain a list of files. You
then specify the COPY command to copy PEOPLE.LST;l to your account on
node RAISIN.

>SET /HOST=VAX5 <RET>
Username: FRASER <RET>
Password:
<RET> (the password does not echo)
Welcome to VAX/VMS V4.0 on node VAX5
$DIRECTORY <RET>
Directory USER$DISK: [FRASER]
REMINDER.CMD;1
LOGIN.CMD;1
NFTTEST.LOG;1

MASTERINI.CMD;l
PEOPLE.LST;l
TSETCMP.LOG;l

TELI.CMD;l
NULLTEST.LST;1
SETCMP.LOG;1

TESTFILE.COM;l
COPY.LST;1

Total of 11 files
$COPY <RET>
_From:
VAX5"FRASER PASSWORD": :PEOPLE.LST;l <RET>
_To:
RAISIN"FRASER PASS2": :PEOPLE.LST;1 <RET>
$LOGOUT <RET>
FRASER logged out at 7-AUG-84 22:02:58.31
NCT -- Control returned to node "RAISIN"
>

5-6

DECnet-RSX Guide to User Utilities

5.4 NCT Error Messages
NeT returns both connect and disconnect errors. These error types are defined
here:
• Connect Errors. These errors can be returned by either your local node or

the host node. depending on the reason for the error.
• Disconnect Errors. These errors occur when a logical link to the host node

is aborted by the network.
5.4.1 Connect Errors
NCT .• No more LUNs

There are no available outgoing ports on your system. You can try the connect
again. (A port will not be available until another user on your system who is
engaged in a remote session ends that session.)
NCT •• Terminal is already attached

Your terminal is attached by another task. You can find out what task is
running and abort the task to free up your terminal.
NCT •• No pool available

There is no system pool available for you to use NeT. You can wait awhile
and try the connect again.
NCT •• Connection rejected, Invalid node name format

The logical link could not be connected because the host node name format
was incorrect. A node name is deemed invalid if it contains illegal characters.
and/or is too long.
NCT •• Connection rejected, Rejected by object

The logical link could not be connected because the remote object rejected the
connect.

The Network Command Terminal Utility (NCT)

5·7

NCT •• Connection rejected, Network modules not installed

The required CTERM modules are not installed on your system. Consult your
system manager.
NCT .• Connection rejected, Node unreachable

The logical link could not be connected because no path existed to the host
node.
NCT •• Connection rejected, No response from object

The logical link could not be connected because the remote object did not
respond. The object either responded too slowly or terminated abnormally.
NCT .• Connection rejected, Access control rejected

The logical link connection was rejected because the network partner could
not validate the access control information it received.
NCT •• Connection rejected, Local node shutting down

The logical link could not be connected because the network on the local node
was shutting down.
NCT .• Connection rejected, Object too busy

The logical link connection was rejected by the network partner because the
remote obj ect was too busy handling other logical links.
NCT •• Connection rejected, Remote node shutting down

The logical link could not be connected because the network on the remote
node was shutting down.
NCT .• Connection rejected, Unrecognized node name

The logical link could not be connected because the local node could not map
the destination node name to any known node address.

5·8

DECnet-RSX Guide to User Utilities

NCT -- Connection rejected, Insufficient network resources

The logical link connection was rejected due to inst).fficient network resources
on either the local or remute node
NCT -- Connection rejected, Unknown reject reason

= reason

This error is returned in rare cases of unexpected, unknown errors. You can
try the connect again. If the error persists, you can submit a software
performance report (SPR). (See the DECnet-RSX Release Notes for instructions
on submitting an SPR.)
NCT -- CTERM not available on host

The CTERM host protocol is not available on the host node. In this case,
NCT will attempt to use RMT as an alternative method of connecting to the
host.
If your node supports RMT, you will receive the following message:

NCT -- Using RMT
If your node does not support RMT. you will receive the following message:

NCT -- RMT not available on local node
NOTE

RMT cannot be used to connect to a VMS system (see Chapter
6). Therefore, if NeT attempts to use RMT as an alternative
means of connecting to a VMS host. an error will result.

The Network Command Terminal Utility (NCT)

5-9

5.4.2 Disconnect Errors
NCT -- Connection aborted, Incompatible CTERM versions

The version of CTERM on your local node cannot communicate with the
version of CTERM on the host node.
NCT -- Connection aborted, CTERM protocol error

A CTERM protocol error occurred on either the local or host node. In this
case, you may want to submit a software performance report (SPR). (See the
DECnet-RSX Release Notes for instructions on submitting an SPR.)
NCT -- Connection aborted, Remote node or object failed

The logical link was aborted because the remote node or object terminated
abnormally.
NCT -- Connection aborted, Link aborted by object

The logical link was aborted because the remote object terminated abnormally.
NCT -- Connection aborted, Link aborted by network management

The logical link was aborted by a user or a program using network management.
NCT -- Connection aborted, Unknown disconnect reason

= reason

The logical link was aborted due to some rare, unexpected, and unknown
reason. In this case, you may want to submit a software performance report
(SPR). (See the DECnet-RSX Release Notes for instructions on submitting an
SPR.)
NCT -- Connection aborted, Node unreachable

The logical link was aborted because the path that existed to the host node
was broken.

5-10

DECnet-RSX Guide to User Utilities

6
The Remote Terminal Utility (RMT)

The Remote Terminal utility (RMT) logically connects your terminal to another
DECnet-RSX target node. This connection allows you to log on to the host
node and to use its resources as though your terminal were physically connected
to the host node. Whenever you use RMT, the local node is the node to which
your terminal is physically connected. The host node is the node to which you
are logically connected by means of RMT. Figure 6-1 illustrates the RMT
utility.
The RMT utility allows you to connect to any host in the network that
supports the RMT host facility (RMHACP). When you are connected to the
host system by means of RMT. your terminal device is designated HT:. With
RMT. you can use any facility that is mutually supported by HT: and the
local terminal driver. This excludes the TLK utility. which supports only the
TT: device. See Appendix A for QIO functions supported by the HT: driver.
The RMT utility is supported on RSX-IIM. RSX-IIM-PLUS, and RSX-llS
local node operating systems. Likewise, the host system can be any of these
three systems.

The Remote Terminal Utility (RMT)

6·1

CJ)
I

LOGICAL LINK

--------------~I DECNET-RSX
NODE WASH

o::J

*
:0

(f)

(j)

c
0:
CD

o
c

(/)

CD
...,

TW140

a;"
(/)

Figure 6-1: The RMT Utility: Access to Remote DECnet-RSX Node Resources

6.1 Connecting to a Host Node
To connect to a host node. you must invoke RMT and supply the name of
the node to which you want to connect. There are three methods by which
you can do this. Methods 1 and 2 apply to DECnet-l1M or DECnet-llM-PLUS
operating systems; method 3 applies to DECnet-l1S operating systems.
NOTE

You should not invoke the RMT utility from an indirect
command file or from a batch job. The results are unpredictable
and depend heavily upon the system and the timing involved.
Method 1: DECnet-11 M and DECnet-11 M-PLUS Systems

Type RMT after the MCR (or DCL) prompt. RMT then prompts you for a
host name. After you enter a host name, RMT establishes the connection and
identifies the type of operating system to which you are connected.
>RMT<RET>
Host: BASIN<RET>
Connected to "BASIN", System type = RSXllM-Plus
System 10: *OECNET-llM-Plus V3.0 5/24/84*
Method 2: DECnet-11 M and DECnet-11 M-PLUS Systems

Invoke RMT and enter the host node name on the same line:
>RMT BASIN<RET>
Connected to "BASIN", System type = RSXllM-Plus
System 10: *OECNET-llM-Plus V3.0 5/24/84*
Method 3: DECnet-11 S Systems

Issue the RUN command for RMT after an MCR prompt (»:
>RUN RMT<RET>
Host: BASIN<RET>
Connected to "BASIN", System type = RSX11M-Plus
System 10: *DECNET-llM-Plus V3.0 5/24/84*

The Remote Terminal Utility (RMT)

6-3

The host node name is defined by $HOST and can be changed by the system
manager using either the Network Control Program (NCP) or the virtual
network processor (VNP). If you omit the host node name, the default host
node name is substituted for it. The default host node name is initialized to
be the local node name for RSX-IIM. RSX-llM-PLUS. and RSX-l1S systems.
If an RSX-llS system has been down-line loaded. $HOST is set to the name
of the system from which RSX-llS was loaded. Refer to the DECnet-RSX
Network Nfanagement Concepts and Procedures manual for more detailed
information on setting the default host node name.
The following example illustrates a sample RMT log-in to remote host node.
MANCE.
Example RMT Log-in:

>RMT<RET>
Host: MANCE<RET>
Connected to "MANCE", System type
System ID: MAPPED RSX11M V4.2

RSX11M

>HELLO CASEY<RET>
PASSWORD:
<RET> (the password does not echo)
RSX-l1M V4.2 MULTI-USER
GOOD MORNING
3-MAY-85 10:12 LOGGED ON TERMINAL HT3:
>

6.2 Disconnecting from a Host Node
When you finish remote terminal operations, type BYE to log off the host
system. For multiuser host systems, typing BYE automatically disconnects
you from the host node and returns control to the local operating system.
If you want to stay connected to the host node, you can specify BYE/HOLD.
Typing BYE/HOLD will return you to the MCR prompt, and although you
are still connected to the host, you must log back in if you still want to use
the host system resources.

6-4

DECnet-RSX Guide to User Utilities

Example:

>BYE<RET>
>
HAVE A GOOD AFTERNOON
21-MAY-84 14:20 HT2: LOGGED OFF
RMT -- Control returned to node local node::

>
You can also disconnect from the host node by typing EXIT RMT in response
to an MCR prompt.
If your terminal is externally forced to log off the local system without first
exiting from the RMT task. RMT automatically terminates your connection
with the host node.
If, for some reason. the RMT connection to the host node is terminated before
you can log off, the HT: on the host will automatically be logged off.

6.3 Aborting RMT
On DECnet-llM-PLUS systems. the Remote Terminal task (RMTACP) is made
abortable through an Executive feature. Since this feature does not exist on
RSX-IIM or RSX-llS. it is possible for a privileged user to abort the task
while it is in use. If RMTACP or any other privileged task is aborted, the
system data structures may be left corrupted.

The Remote Terminal Utility (RMT)

6·5

If such an abort occurs the user" that are connected through RMT can enter
a "garbage" line. This line cause~ RMTACP to be invoked again and resets
their terminals to the original qtate.

If RMTACP is aborted. it should not be removed from the system until all
terminals are reconnected to the local system. Premature removal of RMT ACP
after an abort may lead to a system crash.

6.4 RMT Control Character Handling
RMT handles most control characters «CTRL/O>, <CTRL/S>, <CTRL/Q>, and
<CTRL/R» according to standard RSX-ll conventions. However, <CTRL/C>
causes RMT to prompt for input (RMT» and then pass that input to the CLI
on the host system (generally either MCR or DCL). This procedure differs
from conventional RSX-ll usage, where <CTRL/C> directly initiates a local
CLI prompt (for example, MCR».
Example:

>MAC @BCASMASM<RET>
<CTRL/C>
RMT>ACT<RET>
MCR ...
ACTH3
MACH3

6·6

DECnet-RSX Guide to User Utilities

6.5 Sample RMT Session
The following example depicts a typical RMT session. The example shows a
connect to host node ALIEN from local node TERRAN, the issuing of a PIP
command for a directory list. and a subsequent exit from Rl\IT.

>RMT ALIEN<RET>
Connected to "ALIEN", System type = RSX11M
System ID: REMOTE TERMINAL TEST SITE
>HELLO DALEY<RET>
PASSWORD:
<RET> (the password does not echo)
RSX-11M V4.2 MULTI-USER SYSTEM
GOOD AFTERNOON
15-MAR-84 14:23 LOGGED ON TERMINAL HT3:
>PIP [354,20]/LI<RET>
DIRECTORY DBO: [354,20]
15-MAR-84 14:27
RMHACP. OLB; 10
HTDRV. OLB; 10
RMHACP.CMD;7
<CTRL/C>
RMT>ABO PIP<RET>
14:28:57

110.
19.
14.

04-MAR-84 11:52
C 04-MAR-84 11:53
06-MAR-84 12:32

TASK "PIPH3" TERMINATED
ABORTED VIA DIRECTIVE OR MCR
AND WITH PENDING 10 REQUESTS

>EXIT RMT<RET>
RMT -- Control returned to node TERRAN::
>

The Remote Terminal Utility (RMT)

6·7

6.6 RMT Error Messages
If one of the following errors occurs during an RMT session. you are
automatically logged off the host system and disconnected from the host node.
RMT -- Cannot access RMT service task (RMT ACP)

The local node service task (RMTACP) was not installed.
RMT -- Cannot access terminal

A terminal input error has occurred.
RMT -- Command syntax error

The node name was entered in an illegal format.
RMT _. Illegal RMT terminal device

The terminal used to invoke RMT is not a TT: device.
RMT •• Initialization failure

RMT failed to go through its start-up initialization properly.
RMT _. Network access failure

RMT could not open the network.
RMT _. No connections available at remote node

The number of connections established at the host node exceeds the number
allowed.
RMT •• No more remote connections available

The number of local users simultaneously using RMT exceeds the number of
remote connections available to RMT.

6-8

DECnet-RSX Guide to User Utilities

RMT -- No such node
R~IT could not connect to the specified host node. Either the node is not in
the network. or its name has not been defined by the system manager.

RMT -- Recursive use of RMT not allowed

The R~IT task cannot be invoked on the host node.
RMT -- Remote connection aborted

The connection to the host node has been abnormally terminated. (When this
error occurs. it is likely that the link has been aborted.)
RMT -- Remote connection already established

The terminal used to invoke RMT is already connected to a host node by
means of RMT.
RMT -- Remote host incompatibility error

The host service task (RMHACP) version is not compatible with RMT.
RMT -- Remote server not installed on remote node

RMT successfully connected to the host node. but the remote terminal host
service task (RMHACP) was not installed.
RMT -- Resource allocation failure

System resources were unavailable for use.
RMT -- Unable to communicate with node

RMT could not successfully connect to the host node.

The Remote Terminal Utility (RMT)

6-9

7
The Phone Communications Utility (PHO)

The Phone Communications utility (PHO) allows you to engage in an interactive
dialog with one or more users on your node or on a remote DECnet-RSX.
DECnet- VAX. or PRO/D ECnet node. PHO simulates the features of an actual
telephone. including the hold feature. the telephone directory, and conference
calling. In addition. PHO provides many advanced features that are not
available with the TLK utility (see Chapter 8) such as the ability to "phone"
a person by name. to leave a message with someone who was not in when
you "phoned" them, or to include the contents of a file in your conversation.
The advanced features of PHO require the use of resource accounting
information not available on RSX-IIlVI or RSX-llS systems. Therefore, PHO
is available only on RSX-IIJVI-PLUS and Micro/RSX systems.
Tables 7-1 and 7-2 list and describe the PHO qualifiers and commands.
respectively. Section 7.4 describes each PHO command in detail. Table 7-3
describes the control characters used for formatting your PHO sessions. Figure
7-1 depicts the screen format for the PHO utility. Figure 7-2 depicts a sample
PHO conversation.

7.1 PHO Screen Format
PHO can be used only on video terminals with direct cursor positioning, such
as VT200, VT100, and VT52 terminals. When PHO is invoked, your screen
will appear much like the sample screen shown in Figure 7-1.

The Phone Communications Utility (PHO)

7·1

Each participant In a phone conversation has his/her own viewport area on
the screen. Each participant' s viewport is marked with his/her DECnet node
name and user name and is separated from other participants' viewports with
a broken line (see Figures 7-1. 7-2). Each participant's conversation text appears
in his/her own viewport. (along with various status messages. sucn as HOLD
messages).
PHO can display up to six viewports at one time. Thprefore. people that you
ha ve on hold can be temporarily eliminated from your s( reen to make room
for new participants.
RS){-llM-PLUS Phone FaCIlIty
/..

8-AUG-811

(COMMAND INPUT LINE)
(STANDARD MESSAGE LINE)

1
1
1

NOOENAME::USERNAME

(VIEWPORT)

- - - ---- - --- -- - - - - - - ----------------------NODENAME::USERNAME
(VIEWPORT)

!
NOTE: The switch hook character shown in this sample screen is the default percent sign,
(%). The switch hook character is always displayed in column 1 of the command input
line.
TW141

Figure 7·1: The PHO Utility: Sample Screen Format

7·2

DECnet-RSX Guide to User Utilities

-i
:::r

-u

:::r

:::l

USER SMITH'S SCREEN ON NODE YUKON

USER JONES' SCREEN ON NODE BASIN

(I)

oo
3
3

:::l

RSX-llM PLUS Phone Fac i l i t.v B-AUG-B4
'1

RSX-llM PLUS Phone FaCIlIty 8-AUG-B4
'1

o·

-ci"
Q)

:::l

~
;:+

YUKON: :SMITH
Hi. How are vou?
I was wonderin. if vou Made it. t.o Larrv Anderson's
bud.et. Meet.in., vest.erdav.

Great.. Bv t.he way, could YOU send Me a copy
of t.he fi le, BUDGET .DAT?

-:0

Thanks. Talk t.o vou lat.er.

Bve.

BASIN::JONES
I'M fIne, t.hanks •••• What.'s up?
Yes, I was there. It looks like we're ~oin~ to be
adequate}}' funded for the next fIscal }'ear.
Sure, I'll send It lMMediatelv, vIa NFT.
O.K. Bye.

YUKON: :SMITH

BASIN::JONES
I'M fine, t.hanks . . . . What.'s up?

HI. How are }'ou?

Yes, I was t.here. It. looks like we're .oin. t.o be
adequat.ely funded for t.he next. fiscal Year.

bud~et

Sure, I'll send it. iMMediat.elY, viaNFT.
O.K. Bve.

I was wonderln~ If vou Made It to Larr}' Ar,derson 's
Meet in' , yesterdav.

Great. Bv the wav, could }'O'J send Me a copy
of the flle , BUDGET. OAT?
Thar,ks. Talk t.o }'O'J later.
Bve •

......

Figure 7-2: The PHO Utility: Sample PHO Conversation

7.2 Conference Calls
Conference calls allow thrPt' or more users to engage in an interactive.
concurrent PHO session. When setting up a conference call. one participant
should act as the operator. This person should set up the conference by calling
the other participants in turn and waiting for a response.
Only users who are currently participating in a conference call can bring new
participants into the conference with the DIAL command (see Section 7.4.2).
If you (or any of your fellow conference call participants) should dial a person
who is currently engaged in his/her own conference call. you will talk only to
that person.

7.3 Invoking Phone
To invoke PHO. use the following command format:
PHONE[/qualifier(s)] [command]

where
I qualifier(s)

is one or more of the qualifiers that modify the characteristics
of a PHO session. Table 7-1 lists and describes the PHO
qualifiers.

command

is one of the PHO commands that is to be executed before
PHO prompts you for additional commands. Table 7-2 lists and
briefly describes each PHO command. Section 7.4 describes each
PHO command in detail.
NOTE

When invoking PHO or when specifying any PHO command,
you can truncate the word PHONE and any of its command
keywords to the first three letters.
7.3.1 Exiting from PHO

Typing either <CTRL/Z> or the EXIT command will exit you from PHO and
return control to your Command Language Interpreter (CLI). (If you are
engaged in a PHO conversation. typing <CTRL/Z> will hang up your phone,
and you will then have to type either <CTRL/Z>, again. or use the EXIT
command to exit from PHO.)

7·4

DECnet-RSX Guide to User Utilities

Table 7-1: Summary of PHO Qualifiers
Qualifier

Function

ISCROLL
INOSCROLL

Specifies how the text in your viewport (the area
on your screen where your conversation text is
displayed) is scrolled when your viewport becomes
full. When ISCROLL is specified, your conversation
text is scrolled up one line. and a new line of text
appears on the bottom line of your viewport. When
INOSCROLL is specified, new text entering your
viewport is wrapped and appears on the top line of
your viewport. (Specifying INOSCROLL improves the
response time on slow-speed terminals.) The default
is ISCROLL.

IVIEWPORT SIZE =n

Specifies the maximum number of lines in your
viewport. (A viewport extends from the heading line
down to the bottom line of dashes.) The valid range
of lines in a viewport is 3 to 10. with a default of
10 lines. (Smaller viewports improve the response
time on slow-speed terminals.)

ISWITCH_HOOK=c

Specifies the PHO switch hook character for a
particular PHO session. The switch hook character
is typed in a PHO session to instruct the PHO utility
to treat the text following the character as a PHO
command. Text typed without this preceding
character is considered part of the PHO conversation.
The default switch hook character is the percent sign
(%).

For example, if you are engaged in a PHO
conversation and you want to know if Joe Smith is
available to phone on node YUKON. you can type
the switch hook character and enter the command
DIR YUKON <RET), and the phone directory for
node YUKON will be displayed on your screen. When
you subsequently type any character key, you will
be returned to your phone conversation.
The switch hook character is always displayed in
column 1 of the command input line (see Figure 7-1).

The Phone Communications Utility (PHO)

7-5

Table 7-2: Summary of PHO Commands
Command

Meaning

ANSWER

Answers the phone when you receive a call.

DIAL

Phones another user.