Re: Code128 CR/LF

[Roger Harman <roger.harman@xxxxxxxxxxx>]

I see that the problem was resolved with RPLUNPRT().  Glad you caught that.

I looked right past the DDS keyword as, when I was doing CODE128 stuff (so many years ago) it was kind of "roll your own" interfacing to HP LaserJets and beta testing HP's early barcode cartridges (remember those?).

Roger Harman
COMMON Certified Application Developer - ILE RPG on IBM i on Power

 --

From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>

Sent: Friday, August 9, 2019 2:12 PM

To: rpg400-l@xxxxxxxxxxxxxxxxxx <rpg400-l@xxxxxxxxxxxxxxxxxx>

Subject: Re: Code128 CR/LF

Roger,

That's true, but she isn't coding this herself directly, she's using the 
DDS BARCODE() keyword, which is supposed to convert the data from EBCDIC 
to the Code128 character set.

Here's the chart that IBM supplies:

https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_74/rzakd/code128.htm

Notice that it says CR is x'0D' and LF is x'25', just like she coded?!

I think it's more likely that she has the RPLUNPRT(*YES) options 
specified in in her CRTPRTF command.  (It is the default.) so 
unprintable characters like CR and LF are being replaced with blanks.

-SK


On 8/9/2019 12:05 PM, Roger Harman wrote:

> It's been a lot of years so I had to refresh my memory as I recalled that the character set is different for 128.  Yes, 128A supports CR/LF but does not use the values you are supplying.

> https://www.barcodefaq.com/1d/code-128/#Code-128CharacterSet

>

> 77/74 are equivalent to CR/LF in 128A

>

>