T.R | Title | User | Personal Name | Date | Lines |
---|
4403.1 | more info since no reply | KERNEL::MISTRYB | | Fri Jan 22 1993 10:42 | 17 |
| Ok,
I have no collected NODE4, LINE and CIRCUIT and I still get the
following message:
$ datatrieve
VAX DATATRIEVE V6.0
Digital Query and Report System
Type HELP for help
:NODE4_LINE_ERROR_RPT
"EXP_CVR_STATISTICS" is undefined or used out of context.
exit
So, what else do i have to collect, is there anything left to collect.
Bipin.
|
4403.2 | more info | KERNEL::MISTRYB | | Fri Jan 22 1993 11:59 | 6 |
| Hi,
More info, we've gone into SQL and found that EXP_CVR_STATISTICS is
defined as a BIGINT. So i don't understand why its complaining.
Bipin.
|
4403.3 | Yes there is a PB ... but FIX ? | MARS03::THOMAS | | Wed Jan 27 1993 11:30 | 7 |
|
I had the same pb on my customer site.
I think that something is wrong in the DTR procedure that builds
the node4 line error report. Is there anywhere a fix to this bug?
Regards
|
4403.4 | Another problem i have noticed | BEANO::MISTRY | | Thu Jan 28 1993 06:39 | 9 |
| Hi,
Another problem is that some of the reports (ie node4 line error and some snmp
ones) generate empty report files. Now this was mentioned earlier in the
notesfile but i'm not sure whether anyone put a solution in. Has anyone ever
sorted this problem out.
Bipin
|
4403.5 | Someone may be looking at it | TOOK::MINTZ | Erik Mintz | Thu Jan 28 1993 06:46 | 5 |
| Someone in the Network Applications group has started to examine
reports very recently. I don't know what they have found so far.
-- Erik
|
4403.6 | Thanks for the info | BEANO::MISTRY | | Thu Jan 28 1993 12:45 | 8 |
| Hi,
Any ideas what version of MCC they are going to be looking at, because all the
problems are in 1.2 and 1.2.3. I haven't as yet had a chance to look 1.3. But I
suspect these problems may exist in that version as well.
Bipin.
|
4403.7 | Working on the 1.3 stream | TOOK::MINTZ | Erik Mintz | Thu Jan 28 1993 13:43 | 9 |
| Until recently, reports were not touched since the release of V1.2
(at which time the developer of the reports SERPed).
So the same problems continue in T1.3.1. The goal is to
improve them where possible for V1.3.
However, there is some chance since the reporting procedures are not
tied directly to MCC code, the V1.3 report procedures may be backwards
compatible with V1.2.x
|