[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference pamsrc::decmessageq

Title:	NAS Message Queuing Bus
Notice:	KITS/DOC, see 4.*; Entering QARs, see 9.1; Register in 10
Moderator:	PAMSRC::MARCUSEN

Created:	Wed Feb 27 1991
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	2898
Total number of notes:	12363

2753.0. "mismatch possible error on Digital Unix" by CARDHU::BOURAKOFF (MCS/STN-IM Switzerland 761-4820) Fri Jan 31 1997 08:05

    Using Digital Unix is that possible to use 2 differents versions of DMQ
    like DMQ V3.2 and DMQ V3.2-A on the same machine (both versions of
    the product are installed)
    
    Pierre

T.R Title User Personal
Name Date Lines

2753.1 XHOST::SJZ Rocking the Messaging Desktop ! Fri Jan 31 1997 12:52 23

T.R	Title	User	Personal Name	Date	Lines
2753.1		XHOST::SJZ	Rocking the Messaging Desktop !	`Fri Jan 31 1997 12:52`	23
	It is possible. However, whichever version you install second will overwrite the symbolic links in /usr/bin, /usr/lib, /usr/include and so forth. That means you have to extra care- ful when running applications. That is you should have your path setup to point through the appropriate bin directories. For instance set path = (/usr/kits/DMA32A/bin $path) should guarantee that you are running V3.2A. this would have to be done in your shell login script (.profile, .login, .cshrc or equivalent). similarly when building applications you need to be careful when compiling against the include files and linking against the libraries. lastly, you need to worry about running applications. applications need to be linked against the run- ning version. if you have a single application that you want to run against the two different versions you would need two sepa- rately linked images of that application and make sure you run the correct one. In short it is more trouble than it is worth. _sjz.

    
    It is possible.  However,  whichever version you install second
    will  overwrite  the  symbolic  links  in  /usr/bin,   /usr/lib,
    /usr/include and so forth.  That means you have to  extra  care-
    ful when running applications. That is  you  should  have  your
    path setup to point through the appropriate bin directories.
    For instance
    
    set path = (/usr/kits/DMA32A/bin $path)
    
    should guarantee that you are running V3.2A. this would have to
    be done in your shell login script (.profile, .login, .cshrc or
    equivalent).   similarly when building applications you need to
    be careful when compiling against the include files and linking
    against the libraries. lastly,  you need to worry about running
    applications.   applications  need to be linked against the run-
    ning version. if you have a single application that you want to
    run against the two different versions you would need two  sepa-
    rately linked images of that application and make sure you  run
    the correct one.
                                                 
    In short it is more trouble than it is worth.
    _sjz.