| 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 |
Is there any change from V1.2 with the meaning of the bits in the
logical names
MCC_EVENT_LOG
MCC_EVENT_TRACE
Which bits are do you advise to use to trace back problems related
to the use of the event-manager?
Regards,
Dominique.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3316.1 | Here are the bits... | BIKINI::KRAUSE | European NewProductEngineer for MCC | Tue Jul 07 1992 04:23 | 8 |
MCC_EVENT_LOG 1 enables event trace logging
MCC_EVENT_TRACE 80 trace event_get
100 trace event_put
Values are hex bitmasks. As usual: do NOT use any other values!
*Robert
| |||||
| 3316.2 | folklore | TOOK::MINTZ | Erik Mintz, dtn 226-5033 | Tue Jul 07 1992 10:19 | 7 |
DECmcc development will neither confirm nor deny the existance of these log bits :-) Seriously, the use of logicals/environmental variables that were introduced for use during development is totally unsupported, and some may have unpredictable results in the production code. | |||||