Conference virke::mrmemo

178.0. "what unsupported document type?" by MLN08::MALACRIDA () Mon May 31 1993 11:30

    Although I've applied the patch to "handle" binary document type
    coming from MEMO, and although the customer has provided some filters 
    in order to not to send "strange" document type from MEMO,
    it looks like there still is around some document type coming 
    from MEMO that our gateway doesn't digest: here is what is left in the
    log file
    
    Can someone help in understandingg what is happening?
    
    Thanks,
    
    giovanni
    
    
%MRMEMO-W-UNSDOCTYP, unsupported document type
-MRMEMO-I-GIU_GIDMTDP, document profile operand
-MRMEMO-I-GIU_GIDMT, document unit

%MRMEMO-W-TRACE, traceback forced from the Server Handler
-MRMEMO-I-FSM, receiving from MEMO after data received from MEMO
-MRMEMO-I-RING, ring  '1A 1A 1A 1A 1A 1A 1A 13 3A 36.', substates: 00000070
%TRACE-W-TRACEBACK, symbolic stack dump follows 
module name     routine name                  line        rel PC      abs PC

SRVLOG          SRV$LOG_HANDLER
----- above condition handler called with exception 08938290:
%MRMEMO-W-UNSDOCTYP, unsupported document type
-MRMEMO-I-GIU_GIDMTDP, document profile operand
-MRMEMO-I-GIU_GIDMT, document unit
----- end of exception message 
ALLUNP          ALL$UNP_DOCPROFIL             3557        000001F4   001F38EE
ALLUNP          ALL$UNP_DOCUMENT_UNIT         3652        00000050   001F39C0
ALLUNP          ALL$UNP_GIU_TO_MSGITMLST      3859        000000E6   001F3B93
SRVACT          SRV$ACT_R                     5172        000000A2   001EB591
SRVDSP          SRV$DSP_FSM                   3423        000002A6   001E342A
SRVMMO          SRV$MMO_ONE_LIFE              4376        000001EF   001E03BF
SRVMMO          SRV$MMO_MAIN                  4208        00000017   001E01C3
                                                          00239BAE   00239BAE
KOTERM          KOTERM                         804        00000039   002375A2
                                                          00239B89   00239B89
KODOC           KODOC                         1768        00000097   002347E4
                                                          00239B89   00239B89
                                                          0026537D   0026537D
ADA$ELAB_DDS    ADA$ELAB_DDS                              0000000E   001C0C0E
                                                          00239B89   00239B89
    

    Well, according to the traceback from the log file, the patch (the
    one in note 5.21) is definitely *not* installed in this server.

    Check that the patch is installed. What is the output from:

      $ run/debug SYS$SYSTEM:MRMSRV
      DBG> set module ALLUNP
      DBG> ex/instr ALL$UNP_DOCPROFIL+1A5

    If the patch is installed, you get:

      MOVZBL   B^02(R6),R0

    If the patch is not installed, you get:

      TSTB     B^02(R6)

    If the patch really seems to be installed, you are probably not running
    the right image. One thing that might play games with you is INSTALL. If
    MRMSRV.EXE is installed as a known image, you will not run the new version
    created by PATCH unless you use INSTALL to REPLACE the image after 
    patching. You can use e.g. SHOW DEV/FILE to find out exactly what instance
    of MRMSRV.EXE that you are running. 

    Anders