[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

815.0. "VCS-I-SYNCHINITWAIT" by KERNEL::HORSNELL () Thu Jun 15 1995 10:46


       Hi,

       I have the following problem and hope someone can give some advice.

System : VAX 4000 VLC (24mb)
VMS version 5.5-2
VCS version 1.4

       The VCS system has stopped working, no h/w or s/w changes have been
       made. It worked ok until a reboot.

       When VCS is started the four processes (IODL,SCANNER,ELOG & ENS) appear
       to start ok, but when you try and do a

          $VCS COORD to invoke the C3 window, the following message is
      Displayed....

        $VCS-I-SYNCHINITWAIT, waiting for VCS$IODL to complete initialization

      It just seems to sit there and hang, you aren't returned back to $

      The VCS$IODL process is there and in a LEF state.

      Any suggestions

      Daryl Horsnell
      UK CSC

    
T.RTitleUserPersonal
Name
DateLines
815.1OPG::PHILIPAnd through the square window...Thu Jun 15 1995 10:5510
Daryl,

  This is not the VCS conference, your customer should upgrade to
  PCM, we neither have the time or resources to support VCS any more.

  However, I suggest that if it was working and now isnt then SOMETHING
  MUST have changed!!

Cheers,
Phil
815.2OK KERNEL::HORSNELLThu Jun 15 1995 11:0413
    
    
    Sorry,
    
    I did try NOTED::VCS, however this advised me to use PCM. I was unable
    to write to that conference.
    
    Oh well 
    
    Cheers
    
    Daryl
    
815.3OPG::PHILIPAnd through the square window...Thu Jun 15 1995 11:086
Daryl,

  It advised you to use the PCM product, not the conference.

Cheers,
Phil
815.4ZENDIA::DBIGELOWInnovate, Integrate, EvaporateThu Jun 15 1995 15:091
    You might make sure that the license has not expired.
815.5start with thisBACHUS::WILLEMSGGeert Willems MCS-BelgiumThu Jun 15 1995 18:2322
    
    
    	Hi Daryl,
    
    
    	Can you check the VCS logfiles. I mean in sys$manager you
    	have a 	VCS$IODL_OUTPUT.LOG (especially this one)
    		VCS$SCANNER_OUTPUT.LOG
    		VCS$ELOG_OUTPUT.LOG
    		VCS$ENS_OUTPUT.LOG
    
    	Another thing that you can do :
    	1)Stop VCS ($VCS SHUT)
    	2)Test all LTA ports (SET HOST/DTE LTAxxx). See if there is no
    	  problem with one of them.
    	3)Check also if there aren't two decserver with the same address.
    
    	Start with this.
    
    	Rgds,
    
    	Geert
815.6More than likely you have a hung server port.CSC32::BUTTERWORTHGun Control is a steady hand.Thu Jun 15 1995 18:3844
    More than likely the IODL is hanging on a connect to a server port.
    There is either an existing connection or the port never completed
    disconnect processing and is thus in a disconnecting state.
    
    Do the following to find the prot we are hung up on:
    
    $ ANA/SYSTEM
    SDA> SET PROC VCS$IODL
    SDA> SHO DEV/ADDRESS=@R5
    
    It should print out the name of an LTA device. Jot this down. Get out
    of SDA and do
    
    MCR LATCP
    LATCP> SHO PORT LTA-device-from-above
    
    Note the server name and port number. You will need to connect to this
    terminal server and find the port in question. If the customer did the
    sensible thing then ports will be named according to the their actual
    port number i.e., if the port is named VCS07 then the physical port is
    port 7. SO you would do
    
    Local> SHOW PORT 7 
    
    and verify the actual port name is correct. If it is then do
    
    Local> SHOW PORT 7 STATUS
    
    If the port shows connected it will tell you from where. See if there
    is a connection from somewhere other than the VCS engine. If there is
    then someone grabbed the port for another purpose. If there is no
    conencttion and the port is in say disconnecting state then do
    
    Local> LOGOUT PORT 7
    
    Bearin mind that most of the commands above are priviledged so your
    customer needs to know the priv'd password for the server and turn on
    priv's via 
    
    Local> SET PRIV
    
    Regards,
       Dan
    in a disconencting state. If 
815.7Thanks !!!KERNEL::HORSNELLTue Jun 20 1995 12:417
    
    Thanks, for all the suggestions.
    
    I'll checkout those details.
    
    Daryl