[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

765.0. "Excursion with PCM" by ROM01::CHIARANTINI (Azucar negra!) Thu May 25 1995 13:40

    
    	<< Cross-posted in NOTED::EXCURSION >>

	I'd like to know if somebody experienced this or even if some 
good hints is flying around...

	The customer has POLYCENTER Console Manager v1.5.008 on a VAX 
OpenVMS system, connected via TCP/IP to a HP Vectra PC with eXcursion 
v1.2A-4. The majority of applications can be correctly used by 
excursion, but some commands of PCM seems to have terrible effects on 
the Excursion session. 

	For example, the CONNECT CONSOLE name, open an X window on the 
PC directly connected to the console of the system. If I open the 
Options pull-down menu and select General, the X window application 
disappear and the window get closed.

	Logging the events with the Excursion tools, the only strange 
thing I can see is just an

	Error reply sent to client 3, Request = QueryFont, Error = BadFont

	Differently from other instances where the font name was clearly 
shown (-adobe-courier-.....), in this case I don't know how to trap the 
font required. I tried with the -trap switch in the Xcursion icon, but I 
must tell I do not know how to read the .TRP files (I believed it was a 
Text file!).

	So, I cannot understand if it happens due to font problem or 
something related to the hw/sw configuration. The TCP/IP stack is a 
Microsoft one, and the TCPUTILS.INI shows numsockets=4, numthreads=32 
that sound enough to me. The Windows system offers 70% of system 
resources. DNETHeapsize in SYSTEM.INI is set to 64.

	The same function with previous product on VAX (VCS) worked 
properly. Unfortunately I can still think about many different ways to 
investigate: Vax  
processes, video drivers (HP monitor won't work in rel 3), better 
tuning... But maybe somebody experienced this or know of something that 
could help.

	If I could just know how to correctly trap and then read what is 
happening... 

    	Has PCM special new requests to X window servers?
    
    	Has anybody tried eXcursion with PCM?

	Thanks in advance,

		Dave
		Rome, Italy
T.RTitleUserPersonal
Name
DateLines
765.1PBUNIX::pgbAnd through the square window...Thu May 25 1995 13:5715
Dave,

  From what you have described, you are selecting an option on the 
  DECterm created by PCM, if this is the case, then I doubt that it is 
  directly a PCM problem! What happens if you create other DECterm 
  sessions with your eXcursion system as the server?

  I have eXcursion running on my PC and cannot reproduce your 
  problem.

  Maybe you have a UCX quota problem??

Cheers,
Phil

765.2do not think about DECtermROM01::CHIARANTINIAzucar negra!Thu May 25 1995 18:3519
    
    
    	Thanks for the suggestion, I'll try to have a look at UCX quota as
    well. I do not think anyway it is related to DECterm, because I just
    use DECterm (successfully) to launch the CONNECT CONSOLE myVAX command,
    than, after a while, the PCM let's pop up its window on my
    excursion/PC. This is due to PCM settings that re-route its output
    somewhere else.
    
    
    	So the window that get closed unwillingly seems to really belong
    to PCM. The problem could be: does it need extra
    resources/fonts/TCP sockets/... that, for example, were not required in
    former VCS ? More data on the net...between PCM an X server?
    
    	Thanks again, 
    
    
    		Dave