| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
Hello !!
Here is an interresting customer problem.
A customer use TELEX 2.1 with ALL-IN-1 3.0A Mailbus 3.1B
and is complain themself that no telex is received in imcoming,
then so other external mails are recieved without problem.
So the connection between Mailbus and ALL-IN-1 .
My question is concerning the following NBS file that i
retreived from the customer site, does anybody can tell me
if there is somthing wrong in it. (i am not a specialist of NBS
file)
Thank you for your help
Best regards
David Blanchard@Geo
PS: Note cross posted to Mailbus
Content and envelop posted to MR:
--------------------------------
File $1$DUA4:[MB$.LANE.WORK]MR_LANE$POST.ENV;18 contains ****** bytes.
000007 1 MSG[V2ENV] Len=000124
00000E 2 FIELD[PREC] Len=000003
000010 3 INT Len=000001
%00
000018 2 FIELD[SENDER] Len=00003A
00001F 3 ENT[NAME] Len=000033
000025 4 SEQ Len=000000
00002B 4 SEQ Len=000027
000032 5 ATTR[ROUTE] Len=00000C
000038 6 SEQ Len=000006
00003A 7 ASCII Len=000004
"LANE
000045 5 ATTR[USERID] Len=00000D
000047 6 ASCII Len=00000B
"NCH FIN MVA
000059 2 FIELD[TO] Len=0000C0
00005F 3 SEQ Len=0000BA
000066 4 ENT[NAME] Len=000037
00006C 5 SEQ Len=000000
000072 5 SEQ Len=00001D
000079 6 ATTR[ROUTE] Len=00000A
00007F 7 SEQ Len=000004
000081 8 ASCII Len=000002
"a1
00008A 6 ATTR[USERID] Len=000005
00008C 7 ASCII Len=000003
"JOE
000096 5 ATTR[PERRECFLG] Len=000007
000099 6 BITS[%00] Len=000004
%88000000
0000A4 4 ENT[NAME] Len=000037
0000AA 5 SEQ Len=000000
0000B0 5 SEQ Len=00001D
0000B7 6 ATTR[ROUTE] Len=00000A
0000BD 7 SEQ Len=000004
0000BF 8 ASCII Len=000002
"A1
0000C8 6 ATTR[USERID] Len=000005
0000CA 7 ASCII Len=000003
"IMK
0000D4 5 ATTR[PERRECFLG] Len=000007
0000D7 6 BITS[%00] Len=000004
%88000000
0000E2 4 ENT[NAME] Len=000037
0000E8 5 SEQ Len=000000
0000EE 5 SEQ Len=00001D
0000F5 6 ATTR[ROUTE]
0000F5 6 ATTR[ROUTE] Len=00000A
0000FB 7 SEQ Len=000004
0000FD 8 ASCII Len=000002
"A1
000106 6 ATTR[USERID] Len=000005
000108 7 ASCII Len=000003
"JLJ
000112 5 ATTR[PERRECFLG] Len=000007
000115 6 BITS[%00] Len=000004
%88000000
000122 2 FIELD[UACONTID] Len=000009
000124 3 ASCII Len=000007
"MR_LANE
00012B 0End of file
File $1$DUA4:[MB$.LANE.WORK]MR_LANE$POST.CON;18 contains ****** bytes.
000007 1 MSG[V2CONT] Len=0002EA
00000E 2 FIELD[FROM] Len=000069
000015 3 ENT[NAME] Len=000062
00001B 4 SEQ Len=00001B
000022 5 ATTR[PNAME] Len=000014
000029 6 ATTR[SURNAME] Len=00000D
00002B 7 ASCII Len=00000B
"NCH FIN MVA
00003C 4 SEQ Len=000027
000043 5 ATTR[ROUTE] Len=00000C
000049 6 SEQ Len=000006
00004B 7 ASCII Len=000004
"LANE
000056 5 ATTR[USERID] Len=00000D
000058 6 ASCII Len=00000B
"NCH FIN MVA
00006A 4 ATTR[FREEFORM] Len=00000D
00006C 5 ASCII Len=00000B
"NCH FIN MVA
00007E 2 FIELD[TO] Len=000036
000084 3 SEQ Len=000030
00008B 4 ENT[NAME] Len=000029
000091 5 SEQ Len=000000
000097 5 SEQ Len=00001D
00009E 6 ATTR[ROUTE] Len=00000A
0000A4 7 SEQ Len=000004
0000A6 8 ASCII Len=000002
"a1
0000AF 6 ATTR[USERID] Len=000005
0000B1 7 ASCII Len=000003
"JOE
0000BB 2 FIELD[SUBJ] Len=00001E
0000BD 3 ASCII Len=00001C
"RATES OF EXCHANGES 06 MAY 94
0000E2 2 FIELD[CRTDATE] Len=000012
0000E4 3 DATE Len=000010
0000E6 4 ASCII Len=00000E
"19940506130821
0000FB 2 FIELD[ATTACH] Len=0001F6
000102 3 MSG[TEXT] Len=0001EF
000108 4 ASCII Len=0001E9
"FBSUN RCTRL
".FBNOT
"
"
"TO : ROC ROT IMK (**auto delivery**)
"TO : NNL OPS JLJ (**auto delivery**)
"FM : NCH FIN MVA
"
"RATES OF EXCHANGES 06 MAY 94
"
"BFR 34.3950
"DEM 1.6713
"DFL 1.8752
"DKR 6.5320
"FFR 5.7260
"HKDLRS 7.7265
"LIT 1608.7500
"PDS 1.4925
"SFR 1.4190
"SKR 7.9190
"YEN 102.9500
"SGD 1.5575
"PTAS 137.0700
"
"RGDS
"
"
"
"
"
"NNNN
0002F1 0End of file
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4148.1 | you have to specify | ISTWI1::CAGPAR | Wed May 11 1994 13:15 | 16 | |
Hi David;
I once installed Telex gateway on a customer . I did a configuration
to supply an ALL-IN-1 user name for incoming mails and a telex mailbox
that has a password "mr_telex" has to be set. You have to give other
information in order to get an help.
Did you specified an ALL-IN-1 account for incoming telexes ?
Did you checked your ALL-IN-1 mailbox A1's password ?
.
.
.
Seden cagpar
| |||||
| 4148.2 | more info | LEMAN::BLANCHARD | Blanchard David @ZSW DTN 753 2320 | Fri May 13 1994 10:24 | 25 |
Hi,
More info concerning this NBS question.
The Telex was running without problem with ALL-IN-1 3.0 , the customer
upgraded is system ALL-IN-1 to 3.0A (Mupa installation) , and
as soon he did it no more Incomming Telex arrived. I discussed with
Walter Bischel in Zurich, and he said that the problem is from
the ALL-IN-1's Fetcher ?? .
So now we should know wath is the differences between the Telex NBS
file and other NBS files, does a field inside the Telex NBS file
missing or the ALL-IN-1 3.0A Fetcher require it ?? .
I will receive an TK50 with the original Telex NBS file and i want
to try to repost this NBS file into my system to see if it goes
through or not.
Thank you for your help.
Best regards.
David Blanchard @GEO
Thank you for your help.
| |||||
| 4148.3 | Known feature? | IOSG::MARSHALL | A glitch in reality | Fri May 13 1994 11:44 | 16 |
I believe there was a fix put into V3.0A to improve the Fetcher's recovery process when presented with corrupt NBS files. One "problem" with this is that the Fetcher is now very sensitive to envelope files that do not adhere exactly to the NBS format for these files, as defined to us (ALL-IN-1) by the Message Router group. In particular, I notice your envelope NBS file doesn't have a Message Router ID, which may well upset the Fetcher: the MR ID is one of the fields it expects to be present (because the MR rules say it has to be there), and so may assume the file is corrupt if it's not there. My suggestion would be to wait for the next release to be announced and upgrade to it asap, as it should improve mail interworking considerably. Scott | |||||
| 4148.4 | Scott's right - missing MR ID will confuse it | IOSG::SHOVE | Dave Shove -- REO2-G/M6 | Fri May 13 1994 12:56 | 16 |
Scott is (as so often the case :-) ) quite right. I qoute from a
comment in the code (written by me, that's why I remembered it):
!+
!
! *************************************************************************
! Note -- this code relies on the MRID always being present in the envelope,
! and always before the FROM field, as READ_ENV_FLDS will not rewind
! the message if it fails to find a field.
! The Message Router team assure me (March, 1990) that this is so.
!
! *************************************************************************
!-
Sorry!
Dave.
| |||||
| 4148.5 | Just checking | AIMTEC::WICKS_A | Atlanta's Most (In)famous Welshman | Fri May 13 1994 18:37 | 1 |
has anyone reported this to MR/TELEX engineering? | |||||
| 4148.6 | CSOA1::LENNIG | Dave (N8JCX), MIG, @CYO | Fri May 13 1994 18:46 | 9 | |
re: .0
It appears to me as though the envelope and content dumps posted in .0
are the pre-post versions generated by MR/T (and as such won't have a
message-id or trace info or pdate or ... yet). You'll need to provide a
dump of the message as it sits in the A1 mailbox, or even better if
possible, dumps of the envelope and content files created by the fetch.
Dave
| |||||
| 4148.7 | MR ID creation | LEMAN::BLANCHARD | Blanchard David @ZSW DTN 753 2320 | Mon May 16 1994 12:11 | 19 |
Hello,
Ican't for the moment retreive information from nbs file stored into
A1 mailbox because there are so much waiting file i have to select the
right one. The envelope and content created by the fetch is the dump
inserted in reply .0 .
Another question is to know if the MR ID is set by Message Router or
if it should be create by the Application?
The MRIF manuel said that the Identification of the mail is created
by Message Router. ?? So what is correct.
Thank again and Best Regards
David Blanchard
| |||||
| 4148.8 | CSOA1::LENNIG | Dave (N8JCX), MIG, @CYO | Mon May 16 1994 12:35 | 16 | |
The NBS in .0 is V2 format; ALL-IN-1 pre-V3.1 requires V1 format (MR
converts the messages from V2 to V1 for ALL-IN-1). The NBS in .0 was
not fetched by ALL-IN-1. It looks to me like those are dumps of the
envelope and content produced by MR/T before being posted to MR.
>> Another question is to know if the MR ID is set by Message Router or
>> if it should be create by the Application?
>>
>> The MRIF manuel said that the Identification of the mail is created
>> by Message Router. ?? So what is correct.
If one is not supplied by the creator of the message, MR will add it.
Some applications generate their own MR IDs, some don't. It's up to the
application programmer/designer...
Dave
| |||||
| 4148.9 | There's nowt so queer as MR IDs... | IOSG::MARSHALL | A glitch in reality | Mon May 16 1994 15:05 | 12 |
re .7 and .8 Message IDs. There are some anomalies in this area; for example, if the application doesn't set the Message ID, but posts the message complete (which it's not supposed to do, but it appears that MRIF/MR allow this), MR will add the ID, but in the wrong place in the NBS file. This causes problems for other applications, such as ALL-IN-1 V3.0, which expect the ID to be in the correct place (as described in .3 and .4). I wonder if this is the problem in this case? Scott | |||||
| 4148.10 | problem fixed ! thank you ! | LEMAN::BLANCHARD | Blanchard David @ZSW DTN 753 2320 | Fri Jun 17 1994 10:54 | 16 |
Hello!
we fixed the problem by upgrading the Mailbus from 3.1B to S3.2-220
In fact the problem is really coming from the MR identication added
by the MAILBUS 3.1B, this identification was inserted into
the NBS file but not at the top of it, and the ALL-IN-1 3.0A
fetcher check it as first, if this identification doesn't appear
as first NBS field the fetcher will never deliver the mail.
We relinked the Telex gateway because the Mailbus version changed.
Thank you for your help really appreciated.
Best regards.
David Blanchard
| |||||