Re: CCSID - getting the correct character to pc/printer -- MIDRANGE-L

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

Are you putting these commands in with your program? Or are you using standard stuff, like highlight and underline, etc.? Host Print Transform will usually take care of that. I worked at a place where we put PCL strings into the spooled files. We ended up using Host Print Transform with a custom WSCST. The problem was the escape character.

You could reverse engineer - see what translation table has a code point with the codes you need, then figure out what EBCDIC character gets converted to that. Or build you own translation table in the WSCST - that's what we did. The company used to use a Decision Data terminal, which let you specify a multi-character string that it would replace with another string. But nothing in networks will do this.

HTH

Vern

At 02:39 PM 3/25/2003 +0400, you wrote:

After FTPing a source file to a PC, it happens that there are some special
characters that get converted. For example a "$" becomes a " £" .  I
believe this has to do with the CCSID associated to the fields of the
source file. For example, if the job's CCSID at the time of creation is
297, then the CCSID will be 297. How can one prevent this character
conversion. In fact our ultimate aim, is to send spool files via a remote
outq to a printer's flash memory. As these spool files contain specific
commands to be processed by the printer, and these commands contain special
characters such as the above, these keep getting converted and hence cannot
be processed by the printer.

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.