|
As the developers don't seem to have read this, I'll give you some
indications :
> 1. How complex is the product to install on both the VAX and IBM
> side?
It's very easy by MAILbus standards. You have to do a little bit of
configuring after installation, but that is fairly straight forward.
On the IBM side DEC provides no sw, so there is nothing for you to
install. The IBM side is normally done by the company installing the
MEMO (proper) stuff. Hope you have somebody in the US that supports
MEMO!
> 2. Are there any known problems with the current release (vers.
> 2.0A) that we should know about?
Well, there are some "features" in the addressing that makes the pro-
duct addressing a bit ackward at times. These are being fixed in
an upcoming release.
Also, you have to manually do the housekeeping of log and acc files.
Addressing in a VAXmail environment is not quite as described in
the manual, see this notes.
There are also a couple of patches that you might want to apply, they
can also be found in this notes conf.
The MEMO server has had a habit of looping on certain errors related
to DDS. Increasing MRMEMO ENQLM to say 400 and installing MR S3.1-005
seems to have gotten rid of most problems.
> 3. How difficult is the product to support after installation?
Very easy, after installation we get hardly any calls now that we
have 2.0A installed.
> 4. Is there any prerequisite experience that a Specialist should
> have to install and support the product so that things run as smoothly
> as possible?
Well, it helps if you know your MAILbus, most customer problems are
addressing related anyway, so you might as well know MAILbus addressing
from the start, or you'll learn it the hard way.
You also need to set up a few access names in the IBM gateway, a IBM
guru onsite at the time of installation could be handy. After that
you hardly ever have to touch any IBM stuff.
> 5. What factors could complicate the installation and support of
> MR/MEMO? Is there any information we should get from our customer
> that we may not have now.
Seems you can make quite a mess of the IBM side if you don't know
what you're doing. Also we've sometimes found it hard to communicate
the IBM parameter settings between the IBM managers and us.
> 6. Is there any information regarding the "tool" used to implement
> the DDS data bas. If so, where can I find it?
The DDS data base is the DDS included in MR - regular MR manuals tell
you most things you need to know. There is also on MR support guide
available, see the notes FORTY2::MAILBUS for info on how to get it.
H�kan
|
|
> As the developers don't seem to have read this, I'll give you some
> indications :
Of course we've read it, we were waiting for you to do the explaining,
H�kan :-)
.1 covers the issues quite well, I'll just add a couple of things for
completeness:
> 2. Are there any known problems with the current release (vers.
> 2.0A) that we should know about?
The release notes for V2.0A can be found in 4.1, patches in 5.*
>> 6. Is there any information regarding the "tool" used to implement
>> the DDS data bas. If so, where can I find it?
> The DDS data base is the DDS included in MR - regular MR manuals tell
> you most things you need to know. There is also on MR support guide
> available, see the notes FORTY2::MAILBUS for info on how to get it.
I think Ilene might refer to the sync tool produced by LEG, Frankfurt.
This and documentation should be available through the Assets library in
Turin. If someone (in Frankfurt?) has recent information on this then
please post it here or in the particular note (10.*) dedicated to the
sync tool. I also seem to remember some type of info on the tool in
recent weeks in FORTY2::MAILBUS but can't remember what it was.
|