RE: Printing to a remote system

Honestly there are others here who configure lan based printers here. I have some configuration below.
Let me prefix it with these comments.
IDK if I would make any writer dependent on another system/lpar. If the intermediate lpar/system is down then the writer is down for the other. That is why using remote outq to a different lpar/system does not appeal to me.
And we avoid hard coding IP addresses more than the plague. I've eaten multiple meals close to a sign warning there's plague in the area. Even printers are in our DNS. Having moved offices, data centers, etc hard coding has no appeal to me. That and the network nazi occasionally likes to change IP addresses.


PROD:
WRKOUTQD PRTL023
Remote system . . . . . . . . . . . . : *NONE
DSPDEVD PRTL023
Device class . . . . . . . . . . . : *LAN
Device type . . . . . . . . . . . : 3812
Device model . . . . . . . . . . . : 1
LAN attachment . . . . . . . . . . : *IP
Port number . . . . . . . . . . . : 9100
Physical attachment . . . . . . . : *DIRECT
...
Remote location:
Name or address . . . . . . . . : PRTL023
...

DEV:
WRKOUTQD PRTL023
Remote system . . . . . . . . . . . . : *NONE
DSPDEVD PRTL023
Device class . . . . . . . . . . . : *LAN
Device type . . . . . . . . . . . : 3812
Device model . . . . . . . . . . . : 1
LAN attachment . . . . . . . . . . : *IP
Port number . . . . . . . . . . . : 9100
Physical attachment . . . . . . . : *DIRECT
...
Remote location:
Name or address . . . . . . . . : PRTL023
...



Rob Berendt