| > Our product has the requirement of maintaining 2 versions
> of the product on the same system simultaneously. This will
> cause a problem if the dictionaries are different between
> the 2 versions. Is there a recommended way for handing
> this?
If you are talking about field test versions, this is not recommended
at all. Depending on which version, you may have event pool incompatabilities
and private MIR problems in addition to dictionary problems.
> I thought we could copy the dictionary and parse files
> to a separate directory, as described in creating a DECmcc's
> developor's dictionary, but I think that would cause problems
> for other MM's which aren't defined by the environment
> variable MCC_SYS_LOCATION.
This is exactly what MCC_SYS_LOCATION is for. As long as MCC_SYS_LOCATION
is defined by everyone invoking a PM, it will be inherited by each
MM process created from that PM process.
-- Erik
|
|
> Our product has the requirement of maintaining 2 versions
> of the product on the same system simultaneously.
The product ACMS for UNIX product (or whatever it
is called when released) needs to support multiple
versions of the ACMS for UNIX product. (Both on UNIX
and VMS.) So, our customer could have ACMS for UNIX 1.0
and ACMS for UNIX 1.1 installed on the same system, and
require to be able to run them both without dependencies
or interference
So... could we take our .com files, help files, script
files and instead of putting them in /usr/mcc/mcc_system,
as described in the development guide, put them in
another directory like /usr/pdir/acms_010/mcc_system.
Then mv all the dictionary and parse files over there?
We would still put the exe in /usr/mcc/mmexe.
If our customer wanted to use 2 different AM's, one
being the ACMS for UNIX and some other that has the
information defined in /usr/mcc/mcc_system, wouldn't
there be a problem? (That second AM wouldn't find its
data?)
For VMS would we redefine the logical MCC_SYSTEMM to
be a search path including the default directory and
the ACMS for UNIX directory?
thanks,
Bonnie
|