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



Aaron

As a further thought, try WRKWTR *ALL - when you display them, there is a way to see the job associated with them. Every writer is just another job, after all, and there will usually be some messages that MIGHT be helpful.

But as Charles and I have said, you don't use STRRMTWTR with a device - the Zebra info is probably somewhat old, before *LAN print devices were easily set up.

Good luck
Vern

On 7/22/2010 7:43 AM, Charles Wilt wrote:
Gotta love remote writers...the send the data...doesn't matter if it
gets printed or not.

Forget about the ZEBRA14 remote writer for now, concentrate on the
ZEBRA13 device description.

Charles

On Wed, Jul 21, 2010 at 5:57 PM, Aaron Bartell<aaronbartell@xxxxxxxxx> wrote:
How timely! I just tried that and the spool file went through! Only
problem is that it didn't come out on the printer :-(

STRRMTWTR OUTQ(QGPL/ZEBRA14)

I found the STRRMTWTR command in a Zebra manual and they subsequently tell
me to do the following:

OVRPRTF FILE(*PRTF) FORMFEED(*CONT) OUTQ(QGPL/ZEBRA14)

Now whenever I run my RPG program that produces a zebra label, it
immediately disappears. So the spool file is going *somewhere*
successfully, just not to my Zebra printer.

Thoughts?

Aaron Bartell
http://mowyourlawn.com
http://mowyourlawn.com/blog/


On Wed, Jul 21, 2010 at 4:19 PM, Vern Hamberg<vhamberg@xxxxxxxxxxx> wrote:

You may have defined the device to start a writer automatically, but
that's only at IPL. So you'll need to STRPRTWTR on it.

Vern

On 7/21/2010 4:10 PM, Aaron Bartell wrote:
Lukas,

That command runs successfully. I changed the name to ZEBRA11 and the
IP
to 192.168.0.102. I do a 2 on my ZPL spool file and specify an OUTQ of
ZEBRA11. It goes to the ZEBRA11 OUTQ but it just sits there in RDY
status.
The OUTQ is in RLS status. Do I need a writer attached to this OUTQ?

Aaron Bartell
http://mowyourlawn.com
http://mowyourlawn.com/blog/


On Wed, Jul 21, 2010 at 2:49 PM, Lukas Beeler<
lukas.beeler@xxxxxxxxxxxxxxxx
wrote:

On Wed, Jul 21, 2010 at 21:15, Aaron Bartell<aaronbartell@xxxxxxxxx>
wrote:

The Zebra GK420t arrived today. I am pulling my hair out again

concerning

the setup because I am too ignorant to try anything logical and am just
throwing mud at the wall at this point. Too many terms being thrown

around

on the web search results like "you don't need a WCST object" and "make

sure

to configure it with a RMTPRTQ of 'PORTLF1' ", and I don't have a solid
understanding how a remote outq is different from a regular outq other

than

I see it seems to be using some PASE type features when it is created

(i.e.

'/prt01') via iNav.

A Remotq Outq uses the LPR protocol to send a spool file to another
system. The RMTPRTQ parameter specifies to which remote print queue
it's being sent - in case of a directly network attached printer, this
can be either inconsequential (Zebra print servers), specify the type
of content (HP, for example) or in case of another system it can
specify the other print queue (for example, when sending to another
IBM i machine.

Here's how i create my Zebra Remote OUTQ, with which i've installed a
few GK420ts just a few weeks ago:

CRTOUTQ OUTQ(PRTETIK) RMTSYS(*INTNETADR) RMTPRTQ('1') CNNTYPE(*IP)
DESTTYPE(*OTHER) TRANSFORM(*YES) MFRTYPMDL(*WSCST) WSCST(QWPDEFAULT)
INTNETADR('192.168.1.100') SEPPAGE(*NO)

As you can see, RMTPRTQ is '1' in this case - this is a dummy value.

Make sure you print SCS spool files that are 100% aligned to the left,
no spaces, no nothing. This can cause issues, otherwise.



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