I've gone through all of the steps, but the "writer" will not start or
appear ass associated with the new printer (IORECV02) as it does with
the others.

 IOLABEL02      QUSRSYS             0      IOLABEL02       RLS    
 IOLABEL03      QUSRSYS             0      IOLABEL03       RLS    
 IOLABEL04      QUSRSYS             0      IOLABEL04       RLS    
 IOLABEL05      QUSRSYS             0      IOLABEL05       RLS    
 IOLABEL10      QUSRSYS             0      IOLABEL10       RLS    
 IOPRINTEK      QUSRSYS             0      IOPRINTEK       RLS    
 IORECVING      QUSRSYS            0      IORECVING       RLS    
 IORECV02       QUSRSYS              0
RLS    

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
daparnin@xxxxxxxxxxxxxx
Sent: Thursday, April 27, 2006 9:04 AM
To: Midrange Systems Technical Discussion
Subject: RE: Remote IP Printer







After creating the IP output queue you can also create a "dummy device"
such as:

CRTDEVPRT DEVD(BREPRD) DEVCLS(*RMT) TYPE(*IPDS) MODEL(0) LOCADR(FD)
FONT(011 10.0) FORMFEED(*CONT) MSGQ(*LIBL/QSYSOPR)

When printer devices are created it attempts to create an OUTQ to go
with
it that matches the printer name.  Because one already exists with that
name it uses it instead of creating a new one.  After that you can use
either the device or the output queue and it will print just fine.  It
will
still show up with a status of *END if you do a WRKWTR but will appear
as
started if you do a WRKWTR *ALL.


Dave Parnin
--
Nishikawa Standard Company
Topeka, IN  46571
daparnin@xxxxxxxxxxxxxx





 

                      Bryan Dietz

                      <BDietz@xxxxxxxxxx>         To:       Midrange
Systems Technical Discussion                
                      Sent by:
<midrange-l@xxxxxxxxxxxx>                                     
                      midrange-l-bounces@m        cc:

                      idrange.com                 Subject:  RE: Remote
IP Printer                                
 

 

                      04/27/2006 09:44 AM

                      Please respond to

                      Midrange Systems

                      Technical Discussion

 





That is because it not a "real" printer.  It is an outq description that
uses (essentially) LPR to send output to the LAN printer.
The users need to use the outq() parm on the chgsplfa command.
or follow
http://www-912.ibm.com/s_dir/slkbase.nsf/1ac66549a21402188625680b0002037
e/770fa496343139bc862565c2007d44cc?OpenDocument&Highlight=0,crtdevprt


If you want a "real" printer description you would need to creat a LAN
printer.
http://www-912.ibm.com/s_dir/slkbase.nsf/1ac66549a21402188625680b0002037
e/00e3c3d5af21afa6862565c2007d437f?OpenDocument&Highlight=0,crtdevprt


Make sure you printer meets the hardware requirements.

_____________________________
Bryan Dietz
Aktion Associates



midrange-l-bounces@xxxxxxxxxxxx wrote on 04/27/2006 09:08:44 AM:

-> I set up a remote out queue "NEWQ" to a network printer using
CRTOUTQ.
The
-> new queue appears on the "Work with all output queues" screen with a
-> writer of the same name. I am able to change an existing spool file
to
the
-> new queue so it prints -- but when other users try to do the same
they
get
-> "Printer NEWQ not found". The new printer does not appear on the
"Work
-> With All Printers" screen. What is happening here?
->
-> Mark Bazer
--
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 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.