| 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 |
What can be the reason to have a timestamp of 17-nov-1858 in a
RDB-file created by the Exporter?
-Geert-
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4147.1 | date field zero filled | CSOADM::ROTH | Call off your goons, I give up! | Fri Nov 27 1992 11:11 | 5 |
I'm not an MCC or RDB guru, but it appears the date/time field is all 0's, thus the date of 17-Nov-1858. (VMS keeps time by the number of 100 nanosecond ticks since that date, stored as a quadword.) Lee | |||||
| 4147.2 | What is the cause? | BACHUS::FOLENS | Mon Nov 30 1992 08:08 | 20 | |
I was aware of the fact that this timestamp is equal to all 0's in the
date/time field of VMS. But how can the exporter used this timestamp?
Because Distributed Time Services need some time to initialize and
in the mean time the first data sample has been exported?
I also noticed that sometimes the exporter exports null-records to
the database with only the following fields containing real data:
bridge
time_stamp
mcc_export_sequence
mcc_export_sequence_number
All other values contain null-values.
After each entry with null values a new entry follows with the same
time_stamp and valid data.
What can be the cause of this?
-Geert-
| |||||
| 4147.3 | TOOK::SHMUYLOVICH | Tue Dec 01 1992 09:20 | 20 | ||
> I was aware of the fact that this timestamp is equal to all 0's in the
> date/time field of VMS. But how can the exporter used this timestamp?
> Because Distributed Time Services need some time to initialize and
> in the mean time the first data sample has been exported?
I think that Exporter received this timestamp from MCC call.
If you use MCC V1.2 I would recommend to look at the following columns:
- MCC_EXPORT_POLL_STATUS (1 - data available);
- EXP_CVR_STATUS (1 - response
2 - error
3 - common exception
4 - specialized exception);
- EXP_CVR1_STATUS.
Sam
| |||||