|
those printers still have a limitation of 198. we are using NLynx emulation. I was getting page size errors on the 5225 and got the same error when we tried 3812. We can print maxicodes fine - it's the larger data content of the PDF417 that giving me the business what would you do if you had 1000 btyes of data -----Original Message----- From: Alex A Moore [mailto:alexm@ellishosiery.com] Sent: Tuesday, November 13, 2001 8:14 PM To: rpg400-l@midrange.com Subject: RE: Barcoding - ZPL instruction ^B7 You want to use a printer definition that is fairly "stupid". 3812 would not be a good choice. 5225 would be better, but how is your printer attached? If through a dumb terminal, or a PC, that introduces another variable. We configure our's as 4214, but if attached through a PC (client access) it will normally auto-configure as a 3812. Here is some sample output that includes a maxi-code 柔A挂G柔Z 柔A挂F柔Z 柔A映CY柔Z 柔A 拴VY 柔Z 柔A映MC柔Z 柔A 昭H0,0政S 昭L1219政S 星ON政S 柔Z 柔A 星RD政S 政T0020,0041括0N,0022,0028政D-*LINK政S 政T0446,0041括0N,0028,0036政D-*LINK政S 政T0610,0041括0N,0028,0036政D-*LINK政S 政T0020,0062括0N,0022,0028政D-*LINK政S 政T0020,0082括0N,0022,0028政D-*LINK政S 政T0020,0122括0N,0022,0028政D-*LINK政S 政T0020,0163括0N,0034,0034政D-*LINK政S 政T0122,0183括0N,0030,0034政D-*LINK政S 政T0132,0142括0N,0018,0024政D-*LINK政S 政T0020,0203括0N,0034,0034政D-*LINK政S 政T0122,0224括0N,0030,0034政D-*LINK政S 政T0122,0265括0N,0030,0034政D-*LINK政S 政T0122,0305括0N,0030,0034政D-*LINK政S 政T0122,0356括0N,0042,0046政D-*LINK政S 政T0294,0447括0N,0077,0081政D-*LINK政S 政T0020,0685括0N,0054,0058政D-*LINK政S 政T0020,0711括0N,0022,0024政D-*LINK政S 政T0122,0142括0N,0018,0024政D-*LINK政S 政T0548,0163括0N,0081,0091政D---政S 政T0030,0996括BN,0011,0007政D-*LINK政S 政T0203,1210括BN,0022,0014政D-*LINK政S 拾Y03,0.0政S 政T0345,0570拾CN,0111,N,N,N,N 政D>;0000000000000政S 拾Y02,2.0政S 政T0030,0590拾D4政H 政D000000000000000000000000000000政S 拾Y03,0.0政S 政T0061,0939拾CN,0203,N,N,N,N 政D>:0000000000000000000000政S 拾Y04,0.0政S 政T0091,1179拾CN,0162,N,N,N 政D>;>800000000000000000000政S 政T0010,0366故B0792,0000,0005政S 政T0264,0610故B0000,0244,0005政S 政T0010,0630故B0792,0000,0020政S 政T0010,0722故B0792,0000,0005政S 政T0010,0972故B0792,0000,0018政S 政T0670,0722故B0132,0098,0053政S 星Q0001,0,0001,Y政S 柔Z Alex ZPL instruction ^B7 > > > I'm still getting page size errors on the printer > > -----Original Message----- > From: Steiner, Webb H (TC) [mailto:whsteiner@taylorcorp.com] > Sent: Tuesday, November 13, 2001 4:51 PM > To: 'rpg400-l@midrange.com' > Subject: RE: Barcoding - ZPL instruction ^B7 > > > I was trying to break down the data but I found documentation > that requires > - structure in one piece without row breaks and space > > I'm going to try 241 - I've changes the label printer from > 5225 to 3812 > > Have you done this? > > > > -----Original Message----- > From: Alex A Moore [mailto:alexm@ellishosiery.com] > Sent: Tuesday, November 13, 2001 4:05 PM > To: rpg400-l@midrange.com > Subject: RE: Barcoding - ZPL instruction ^B7 > > > How long is your printer file record defined? > > Alex > > > > > > > I need to know how to code the O specs for the PDF417 > > barcode. I have a data > > element of 207 bytes. I have broken the data down into three > > fields and am > > spacing 0 before and 0 after on the except lines. Nothing > > prints when I send > > it to the Zebra printer. On examination - the hex dump is > > showing carriage > > returns are being inserted into the data causing the barcode > > not to print. > > > > Someone must be using the 417. Please help. > > > > > > Webb > _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l or email: RPG400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.
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.