Remote Output Queues: Difference between revisions
Jump to navigation
Jump to search
(+Link) |
(+Cmdline) |
||
| Line 9: | Line 9: | ||
== SNA == | == 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. | 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. | ||
ADDDIRE USRID(QNETSPLF ''sysname'') USRD('LPR over SNA') USER(QNETSPLF) SYSNAME(''sysname'') | |||
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. | 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. | ||
Latest revision as of 18:34, 13 February 2024
|
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.
ADDDIRE USRID(QNETSPLF sysname) USRD('LPR over SNA') USER(QNETSPLF) SYSNAME(sysname)
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.