We've had a vaxstation 3100 boot node running VMS 7.1 up and running for several years. A couple of weeks ago one of the drives gave out so I replaced it. It took a number of attempts to get the scsi jumpers configured correctly, but now the system is up and running with the drive. However sometime during this process, Decnet seems to have quit working. Here's what I see: o Whenever I try to issue any commands from NCP the involve the volatile database, I get the error messages $NCP-W-OPEFAI, Operation Failure %SYSTEM-W-NOSUCHDEV, no such device available This happens for anything like Show Executor Char, show known circ, etc. If I issue commands involving the non-volatile database, like Defines, List Known Circ, etc., it works OK. (List Known Circ shows SVA-0 with a state On) o tcp/ip is up and working, so I know the network connection is OK. I can telnet or ftp into the Vax o If I issue the command Show Net, it shows the Decnet product with the correct node name and address. However if I try a Set Host 0 or Set Host <nodename>, I get the error %RMS-F-DEV, error in device name or inappropriate device type for operation I tried re-running netconfig but still get the same error Does anyone have any idea what may be causing this, what I could try to fix this, or where I could look for any assistance? Any help you can provide would be greatly appreciated. Thanks, Chris Musial

Chris, First, the OpenVMS web site is www.hp.com/go/openvms. There is a link to the HP maintained forums, including the OpenVMS forum, and to the complete OpenVMS documentation set. The DECnet documentation in PDF format is on-line at h71000.www7.hp.com/doc/decnet.html. ("NCP" is DECnet IV, not DECnet-Plus, and these have different document sets.) The errors you're getting sound like the software can't find some drive it's looking for. Maybe the replacement still isn't working properly, wasn't recognized as a disk by VMS, or wasn't mounted. What are the results of the command "$ Show Device DK"? That assumes the replaced drive is not the system disk, of course. There should be a mount command for it somewhere in your system startup procedure(s). If you gave the replacement a different volume label than the original, the mount command will fail. Maybe the volatile database didn't get initialized. Try entering "$@SYS$MANAGER:STARTNET" or "$ MCR NCP Set Known Nodes All" That's about the limit of my expertise! Good luck. Kelly

decnet likes to be first to the network resources , take down tcpip from a locally attached terminal/laptop, then start up decnet followed by tcpip. check that your decnet startup in systartup is correct and before tcpip startup.