Digital PDFs

AA-PB61A-TE

May 1990

75 pages

Original

3.0MB

Document:	DECnet—ULTRIX
Order Number:	AA-PB61A-TE
Revision:	000
Pages:	75
Original Filename:

OCR Text

DECnet-ULTRIX

Use

May 1990
This manual shows how you use the DECnet-ULTRIX user
commands to perform file transfer and other user tasks.

Supersession/Update Information:

This is a new manual.

Operating System and Version:

ULTRIX V4.0

Software Version:

DECnet-ULTRIX V4.0

o
Order Number: AA-PB61A-TE

AA-PB61 A-TE
May 1990

The infonnation in this document is subject to change without notice and should not be construed as
a commitment by Digital Equipment Corporation. Digital Equipment 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.
Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions
as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software
clause at DFARS 252.227-7013.

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

PDP
ULTRIX
UNIBUS

VAX
VMS

~DmDDmDTM

UNIX is a registered trademark of AT&T in the USA and other countries.

This manual was produced by Networks and Communications Publications.

o
Contents
Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 1

vii

Introduction to the DECnet-ULTRIX Product

1.1

DECnet-ULTRIX User Commands and Utilities. . . . . . . . . . . . . . . . . . . . . . .

1-2

1.2

DECnet-lnternet Gateway Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-2

1.3

DECnet-ULTRIX Programming Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-3

1.4

DECnet-ULTRIX Network Management Features . . . . . . . . . . . . . . . . . . . . . .

1-3

1.5

Similarities Between DECnet-ULTRIX and ULTRIX. . . . . . . . . . . . . . . . . . . . .

1-3

1.6

Displaying On-Line Manual Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-4

C'
Chapter 2

Logging On to a Remote DECnet Node

2.1

Understanding dlogin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-1

2.2

Logging On to a Remote DECnet Node ......... . . . . . . . . . . . . . . . . . . .

2-2

2.3

Logging Off a Remote Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-2

2.4

Entering Local Command Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-3

2.5

Displaying a List of dlogin Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-3

2.6

Suspending the dlogin Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-4

2.7

Recording the dlogln Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.7.1
Creating a Log File ...................................
2.7.2
Adding New Log Information to a Log File. . . . . . . . . . . . . . . . . . . .
2.7.3
Closing a Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-4
2-4
2-5
2-5

2.8

Selecting a New dlogin Escape character .......................... .

2-5

2.9

Using the Escape Character Without Entering Local Command Mode ...... .

2-6

o
iii

Chapter 3

Sending Mall to Users on Remote OECnet Nodes

3.1

The DECnet Mail Address ..................................... .

3-1

3.2

Sending Mall to a Remote DEenet User ........................... .
3.2.1
Mailing a New Message ............................... .
3.2.2
Mailing a File to a Remote DEenet User .................... .
3.2.3
Special Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-1
3-2
3-2
3-2

Chapter 4

Specifying Files on Remote OECnet Nodes

4.1

File Specification Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-1

4.2

Using Wildcard Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-2

4.3

Supplying Access-Control Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.1
Entering the Information Manually . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.1 .1
User Name and Password. . . . . . . . . . . . . . . . . . . . . . .
4.3.1 .2
User Name Only (Password Required) ............. .
4.3.1.3
User Name Only (Password Not Required) .......... .
4.3.2
Using an Alias ...................................... .
4.3.3
Using Proxy Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

Chapter 5

