Kbase 420: How to connect PC with DECNet DOS pathworks - Configuration
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
How to connect PC with DECNet DOS pathworks - Configuration
900620-sec01
INTRODUCTION: Date Last Modified: 9/08/95
=============
This Knowledgebase entry describes how to connect to a PROGRESS
database on a VMS server machine from a P.C. client via DECnet DOS.
WHY YOU NEED TO DO THIS:
========================
If you want to connect to a PROGRESS database that resides on a
VMS server from a PC client through DECnet, you need to set up the
node addresses of the VAX host and the PC client to successfully
complete the connection. The steps necessary to do this are
described below.
This Knowledgebase entry assumes that you have DECnet (from Digital
Equipment Corporation) installed on the VMS (server) machine and
DECnet DOS installed on the DOS (client) machine. It also
references the DECnet utilities:
NCP - Network Control Program
NFT - Network File Transfer
FAL - File Access Listener
For further information on these DECnet utilities, consult your DECnet
documentation.
PROCEDURAL APPROACH:
====================
1) Find out the node address of the host and other nodes on the
DECnet.
On VMS machine, invoke NCP (Network Control Program) by typing:
Run SYS$SYSTEM:NCP
NCP>
NCP> show known nodes
The output will include the address of the local host and
any other nodes defined on the network.
2) Choose a unique node address and a node name for the DOS node.
For example, you might decide to name the DOS node "MYPC" with a
node address "1.4".
3) Define the DOS node on the host (VMS) machine by typing:
Run SYS$SYSTEM:NCP
NCP> define node 1.4 name MYPC
NCP> show known nodes
Make sure "MYPC" with node address 1.4 is defined.
4) On the DOS node, install DECnet-DOS software and set up the node,
using "MYPC" as the node name and "1.4" as the node address.
You will be prompted for the node name and address during
installation.
5) On the DOS node, after the DECnet-DOS installation, define the
VMS node using NCP by typing:
NCP> define node 1.2 name uvax2
NCP> show known nodes
In this example, the local host name "uvax2" and host address had
been previously defined through NCP on the host (VMS) machine. The
show known hosts should display the node name and address for the
host (VMS) machine and the client (DOS) machine.
6) Test to see the network connects correctly. On the DOS (client)
machine, type:
NCP> loop node uvax2
7) While connected, use the Network File Transfer (NFT) utility to
access a remote directory . Type:
NFT
NFT>set uvax2"userid password"::<device>:<directory path>
NFT>directory uvax2::
8) Use NFT to remote copy a file from the VMS to the DOS node. Type:
NFT
NFT>set uvax2"userod password"::<device>:<directory path>
NFT>copy uvax2::<remote_file> <local_file>
Where <remote_file> is the name of a file on the VMS machine and
<local_file> is the name of the file you are copying to on the
DOS machine. In this example, uvax2 is the name of th VAX machine.
Remember filenames on DOS are limited to 8 characters.
9) Use NFT to remote copy a file from the DOS to the VMS node. Type:
NFT
NFT>set uvax2"userid password"::<device>:<directory path>
NFT>copy <local_file>uvax2"userid password" <remote_file>
Where <local_file> is the name of a file on the DOS machine and
<remote_file> is the name of the file you are copying to on the
VMS machine. In this example, uvax2 is the name of the VMS
machine.
Assuming all of these tests (steps 6-9 above) are successful, then
the network is correctly set up and you're ready to start PROGRESS.
10) Start the remote PROGRESS server on the VMS (host) machine. Type:
PROGRESS/MULTI=START/SERVICE=SERVICENAME DATABASE-NAME
Here, the servicename is a logical name that you assign to the
server process. For further documentation , see the (PROGRESS
version 5) Environments Guide - specifically the Chapter on
PROGRESS on DECnet. In PROGRESS version 6, consult the System
Administration Guide I, same chapter.
11) Define the server name with the Network Control Program (NCP) on
the remote P.C.
You want to include the service names in both the Volatile
Remote Adapter Database and the Permanent Remote Adapter
Database. This is described in steps 12 through 15 below.
12) To include SERVICENAME in the Volatile Remote Adapter Database,
type:
SET REMOTE-ADAPTER-NAME SERVICENAME NODE NODENAME
SET REMOTE-ADAPTER-NAME SERVICENAME1 NODE NODENAME
SET REMOTE-ADAPTER-NAME SERVICENAME2 NODE NODENAME
SET REMOTE-ADAPTER-NAME SERVICENAME3 NODE NODENAME
SET REMOTE-ADAPTER-NAME SERVICENAME4 NODE NODENAME
The SERVICE-NAME you assign, should be the same SERVICE-NAME you
used when you started the PROGRESS server. Since you started that
server on the VMS machine, use the VMS node and address.
13) To list SERVICENAME in the Volatile Remote Adapter Database, type:
SHOW KNOWN REMOTE-ADAPTER-NAME
14) To include SERVICENAME in the Permanent Remote Adapter Database,
type:
DEFINE REMOTE-ADAPTER-NAME SERVICENAME NODE NODENAME
DEFINE REMOTE-ADAPTER-NAME SERVICENAME1 NODE NODENAME
DEFINE REMOTE-ADAPTER-NAME SERVICENAME2 NODE NODENAME
DEFINE REMOTE-ADAPTER-NAME SERVICENAME3 NODE NODENAME
DEFINE REMOTE-ADAPTER-NAME SERVICENAME4 NODE NODENAME
The SERVICE-NAME you assign, should be the same SERVICE-NAME you
used when you started the PROGRESS server. Since you started that
server on the VMS machine, use the VMS node and address.
15) To list SERVICENAME in the Permanent Remote Adapter Database, type:
SHOW KNOWN REMOTE-ADAPTER-NAME
*****Note: The SERVICENAME must be in UPPERCASE. You need a
minimum of the SERVICENAME and SERVICENAME1
defined in both databases (Volatile and Permanent)
since the broker takes up the SERVICENAME entry
and the first remote user that logs in will
take up the SERVICENAME1 entry. By default
under VMS the Broker will create 4 remote
servers thats why we create SERVICENAME1
through SERVICENAME4.
13) To start PROGRESS session on the P.C., type:
mpro database-name -S SERVICENAME
ONLINE PROCEDURES OR UTILITIES:
===============================
DECnet:
NCP - Network Control Program
NFT - Network File Transfer
FAL - File Access Listener
REFERENCES TO WRITTEN DOCUMENTATION:
====================================
Environments Guide (PROGRESS version 5) - Chapter on DECnet and DOS
System Administration Guide I (PROGRESS version 6) - Chapter on DECnet
and DOS
DECnet documentation
Progress Software Technical Support Note # 420