[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

1476.0. "icons not changing colour for certain machines PCM 1.6-308" by COMICS::HAWLEYI (668 - the neighbour of the beast!) Wed Jan 29 1997 01:41

One of our big customers over here has been seeing a niggly problem for some
time that has us beat, so i thought i'd throw it open to the PCM universe to see
if we can get some more ideas!

when the customer does a connect to console the icon for that machine turns
green. only on some machines it doesnt, it stays white. what foxes me, is that
the machines are using the exactly the same scans and events. They are grouped
into a scan profile called IIS and the machines IIS1-6 all use the same scans,
yet only IIS5 and 6 have the problem.

Ive recently upgraded this system from ECO 1 to 1.6-308 but the problem remained.

My main question is, what turns the icons green in the first place? I assume its
a console manager internal event?


can anyone help?


thanks,

Ian Hawley.
T.RTitleUserPersonal
Name
DateLines
1476.1CSC32::BUTTERWORTHGun Control is a steady hand.Wed Jan 29 1997 12:3018
    >My main question is, what turns the icons green in the first place? I
    >assume its a console manager internal event?
    
    Thats exactly correct. It's an internal event. Now, if you have a
    Multi-Line Window running thats setup to receive all events you
    should see all Consolemanager internal events there. Do you?
    
    You might also have a peripheral Icon occluding the node icon or
    there's somehting wierd in the CONSOLE$C3.DAT file (.consolec3rc on
    DUnix). I would recommend that you rename or delete all of these in 
    the users login dir, start the C3 and see what happens. If the 
    effected systems icons start working correctly then turn on edit mode
    and reconfig the screen and save it. Now restart the C3 and again check
    for proper function. if it fails again then I would want to see
    the C3 options file as you've found a bug.
    
    Regs,
      Dan
1476.2.consolec3rcCOMICS::HAWLEYI668 - the neighbour of the beast!Thu Jan 30 1997 09:29141
Dan,

we are going to test this tomorrow. The internal events ARE being seen on the
multi-line window, its just that pesky icon wont change colour! :-)
I'm going to post the .consolec3rc file here now anyway, ive had it a while and
couldnt see anything untoward, but hey, i wasnt sure what i was looking for! :-)

!
! C3 datafile
!

HEADER:
    VERSION: V1.6-125
    X: 225
    Y: 197
    WIDTH: 409
    HEIGHT: 242
    PANE1_HEIGHT: 114
    PANE2_HEIGHT: 242
    HSCROLL: 20
    VSCROLL: 0
    BACKGROUND: #CACAAAAA9191
    SYSTEM_FOREGROUND: #000000000000
    PERIPHERAL_FOREGROUND: #000000000000
    GROUP_FOREGROUND: #000000000000
    AUTOSTART EVENT LIST: Y
    ICONIFY C3 AT STARTUP: N
    CRITICAL_COLOR: #FFFF00000000
    CRITICAL_BELL: 0
    CRITICAL_VOLUME: 1
    MAJOR_COLOR: #FFFF0000FFFF
    MAJOR_BELL: 0
    MAJOR_VOLUME: 1
    MINOR_COLOR: #FFFFA5A50000
    MINOR_BELL: 0
    MINOR_VOLUME: 1
    WARN_COLOR: #FFFFFFFF0000
    WARN_BELL: 0
    WARN_VOLUME: 1
    CLEAR_COLOR: #0000FFFF0000
    CLEAR_BELL: 0
    CLEAR_VOLUME: 1
    IND_COLOR: #ADADD8D8E6E6
    IND_BELL: 1
    IND_VOLUME: 1
    KEEP_HIGHEST_PRIORITY: YES
    ENS_TIMER: 30
    SYSTEM_DLICK_OPTION: EVENT HISTORY
