T.R | Title | User | Personal Name | Date | Lines |
---|
1154.1 | Can you supply more information? | CHRISB::BRIENEN | DECmcc Bridge|Station|SNMP Management. | Mon Jun 17 1991 11:31 | 4 |
| 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.2 | | SCRPIO::LIZBICKI | | Mon Jun 17 1991 17:59 | 11 |
|
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.3 | Missing Comma | PHLACT::BBRADBURY | | Wed Jun 19 1991 17:00 | 19 |
| 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.4 | You may have a symbol defined | NSSG::R_SPENCE | Nets don't fail me now... | Wed Jun 19 1991 17:16 | 12 |
| 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.5 | TYPE as Symbol | PHLACT::BBRADBURY | | Thu Jun 20 1991 18:37 | 6 |
| 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.6 | Privileges for TS AM | PHLACT::BBRADBURY | | Wed Jun 26 1991 09:56 | 8 |
| 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.7 | | TOOK::LIZBICKI | | Wed Jun 26 1991 12:12 | 9 |
|
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
|