| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 6238.1 | | EDSCLU::MENDEL | Welcome to the next baselevel | Mon Jul 10 1995 14:45 | 14 |
| 6238.2 | more details | NECSC::OKOLITA | | Tue Jul 11 1995 15:27 | 19 |
| 6238.3 | | EDSCLU::MENDEL | Welcome to the next baselevel | Wed Jul 12 1995 11:19 | 42 |
| 6238.4 | ncl example? | HOTAIR::SIMON | Hugs Welcome Anytime! | Fri May 02 1997 14:21 | 15 |
| I have a customer who needs to generate a cmip file. He upgraded
to decnet/osi sometime after his last cmip file was generated and
did not include DNS. I explained he needed it and when he called
the Decnet team, he was told he need a license for DNS but they were no
longer available for V6.x of OpenVMS so he'd have to upgrade to V7 and
buy a license... He was not happy. It looks like V2.1 of the domain
gateway will fix his problem but in the meantime, maybe he can use
the .-1 workaround since that kit is not available yet.
Has anyone set up an ncl file to define the known towers? If so,
could you explain the commands or include an example?
Thanks for any help
Denise Simon
|
| 6238.5 | Hand craft the NCL | EDSCLU::GARROD | IBM Interconnect Engineering | Mon May 05 1997 12:07 | 8 |
| Re .-1
Yes it will be fixed in V2.1. The AlphaVMS loadhost kit has now been
submitted to the SSB. The VAXVMS one will be shortly. In the meantime
do as .-1 recommends ie hand craft the tower definitions. Look at an
old NCL file to see their format.
Dave
|
| 6238.6 | ncl example? | HOTAIR::SIMON | Hugs Welcome Anytime! | Mon May 05 1997 12:39 | 1 |
| Does anyone have an old ncl file they can post as an example?
|
| 6238.7 | no luck | HOTAIR::SIMON | Hugs Welcome Anytime! | Mon May 05 1997 18:17 | 22 |
| I had the customer look at his old .ncl files and obtain the create
a file with the create node known tower command in it for later
specification in the configuration utility as recommended in .3.
He tried to run the snapu5$configure procedure and when it asked
for gateway nodename, he got:
%SNAPU5-I-NSLOOKUP, Name Server lookup for node .DNA_NodeSynonym.snast1
%SNAPU5-E-GWYNOTFND, Gateway node name not found
(This is the original problem)
I had him execute the ncl create node...tower... command and then
try and run SNAPU5$CONFIGURE again. Still, the same error occurred.
So,it looks like the .3 workaround won't work. Is the customer stuck
waiting for 2.1 to be released?
Thanks
Denise Simon
|
| 6238.8 | Try this | EDSCLU::GARROD | IBM Interconnect Engineering | Mon May 05 1997 18:55 | 20 |
| Re .-1
You need to bypass the configuration step and just do the
compile ie:
@SYS$MANAGER:SNAPU5$COMPILE xxx.NCL
where xxx is the name of the NCL file previously created. Make sure
the NCL file doesn't have any nodename specification in it of the form:
YYY:etc
ie the YYY:
If DECdns type names are not in the NCL file the compiler shouldn't
complain.
Dave
Dave
|
| 6238.9 | trying | HOTAIR::SIMON | Hugs Welcome Anytime! | Tue May 06 1997 11:14 | 1 |
| Customer will try this and I will post the results. Thanks.
|