Lizette, One other thing to check out - if in fact the CA print spooler software can use DNS-based routing. Does the DHCP server talk to the DNS server and possibly auto-register the IP address? We are doing exactly that at our site. When the network staff sets up a printer, they assign it a host name as well as defining it to use DHCP for picking up an IP address. When the printer is then plugged into the network, it broadcasts it's name and asks DHCP for the address. DHCP then assigns an address and also sends the combination of IP address and name to DNS to get registered. This way, if the printer gets a new IP address, it simply gets re-registered and our mainframe print software (VPS, not CA-SPOOL) simply keeps sending print to the DNS name.
This way keeps the network people from having to maintain a static list of IP addresses for printers and allows you to use DNS to get the print software set up ahead of time. Rex -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of J R Sent: Thursday, August 23, 2007 8:09 AM To: [email protected] Subject: Re: Print Distribution and IP connected Devices Dynamic IP addresses via DHCP make perfect sense for "client" devices that "come and go", e.g. end user desktops, laptops, etc. No one else needs to know their address until they make contact with a request. However, "server" devices that are expected to be there "all the time" require static IP addresses so that clients know where they are. Using a URL is analogous to cataloging a dataset. It enables one to get there by name alone, without needing to know the address, volser, etc. >From: Bill Dodge <[EMAIL PROTECTED]> >Reply-To: IBM Mainframe Discussion List <[email protected]> >To: [email protected] >Subject: Re: Print Distribution and IP connected Devices >Date: Thu, 23 Aug 2007 08:28:37 -0400 > >The best way (IMHO) is for the network group to establish a pool of >static addresses for printers and to hard assign those addresses to the printers. >Then to take it a step further to give them DNS entries so the IPADDR >can be changed if necessary but your print distribution doesn't need to >be changed. The problem with DHCP is that you need to wait for the >printer to attach to the network and then go find out what IPADDR was >assigned. Then you have to go back and establish that address for the >right printer in your distribution package. The real FUBAR happens if >DHCP leases expire and the netwwork goes down (like that never >happens)or the printer goes offline for an extended period of time >(What? Hardware breaks? Go figure.). Now as the printers attach to >the network they will all undoubtedly have new IP adrresses - just the nature of the beast. ---------------------------------------------------------------------- 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
