Lizette
I'm looking at this purely as an issue of an IP-based application running on
an IP node.
The virtual IP address (VIPA) was created in order to be able to separate
the IP address used by the IP-based applications from the IP addresses of
the interfaces to the IP node supporting the application.
If you are not familiar with the use of VIPAs, perhaps now is a good time
for both you and the people in your networking group to start.
I was rather surprised to see that none of the eminent responders hitherto
had mentioned this, to me, rather obvious solution. Perhaps there's some
aspect of the "print (report) distribution" application which is
VIPA-unfriendly and which is also obvious to anyone who can be expected to
be familiar with the application. In which case I'm sorry for my ignorance.
If it turns out that the use of VIPAs is possible, your networking group
will have to tackle the issue of allocation of address ranges for VIPAs to
be used by applications which address ranges fit within your overall IP
address range schemes. In order to exploit the many possibilities of the use
of VIPAs in the future, be sure that your networking group allocates
generous address ranges.
Incidentally, the list where Communications Server (CS) IP component (even
SNA component) specialists is concentrated is IBMTCP-L:
<quote>
For IBMTCP-L subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO IBMTCP-L
</quote>
As Ulrich indicated, you should challenge the statement that a name server
cannot be used. This is a most curious limitation given that just about the
first trick a socket programmer learns is to treat a the character string
providing the destination first as an IP address and, when that fails, as a
name to be resolved. I have found this flexibility to be present in every
serious IP-based client program I have used - not a great number, it has to
be admitted. In addition when you use a name server, multiple IP addresses
can be returned and the serious IP-based client program will try each in
turn. You may have a use for that capability - if, as it should be, it is
present in this "print (report) distribution" application.
Finally, if it turns out that a name server can be used after all, be sure
that, in addition, you and your networking group take on board the manifold
benefits of the VIPA.
Chris Mason
----- Original Message -----
From: "Lizette Koehler" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To: <[email protected]>
Sent: Wednesday, August 22, 2007 10:31 PM
Subject: Print Distribution and IP connected Devices
We will be moving many people over the next few months from one building
to
another about 10 miles away. Some will keep their current equipment and
some will get new equipment.
What I am running into is with print (report) distribution.
The network group (not MAINFRAME) cannot tell me the new IP addresses for
this equipment until it is actually plugged in. That means I have to wait
until the customer is ready to work to find out they can no longer receive
print from CA Spool or Dispatch because the old IP address for their
equipment is no longer valid.
Is there any way I can get this under control before the move or am I just
SOL?
CA tells me they cannot use a DNS name for the IP connected equipment;
that
it has to be a physically coded IP address.
Any thoughts, suggestions or comments are welcome.
Lizette
----------------------------------------------------------------------
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
