[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| 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 |
3079.0. "YAMERB? (Yet Another MCC EXPORTER RDB BUG?)" by USTICA::ODOARDI () Tue May 26 1992 10:18
Dear all,
I may have hit one major problem with DECmcc V1.1 (but also propagated
to V1.2 as well):
- I'm EXPORTing data from entities NODE4 for EXECUTOR, LINE and CIRCUIT, no
apparent problems so far...
- When I try to REPORT based on this EXPORTed data for few nodes with one of
the provided procedures it always fails when I ask for data regarding ASKY
Fact is that ASKY has DECnet address 46.1016.
I'll save you time jumping directly to the conclusions:
- Opening the RDB file and looking at instance NODE4 I can only see 46.101, with
the last digit tragically missing from the database.
Now, I'm positive that this RDB file only contains data for ASKY and a couple
more NODE4 nodes (incidentally ASKY is the only one exceeding the fata 46.999
barreer...)
Has anybody seen this? Am I doing something wrong?
Thanks in advance,
Barbara.
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3079.1 | BUG | TOOK::SHMUYLOVICH | | Tue May 26 1992 19:00 | 6 |
|
Thank you for pointing to this problem.
It's fixed in final version of V1.2.
SAm
|