Remote Output Queues: Difference between revisions
Jump to navigation
Jump to search
(New) |
(+Link) |
||
| Line 14: | Line 14: | ||
== See also == | == See also == | ||
* [[Printing]] | * [[Printing]] | ||
== Weblinks == | |||
* [https://www.ibm.com/support/pages/configuring-remote-output-queue-rmtoutq Configuring a Remote Output Queue (RMTOUTQ)], IBM.com | |||
[[Category:System Administration]] | [[Category:System Administration]] | ||
Revision as of 11:48, 9 June 2022
|
This article isn't finished yet or needs to be revised. Please keep in mind that thus it may be incomplete.
Reason: Complete article, add documentation links, etcpp. |
Remote Output Queues allow the transfer of spooled output to non local machines:
- IP connected printers,
- IP connected systems,
- SNA connected systems.
The former two is an implementation of lpr for OS/400, while the latter uses SNA for transport.
SNA
No special things to consider for creating an *OUTQ object. An entry for a local QNETSPLF must be enrolled in the system directory on both sending and receiving side, though.
Also the conversion of data to ASCII can take place at the last machine before the job is sent into the ASCII world, so you may set TRANSFORM(*NO) when creating the *OUTQ object.