[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference virke::mrmemo

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

92.0. "DDS validation and trouble" by SUOSW4::MOOG (ute_moog at suo) Tue Jul 30 1991 15:35

    Hello,
    
    we do have a slight problem with MRMEMO at BOSCH. 
    Since we introduced DDS validation, the server crashes every night.
    It seems that DDS housekeeping are the reason.
    
    The log file states the following:
    %SNA-I-UNBIND, unbind reeceived from IBM application
    Time:.... 02:34:... message from MRMEMO1:
    %MRMEMO-F-UNBIND, UNBIND request received from MEMO gateway
    Time:... 03:31:... message from Server MRMEMO1:
    %DDS-E-OPSYS, Operating system interface error
    -SYSTEM-F-NOPRIV, no privilege for attempted operation
    %MRMEMO-W-TRACE traceback forces from Server Handler
    MRMEMO-I_FSM,. idle, connected to MR and MEMO after clock tick
    MrmEMO-I-RING ring: '1A 1A 1A 1A 1A 1A...' substates: 0000030
    TRACE-W-TRACEBACK symbolic stack dump follows...
    
    TAt about this time ran DDS$TIDY and had some problems with updating
    the cache.
    
    This message is repeated 2 times in the logfile.
    
    The next then is  
    Time:... 03:31:... message from Server MRMEMO1:
    %DDS-E-OPSYS, Operating system interface error
    -SYSTEM-F-NOPRIV, no privilege for attempted operation
    
    Time: ... 03:34..., messager from server MRMEMO1:
    % MRMEMO-W-DDSINITTIME, DDS initializtaion timed out
    ...
    stack dump folows
    
    This continues until the server is stopped and started.
    
    
    Any comments ?
    
    Thanks 
    Ute

T.R Title User Personal
Name Date Lines

92.1 MRMEMO doesn't handle DDS being away very well STKOFF::SPERSSON Pas de probleme Thu Aug 08 1991 11:49 26

T.R	Title	User	Personal Name	Date	Lines
92.1	MRMEMO doesn't handle DDS being away very well	STKOFF::SPERSSON	Pas de probleme	`Thu Aug 08 1991 11:49`	26
	Hi, MRMEMO is known to have problems if: 1) DDS is gone for a long time (ie longer than the few minutes that DDS$TIDY usually requires) 2) At the same time a message is processed which requires DDS access. In this case it seems that DDS$TIDY has problems fulfilling its mission, so MRMEMO suffers, too. It seems a bit strange when you say that MRMEMO crashes every night. This seems to imply that messages are transferred every night. Is this so? Maybe they can be transferred at another time, say before or after DDS$TIDY runs. Anyway, if you have problems running DDS$TIDY, then I think you should concentrate on solving those and there's a good chance that MRMEMO will work better, too. In the meantime, I suggest you define a routine which closes the MRMEMO server while DDS$TIDY runs. Cheers, Stefan

    
    Hi,
    
    MRMEMO is known to have problems if:
    
    1) DDS is gone for a long time (ie longer than the few minutes that
    DDS$TIDY usually requires)
    
    2) At the same time a message is processed which requires DDS access.
    
    
    In this case it seems that DDS$TIDY has problems fulfilling its
    mission, so MRMEMO suffers, too. It seems a bit strange when you say
    that MRMEMO crashes every night. This seems to imply that messages are
    transferred every night. Is this so? Maybe they can be transferred at
    another time, say before or after DDS$TIDY runs.
    
    Anyway, if you have problems running DDS$TIDY, then I think you should
    concentrate on solving those and there's a good chance that MRMEMO will
    work better, too. In the meantime, I suggest you define a routine which
    closes the MRMEMO server while DDS$TIDY runs. 
    
    Cheers,
    
    	Stefan