[Info-vax] Distributed Applications, Hashgraph, Automation

[Stephen Hoffman]

On 2018-02-24 22:15:01 +0000, Kerry Main said:

>> 
>> -----Original Message-----
>> From: Info-vax [mailto:info-vax-bounces at rbnsn.com] On Behalf Of Craig 
>> A. Berry via Info-vax
>> Sent: February 24, 2018 4:33 PM
>> To: info-vax at rbnsn.com
>> Cc: Craig A. Berry <craigberry at nospam.mac.com>
>> Subject: Re: [Info-vax] Distributed Applications, Hashgraph, Automation
>> 
>> On 2/24/18 2:52 PM, Kerry Main wrote:
>>>> -----Original Message-----
>>>> From: Info-vax [mailto:info-vax-bounces at rbnsn.com] On Behalf Of Craig 
>>>> A. Berry via Info-vax
>>>> Sent: February 24, 2018 2:17 PM
>>>> To: info-vax at rbnsn.com
>>>> Cc: Craig A. Berry <craigberry at nospam.mac.com>
>>>> Subject: Re: [Info-vax] Distributed Applications, Hashgraph, Automation
>>> 
>>> Never been much of an issue if its just the OS (modparams) and TCPIP 
>>> (tcpip$config).
>> 
>> There is quite a bit more to it than that:
>> 
>> <http://h41379.www4.hpe.com/faq/vmsfaq_007.html#mgmt9>

That list is incomplete, too.  The host name(s) have been stored in 
various other spots since that list was created or other storage 
locations have been found.   This due to the complete lack of 
system-wide shared data for these and related details.  OpenVMS never 
really solved this problem, and deferred it to the applications, and 
the applications then all went their own unique ways, with their own 
unique interpretations, tools and methods for changing the name.  Which 
really makes creating a monolithic master... interesting.

> There are best practices when building a homogeneous environment.

Alas, OpenVMS nor layered products nor apps follow these (unpublished) 
practices....  The host name(s) of an OpenVMS server is a complete mess.



-- 
Pure Personal Opinion | HoffmanLabs LLC