[Info-vax] Cutting down on routing nodes
CY
christery at gmail.com
Mon Aug 3 16:54:29 EDT 2009
> Hmmm...
> There must be something that prevents the procedure to go to that branch.
> What computer model are you using in this case?
> $ SHOW CPU
>
> What kind of DECnet license do you have registered?
> $ SHOW LICENSE
>
> What DECnet version do you have installed?
> $ MC NCP SHOW EXEC CHAR- Dölj citerad text -
>
> - Visa citerad text -
Huvvä illta (aorry my finnish is a bit poor, as is the english, but
bare with me)
We concluded at work, that I run FOE at the new desingated (spellled
something like that) router wont cut it due to lic problems, its a
830c IA64 or something running OVMS 8.... H1 something, dont got that
in my head, and no I cant just "set executor" to routing IV as the
package is not insstalled (o that is my thoughts) so I will live
without it, trying a nice dcl hack when I get the time to see other
nodes... answering to set host or something..
Upgrading the alpha productiondata DW(oh yes got licences for that) to
router "again" (router put to sleep at alpha conversion -99) is not in
my gameplan, want to make it easy to comprehend who/what is doing
what, it took that role many years ago because the PDP was lagging.
Now its out of the q.
now got enough CPU to run anything everywhere, but want order in the
functions...
And the alpha is going IA64 as soon as they get the float problem
fixed, (HP) so the thing it is a package of decnet phase iv problem
that I am having...
and as we solved it by saying, we dont need one, problem solved ;)
Will try that with decnet accounts, will be 5 min or work..., and ncp
storing all MOP calls (as I read the manual) might help.
Hyvvä yöta Kari.
//CY
More information about the Info-vax
mailing list