Conference virke::mrmemo

    
    Hi, this is the support group (of sorts). It is located in Stockholm,
    Sweden, which is not and has never been a part of Germany.
    
    MRMEMO uses the VAX SNA API for LU0 communication. This works and is
    supported over an SNA Gateway. Whether it works over Interlink I don't
    know.  
    
    The general Digital view of Interlink gateways seems to be that we don't
    support them unless we can reproduce reported problems on our own
    equipment. In my opinion this is fair enough. This has to go for MRMEMO
    as well. 
    
    In reply to this, Interlink usually claim that they can provide the
    support. Well in this case it means that they will have to install a full
    MAILbus configuration including ALL-IN-1, MRX, MRGATE etc in their
    support organization. Once they've done this they could easily provide
    the benchmarks you're after. 
    
    I don't wish to sound hostile, but it should be Interlink's
    responsibility, not ours, to prove that they can serve as platform for
    our software.
    
    Comments anyone?
    
    	Stefan
    

    Stefan,
    
    Thanks for the info...  I called Interlink, and (finally) got to speak
    to a Systems Engineer, who said that as long as an API could be made
    available, then MRMEMO would work (she said Interlink has LU0
    capability, if this is the proper terminology (please correct me
    here)).  In this case, I assume (you know what they say about
    assuming!) that all Alcatel would need to purchase is MRMEMO and API. 
    Alcatel will be purchasing MRX (our X.400 Gateway), as well as
    ALL-IN-1 Mail, so there's probably no need for them to use MRMEMO.
    
    By the way, I recently found out that a Digital site in Connecticut was
    proposing MRMEMO at ABB IMS (?) in the U.S., against Soft Switch, but
    lost the business.  Don't know whose Gateway product was used.
    
    Anita

    
    Hi Anita,
    
    Yes you're right that X.400 connections should be the ultimate way of
    communicating. Be aware though that they would need X.400 connectivity
    from MEMO as well. This exists, but it is very new in the marketplace,
    and I don't know of any sites where MEMO X.400 speak to MRX. Anyway, if
    they conform to the protocol it should work and even more important it
    should be supported.
    
    cheers,
    
    	Stefan
    
    

    G'day, Stefan,
    
    I guess there's always a first time for anything!  However, this maiden
    voyage of MEMO X.400 <-> MRX is a bit scary...
    
    Thanks for your help.  If you hear a scream emanating from Research
    Triangle Park, it'll be me!
    
    Regards,
    Anita

    Another question:
    
    Is there a notesfile w.r.t. DDS Synchronization?  I was curious as to
    whether or not DDS would work with the ALL-IN-1 directory (remember,
    I'm *new* at this!).
    
    Thanks again,
    Anita

    
    Anita,
    
>    Is there a notesfile w.r.t. DDS Synchronization?  I was curious as to
>    whether or not DDS would work with the ALL-IN-1 directory (remember,
>    I'm *new* at this!).
 
    I don't know of any conference dedicated to DDS synchronization.
    FORTY2::MAILBUS handles all Mailbus related stuff, including DDS.
    
    Just to clarify possible confusion, there is usually no need for
    specific sync tools between ALL-IN-1 and DDS, because that's provided
    within standard ALL-IN-1. What you may want here is something that
    synchronizes DDS with the MEMO directory.
    
    As you may already know, there is an Asset available which provides DDS
    synchronization with MEMO (see 10.* for details). That tool is a bit
    old and I don't know whether you'll be able to get any support for it.
    
    However I do know of a fairly new tool called the Directory
    Synchronizer. This is a generic DDS synch tool which has been produced
    by the DCC in Landover. It is available to you in the US as a product
    (or at least "product-like"), but not here in Europe yet. This tool is
    quite useful and the team that produces it is approachable, friendly
    and dedicated. The Directory synchronizer is a component within a "box"
    of software tools called Enterprise Messaging Services. Brief
    descriptions can be found in FORTY2::MAILBUS, notes 2672 and 2679-2684
    
    cheers,
    
    	Stefan

    
Hallo Anita,

DDS-SYNC is a PASS at the European Assets Library and was 
written in Germany. There isn't a Notesfile around the world.

The first Version of DDS-SYNC offers a solution which facilitates
the synchronization between the MEMO (IBM-Side) and the DDS database
and vice versa. You can also use DDS-SYNC (with some modifications) for 
PROFS and DISOSS.

Now, the EFT3 Version of DDS-SYNC V2.0 is available.
some infos about Version 2:
- support all DDS-Attribute-fields
- format-qualifier accepted
	-- Lower- and uppercase
	-- HEAD for headline at top of input-lists
	-- ...
- new indexfile structure (similar to X400-address)
- unique delete qualifier USE1
- ....
- ....
- bug fixing


if you need more information, write a reply or mail

Servus und sch�ne Gr��e aus dem sonnigen M�nchen
	Michael