Conference cookie::sls

2198.0. "Bad logical OPCOM messages" by TROOA::TROU48::DINELEY () Fri Feb 14 1997 11:19

    Hello,
    
      I have just recently upgraded to SLS 2.8 on VMS 6.2 system. When I
    run the SLS$STARTUP everything seems to go ok, but I get a whole wack
    of opcom messages like:
    
    
    $ 
    %%%%%%%%%%%  OPCOM  14-FEB-1997 11:09:47.02  %%%%%%%%%%%
    Message from user SLS on CGOU04
    SLS$TAPMGRRQ, %SLS-E-BADLOGNAM, bad logical name
    DEFAULT_DCSC_EXPORT_MTYPE in ta
    ble LNM$SLS$VALUES
    
    $ 
    %%%%%%%%%%%  OPCOM  14-FEB-1997 11:09:47.32  %%%%%%%%%%%
    Message from user SLS on CGOU04
    SLS$TAPMGRRQ, -SYSTEM-F-NOLOGNAM, no logical name match
    
    
    
    %%%%%%%%%%%  OPCOM  14-FEB-1997 11:09:49.10  %%%%%%%%%%%
    Message from user SLS on CGOU04
    SLS$TAPMGRRQ, %SLS-E-BADLOGNAM, bad logical name DEFAULT_CAPACITY_1 in
    table LN
    M$SLS$VALUES
    
    $ 
    %%%%%%%%%%%  OPCOM  14-FEB-1997 11:09:49.10  %%%%%%%%%%%
    Message from user SLS on CGOU04
    SLS$TAPMGRRQ, -SYSTEM-F-NOLOGNAM, no logical name match
    
    $
    
    
    ...all the way to DEFAULT_CAPACITY_32 logical.
    
    
    Is this normal? What, if anything should be done?
    
    
    Thanks, Tim.
    
    

>Is this normal? What, if anything should be done?

No this is not normal.

Please post yout tapestart.com and the output from
show logical/table=lnm$sls$values default_*

\David