T.R | Title | User | Personal Name | Date | Lines |
---|
1085.1 | Your wish has already been granted, you have 2 left1 | IOSG::WDAVIES | There can only be one ALL-IN-1 Mail | Tue Jul 21 1992 12:36 | 5 |
| Sunil,
You can set automatic search escalation in V3.0 for certain.
Its a amatter of setting the breakpoints using SM/
Winton
|
1085.2 | Customer's like automagical things and DSB doesn't do much | GIDDAY::SETHI | Man from Downunder | Wed Jul 22 1992 03:03 | 34 |
| G'day Winton,
Thanks for your suggestion I did a SM MM DBS and set the flags to N.
This disabled the displaying of the messages "Addresse not found,
Search mail directory? ", points 2 and 3 in .0.
The user had to do a GOLD-MENU and enter SMD this returned a blank
index form then enter I to display the index. At this point the user
has to enter the Surname etc.
All that DSB does is disable the displaying of those messages and does
not continue to search Mail Directory. There is no automatic searching
of the Mail Directories at all. The customer wanted the users to enter
the surname and have a list of users displayed. What they find irritating
is having to enter I at the SMD menu then the Surname. The Username
that is displayed in the current item block isn't used.
The point is that this is not very intuitive interface for the users
nor user friendly. The customer would like to see the SMD searched
automatically if they have set OA$DDS_PRIME set to 1 or 2. I am just
making a point from the customers point of view and not having a go at
anyone. That's why I said in .0 the title of this topic can be changed
to having a *WISH*, I was not sure if this was a misfeature (bug).
From the customers point of view it's a bug or tacky way of doing
things. I am sure there are good reason why this has not been done
already.
Customer's like automagical things :-). Will the next release have a
thought scanner ? So customer only have to think and the computer will do
it all for them ;-).
Thanks for your help
Sunil
|
1085.3 | | IOSG::WDAVIES | There can only be one ALL-IN-1 Mail | Wed Jul 22 1992 11:32 | 6 |
| I'm sure the DSB should allow automagic escalation if they don't its
bust.
I'm investigating.
Winton
|
1085.4 | | IOSG::WDAVIES | There can only be one ALL-IN-1 Mail | Wed Jul 22 1992 12:45 | 14 |
| ok Sunil, experiment with me please :-)
There are four symbols you need to look at!
$EMDESCAL1
$EMDESCAL2
SYS$$EMDESCAL1
SYS$$EMDESCAL2
For automatic escalation, try setting all four to "0". In theory, just
the second two are neccessary - but I had the same problem as you
without them set. SM MM DSB sets the second two.
Winton
|
1085.5 | The results of my testing | GIDDAY::SETHI | Man from Downunder | Thu Jul 23 1992 09:52 | 48 |
| Winton,
First thing first the system wide symbol names are incorrect one "$", they
should be :-)
SYS$EMDESCAL1
SYS$EMDESCAL2
The system wide symbols were created by the DSB and created the local
permanent symbols and set them to 0.
Entered SMITH and got the DDS entry as expected. I exited ALL-IN-1 and
renamed the MANGER.PST to MANAGER.OLD and invoked ALL-IN-1. Entered
SMITH and got the DDS entry. Check for the values of the local permanent
symbols and got a symbol "$EMDESCALn" not found as expected.
Test two I reset the flags to "Y" in DBS and everything worked as
expected. The prompt was displayed and SMITH was found in DDS. It
looks like you dont need the local permanent symbols.
Test three I deleted the MANAGER.PST and renamed the MANAGER.OLD to
MANAGER.PST. Went into SM MM DSB and set the flags to "Y" and checked
the values of SYS$EMDESCALn they were set to 1 as expected. With the
break points enabled I would expect the prompt to be displayed to
search other mail directory it wasn't. The values of $EMDESCALn's was
set to 0.
Test four I set the values for $EMDESCALn's to 1 and I got the prompt
to display to search other mail directory.
Now what is the relationship between disabling the break points and the
local permanent symbols $EMDESCALn's, I can't see any. The local
symbols take precedence over the system wide one's.
To add to the mystery I adopted the Mail Directory after Installation
as per the Mail Management Guide page 3-10. I wonder if this has
anything to do with my system not requiring $EMDESCALn's ?
The only cause of this problem I can think of is that the System wide
and local symbols were undefined and may have caused this problem. I am a
bit puzzled by all of this. I would like to know what happened on your
system, the only difference I can see is that I adopted the mail directory
after installation.
The good thing is that we do have automagical searching another plus
for ALL-IN-1 development team.
Sunil
|
1085.6 | AUTOMAGIC DDS SEARCHING DOES WORK FOLKS! | IOSG::WDAVIES | There can only be one ALL-IN-1 Mail | Thu Jul 23 1992 10:45 | 16 |
| Sunil,
You do not need the user symbols - you are correct - they do
override the sytsem wide ones IF and ONLY IF they exist.
When I initially tested, I checked the DSB form and they were off, yet
I could not get 'davies' <RETURN> to do more than give the GOLD-M
message. Gold-M 'davies' worked fine.
I did something, which I do not know, which solved the problem - and it
worked - I could no longer reproduce the error. I thought it originally
was the user symbols being undefined, but I think it might the system
ones not being set properly by default. I may try to prove this later,
but I have a FUNC spec to write :-)
Winton
|
1085.7 | More news of my testing | GIDDAY::SETHI | Man from Downunder | Fri Jul 31 1992 10:09 | 27 |
| G'day All,
Just to let you know that I have adopted the Mail Directory after
installation on two nodes and have not experienced the problem.
On Monday I will try to reproduce the problem on a node that we are
currently installing ALL-IN-1 on and have accepted the Mail Directory
during installation.
If as I suspect on Monday DDS search does not work correctly I will SPR
this. I think there is something wrong with the installation
procedure hopefully I'll have some proof. If someone else can do the
testing I would be very grateful and post the results here and I'll SPR
it.
Is there a workaround to the problem ? Because Adopting the
Mail directory after installation on a system that you accepted the
Mail directory during installation does not work. If you get my drift.
I have checked DDS and everything I can think of.
Can someone tell me how do a display the trace on screen now days in
Version 3.0. Sorry to be a bit ignorant we have finally got version
3.0 working in Australia and I have not had the time to explore.
Thanks in advance
Sunil
|
1085.8 | Solution to the problem | GIDDAY::SETHI | Man from Downunder | Thu Aug 06 1992 09:07 | 58 |
| Hi,
At last we managed to solve the problem. We found the following
problems :-(
1. The customer had MBMAN V3.2-000 (BL5.26) installed and the
DDS$INQUE.DAT kept on getting corrupted. Each time
MAIL_DIR_CONVERT.SCP was run.
2. The ALL-IN-1 DDSID's did not match the one in DDS. This was checked
by doing a
a. within ALL-IN-1 <get profil.ddsid[#user], I couldn't get the
syntax correct for the for loop please let me know.
b. mc mbman SHOW DDS SUBSCRIBER/NAME="surname"/FULL
The solution that was put forward was to :-)
1. To install the latest version of Message Router and Message Router
Gateway Version 3.2-1. To check if you enter $ MC MBMAN it should
display MBMAN S3.2 (BL5.27)
One thing to node if MB$DISK:[MB$.DDS.DB]DDS$INQUE.DAT etc. already
exist the installation procedure will not replace them. So they
were copied to another directory then all the components were
re-configured. We delete the old components were deleted at the end
of this exercise. Another thing to note was that analyze/rms/check
did not show up any error's for DDS$INQUE.DAT. Stars articles were
helpful enter MAIL_DIR_CONVERT to display these articles.
2. In ALL-IN-1 we initialized the DDSID field for all users by entering
<FOR PROFIL DO WRITE CHANGE PROFIL USER = .USER, MDFLAG = OA$N,
DDSID = ""
3. Then ran the script MAIL_DIR_CONVERT.SCP.
4. Set the break points to "N" by doing a SM MM DSB.
Problem solved.
Points to look out for
The main one being if you have OA$DDS_PRIME set to 1, ALL-IN-1 profile
will be searched first than DDS. If you have SMITH A in profile and
SMITH B in DDS it will only find SMITH A. Looks like you can olny
search on surnames.
So the customer has to decide if he wants to use DDS as the primary
directory or ALL-IN-1. Setting OA$DDS_PRIME to 2 will search DDS first
overcoming the above problem. But there is are performance
considerations the customer has to think about.
Sorry if I have put in the obvious I thought it might be helpful to
someone who may not be aware of everything, just like me. If you have
anything to add please do so, I am always willing to learn.
Sunil
|