[Info-vax] Howto make OpenVMS remember "SET CONFIGURATION MAP"

[Paul Sture]

On 2017-07-18, Marco Beishuizen <mbeis.vms at xs4all.nl> wrote:
> On Tue, 18 Jul 2017, the wise oswald.knoppers--- via Info-vax wrote:
>
>> Do you have a logical tcpip$configuration defined? Maybe it's defined 
>> too late in the startup sequence.
>
> No, no logical defined.
>
>> Do you see your map settings with a 'tcpip show configuration map' 
>> before and after reboot?
>
> Map settings are only there when done manually (both "MAP" and "SET 
> CONFIGURATION MAP"). After a reboot, settings are gone and have to be set 
> manually again. I know "MAP" is supposed to work this way, but the "SET 
> CONFIGURATION MAP" command is to make it permanently. Except in my case it 
> isn't permanent.
>

Depending on version (all of them?), TCP/IP Services isn't very good at
understanding clusters.

It also has version 1 hard coded for the filenames in various places, so
e.g. restoring from a backup using /NEW_VERSION will leave version 2 or
greater, waiting around to be ignored.

Is your system clustered?  If not, was it previously a member of a
cluster?

What does the following give?

$ set def sys$system
$ dir/da/siz=all tcpip*.dat

Look for

a) stuff in SYS$SPECIFIC which is getting picked up in one place
   but not another.
b) TCPIP*.DAT filenames with version number greater than 1

FWIW on my non-clustered VAX (running under SimH), all my TCPIP*.DAT
files are in SYS$COMMON:[SYSEXE], and are version 1.

-- 
Everybody has a testing environment. Some people are lucky enough to
have a totally separate environment to run production in.