RE: Remote outq problem.

["Smith, Mike" <Mike_Smith@xxxxxxxxxxxxxxxx>]

Thanks Brian.  
I downloaded these and they were helpful.  They didn't directly solve
the problem, but they led to the problem being solved.  As it turns out
we had to install 'Print Services for Unix' on the server hosting
Formport.  
Your tools did help me resolve the issue with the conflict in the IP
addresses.  There was an old outq that that the IP address that was
showing up in the error message.  



Michael Smith
 


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bryan Dietz
Sent: Tuesday, May 08, 2007 4:50 PM
To: Midrange Systems Technical Discussion
Subject: Re: Remote outq problem.


Maybe, hopefully that message was just a coincidence.
Can you ping the printers IP address??
Not knowing what your IP address of the 400 is maybe there is a routing 
problem.  I have a couple of utilities that may help troubleshoot the 
problem.  Look for WRKRMTWTR and SCANHOST here:
http://home.columbus.rr.com/jbmmdietz/iseries.html

Scanhost is a port scanning program that you can use to make sure that 
port 515 (lpd) and/or 9100(pjl) are listening.
wrkrmtwtr is a tool to see all configured remote writers(outqs)

Bryan


Smith, Mike said the following on 5/8/2007 3:36 PM:
> We are in the process of Installing Formport Server.  The server has 
> been installed, but I'm having difficulty with the remote outq. I have

> setup the remote outq and also a dummy device description.
>
> This is the command I used to create the remote outq. 
>    ===> CRTOUTQ OUTQ(QUSRSYS/CPYROAN) RMTSYS(*INTNETADR)
> RMTPRTQ(CPYROANO) CNNTYPE
> (*IP) DESTTYPE(*OTHER) MFRTYPMDL(*HP4) INTNETADR('192.168.0.27')
> TEXT('FormPort-
>  Copy of Roanoke AP Checks')
>
>
> However, when I start the remote writer I get a message in qsysopr 
> which states. TCP/IP connection to remote system 192.68.0.27 closed, 
> reason code 2
>
> The IP addresses do not match.  I've been told that there is nothing 
> at 192.68.0.27.  I can't figure out why this message is pointing at 
> this IP address, Or for that matter, if this is really telling me 
> where my problem is.
>
> My spool files just get stuck in *SND status.
>
> Michael Smith
> iSeries.mySeries.