[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

545.0. "Not creating LTA devices on cold start" by SEDOAS::CLIFFE_S () Fri Jan 06 1995 11:30

    Sorry to be a nuisence. My customer did their first cold start of their
    VAX that was migrated from VCS to PCM seemed to starup fine, with the
    C3 box etc. However PCM was unable to connect to any of the systems
    it was managing. Upon looking at the LTA devices in existance, only
    LTA0 existed. There are no print queues on this system. looking at
    systartup, the command to start LAT was unchanged at :- 
    $ @sys$startup:lat$startup -
                    SMVX53 -
                    /IDENT="V.C.S." -
                    /CONNECTIONS=BOTH -
       		  "" -
    
    PCM is started later in the SYSMAN phase of LPMAIN. I suspect that for
    some reason this is insuffiecient for the autoconnect feature to work.
    However, the workaround in the systartup to get it to work was to add
    the line :-
    
    @sys$manager:VCS_LAT_DEVICES.COM
    
    	I am not quite sure what difference running the com file first 
    makes, however the autoconnect feature works with this line added
    to systartup_vms.com
    
    
    			Answers on a postcard
    
    
    
    			Steve
T.RTitleUserPersonal
Name
DateLines
545.1OPG::PHILIPAnd through the square window...Fri Jan 06 1995 12:238
Steve,

  Does the customers LAT startup set the correct LAT groups for connecting
  to the terminal servers? If not, theres your reason, as the VCS command
  procedures did this for you.

Cheers,
Phil
545.2CSC32::BUTTERWORTHGun Control is a steady hand.Fri Jan 06 1995 20:2916
    If the problem isn't fixed by what Phil suggested then I suspect the 
    config database is setup so that the "connection type" field for the
    system records is setup to be "Direct" with the terminal device name
    set to be an LTA device and those LTA devices were created by the
    command procedure mentioned in the base note. If this is the case, this
    setup is incorrect for PCM. When PCM was designed, LATMaster had been
    released thus PCM can dynamically create it's own LTA ports at
    run-time. The correct way to set it up is to set the connection type
    to LAT and then fill in the terminal server node-name and 
    terminal server port name that each service node is connected to. 
    
    BTW, if it is group codes, then you can modify LAT$SYSTARTUP.COM
    to turn on the appropriate service group.
    
    Regs,
      Dan
545.3Easy when you know the answer45211::CLIFFE_STue Jan 10 1995 16:259
    Re -1 & -2
    
    	Yes!! what stars you are, all it needed was a LATCP command
    	to include group 1 ( easy when you know the answer)
    
    			Thank you
    
    
    			Steve Cliffe