|
Robin,
MRMEMO is known to have trouble coping with DDS being shutdown and then
coming up again, If no messages are sent to/from the gateway during
this time then it usually manages (and obviously if DDS lookups are
not used), but if messages do arrive during this time, the symtoms
described in your note are likely to occur. No messages will be lost,
fortunaltely. The recommendation is to stop MRMEMO while reconfiguring
DDS, and then restart.
If do hope your customer manages to restart MRMEMO after reconfiguring
DDS?
cheers,
Stefan
|
| $!
$! sylogin.com
$!
$ IF F$MODE() .NES. "INTERACTIVE" THEN 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-06-10 15:14:55.04; message from server MRMEMO2:
%MRMEMO-I-NEWACCOUNT, opening new accounting file: R3FUBA$DIA0:[MRMEMO]MRMEMOACC2.DAT;165
%ADA-F-PROGRAM_ERROR, PROGRAM_ERROR
-ADA-F-RECNOTPOS, Program is erroneous, error recovery by exception handling is not possible
-ADA-F-IMAFOREXI, The image was forced to exit
-ADA-F-EXCDUREXC, An exception occurred in the VAX Ada run-time library while handling an exception
%MRMEMO-I-CLOSEACC, closing accounting file: R3FUBA$DIA0:[MRMEMO]MRMEMOACC2.DAT;165
%MRMEMO-I-BYE, VAX MAILGATE for MEMO Server Exit
%ADA-F-PROGRAM_ERROR, PROGRAM_ERROR
$ logout
MRMEMO job terminated at 10-JUN-1991 15:18:21.23
Accounting information:
Buffered I/O count: 149 Peak working set size: 2689
Direct I/O count: 75 Peak page file size: 11888
Page faults: 1870 Mounted volumes: 0
Charged CPU time: 0 00:00:10.45 Elapsed time: 0 00:03:40.16
The customer will shut the mrmemo-servers and reconfigure the (lokal)node
from england to a worldsearchnode tomorrow-morning.
thanks
michael
that's a good item for the release notes?
|