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

[Stephen Hoffman]

On 2017-07-16 10:37:57 +0000, Marco Beishuizen said:

> My Digital PWS is running OpenVMS 8.4, and I'm trying to set it up as 
> an NFS server. Everything seems to be working and the exported 
> filesystem is accessible from other systems.
> 
> Only thing is that after a reboot, I need to reenter the "SET 
> CONFIGURATION MAP" and "MAP" commands, because they are lost after a 
> reboot.
> 
> Is there a way to make OpenVMS remember the mappings?

SET CONFIGURATION MAP and SET CONFIGURATION NOMAP is supposed to be the 
permanent version of the MAP and UNMAP stuff.    Which implies you have 
either found a bug, that there's an error here that's being suppressed 
or some odd logical names, or there's something odd in the local 
configuration that's discarding or otherwise overwriting the NFS 
mapping.

Or maybe that the NFS services aren't being correctly auto-started, and 
are tossing some errors somewhere in a log file?   Some of the TCP/IP 
Services servers sort-of work, when there are errors in the particular 
service-specific startup procedures for the service or sometimes even 
when the service is not configured.  See if the NFS server log file 
provides any insights here, if you've not already looked there.   The 
NFS server chatter is often stored in SYS$SYSDEVICE:[TCPIP$NFS], but 
can be relocated elsewhere.   (Probably not for this particular case, 
but sometimes check for NFS errors on the remote end of the NFS mount 
too, as sometimes that can provide some insight into the failure.   
Sometimes client-side errors can also provide confusion, unfortunately.)

Obvious brute-force: implement and issue the MAP commands during each 
startup, after the NFS server has been started.


-- 
Pure Personal Opinion | HoffmanLabs LLC