| Title: | SQL/Services Forum | 
| Notice: | kits(3) ft info(7) QAR access (8) SPR access (10) | 
| Moderator: | SQLSRV::MAVRIS | 
| Created: | Thu Oct 13 1988 | 
| Last Modified: | Fri Jun 06 1997 | 
| Last Successful Update: | Fri Jun 06 1997 | 
| Number of topics: | 2214 | 
| Total number of notes: | 8586 | 
    
    When a customer shuts down SQS 7.0 the SQS<_node>_SQLSRV_MON_0070.LOG
    file reports an event:
    
    %SQLSRV-I-EVENT_LOG, event logged at line 1415 in file COM_LISTENER.C;1
    %SQLSRV-E-BADLIS_MBXMSG, Bad DECnet listener mailbox message type: 1
    
    followed by another event:
    
    %SQLSRV-I-EVENT_LOG, event logged at line 3815 in file COM_DIALOG.C;1
    %SQLSRV-E-READERR, Error on read
    %SYSTEM-F-LINKABORT, network partner aborted logical link
    
    According to SQLSRV_MESSAGES70.TXT "An OpenVMS listener mailbox message
    had a type it did not know about."
    
    Why is this message here and what does it mean for the health of this
    node's DECnet services ?
    
    Regards,
    rcs
    
| T.R | Title | User | Personal Name | Date | Lines | 
|---|---|---|---|---|---|
| 2164.1 | FWIW | ORAREP::RTOAL2::MAHER | TIER3 simply a better RPC! | Thu Mar 20 1997 03:32 | 18 | 
|     Hi,
    
    Seeing how noone else replied, I'll have a guess.
    
    Message type 1 is msg$_trmunsolic which is great if you want to
    trap unsolicited data entry at a terminal but a network comserver
    is not very interested :-)
    
    I don't know what the protection mask is on the comserver's network
    message mailbox but I'd suggest some other program is writing
    rubbish to it or testing a broadcast trapping/unsolicited input
    program and ended up associating the wrong mailbox.
    
    I can't remember if it's possible to get the sender pid from the iosb
    and put that in a message but I am curious as to what is the protection
    mask you put on the mailbox?
    
    Regards Richar Maher
 | |||||
| 2164.2 | Benign error message logging bug | ORASQS::OXBURY | Oracle Corporation, Rdb Desktop Group|DTN 381-2704 | Thu Mar 20 1997 09:11 | 6 | 
|     I suspect this is a benign bug at the end of the shutdown processing
    where the code that's handling the shutdown sequence simply isn't
    handling the termination of stuff correctly. I've seen it before, and I
    think I may have even QAR'd it, but I don't remember for sure. 
    
    Si
 | |||||