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

Conference iosg::all-in-1_v30

Title:	OLD ALL-IN-1 (tm) Support Conference
Notice:	Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:	IOSG::PYE

Created:	Thu Jan 30 1992
Last Modified:	Tue Jan 23 1996
Last Successful Update:	Fri Jun 06 1997
Number of topics:	4343
Total number of notes:	18308

977.0. "Switch Logs - clarification ..." by TAV02::CHAIM (Semper ubi Sub ubi .....) Thu Jul 02 1992 18:22

A customer has described the following behavior using SL (Swith Logs), and I
have confirmed the exact same behavior on my test ALL-IN-1 V2.4 system:

1. Both the MTI*.LOG are renamed to MTI*.BAK however NEW files are not created 
   immediately. I am assuming that this is NOT a problem, and they will be
   created the moment they are required, although the documentation does seem 
   to imply that thet are opened immediately by SL

2. If there are multiple MTI*.LOG files, and the user requests to delete any
   previous versions (answers Y to the question), then he expects any 
   older versions to be deleted. In reality, none of the older versions are 
   deleted.

   I agree that the question answerd DOES imply this. I have looked in the 
   EMLOGCTRL.COM which is actually executed and used DCL verification from
   TRACE. Both these confirm that ONLY the .BAK files are going to be
   purged. Is this the intended behavior?

   BTW, there is a slight bug. If for whatever reason, there do not exist 
   either an actual copy of MTILOG.LOG or MTIERR.LOG, then the corresponding
   old_traffic_log or old_error_log symbol will be empty and the
   PURGE/NOLOG/KEEP=2 'old..' command will in actuality purge the entire 
   directory - this I am sure was not intended.

Thanks,

Cb.

T.R Title User Personal
Name Date Lines

977.1 SL - a few features AIMTEC::WICKS_A DEC Mail Works for ME sometimes Thu Jul 02 1992 21:04 27

T.R	Title	User	Personal Name	Date	Lines
977.1	SL - a few features	AIMTEC::WICKS_A	DEC Mail Works for ME sometimes	`Thu Jul 02 1992 21:04`	27
	Chaim, That's how it's worked for a long time (since at least v2.1). There used to be an open bug on SL putting out the same message to the screen twice that got closed but not fixed during v3.0 development!! take a look at the GOLD_W buffer at it says MTIERROR.LOG renamed to MTIERROR.BAK twice this is due to some over entusiastic cut-and-paste when the file was I18Ned take a look below and you'll see what went wrong: $! oa "OA DISPLAY ''error_log' renamed to ''old_error_log'" $ oa "OA GET OA$DISPLAY=""''error_log'"" OA$_EM_ERRNAM ""''old_error_log'""" $ ..... ! oa "OA DISPLAY ''traffic_log' renamed to ''old_traffic_log'" $ oa "OA GET OA$DISPLAY=""''error_log'"" OA$_EM_ERRNAM ""''old_error_log'""" $ SPR time! the other ones you report also appear to be there on v3.0 regards, Andrew.D.Wicks (who changed EMLOGCTRL but not that time)

    Chaim,
    
    That's how it's worked for a long time (since at least v2.1). There
    used to be an open bug on SL putting out the same message to the screen
    twice that got closed but not fixed during v3.0 development!! 
    
    take a look at the GOLD_W buffer at it says
    MTIERROR.LOG renamed to MTIERROR.BAK twice this is due to some over
    entusiastic cut-and-paste when the file was I18Ned take a look below and
    you'll see what went wrong:
    
    $! oa "OA DISPLAY ''error_log' renamed to ''old_error_log'"
    $ oa "OA GET OA$DISPLAY=""''error_log'"" OA$_EM_ERRNAM
    ""''old_error_log'"""
    $
    .....
    
    ! oa "OA DISPLAY ''traffic_log' renamed to ''old_traffic_log'"
    $ oa "OA GET OA$DISPLAY=""''error_log'"" OA$_EM_ERRNAM
    ""''old_error_log'"""
    $
    
    SPR time! the other ones you report also appear to be there on v3.0
    
    regards,
    
    Andrew.D.Wicks (who changed EMLOGCTRL but not that time)