[Info-vax] Infoserver 150

[Jan-Erik Soderholm]

Paul Sture wrote 2012-10-20 19:01:
> In article <5082a622$0$6453$c3e8da3$dbd57e7 at news.astraweb.com>,
>   JF Mezei <jfmezei.spamnot at vaxination.ca> wrote:
>
>> Question about MOP booting and Infoservers:
>>
>> It is/was my understanding that when VMS serves a MOP request from
>> another VMS host, it appends extra information to the specificed load
>> file (such as the SYSGEN paremeters applicable to that architecture)
>
> I honestly don't know.  When I was running an Alpha cluster with PWS
> satellites, all I saw was that they went to the correct root on the
> system disk to get the SYSGEN parameters and startup files.
>
>> I don't remember how terminal server configs were stored. Were they on
>> non volatile memory on a server like DECserver 200 ? Or were they copied
>> back to the MOP host to be appended to the load file ? (I just realised
>> how far this info is for me , last time I played with a decserver was in
>> early 1990s).
>
> There was a bit of DCL available which could dump the non-volatile
> settings from a DECserver to your VMS system.  If you didn't run that, a
> replacement DECserver meant you got to reconfigure it from scratch.
>
> IIRC it wasn't a particularly elegant bit of DC L, but it did the job.
>


It "simply" parsed the output from a series of SHOW SERVER and SHOW PORT
commands and created a file with the relevant DEFINE SERVER/PORT commands
that you later could run against a replacement DECserver.

Jan-Erik.



>> When it comes to an Infoserver, does it provide the exact same
>> capabilities in terms of appending information to the load file served
>> by the MOP server ?
>
> Pass.
>