| 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 |
DECmcc SMS 2.1
VMS 5.5, VS4000 VLC, 16mb
Any ideas on why these attributes aren't accessible/defined? All this
has worked on my VS3100 (VMS 5.4-3!)
After editing MCC_STARTUP_DNA4_EVL.COM (<os_node>, etc, vs4000
registered successfully), it worked as expected until setting the
local sink monitor name to MCC_DNA4_EVL. Thanks in advance for any
comments.
$ @sys$startup:mcc_startup_dna4_evl
.
.
SET NODE4 VS4000 LOCAL SINK MONITOR NAME = MCC_DNA4_EVL
Response:
MCC ERROR = %MCC-E-ILVTNF, specified tag not found within current
constructor.
The procedure completed with no further errors, but the MCC_DNA4_EVL
process was not started.
From the IMPM, I selected the local sink monitor child entity of the
node. Then did: Operations-> Set-> Initial Attributes:
Initial Name-> MCC_DNA4_EVL
Initial State-> On
Initial Type-> MONITOR
The response was:
Attribute list contains one or more invalid attributes.
Initial Name: --Part of Failed Atomic Update
Initial State: -- ditto
Initial Type: --Attribute Not Settable
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2127.1 | some questions | TOOK::JEAN_LEE | Fri Jan 17 1992 13:22 | 13 | |
Hi,
Can you reproduce this error at MCC command line?
Can you reproduce this error repeatedly?
Can you use NCP to set the name?
I just tried this command (set) on a VMS 5.5 system and worked.
Can you provide more information about your system?
Jean
| |||||
| 2127.2 | Problem resolved via NCP. | GRANMA::JPARKER | Mon Jan 27 1992 21:33 | 12 | |
To close this...
Yes to the questions. BUT, when NCP was used to set the logging monitor
to name = mcc_dna4_evl, it worked. The process started and went to HIB
state normally. I then re-ran the DECmcc mcc_startup_dna4_evl.com
procedure it too worked normally. I have no additional data to describe
whay the procedure worked. No other actions were taken between using
NCP and re-running the dna4 startup procedure.
Thanks for the questions.
Jeff.
| |||||
| 2127.3 | MCC_DNA4_EVL error still persists erratically | FRSOLD::FRAFS1::MAASS | Fri Jan 31 1992 14:11 | 19 | |
Hi all, I have had the same problem with two installations. Exception: after setting the local sink via NCP, the procedure still gives error messages. DECmcc BMS V1.1 VAX/VMS V5.4-3 Motif V1.0 DECmcc SMS V2.1 VAX/VMS V5.4-2 DW On other nodes with the same S/W versions everything worked fine! Josch (Joerg Maass @FRS, OSS-NIS Frankfurt, Germany) | |||||