> You can tell the LPRXONE exit which translate table to use > (it can be configured to use the TCPXLATE TCP/IP translate > tables) as the default translation table. > [...snip...]
This seems symptomatic of a larger question. How difficult would it be to really get down to *one* printing interface on VM? Right now, we have 3 (CP spool, RSCS, and PSF). Could we consolidate that, probably into RSCS (as it would take the least work IMHO)? If RSCS could control channel-attached printers (not necessarily drive, but just control), I think this could be done fairly easily. A CMS MODULE version of PPS could replace PRINT, and the default CMS user configuration in SYSPROF EXEC could spool the user's printer to RSCS by default. Operators would have ONE place to look for printout, and one control interface to learn/manage. Non-CMS guests would spool their printer to RSCS, and continue to write to CP spool as normal. That would also enable all the nice PCL and PS support enhancements that Les and Co. have added to RSCS for guests w/o a lot of effort or additional Interesting/desirable? -- db
