| Sorry,
I forgot one point. The MEMo manager on the IBM side told us, that we
would not have the right to use the gateway.
We work with DDS validation, but we can test without DDS validation as
well.
Where is this right granted, I remember Stefan mentioning that the
gateway would set the flag anyway. Is there any other place we have to
countercheck ?
Thank Ute
|
|
Hi,
> I forgot one point. The MEMo manager on the IBM side told us, that we
> would not have the right to use the gateway.
>
> We work with DDS validation, but we can test without DDS validation as
> well.
> Where is this right granted, I remember Stefan mentioning that the
> gateway would set the flag anyway. Is there any other place we have to
> countercheck ?
There is nothing that can be done on the VAX side. As you say yourself
the authorization flag is always set by MRMEMO. All messages are
handled by MRMEMO in exaclty the same way, and MRMEMO does not
specifically recognize a Telex bound message from any other. If the
MEMO manager says that you're not allowed to use the gateway then he
seems to know more than I do. Presumably he has ways of
enabling/disabling this use. I suggest you talk directly to him. Also,
ask him whether he has means of tracing a message on the IBM side.
cheers,
Stefan
|
| Hello Ute,
.0> Any idea what can cause this attitude ? By the way, addressing syntax
.0> is something, we got from the MEMO user side, so that should work.
What does the addressing syntax look like?
1) abc.def
or
2) tx=12345 xyz
Syntax 2) does not work through the gateway. Syntax 1) might work but
I'm not sure. Since syntax 1) is a perfectly normal addressing syntax,
any problems with routing the message to the Telex port on the Memo
side should be a Memo problem. See also note 14.4.
Is there anyone out there that have a working installation where messages
are sent through MRMEMO to Memo Telex?
Anders
|