Kbase 10564: Multiple versions of Progress on VMS
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Multiple versions of Progress on VMS
920623-ctp01
MULTIPLE VERSIONS OF PROGRESS ON VMS
To set up running multiple versions of Progress on VMS
review the following steps:
1. You must install each version in a separate directory.
When the installation procedure asks for a directory,
type in a directory other than the one in the directory
where the current product is installed.
2. Create a PRODUCTION environment. This is most likely
the current Progress version on the system. The
_mprosrv.exe and _progres.exe for this version should
be installed in memory using the VMS Install utility.
The PROGRESS.CLD for this version is installed in
the DCLTABLES.EXE. The other logicals that are
to be set to point to this environment are:
DLC, PROEXE, PROSRV, PROPATH, PROTERM, PROMSGS,
PROTERMCAP, PROCFG. The SET COMMAND DLC:PROGRESS.CLD
in the users' LOGIN.COM must point to the DLC in this
area.
3. Create a TEST environment. This is the new version of
Progress on your system. The images CANNOT be installed
in memory, as they are the same names as the production
images. INSTEAD, the users of this test environment must
run with the privileges to execute the images, OR the
images must have the ACLs to execute. The LOGIN.COM
of the users must be set to point to the test area.
The logicals include:
DLC, PROEXE, PROSRV, PROPATH, PROTERM, PROMSGS,
PROTERMCAP, PROCFG. The SET COMMAND DLC:PROGRESS.CLD
MUST be included in the LOGIN.COM. DLC will point
to the TEST environment, and the PROGRESS.CLD will
be loaded in the process table for that user.
The drawback is that the TEST ENVIRONMENT users must have
privileges.
Progress Software Technical Support Note # 10564