END:
MAIN:
    BACKGROUND: #CACAAAAA9191
    PADB_X: 225
    PADB_Y: 197
    WIDTH: 409
    HEIGHT: 242
    LINE: 176,105,176,105,1,#000000000000
    LINE: 176,105,176,105,1,#000000000000
    LINE: 58,116,59,116,1,#000000000000
    LINE: 0,0,56,68,1,#000000000000
    LINE: 345,61,345,61,1,#000000000000
    LINE: 345,61,344,61,1,#000000000000
    LINE: 355,60,355,60,1,#000000000000
END:

GROUP:
    NAME: GIGASwitches
    LABEL_PLACEMENT: b
    BACKGROUND: #FFFFFFFFFFFF
    X: 195
    Y: 20
    PADB_X: 500
    PADB_Y: 52
    WIDTH: 182
    HEIGHT: 217
    SYSTEM: GIGASwitch-downstream,GigaSwitch.xbm,10,30,P,G,E,W,n,b, , , 
    SYSTEM: GIGASwitch-upstream,GigaSwitch.xbm,95,30,P,G,E,W,n,b, , , 
END:

GROUP:
    NAME: Video
    LABEL_PLACEMENT: b
    BACKGROUND: #FFFFFFFFFFFF
    X: 330
    Y: 20
    PADB_X: 16
    PADB_Y: 42
    WIDTH: 483
    HEIGHT: 353
    SYSTEM: IIS1,DEC_4000.xbm,180,92,P,G,E,W,n,b, , , 
    SYSTEM: IIS2,DEC_4000.xbm,250,92,P,G,E,W,n,b, , , 
    SYSTEM: IIS3,DEC_4000.xbm,320,92,P,G,E,W,n,b, , , 
    SYSTEM: IIS4,DEC_4000.xbm,390,92,P,G,E,W,n,b, , , 
    SYSTEM: IIS5,DEC_4000.xbm,460,92,P,G,E,W,n,b, , , 
    SYSTEM: MCSBU1,DEC_4000.xbm,290,262,P,G,E,W,n,b, , , 
    SYSTEM: MCSBU2,DEC_4000.xbm,358,262,P,G,E,W,n,b, , , 
    SYSTEM: SMU1,DEC_4000.xbm,290,172,P,G,E,W,n,b, , , 
    SYSTEM: SMU2,DEC_4000.xbm,360,172,P,G,E,W,n,b, , , 
    SYSTEM: SAC,DEC_3000.xbm,440,211,P,G,E,W,n,b, , , 
    SYSTEM: NCG,DEC_4000.xbm,210,212,P,G,E,W,n,b, , , 
    TEXT: 
170,42,#FFFF00000000,-adobe-courier-bold-o-normal--18-180-75-75-m-110-iso8859-1,
Westminster Cable Video Server
    SYSTEM: Control,DECstation_5000.xbm,556,201,P,G,E,W,n,b, , , 
    SYSTEM: IIS6,DEC_4000.xbm,530,92,P,G,E,W,n,b, , , 
    LINE: 386,224,386,224,1,#000000000000
    LINE: 427,-11,428,-11,1,#000000000000
    LINE: 356,323,355,322,1,#000000000000
    LINE: 399,326,399,326,1,#000000000000
    LINE: 318,323,318,324,1,#000000000000
    LINE: 282,323,282,323,1,#000000000000
    LINE: 363,311,363,311,1,#000000000000
    LINE: 446,260,446,263,1,#000000000000
    LINE: 453,254,453,254,1,#000000000000
    LINE: 453,254,453,254,1,#000000000000
    LINE: 342,-139,342,-139,1,#000000000000
    LINE: 0,0,340,144,1,#000000000000
    LINE: 0,0,343,150,1,#000000000000
END:

