Consultor Eletrônico

Running Probuild on VMS with Progress 7 or 8

PROBLEM:
When you try to run probuild on OpenVMS, running the buildenv.com command file will not set up the environment for you, meaning that when you run "@probuild" it fails.


SOLUTION:
The BUILDENV.COM command file is only meant as an example and WILL
NOT set up your environment without much modification.

To be able to run probuild successfully you will need to do the following:

1. Make sure your logicals are defined correctly

Define PROLOAD:
This logical must be defined as a ROOT, CONCEALED logical. A root logical is one way VMS creates a a "root directory" of sorts. This allows us to access files within subdirectories from a single point rather than an unrelated collection of directories. This is somewhat like a "/" on unix or "C:\" on dos. You can refer to the files with the logical name followed by a subdirectory, ie: PROLOAD:[4GL]<file>, hiding the preceding path.

$ DEFINE/SYSTEM/TRANSLATION=CONCEALED PROLOAD <disk>:[DLC.PROBUILD.]
^
Make sure the "." is here to specify the root -------+

Redefine PROPATH:

$ DEFINE PROPATH ",PROLOAD:[EUCAPP]EUC.PL"

Plus any other directories you want to add.

2. Move to the correct location and run probuild

$ set def <disk>:[dlc.probuild.eucapp]
$ @probuild

This will take you into a small application.

Screen 1: Just hit return twice.

Screen 2: Select the product you want to build - ie. client or server

Screen 3: return through the first line (or change the name if you wish), and change the executable name appropriately. Continue

Screen 4: Select all the configurable elements you want to have built into the executable, ie "DECNET NETWORK PROTOCOL", "TCP-IP NETWORK PROTOCOL", "REMOTE RMS DATASERVER" - do this by using the space bar to select/deselect. Continue.

Screen 5: You will see the following at the bottom of the screen.
Analyzing Progress EUC Database for <the product you selected in screen 2> ...

Then you will see:
Generating load script for <the product you selected in screen 2> ...
Press space bar to continue.

Load script generation complete.
F4 twice to exit the application.

You will now have generated a command file based on what was the default, or what you renamed in screen 3. You need to run this to generate the executable:

$ @ldpro (this is the default name for a client executable)

This assuming it links correctly, will give you an executable file based on what you chose in Screen 3 ie. progres.exe.

Copy the executable into your bin directory. (You should have a logical BIN defined)

You now need to do a replace in install - this example assumes you have built a new client executable with the default name:

$ set def sys$system
$ install
INSTALL> replace bin:progres.exe /open/share/priv=(sysprv,syslck,group,world,sysnam,setprv,detach,sysgbl)
INSTALL> exit
$

Please check that you don't have PROEXE set in the system table pointing to another file. If so, please redefine it and make sure it picks up the executable you have just built.

As new clients login, they will start to pick up this executable. If you rebuilt the server executable, you will need to stop and restart the broker after installing it in install.

You can now deassign your modified propath, or redefine it as needed.


If you are in doubt of their logical settings have them fax you a
screen snapshot of the "show log PRO*" and "show log DLC*" commands.
Or have them do a "show log /out=list.txt PRO*" and have them fax you
the list.txt file.

Getting their login.com is always usefull too.

SUGESTED REFERENCE:
VAX/VMS DCL CONCEPTS GUIDE - available from Digital Equipment Corp.

Progress Software Technical Support Note # 13791