>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=3DLPRXONE EP=3D'C=3DLPRA ...' ... >LINKDEF PRTB TYPE LPR FORM * AST >PARM PRTB EXIT=3DLPRXONE EP=3D'C=3DLPRB ...' ... > >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 ?
Yes this is certainly one correct way you can provide translate tables. However, if you have a third printer, you will need to define a 3rd LPR link and point to whatever unique translate table you require. > >I understand that in the LPRXFORM I can create forms and for each form I >can specify 'TRANS=3Dstring' within the LPRXFORM file but isn't there = >only >1 form file for all printers (as specified by the FILEDEF LPRXFORM >statement)? No, you can define as many forms as you want, all selectable printer independant by using the spool file form. > >How would PRTA and PRTB be able to use the same form if the form as only >1 set of 'TRANS=3Dstring' and therefore only 1 translate table = >associated >with it? It is all through the spool file form on the print file. Best Regards, Les Geer IBM z/VM and Linux Development
