Your Doman Name Service (DNS) should be able to overcome this difficulty. A DNS translates an name (e.g. HOSTNAME) to an IP address (e.g. 192.168.81.99) or vice versa. If you are not changing the IP address, as long as the original name is known to the DNS, the connection should be successful.
More info here: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/F1A1B3B0/CCONTENTS?SHELF=f1a1bkd0&DN=SC31-8775-19&DT=20110608115203 and here: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/F1A1B4B0/CCONTENTS?SHELF=f1a1bkd0&DN=SC31-8776-20&DT=20110609204120 (watch the wrap) Might also be asked on the TCPIP list: IBM TCP/IP List <[email protected]> HTH, <snip> Is there anyone that would be willing to provide me with a list of the implications of changing the 'HOSTNAME' statement in TCPIP.DATA. My concern is this: There are a lot of jobs on the z/OS platform that connect to midrange and possibly x86 servers using the existing name schema The same is true for applications on open systems. i.e. they connect to the main frame using MVS_HOST1. Are all these application going to be modified to connect using new host names? </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
