[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

3061.0. "TSAM uses circuit even if state -= off and hangs" by CLARID::PATEL (We'll get it right on the night) Fri May 22 1992 13:03

    related to 3022...

    The reason for hitting ^C was that the command 
     MCC> show terminal_Server e111s1 port * number  seemed to have hung,
    ie it did not complete even after 12 hrs.

    This problem was due to the fact that there was a circuit set on the
    node QNA-0 state off, the real circuit used on the system was SVA-0

    NOW, it appears that TSMAM takes the first circuit it finds and uses it
    as the service circuit... well that's a real bummer if the circuit is
    state off....  So, should the AM have realized that the circuit was off
    and use the next one in line ?

    Amrit
T.RTitleUserPersonal
Name		DateLines
3061.1Hung for some other reasonTOOK::FONSECAI heard it through the Grapevine...Fri May 22 1992 14:5230
Amrit-

The symptoms you are seeing must have been caused by some other problem.
From talking to the other developers here, and doing an experiment myself,
I successfully done several SHOW commands on a terminal server when the
only circuit listed for it was set to state off.

I've been told that the circuit needs to be state on only for up-line
dumps to occur successfully.

If you are having problems getting TSAM to enable and work, and have been doing
several enables/disables, and fooling with the TSAM system logicals, it
is possible to get TSAM wedged badly.

From FCL execute the command 
  MCC> DISABLE MCC 0 TERMSERVER_AM ABORT TRUE

Then from DCL level, verify that the detached process MCC_TS_AM_SRV no longer
exists on the system.  If it still does, stop it.  Then deassign the system
logical MCC_TS_AM_STATE, if that is still defined.

Verify that ALL users of TSAM have exited out of MCC, I would imagine this
includes disabling any rules which might be firing on terminal servers.

Then go back in and enable TSAM:
  MCC> ENABLE MCC 0 TERMSERVER_AM

I hope this helps...

-Dave
3061.2thanks -- all is well CLARID::PATELWe'll get it right on the nightFri May 22 1992 16:1417
    Maybe, I was not too clear.  The system I had is a VAXstation 3100 MDL
    76, it only has SVA device in it.  But, for some (unmentionable) reason
    a circuit QNA-0 got defined in NCP and set.  The state of this circuit
    was off.

    Now, when I ^C you see the attributes for the load and dump files, and
    you also see that the service circuit attribute was QNA-0... well
    looking at the help description of service circuit attribute, states
    that tsam will pick up the first circuit in the list.  May be if I
    defined the attribute to be {QNA-0,SVA-0} it may have worked.

    Having purged the 'erroneous' circuit entry out, and followed the steps
    you indicated all is working OK now -- many thanks
    
    Amrit