GROUP:
    NAME: hubs
    LABEL_PLACEMENT: b
    BACKGROUND: #FFFFFFFFFFFF
    X: 45
    Y: 20
    PADB_X: 575
    PADB_Y: 241
    WIDTH: 313
    HEIGHT: 354
    SYSTEM: hub1,DEChub_900.xbm,15,40,P,G,E,W,n,b, , , 
    SYSTEM: hub2,DEChub_900.xbm,90,40,P,G,E,W,n,b, , , 
    SYSTEM: hub3,DEChub_900.xbm,165,40,P,G,E,W,n,b, , , 
    SYSTEM: hub4,DEChub_900.xbm,240,40,P,G,E,W,n,b, , , 
    SYSTEM: hub5,DEChub_900.xbm,15,130,P,G,E,W,n,b, , , 
    SYSTEM: hub6,DEChub_900.xbm,90,130,P,G,E,W,n,b, , , 
    SYSTEM: hub7,DEChub_900.xbm,165,130,P,G,E,W,n,b, , , 
    SYSTEM: hub8,DEChub_900.xbm,240,130,P,G,E,W,n,b, , , 
    SYSTEM: hub9,DEChub_900.xbm,135,205,P,G,E,W,n,b, , , 
    LINE: -66,-138,-66,-138,1,#000000000000
    LINE: -66,-138,-66,-138,1,#000000000000
END:
1476.3This took a year to find...WOTVAX::WATSONRLambs... so cute... but so tasty !Fri Jan 31 1997 06:5015
Hi,

   you haven't changed any of the 'standard' PCM Cmgr event definitions have
you ? We've found that, using the "CMgr Connect" event as an example, by
changing the 'class' from "CONSOLEmanager" to "Polycenter", we saw exactly the
effect you have.

   We noticed that, on a system with multiple controller processes, systems
controlled by the first controller would exhibit colour changes on connects,
but systems on subsequent controllers wouldn't. Putting the Cmgr events back
to standard definitions fixed the problem.

Just a thought.

Ross
1476.4CSC32::BUTTERWORTHGun Control is a steady hand.Fri Jan 31 1997 12:5210
    Re -1.
    
    WOW! I would never expect changing the class name to cause that
    problem! C3 proccesses connect to special listeners and these listeners
    receive all events. I suspect something is amiss in the C3 code.
    
    Thats for the info Ross and execllent work by the way!
    
    Regs,
      Dan
1476.5sorry, i mean, IS this the event in question?COMICS::HAWLEYI668 - the neighbour of the beast!Wed Feb 12 1997 09:0019
Ross/Dan,

this is the event in question:

ADD_EVENT:
    NAME: CMgr Connect
    INFO: User has connected to CONSOLEmanager
    TEXT: User has connected to CONSOLEmanager
    CLASS: CONSOLE
    SUB_SYSTEM: CM Internal
    REGULAR_EXPRESSION: N
    START: 1
    COUNT: 1
    PRIORITY: CLEAR
END:


Ian.
1476.6CSC32::BUTTERWORTHGun Control is a steady hand.Wed Feb 12 1997 12:136
    Thats the one!! Take a look at the class field. It's not what it
    should be. Change the class to CONSOLEmanager and see if it works.
    If it does, please IPMT this!!
    
    Regs,
      Dan
1476.7COMICS::HAWLEYI668 - the neighbour of the beast!Thu Feb 13 1997 08:5811
I changed the class to CONSOLEmanager and saved the database but it still didnt
go green when connecting. It doesnt seem to tell the eventlist that its
disconnecting from the node either which leads me to believe that perhaps ALL
the internal events are set up improperly. certainly all the events have class:
CONSOLE and not CONSOLEmanager. apart from trashing their config file completely
and starting again i dont know where to turn! :-)

thanks,

Ian Hawley.
1476.8CSC32::BUTTERWORTHGun Control is a steady hand.Thu Feb 13 1997 11:486
    Did you remember to do a reconfigure after making the change? I would
    recommend that you change the class on all of them and see if it has
    any effect. ENS is obvioulsy working or you wouldn't get any events.
    
    Regs,
      Dan
1476.9COMICS::HAWLEYI668 - the neighbour of the beast!Fri Feb 14 1997 02:478
yeah, we reconfigured...i'm going to edit his config file myself and re-import
it. unfortunately, i'm on Sun training for a week so I wont get chance till
after that :-( 


thanks,

Ian.