Kbase 14177: RMS DSV Connectivity between VAX/VMS Broker and Windows
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
RMS DSV Connectivity between VAX/VMS Broker and Windows
TITLE: RMS Gateway connectivity between VAX/VMS
Broker and Windows client.( Local RMS Schema)
DESCRIPTION:
------------
The following Steps outline a configuration for attaching
to an RMS BROKER on a VAX from a Windows Client. The RMS
files physically reside on the VAX. This example demonstrates
the connection using PATHWORKS or TCP from DOS client to
the VMS Broker. The RMS Schema physically resides on the
PC. (Local Schema)
PREREQUISITES:
-------------
PROGRESS/RMS DataServer on VMS
PROGRESS on DOS/Windows Client
UCX/TCP on VAX/VMS and TCP Product on DOS Client.
STEPS FOR CONNECTIVITY:
----------------------
1. Probuild and executable on the VAX/VMS side that
contains the following components for BROKER.
REMOTE GATEWAY BROKER
DECNET PROTOCOL or TCP
REMOTE RMS SERVER
DECNET PROTOCOL or TCP
Note: If using the protocol TCP/IP , you must have
entries in the sys$system:services.dat file
specific to the services you are starting your
broker and servers with. For example
$ type sys$system:services.dat
demosrv 2050/tcp # used for the SERVER
demobrkr 2060/tcp # use for the broker
.
.
.
2. DEFINE the following logicals in the SYSTEM table on
the VAX. This may or not be desirable. You can
alternatively define them in the login.com of the
users access PROGRESS. If so, you can remove the
"/system" qualifier from the definition.
$ define/system dlc disk:[dlc]
$ define/system rmssrv dlc:_rmssrv.exe;
$!! .exe from probuild
$ define/system probrkr dlc:_probrkr.exe;
$!! .exe from probuild
$ define/system proexe dlc:progres.exe
$ define/system promsgs dlc:promsgs.dat
$ define/system proterm vt100
$ define/system procfg dlc:progress.cfg
$ define/system prosrv dlc:_mprosrv.exe
$ define/system protermcap dlc:proterm.dat
3. Install the following images in shared memory with the
required privledges. PROGRESS requires a minimum of 1000
GBLPAGES to properly install these images. You can
determine the amount of free_gblpages on your system
with the following lexical function. If the return
integer is not equal to or greater then 1000, contact
your DEC representative regarding increasing GBLPAGES
on your VAX.
$ write sys$output f$getsym("free_gblpages")
Install the following lines in a startup command
procedure that is activated at boot time,
(ie @dlcstartup.com).
$ run sys$system:install
dlc:_rmssrv.exe /shared/open/priv=(syslck,sysgbl,
sysnam,detach,group,,world,cmkrnl,altpri,sysprv)
dlc:_probrkr.exe /shared/open/priv=(syslck,sysgbl,
sysnam,detach,group,,world,cmkrnl,altpri,sysprv)
4. Start the RMS gateway BROKER from the directory that the
RMS files reside.
$ set command dlc:progress.cld
$ set def disk:[rmsfiles]
$ progres/gateway=start/service=service_name -
/host=hostname
etwork=protocol
Below is an example of a sys$login:login.com
$ IF F$MODE() .NES. "INTERACTIVE" THEN GOTO NOINTER:
$ NOINTER:
$ set verify
$ write sys$output "This is for NO-INTERACTIVE MODE"
$ define dlc disk:[dlc]
$ define rmssrv dlc:_rmssrv.exe;
$! NOTE:
$!////////////////////////////////////////////////////////
$!The line below is a logical pointer to the new executable
$!that was build with probuild. Sometimes Database
$!Administrators choose a different location for this file
$!following the probuild. It is your choice.
$!////////////////////////////////////////////////////////
$ define probrkr disk:[dlc.test]_probrkr.exe;
$!
$ define proexe dlc:progres.exe
$ define promsgs dlc:promsgs.dat
$ define proterm vt100
$ set command dlc:progress.cld
$! NOTE:
$!////////////////////////////////////////////////////////
$!If the images are not properly installed in shared memory
$!You can avoid potential privledge problems by
$!granting all privledges to this user, as long as the user
$!has the SETPRIV privledge, which is granted in the UAF
$!record or the user.
$!////////////////////////////////////////////////////////
$ SET PROCESS/PRIV=ALL
$ exit
-------------------------
LOCAL RMS Schema Section
-------------------------
Log into DOS/WINDOWS client.
Create a directory that will eventually contain the
FDL files.
(Only necessary for Local RMS Schema)
Install the appropriate REMOTE-ADAPTER's in the
Network Control Protocol. (Only for Netbios). Make
sure that your services on your PC match up with
the services on your VAX if you are using TCP/IP.
1. Generate the appropriate FDL file for each of the
RMS files on the VAX.
$ ANALYZE/RMS/SUMMARY/FDL rmsfile
2. Transfer the FDL files over to the DOS client via
FTP or other means.
3. Set your working directory to the location of the
FDL files on your DOS machine.
4. Set up the all PROGRESS enviroment variables. To
avoid entering the environment variables each time
you log in, place them in a BATCH file on your DOS
client.
DLC
PROCFG
PROEXE
PROMSGS
PROPATH
PATH
5. BUILD a PROGRESS database.
C> prodb dbname empty
6. Enter the procedure editor and connect to a local
database.
7. Enter the PROGRESS Data Dictionary.
8. Select Database Adminstration from the Tools Menu.
9. Select RMS UTILITIES from Database Menu.
10. Create RMS Schema from the RMS UTILITIES Menu.
11. Enter your Logical Database Name. (ie rmsdemo).
12. Input Connection Parameters.
-H hostname
-S service-name
-N protocol
-U username on VAX
-P password on VAX
13. Enter the physical rms database.
ie. rmsdemo
14. Press F2 to GO.
15. Enter the Physical RMS file-name specification.
For Example: pro_customer.dat
16. Enter the PROGRESS file-name:
For Example: customer.
17. Select FDL instead of Summary at the next prompt.
18. Insert the name of the FDL file:
For Example: c:\pro_cust.fdl
19. Continue performing steps 22 to 25 until all table
information has been added.
20. Press GO or <CTRL-X>
21. Exit from the PROGRESS Dictionary.
Between the PROGRESS edit bars, perform a query like
the following
for each file:
display field.
end.
IF your RMS Data Definitions reside in CDD Plus.
Steps to Retrieve remainder field definitions.
1. Go to your VAX and begin extracting CDD definitions
into the PROGRESS format by using the following
command at your DCL prompt. The qualifier "/cdddef"
is the name of the CDD Record containing field
definitions, you will need to substitute for your own.
The procedure below is an same solution used from within
the RMS UTILITIES menu from the Dictionary, ie Import
CDD Definitions, which should be tried first. If you do
not have CDD on your VAX, you are forced into manually
adding the additional table information throught the
PROGRESS dictionary on your PC client.
$ progres/util=cddtodf -
/cdddef=SYS$COMMON:[CDDPLUS]-
PROGRESS$EXAMPLES.CUST$DIR.CUSTOMER -
/dffile=customer.df - ! any name here
/profile=customer ! any name here
2. Once you have successfully completed extracting
all CDD record definitions into a progress.df file,
transfer the files from the VAX to your DOS Client
or on a DISK that is currently being exported to you
DOS or Windows Client.
3. Load all the definitions using the PROGRESS Dictionary
Load Utility.
TITLE: RMS Gateway connectivity between VAX/VMS Broker
----- and SERVER and Windows client.(REMOTE RMS Schema)
DESCRIPTION:
------------
The following Steps outline a configuration for attaching
to an RMS BROKER and SERVER on a VAX from a WINDOWS Client.
The RMS files physically reside on the VAX. This example
demonstrates the connection using PATHWORKS or TCP from DOS
client to the VMS Broker. The RMS Schema physically resides
on the VAX. (REMOTE Schema)
PREREQUISITES:
-------------
PROGRESS/RMS DataServer on VMS
PROGRESS on DOS/Windows Client
UCX/TCP on VAX/VMS and TCP Product on DOS Client.
STEPS FOR CONNECTIVITY:
----------------------
1. Probuild and executable on the VAX/VMS side that contains the
following components for BROKER.
REMOTE GATEWAY BROKER
DECNET PROTOCOL or TCP
REMOTE RMS SERVER
DECNET PROTOCOL or TCP
Note: If using the protocol TCP/IP , you must have
entries in the sys$system:services.dat file
specific to the services you are starting your
broker and servers with. For example
$ type sys$system:services.dat
demosrv 2050/tcp # used for the SERVER
demobrkr 2060/tcp # use for the broker
.
.
.
2. DEFINE the following logicals in the SYSTEM table
on the VAX. This may or not be desirable. You can
alternatively define them in the login.com of the
users access PROGRESS. If so, you can remove the
"/system" qualifier from the definition.
$ define/system dlc disk:[dlc]
$ define/system rmssrv dlc:_rmssrv.exe;
$ !! .exe from probuild
$ define/system probrkr dlc:_probrkr.exe;
$ !! .exe from probuild
$ define/system proexe dlc:progres.exe
$ define/system promsgs dlc:promsgs.dat
$ define/system proterm vt100
$ define/system procfg dlc:progress.cfg
$ define/system prosrv dlc:_mprosrv.exe
$ define/system protermcap dlc:proterm.dat
3. Install the following images in shared memory with
the required privledges. PROGRESS requires a minimum
of 1000 GBLPAGES to properly install these images.
You can determine the amount of free_gblpages on your
system with the following lexical function. If the
return integer is not equal to or greater then 1000,
contact your DEC representative regarding increasing
GBLPAGES on your VAX.
$ write sys$output f$getsym("free_gblpages")
Install the following lines in a startup command
procedure that is activated at boot time,
(ie @dlcstartup.com).
$ run sys$system:install
dlc:_rmssrv.exe /shared/open/priv=(syslck,
sysgbl,sysnam,detach,group,world,cmkrnl,altpri,sysprv)
dlc:_probrkr.exe /shared/open/priv=(syslck,
sysgbl,sysnam,detach,group,,world,cmkrnl,altpri,sysprv)
4. Create a directory and set default to it
Example: $ create/directory disk:[PROGRESS.RMS]
$ set default disk:[PROGRESS.RMS]
5. Copy all your RMS files to that directory
Example: $ copy *.dat; disk:[PROGRESS.RMS]
6. Create a PROGRESS Database from Empty
Example: $progres/create rmsholder empty
7. Enter PROGRESS and Enter the Data Dictionary
Example: $progres rmsholder
8. Select DataServer from the Tools Menu.
9. Select RMS UTILITIES from Database Menu.
10. Create RMS Schema from the RMS UTILITIES Menu.
11. Enter your Logical Database Name.
Example: rmsdemo
12. CTRL-X to GO.
13. Enter the Physical RMS file-name specification.
For Example: pro_customer.dat
14. Enter the PROGRESS file-name:
For Example: customer.
15. Continue performing steps 12 to 14 until all
table information has been added. This will only
add the index information for each file. You will
still have to manually add the remainder data
definitions. See Section on CDD Plus.
16. Exit from the PROGRESS Dictionary.
In the PROGRESS procedure editor, perform a query like
the following to verify
for each rmsfile:
display field.
end.
17. Exit from PROGRESS and get back to your VMS prompt.
18. Start the RMS gateway BROKER from the directory that the
RMS files reside after you start the Database Server.
$ set command dlc:progress.cld
$ set def disk:[rmsfiles]
$ progres/mult=start/service=service_name -
/host=hostname
etwork=protocol database
$ progres/gateway=start/service=service_name -
/host=hostname
etwork=protocol
Below is an example of a sys$login:login.com
$ IF F$MODE() .NES. "INTERACTIVE" THEN GOTO NOINTER:
$ NOINTER:
$ set verify
$ write sys$output "This is for NO-INTERACTIVE MODE"
$ define dlc disk:[dlc]
$ define rmssrv dlc:_rmssrv.exe;
$! NOTE:
$!/////////////////////////////////////////////////////////
$!The line below is a logical pointer to the new executable
$!that was build with probuild. Sometimes Database
$!Administrators choose a different location for this file
$!following the probuild. It is your choice.
$!////////////////////////////////////////////////////////
$ define probrkr disk:[dlc.test]_probrkr.exe;
$!
$ define proexe dlc:progres.exe
$ define promsgs dlc:promsgs.dat
$ define proterm vt100
$ set command dlc:progress.cld
$! NOTE:
$!/////////////////////////////////////////////////////////
$! If the images are not properly installed in shared memory
$! You can avoid potential privledge problems by
$! granting all privledges to this user, as long as the
$! user has the SETPRIV privledge, which is granted in the
$! UAF record for the user.
$!/////////////////////////////////////////////////////////
$ SET PROCESS/PRIV=ALL
$ exit
Log into DOS/WINDOWS client.
Install the appropriate REMOTE-ADAPTER's in the Network
Control Protocol. (Only for Netbios). Make sure that
your services on your PC match up with the services on
your VAX if you are using TCP/IP.
Client Steps
------------
1. Set up the all PROGRESS enviroment variables. To avoid
entering the environment variables each time you log in,
place them in a BATCH file on your DOS client.
DLC
PROCFG
PROEXE
PROMSGS
PROPATH
PATH
2. Enter the procedure editor.
3. Connect from the procedure editor to your VAX Server.
-S service-name -H hostname -N protocol dbname
4. Enter the PROGRESS Data Dictionary and connect to your
REMOTE RMS Schema. Go right down to the Section below and
enter. NOTE: USERNAME and PASSWORD are for the VMS Machine.
Other CONNECT Statements Parameters
-----------------------------------
-S service-name -H hostname -N protocol -U
USERNAME -P PASSWORD
5. Exit from the PROGRESS Dictionary.
Between the PROGRESS edit bars, perform a query
like the following
for each file:
display field.
end.
IF your RMS Data Definitions reside in CDD Plus.
-----------------------------------------------
Steps to Retrieve remainder field definitions.
1. Go to your VAX and begin extracting CDD definitions
into the PROGRESS format by using the following
command at your DCL prompt. The qualifier "/cdddef"
is the name of the CDD Record containing field
definitions, you will need to substitute for your own.
The procedure below is an same solution used from within
the RMS UTILITIES menu from the Dictionary, ie Import
CDD Definitions, which should be tried first. If you do
not have CDD on your VAX, you are forced into manually
adding the additional table information throught the
PROGRESS dictionary on your PC client.
$ progres/util=cddtodf -
/cdddef=-
SYS$COMMON:[CDDPLUS]PROGRESS$EXAMPLES.CUST$DIR.CUSTOMER -
/dffile=customer.df - ! any name here
/profile=customer ! any name here
2. Once you have successfully completed extracting
all CDD record
definitions into a progress.df file, transfer the
files from the VAX to your DOS Client or on a DISK
that is currently being exported to you DOS or Windows
Client.
3. Load all the definitions using the PROGRESS Dictionary Load Utility.
Progress Software Technical Support Note # 14177