(-~
I

'"","

Working with Files on Remote OECnet Nodes

5.1

Viewing Remote Directories ................................... .
5.1.1
On ULTRIX Remote Nodes ............................. .
On Non-ULTRIX Remote Nodes .......................... .
5.1.2

5-1
5-2
5-2

5.2

Displaying and Concatenating Remote Flies . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.1
Displaying Remote Files on the Screen . . . . . . . . . . . . . . . . . . . . . .
5.2.2
Concatenating Remote Files ............................ .

5-2
5-2
5-3

5.3

Copying Flies Between Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.1
From Local to Remote Node . . .. ". . . . . . . . . . . . . . . . . . . . . . . . .
5.3.2
From Remote to Local Node ............................ .
From Remote to Remote Node .......................... .
5.3.3

5-3
5-3
5-3
5-4

5.4

Converting File Names During File Transfer . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.1
dcp -c Option Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.2
Setting -c Option Rags ................................ .

5-4
5-4
5-5

5.5

Deleting Remote Flies ........................................ .
5.5.1
A Single File ....................................... .
5.5.2
Multiple Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.3
All Files of a Single File Type ........................... .

5-5
5-5
5-6
5-6

c:'

o
iv

Chapter 6

Appendix A

6-2
6-3
6-6
6-8

6-10
6-12

Error Messages

A.1

Connect Errors ............................................ .

A-1

A.2

File-Access Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A-2

Appendix B

o
c

DECnet-ULTRIX Command Summary
dcat(1dn) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
dcp(1dn) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
dlogin(1dn) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
dls(1dn) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
drm(1dn) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DECnet File Specifications

B.1

DECnet-ULTRIX File Specification ............................... .

B-2

B.2

DECnet-VAX File Specification ................................. .

B-4

B.3

DECnet-RSX and DECnet-IAS File Specifications .................... .

B-S

B.4

DECnet/E File Specification .................................... .

B-6

B.S

DECnet-10 File Specification ................................... .

B-7

B.6

DECnet-20 File Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-8

B.7

DECnet-RT File Specification ................................... .

B-9

B.8

DECnet-DOS File Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-1 0

Glossary

Index

Tables
1-1

Overview of DECnet-ULTRIX User Commands and Utilities . . . . . . . . . . . . . . . .

1-2

4-1

File Specifications for DEC net Nodes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-1

4-2

ULTRIX Metacharacters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-2

4-3

Wildcard Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-3

6-1

DECnet-ULTRIX Command Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-1

o
v

o
Preface
This manual contains both tutorial and reference material for DECnet-ULTRIX.
end users.

Intended Audience
This manual is for anyone who wants to use DECnet-ULTRIX to log on to remote
DECnet nodes, exchange mail with users on remote DECnet nodes, and work
with files on DECnet nodes. You should be familiar with the ULTRIX operating
system and general file transfer principles. You should also know how to work on
the DECnet nodes you plan to access via remote login.

Structure of This Manual

This manual contains six chapters and two appendixes:

•
•

Chapter 1 introduces DECnet-ULTRIX. product features and utilities.
Chapter 2 describes how to use the dlogin command to log on to other DECnet
systems.

•

Chapter 3 describes how to use the ULTRIX. mail utility to exchange mail
with DECnet nodes.

•
•

Chapter 4 explains how to specify remote files on a DECnet node.
Chapter 5 describes how to display, copy, and delete files and directories on a
remote DECnet node.

•

Chapter 6 describes the DECnet-ULTRIX. commands in detail. This reference
chapter is also available on line using the man command.

•
•

Appendix A lists the DECnet-ULTRIX error messages.
Appendix B shows sample DECnet file specification formats.

o
vii

Related Documents
'lb supplement the DECnet-ULTRIX Use manual, see the following DECnetULTRIX documents:

•

DECnet-ULTRIX Release Notes
This document contains miscellaneous information and updates not included
in other books in the DECnet-ULTRIX documentation set.

•

DECnet-ULTRIX. Installation
This manual describes procedures for installing, customizing, and testing
a DECnet-ULTRIX node for proper operation. This manual also lists the
DECnet-ULTRIX distribution files and the directory path names.

•

DECnet-ULTRD( DECnet~Internet Gateway Use and Management
This manual describes how to install, use, and manage the DECnet-Internet
Gateway.

•

DECnet-ULTRIX. Programming
This manual explains concepts and offers guidelines for application programming in the DECnet-ULTRIX programming environment. This manual
also describes DECnet-ULTRIX system calls and subroutines, and shows
DECnet-ULTRIX. data structures and programming examples.

•

",,--

DECnet-ULTRIX Network Management
This manual describes procedures for managing the network, such as defining permanent and volatile databases, defining node identifications and
addresses, defining lines and circuits, enabling event logging, displaying network counter information, operating and controlling a DECnet-ULTRIX node,
and testing the network operation.

•

DECnet-ULTRIX NCP Command Reference
This manual describes the Network Control Program (ncp) commands for
defining, monitoring, and testing your network.

To obtain a detailed description of the Digital Network Architecture, see DECnet
Digital Network Architecture (Phase IV), General Description.

For a beginner's introduction to the ULTRIX operating system, see The Little
Gray Book: An ULTRIX Primer.

o
viii

Graphic Conventions
This manual uses the following conventions:
Convention

Meaning

special

In running text, ULTRIX. commands, command options, user
names, file names, and directory names appear in special
type.

example

Indicates an example of system output or user input. System
output is in black type; user input is in red type.

10wercaselUPPERCASE

Because the ULTRIX. software is case sensitive, you must
type all literal input in the case shown. In running text,
UPPERCASE is also used for the names of all DECnet nodes,
including DECnet-ULTRIX. nodes. This convention follows
DECnet protocol, which names and recognizes all nodes in
UPPERCASE. However, node names are not case sensitive and
need not be typed in the case shown.

italic

Indicates a variable, for which either you or the system specifies a value.

[

On command syntax lines, square brackets indicate optional
arguments. Do not type the brackets.

]

Indicates a key on your keyboard. I CTRLJkey I represents a
CONTROL key sequence, where you press the CONTROL key
at the same time as the specified key. Note that keyboard keys
are represented by this symbol, <key>, on line.
Indicates the RETURN key.
The percent sign, the standard ULTRIX system prompt, is
used in all examples in this manual to indicate an ULTRIX.
system.

The dollar sign, the standard VMS system prompt, is used in
all examples in this manual to indicate a VMS system.
NOTE

All numbers are decimal unless otherwise noted.

Terminology
In this manual, "DECnet-RSX" stands for any of these DECnet products:
DECnet-llM-PLUS, DECnet-MicroIRSX, DECnet-llS, DECnet-llM.
The following acronyms are used in this manual:
DDCMP

Digital Data Communications Message Protocol

DNA

Digital Network Architecture

F1'P

File Transfer Protocol

TCPIIP

Transmission Control ProtocollInternet Protocol

o
ix

o
I

,I;,'I

Chapter 1

Introduction to the DECnet-ULTRIX Product
The DECnet-ULTRIX product is software that runs on an ULTRIX system. With
DECnet-ULTRIX software, an ULTRIX system can act as an end node on a
DECnet network. The DECnet-ULTRIX product is an end-node implementation
of Digital Network Architecture (DNA) Phase IV.
You can connect your DECnet-ULTRIX system to a DECnet network either
through Digital Data Communications Message Protocol (DDCMP) point-topoint line or a DECnet Ethernet cable. A DECnet-ULTRIX node can access
all other Phase III and Phase IV Decnet nodes on its network through direct
communication with a Phase IV routing node. The routing node for a DECnetULTRIX system is either the adjacent node on its DDCMP point-to-point line or
one of the nodes on the same Ethernet.
DECnet-ULTRIX software offers numerous features and capabilities:

•

User commands that support standard ULTRIX. conventions, including
support of regular expressions, wildcards, and metacharacters. DECnetULTRIX software offers remote login to remote DECnet nodes; mail exchange;
and file access and transfer between systems. The DECnet-ULTRIX user
commands and utilities are documented in this manual.

•

Software that supports the DECnet-Internet Gateway, which offers
bidirectional gateway functions between DECnet and Internet systems,
including file transfer, remote log-in, and mail.
For example, an VMS user on a DECnet node and a UNIX user on an
Internet node can display, copy, and delete each other's files; exchange
mail; and log in to each other's systems. (The Gateway offers VMS users
access to the powerful resources of the ULTRIX environment.) For more
information about the DECnet-Internet Gateway, see the DECnet-ULTRIX.
DECnet-Internet Gateway Use manual.

•

A programming interface that lets you write cooperating programs to
exchange data over a DECnet network. For more information about
DECnet-ULTRIX programming, see the DECnet-ULTRIX Programming
manual.

•

Network management features that let you configure a DECnet-ULTRIX
node, test network performance, monitor network activity, and manage
network components. For more information about network management, see
the DECnet-ULTRIX. Network Management manual and the DECnet-ULTRIX
NCP Command Reference.

The following sections describe these features and capabilities.

Introduction to the DECnet-ULTRIX Product

1-1

1.1 DECnet-ULTRIX User Commands and Utilities
Table 1-1 shows the tasks DECnet-ULTRIX users can perfonn and describes the
commands associated with those tasks.

Table 1-1: Overview of DECnet-ULTRIX User Commands and Utilities
Task

Command

Description

Remote login

dlogin

The dlogln command lets you log on to remote DECnet nodes so that you can access the
resources of those systems. DECnet-ULTRIX
software also lets remote DECnet users log on to
your node. For more information, see Chapter 2
or 6.

Mail exchange

mall

The ULTRIX mail utility lets you exchange
messages with other DEC net users. For more
information, see Chapter 3 and The Little Gray
Book: An ULTRIX Primer.

Directory listing

dis

The dis command lets you examine the contents
of remote directories. DECnet-ULTRIX software
also lets remote DECnet users display the contents of your directories. For more information,
see Chapter 5 or 6.

File display

dcat

The dcat command displays the contents of one
or more remote DECnet files. DECnet-ULTRIX
software also lets remote DECnet users display
the files on your system. For more information,
see Chapter 5 or 6.

File transfer

dcp

The dcp command lets you copy files to and from
remote DECnet systems. Remote DECnet users
can initiate copy requests to your node. For more
information, see Chapter 5 or 6.

File deletion

drm

The drm command lets you delete files from
remote directories. Remote DECnet users can
delete files from your local directories. For more
information, see Chapter 5 or 6.

1.2 DECnet-lnternet Gateway Features
The DECnet-Internet Gateway offers the following features:
Telnet

You can use Telnet commands through the Gateway.
Telnet is the standard Internet application protocol
for remote login. Using Telnet through the Gateway,
Internet users can log on to remote DECnet nodes.

File Transfer Protocol

You can use File Transfer Protocol (ftp) through the
Gateway. ftp is the primary Internet standard for file
transfer. Using ftp through the Gateway, Internet
users can access and manipulate files and directories
on remote DECnet nodes.

c
1-2

Introduction to the DECnet-UlTRIX Product

Mail systems

You can use VMS, ULTRIX, and UNIX mail systems
through the Gateway. Specify recipients according
to the addressing syntax described in the DECnetULTRIX DECnet-lnternet Gateway Use manual.

Common DECnet commands

You can use various common DEC net commands
through the Gateway. See Chapter 3 for sample
DECnet-VAX commands.

1.3 DECnet-ULTRIX Programming Interface
The DECnet-ULTRIX programming interface offers the following features:

Client-server communication

Sometimes called task-to-task communication,
client-server communication lets DECnetULTRIX applications communicate with
remote Phase III and Phase IV DECnet applications through a socket-level programming
interface.

DECnet and TCPIIP coexistence

DECnet protocols and Transmission Control
ProtocollInternet Protocol (TCPIIP) coexist and
share system resources, including Ethernet
and DDCMP hardware. You can easily modify
most TCPIIP programs to use DECnet protocols, or DEC net programs to use TCP/IP
protocols. You can use DECnet and TCP/IP
simultaneously on an Ethernet, and you
can alternate between the two protocols on
DDCMP point-to-point lines.

File access

Programs on any other DECnet Phase III or
Phase IV system can access DECnet-ULTRIX.
files and directories for sequential reading,
writing, or deletion.

1.4 DECnet-ULTRIX Network Management Features
The DECnet-ULTRIX network management software offers the following
features:
Node configuration

You can configure your DECnet-ULTRIX node to
ensure that it runs smoothly on the network.

Network performance testing

You can test your DECnet-ULTRIX. node's performance on the network.

Network Control Program (ncp)

You can manage the components of your network
and test network performance. You can also display
information on the condition, characteristics, and
performance of network components.

1.5 Similarities Between DECnet-ULTRIX and ULTRIX
Both new and experienced ULTRIX users can easily become familiar with the
DECnet-ULTRIX user environment because:

•

DECnet-ULTRIX commands support standard ULTRIX conventions,
including the use of regular expressions, wildcards, and metacharacters.

Introduction to the DECnet-ULTRIX Product 1-3

•

You can pipe or redirect the DECnet-ULTRIX commands' input or output
according to standard ULTRIX conventions.

•

The DECnet-ULTRIX mail system utilizes the ULTRIX mail interface,
requiring ULTRIX users to learn only a new syntax for creating mail
recipients' addresses.

•

DECnet-ULTRIX provides on-line manual pages (also called man pages)
that follow standard ULTRIX man page conventions. The DECnet-ULTRIX
manual pages, however, use a "dn" page identifier to distinguish them from
ULTRIX manual pages. For example:
To see the ULTRIX base system manual page for the write command, type:
% man

write

To see the ULTRIX base system manual page for the write system call, type:
% man

2 write

To see the DECnet-ULTRIX manual page for the write system call, type:
% man

2dn write

The following section provides more information about on-line manual pages.

1.6 Displaying On-Line Manual Pages
On-line manual pages are pages from reference manuals that you can display
on your screen. See the on-line manual pages for detailed descriptions of all the
DECnet-ULTRIX commands. (Note that the DECnet-ULTRIX manual pages also
appear in the DECnet-ULTRIX Command Summary (Chapter 6) of this manual.
To display an on-line manual page for a specific command, enter man and the
command name. You can even display a reference page describing the man
command itself. Enter:
% man

man

The system displays:
man(l)
NAME

man - displays manual pages on-line

SYNTAX
man -k keyword ...
man -f page title ..•
man [-] [-tT [-s] [1 ... 8] page_title ...
DESCRIPTION
The man command is a program th3t provides on-line displays
of the reference pages. Using options, you can direct the
man command to display one line summaries of reference pages
which contain a specific keyword, or you can use this command to display one line summaries of specific reference
pages.
OPTIONS
-k

display one line summaries of each
reference page that contains the specified keyword or keywords.

--More-- (27%)

1-4

Introduction to the DECnet-ULTRIX Product

The -More- symbol indicates that there is more information available. Press the
space bar or ~ to see more, or type q (without pressing ~ to quit. The (270/0)
symbol indicates that 27% of the information available on the man command is
displayed. The man(1) symbol at the top of the display is the page title.

NOTE

To use the man command, you must have the ULTRIX. manual pages
installed on your local system.

I.,

"I'

o
Introduction to the DECnet-ULTRIX Product 1-5

C··'·'

Chapter 2

Logging On to a Remote DECnet Node
Using the dlogln command, you can log on to a remote DECnet node and use
programs running on that system. The remote DECnet node can be another
DECnetr-ULTRIX system or a different operating system running DECnet, such
as a VMS system. (In this chapter, your target node is referred to as a remote
node. Your target node, however, could just as easily be your local node.)
This chapter describes how you can use dlogln to establish and control a login
session with a remote DECnet node. This chapter tells you how to:

•
•
•
•
•
•
•
•

Log on to a remote DECnet node
Log off a remote DECnet node
Enter local command mode
Display a list ofdlogln commands
Suspend the dlogin session
Record, or log, the dlogin session
Select a new escape character
Use the escape character without entering local command mode

Be sure you understand how to use dlogln before you log on to a remote DECnet
node. See the next section.

2.1

Understanding dlogin
This section describes the dlogln session you create when you log on to a remote
DECnet node.
Your local node is your local DECnet-ULTRIX system. When you log on to this
node, you start a local login session. During this local login session, you can
use the dlogin command to log on to a remote DECnet node. A remote DECnet
node is any node in the network that is running DECnet software. When you log
on to a remote node, you start a remote login session. That session is called the
dlogin session because you use the DECnet login command, dlogln, to initiate it.

During the dlog In session, you can run programs and access resources available
on the remote system, according to whatever privileges the remote system grants
you. You can also interrupt your dlogin session and execute commands on your
local node. Th do this, you use the dlogln escape character. The escape character
can be any keyboard character; the default escape character is the tilde (-).

Logging On to a Remote DECnet Node

2-1

When you type the escape character and press ~ the escape character is not
echoed to your screen or even read by the remote node. Instead, the local node,
which controls your dlogin session, reads the escape character and interprets it
as your signal to interrupt your activities on the remote node.
When you interrupt your dlogln session, you enter local command mode. Local
command mode is simply an interlace to your local node. The dlogln session
is still active while you are in local command mode. Local command mode is
characterized on screen by the local command> prompt.

At the local command> prompt, you can issue any ULTRIX or DECnet-ULTRIX
command you want to execute on your local node. You can also issue the
commands described in this chapter that control your dlogin session (for example,
the commands that suspend your dlogin session or open a new log file).
The following sections show you how to begin, end, and control your dlogin
session.

2.2 Logging On to a Remote DECnet Node
To log on to a remote DECnet node from your DECnet-ULTRIX system, type

the dlogin command followed by the remote DECnet node name. The remote
node prompts you for the login information it requires. Once you are logged on
to the node, you can issue commands to that system. In the following example,
user Irene logs on to the remote VMS node BACON and issues the VMS SHOW
USERS command:
% dlogin

Username:
Password:

bacon

IRENE ~
GOODNIGHT

(not echoed)

Welcome to VAX/VMS V5.2 on node BACON
$ SHOW USERS ~

2.3 Logging Off a Remote Node
To log off the remote DECnet node, simply type the remote node's logout
command. Logout commands vary; for example, the command is logout on
DECnet-VAX and bye on DECnet-RSX. If you do not know the logout command
for the remote operating system you are using, see that system's documentation.
In the following example, user Irene is shown logging off a DECnet-VAX node:
$ logout ~

IRENE
logged out at
6-JAN-1990
dlogin -- session terminated

09:46:29.97

Remember, when you log off the remote node, you end the dlogin session.
To end a dlogin session before you have logged on to the remote node, type

the escape character (the tilde (-) is the default) and press ~'. At the local
command> prompt, press ICTRL-O I or type exit and press ~.
In this example, user Frank ends the dlog in session because he cannot remember
the user name and password that have been assigned to him on the remote node
BACON:

2-2

Logging On to a Remote DECnet Node

% dlogin

C'"

bacon

Username: FRANK ~
Password: ORANGES ~ (not echoed)
User authorization failure
Username: - ~ (not echoed)
? for HELP in local command mode
local command> exit ~

dlogin -- session terminated
%

2.4 Entering Local Command Mode
Using the dlogin escape character, you can interrupt your login session on the
remote node and enter local command mode.

At the local command> prompt, you can execute any ULTRIX or DECnetULTRIX command on your local node. You can also perform the following tasks,
as described in this chapter:
•

Display a list of dlogin commands

•

Suspend the dlogln session

•

Record the dlogin session

To enter the local command mode, type the escape character followed by.B§TI at
the remote system's prompt. (The tilde (.... ) is the default escape character.) The
screen displays the local command> prompt. For example:

$ '" ~

(not echoed)

? for HELP in local command mode
local command>

To return control to your dlogln session on the remote node, press ~ at the local
command> prompt, as follows:
local command> ~
$

You may have to press ~ twice for the system prompt to appear.

2.5 Displaying a List of dlogin Commands
To display helpful information about the commands that control your dlogln
session, type a question mark (?) at the local command> prompt. For example:

local command> ?
local command> ?
local command> >filename
local command> »filename

Displays this menu.
Logs session to specified file.
Logs session, appending it to specified file.

local command> >
local command> suspend
local command> exit

Closes the open log file.
Suspends dlogin session.
Exits dlogin session.

local command> <CTRL-D>
local command> cmd
local command>

Exits dlogin session.
Invokes shell to execute a command.
(Blank line) - Resumes dlogin session.

[No log file active]

Logging On to a Remote DECnet Node

2-3

NOTE

In this display, cmd represents any ULTRIX command you can enter at
the local command> prompt.

2.6 Suspending the dlogin Session
If you want to interrupt your dlogin session and return control (temporarily)
to your local node, you can suspend your dlogln session. A suspended dlogin
session is not active. As a result, the screen displays your local node's prompt,
and you can execute commands at your local node.

To suspend a session, type the escape character followed by ~ at the remote
system's prompt. When the local command> prompt appears, type the suspend
command followed by~. For example:
$ '" ~

(not echoed)

? for HELP in local command mode
local command> suspend ~
Stopped
%

At your local system's prompt, you can execute any commands or procedures that
you usually execute on your local system.
When you are ready to resume the dlogin session, you simply issue a fg command
to bring the session to the foreground and press ~ at the local command>
prompt. The following example shows a suspended session on node BACON being
resumed:
% fg ~
dlogin bacon
local command> ~
$

2.7 Recording the dlogin Session
If you want to maintain a record of a dlogin session, you can open a log file.
The log file contains both your input and the system's responses. The dlogin
command allows you to have the session logged to a new log file or appended
to an existing log file. The dlogin command also allows you to close the log file
during the session.

2.7.1

Creating a Log File
You can open a new log file using either of the following methods:

•

When logging on to the remote DECnet node: use the ·1 option on the
dlogln command line and specify the name of the log file to which you want
the session logged. For example, the following command line begins a dlog in
session on nodb BACON and opens the file logfile3:
% dlogin bacon -1 logfile3

2-4

Logging On to a Remote DECnet Node

•

During a session on the remote node: enter local command mode with
the escape character and, at the local command> prompt, issue the >fi,lename
command, where filename specifies the name of a log file. For example, the
following command opens the file logfile3:
$ '"

(not echoed)

? for HELP in local command mode
local command> >logfile3 ~
local command> ~

If you specify an existing log file when you use either of the two preceding
commands, the system replaces the contents of that file with the new log file
information.
If you begin your session using the -I option to open a log file and later, during
the session, you open a second log file with the >filenamecommand, the first log
file is automatically closed.

2.7.2

Adding New Log Information to a Log File
You can add, or append, new log information to an existing log file. Enter the
local command mode and issue the »filename command, where filename specifies
the name of the existing log file. For example, the following command appends a
record of the current session to the file logfile_1990:
$ '"

(not echoed)

? for HELP in local command mode
local command> »logfile 1990 ~
local command> ~
-

()
2.7.3

Closing a Log File
Log files are closed automatically when you log off the remote node and end
the dlogin session. '1b close a log file during a dlogin session, enter the local
command mode and issue the> command. For example:
$ '"

(not echoed)

? for HELP in local command mode
local command> > ~
local command> ~

2.8 Selecting a New dlogin Escape character
When you start a dlogin session, you can select a new escape character for that
session. The character you select is the escape character only for the length of
that dlogln session. '1b select a different escape character, use the -e option on
the dlogin command line. For example, the following command starts a dlogln
session and sets the escape character to the circumflex (") character:
% dlogin

bacon -e" ~

o
Logging On to a Remote DECnet Node

2-5

2.9 Using the Escape Character Without Entering Local Command
Mode
You might want to use the escape character as part of a mail message or a
command line without signaling the dlog In session to enter local command mode.

Type the escape character once, followed by any character (even the escape
character) except~. The escape character appears on your screen only after you
have typed another character. For example:
% dcp -r kimono:: .... uucp

•~

or
%

cd........ I!!gj

(one .... is echoed)

c
2-6 Logging On to a Remote DECnet Node

Chapter 3

Sending Mail to Users on Remote DECnet Nodes
You can use the ULTRIX. mail command to send messages to users on remote
DECnet nodes. You use the recipient's DECnet mail address as the destination
for the message. This chapter defines the DECnet mail address and shows
sample mail messages.
For information on the conventions used by ULTRIX. mall, see The Little Gray
Book: An ULTRIX Primer.

3.1 The DECnet Mail Address

The DECnet mail address identifies the user who will receive the mail you are
sending. The DECnet mail address consists of the user's DECnet node name, a
double colon (::), and the user's DECnet user name. For example, the DECnet
mail address for user Jim on node DAVIS is
davis:: jim

You can also follow the popular Internet mail addressing syntax to identify mail
recipients. Internet syntax is as follows:
username@node.dnet

where
usemame

is the name of the mail recipient.

node

is the name of the recipient's node.

.dnet

is the Internet pseudodomain name.

For example, the Internet mail address for user Markle on node rrvncE is
markie@twice.dnet

The Internet addressing syntax is provided merely as a convenient interface for
Internet users. DECnet-ULTRIX. actually converts this Internet address to the
DECnet syntax before sending the mail out.

3.2 Sending Mail to a Remote DECnet User
To send mail to a user on a remote DECnet node, type the DECnet-ULTRIX mail
command and the user's DECnet (or Internet format) mail address. For example:
% mail davis:: jim ~

o
Sending Mail to Users on Remote DECnet Nodes 3-1

3.2.1

Mailing a New Message
In this example, user Helen on a DECnet-ULTRIX node sends mail to user Jim
on node DAVIS.
% mail davis:: jim ~
Subject: New Position ~
~
Dear Jim, ~
~
You've been in Davis, California, for three years now. ~
If you are open to moving to Atlanta, we would like to ~
consider you for a position here. Please let me know ~
by next week how you feel about this. ~
~
Sincerely, ~

Helen

ICTRUO I
Cc: helen

3.2.2

Mailing a File to a Remote DECnet User
In this example, user Jim on node DAVIS sends the existing file resume to user
Helen on remote DECnet-ULTRIX node ATLANT. Jim does not send a copy of the
message to anyone.
% mail atlant:: helen ~
Subject: helen, here is my updated resume
"'r resume ~
"resume" 23/1204. ~

ICTRUO I
Cc: ~
%

3.2.3 Special Considerations
Be aware that a VMS node will not accept a message from ULTRIX if the "TO:"
field of the message exceeds 512 characters. 1b reduce the number of characters
in this field, use a sendmall alias.
For more details about setting up an alias, see the description in lusr/lib/aliases.

3-2

Sending Mail to Users on Remote DECnet Nodes

c
Chapter 4

Specifying Files on Remote DECnet Nodes
Before you can view or work with remote files and directories, you must be able
to specify those files and directories. This chapter explains how to specify remote
files and directories using the following information:

•

File specification formats for all the operating systems that run DECnet

•

Wildcard characters for use in file specifications

•

Access-control information required to access files on a remote node

•

Short cuts for specifying the full access-control string in the file specification

The examples in this chapter illustrate three DECnet--ULTRIX commands, dcat,
dcp, and dis. In these examples, dcat displays the contents of files, dcp copies
files, and dis lists the contents of directories. For more information about these
commands, see Chapters 5 and 6.

4.1

File Specification Formats
Using DECnet-ULTRIX commands, you can work with files that reside on remote
ULTRIX and non-ULTRIX DECnet nodes. The format you use to specify the
files will vary according to the type of system the file resides on.
Table 4-1 lists the file specification formats for files on ULTRIX and non-ULTRIX
DECnet nodes. For more information on these file specifications, refer to
Appendix B.

Table 4-1 : File Specifications for OECnet Nodes

DECnet System

File Specification

DECnet-VAX

node::'dev:[directorylfilename.typ;ver'

DECnet-RSX
DECnet-1AS
DECnetIE
DECnet-10
DECnet-20

node::'dev:[ufdJfilename.typ,·ver'
node::'dev:[ppnJlilename.typ'

DECnet-RT

node::'dev:filename.typ'

DECnet-DOS

node::'dev:\path \filename.typ'

DECnet-ULTRIX

node::'pathlfilename'

node: :'dev :[ufdJfilename.typ;ver'
node::'dev :[ufdJfilename.ext[p,pn ]<prot'
node::'dev:<directory>filename.typ.gen;att'

Specifying Files on Remote DEC net Nodes

4-1

In Table 4-1, all the information following the node name is enclosed in
single quotation marks (' '). The quotation marks prevent the local shell (or
command interpreter) from reading and interpreting certain special characters (or
metacharacters) which are included in the specification. Only the remote system
reads and interprets characters enclosed in quotes.

Metacharacters represent special commands or functions to the local shell. Here
are the ULTRIX. metacharacters:
Table 4-2:

ULTRIX Metacharacters

Character

Meaning

Angle brackets

Ampersand

Asterisk

Backslash
I

Bar

{)

Braces

(- "-\

Blank space

Dollar sign
Exclamation point

( )

Parentheses

Question mark

[ ]

Square brackets

Semicolon

You must do something to ensure that the metacharacters you include in file
specifications are not interpreted by the local shell. You can (as shown in the
table) choose to enclose all the information following the node name in single
quotes as a standard part of your file specification. The advantage of this choice
is that you do not have to remember which characters require special treatment.
Of course, you can also choose to treat the special characters individually by
enclosing them in single quotes or preceding each one with a backslash.
The following example shows several ways you can compose a command line that
includes metacharacters (square brackets and an asterisk):
% deat woods::'usrdsk2: [nature]trees.txt;*'

or
% deat woods::usrdsk2:\[nature\]trees.txt;\*

or
% deat woods::usrdsk2:' [nature]'trees.txt;'*'

4.2 Using Wildcard Characters
All Digital operating systems support the use of wildcard characters. You can use
them in file specifications to refer to a group of files by a general name, rather
than specifying each file individually. Table 4-3 describes the ULTRIX-specific
wildcard characters.

4-2

Specifying Files on Remote DEenet Nodes

Table 4-3: Wildcard Characters
Character

Meaning

Matches one or more characters, except a slash (/).

Matches a single character, except a slash (/).

[set]

Matches one character from a set. Set members can be enumerated (for
example, [1234]) and/or contain ranges (for example, [1-4]) where the
ASCII order is used.

(tokens)

Matches a string from a list of ASCII strings, separated by commas,
which can be a portion of the filename. For example, (abc,defl* will
match any file Dame that begins with abc or def. A token can contain
other wildcard characters.

These wildcard characters are among the metacharacters listed in Table 4-2.
If you include a wildcard in a file specification, enclose it in single quotes or
precede the wildcard with a backslash (\). Otherwise, the local shell will read
and interpret the wildcard character.
This example shows two ways you can compose a command line that includes the
asterisk (*) wildcard character:
% deat faet::'dev233:*.txt'

or
% de at fact:: dev233 : \ * • txt

Table 4-3 describes how the ULTRIX system interprets wildcard characters. See
the documentation supplied with the remote system for infonnation on how that
system interprets wildcard characters.

4.3 Supplying Access-Control Information
DECnet nodes can use access-control information to screen connection requests
from remote nodes. A node screens connection requests by checking this
user-supplied information against information in local password or proxy files.

Access-control information consists of a user name, password (optional), and
account (optional). You can specify this infonnation in the following ways:
•

Enter the access-control information manually.

•

Use an alias.

•

Use a proxy account.

The target system handles access-control infonnation as follows:

•

When you supply access-control information to a remote system, the remote
system checks its password file to verify the user name and password you
gave it.

•

When you supply only a user name, the remote system checks its proxy file.
If the user name is not defined in the proxy file, the remote system checks if
the user name belongs to an account that has no password.

•

When you omit all access-control information, the remote system checks to
see if you are defined in its proxy file. If not, the system then tries to use its
default access account.

Specifying Files on Remote DECnet Nodes

4-3

NOTE

The ULTRIX system is case sensitive. Non-ULTRIX systems may pass
access-control information in uppercase. Therefore, if you plan to pass
access-control information from a non-ULTRIX to an ULTRIX system,
consult the other system's documentation to see whether or not the
system provides a case-sensitive means for passing this information.
If it does not, add an uppercase account name and password to your
ULTRIX system password file.

The following systems pass access-control information in uppercase:

4.3.1

•

DECnet-IAS

•

DECnet-RT

•

DECnet-llM V4.0 or earlier

•

DECnet-llM-PLUS V2.0 or earlier

Entering the Information Manually
You can manually specify access-control information following the node name in
the file specification. Use this format:

nodelusername/passwordlaccount::file_information
where

4.3.1.1

node

is the name or address of the DECnet node.

username

is a string of up to 39 characters identifying the userts log-in
name t which is verified by the remote node.

password

is a string of up to 39 characters needed for gaining access to
the remote system.

account

is a string of up to 39 characters that is verified by the remote
node's system account file. (The account field is ignored by
most DECnet systems.)

file_information

is the rest of the file specification as specified in Table 4-1.

User Name and Password
When you include the user name and password in the file specification, the
remote node can verify access clearance and then execute the command. This
example does not include file information because ATLANT/jones indicates the
login directory to be listed by the dis command:
% dIs

atlant/ jones/mysecret::

Directory ATLANT::/usr/users/jones/
MYFILE
bin
log
10g2

printf.notes

fi1en

4.3.1.2

User Name Only (Password Required)
If you include only the user name in the file specification, DECnet-ULTRIX
prompts you for the password. The advantage of letting the system prompt you
for the password is that your password is not displayed on your screen as you
type it, thus providing additional security.

4-4

Specifying Files on Remote DECnet Nodes

In the following example, a file in accoWlt don on node RED is copied to account
sue on node BLUE. The system prompts for passwords to both accounts:
% dcp red/don::'dsk3: [don]num.dat' blue/sue::'u$2:[sue.data]02.dat'
Password for red/don:: ? subway ~ (not echoed)
Password for blue/sue:: ? underground ~ (not echoed)

4.3.1.3

User Name Only (Password Not Required)
A password is not required along with the user name if the accoWlt does not have
a password or if a proxy account exists. However, to avoid being prompted for a
password, type a slash (/) immediately after the user name. This indicates that
you are not specifying a password, so the system does not prompt you for one.
For example:
% dls atlant/public/::

Directory ATLANT::/usr2/users/public/
README
bin
logfilel
logfile2

printf.notes

filen

If you omit the slash from the command line and the system prompts you for a
password, simply press ~ at the password prompt. For example:
% dls atlant/public:: ~
Password for ATLANT/public:: ?

Directory ATLANT::/usr2/users/public/
README
bin
logfilel
logfile2

printf.notes

filen

4.3.2

Using an Alias
As a shortcut to typing the node ID and access-control information, you can
specify an "alias" node name. An alias node name is an alphanumeric string of
one or more characters that you type in place of a node ID and any access-control
information defined for it.
For example, you could have an alias "boo" that stands for user tom with
password secrets on node BOSTON. With an alias like "boo," you do not have to
specify any access-control information on the command line.
1b use an alias in a command line, type the alias followed by the double colon (::)
and the file specification. For example:
% dcat boo::'userdsk: [tom]memo.txt;3'

You can define an alias node name for any node on your network by creating a
.nodes file in your home directory. Use the following format for your entries in
the .nodes file:
alias=node-id[llogin-name[lpassword]]

o
Specifying Files on Remote DECnet Nodes

4-5

You cannot use spaces or tab characters in any of the fields. The following
example shows sample .nodes file entries:
b=boston
w=boston/root/xyzkoroijt
boo=boston/tom/secrets

NOTE

Set up the protections on your .nodes file so that only the owner can
read the file or write to it. Do this to prevent unauthorized access to
your passwords.

4.3.3

Using Proxy Access
Using proxy access is another way to access a remote node without supplying
access-control information. Although DECnet-ULTRIX systems support proxy
access, not all DECnet systems do. Check with the manager of any non-ULTRIX
system to find out if it does.
Before you can use proxy access, the system manager for the remote node must
set up a proxy account for you. If you are going to have access to more than one
proxy account from the same node and log-in name, indicate which proxy account
is the default.
1b use your default proxy account, enter the command without any access-control
information. For example:
% deat kokomo: :farms.dat

1b use an account other than your default proxy account, append the account
login name to the node followed by a slash (/). The slash indicates that you are
not supplying a password. For example:
% deat kokomo/henry/::farms.dat

The DECnet-ULTRIX Network Management manual contains a full discussion of
proxy access and instructions for defining proxy file entries.

o
4-6

Specifying Files on Remote OeCnet Nodes

Chapter 5

Working with Files on Remote DECnet Nodes
This chapter tells you how to:

•

View directories on remote DECnet nodes

•

Display and concatenate files from remote DECnet nodes

•

Copy files to and from remote DECnet nodes

•

Convert file names during file transfer

•

Delete files on remote DECnet nodes

This chapter introduces the four DECnet-ULTRIX commands (dis, deat, dep, and
drm) that you use to work with files on remote DECnet systems. Each command
is illustrated with examples. For more information about each command, see
Chapter 6 or the on-line manual pages.

Note that you can pipe or redirect input and outputfrom the diS, deat, and dcp
commands, according to standard ULTRIX conventions.
NOTE

Each sample command line in this chapter shows access-control
information. Whenever you use the commands described in this
chapter, you have to specify access-control information, unless you meet
one of these criteria:

c~::

•

You have defined an alias for the remote node.

•

You have a proxy account on the remote node.

See Section 4.3 for a discussion about access-control information.

5.1 Viewing Remote Directories
The dis command displays the directories of a remote ULTRIX or non-ULTRIX
node. The command displays the output on your terminal screen by default.
The syntax for the dis command is as follows:
dis [options ... ] filespec ~

For a complete description of the dis command, see Chapter 6.

o
Working with Files on Remote OECnet Nodes

5-1

5.1.1

On ULTRIX Remote Nodes
The following example displays brightstar's home directory on the remote
DECnet-ULTRIX node BRAGG. The password is starlet.
The command line includes two options, -a and -I. The -a option causes all the
files in the directory to be listed, including those whose names begin with a
period. The -I option produces the long format, which includes the directory's
protection level, creation date (or last modified date, for ULTRIX systems), size,
and owner.
% dIs -a -1 bragg/brightstar/starlet:: ~

Directory WBRAGG::/usr/users/brightstar/
drwxrwxr-x
03-AUG-89 12:54:14
drwxr-xr-x
29-JUL-89 15:09:39
.cshrc
-rwxr-xr-x
05-MAY-89 19:03:53
• forward
-rw-r--r-05-MAY-89 20:12:49
. login
-rwxr-xr-x
05-MAY-89 19:03:54
-rwxr-xr-x
05-MAY-89 19:03:53
.profile
-rw-r--r-03-AUG-89 12:43:09
log
-rw-r--r-02-AUG-89 10:25:30
text

512
2048
281
16
234
138
311
442

brightstar
root
brightstar
brightstar
brightstar
brightstar
brightstar
brightstar

i---'\
\

8 files in 1 directory

5.1.2

On Non-ULTRIX Remote Nodes
The following example lists the files in directory [MANGO] on disk DRA2: on the
DECnet-VAX node DAVIS. The access-control information includes the user name
s_wolf and the password quirk.
% dIs davis/s_wolf/quirk::'dra2: [mango]'

Directory DAVIS::DRA2:[MANGO]
FRUITY. TXT;2
FRUITS.LIS;6

TROPICAL.EXE;l

5.2 Displaying and Concatenating Remote Files
The deat command displays the contents of a remote file and (by default) directs
the output to your terminal screen, and also concatenates the contents of more
than one file, following standard ULTRIX conventions.
The syntax for the deat command is as follows:
deat [options ... ] filespec ... ~

For a complete description of the deat command, see Chapter 6.

5.2.1

Displaying Remote Files on the Screen
You can use the deat command to display remote files on your screen. In the
following example, the command displays the contents of the file FRUITS.LIS in
directory [MANGO] on disk DRA2: on the remote DECnet-VAX node DAVIS. The
access-control information includes the user name s_wolf and the password quirk.
% dcat davis!s_wolf!quirk::'dra2: [mango] fruits. lis'

5-2

Working with Files on Remote DECnet Nodes

5.2.2

Concatenating Remote Files
You can also use the deat command to concatenate multiple files. In the following
example, all the files with the extension .TXT from the directory [ADOBE] on
the remote DECnet-VAX node NAVAHO are concatenated and redirected into the
local file textfiles. The access-control information includes the user name SANDY
and the password BEACH.
% deat navaho/sandy/beach::' [adobe]*.txt' > textfiles

5.3 Copying Files Between Systems
The dep command lets you copy ASCII text and binary image files to and from
remote DECnet nodes. You can copy files:

•

From local to remote node

•

From remote to local node

•

From remote to remote node

The syntax for the dep command is as follows:
dep [options ... ] input output ~

For a complete description of the dep command, see Chapter 6.

If you copy non-ULTRIX files to an ULTRIX system, you lose the non-ULTRIX
attributes associated with those files.

5.3.1

From Local to Remote Node
In the following example, the command copies the local file renee to a
new file RENEE.LIS on the remote VMS node WOODS in the directory
[PETS.RACCOON]. The access-control information includes the user name
TOMAS and the password TOM.
% dep renee woods/tomas/torn::' [pets.raccoon]renee.lis'

5.3.2

From Remote to Local Node
The following command copies the file FARM.LIS from the remote DECnetVAX node DAVIS to the file farm on the local DECnet--ULTRIX node. The

access-control information includes the user name EVELYN and the password
SECRET.
% dop ?avis/evelyn/secret::'dra2: [mango]farm.lis' farm

The following command uses the -i option to copy, in image file mode, all the data
files with the extension .DAT from the directory [HERO.HELIX.DATA] of HERO's
account on the remote VMS node ONYX to the local directory lusrlsre/data.
The access-control information includes the user name HERO and the password
MAGIC.
% dcp -i onyx/hero/magic::' [hero.helix.data]*.dat' /usr/src/data

o
Working with Files on Remote DECnet Nodes

5-3

The following command uses the -r option to copy all of the files in .... uucp on
the remote ULTRIX node KIMONO to the local directory. The access-control
information includes the user name larry and the password newcar.
% dcp -r

5.3.3

kimono/larry/newcar::~uucp

From Remote to Remote Node
The following command copies the file [DON]NUM.TXT to the file [SUE.DATA]02.TXT.
There is no access-control information in this example, because the aliases red
and blue replace the full access-control information string. (For more information
on using an alias, see Section 4.3.2.)
% dcp red::'user$55:[don]num.txt' blue::'user$22: [sue.data]02.txt'

B[IT

5.4 Converting File Names During File Transfer
Non-ULTRIX DECnet systems do not follow the ULTRIX file-naming scheme.
Therefore, when you copy a file from non-ULTRIX remote nodes to ULTRIX
nodes, you may need to convert the file name. You can do this by using the dcp
-c command option. Another way to solve this problem is to explicitly specify, on
the command line, a name for the destination file.
By default, when you transfer a file, the file name changes (uppercase characters
convert to lowercase, and the version number disappears) to match ULTRIX filenaming conventions. In the following example, the remote VMS file COSTS.TXT;3
is copied to the current directory on the local ULTRIX node. The access-control
information is user name ANNA and password TOURIST:
% dcp venice/anna/tourist::'toni: [boats]costS.txti3'

This file appears as costS.txt in the local directory.
In the following example, the file name is not automatically converted during
transfer because an output file name, costs, is specified in the command line:
% dcp venice/anna/tourist::'toni: [boats]costs.txti3' costs

/.-~ ~~-~"',

5.4.1

dcp -c Option Flags

"---/

The -c option flags control the format of the converted file output. By default,
whenever you use the dcp command, the ultrix flags are in effect: lower, nodollar,
nosemlcolon, and noversion.
The value for each flag is defined as follows:
ultrix (default)
lower
nodollar
nosemicolon
noversion

sets all-C flags (lOwer, nodollar, nosemicolon, and noversion)
converts uppercase to lowercase
converts '$' to underscore'_'
converts ';' to '.'
strips off version numbers

Each flag also has a corresponding negative value:
none
nolower

clears all -c flags
does not convert uppercase to lowercase

5-4 Working with Files on Remote DECnet Nodes

dollar
semicolon
version

does not convert '$' to underscore'_'
does not convert ';' to '.'
does not strip oft'version numbers

NOTE

The nosemicolon flag is redundant when paired with the noverslon
flag. For example, if you specify nosemicolon and noverslon when
you transfer the file COSTS.TXT;3 to your local system, the semicolon
is changed to a period, but that period is stripped off along with the
version number.

5.4.2

Setting -c Option Flags
Use the -c option flags to change the way file names are converted during file
transfer. Follow these guidelines:

•

You can replace the ultrlx default flags by adding the setenv DCP_CNAMES
command to your .login file. For example:
setenv DCP CNAMES nodollar,noversion

NOTE

Because the ULTRIX. system is case sensitive, you must enter
DCP_ CNAMES in uppercase.
•

You can add to the default (or DCP_CNAMES) flags by including -c option
flags in the command line. For example:
% dcp -cnolower woods::' [pets.racoon]renee.1isi22'

Note that the alias woods is used in this example in place of a complete
access-control information string.

5.5 Deleting Remote Files
The drm command lets you delete a single file, multiple files, or an entire
directory of files from a remote DECnet node. Of course, you need the appropriate
access rights to delete any remote files and directories you specify.
The syntax for the drm command is as follows:
drm [options ... ] filespec ~

For a complete description of the drm command, see Chapter 6.

5.5.1

A Single File
In the following example, the drm command deletes the file FARM.LIS from the
remote DECnet-VAX node DAVIS. The access-control information includes the
user name S_WOLF and the password QUIRK:
% drm davis/s_wolf/quirk::'dra2:[mango]farm.lis'

o
Working with Files on Remote OECnet Nodes

5-5

5.5.2

Multiple Files
The -r option (recursive delete) for drm deletes all of the files and subdirectories
from the directory lusr/kelth on the remote DECnet-ULTRIX node IAMOK.
The access-control information includes the user name keith and the password
partridge. For example:
% drm -r iamok/keith/partridge::/usr/keith

5.5.3

All Files of a Single File Type
The following example deletes all the files with the .RNO extension from user
WHITE'S account on the remote DECnet-VAX node ONYX. Because the files are
in the home directory, no directory is specified.
% drm onyx/white::'*.rno' ~
Password for onyx/white:: ? snow ~

(not echoed)

o
5-6

Working with Files on Remote DECnet Nodes

c
Chapter 6

DECnet-ULTRIX Command Summary

This section describes each DECnet-ULTRIX user command in detail. The
commands appear in alphabetical order and follow the graphic conventions set
down in the Preface. Table 6-1 summarizes the functions of the DECnet-ULTRIX
user commands.
Table 6-1:

DECnet-ULTRIX Command Functions

Command

Function

dcat
dcp
dlogln
dis
drm
mall

Types the contents of remote files.
Copies files between DECnet systems.
Provides a virtual terminal connection to remote DECnet nodes.
Lists the contents of a remote directory.
Deletes remote files.
Sends messages and files to remote DECnet users.

Note that the command descriptions do not discuss error messages. For a
complete list of all possible error messages and a description of each message, see
AppendixA.
The DECnet-ULTRIX command descriptions also appear on-line in dcat(1dn),
dcp(1dn), dlogln(1dn), dls(1dn), and drm(1dn). In addition, all error messages
are described in errors(1dn).

o
DECnet-ULTRIX Command Summary 6-1

dcat{1dn)

dcat(1dn)
NAME
deal - type the contents of remote files

SYNTAX
dcat [-v] filespec ...
where
-y

logs the name,s of the files being typed to standard error.

filespec

is a file specification for one or more remote files. The format for a file
specification varies with each Digital operating system.
You can specify wildcard characters. If you want the target node
instead of the local shell to interpret a string of wildcard characters,
you must enclose the string in quotation marks. See the DECnetULTRIX Use manual for file specifications and wildcard characters.

DESCRIPTION
The dcat command reads remote files and displays them on the standard output.
The command displays the files in the order that you list them.

EXAMPLES
The following example displays, to standard output, the contents of the file
FRUITS.LIS in the directory [MANGO] on disk DRA2: on the remote DECnetVAX node DAVIS. Note that no access control information is given, indicating
one of these possibilities: the file is world-readable, you defined an alias for the
remote node, or you have a proxy account on the remote node.
% dcat davis::' dra2: [mango] fruits .lis'

The following command redirects all the files with the extension .TXT from the
directory [ADOBE] on the remote DECnet-VAX node NAVAHO into the local
file lefile.txt. The string /adobe/secret is the access-control information that
NAVAHO uses to verify remote access.
% dcat navaho/adobe/secret::' [adobe]*.txt' > lefile.txt