[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

474.0. "Ctrl 01 process 'dies' after third DCL Connect" by CSC32::J_COFFEY () Fri Nov 11 1994 18:44

         
Hello,

I am working with a customer who is having the problem described below
with Polycenter Console Manager V1.5  and OpenVMS for VAX 6.1. 
Has anyone else seen this behavior?  We have not been able to reproduce
this here at the CSC.  The description was sent in via dsnlink by the
customer.  

Thanks in advance for any assistance.

Joanne Coffey
CSC32::J_COFFEY
CSC/CS
x24231



         
          On each of three DECterms (one at a time):
          
	    a) $CONSOLE CONNECT VIP062
            b) $CONSOLE CONNECT VIP064
            c) $CONSOLE CONNECT VIP015

The (c) command cleared the screen and stopped.  No other message or
display.  The (a) and (b) sessions went to "console monitor command mode"
and stated that:
        "Console Manager has been shut down
         Console Manager is not running - loading log file"


(a) and (b) do connect successfully.
If (c) never connects (the command is never issued), then
(a) and (b) continue to work.  They remain connected.
        


Here is the contents of the logfile after the process goes away.
---------------------------------------------------------------------------
ALGOMA_SCHNEI>type  CONSOLE_DAEMON_OUTPUT.LOG;6
$VFY = 0
$EXIT
$       SET MESSAGE /FACILITY /IDENTIFICATION /SEVERITY /TEXT
$       SET DEFAULT CONSOLE$TMP:
$       SET PROCESS /DUMP
$ RUN CONSOLE$IMAGE:CONSOLE$DAEMON.EXE
Console Manager shutting down at user request
  SYSTEM       job terminated at 27-OCT-1994 18:23:49.11

  Accounting information:
  Buffered I/O count:             106         Peak working set size:    1786
  Direct I/O count:                44         Peak page file size:     10239
  Page faults:                   1152         Mounted volumes:             0
  Charged CPU time:           0 00:00:00.54   Elapsed time:     0 00:04:33.26

    
    
    The Console Ctrl 01 'dies'.  The logfile above indicates that 
    the Console Manager has been shut down which is really not the
    case.
T.RTitleUserPersonal
Name		DateLines
474.1console status/allZENDIA::DBIGELOWInnovate, Integrate, EvaporateFri Nov 11 1994 19:1210
    Joanne,
    
       Not sure what's going on here. See if you can get some additional
    information from the customer. Have them '$console
    status/all/out=pcm_status.dat'. Somehow, it looks like a daemon
    connection problem with the terminal server. Also, they have enough
    license units, correct? Also, I take it that they have the latest patch
    kit?
    
    Dave
474.2BYTLM too low for ctrl 01 processCSC32::J_COFFEYFri Nov 11 1994 21:1721
    
    Dave,
    
    I was able to dialin while the customer reproduced the problem.  I 
    found that the Console Daemon process also 'dies' and the BYTLM 
    quota for the Console Ctrl 01 that goes away, gets depleted.  
    
    Increasing the quota on the the Daemon process in console$startup did
    not affect the quota(bytlm) for the Ctrl 01 process.  We ended up 
    increasing the PQL_xBYTLM quotas in SYSGEN to 500000.  When the console
    manager was restarted, and the 3 connections were made, bytlm for 
    the Ctrl 01 process began at 300000+ and went down to over 200000.  
    
    I will have to do a bit more investigating into how these processes
    are started and where they get their quotas from. 
    
    Thanks for the reply.
    
    Joanne Coffey
474.3Please keep us postedZENDIA::DBIGELOWInnovate, Integrate, EvaporateFri Nov 11 1994 22:0710
Joanne,

    There are a few other notes relating to quotas. 
They are 273.0 and 415.0.

Please let us know about your findings.

Cheers,

Dave
474.4CSC32::BUTTERWORTHGun Control is a steady hand.Mon Nov 14 1994 19:557
    Those quotas are hardcoded into the daemon image. Joanne, what
    is the value of SYSGEN param DEFMBXBUFQUO? The value of this param
    will effect PCM.
    
    Regs,
      Dan
474.5 DEFMBXBUFQUO is 8192CSC32::J_COFFEYThu Nov 17 1994 21:1723
    
    Dan,
    
    DEFMBXBUFQUO look like this on the customer's system:
    
    
    Parameter Name            Current    Default     Min.     Max.     Unit
    Dynamic
    --------------            -------    -------    -------  -------   ----
    -------
    DEFMBXBUFQUO                 8192       1056       256     64000 Bytes     
    
    
    How does it effect PCM?   If you like, Dan, we can take this out of the
    notes file since we both are in the CSC in Colorado.
    
    I am at 24231.
    
    Thanks.
    
    Joanne
474.6CSC32::BUTTERWORTHGun Control is a steady hand.Fri Nov 18 1994 17:464
    For temporary mailboxes it would indeed effect bytlm usage.
    
    Regs,
      Dan