I'll take a wild shot here - it isn't remote outqs that can do this, it's using a DNS name, not a numeric IP address.
If possible, it's really wise to use a DNS and have your IBM i talk to it.
I only hope my response is on point!!
Vern
----- Original Message -----
Mike, Rob, are you saying that remote outqs can potentially eliminate
the need for a static I.P. address in the INTNETADR parameter?
How can a remote outq communicate with a remote system without an I.P.
address?
All of my outqs are remote outqs with these parms because we use
Create!form.
Remote system . . . . .RMTSYS *INTNETADR < are you saying change
this?
Remote printer queue . .MRTPRTQ ITDEPT <outq for I.T.
department printer
Connection type . . . .CNNTYPE *IP < I use *IP along with
next fields
Internet address . . . .INTNETADR 10.0.3.102 <the I.P. of our
Create!form server
User data transform . . SND100 <program Create!form
uses
Library. . . . . . . . . CSNDSYS640 >library that SND100 is in
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.