× 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.



Remote OUTQs are basically uni-directional.

SNMP, IPP, PJL are all bi-directional.  So you get better feedback on
the status of the print job.  You'll see the print go to a MSGW status.

HTH,

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
  

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx 
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, September 28, 2006 10:49 AM
To: Midrange Systems Technical Discussion
Subject: RE: Monitoring an output queue

What problem would this solve?

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Wilt, Charles" <CWilt@xxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
09/28/2006 10:46 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: Monitoring an output queue






Rob,

Do you really have to use a remote OUTQ?

You'd be better served by using the SNMP, IPP, or PJL driver 
with a DEVD
instead of LPR and a remote OUTQ.

Even on thermal label printers I've been able to use the SNMP driver
with internal network cards and IPP with external print servers.

HTH,

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx 
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, September 27, 2006 1:29 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Monitoring an output queue

We are using some monitoring software.  I have a problem 
monitoring remote 
output queues.  When I turn off the printer on a -REMOTE- 
output queue and 
send it a spool file it doesn't go into a MSGW or anything. 
Like this 
remote output queue P01A08.
WRKSBSJOB QSPL
Job         User        Type     -----Status-----
PVCBAR1     QSPLJOB     WTR      ACTIVE 
P01A01      QSPLJOB     WTR      ACTIVE 
P01A01T     QSPLJOB     WTR      ACTIVE 
P01A02      QSPLJOB     WTR      ACTIVE 
P01A06      QSPLJOB     WTR      ACTIVE 
P01A07      QSPLJOB     WTR      ACTIVE 
P01A08      QSPLJOB     WTR      ACTIVE 

WRKWTR *ALL 
Writer      Type  Device      Queue       Library     Status 
Form Type 
P01A08      RMT               P01A08      QUSRSYS      STR 
*ALL 
Notice, no MSGW? 

And the spool file itself will look like: 
            Device or                       Total   Current 
File        Queue       User Data   Status  Pages     Page   Copies 
QSYSPRT     P01A08                   SND        1                1 

About all I could think of was to monitor for any spool 
file in a SND 
status for an inordinate amount of time.  Or, x number of 
spool files in 
RDY state in that output queue.  Any other suggestions?  (Now 
if I could 
only get our monitoring software to handle one of those.)

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

-- 
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.


-- 
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 ...

Follow-Ups:
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.