| 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 |
Sam, I am running DECmcc BMS T1.2.3 for VMS and the Exporter FM. I post a lot of export requests for different entities during one month. At the end of the month, I analyze the VMS/Rdb file with C programs and dynamic SQL. I am wondering about how to know (and consequently how to count) the unsucessful polls during the period. When an entity becomes unreachable, is a new row added into Rdb ? With which argument values ? NULL everywhere ? I guess TIME_STAMP always set up ? The following attributes are in ANY Rdb table : TIME_STAMP MCC_EXPORT_SEQUENCE MCC_EXPORT_SEQUENCE_NUMBER TIME_IDENTIFIERS TIME_STATUS What are the TIME_IDENTIFIERS and TIME_STATUS used for ? Thx. Jean-Luc
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2112.1 | RE .0 | TOOK::SHMUYLOVICH | Thu Jan 16 1992 17:13 | 27 | |
>When an entity becomes unreachable, is a new row added into Rdb ?
Yes.
>With which argument values ? NULL everywhere ?
NULL everywhere except TIME_STAMP, entity identification column(s),
MCC_EXPORT_SEQUENCE,MCC_EXPORT_SEQUENCE_NUMBER.
>What are the TIME_IDENTIFIERS and TIME_STATUS used for ?
The TIME_<attribute_partition_presentation_name> column represent
the time stamp returned from the corresponding MCC_call, e.g time
when these data were collected.
The TIME_STAMP is equal to TIME_IDENTIFIERS if MCC_call to Show
ALL IDENT has been successful. Otherwise TIME_STAMP contains the
time when this call has been made.
All above is correct for both V1.1 and V1.2.
The database table structure created by Exporter FM is described
in 1392.1
SAm S.
| |||||