| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
Using V2.4 with customisations, we have a strange anomaly in Time
Management. It appears that some users do not always get the
'Conflicts ...' message when they read a meeting invitation which
conflicts with something in their diary. It is not readily reproducible
except in one case. This is a user's calender for one day (from EP
index):
> 1 A 08:00am 04:30pm Monsanto Board Visit
2 M 09:00am 10:00am TEST MEETING
3 M 01:00pm 02:00pm ANOTHER TEST
4 M 03:00pm 04:00pm TEST NO. 3
5 M 04:02pm 04:03pm TEST FROM COLIN #1
The first appointment should have blocked out the whole day, but when
the messages for the other 4 meetings came in, he did not get the
'Conflicts ...' message (I saw this with my own eyes!)
Here are some facts:
- I could *NOT* re-create the problem using other accounts (though
other users have said it happens).
- If I used NEWDIR to get to the offending account I did *NOT* get
the problem (on the same meeting).
- The account was re-named about 3 years ago.
- The account has over 300 meetings (mostly in the past).
- There are no customisations directly in this area, but TM is
customised to include Resource Scheduler.
Has anyone come across this before? By the way, I think the
'Conflicts..'
message is rather too fleeting; it's only a DISPLAY so pressing any
key will clear it. Perhaps it should change the default reply to
'NO' or be a prompt.
Colin Mclellan (DEC rep. at Monsanto, Pensacola)
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 348.1 | More insight | AIMTEC::ZANIEWSKI_D | Why would CSC specialists need training? | Fri Mar 27 1992 21:30 | 13 |
I've seen this, and reported it. The problem is reproducible on
demand. Thanks to Jonathan for looking into this one.
The problem only appears when a user reads an event notice
message, without having used the TM subsystem previously. And then
only on the first event message read (TM stuff must be initialized
far enough to stop further occurances at this point). And only if
it conflicts with a certain type of event.
You might try running the TM initialization things right after
MAIL INITIALIZE, to resolve the problem (untested).
Dave Zaniewski
| |||||
| 348.2 | That works! | ODIXIE::MCLELLAN | Make it so, Mr. Data | Fri Mar 27 1992 22:14 | 9 |
Thanks for your help!
I can confirm that a:
DO TMTMSPRE
before reading the message does cure the problem.
Colin.
| |||||