Hi Kevin,

On the other userids, are you linking TCPMAINT 592? All userids
attempting to use TCP/IP need to be able to see TCPIP DATA, which is
usually on TCPMAINT 592.

Peter

-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Morris, Kevin J. (RET-DAY)
Sent: June 16, 2008 14:54
To: IBMVM@LISTSERV.UARK.EDU
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


The information transmitted is intended only for the person or entity to which 
it is addressed and may contain confidential and/or privileged material.  Any 
review retransmission dissemination or other use of or taking any action in 
reliance upon this information by persons or entities other than the intended 
recipient or delegate is strictly prohibited.  If you received this in error 
please contact the sender and delete the material from any computer.  The 
integrity and security of this message cannot be guaranteed on the Internet.  
The sender accepts no liability for the content of this e-mail or for the 
consequences of any actions taken on the basis of information provided.  The 
recipient should check this e-mail and any attachments for the presence of 
viruses.  The sender accepts no liability for any damage caused by any virus 
transmitted by this e-mail.  This disclaimer is property of the TTC and must 
not be altered or circumvented in any manner.

Reply via email to