[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | VAX MAILGATE for MEMO |
|
Moderator: | STKHLM::OLSSON |
|
Created: | Sat Feb 25 1989 |
Last Modified: | Tue May 14 1996 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 216 |
Total number of notes: | 933 |
59.0. "MEMO->DISOSS->MR/S wrong corr. id" by PEARS::SONNTAG (Michael Sonntag, TSSC-OIS, @MUH) Fri Nov 30 1990 12:42
Hello,
a customer has this configuration:
+--------+ verimation gwy +--------+
| MEMO +-----------------+ DISOSS |
+--------+ +---+----+
|
sna | gwy
|
+--+----+ mailbus +----------+
| MR/S +---------------+ ALL-IN-1 |
+-------+ +----------+
he sends a memo-message via disoss to an ALL-IN-1 user at the vmsworld,
disoss routet the (incoming) message from memo to the gateway, no problem.
mr/s accepts the message, no problem
mr/s routet to TS and TS to ALL-IN-1, no problem
but the memo user becomes not the delivery message back, because the correlation
id on the memo side is different to the corr. id wich comes back.
the corr. id comes from memo to disoss and to the sna-gwy (correctly), the mr/s
picks the id up and sends it back to disoss, but here is the problem. the mr/s
'manipulate' the corr. id (i belive a translation table is the originator of
the problem).
example:
from memo via disoss to mr/s: 0D07575BCAA307525122901A43
from mr/s back to memo via disoss: 0D07575BE0A30052510090E043
xx xx xx xx
reason:
disoss corr. id are only uppercase letters and figures, memo send hexcodes
(unprintable characters).
some questions:
- is my adoption correctly that the translation table generates the wrong corr.
id on mr/s side
- is it possible to manipulate the table that the correct corr. id doesnot
change
- if it possible, how much effort must be done
thanks and regard
Michael
p.s. i x-post this note to MAILBUS and MRMEMO
here an extract from the nbs-file from the memo-message:
000007 1 MSG[V2ENV] Len=0006CF
00000E 2 FIELD[MID] Len=00009E
000010 3 ASCII Len=000016
"S008809OCT199011080000
00002F 3 FIELD[%8043] Len=00007D
000038 4 FIELD[EXTERNAL_DATE] Len=000014
00003A 5 DATE Len=000012
00003C 6 ASCII Len=000010
"1990100911080000
000055 4 FIELD[EXTERNAL_ID] Len=00000D
000057 5 ASCII Len=00000B
"��*sL;|�'q� <======= ??????
00006B 4 FIELD[EXTERNAL_NUMBER] Len=000003
00006D 5 INT Len=000001
%58
000077 4 FIELD[SENDER_DEN] Len=000009
000079 5 ASCII Len=000007
"A446297
000089 4 FIELD[SENDER_DGN] Len=000005
00008B 5 ASCII Len=000003
"DGA
000097 4 FIELD[SENDER_REN] Len=000006
000099 5 ASCII Len=000004
"DSUA
0000A6 4 FIELD[SENDER_RGN] Len=000006
0000A8 5 ASCII Len=000004
"MEMO
0000B3 2 FIELD[PDATE] Len=000012
0000B5 3 DATE Len=000010
0000B7 4 ASCII Len=00000E
"19901009112220
0000CC 2 FIELD[PREC] Len=000003
0000CE 3 INT Len=000001
%01
here an extract from the nbs-file from a disoss-message:
000007 1 MSG[V2ENV] Len=000723
00000E 2 FIELD[MID] Len=000099
000010 3 ASCII Len=000016
"S011008OCT199014005403
00002F 3 FIELD[%8043] Len=000078
000038 4 FIELD[EXTERNAL_DATE] Len=000014
00003A 5 DATE Len=000012
00003C 6 ASCII Len=000010
"1990100814005403
000055 4 FIELD[EXTERNAL_ID] Len=000019
000057 5 ASCII Len=000017
"GOSK74 C60A080E0035E3S <===== correct
000077 4 FIELD[EXTERNAL_NUMBER] Len=000003
000079 5 INT Len=000001
%6E
000083 4 FIELD[SENDER_DEN] Len=000008
000085 5 ASCII Len=000006
"GOSK74
000094 4 FIELD[SENDER_DGN] Len=000005
000096 5 ASCII Len=000003
"CS1
0000A2 4 FIELD[SENDER_REN] Len=000005
0000A4 5 ASCII Len=000003
"CS1
0000AE 2 FIELD[PDATE] Len=000012
0000B0 3 DATE Len=000010
0000B2 4 ASCII Len=00000E
"19901008142004
0000C7 2 FIELD[PREC] Len=000003
0000C9 3 INT Len=000001
%01
T.R | Title | User | Personal Name | Date | Lines |
---|
59.1 | I suppose so | STKOFF::SPERSSON | Pas de Probleme | Fri Nov 30 1990 16:37 | 6 |
|
Well, this question seems to have got at least a part answer in the
MAILBUS conference. Those of you who read my first (now deleted) reply
try and forget it, it was completely off-target.
Stefan
|