Ok (have patience with me on this). 

Let's suppose I have 2 printers PRTA and PRTB using 2 different
translate tables (say PRTA uses CANADIAN and PRTB uses 00371252). All
the data for a printer (forms or no forms, CMS or VSE output) would be
translated using its own translate table. 

I define them as 

LINKDEF PRTA TYPE LPR FORM * AST
PARM PRTA EXIT=LPRXONE EP='C=LPRA ...' ...
LINKDEF PRTB TYPE LPR FORM * AST
PARM PRTB EXIT=LPRXONE EP='C=LPRB ...' ...

In my PROFILE GCS on RSCS 191 disk I Have

FILEDEF LPRA DISK LPRA CONFIG *
FILEDEF LPRB DISK LPRB CONFIG *

Within the file 'LPRA CONFIG' I have TOASCII and TOASCIIC statements
that represent the translate table CANADIAN and in 'LPRB CONFIG' I Have
TOASCII and TOASCII statements that represent the translate table
00371252. 

Is this the way to do it ? 

I understand that in the LPRXFORM I can create forms and for each form I
can specify 'TRANS=string' within the LPRXFORM file but isn't there only
1 form file for all printers (as specified by the FILEDEF LPRXFORM
statement)?

How would PRTA and PRTB be able to use the same form if the form as only
1 set of 'TRANS=string' and therefore only 1 translate table associated
with it?

Mike     


-----Original Message-----
From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] On
Behalf Of Les Geer (607-429-3580)
Sent: December 16, 2005 12:47 PM
To: [email protected]
Subject: Re: LPR & French Canadian characters

>Thanks for the explanation. I think it's all lining up properly in my =
>brain now.
>
>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.
>
>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.
>
>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 ? 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 ?
>
>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 ?
>


Instead of creating separate LPR links in RSCS, I would use the
LPRXFORM exit package to develop forms that can be used to select
different translation tables on a print by print basis.

On a printer link, using the LPRXONE configuration file you would be
specifying a default translation table for any printout.


The LPDXMANY translation table would be for converting ASCII to EBCDIC
as a file is received.



Best Regards,
Les Geer
IBM z/VM and Linux Development

Reply via email to