Conference csc32::consolemanager

>3) Not related to V1.5-006 specifically, I am getting the error "Failed to
>   dearchive log for system admin - No archived or live data available" when
>   I give the command "cons extr admin /since=xxx/before=xxx" for any period
>   that has been archived. The command will work fine for any unarchived data.
>   I looked in the CONSOLE$ARCHIVE directory and verified that there are
>   files there for the periods I would like.
    
    If your archive location is a sub-directory then this is a known issue
    that was discovered too late to make the MUP. When I say a
    sub-directory I mean a path such as this:
    
    PCM_DISK:[PCM.ARCHIVE]
    
    and the path is either entered in the config as above or you use a
    logical-name that *is not* a concelaed device logical. The archive
    fails to correctly parse the path. The workaround is to use a top-level
    directory for the archive location or to use a concealed device
    logical in the following example. Note that I use the logical
    CONSOLE$ARCHIVE as it's intuitive. You don't necessarily have to use it
    as long as you plug the correct logical into the config database.
    
    1. Using the config editor, plug in a logical- name for the archive 
       location.   Again we are using CONSOLE$ARCHIVE for this example.
    
    2. Place these commands in CONSOLE$PRIVATE_SETUP.COM. Note that
       anything in lower-case means you have to fill in the appropriate
       value for your site:
    
       A. DEFINE/TABLE=CONSOLE$LOGICAL_NAMES CONSOLE$ARCHIVE_ROOT -
             disk:[dir.]/TRANS=CONCEALED
    
       B. DEFINE/TABLE=CONSOLE$LOGICAL_NAMES CONSOLE$ARCHIVE -
             CONSOLE$ARCHIVE_ROOT:[sub-dir]
    
>4) Related to (3), how would I view data that has previously been archived
>   within the monitor interface? I have tried the "REVIEW node" command 
>   followed by "TOP", but this does not take me back past the last archive 
>   time. I assume that one I get (3) working this will too, but I would like
>   confirmation that this could be performed from within the monitor interface.
    
    As soon as you resolve item 3 above, this will work.

	

    re .1
    
    Thank you for the reply. I set up CONSOLE$ARCHIVE using the concealed
    logical and it works fine! This resolves questions 3 and 4.
    
    Any ideas on 1 and 2?
    
    					Thank you again,
    							...... Vern.

    I can speculate on number 1. The fact that you see a disconnect event
    is one of timing due to the lag between the controller daemon
    signalling that someone disconnected and ENS delivering it to you.
    During this lag, you have returned to the Monitor's Command: prompt and 
    your event "tag" line was cleared. In other words, the disconnect
    event was delivered *after* your "event tag" line was cleared.
    The other possibility is that Conmon doesn;t process the work request
    to disply the event until after the tag line is cleared.
    
    I can't answer number 2 as I'm not the project leader but merely
    PCM hacker-at-large. ;-}
    
    Regs,
      Dan

    Hi Dan!
    
    re .3
    
    Yes, that does appear to describe what is occurring. In notes 431.2 and
    431.4, Phil describes what appears to be a fix that was in a patch he
    provided. That patch worked fine, removing all events for a system once
    you disconnect from it. However, it appears that patch did not make its
    way into the full MUP.
    
    Perhaps Phil or Simon could shed some light on this.
    
    As for the VIEW request: that was a request based on comments I
    recieved from the operations staff who use PCM constantly. Having VIEW
    clear events would greatly improve the value they get from PCM during
    the high-volume backup sessions.
    
    				Thanks for your responses, Dan!
    						............... Vern.

Vern,

  The fix is indeed in the MUP, it could be that other changes/fixes have
  caused the "problem" to reappear!

  Sorry about this, I will try and take another look at this for the next
  patch kit, although I dont know when that will be yet.

Cheers,
Phil

    Hi Phil!
    
    No need to apologize. I'm glad to hear that it hasn't been forgotten
    and I'll look forward to the next patch!
    						Thank you,
    							........ Vern.