Hello, I've been looking at the translate tables supplied for TCP/IP and it seems that CANADIAN and 00370850 are nearly identical (differing for 3 bytes below x'40') and 00371252 and 00370819 are identical.
My client is also experiencing the same problem in that the LPD is apparently using Code page 437 which does not have all the French characters. He is apparently looking into determining what LPD printer server is controlling his printer(s). I was wondering if this is a common problem and what LPD software is out there that will use Windows-1252 which would give all the French characters. Any help/suggestions would be appreciated. Thanks, Mike -----Original Message----- From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: December 16, 2005 12:41 PM To: [email protected] Subject: Re: LPR & French Canadian characters On Friday, 12/16/2005 at 11:44 EST, "Horlick, Michael" <[EMAIL PROTECTED]> wrote: > I did create an ASCII file with codes x'20' through x'FE' as you suggested, > printed it with the binary option and it all makes it clearer to me. I see that > there are some French characters that do not print out since I guess they don't > exist in Code page 437. Whew! Reality matches theory! (I get worried sometimes.) > I checked the ASCII code versus the printed character and CANADIAN TCPXLATE > seems to match and work fine so I'm not sure if the 00370437 TCPXLATE file you > want to create will be any different. 37 <-> 437 is an impossible conversion due to the missing characters in 437. > I guess I cannot assume that the CANADIAN TCPXLATE (or 00370437) will work for > all the clients' printers. How do I associate a specific default TCPXLBIN for 1 > or all printers? I see in the IBM supplied RSCSLPR CONFIG file, TOASCII and > TOASCIIC statements. Would I have to use these statements and possibly create > different configuration files for different printers ? You might have to create a separate LPR queue for each printer, specifying the translation table to use. (Be sure to use SECURE=NO.) You need to figure out how each printer/print server is deployed. 1. standalone printer with internal LPD support 2. Windows built-in LPD server 3. Separately installed LPD server on Unix/Linux 4. Separately installed LPD server on Windows 1 and 3 should work with 00370819 (819 is ISO 8859-1). 2 will work with 00371252. 4 is the pain, and I just don't know enough about the way COUNTRY= in CONFIG.SYS, COUNTRY.SYS, code page switching, CHCP and MODE in AUTOEXEC.BAT, etc. all work together. It is a really esoteric subject as you can see by googling. >The "TCP/IP Planning and > Customization Guide" makes mention of the preferred translation table being LPR > for the LPR client but I see no LPR TCPxxBIN file anywhere. There is a > "tcpxlbin" option for the LPDXMANY configuration file but that is for LPD , not > what I want to do, correct ? Right. You will have to use TOASCII= in the LPRXONE CONFIG to define the translation. See below, though. > I'm also assuming that if a default translation table can been set for a > printer that it will work for any CMS command (PRINT, PPS or LPR) or spool file > coming from say, VSE/ESA, correct ? No. The whole default translation table concept is limited to the legacy VM TCP/IP application suite (e.g. LPR client). It explicitly looks for LPR and STANDARD TCPXLBIN files, conveying information to RSCS as needed. If you copy the TCPXLBIN file you want to TCPMAINT 592 as LPR (or STANDARD) TCPXLBIN, then that's what LPR will use. Note that PRINT and PPS are not the same as LPR. I'm sorry I can't be of more assistance. Getting your clients to standardize on their print server technology will make your life easier. Alan Altmark z/VM Development IBM Endicott
