[Info-vax] Tertiary VMB?

[H Vlems]

On 14 jan, 15:46, JF Mezei <jfmezei.spam... at vaxination.ca> wrote:
> H Vlems wrote:
> > $ mc ncp list node jodium char
>
> > Node Permanent Characteristics as of 10-APR-2005 08:44:48
>
> > Remote node =   1.6 (JODIUM)
>
> > Service circuit          = SVA-0
> > Hardware address         = 08-00-2B-07-7A-68
> > Tertiary loader          = SYS$SYSTEM:TERTIARY_VMB.EXE
> > Load Assist Agent        = SYS$SHARE:NISCS_LAA.EXE
> > Load Assist Parameter    = SYS$SYSDEVICE:<SYS10.>
>
> Most interesting. HELP SET NODE shows there is a secondary and tertiary
> loader paparemeters. And interesting that it has NISCS_LAA.EXE instead
> of NISCS_LOAD.EXE.
>
> If tertiary_vmb.exe is specified as a parameter in the NCP database, it
> would explain why there is no mention of it in any of the .EXEs in
> SYS$COMMON:
>
> But in LANCP, there is no such thing as secondary and tertiary, just the
> one file to be fed. (but  I think both would seem to know to package
> that first file along with the VAXVMSSYS.PAR and the cluster authorise
> file).
>
> Perhaps the LANCP environment uses a more evolved NISCS_LOAD.EXE which
> doesn't require the tertiary one ?

JF
when you add a satellite to a cluster, you're asked whether DECnet or
LANCP is used.
I guess that DECnet uses NISCS_LOAD.EXE while LANCP probably uses
NISCS_LAA.EXE.
Hans