[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

896.0. "Slow PCM V1.6 " by 58633::FERRO (Rick Ferro) Thu Jul 27 1995 12:59

    My customer has three sites and we run mission-critical applications
    (gambling software). Two of the sites are linked as one cluster using
    BRS over T3 lines.
    
    We have been using VCS V1.4 on VMS V6.1 and because of the slow echo
    problem on the consoles we are now evaluating PCM V1.6 on VMS V6.1.
    There are however two problems. First, we need the failover capability
    that we had with VCS since, at each of the three sites we have two
    VAXstation 4000-90 workstations to handle the VCS. Second and somewhat
    more critical is the fact that the screens seem to react very slowly.
    
    It took me forever to edit one of the site screens because of the slow
    response. There is nothing else running on the stations. Also when we
    go from one site screen to the other it seems to forever. 
    
    I put DECps on one station to try and ascertain what the problem is but
    to no avail. CPU utilization seems to be none, memory utilization (80
    MB) does not increase and the disks are idle. What is the problem.
    
    Does the software recreate the LAT devices every time I close the
    screen and open it again ? I've tried increasing some of the PQL
    parameters that deal with MOTIF (DECwindows V1.2-3) but the response is
    not any better.
    
    Can someone help ?

T.R Title User Personal
Name Date Lines

896.1 29067::BUTTERWORTH Gun Control is a steady hand. Thu Jul 27 1995 15:04 45

T.R	Title	User	Personal Name	Date	Lines
896.1		29067::BUTTERWORTH	Gun Control is a steady hand.	`Thu Jul 27 1995 15:04`	45
	> We have been using VCS V1.4 on VMS V6.1 and because of the slow echo > problem on the consoles we are now evaluating PCM V1.6 on VMS V6.1. > There are however two problems. First, we need the failover capability > that we had with VCS since, at each of the three sites we have two > VAXstation 4000-90 workstations to handle the VCS. The failover capability that you speak of was really a side effect of the way LAT works when LAT devices are set /QUEUED. VCS never had any failover designed into it. Now, you really could setup somehting similar with PCM. If you start PCM on a "primary" it will assume control of the service nodes. When you start PCM on the secondary it will be unable to open the lines and it will reattempt to open the lines every 150 seconds. SO if the primary fails, the maxtime it would ever take for the secndary to open the lines would be 150 seconds. I will also tell you that this value is tuneable but it is unsupported to do so. Lastly, the groundwork for real failover has been done for PCM but it is doubtful that you will ever see it. >Second and somewhat more critical is the fact that the screens seem to >react very slowly. >It took me forever to edit one of the site screens because of the slow >response. There is nothing else running on the stations. Also when we >go from one site screen to the other it seems to forever. I'm assuming you are talking about the C3. A problem was found by some local folks that sounds similar to yours. They discovered that if anyone has drawn any vertical lines that the C3's repsonse to any input is very slow as you have described. If you have any vertical lines, delete them and see how it goes. > Does the software recreate the LAT devices every time I close the > screen and open it again ? No. This will happne if you issue CONSOLE RECONFIG or if you restart the software. How are the character cell interfaces working, i.e., is the response good if you do CONSOLE CONNECT node-name from a decterm? REgards, Dan

>    We have been using VCS V1.4 on VMS V6.1 and because of the slow echo
>   problem on the consoles we are now evaluating PCM V1.6 on VMS V6.1.
>    There are however two problems. First, we need the failover capability
>    that we had with VCS since, at each of the three sites we have two
>    VAXstation 4000-90 workstations to handle the VCS. 
    
    The failover capability that you speak of was really a side effect of
    the way LAT works when LAT devices are set /QUEUED. VCS *never* had any
    failover designed into it. 
    
    Now, you really could setup somehting similar with PCM. If you start
    PCM on a "primary" it will assume control of the service nodes. When
    you start PCM on the secondary it will be unable to open the lines and
    it will reattempt to open the lines every 150 seconds. SO if the
    primary fails, the maxtime it would ever take for the secndary to open
    the lines would be 150 seconds. I will also tell you that this value is
    tuneable but *it is unsupported to do so*.
    
    Lastly, the groundwork for real failover has been done for PCM but it is
    doubtful that you will ever see it. 
    
    >Second and somewhat more critical is the fact that the screens seem to 
    >react very slowly.
    
    >It took me forever to edit one of the site screens because of the slow
    >response. There is nothing else running on the stations. Also when we
    >go from one site screen to the other it seems to forever. 
    
    I'm assuming you are talking about the C3. A problem was found by some
    local folks that sounds similar to yours. They discovered that if
    anyone has drawn any vertical lines that the C3's repsonse to any input
    is very slow as you have described. If you have any vertical lines,
    delete them and see how it goes.
    
>    Does the software recreate the LAT devices every time I close the
>    screen and open it again ?
    
    No. This will happne if you issue CONSOLE RECONFIG or if you restart
    the software.
    
    How are the character cell interfaces working, i.e., is the response
    good if you do CONSOLE CONNECT node-name from a decterm?
    
    REgards,
       Dan