On Monday, 07/06/2009 at 01:52 EDT, "Frank M. Ramaekers" <[email protected]> wrote: > I'm attempting to setup a caching name server, but when the VM is logged > on, I get a rc of -9 and not much of an explaination: > > DTCRUN1021R To cancel Domain Name server startup, type any non-blank > character > and press ENTER. To continue startup, just press ENTER. > > DTCRUN1011E Server started at 11:26:43 on 6 Jul 2009 (Monday) > DTCRUN1011E Running "NSMAIN" > 11:26:46 main: VM TCP/IP Name Server Level 310 > : > 11:26:49 NsInitPm: Using * as RSCS name > > main: error -9 beginning TCP/IP service > DTCRUN1015I Server ended with RC=-9 at 11:26:49 on 6 Jul 2009 (Monday) > DTCRUN1019I Server will not be logged off because you are connected > > Ideas?
To answer your specific question, error -9 can be found in the TCP/IP Programmer's Ref. It is in Appendix B, Pascal Return Codes. It means that VMCF communications failed to the TCPIP stack. The name of the stack is coming from TCPIP DATA, so make sure you don't have a bogus TCPIP DATA laying around where NAMESRV can see it. [In a later post, you indicated you fixed the problem, but you didn't say how.] You appear to be running VM/ESA 2.3 (FL310), a release so old that the source code has been buried in the back yard in a coffee tin. There have been a LOT of fixes since then. To Frank and others: I recommend that you NOT expend effort to deploy a name server (caching-only or otherwise) on VM TCP/IP. Given the number of burned-out light bulbs, broken windows, and rusted pipes, we have decided to bring in the demoltion crew. NAMESERV is going to slip silently into that Good Night. Just point NSINTERADDR to the same nameserver you point everyone else to. With fast servers and networks, the latency for the DNS lookup won't be an issue. If your DNS lookup rate is high enough to make an on-board DNS server worthwhile, then Dr. Boyes' suggestion to run a Linux guest is the way to go. Alan Altmark z/VM Development IBM Endicott
