Kbase 13982: Network Connections for VMS, UNIX, DOS with TCP, SPX, DECnet
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Network Connections for VMS, UNIX, DOS with TCP, SPX, DECnet
NETWORK CONNECTIONS NEEDED FOR PROGRESS SERVER AND CLIENTS
----------------------------------------------------------
The startup connections needed for a PROGRESS Server and
Client are dictated by the type of network being used.
These will remain consistent regardless of whether you
are connecting a DOS client to a UNIX server, or a UNIX
client to a VMS server, etc.
There are other variations that can make this task seem
more complicated, an example of this being the executable
needed. (For example, different executables may be needed
depending on the version of PROGRESS.)
SPX
---
SERVER: -N and -S
CLIENT: -N and -S
* -H is not applicable for SPX.
SPECIAL NOTES REGARDING THE NLM SERVER:
--------------------------------------
NLM V7:
NLM SERVER: _mprosrv dbname -N TLI -S xxxxx
SPX CLIENT: dbname -N SPX -S xxxxx
TCP CLIENT: dbname -N TCP -S xxxxx -H xxxxx
NLM V6.2M15 or later:
NLM SERVER: _mprotli dbname -N TLI -S xxxxx
SPX CLIENT: dbname -N SPX -S xxxxx
TCP CLIENT: dbname -N TCP -S xxxxx -H xxxxx
Prior to NLM V6.2M15: (NOTE: Customer should upgrade.)
NLM SERVER: _mprosrv dbname -N SPX -S xxxxx
SPX CLIENT: dbname -N SPX -S xxxxx
TCP CLIENT: dbname -N TCP -S xxxxx -H xxxxx
NLM SERVER: _mprotli dbname -N TLI -S xxxxx
SPX CLIENT: dbname -N SPX -S xxxxx
TCP CLIENT: dbname -N TCP -S xxxxx
* The executable for 6.2M15 and later (_mprotli) is
the only executable needed for NLM Servers. This
executable continues to support both TCP and SPX.
It will look to see if both networks are there.
If an environment is set up to include SPX only,
then the server will give some informational
warnings that it couldn't find TCP. If you are
not planning to use TCP, then you can ignore
these messages. The messages in this situation
are:
"Unable to open file <services> to read server
process name and port (1080)", and
" Unable to find server with protocol 'TCP' in
/etc/services (777)".
** -S needs to be unique for each DB server connection
and must match eactly with the -S on the server
(case-sensitive). For SPX, -S is not provided
in an /etc file and can be anything you want it
to be.
*** If -N TLI is not specified on the NLM Server for
6.2M15 or later, PROGRESS won't be stable.
Customers may complain of poor performance or
other problems/inconsistencies.
**** If customers want the client to support both TCP
and SPX, they can do so. By using Novell's ODI
(Open Datalink Interface) network drivers, you
can load multiple protocols on a single network
interface card. Most major vendors of TCP/IP
support ODI.
NETBIOS
-------
SERVER: -S xxxxx
CLIENT: -S xxxxx -H unique-name
* On NETBIOS Clients, -H is actually a NETBIOS name
table entry. Therefore, it must be unique.
** -N is not needed by the client (or server);
PROGRESS defaults to NETBIOS.
*** NETBIOS networks have no hosts, services, and
protocols files.
TCP/IP
------
SERVER: -S <servicename> -N <network>
CLIENT: -H <hostname> -S <servicename> -N <network>
* The <servicename> and <hostname> come from the
/etc/services and /etc/hosts files, respectively.
** Windows and DOS clients may run into System Error
1432 if the /etc files are not copied (FTP)
locally onto the pc. See KBASE entry "PROGRESS
System Error 1432 and using -N TCP" for more
information. This applies to both V6 and V7.
UNIX:
----
Each machine in a TCP/IP network has:
a network address (needed for hosts file)
an /etc/hosts file (should already exist)
an /etc/services file
an /etc/protocols file
The structure and usage of these files is described
in the "System Administration Guide II" (Version 6),
or the "Networks Guide" (Version 7). There is also
an excellent entry in the KBASE entitled "How to
use PROGRESS on a tcpip network" that addresses
tcp/ip in a UNIX environment.
* In Version 6.2, if -N is not specified, the default
is TCP. In Version 6.3 and later, the default is
TLI.
VAX/VMS:
-------
By default, VMS PROGRESS executables include the
DECnet protocol. For more information about
establishing a PC to VMS connection using DECnet
(Pathworks), see the KBase entry entitled, "How
to connect PC with DECnet DOS-Configuration".
If using TCP on the VAX, you must build a new
executable (using PROBUILD) that contains TCP as
a configurable element. The VMS PROGRESS
executables only support DEC's TCP/IP (also called
UCX). The Services file is located in
SYS$SYSTEM:SERVICES.DAT and hosts can be found
by using the NCP utility.
For more information on connecting to a VAX/VMS
system using TCP/IP, please see the two KBASE
entires entitled:
"Setting up TCP/IP on VAX/VMS via UCX" and
"What TCP/IP we support for VMS connection: Not
Wollongong"
NLM:
---
See the "Special Notes Regarding the NLM Server"
under the section SPX for information about TCP
clients connecting to an NLM Server.
Progress Software Technical Support Note # 13982