[Info-vax] RPC and NFS Locking?

[Jan-Erik Soderholm]

Tim Ellis wrote 2012-03-09 11:36:
> We have a process which makes use of RPC calls to fetch data from a
> remote (non vms) server.  This process was originally built on an
> Alpha using OpenVMS 7.3-2 and TCPIP 5.4, and has worked without any
> problems for 2+years
>
> We recently migrated to a new VMS server running OpenVMS 8.4 and TCPIP
> 5.7 - We rebuilt and relinked the procedure under this version, and it
> runs for between 15 mins to 4 hours, then starts to fail.  Once it
> starts failing it seems to continue to do so unless one or other of
> the servers involved are rebooted.
>
> Running the executable built under OpenVMS 7.3-2 continues to work
> without displaying this problem.
>
> The error returned is JCI_SERVER: RPC: Remote system error -
> Connection refused
>
> My suspicion is that something on the new build is triggering NFS
> record locking, that is not called by the original build.  Since we
> don't make use of any other NFS services we don't have either STATD or
> LOCKD running, and the thought was that starting these processes might
> relieve the issue - however when I try running SYS$STARTUP:TCPIP
> $STATD_STARTUP I get the following error message
>
> %TCPIP-I-INFO, image SYS$SYSTEM:TCPIP$STATD.EXE installed
> %TCPIP-E-STARTERROR, error starting STATD service
> -TCPIP-W-NORECORD, information not found
> -RMS-E-RNF, record not found
> %TCPIP-E-STARTFAIL, failed to start TCPIP$STATD
> -TCPIP-E-ENABLERR, error enabling service
>
> Either the manual is not much help, or I'm looking in the wrong one
> (or the wrong place in the right one) as I can't see what record it is
> looking for.  Anyone able to help?

I do not know if STATD solves the actual problem, but in some cases
you can't run the STARTUP routines if you havn't done the "config"
in TCPIP$CONFIG.COM first. I noticed that there is an entry in
the "server" submenu "11 - LOCKD/STATD  Disabled Stopped".
This is on "V5.7 - ECO 3".

Jan-Erik.