Steps to Create and Start an RMS Dataserver
Steps to Create and Start an RMS Dataserver
LOCAL Access - the ONLY executable that needs to be built
is the PROGRESS executable that contains RMS DATASERVER.
REMOTE Access - 3 executables must be built.
a. PROGRESS executable that contains REMOTE RMS
DATASERVER, and appropriate Network protocol.
b. REMOTE DATASERVER BROKER with the appropriate
Network protocol.
c. REMOTE RMS SERVER with the appropriate Network
protocol.
Starting Probuild:
1. Define PROLOAD logical to point to where Probuild was
installed (by default it's in the DLCLOAD directory).
DEFINE/TRANS=CONCEAL PROLOAD <device>:[DLCLOAD.]
2. Execute PROBUILD to create link script. Go to the
directory where PROBUILD.COM resides
$SET DEFAULT PROLOAD:[EUCAPP]
@PROBUILD
3. Once in PROBUILD it asks where to place the link
script. Place the link script in the current
working directory. A link file does not always
get generated unless in the [DLCLOAD.EUCAPP]
directory.
Install Link Script Into: <leave blank> or []
4. Select the appropriate PROGRESS product.
For example,
(for V6)
PROGRESS 4GL, QUERY, or RUN-TIME
(for V7)
PROGRESS CLIENT
5. Link script name - by default this is LDPRO.COM.
This can be any name.
Executable name - we suggest naming the PROGRESS
executable to something other than _progres to
avoid confusion.
Again, to avoid confusion, if building for REMOTE
Access, change the default name of LDPRO.COM as well
for each of the executables being built.
6. Select the appropriate Gateway product.
For example, if this is for LOCAL Access only select
RMS DATASERVER
For REMOTE access select REMOTE RMS DATASERVER and
the appropriate Network protocol, for example
DECNET NETWORK PROTOCOL.
7. Press <PF1> to generate the Link Script.
8. Once the Link Script is generated you can exit PROBUILD
and execute the Link Script at the $ sign
<PF4> to exit PROBUILD
$ @LDPRO (or new name chosen from step 6 above)
At this step, you could choose to move LDPRO.COM to
its ultimate destination directory, and then execute the
command procedure there.
9. Define the PROEXE logical.
$ DEFINE PROEXE <device>:[<directory>]_<new progres>.EXE
For Remote Access, 2 additional logicals need to be
defined
(for V6)
$ DEFINE RMSSRV DLC:_RMSSRV.EXE
$ DEFINE PROBRKR DLC:_PROBRKR.EXE
(for V7)
$ DEFINE RMSSRV BIN:_RMSSRV.EXE
$ DEFINE PROBRKR BIN:_PROBRKR.EXE
10. To start a Local Self-Service client
$ PROGRESS/MULTI=LOGIN <database name>
11. To start a Remote client, the RMS Dataserver Broker, and
RMS Dataserver Remote Server must be started first.
$ PROGRESS/GATEWAY=START/SERVICE=<unique service name1> -
_$ /HOST=<node name>/NETWORK=<protocol, e.g., DECNET>
$ PROGRESS/MULTI=START/SERVICE=<unique service name2> -
_$ HOST=<node name> -
_$ /NETWORK=<protocol, e.g., DECNET> <database name>
$ PROGRESS/MULTI=REMOTE/SERVICE=<unique service name2> -
_$ /HOST=<node name> -
_$ /NETWORK=<protocol, e.g., DECNET> <database name>
12. To start a remote DOS client
CONNECT -db <database name> -H <node name>
-N <protocol, e.g., DECNET> -S <unique service name2>
-Nn <unique number>
Progress Software Technical Support Note # 16007