| 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 |
Hi all,
I've a problem in a customer site, the mrmemo version is 2.1;
Memo is closed then reopened on the IBM side every nights; to avoid log
message, problems whith automatic restart and to purge old log file, also
MRMEMO is stopped then restarted every days.
This works fine until we have changed VMS release (5.5-2), reinstalled Mrmemo
and reapplied patch on MRMSRV.EXE.
After the startup doing a 'mc mrmman sho 2' :
Current state: starting, connecting to MR and MEMO Gateway
In the 'mrmemo2.log' file: (mrmemo$logMask is 53)
Time: 1994-03-02 11:28:18.09; message from server MRMEMO2:
%MRMEMO-I-FSM, starting, connecting to MR and MEMO Gateway after clock tick
(one for every clock tick!)
The 'MRMEMO Server 2' process is in LEF state, using SDA the process appear:
Process index: 00B5 Name: MRMEMO Server 2 Extended PID: 2041EAB5
--------------------------------------------------------------------
Process status: 00140001 RES,PHDRES,LOGIN
PCB address 89E12D80 JIB address 8AFB75C0
PHD address 8EC91600 Swapfile disk address 00000000
Master internal PID 00F500B5 Subprocess count 0
Internal PID 00F500B5 Creator internal PID 00000000
Extended PID 2041EAB5 Creator extended PID 00000000
State LEF Termination mailbox 0000
Current priority 6 AST's enabled KESU
Base priority 5 AST's active NONE
UIC [00001,000011] AST's remaining 98
Mutex count 0 Buffered I/O count/limit 99/100
Waiting EF cluster 0 Direct I/O count/limit 100/100
Starting wait time 1A001A19 BUFIO byte count/limit 35024/35024
Event flag wait mask FFFFFF01 # open files allowed left 95
Local EF cluster 0 60000000 Timer entries allowed left 6
Local EF cluster 1 20000000 Active page table count 0
Global cluster 2 pointer 00000000 Process WS page count 1155
Global cluster 3 pointer 00000000 Global WS page count 53
We need to shut and restart the Mrmemo process, then it works well.
Thank you for any suggestion.
Paolo Recchia
SC Torino Italy.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 196.1 | Questions... | STKHLM::OLSSON | Anders Olsson, DC Sweden | Fri Mar 04 1994 19:52 | 39 |
I don't have any answers but some more questions...
> Memo is closed then reopened on the IBM side every nights; to avoid log
> message, problems whith automatic restart and to purge old log file, also
> MRMEMO is stopped then restarted every days.
Is MRMEMO restarted before or after Memo?
> This works fine until we have changed VMS release (5.5-2), reinstalled
> Mrmemo and reapplied patch on MRMSRV.EXE.
Which patch? Could you do ANALYZE/IMAGE on MRMSRV.EXE (both the running
one and the one used before re-installation if you still have it) and check
the following part (just to make sure the patch is there and that there
wasn't a patch in the old server that has been forgotten):
Patch Information
DEC eco levels 1- 96: %X'1E800200', %X'00000000', %X'00000000'
user eco levels 97-128: %X'00000000'
read/write patch area address: %X'00257CC9', length: 311
read-only patch area address: %X'00000000', length: 0
patch command text VBN: 1791
last patch date/time: 9-SEP-1993 17:58:53.01
> After the startup doing a 'mc mrmman sho 2' :
>
> Current state: starting, connecting to MR and MEMO Gateway
>
>
> In the 'mrmemo2.log' file: (mrmemo$logMask is 53)
>
> Time: 1994-03-02 11:28:18.09; message from server MRMEMO2:
> %MRMEMO-I-FSM, starting, connecting to MR and MEMO Gateway after clock tick
> (one for every clock tick!)
Could you get an SNA-trace of this situation?
Anders
| |||||
| 196.2 | Delete ncp object? | TOSSUC::RECCHIA | Mon Mar 07 1994 15:30 | 44 | |
Hi Anders,
the Mrmemo is restarted after Memo,
the applied patches are:
Channel Gateway (from your mail)
Fail to Shutdown (note 5.7)
Memory problem (note 5.14)
Incoming Non-Receipt Notifications (note 5.16)
now the ana/ima gives:
Image Identification Information
image name: "MRMSRV"
image file identification: "V2.1"
link date/time: 7-JAN-1994 13:10:00.28
linker identification: "05-13"
Patch Information
DEC eco levels 1- 96: %X'04050040', %X'00000000', %X'00000000'
user eco levels 97-128: %X'00000000'
read/write patch area address: %X'00257CB1', length: 335
read-only patch area address: %X'00000000', length: 0
patch command text VBN: 1791
last patch date/time: 2-MAR-1994 10:03:04.36
The last patch applied was the 'non-receipt' one, and I've also changed
the restart bach to delete the NCP object mrmemo2 before the 'MRMMAN
START 2' command.
After the two changes, the restart process seems working well during the
last days, but I'll wait a few.
When the mrmemo start wrongly the 'Net mailbox message' shows 'Type: 52'
when start normally I've seen always 'Type: 49' (If this can be helpful!!).
The Sna-Trace is empty, the link with the gateway is not created
when the problem occours.
Thank you Anders,
few days then I'll write you an answer.
Paolo Recchia
| |||||
| 196.3 | RESTART WORKS WELL!! | TOSSUC::RECCHIA | Thu Mar 10 1994 10:11 | 7 | |
Delete the NCP object before restarting the Mrmemo process, seems
resolves the problem.
Ciao,
Paolo Recchia
| |||||
| 196.4 | Still confused | STKHLM::OLSSON | Anders Olsson, DC Sweden | Fri Mar 11 1994 20:16 | 11 |
Nice to hear that a workaround was found. I still wonder though why the
NCP object definiton caused a problem. What does the object look like
before it is deleted?
Is there any NETSERVER.LOG created when in "problem mode"? What's in it?
Could it be a cluster alias related problem - any changes regarding
this lately?
Anders
| |||||