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



Loyd,

That sounds kind of funny to me.  What does the PSFCFG object being used
look like?

How much bigger are the bar codes?  Does it seem to be a 230pel vs. 300pel
issue?

I'm mostly out of ideas <grin> if it were me I'd try calling IBM and see
what they say.  You might also post a message in the comp.sys.ibm.as400.misc
newsgroup as a couple of the IBM spool/print people hang out there.

Good Luck,
Charles


> -----Original Message-----
> From: Goodbar, Loyd (ETS - Water Valley) 
> [mailto:LGoodbar@xxxxxxxxxxxxxx]
> Sent: Friday, September 10, 2004 3:58 PM
> To: Midrange Systems Technical Discussion
> Subject: RE: Confused about printing
> 
> 
> The reason for both device descriptions is when I tried 
> printing the AFPDS
> spooled file on WV17, it got held immediately by the writer. Hence, I
> created a different DEVD for AFPDS printing.
> 
> I received "Bar Code Specification Check exception at printer WV17."
> Messages in the writer when trying to print the AFPDS spooled 
> file to WV17.
> It looks like the sense data X'04110100 DE010001 00000000 
> D6810101 01010000 
> 00000001' is a result of trying to print off the page, or the 
> positional
> translation put part of the barcode off the page.
> 
> Judging by the AFPDS results, that is correct. I have bar 
> codes running all
> off the page.
>  
> Loyd
> 
> Loyd Goodbar
> Senior programmer/analyst
> BorgWarner
> E/TS Water Valley
> 662-473-5713
> 

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.