Kbase 14165: How to run multiple versions of PROGRESS on Alpha or VAX VMS
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
How to run multiple versions of PROGRESS on Alpha or VAX VMS
The following STEPS below outline a practical way of having
more then ONE version of PROGRESS on a VAX/VMS Machine at
one time
1. Create a TOPLEVEL directory call PROGRESS.
DISK:[PROGRESS]
2. Create a subdirectory called VersionA.
DISK:[PROGRESS.VERSIONA]
3. Create a subdirectory called VersionB.
DISK:[PROGRESS.VERSIONB]
4. Install PROGRESS Version A
DISK:[PROGRESS.VERSIONA.DLC]
5. Install PROGRESS Version B
DISK:[PROGRESS.VERSIONB.DLC]
6. Rename all VERSION A PROGRESS executables, use this format
[PROGRESS.VERSIONA.DLC]PROGRESS_VA.exe
[PROGRESS.VERSIONA.DLC]MPROSRV_VA.exe;
7. Rename all VERSION B PROGRESS executables, use this format
[PROGRESS.VERSIONB.DLC]PROGRESS_VB.exe;
[PROGRESS.VERSIONB.DLC]MPROSRV_VB.exe;
8. Install the images in SHARED MEMORY for both VERSION A and
VERSION B.
$ INSTALL :==$INSTALL/COMMAND
$ MCR INSTALL
INSTALL> ADD diskname:[PROGRESS.VERSIONA.DLC]PROGRESS_VA.exe
-/open/share/header/priv=(syslck,sysnam,detach,world,group,
sysgbl,sysprv,cmkrnl,tmpmbx,netmbx)
INSTALL> ADD diskname:[PROGRESS.VERSIONA.DLC]MPROSRV_VA.exe;
-/open/share/header/priv=(syslck,sysnam,detach,world,group,
sysgbl,sysprv,cmkrnl,tmpmbx,netmbx)
INSTALL> ADD diskname:[PROGRESS.VERSIONA.DLC]PROGRESS_VB.exe
-/open/share/header/priv=(syslck,sysnam,detach,world,group,
sysgbl,sysprv,cmkrnl,tmpmbx,netmbx)
INSTALL> ADD diskname:[PROGRESS.VERSIONA.DLC]MPROSRV_VB.exe;
-/open/share/header/priv=(syslck,sysnam,detach,world,group,
sysgbl,sysprv,cmkrnl,tmpmbx,netmbx)
9. REMOVE the OLD or PREVIOUS PROGRESS images from SHARED MEMORY.
INSTALL> REMOVE PROEXE
INSTALL> REMOVE PROSRV
10. Create a VERSION A command PROCEDURE call VERSIONA.COM:
$ write sys$output "Setting Version A..."
$ define DLC [PROGRESS.VERSIONA.DLC]
$ define PROMSGS [PROGRESS.VERSIONA.DLC]PROMSGS.DAT
$ define PROTERM VT100 ! or desirable terminal, ie vt300?
$ define PROTERMCAP [PROGRESS.VERSIONA.DLC]PROTERM.DAT
$ define PROCFG [PROGRESS.VERSIONA.DLC]PROGRESS.CFG
$ define PROEXE [PROGRESS.VERSIONA.DLC]PROGRESS_VA.exe;
$ define PROSRV [PROGRESS.VERSIONA.DLC]MPROSRV_VA.exe;
$ set command DLC:PROGRESS.CLD
$ write sys$output "DONE Setting VERSION A.."
11. Create a VERSION B command PROCEDURE call VERSIONB.COM
$ write sys$output "Setting Version B..."
$ define DLC [PROGRESS.VERSIONB.DLC]
$ define PROMSGS [PROGRESS.VERSIONB.DLC]PROMSGS.DAT
$ define PROTERM VT100 ! or desirable terminal, ie vt300?
$ define PROTERMCAP [PROGRESS.VERSIONB.DLC]PROTERM.DAT
$ define PROCFG [PROGRESS.VERSIONB.DLC]PROGRESS.CFG
$ define PROEXE [PROGRESS.VERSIONB.DLC]PROGRESS_VB.exe;
$ define PROSRV [PROGRESS.VERSIONB.DLC]MPROSRV_VB.exe;
$ set command DLC:PROGRESS.CLD
$ write sys$output "DONE Setting VERSION B."
12. In the Login.COM of each user install the following command
on LINE 1 and remove all other PROGRESS logicals from the
USER account.
$ @DISK:[PROGRESS.VERSION?]VERSION?.COM
$ ! substitute '?' with 'A' or 'B'
13. In the Login.COM of the user starting the database, also
install the above command procedure.
Note: If you already have the PROGRESS Command Language
Definitions in DCLTABLES.exe you MUST override them
with the SET COMMAND that is documented in the above
command procedures, or you will recieve SHARED MEMORY
Mismatch problems.
Progress Software Technical Support Note # 14165