× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Nick,

Thanks for the reply. The writer is started automatically. If I run STRRMTWTR it
says Writer HP990 already started.

Thanks,

Gary

On 6 Sep 2011 at 14:07, Nick_Radich@xxxxxxxxxxxxxx (Nick_Radich@xxxxxxxxxxxxxx
<midrange-l@xxxxxxxxxxxx>) commented about Re: Can't print to remote outq:

Hello,

Do you need STRRMTWTR also?



Thanx,

Nick



Nick Radich
Sr. Programmer/Analyst
EPC Molding, Inc.
Direct (320) 679-6683
Toll free (800) 388-2155 ext. 6683
Fax (320) 679-4516
nick_radich@xxxxxxxxxxxxxx



From: "Gary Kuznitz " <docfxit@xxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 09/06/2011 02:01 PM
Subject: Can't print to remote outq
Sent by: midrange-l-bounces@xxxxxxxxxxxx



I can't seem to print to a remote outq and I can't figure out why.

I setup a remote outq with this CLP:
PGM
ENDWTR WTR(HP990) OPTION(*IMMED)
MONMSG MSGID(CPf3313) /* Writer HP5IP not active +
nor on job queue. */

DLYJOB DLY(15)
CLROUTQ OUTQ(HP990)
MONMSG MSGID(CPF3357) /* Output queue In Library +
*LIBL not found. */

DLTOUTQ OUTQ(QUSRSYS/HP990)
MONMSG MSGID(CPF2105) /* Object in QUSRSYS type +
*OUTQ not found. */

CRTOUTQ OUTQ(QUSRSYS/HP990) RMTSYS(*INTNETADR) +
RMTPRTQ(HP990) AUTOSTRWTR(1) CNNTYPE(*IP) +
DESTTYPE(*OTHER) MFRTYPMDL(*HP4000) +
INTNETADR('75.79.xxx.xxx') DESTOPT('xaix +
xautoq') SEPPAGE(*NO) TEXT('Remote Print +
Manager to PDF') AUTCHK(*DTAAUT)
ENDPGM
Of course the xxx.xxx has a valid IP address.

In WrkActJob it has a writer in QSPL
Work with Remote Writer

Writer . . . . . . . : HP990 User . . . . . . . . : QSPLJOB
Number . . . . . . . : 161306

Started by user . . . . . . . . . . . : QSECOFR
Status:
Writing . . . . . . . . . . . . . . : Y
Waiting on message . . . . . . . . . : N
Held . . . . . . . . . . . . . . . . : N
End pending . . . . . . . . . . . . : N
Hold pending . . . . . . . . . . . . : N
Between files . . . . . . . . . . . : N
On job queue . . . . . . . . . . . . : N
File being written . . . . . . . . . . : QPQUPRFIL
File number . . . . . . . . . . . . : 1

It has a spool job that it's trying to write.

The outq shows it's ready to write:
HP990 QUSRSYS 1 HP990 RLS

Work with Output Queue

Queue: HP990 Library: QUSRSYS Status: RLS/WTR

Opt File User User Data Sts Pages Copies Form Type
Pty
QPQUPRFIL GARYT SND 2 1 *STD 5

I have a packet monitor on the LAN of the AS/400 that shows no packets are
coming
from the AS/400. I don't have a firewall on the AS/400. It is connected
through a
hub to the router. I am using Client access remotely through the same
router and I do
see port 23 traffic.

I have had this working in the past. Any ideas why the AS/400 model 150
wouldn't be
sending the spool file?

Thanks,

Gary Kuznitz
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.