| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
Hi there, I installed mccbms version 1.2.7 it all worked fine. Then I installed
mccelm version 1.2.4 it compains about the following several times;
----------------------------------------------------------------------------
%DAP-E-ILLEGAL_CMDFILE, Illegal DAP command file -- File must be produced
by the
MSL Translator
------------------------------------------------------------------------------
then continues the installation seemingly fine. When it gets to the IVP it fails
with the following;
------------------------------------------------------------------------------
DECmcc (T1.2.7)
%MCC-I-NOPARCMD, BRIDGE_AM, TO FILE = MCCELM$OUT.TXT
^
%MCC-I-SYNTAXERR, Syntax error -- unable to interpret remainder of line
%MCC-E-ATTRNOTALLOW, no attribute or argument allowed
The following command failed.
"MANAGE/ENTERPRISE TEST MCC 0 BRIDGE_AM, TO FILE = MCCELM$OUT.TXT"
DECmcc ELM T1.2.4 Installation Failed
------------------------------------------------------------------------------
I have the entire installation captured in a file if someone wants to see it.
Questions.
What did I do wrong?
Do we have to track rev.s in the modules? ie. V1.2.7 with V1.2.7
By the way I am sure there was no other MCC process running.
The installation of ELM corupted the BMS environment such that I cannot start
MCC using the windows interface. But the character cell and forms environment
seem to work fine. The windows error is;
---------------------------------------------------------------------------------
$ manage/enter/inter=decw
no corresponding entity instance exists
%MCC-E-NOENTITY, no corresponding entity instance exists
$
--------------------------------------------------------------------------------
Reinstalling the bms package fixes the windows problem.
thanks
bill
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2875.1 | ELM T1.2.4 not compatible with BMS T1.2.7 | QUIVER::HAROKOPUS | Tue Apr 28 1992 17:52 | 7 | |
ELM T1.2.4 will not work with BMS T1.2.7 for about a million reasons. You need the ELM T1.2.7 kit. See note 3.149 for a pointer to the latest ELM kit. Make sure you read the release notes especially the "known problems and restrictions" around the installation process before attemting the installation. Bob | |||||
| 2875.2 | ASOLOK::SYSTEM | "Bill Morgan ASO network consultant." | Wed Apr 29 1992 09:27 | 7 | |
Thanks Bob, I wondered about that. I was under the impression I had the latest kit. Silly me. Will it be the general rule that all "modules" need to be the same rev and sub-rev? Thank again bill | |||||
| 2875.3 | TOOK::FONSECA | I heard it through the Grapevine... | Wed Apr 29 1992 10:48 | 5 | |
No, Management Module version numbers are no indication of compatability with a given version of BMS. TSAM T1.0.6 works only with BMS T1.2.4. TSAM T1.0.7 works only with BMS T1.2.7. -Dave | |||||
| 2875.4 | ELM Installation will help out with this | QUIVER::HAROKOPUS | Wed Apr 29 1992 11:08 | 10 | |
re .2 The ELM field test installation kit asks if you are runnning version xxx of BMS before proceeding. If you answer yes then the installation takes your word for it. In the SSB kit we will actually check to make sure that the user is running a compatiable version before proceeding with the installation. In addition. the release notes should indicate which versions of MCC are compatible with a given version of ELM. Bob | |||||