[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

1154.0. "TS AM Problem - ID802 Error" by PHLACT::BBRADBURY () Mon Jun 17 1991 12:02

While trying to register terminal servers with the TSAM, I experienced the
following problems:

1) Received the following error while using the command line interface:

   MCC-E-ID802  ERROR, error in ID802 value

   I thought it might be referring to the server address, but I have checked it
   multiple times.  I have also tried it with multiple servers.

2) I have also received "insufficient privilege" messages while trying to 
   register via the Iconic map.  I have the suggested privileges and my
   namespace is currently wide open.

I have been away from the product for awhile and the only thing that appears to
have changed is that the license for my SNMP AM expired.  I am working off
a 16Meg machine, I don't know if this would cause the problems.

Thanks in advance

Bob


T.RTitleUserPersonal
Name
DateLines
1154.1Can you supply more information?CHRISB::BRIENENDECmcc Bridge|Station|SNMP Management.Mon Jun 17 1991 13:314
Supplying the actual ascii text that generated the error (cut/paste the
Register command) and maybe listing the privs you have might help.

Have you tried enabling ALL PRIVs to see if the problem goes away?
1154.2SCRPIO::LIZBICKIMon Jun 17 1991 19:5911
   The ID802 error is not returned by the Terminal Server AM, but 
   rather by the FCL interface, when an invalid ethernet is specified
   as the server address.  If you are sure that you are specifying
   the correct address, it may be that you are omitting the comma
   between the Address argument and the Type argument (this will 
   confuse the FCL PM).

   With regards to the insufficient privilege message, do you have 
   write access to the TSAM MIR files (MCC_COMMON:MCC_TS_AM*MIR.DAT)?

1154.3Missing CommaPHLACT::BBRADBURYWed Jun 19 1991 19:0019
    By inserting the comma the ID802 error went away, but it seems that the
    word "SPAWN is being inserted into the command and causing an error.
    
    I also went looking for the TSAM MIR files and I could not even find
    them.  Any suggestions?
    
MCC> register terminal_server ds3s10 address 08-00-2b-12-66-68, type ds300
MCC>
                                 DECmcc Output                         ... More
                                          attempted operation

register terminal_server ds3s10 address = 08-00-2b-12-66-68  SPAWN TYPE = ds300
%MCC-E-ID802_ERROR, error in ID802 value

register terminal_server ds3s10 Address = 08-00-2b-12-66-68, SPAWN TYPE = DS300
%MCC-W-QUALUNKNOWN, qualifier is unknown: SPAWN
    

   
1154.4You may have a symbol definedNSSG::R_SPENCENets don't fail me now...Wed Jun 19 1991 19:1612
    Do you have a symbols defined?
    
    Try
    MCC> DISPLAY SYMBOL
    
    and see what you get. I expect you have a symbol for TYPE defined
    as SPAWN TYPE and it got you.
    
    Keep in mind that TYPE and MAIL actually ARE keywords in some FCL
    directives so be careful with symbols.
    
    s/rob
1154.5TYPE as SymbolPHLACT::BBRADBURYThu Jun 20 1991 20:376
    Thanks, Rob.  That fixed the problem.  TYPE was a symbol set up with
    the demo and the problem did not show up until I installed the TS AM.
    
    I am still working on the other problem.
    
    Bob
1154.6Privileges for TS AMPHLACT::BBRADBURYWed Jun 26 1991 11:568
    I solved my remaining problem, "No privilege for attempted operation"
    by giving the process all priv's.  I could not find in the
    documentation what privileges are required for operating the TS AM.
    Could someone state what the required privileges are?
    
    Thanks,
    
    Bob
1154.7TOOK::LIZBICKIWed Jun 26 1991 14:129
    Information on the privileges required to enable the TSAM software
    can be found in the TSAM Use guide, in the chapter on "Managing the
    Terminal Server AM Software", in the section on "Enabling and
    Disabling the Terminal Server AM Software".  I believe that
    it is also in the release notes.

				Lynne