Problem with reports transfering from one Remote Output Queue to another
From Support
| If you have a question or seek clarification, please call Technical Support. |
Problem:
The customer has created a remote output queue via the CRTOUTQ command and the remote writer has been started with the STRRMTWTR command, but reports are not getting sent to the remote AS/400 system. They have also checked to see if TCP/IP connectivity is active between the systems by using the PING command.
Solution:
We ran the NETSTAT command on the AS/400 and took menu option 3 - "Work with TCP/IP connection status".
Once the Netstat screen was shown, we looked for "lpd" under the local port listing. "lpd" stands for "Line Printer Daemon". This AS/400 service is used for remote TCP/IP printing.
In this customers case we did not find the "lpd" service running so we ran the following command to start the "lpd" service:
STRTCPSVR *LPD
This resolved the problem.
See NETSTAT option 3 example listed below for identifying whether the "lpd" service is active:
Work with TCP/IP Connection Status
System: S103N0YM
Local internet address . . . . . . . . . . . : *ALL
Type options, press Enter.
4=End 5=Display details
Remote Remote Local
Opt Address Port Port Idle Time State
* * lpd 042:31:00 Listen
* * 1038 +++++++++ Listen
* * 1080 073:40:56 Listen
* * 1100 719:08:04 *UDP
* * 1352 142:40:38 Listen
* * as-admi > 115:35:37 Listen
* * as-cent > 001:28:38 Listen
* * as-data > 216:28:38 Listen
* * as-dtaq 216:28:36 Listen
* * as-file 216:28:40 Listen
* * as-netprt 216:28:39 Listen
More...
F5=Refresh F11=Display byte counts F13=Sort by column
F14=Display port numbers F22=Display entire field F24=More keys
