| 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'd like to request a couple enhancements to the mib compiler:
- Check to see if the dictionary is open for read-only access
at the start of the routine
- Check to see if the all the mib files entered in the list exist
I realize that these enhancements are meant to "protect the user
from themself", but I think these simple enhancements would be
very worthwhile.
The Mib compilation process is very time consuming. I tried compiling
6 mibs into MCC and it took approximately 5 hours. The first attempt
compiled the help files for the first mib and then aborted since I
had spawned out of the MCCFCL process to run the mib compiler.
The next attempt failed on the third mib compilation, due to and error
in creative window command editing. I compiled the STD and Experimental
mibs (cut/paste and edited the STD mib name and substituted EXP for
STD). My error was that I didn't have the right version number for the
experimental mib. So the compilation aborted, due to file not found,
never attempting to continue with the mibs in the rest of the list to
be compiled.
It's embarrassing pilot error, but I'll bet I'm not the only one that
one that will attempt to compile mibs with the dictionary open for
read only access. Please consider the enhancements...
Thanks!
rick
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4761.1 | MCDOUG::doug | pre-retinal integration | Thu Mar 25 1993 10:20 | 4 | |
If it's a bug, QAR it. If it's an enhancement request, put a note in NOTED::EMF_REQ. /doug | |||||
| 4761.2 | Easy MIB Compilation | MAIL::CLAYTON | Merlin Clayton DTN 445-7217 | Fri Mar 26 1993 13:39 | 38 |
I would like to add my 2-cents worth to .0. A customer of mine who is trialing MCC EMS V1.3 right now is having a hell of a time with the MIB compiler. I don't know that they have gotten any MIBs to compile in the past two weeks. They do things like: 1. Try to compile MIBs with the ICMP up and running (this is a definite no-no that is intuitive to us all) 2. Shut MCC down but leave the IP Poller up and running (same results as number 1 Data Dictionary Read Only error) 3. Due to lack of VMS knowledge and patience, they've blown away (corrupted) the data dictionary once and we had to go back in and reinstall. I've been on site two days a week for the past 3 weeks, and things work OK when I'm there. But when someone is not there to hand-hold, the customer makes little mistakes that have a big impact. I've been fooling around with a launched appl that invokes the MIB compiler from a "master" copy of the data dictionary, but have not yet succeeded in making that work. However, we need something like this (POLYCENTER MIB Compiler launched application) from the ICMP to make this function more idiot proof. This MIB compiler launched appl should incorporate the suggestions in .0. It should also present the user with a list of MIBs to select from with the possibility of incorporating a filtering feature for only Cisco, or only Chipcom, or only Xyplex, etc. I think the help files should be updated after the fact also, since this part is time consuming up front. Does anyone care to comment on the feasability of such an approach? At my customer's sight, we are be compared side-by-side with OPENview, and I'm reminded how well HP handles the inclusion of new MIBs from a simple "idiot proof" point and click menu appl. I would hope that we could try to achieve this level of simplicity. Merlin | |||||
| 4761.3 | We are aware of this problem... | MOLAR::DFLAT::PLOUFFE | Jerry | Mon Mar 29 1993 15:53 | 11 |
We are aware of this (serious) problem. We know it needs work. I am very busy replacing the v1.3 dictionary subsystem with some new technology gotten from the Common Agent project. This work currently takes precedence. After this work is completed we can address your legitimate concerns. Please be patient (he says, as if you already haven't! ;) ) - Jerry | |||||