| 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 |
Hello, i have generate a DECwrite Document only with text. Then i send this DOC-File via MRGATE to MEMO. The state of the SERVER changes from: starting, connecting to MR and MEMO Gateway to idle, connected to MR and MEMO (message indicated in MR mailbox) (disassembling) starting .............. OK, the server loops and cann't disassemble the message but the attached document have decbody_7. May you can help me to find where the failure is. Regards Michael MRMEMO V2.1 MRGATE V3.2 (BL10.8) Message Router V3.2 (BL9.07) Here is a part of the NBS-Dump of the Message: File DISK$USER2:[MB$.MR.MSG1]MR2834.NBS;1 contains ****** bytes. 000007 1 MSG[V2ENV] Len=001578 00000A 2 FIELD[MID] Len=00001C 00000C 3 ASCII Len=00001A "32945142901991/2834@TSSCOS 000029 2 FIELD[PDATE] Len=000012 00002B 3 DATE Len=000010 00002D 4 ASCII Len=00000E "19910924154923 000042 2 FIELD[SENDER] Len=000038 000049 3 ENT[NAME] Len=000031 00004F 4 SEQ Len=000000 000055 4 SEQ Len=000025 00005C 5 ATTR[ROUTE] Len=00000E 000062 6 SEQ Len=000008 000064 7 ASCII Len=000006 "MRGATE 000071 5 ATTR[USERID] Len=000009 000073 6 ASCII Len=000007 "SONNTAG 000081 2 FIELD[TO] Len=00004E 000087 3 SEQ Len=000048 00008E 4 ENT[NAME] Len=000041 000094 5 SEQ Len=000000 00009A 5 SEQ Len=000027 0000A1 6 ATTR[ROUTE] Len=00000C 0000A7 7 SEQ Len=000006 0000A9 8 ASCII Len=000004 "MEMO 0000B4 6 ATTR[USERID] Len=00000D 0000B6 7 ASCII Len=00000B "DGA.GYTSCBB 0000C8 5 ATTR[PERRECFLG] Len=000007 0000CB 6 BITS[%00] Len=000004 %A8000000 0000D8 2 FIELD[UACONTID] Len=00000C 0000DA 3 ASCII Len=00000A "TEST AGAIN 0000ED 2 FIELD[PERMSGFLG] Len=000007 0000F0 3 BITS[%00] Len=000004 %10000000 0000FD 2 FIELD[ITRACE] Len=000045 000103 3 SEQ Len=00003F 00010C 4 FIELD[MTA] Len=000008 00010E 5 ASCII Len=000006 "UNHOLD 00011D 4 FIELD[ARVDATE] Len=000016 000123 5 DATE Len=000010 000125 6 ASCII Len=00000E "19910924154923 00013C 4 FIELD[ACTION] Len=000006 00013E 5 INT Len=000004 %00000000 00014B 2 FIELD[HOPCOUNT] Len=000006 00014D 3 INT Len=000004 %00000001 00015A 2 FIELD[CONTENTDIA] Len=000006 00015C 3 INT Len=000004 %00000002 000167 2 MSG[V2CONT] Len=001418 00016E 3 FIELD[FROM] Len=000050 000175 4 ENT[NAME] Len=000049 000177 5 SEQ Len=000000 00017D 5 SEQ Len=00002D 000184 6 ATTR[ROUTE] Len=000016 00018A 7 SEQ Len=000010 00018C 8 ASCII Len=000006 "TSSCOS 000194 8 ASCII Len=000006 "MRGATE 0001A1 6 ATTR[USERID] Len=000009 0001A3 7 ASCII Len=000007 "SONNTAG 0001B1 5 ATTR[FREEFORM] Len=00000D 0001B7 6 ASCII Len=000007 "SONNTAG 0001C5 3 FIELD[TO] Len=000046 0001CB 4 SEQ Len=000040 0001D2 5 ENT[NAME] Len=000039 0001D4 6 SEQ Len=000000 0001DA 6 SEQ Len=000027 0001E1 7 ATTR[ROUTE] Len=00000C 0001E7 8 SEQ Len=000006 0001E9 9 ASCII Len=000004 "MEMO 0001F4 7 ATTR[USERID] Len=00000D 0001F6 8 ASCII Len=00000B "DGA.GYTSCBB 000204 6 ATTR[PERRECFLG] Len=000007 000207 7 BITS[%00] Len=000004 %A8000000 000212 3 FIELD[SUBJ] Len=00000C 000214 4 ASCII Len=00000A "TEST AGAIN 000225 3 FIELD[ATTACH] Len=000063 00022C 4 MSG[TEXT] Len=00005C 000232 5 ASCII Len=000056 "VMSmail To information: MRGATE::"MEMO::DGA.GYTSCBB" "VMSmail CC information: SONNTAG 00028F 3 FIELD[ATTACH] Len=0012F0 000296 4 MSG[DECBODY_07] Len=0012E9 00029D 5 VEND[IMAGE] Len=0012E2 0002A4 6 VEND[IMAGTY] Len=000015 0002AA 7 ASCII Len=00000F " 0002C0 6 VEND[IMAGPROC] Len=00000D 0002C6 7 ASCII Len=000007 "FOREIGN 0002D4 6 VEND[IMAGDAT] Len=0012AB 0002DB 7 BITS[%00] Len=000008 %0100000201000000 0002EA 7 BITS[%00] Len=000072 %01000400000000000200020000 "more data" ................................ "more data" ................................ %02030004000000000004000100 %810103A3808001020000000000 %0000000000 00157F 0End of file
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 103.1 | Should work, need more info | STKOFF::SPERSSON | Pas de probleme | Wed Sep 25 1991 09:50 | 18 |
Michael,
What does MRMEMOn.LOG say?
How do you send the .DOC file to MRMEMO?
MAIL> SEND X.DOC
To: MRGATE::"MEMO::..." or another way?
Have you got the NBS files available for me to look at?
Can you give me a pointer to an MRGATE V3.2 kit?
cheers,
Stefan
| |||||
| 103.2 | more infos | PEARS::SONNTAG | Michael Sonntag, TSSC-OIS, @MUH | Wed Sep 25 1991 11:43 | 151 |
Hello Stefan,
>> What does MRMEMOn.LOG say?
see end of reply
>> How do you send the .DOC file to MRMEMO?
>>
>> MAIL> SEND X.DOC
>> To: MRGATE::"MEMO::..." or another way?
correct. to:mrgate::"memo::DGA.GYTSCBB"
>> Have you got the NBS files available for me to look at?
you can find the nbs-file on TSSCOS::mr2834.nbs
>> Can you give me a pointer to an MRGATE V3.2 kit?
i can copy the message router and mrgate kit to you
remarks:
$install list sys$library:cda$access
cda$access;3 open hdr shar lnkbl
all patches included in mrmsrv.exe
regards
Michael
-----------------------------------------------------------------------------
$ exit
$! M r m e m o . C o m - comments and copyright notice at the end
$!
$ set noon
$ set verify
$ define tt nl:
$ run/nodebug sys$system:mrmsrv
Time: 1991-09-25 10:17:42.54; message from server MRMEMO1:
%MRMEMO-I-NEWACCOUNT, opening new accounting file: USER2:[MRMEMO]MRMEMOACC1.DAT;116
Time: 1991-09-25 10:17:53.68; message from server MRMEMO1:
%SYSTEM-F-PRIVINSTALL, shareable images must be installed to run privileged image
%MRMEMO-W-TRACE, traceback forced from the Server Handler
-MRMEMO-I-FSM, idle, connected to MR and MEMO after message indicated in MR mailbox
-MRMEMO-I-RING, ring: ' 4A 4D 52 19.', substates: 00000470
%TRACE-W-TRACEBACK, symbolic stack dump follows
module name routine name line rel PC abs PC
SRVLOG SRV$LOG_HANDLER 3943 000001C9 001E379D
----- above condition handler called with exception 00002054:
%SYSTEM-F-PRIVINSTALL, shareable images must be installed to run privileged image
----- end of exception message
SRVMRD SRV$MRD_DISASS_TEXT 6314 00000422 001ED903
SRVMRD SRV$MRD_DISASS_BODY 11056 00000031 001F1F21
SRVMRD SRV$MRD_DISASS 11550 000005E2 001F2575
SRVACT SRV$ACT_M 4710 0000003D 001EB1A9
SRVDSP SRV$DSP_FSM 3310 00000115 001E3299
SRVMMO SRV$MMO_ONE_LIFE 4376 000001EF 001E03BF
SRVMMO SRV$MMO_MAIN 4208 00000017 001E01C3
00239BAE 00239BAE
KOTERM KOTERM 804 00000039 002375A2
00239B89 00239B89
KODOC KODOC 1768 00000097 002347E4
00239B89 00239B89
0026573E 0026573E
ADA$ELAB_DDS ADA$ELAB_DDS 0000000E 001C0C0E
00239B89 00239B89
Time: 1991-09-25 10:18:06.61; message from server MRMEMO1:
%SYSTEM-F-PRIVINSTALL, shareable images must be installed to run privileged image
%MRMEMO-W-TRACE, traceback forced from the Server Handler
-MRMEMO-I-FSM, idle, connected to MR and MEMO after message indicated in MR mailbox
-MRMEMO-I-RING, ring: '4A 4D 52 19 ][ 4A 5A 59 52 19.', substates: 00000430
%TRACE-W-TRACEBACK, symbolic stack dump follows
module name routine name line rel PC abs PC
SRVLOG SRV$LOG_HANDLER 3943 000001C9 001E379D
----- above condition handler called with exception 00002054:
%SYSTEM-F-PRIVINSTALL, shareable images must be installed to run privileged image
----- end of exception message
SRVMRD SRV$MRD_DISASS_TEXT 6314 00000422 001ED903
SRVMRD SRV$MRD_DISASS_BODY 11056 00000031 001F1F21
SRVMRD SRV$MRD_DISASS 11550 000005E2 001F2575
SRVACT SRV$ACT_M 4710 0000003D 001EB1A9
SRVDSP SRV$DSP_FSM 3310 00000115 001E3299
SRVMMO SRV$MMO_ONE_LIFE 4376 000001EF 001E03BF
SRVMMO SRV$MMO_MAIN 4208 00000017 001E01C3
00239BAE 00239BAE
KOTERM KOTERM 804 00000039 002375A2
00239B89 00239B89
KODOC KODOC 1768 00000097 002347E4
00239B89 00239B89
0026573E 0026573E
ADA$ELAB_DDS ADA$ELAB_DDS 0000000E 001C0C0E
00239B89 00239B89
Time: 1991-09-25 10:18:20.31; message from server MRMEMO1:
%SYSTEM-F-PRIVINSTALL, shareable images must be installed to run privileged image
%MRMEMO-W-TRACE, traceback forced from the Server Handler
-MRMEMO-I-FSM, idle, connected to MR and MEMO after message indicated in MR mailbox
-MRMEMO-I-RING, ring: '][ 4A 5A 59 52 19 ][ 4A 52 19.', substates: 00000430
%TRACE-W-TRACEBACK, symbolic stack dump follows
module name routine name line rel PC abs PC
SRVLOG SRV$LOG_HANDLER 3943 000001C9 001E379D
----- above condition handler called with exception 00002054:
%SYSTEM-F-PRIVINSTALL, shareable images must be installed to run privileged image
----- end of exception message
SRVMRD SRV$MRD_DISASS_TEXT 6314 00000422 001ED903
SRVMRD SRV$MRD_DISASS_BODY 11056 00000031 001F1F21
SRVMRD SRV$MRD_DISASS 11550 000005E2 001F2575
SRVACT SRV$ACT_M 4710 0000003D 001EB1A9
SRVDSP SRV$DSP_FSM 3310 00000115 001E3299
SRVMMO SRV$MMO_ONE_LIFE 4376 000001EF 001E03BF
SRVMMO SRV$MMO_MAIN 4208 00000017 001E01C3
00239BAE 00239BAE
KOTERM KOTERM 804 00000039 002375A2
00239B89 00239B89
KODOC KODOC 1768 00000097 002347E4
00239B89 00239B89
0026573E 0026573E
ADA$ELAB_DDS ADA$ELAB_DDS 0000000E 001C0C0E
00239B89 00239B89
Time: 1991-09-25 10:18:33.55; message from server MRMEMO1:
%SYSTEM-F-PRIVINSTALL, shareable images must be installed to run privileged image
%MRMEMO-W-TRACE, traceback forced from the Server Handler
-MRMEMO-I-FSM, idle, connected to MR and MEMO after message indicated in MR mailbox
-MRMEMO-I-RING, ring: '][ 4A 52 19 ][ 4A 5A 59 52 19.', substates: 00000430
%TRACE-W-TRACEBACK, symbolic stack dump follows
module name routine name line rel PC abs PC
SRVLOG SRV$LOG_HANDLER 3943 000001C9 001E379D
----- above condition handler called with exception 00002054:
%SYSTEM-F-PRIVINSTALL, shareable images must be installed to run privileged image
----- end of exception message
SRVMRD SRV$MRD_DISASS_TEXT 6314 00000422 001ED903
SRVMRD SRV$MRD_DISASS_BODY 11056 00000031 001F1F21
SRVMRD SRV$MRD_DISASS 11550 000005E2 001F2575
SRVACT SRV$ACT_M 4710 0000003D 001EB1A9
SRVDSP SRV$DSP_FSM 3310 00000115 001E3299
SRVMMO SRV$MMO_ONE_LIFE 4376 000001EF 001E03BF
SRVMMO SRV$MMO_MAIN 4208 00000017 001E01C3
00239BAE 00239BAE
KOTERM KOTERM 804 00000039 002375A2
00239B89 00239B89
KODOC KODOC 1768 00000097 002347E4
00239B89 00239B89
0026573E 0026573E
ADA$ELAB_DDS ADA$ELAB_DDS 0000000E 001C0C0E
00239B89 00239B89
Time: 1991-09-25 10:18:36.46; message from server MRMEMO1:
%MRMEMO-I-SHUTTING, server shutting down
Time: 1991-09-25 10:18:44.87; message from server MRMEMO1:
%MRMEMO-I-BYE, VAX MAILGATE for MEMO Server Exit
$ logout
MRMEMO job terminated at 25-SEP-1991 10:18:46.22
Accounting information:
Buffered I/O count: 476 Peak working set size: 2048
Direct I/O count: 252 Peak page file size: 17707
Page faults: 5033 Mounted volumes: 0
Charged CPU time: 0 00:00:13.54 Elapsed time: 0 00:01:20.43
| |||||
| 103.3 | Possibly DDIF converters need to be installed, or message size problems | STKOFF::SPERSSON | Pas de probleme | Wed Sep 25 1991 17:54 | 43 |
Hi again,
Well the Logfile clearly indicates that a shareable image should be
INSTALLed. CDA$ACCESS is OK, two other files I can think of are:
SYS$LIBRARY:DDIF$READ_DECBODY7.EXE ! DECBODY 7 Front end. Included in
! MRMEMO kit. Not INSTALLed by
! default
SYS$LIBRARY:DDIF$WRITE_TEXT.EXE ! Standard ASCII Back end.
! INSTALLed by default
Try and INSTALL the above and see if it works better. I must confess I
made some tests and was not able to reproduce your problem, even after
de-installing DDIF$WRITE_TEXT.EXE. This may have to do with Server
Process privs though.
The privs of the MRMEMO account I'm using are:
--------------------------------------------------------------------
Authorized Privileges:
CMKRNL SYSNAM DETACH TMPMBX OPER EXQUOTA NETMBX SYSPRV BYPASS
SYSLCK READALL
Default Privileges:
CMKRNL SYSNAM GRPNAM GROUP ALTPRI TMPMBX WORLD OPER EXQUOTA
NETMBX SYSPRV BYPASS SYSLCK READALL
--------------------------------------------------------------------
Another thing: How large is your message? Be aware that you may run
into problems if you try and transmit messages approaching MEMO's
limit, 50 Kb (approx 100 blocks). I'm currently investigating Large
Message issues, and I've noticed that MRMEMO doesn't always act as
intended...
Hope this helps,
cheers,
Stefan
| |||||
| 103.4 | That's the reason why | PEARS::SONNTAG | Michael Sonntag, TSSC-OIS, @MUH | Thu Sep 26 1991 13:41 | 6 |
Hi Stefan,
DDIF$WRITE_TEXT was n o t installed. Now it works.
Thanks for the support
Michael
| |||||
| 103.5 | Execute only access to sharable image? | STKHLM::OLSSON | Anders Olsson, SIP Sweden | Fri Sep 27 1991 00:17 | 19 |
There is still the question WHY this happened. I can think of two
possibilities:
1) You have installed MRMEMO.EXE with privileges (not recommendable)
2) One (or several) of the sharable images used by MRMEMO is not
readable (RMS read access not allowed) but only executable (RMS
E access).
In both these cases, the image activator enters "restricted" mode and
requires that images referenced by an execute only sharable image or
privileged main image are installed.
Sometimes it can be a little tricky to find the offending (execute only)
image since sharable images often reference other sharable images etc.
and ALL images "below" the execute only image in the "reference tree"
must be installed.
Anders
| |||||
| 103.6 | UNHOLD::SONNTAG | Fri Sep 27 1991 13:34 | 38 | ||
Hello Anders,
>> 1) You have installed MRMEMO.EXE with privileges (not recommendable)
NO
>> 2) One (or several) of the sharable images used by MRMEMO is not
>> readable (RMS read access not allowed) but only executable (RMS
>> E access).
Directory SYS$COMMON:[SYSLIB]
DDIF$WRITE_TEXT.EXE;2
[SYSTEM] (RWED,RWED,RWED,RE)
DDIF$READ_DECBODY7.EXE;3
[SYSTEM] (RWED,RWED,RWED,RE)
Total of 2 files.
Directory SYS$SYSROOT:[SYSEXE]
MRMSRV.EXE;5 [SYSTEM] (RWED,RWED,RE,RE)
Total of 1 file.
Grand total of 2 directories, 3 files.
>> Sometimes it can be a little tricky to find the offending (execute only)
>> image since sharable images often reference other sharable images etc.
>> and ALL images "below" the execute only image in the "reference tree"
>> must be installed.
Do you know which images MRMEMO needs?
Regards
Michael
| |||||
| 103.7 | Get ready to start digging | STKHLM::OLSSON | Anders Olsson, SIP Sweden | Fri Sep 27 1991 22:26 | 22 |
.6> Do you know which images MRMEMO needs?
$ ANALYZE/IMAGE will tell you that (and a lot more). To just get the
list of referenced images, I usually do:
$ ANA/IM xyzzy /OUT=x.x
$ SEARCH x.x "image list"/wind=(0,20)
Then you have to apply the same operation to each one of the referenced
images, and then to each of the images referenced by the referenced
images etc. recursively until you have found all images activated by
MRMEMO directly or indirectly.
And still you are not done. There is also the possibility to dynamically
activate sharable images at run-time (through calls to
LIB$FIND_IMAGE_SYMBOL). CDA$ACCESS seems to use this method. To find
images that have been activated in this way, you can use SHO PROC/CHAN in
SDA (ANA/SYS) which will show you all files held open by a process
(including the image files).
Happy hunting,
Anders
| |||||