Conference virke::mrmemo

209.0. "MR MEMO fails to process outgoing messages" by GIDDAY::VELD () Wed Mar 15 1995 00:56

    This note was originally posted in the FORTY2::MAILBUS conference, but
    they told me I should post it here instead.  So, here we go ...
    
              <<< FORTY2::USER13:[NOTES$LIBRARY]MAILBUS.NOTE;1 >>>
                 -< MAILBUS - Message Router and its Gateways >-
================================================================================
Note 2683.0           MR MEMO - is there anybody out there?              1 reply
GIDDAY::VELD                                        177 lines  14-MAR-1995 07:03
--------------------------------------------------------------------------------
    Hello all,
    
    	I have a customer with the following configuration ...
    
    		ALL-IN-1 V3.1
    		DECfax V1.2
    		Message Router V3.3a
    		 - MR MEMO gateway
    
    	The customer is experiencing problems with the MR MEMO gateway
    failing to process outgoing messages.  This problem has only started
    happening after upgrades to ALL-IN-1 and DECfax.
    
    	The following information is extracted from the notes for this CSC 
    call.  As I have no idea about MR MEMO, I would appreciate any hints or 
    pointers that would allow me to provide an acceptable solution to the 
    customer.
    
    	Thanking you in advance ...
    
    Paul Veld - CSC Sydney.
    
================================================================================
    
MRMEMO FAILS TO PROCESS OUTGOING MESSAGES


>>ty SYS$COMMON:[MRMEMO]MRMEMO1.LOG
$!              SYLOGIN.COM
$!              -----------
$       set prompt = "MOAS2> "
$       set noverify
        Logged in to MOAS at  7-FEB-1995 09:54:38.56

$ define tt nl:
$ run/nodebug sys$system:mrmsrv
Time: 1995-02-07 09:54:41.35; message from server MRMEMO1:
%MRMEMO-I-NEWACCOUNT, opening new accounting file:
SYS$COMMON:[MRMEMO]MRMEMOACC1
.DAT;495

Time: 1995-02-07 09:54:50.28; message from server MRMEMO1:
%MRIF-E-NOMORE, no more elements left of this item code and class remain

%MRMEMO-W-TRACE, traceback forced from the Server Handler
-MRMEMO-I-FSM, idle, connected to MR and MEMO after message indicated in MR
mail
box
-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                  2658      000001BB  0009D71B
----- above condition handler called with exception 0935E862:
%MRIF-E-NOMORE, no more elements left of this item code and class remain
----- end of exception message

SRVMRD          SRV$MRD_GETNAM                   4383      000000C2  000A412D
SRVMRD          SRV$MRD_DISASS_BODY              4969      00000088  000A4800
SRVMRD          SRV$MRD_DISASS                   6142      0000101A  000A59B3
SRVACT          SRV$ACT_M                        3317      0000003D  000A2DEF
SRVDSP          SRV$DSP_FSM                      2093      00000115  0009D225
SRVMMO          SRV$MMO_ONE_LIFE                 3010      000001EF  0009C4E3
SRVMMO          SRV$MMO_MAIN                     2842      00000017  0009C2E7
                                                           000EBF6A  000EBF6A
KOTERM          KOTERM                            804      00000039  000E995E
                                                           000EBF45  000EBF45
KODOC           KODOC                            1768      00000097  000E6BA0
                                                           000EBF45  000EBF45

Time: 1995-02-07 09:54:59.55; message from server MRMEMO1:
%MRIF-E-NOMORE, no more elements left of this item code and class remain

%MRMEMO-W-TRACE, traceback forced from the Server Handler
-MRMEMO-I-FSM, idle, connected to MR and MEMO after message indicated in MR
mail
box
-MRMEMO-I-RING, ring: '      4A 4D 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                  2658      000001BB  0009D71B
----- above condition handler called with exception 0935E862:
%MRIF-E-NOMORE, no more elements left of this item code and class remain
----- end of exception message
SRVMRD          SRV$MRD_GETNAM                   4383      000000C2  000A412D
SRVMRD          SRV$MRD_DISASS_BODY              4969      00000088  000A4800
SRVMRD          SRV$MRD_DISASS                   6142      0000101A  000A59B3
SRVACT          SRV$ACT_M                        3317      0000003D  000A2DEF
SRVDSP          SRV$DSP_FSM                      2093      00000115  0009D225
SRVMMO          SRV$MMO_ONE_LIFE                 3010      000001EF  0009C4E3
SRVMMO          SRV$MMO_MAIN                     2842      00000017  0009C2E7
                                                           000EBF6A  000EBF6A
KOTERM          KOTERM                            804      00000039  000E995E
                                                           000EBF45  000EBF45
KODOC
                                *
                                *
                                *
                                *

%SNALU0-E-XMTFAIL, call to SNALU0$TRANSMIT[_W] failed
-SNALU0-E-TOPOSRSP, failed to change RU to positive response
-SNALU0-E-GETLU0VM, failed to obtain memory for LU 0 processing
-LIB-F-INSVIRMEM, insufficient virtual memory
Time: 1995-02-07 09:57:32.53; message from server MRMEMO1:
%SNALU0-E-XMTFAIL, call to SNALU0$TRANSMIT[_W] failed

--------------------------------------------------------------------------------

There are 6-8 messages in the MEMO mailbox.  The process that retrieves the 
messages from the mailbox appears to terminate each time.

Message Router was upgraded from 3.2 to 3.3a mid December - no problems.

ALL-IN-1 was upgraded from 3.0 to 3.1 last weekend    |  problem started
DECfax patch was applied to fix MR_FETCHER problems   |  happening

--------------------------------------------------------------------------------

We were able to get MRMEMO to work again for one day by stopping memo on the vax
and on the mainframe end, deleting some of the messages waiting to be sent from
VAX to MAINFRAME and restarting both ends again.

Today however it was broken again. The process seems to be looping. The image
running is MRMSRV.EXE. By looking at the process it seems to be running out of
some quotas. The ones involved are TQELM and PGFLQUO.

It seems the process is started without going through authorize to get process
quotas. The process quotas seem to be coming from PLQ params. We boosted TQELM
from 8 to 32 and also WSEXTENT from 2048 to 4096. We tried to change PGFLQUO
but the value we set did not seem to have any effect. It seems to be locked in
to 10,000, even though the PQL_DWSEXTENT is set to 30,000.

We managed to get it to send thorough a couple of messages but it then stopped
again.

--------------------------------------------------------------------------------

The result of the mrmemo test sending memo from ALL-IN-1 to the mainframe
is as follows

Attchments don't seem to make any difference

If the mainframe addressee is entered in the TO: field the memo seems to
go ok

If the mainframe addressee is entered in the CC: field the memo fails and
the sender receives a non delivery notification form memo as follows

                              M O A S   M A I L

                                       File No:
                                       Ref:
                                       Tel No:

                                       Date:     09-Feb-1995 12:03pm EST

TO:   FIELD@A1

FROM:                                      ( MEMO/Gateway@MEMO )


Subject:

MEMO was unable to accept the distribution of a message.
Please try again later or take action according to the next line.
  Receiver list error (on distribution).

--------------------------------------------------------------------------------