HP DECnet-Plus for OpenVMS Alpha and OpenVMS I64, Version 8.3

HP DECnet-Plus for OpenVMS Alpha and OpenVMS I64, Version 8.3 SPD 50.45.19
Applications
Transport Options for Applications
You can run applications written to the DECnet upper
layers over NSP or TCP/IP transports using RFC 1859.
This includes the network applications that are licensed
with DECnet-Plus as well as user-written applications
that adhere to the documented DECnet programming
interfaces.
You can run applications written to the OSI upper layers
over OSI or TCP/IP transports using RFC 1006.
Existing DECnet and OSI applications require no mod-
ification to run over TCP/IP using RFC 1859 and RFC
1006.
Remote File Transfer
HP DECnet-Plus for OpenVMS supports two upper layer
protocols for remote file transfer: the OSI protocol’s
File Transfer, Access, and Management (FTAM) and the
DECnet Data Access Protocol (DAP).
FTAM
FTAM supports file transfer, access, and management
between a DECnet-Plus for OpenVMS system and other
systems with software adhering to ISO 8571. In addi-
tion, FTAM is conformant with NIST Phase II and Phase
III agreements and is certified as being conformant to
the released specifications of U.S. GOSIP, U.K. GOSIP,
and ENV41204.
In addition, FTAM:
• Provides users the ability to create, delete, rename,
view, and copy files using DCL commands.
• Is implemented as an Application Service Element
(ASE) of the OSI Application layer.
• Acts as the initiator or as the responder in a connec-
tion.
• Accesses and transfers files with both binary and
character data. It supports FTAM-1, FTAM-2, FTAM-
3, and NBS-9 document types.
HP DECnet-Plus for OpenVMS also supports gateway
services between FTAM and DAP.
A full description of the FTAM services in DECnet-Plus
for OpenVMS is provided in Appendix A of this docu-
ment.
DAP
The DECnet Data Access Protocol (DAP) supports task-
to-task communications, file and record access, and
proxy access.
Task-to-Task Communications: For most applica-
tions, you can use task-to-task communications in a
transparent manner where the remote task is treated
as a full-duplex, record-oriented device. Transparent
operation is provided with the following interfaces: sys-
tem service calls, RMS calls (OPEN, GET, PUT, and
CLOSE), and high-level language I/O statements (which
are mapped to RMS calls). A nontransparent mode of
task-to-task communications is offered by means of the
system service interface that extends the capabilities
provided by the transparent mode. These capabilities
include support for interrupt messages and multiple in-
bound connect requests.
Using HP DECnet-Plus for OpenVMS, an OpenVMS
program written in a native mode programming lan-
guage can exchange messages with other user pro-
grams.
File Access: File access is supported to and from
remote DECnet-Plus for OpenVMS systems, transpar-
ent to native mode high-level language programs using
RMS. User programs can sequentially read, create, and
delete files on a remote node.
Record Access: User programs can perform record
level operations such as GET, PUT, UPDATE, DELETE,
FIND, and REWIND to access and modify files resid-
ing on a remote OpenVMS node. In addition to se-
quential access to a file, several other access meth-
ods are supported through RMS using DECnet-Plus for
OpenVMS. These methods include random access by
relative record number, random access by key value,
random access by record file address (RFA), and block
I/O access by virtual block number.
Proxy Access: Remote users can have access to up
to 15 proxy accounts on a specific remote system. One
proxy account should be designated as the default proxy
account on the remote system.
Command Language File Management
You can use most OpenVMS DIGITAL Command
Language (DCL) commands to perform remote file
operations. These commands include: ANALYZE,
APPEND, BACKUP, CLOSE, CONVERT, COPY, CRE-
ATE, DELETE, DIFFERENCES, DIRECTORY, DUMP,
OPEN, PRINT, PURGE, READ, SEARCH, SUBMIT,
TYPE, and WRITE. The operation of these com-
mands is transparent except for commands that in-
voke processing on a specific system (for example,
SUBMIT/REMOTE and PRINT/REMOTE). Only a node
name added to a file specification is required to invoke
the network capabilities using one of these commands.
Using the COPY command, a user can transfer sequen-
tial, relative, and indexed-sequential (ISAM) files be-
tween DECnet-Plus for OpenVMS nodes that support
compatible file structures and record formats. Users
4