[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

857.0. "UNLOCK problem with V1.6" by BACHUS::WILLEMSG (Geert Willems MCS-Belgium) Fri Jul 07 1995 11:30

    
    
    
    	Hi,
    
    	OpenVMS AXP V6.1 , PCM V1.6(SBB kit)
    
    	UNLOCK problem.
    
    	When the customer tries to unlock a console via the C3, he sees
    	that the slot disappears. Then he exits/quits and does 'console c3'
    	and the slot appears again.
    	Console reconfig doesn't solve the problem.
    
    	The motive to unlock the system was :
    	Yesterday the Console Ctrl 01 crashed. The customer disabled this
    	particular system that was connected via this Console CTRL 01 in PCM .
    	Via the 'console c3' he sees the slot and so on ...
    	At the time the Console Ctrl 01 crashed there was an open
    	connection via PCM to this system.
    
    	I think it's somewhere related because the I asked him to connect 
    	to another system and try the UNLOCK. Works fine.
    
    
    	Any known problems with UNLOCK in some circumstances ?
    
    	Thanks in advance.
    
    	Rgds,
    
    	Geert 
T.RTitleUserPersonal
Name
DateLines
857.1PossiblyZENDIA::DBIGELOWInnovate, Integrate, EvaporateFri Jul 07 1995 15:2215
    Geert,
    
        There was one problem with the lock/unlock mechanism which we will 
    be in the next mup kit, but I'm not positive that it will fix this
    problem. 
    
    I can only guess that the master PCM controller process still thinks that 
    there is a valid connection. Do you know if the detached connection 
    process was still active? If so, you could try to 'stop/id=whatever' 
    the connected process and see if that happens. If that doesn't work, 
    the only alternative that I can think of is to restart PCM.
    
    Dave
    
    
857.2OPG::PHILIPAnd through the square window...Fri Jul 07 1995 15:2710
Geert,

  The problem is that the controller has crashed, but the details about the
  user who is connected to the system are still in shared memory, for the
  ECO, I have made sure that the shared memory values are cleared out at
  startup time (I did this for another problem, but it will fix yours too).
  However, to get this value cleared, you will need to restart PCM.

Cheers,
Phil
857.3BACHUS::WILLEMSGGeert Willems MCS-BelgiumFri Jul 07 1995 15:33109
    
    
    
	Hi Dave,Phil,
    
    	Thanks for the feedback. I will gave this info to the customer.
    	In the meantime I had this info from the customer.
    
    	Rgds,
    
    	Geert
    
    
CONS STAT    
=========
                       POLYCENTER Console Manager Summary
                                     Totals


Configured Systems:  43 User disabled:   4
Active Systems    :  39 (D:000 P:001 L:042 T:000)   Unreachable: 000
Active Users      :  11 (Connect/Monitor: 008 C3: 003 Event sources: 004)

CM pid ........: 000001D9 V1.6-100         Uptime:   0 23:08:04
ENS pid .......: 000001DA V1.6-100         Uptime:   0 23:08:04

Total bytes ...: 13.88M       (0)         Ave bps:   166.71
Total lines ...: 220.1K       (0)         Ave lpm:   158.55
Total events ..: 3978         (0)         Ave epm:     2.87
Total actions .: 6            (0)         Ave aph: < .01
Active actions : 4                 Failed actions : 0

   Crit: 119  Maj: 520  Min: 2198  Warn: 887  Clr: 254  Ind: 0



CONS STAT/ALL
=============

    ------SYSTEM------ ---PID--- STATE -BYTES- -LINES- EVENTS ------USER------
1   ALFA01             000001DB   LYE    37.6K     806      6
2   BCCNO3             000001DB   LYE       90       3    419
3   BDCNCC             000001DB   LYE    41.1K    1.2K     28
4   BOPRO1             000001DB   LYE     7.0K     161      8
5   BRSSAP             000001DB   LYE    16.5K     337      8
6   BRUOA2             000001DB   LYE   111.6K    3.4K      6
7   CDVMV1             000001DB   LYE    1.32M   35.2K    729
8   COV01              000001DB   LYE    30.7K     756      2
9   COV02              000001DB   LYE    3.29M   70.7K    781
10  COV03              000001DB   LYE   303.7K    6.1K   1.4K COV_OPER
11  COV04              000001DB   LYE    3.16M   64.0K    263
12  COV05              000001DB   LYE        0       0      5
13  C_BOSNCC           000001DB   LYE      284       4      7
14  C_FNXFE2           000001DB   LYE    39.7K     870     17
15  C_RCTNCC           000001DB   LN-      289       6      1 NCC_OPER
16  DEVNCC             000001DB   LYE    11.0K     367     16
17  EBW                00000000   LN-        0       0      0
18  FE_C               000001DC   LYE    1.75M     104      2
19  FE_G               000001DC   LYE        0       0      0
20  FE_M               000001DC   LYE   994.6K      79      2
21  FE_W               000001DC   LYE    1.36M     103      2
22  FE_Z               000001DC   LYE        0       0      0
23  FNXFE3             000001DC   LYE        0       0      0
24  FNXFE5             000001DC   LYE        0       0      0
25  HSC000             000001DC   LYE        0       0      0
26  HSC001             000001DC   LYE        0       0      0
27  HSJ02              000001DC   LYE        0       0      0
28  HSJ04              000001DC   LYE        0       0      0
29  HSJ07              000001DC   LYE        0       0      0
30  HSJ08              000001DC   LYE        0       0      0
31  INFOSE             000001DC   LYE        0       0      0
32  NETBR1             000001DC   LYE    46.7K     738      2 COV_OPER
33  NETBR2             000001DD   LYE    48.7K     763      4 COV_OPER
34  NETBR3             000001DD   LYE    58.3K    1.0K      4 COV_OPER
35  NETBR4             000001DD   LYE   278.3K    7.7K     31 COV_OPER
36  PCMAXA             00000000   LN-        0       0      0
37  PCMAXB             000001DD   PYE    16.3K     480    238
38  R204A              000001DD   LYE        0       0      0
39  SWIFTE             000001DD   LYE   470.5K   12.6K      0
40  SWIFTQ             000001DD   LYE        0       0      0
41  SWIFTR             000001DD   LYE   492.7K   12.5K      2
42  XSERVA             000001DD   LYE     5.8K     137      4
43  XSERVB             00000000   LN-        0       0      0

cons stat/system=c_rctncc
=========================

                       POLYCENTER Console Manager Summary
                                 System Details


System ............: C_RCTNCC
Enabled ...........: No
Line status .......: *** Disabled ***

In use by .........: NCC_OPER

Parent pid ........: 000001DB
Child Index .......: 1
Connection type ...: LAT

Logging device ....: 56% Full
Last Archive ......: None Performed

Lines of data .....: 6  Bytes: 289
Event total .......: 1

   Crit: 0  Maj: 0  Min: 0  Warn: 0  Clr: 1  Ind: 0