Just clarifying what may be some missed points: DHCP can be configured with RESERVATIONS to consistently assign the same IP address to a particular device. That is a compromise in the effort involved, you still don't have to configure each local device, it's just an entry in the DHCP server. In a content filtering environment, I allow devices to get a dynamic address, but that pool is the most restricted. Then I create a reservation into an appropriate pool to give the device the desired level of filtering rules.
If you application can't resolve DNS by name, yes, it's broken as designed. Conceptually, even if dynamic DHCP assigned addresses and updated the DNS server, print by name should work. However, DNS servers use a "time to live", they don't validate the address until that time expires. MVS doesn't need a DNS "server" to be able to resolve names; it just needs a list of servers to access for that service. I don't know if MVS DNS client "caches" addresses or not or if it honors the TTL for those entries. I support several hundred printers across the state. What the networking people are planning probably won't work with what has been said about CA Spool needing IP addresses. You require static IP addresses for each printer; how they do it is the net admins problem. Make sure your users know whose problem it is as well. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
