HP SNA Data Transfer Facility for OpenVMS

HP SNA Data Transfer SPD 27.85.13
Facility for OpenVMS, Version 3.6
Data Translation
DTF for OpenVMS provides two options for data trans-
lation: no data translation at all and HP DMCS (Digi-
tal Multinational Character Set, a superset of ASCII) to
EBCDIC and vice versa.
• Users can specify that DTF for OpenVMS should per-
form no data translation during a file transfer. This
option is useful for transferring image files.
• By default, DTF for OpenVMS performs data trans-
lation from DMCS to EBCDIC and vice versa on a
record-by-record basis. This is the option normally
used to transfer text files.
By default, data translation is performed on the Open-
VMS DTF server node. To decrease the load on the
OpenVMS DTF server, the server manager can option-
ally specify that data translation (DMCS/EBCDIC) occur
on the IBM DTF system.
Data Security
Files on the IBM system are accessible only to HP users
with valid access control information. MDU provides
a standard user exit for security mechanisms through
the System Authorization Facility (SAF) interface. For
OpenVMS systems, security is maintained by using
the standard file protection mechanism provided by the
base operating system.
MDU also allows proxy information to be stored on the
IBM system using standard IBM system security pack-
ages.
For ease of use, the proxy information allows OpenVMS
users to perform file transfers without having to provide
passwords for their files located on the IBM system.
Server Management
DTF for OpenVMS provides a management utility to
manage the server account database, the file definition
database, and the DTF proxy databases on the Open-
VMS DTF server. The server account database allows
the server to support file transfer requests to many differ-
ent IBM DTF clients. The file definition database allows
users to store the IBM file specifications for frequently
accessed files. The proxy database allows the server
manager to set up mappings that allow users to enter
requests without specifying their IBM passwords. Refer
to the Data Security section for more information.
Event Logging
MDU logs events which can be used for historical in-
quiry or for accounting usage. Historical logging can
be used to characterize the use of MDU. Such informa-
tion is necessary for decisions involving operating hours,
performance tuning, and load analysis of the network
and operating system. Account logging allows users of
MDU functions to be recorded along with the resources
they consume. The granularity of the information is suf-
ficient to provide a bill-back capability. Implementation
of the accounting and billing capability is handled with
a user exit and can be customized on a per-site basis.
INSTALLATION
Installation services from HP are recommended for
a customer’s first purchase of this software product.
These services provide for installation of the software
product by an experienced software specialist.
HARDWARE REQUIREMENTS
Processors Supported
For a list of supported processors, refer to the Open-
VMS Operating System for I64, Alpha and VAX Software
Product Description (SPD 82.35.xx and 25.01.xx).
Disk Space Requirements
DTF Server for OpenVMS (Block Cluster Size = 1):
I64 Alpha VAX
Disk space required
for installation:
18200
blocks
5547 blocks 5006 blocks
Disk space required
for use (permanent):
11854
blocks
3196 blocks 1987 blocks
DTF Utilities for OpenVMS (Block Cluster Size = 1:)
I64 Alpha VAX
Disk space required
for installation:
5940 blocks 2462 blocks 2323 blocks
Disk space required
for use (permanent):
3820 blocks 1544 blocks 1101 blocks
5