[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

165.0. "CONSOLE CONNECT problem" by BACHUS::WILLEMSG () Mon Jan 17 1994 13:33



	Hello,

	I need some help with PCM on OpenVms VAX.
	I have a VAXstation 4000-60 with VMS 6.0 and VCS1.4 .
    	VCS is down when I test with PCM.
	I tried to configure PCM on this system. I introduced
	one system (BRSSWS) in the configuration editor.
	
	The problem is that when I try to do a $CONSOLE CONNECT BRSSWS
	I get "Connection between line sensor and remote console has been lost".
	
	In the console$logfiles:CM_CONSOLEMANAGER.LOG I found:
	Unable to open console for system BRSSWS - %SYSTEM-F-ABORT, abort
	Unable to open console for system BRSSWS - %SYSTEM-F-ABORT, abort
	Unable to open console for system BRSSWS - %SYSTEM-F-ABORT, abort
	Unable to open console for system BRSSWS - %SYSTEM-F-ABORT, abort
	Unable to open console for system BRSSWS - %SYSTEM-F-ABORT, abort
	Unable to open console for system BRSSWS - %SYSTEM-F-ABORT, abort
	User SYSTEM connected to system BRSSWS
	User SYSTEM disconnected from system BRSSWS
	Console Manager has been shut down

	
CM EDIT> show system brssws
Full or Brief listing? [f=full, b=brief] (b): f
Output file (SYS$OUTPUT):
System Name         = BRSSWS
    Information     =
    Primary Host    = DBC083
    Failover Host   = DBC083
    Connection      = LAT (terminal server)
    Terminal Server = BRSS97
    Server Port     = LTA2000
    Scan Profile    = VMS 6400    VAX 6000 Model 400 Series VMS System Scan Prof
ile
    Icon filename   = VAX_6000.XBM
    Console line    = Enabled
    Logging is enabled, directory = CONSOLE$LOGFILES:


$ mc latcp sh port lta2000

Local Port Name:   _LTA2000:         Local Port Type:  Application (NonQueued)
Local Port State:  Inactive
Connected Link:

 Target Port Name:     VCS02            Actual Port Name:
 Target Node Name:     BRSS97           Actual Node Name:
 Target Service Name:                   Actual Service Name:


    	Any help is welcome.
    
    	Thanks in advance,
    
    	Geert
                                                
T.RTitleUserPersonal
Name
DateLines
165.1Items to checkOPG::SIMONMon Jan 17 1994 14:0025
Geert,

I think you have tried to copy what you do for VCS in setting up connection
details.

In the system entry in the PCM database theTerminal Server and Server Port 
attributes are the remote server name and port name. Yuo do not create the LTA
device PCM does that for you.

So I guess in your case the entry should look like:

System Name         = BRSSWS
    Information     =
    Primary Host    = DBC083
    Failover Host   = DBC083
    Connection      = LAT (terminal server)
    Terminal Server = BRSS97
    Server Port     = VCS02 
    Scan Profile    = VMS 6400    VAX 6000 Model 400 Series VMS System Scan Prof
ile
    Icon filename   = VAX_6000.XBM
    Console line    = Enabled
    Logging is enabled, directory = CONSOLE$LOGFILES:

Cheers SImon......
165.2found it !BACHUS::WILLEMSGMon Jan 17 1994 14:059
    
    
    	Found it. I changed the server port from LTA2000 in VCS02.
    	Is there in PCM a command procedure like VCS$LTA.COM ?
    	Can someone give more info on CONSOLE$DEBUG logical ?
    
    	Thanks,
    
    	Geert
165.3thanksBACHUS::WILLEMSGMon Jan 17 1994 14:168
    
    
    	Hi Phil,
    
    	PCM does it for me ? Ok, it works. But I don't have an LTA device
    	created. Nothing is seen ! 
    
    	Geert
165.4Show device l?ZENDIA::DBIGELOWInnovate, Integrate, EvaporateMon Jan 17 1994 14:406
    Geert,
    
        Did you use the 'Show device l' VMS command to show the lat
    devices? Also, do you have a valid license?
    
    Dave
165.5ThanksBACHUS::WILLEMSGMon Jan 17 1994 15:1078
    		
    Hi Dave,
    
    Yep, it's there. Just did the test via SDA :
    
    Process index: 0003   Name: Console Ctrl 01   Extended PID: 00007E83
    --------------------------------------------------------------------
    
    
                                Process active channels
                                -----------------------
    
    Channel  Window           Status        Device/file accessed
    -------  ------           ------        --------------------
      0010  00000000                        DKA300:
      0020  81EF9F80                       
    DKA300:[CONSOLE.IMAGES]CONSOLE$DAEMON.EXE;1
      0030  81EF7380                       
    DKA300:[VMS$COMMON.SYSLIB]SMGSHR.EXE;1 (section file)
      0040  81EF8600                       
    DKA300:[VMS$COMMON.SYSLIB]LIBRTL.EXE;2 (section file)
      0050  81EF6C80                       
    DKA300:[VMS$COMMON.SYSLIB]PTD$SERVICES_SHR.EXE;1 (section file)
      0060  81EFB540                       
    DKA300:[VMS$COMMON.SYSLIB]DECW$XLIBSHR.EXE;5 (section file)
      0070  81EF4480                       
    DKA300:[VMS$COMMON.SYSLIB]UVMTHRTL.EXE;2 (section file)
      0080  81EF88C0                       
    DKA300:[VMS$COMMON.SYSLIB]VAXCRTL.EXE;4 (section file)
      0090  81EF8C80                       
    DKA300:[VMS$COMMON.SYSLIB]CMA$TIS_SHR.EXE;1 (section file)
      00A0  81EF8DC0                       
    DKA300:[VMS$COMMON.SYSLIB]DECW$TRANSPORT_COMMON.EXE;1 (section file)
      00B0  81EF7040                       
    DKA300:[VMS$COMMON.SYSLIB]LBRSHR.EXE;2 (section file)
      00C0  81EFB2C0                       
    DKA300:[VMS$COMMON.SYSLIB]DECW$DXMLIBSHR.EXE;4 (section file)
      00D0  81EF6940                       
    DKA300:[VMS$COMMON.SYSLIB]DECW$DWTLIBSHR.EXE;4 (section file)
      00E0  81EF4BC0                       
    DKA300:[VMS$COMMON.SYSLIB]DECW$XMLIBSHR.EXE;4 (section file)
      00F0  81EF8BC0                       
    DKA300:[VMS$COMMON.SYSLIB]DECC$SHR.EXE;1 (section file)
      0100  00000000                        NLA0:
      0110  00000000                        MBA859:
      0120  00000000             Busy       MBA860:
      0130  00000000                        MBA861:
      0140  00000000             Busy       MBA862:
      0150  00000000             Busy       LTA5061:
      0160  81F8C400                       
    DKA300:[CONSOLE.LOG]CM_BRSSWS.LOG;1
      0170  81F33940                       
    DKA300:[CONSOLE.LOG]CM_BRSSWS.TIMES;1
      0180  81F32800                       
    DKA300:[CONSOLE.LOG]CM_BRSSWS.EVENTS;1
      0190  00000000             Busy       MBA863:
    
    
    
    ==>lta device is LTA5061:
    
$ sh dev lta5061/full
    
    Terminal LTA5061:, device type unknown, is online, record-oriented device,
    carriage control, device is busy.
    
    Error count                    0    Operations completed                 5
    Owner process  "Console Ctrl 01"    Owner UIC                     [SYSTEM]
    Owner process ID        00007E83    Dev Prot             S:RWPL,O:RWPL,G,W
    Reference count                1    Default buffer size                 80
    
    
    Yes. I have the POLY-CONSOLEMGR license active .
    
    
    Thanks,
    
    Geert