Kbase 13133: Setting up TCP/IP on VAX/VMS via UCX
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Setting up TCP/IP on VAX/VMS via UCX
The following document outlines the necessary steps on using
Digital Equipment UCX TCP/IP product with PROGRESS VAX/VMS.
STEP 1: Building the new "TCP/IP" PROGRESS executables
----------------------------------------------
Use the PROGRESS PROBUILD utility to build the
appropriate executables that include TCP protocol.
The follow Matrix outlines the required executables that
need to be generated via PROBUILD.COM for each
respectable Product.
"PROBUILD Configurational Element Table"
FOR TCP/IP
PRODUCT ELEMENTS LOGICALS EXECUTABLE
-------------------------------------------------------------
Remote RDB Server TCP-IP RDBSRV _rdbsrv.exe
Remote Gateway Broker TCP-IP PROBRKR _probrkr.exe
-------------------------------------------------------------
Remote RMS Server TCP-IP RMSSRV _rmssrv.exe
Remote Gateway Broker TCP-IP PROBRKR _probrkr.exe
-------------------------------------------------------------
Remote ORACLE Server TCP-IP ORASRV _orasrv.exe
Remote Gateway Broker TCP-IP PROBRKR _probrkr.exe
NOTE:
The PROGRESS Server executable, _mprosrv.exe, already
contains the TCP/IP Configurational Element.
STEP 2: UCX Remote Host Internet Address and Name
-----------------------------------------
The UCX product offers a number of services as a TCP/IP
product. Each individual services depends on many items.
It is necessary that the UCX host table contains the
Machine Name, Machine Alias and Internet Address for your
Clients that wish to connect to PROGRESS in a
CLIENT/SERVER mode.
The following example demonstrates how to add a remote
machines hostname, machine alias and internet address in
the UCX host table.
UCX> SET HOST MOE /ADDRESS = 128.33.33.9 /ALIAS="MOE_3"
UCX> SHOW HOST MOE
NOTES:
The above step may not be necessary if the REMOTE client
can allready telnet or rlogin to the VAX already.
PROGRESS internally retrieves TCP/IP hostname information
with standard socket routines.
For example: gethostname(char *name,int namelen)
STEP 3 Service-Name and Port Number Retrieval
--------------------------------------
When a PROGRESS server is started using /NETWORK=TCP,
PROGRESS immediately opens the file
SYS$SYSTEM:SERVICES.DAT and parses through this file for
the service name used with the qualifier /SERVICE. Once
PROGRESS finds the service entry in the file, PROGRESS
will then map the PORT number to the service entry. From
this point on, that service name and port number are
exclusively owned by that process and can not be used for
starting any other server processes. Basically, you can
not have 2 PROGRESS servers running at the same time with
the same service name.
NOTES:
The SYS$SYSTEM:SERVICES.DAT file must be created by the
SYSTEM MANAGER of the VAX. PROGRESS does NOT create this
file for you during the installation process. This is an
flat file, which should contain the exact same entries
as the services file on the client. Do not confuse this
file with the UCX$SERVICES.DAT file. These are not the
same file, and you do not define Progress services via
the UCX utility.
If your configuration requires you to start a GATEWAY
BROKER as well, you must have an additional entry and port
number in the SYS$SYSTEM:SERVICES.DAT file.
Example:
Start a TCP/IP Database SERVER and Gateway BROKER.
$ PROGRESS/MULTI_USER=start-
/SERVICE=target-
/HOST=vax-
/NETWORK=tcp demo
$ PROGRESS/GATEWAY=start-
/SERVICE=servname-
/HOST=vax-
/NETWORK=tcp
PROGRESS opens the file SYS$SYSTEM:SERVICES.DAT and
looks for the following entries like the ones below.
target 3500/tcp # comment for demo db
target1 3501/tcp # comment for server1
target2 3502/tcp # comment for server2
target3 3503/tcp # comment for server3
target4 3504/tcp # comment for server4
servname 3510/tcp # comment for broker
The above entries should have unique port numbers that
are not already being used by your VAX. You can check
what PORT numbers are already pre-allocated with the
following UCX command. Do not use any of the PORT
numbers defined in this table.
UCX> show services
Finally, confirm that your entry for the service in
SYS$SYSTEM:SERVICES.DAT exactly matches what you have on
your client machine before attempting to remotely connect
via TCP to a PROGRESS server process.
For example for a UNIX Client, look at the file
/etc/services
For a PC client, look at the services file which will be
located in the directory which your TCP package indicates,
such as windows\services for Windows TCP.
Refer to the System Administration I Guide for Progress Version 6
the Networks Guide for Progress Version 7.
Progress Software Technical Support Note # 13133