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 |
I tried to install the mcc$exec kit of 22-dec-89 on a vaxstation 2000 running vms X5.4-4ce. The installation fails when it tries to start mcc on the command $MCC/MODULE=MCC$UI_TRM with two messages %MCC-E-REVECTCONFLICT %MCC-E-REVECTCONFLICT I am running DNS locally and installed both DNS and MCC from my own (privileged) account. I thought that the problem may be to do with DNS and added system access to all the directories (DNS$BackTranslation etc) but it still didn't work. Is MCC limited to VMS 5.3 only? Did I miss something in the release notes? Should I enter a QAR? Thanks, Mike
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
49.1 | Hickory and MCC (vms 5.3) | GOSTE::CALLANDER | Tue Feb 06 1990 12:49 | 28 | |
The following is extracted by a note written by Peter B.; hope this answers your question. The MCC kernel is linked with the input file sys$system:sys.stb in order to obtain some vms symbol addresses. MCC which was built using vms 5.3 has difficulties running on HICKORY when this vms dependent code is executed... A symptom is MCC/MODULE=MCC$UI_TRM %mcc-f-revconflict, Recvectoring conflict Fortunately, there is simple operation work around with the only side-effect of invoking the Debug-32 define mcc$Log 8 ! Image activate the debugger (and don't intercept system service calls) mcc MCC> |