Conference csc32::consolemanager

Hi Michael,

	Mmmm...  Could you please be a little more specific as
	your use of "terms" is confusing.  

    
>    A customer has got some problems with PCM (so he refuses to switch
>    from VCS)
>    
	You should remind him of "supportability" issues.  After 
	Jan '97 customers will be required to purchase special
	"prior version" contracts and only specified versions of the OS
	AND certain Layered Products will be included.  I'm not sure if
	VCS will be one of them.

>    a) When the screen logging events of a node is destroyed
>    	(e.g. show HSJ000)
>       CTRL-W doen't work anymore to restore the mask

	o  Are you referring to the Event List Window that is
	   brought up when the C3 is started or about Mult-Line
	   or Single-Shot event pop-ups?

	o  What do you mean by "destoyed"?  Is the customer
	   double-clicking on an Event to show the event 
	   context?  

	o  What does "restore the mask" mean?  Are you referring
	   to the event context?

    
>    b) when searching for keywords in the files, the search is done
>       CASE_SENSITIVE what is very unlikely for VMS and makes it real
>       hard finding texts if you don't know how they are written 
>       down exactly.

	I "think" you are referring to "EXTRACT"ing logfile data.  
	Would you please provide an example of the command that 
	the customer is using.

Dennis 

    Hi!
    
    a) CTRL-W Problem:
    
    	There are several ways to find out it doesn't work
    
    	1) Console monitor: SET TIME OFF
    
    		Clears the screen, CTRL-W doen't work. Only Priv/Next
    		builds up screen again
    	2) Console monitor: view hsj000
    
    		Coming events shift the bold status bar at the bottom
    		higher. After hitting the Cursor up sometimes (not
    		always) you can get a status where you see 2 lines
    		with the COMMAND> prompt.
    		The next event destroys (overwrites) the bold
    		status bar and CTRL-W doesn't work (sorry there is no
    		absolute way to reproduce this problem)
    
    		Maybe the problem of the problems with the screen buildup
    		result from the change to 48 lines per page, but however
    		CTRL-W doesn't seem to work in CONSOLE MONITOR at all!!
    
    	b) Whats about the case sensitivity of the COMMAND> FIND TEXT
    	   command ?
    
    
    
    	c) There is no way to convince the customer to grade up to the
    	   console monitor at this time.
    
    	   Installing PCM from the CD leaves you with a definatly 
    	   useless piece of software. After applying the latest
    	   MUP you can start using some parts of PCM.
    	   But even if you get the latest MUP it wan't be as
    	   reliable as VCS (even if unsupported) and
    	   does lack many of the features VCS had (prog. funktionkeys,..) 
    
    							thanks
    							Michael

Michael,

	Are we talking "PCM" or "VCS".  If it's PCM - then what version
are you running on?  If it's VCS - it going to be V1.4 with "CSCPAT_1055"
on V5.5-2...  full-stop.

Dennis 

    Hi!
    
    PCM (VCS) is running on a VMS V6.2 system.
    This notesentry shouldn't be used to find out why to use VCS no 
    longer.
    The simplest way to get the customer to grade up is to get PCM
    flieing without problems
    
    thanks
    Michael

    Hi!
    
    Now I've found my old notesentry (I thought that I've asked this
    question some time ago). It's entry # 915.
    
    In reply 4 is stated that the CNTRL_W isn't checked in V1.5
    Is this still the case?
    When will it estimately be fixed?
    
    thanks
    Michael