Conference csc32::consolemanager

    Bob,
    
       Probabily not, although I'm not sure what you mean by 'no image'. 
    Do you mean the main GUI for Console Manager? Did you double click on
    the PCM icon?  By doing so, you should at least get the C3 GUI for 
    Console Manager. From there, you must populate the database for PCM
    with valid node name and terminal server ports, etc.
    
    Let us know how you get on. Contact Larry TOOK::Wellington here in LKG for
    additional assistance. He's done some interesting integration.
    
    Dave
                                                    

  Hi,

   Usually there is some sort of image or picture which depicts the action
  of the ICON Box on the Tools Bar Window of PolyCenter Netview. The C3 app
  does in fact launch on a double click, which leads to...will PCM ever
  have drag and drop. Where whatever entity is in current context can be
  "dragged" and "dropped" onto the PCM ICON Box on the Tools Bar Window of
  PolyCenter Netview?

  OBTW: Thanks for the pointer to Larry.

  Bob

    Bob,
    
       The interface to PVN was done towards the end of the development
    cycle and so not all of what we wanted to do was done. Since there is
    only one option when you drag and drop, it's difficult to imagine what 
    the option should be. Connecting to the console would be a logical
    first choice. Larry has set up PNV so that the console connect option
    appears on the PNV popup menu when you click on the system icon. 
    This seems like the correct approach. To be really slick, we would need 
    to add another option to the PCM command line connect option, 
    'console connect/interface = decw', so that if the user did not have 
    access, a message window would appear stating teh reason why. 
    Perhaps it could be incorporated in into a shell script. If the PCM 
    connect command failed, the exit status would indicate so and then the 
    shell script could fire off another window which would create a message box
    indicating the reason why the connect was rejected. Looks like I'm 
    getting off on a tanget and starting to think aloud. To get back to your 
    main point, we're just starting to work on the next version of PCM. 
    Look for a tighter integration with PVN in the next release.
    
    Dave
    

re: -2
	I've installed Console manager on an OSF/1 2.0B Sable system with
	PNV 2.1A and the toolbar icon for console manager does appear.
	What you could check is that the xbm file hasn't been corrupted
	use a tool such as 'xv' to view the file 
	(/usr/opt/DCR110/examples/CM_Icon.xbm)
	outside of PNV just to check it's ok.

	Though I must say that I've got a different problem with 1.5
	currently..

re: -1
	
	I've also setup this up  of using the IpMap of PNV to 
	connect to registered Console Manager systems. The onlookers
	love it ! I've rigged it up so that I'm using Console Manager
	that's running on an Ultrix system and invoking it using remote
	shell (rsh) to start a decterm session back to $DISPLAY . I've done
	 this for a whole host of other Applications (Hubwatch, and WNT
	  based applications )

	A couple of problems can occur though:

	1) As you say, If the system is not registered
	   then you won't see the output result. If I quickly see a 
	   DECterm flash up and then disappear then I know that
	   system wasn't registered... :^(

	2) When PNV does its IP autotopology and your using bind
	   you'll find part of the selection name also includes the domain
	   name ( e.g reo.dec.com)

	  So it might be easier to have the machines registered in the
	  PCM database including domain name. This of course is
	  a load of bull sh*t if you are using the PDM map to connect to
	  your consoles.

	   I guess the another solution would be to have a script that
	   strips off characters at the first '.' and beyond..

	Maybe correct way is a  PcmMap application, Map containing all 
	Console Manager Icons is required ? 

	All these Maps... which one do you use and which ones telling
	the truth about its current state of operation !!

 jka

    >	All these Maps... which one do you use and which ones telling
    >	the truth about its current state of operation !!

    
    Good question and we probabily haven't heard the end of this one.
    I suppose the logical choice would be PNV because of it's ability to 
    launch applications. The only downside that I can see at this point is
    it's complexity and may be difficult for some users to get a grip on.
    Also, it's possibe to feed PVN with events from PCM and have the
    appropriate icon change color.
    
    Dave

 Hi,

  As stated in .0, I have V1.5 of CM installed. I
  did find the bitmap "CM_Icon.xbm" mentioned in .4,
  however, it was contained in "/usr/opt/DCR150".

  Okay. Now that I've found the bitmap image for CM,
  (thank you) which PNV directory does it belong in? 
  Also, does a "pnv -config" need to be performed as
  is required when adding a symbol bitmap ICON?
 

 Bob

 Ok bob.. you're getting there... sorry if didn't go the whole hog at first..

 Well basically the xbm should stay where it is, you'll find a file in 
 the /usr/OV/registration/C directory called 'console'. This file
 basically contains all "giblets" for getting the Bitmap/Menu options  etc in 
 to PNV.

 The entry in the "Tool" part is incorrect which is why you are seeing the
 blank. It currently reads as if you have V1.1 of console manager.

 If you edit the file (BTW make sure that the file is writeable ) and change 
 the line:

   Icon Bitmap "/usr/opt/DCR110/examples/CM_Icon.xbm";

 to:

   Icon Bitmap "/usr/opt/DCR150/examples/CM_Icon.xbm";

 Also whilest you're there change the line above it which reads:

   Command "/usr/opt/DCR110/examples/console_Launch_Net ...... (extra chars)

 to:

   Command "/usr/opt/DCR150/examples/console_Launch_Net .....(extra chars )

 Someone should QAR this ?

 Stop PNV and then restart it and then you should see the icon.

 Justyn

Ok,
   you can all line up to beat me. I forgot to make the changes for the V1.5 kit
and the pointers in the registration file were based on V1.1.

Sorry about that one I shall make sure it does not happen again.

Cheers Simon....

� you can all line up to beat me. I forgot to make the changes for the V1.5 kit
� and the pointers in the registration file were based on V1.1.
 
 just think... Tall person flogged to death by Chicken Tika Rolls..

 Major headlines..

 jka

    Simon,
     
      Don't be so hard on yourself. Thank you for investigating Justyn.
    
      BTW: Two customers, Chemical Bank and Fordam University, liked
           what they saw. They both stated that drag and drop ICON
           launch should do a direct console connect. Hope this helps.
    
    Bob