| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4100.1 | Does MANAGE/ENTERPRISE work in the registration command file? | TOOK::FIGWER | Ulla Figwer LKG2-2/T2 x226-7858 | Wed Nov 18 1992 13:58 | 28 |
|
Hello,
It looks like you may have discovered a conflict. If so,
that explains why you encountered DCL errors when executing
the Autoconfiguration registration command file. It would
not explain why your Autoconfiguration DECterm went away.
If you edit the Autoconfiguration registration command file
(mcc_<domain>_registration.com in the working directory
for the domain) to read "$ MANAGE/ENTERPRISE" rather than
"$ MANAGE/ENTER" and then choose the "Registration Only"
option for that domain do you get better results?
Please let us know. If so, I will file a QAR which states
that the registration command file should be generated with
the full MANAGE/ENTERPRISE command. And does the DECterm
stay around?
In the future, it is possible to gather Autoconfiguration data
as a separate step from registration. Choose the "Discovery Only"
option. Once discovery is complete, you can follow the same
steps as outlined above to register the nodes found.
Thanks,
Ulla Figwer
|
| 4100.2 | no different....... | CSDNET::DICASTRO | jet ski jockey | Wed Nov 18 1992 14:35 | 16 |
|
Ulla, thank you for your input....
I edited sys$sysroot:[sysmgr.dna4.lmo]mcc_lmo__registration.com
to say manger/enterprise, however it then failed on
\enterprise\ then \on\ then \on\ then \register\ etc.....
The aoutoconfig window gets 3 or 4 dcl errors before it disappears.
I have been trying to see what the other are, but cant keep it on
the screen long enough. Any other ideas ?
There are a slew of other command files that fail, I will get a list
and post it, this is unusual.....
Your help is appreciated/
|
| 4100.3 | found the offending command file(s) | AITMCC::SYSTEM | | Wed Nov 18 1992 15:10 | 43 |
| Here is what causes the autoconfig windows to disappear, I found the .com
file.
AITMCC_MGR>@AITMCC$DUA1:[MCC]MCC_IP_AUTOCONFIG.COM;2
Welcome to IP Autoconfiguration
Type '?' for Help or 'Q' to Quit, at any of the prompts.
Checking the namespace. This will take a moment. Please wait...
%DCL-W-NOQUAL, qualifiers not allowed - supply only verb and parameters
\ENTER\
%DCL-W-IVKEYW, unrecognized keyword - check validity and spelling
\MCC\
%DCL-W-IVKEYW, unrecognized keyword - check validity and spelling
Then *POOF* the window is gone
or :
AITMCC_MGR>@MCC_WAN4_AUTOCONFIG.COM;4
Welcome to DECnet Phase IV Autoconfiguration
Type '?' for Help or 'Q' to Quit, at any of the prompts.
Checking the namespace. This will take a moment. Please wait...
%DCL-W-NOQUAL, qualifiers not allowed - supply only verb and parameters
\ENTER\
%DCL-W-IVKEYW, unrecognized keyword - check validity and spelling
\MCC\
%DCL-W-IVKEYW, unrecognized keyword - check validity and spelling
\MCC\
same difference, unable to keep the window on the screen. In reference to the
basenote and the previous note regrding DCL, at one time this autoconfig
window would stay open however ALL the registration scripts failed w/ DCL
errors.
any more ideas ?
Thank you
|
| 4100.4 | Edit the two .COM files as well: MANAGE/ENTERPRISE | TOOK::FIGWER | Ulla Figwer LKG2-2/T2 x226-7858 | Wed Nov 18 1992 18:16 | 25 |
|
Hmmm.... I'm still surprised that the window disappears (and
even more surprised that at one time it did not), but I
believe there is a similar workaround to get by this
problem.
If in fact there is a conflict with the command MANAGE/ENTER
(which it seems there is) then the Autoconfiguration scripts
will fail because they also issue the MANAGE/ENTER command
(in addition to the registration command files). This
is just what you are seeing.
If you edit MCC_IP_AUTOCONFIG.COM and MCC_WAN4_AUTOCONFIG.COM
(in MCC_COMMON) and replace MANAGE/ENTER with MANAGE/ENTERPRISE
(one instance per file) the scripts should work.
Better yet, you could disable prefix checking by editing both scripts
and commenting out the line "GOSUB check_prefixes". (There are some
cases where this is advisable, for instance if DNS$CONTROL program
is not present on your system.)
Hope this helps!
Ulla
|
| 4100.5 | Filed as QAR 00197 in MCC013_INT | TOOK::FIGWER | Ulla Figwer LKG2-2/T2 x226-7858 | Wed Nov 18 1992 18:43 | 3 |
|
Filed as QAR 00197 in MCCO13_INT
|
| 4100.6 | Maybe it's as simple as RTRN | TOOK::STRUTT | Management - the one word oxymoron | Tue Nov 24 1992 10:37 | 8 |
| Is it possible that you installed RSM after DECmcc and did not
follow the procedure outlined in the DECmcc release notes that
covers this case?
DECmcc and RSM share the same DCL verb - MANAGE
You need to update the DCL tables (refer to the DECmcc release notes
for the exact procedure), to allow MANAGE/ENTERPRISE to be
recognised as a command to invoke DECmcc.
|
| 4100.7 | | AITMCC::SYSTEM | | Tue Nov 24 1992 14:03 | 17 |
|
I'm the system manager working this issue with BOb DICastro. I updated
the DCL tables using the procedure in the MCC release notes and
that did not help. I went as far as rebuilding the entire system
from scratch and the problem reappeared. The workaround I used to
fix it was to setup a global symbol named MCC_DCL_FIX :== MANAGE/ENTER
Then I had to edit all the files in MCC_COMMON:*.COM and modify the
MANAGE/ENTER to MCC_DCL_FIX and it works fine.
The kit we are using was created using RSM however the MCCBMS012
was the last product installed. I know that RSM and MCC use the
same verb, but I can't figure out why MANAGE/ENTER and
MANAGE/ENTERPRISE fail to work.
Mark OToole
X296-5247
|