Thanks Mike. We just copied the TCPIP DATA file to TCPMAINT.592 and that resolved the problem!
-----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mike Harding Sent: Monday, June 16, 2008 3:34 PM To: [email protected] Subject: Re: zVM 5.3 and DNS Where's your TCPIP DATA file? It names the TCPIP server, as well as the DNS servers to use. Mike Harding, Consultant/Specialist Enterprise Platform Services, Mainframe Engineering KP-IT Enterprise Engineering 925-926-3179 (8-473-3179) | E-Mail: [EMAIL PROTECTED] AIM: VMBearDad | Yahoo IM: mbhcpcvt Kaiser Service Credo: "Our cause is health. Our passion is service. We're here to make lives better." NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you. "Morris, Kevin J. (RET-DAY)" <[EMAIL PROTECTED]> Sent by: The IBM z/VM Operating System <[email protected]> 06/16/2008 11:53 AM Please respond to The IBM z/VM Operating System <[email protected]> To [email protected] cc Subject zVM 5.3 and DNS We recently installed zVM 5.3 onto our test VM LPAR (production is still 5.2) and encountered a strange problem in that TCPMAINT appears to be the only user that can resolve hostnames. OPERATOR, MAINT, other systems programmer CMS userids all get "Unknown host xxxxxx". Example: --- as user: TCPMAINT --- ping vm03 Ping Level 530: Pinging host VM03 (10.196.76.30). Enter #CP EXT to interrupt. PING: Ping #1 response took 0.001 seconds. Successes so far 1. --- as user: MAINT ------ ping vm03 DTCPIN0014E Unknown host VM03 Ready(00100); T=0.01/0.01 14:43:36 ping 10.196.76.30 Ping Level 530: Pinging host 10.196.76.30. Enter #CP EXT to interrupt. PING: Ping #1 response took 0.002 seconds. Successes so far 1. ------------------------- Has anyone else encountered this issue? We use RACF, but I don't see any error messages going to RACFVM or OPERATOR, so I don't think it is RACF related. Plus, when we IPL 5.2 on the test LPAR, it uses the same RACF database and we don't have this issue. Any ideas? Thanks, Kevin Morris Reed Elsevier - Technology Services zOS Systems Engineering
