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

Conference csc32::consolemanager

Title:POLYCENTER Console Manager
Notice:Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:CSC32::BUTTERWORTH
Created:Thu Aug 06 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1541
Total number of notes:6564

471.0. "/DIRECTORY=NL: and ALL don't work" by BSS::LIND (Jim Lind; 592-4099 CX03-1/N14 CNMC-West) Thu Nov 10 1994 19:54

    We have noted the following problem with the ARCHIVE command
    
    	$ CONSOLE ARCHIVE ALL /DIRECTORY=NL: /KEEP=24
    
    If the /DIRECTORY=NL: is specified, the log file is cleaned (left with
    ZERO log data) regardless of the /KEEP or /BEFORE qualifier
    specifications.  What's worse, as specified, the ARCHIVE file is 
    not created either ... all data is LOST.
    
    If the /DIRECTORY specifies a non-null device/directory, then the
    ARCHIVE commands behave as expected.
    
    If the ARCHIVE node specified is ALL, no systems are archived.
    The online help indicates that if ALL is used for the node name,
    all systems should be archived.  This is NOT how it actually works.
    
    Jim Lind
T.RTitleUserPersonal
Name
DateLines
471.1CSC32::BUTTERWORTHGun Control is a steady hand.Thu Nov 10 1994 22:0011
    >What's worse, as specified, the ARCHIVE file is
    >    not created either ... all data is LOST.
    
    Granted there is a problem here but if you archive data to the NL:
    device via /DIRECTORY=NL: then it's going to be lost. Period. What did
    you expect to happen? of course the /KEEP qualifier should have been
    honored and that is definitely a problem. There was more than 24 hours
    of data in the logfile I hope????
    
    Regs,
      Dan
471.2LOG data lost tooBSS::LINDJim Lind; 592-4099 CX03-1/N14 CNMC-WestTue Nov 22 1994 22:197
    Yes, there was more than 24 hours of data in the log file.
    
    We, of course, understand that sending data to the NL: device
    was expected to loose the archive data.  Point is, the log file
    was cleaned also ... ALL data was lost, not just archive data.
    
    Jim Lind
471.3Since when was NL: a directory.OPG::SIMONMon Nov 28 1994 12:579
Hi,
    the reason this occurs is that NL: is not a valid system directory. 
The current way archive works is to produce temporary files in the specified
directory both for the archived bit of the data and for what will become the new
log files. As NL: is not a directory the files do not exist and when the archive
exits ALL the data is gone.


(Section 4.5.1, pg 4-10  You cannot archive to a NON disk device)
471.4CSC32::BUTTERWORTHGun Control is a steady hand.Mon Nov 28 1994 18:4317
    Simon,
      Actuall it is more basic than that even since th NL: device is *the*
    bitbucket in VMS however your explanation did turn on the light. I
    would like to see the following change:
    
    Check the specified device to see if it's a disk device. If it
    isn't then output a message saying so and abort the archive. Since these
    are stream-LF files we could also store them on a files-11 mounted
    tape I would think. If I get time I'd like to test it and see how it
    works.
    
    Regs,
      Dan
    
    
    
    
471.5OPG::PHILIPAnd through the square window...Mon Nov 28 1994 21:1611
Dan,

  Dont spend too much time "working" on this as the code for Archive
  for V2.0 is just about all sewn up, it works differently than today, is
  more reliable and gets around this particular problem.

  And before you ask, no we cant retofit it to V1.5, too many changes would 
  be required.

Cheers,
Phil