As long as DHCP updates your DNS tables (I would want immediately), I don't
see why not. Otherwise RSCS would be trying to connect to a "moving" target
IP address wise. And yes, you would need to run RSCSDNS to do the name
resolution.
Mike
EDS
(215)246-4306
To
"Smith, Ann [email protected]
(ISD, IT)" cc
<[EMAIL PROTECTED]
artford.com> Subject
Sent by: VM/ESA RSCS and DHCP
and z/VM
Discussions
<[EMAIL PROTECTED]
RV.UARK.EDU>
10/19/2005
02:13 PM
Please respond
to
VM/ESA and z/VM
Discussions
<[EMAIL PROTECTED]
RV.UARK.EDU>
The desktop support folks in our Simsbury office want to convert all LAN
printers to DHCP. We currently have LPR printers using static IP addresses.
Customers do not use PPS but an older command which basically issues
SPOOL/TAG/PRINT. If the printers are converted to DHCP is there a way to
define the RSCS printers to print to HOSTNAME rather than IP addresss? Do I
need to create an RSCSDNS id or can RSCS print to a DNS name without
RSCSDNS?
*************************************************************************
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information. If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited. If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*************************************************************************
NOTICE: This communication may contain confidential, proprietary or
legally privileged information. It is intended only for the person(s) to
whom it is addressed. If you are not an intended recipient, you may not
use, read, retransmit, disseminate or take any action in reliance upon it.
Please notify the sender that you have received it in error and immediately
delete the entire communication, including any attachments. Although EDS
encrypts certain email where appropriate, EDS cannot ensure the
confidentiality or integrity of all external e-mail communications and,
therefore, cannot be responsible for any unauthorized access, disclosure,
use or tampering that may occur during transmission. This communication is
not intended to create or modify any obligation, contract or warranty of
EDS, unless the firm clearly expresses such an intent.
