PSF Command-attached DSS
You should use the PSF command-attached DSS when you need to either transform input data types to forward to a PCL printer that you have no other way to reach or store the data for later handling. For example, if the PCL printer is physically connected to another system, this method might be the only way to print to it. Before you create the PSF command-attached actual destination, you must create the print queue to which the actual destination will submit requests.
Because PSF command-attached actual destinations requeue jobs to a local or remote queue, they share many of the limitations of BSD actual destinations listed in the BSD section. However, there are some notable differences.
Unlike BSD actual destinations, PSF command-attached actual destinations:
- Support multiple document formats because the PSF DSS automatically transforms all
input data to AFP and then to some form of PCL or PPDS before sending it to the print
For more information about limitations specific to using PSF command-attached printers to transform input data types to forward to a PCL printer, see Processing concerns when using the PCL Secondary.
- Generate auxiliary sheets
Unfortunately, a command-attached actual destination does not receive very much printer and job status information. Because the command used must be able to accept data from STDIN, the PSF command-attached DSS cannot use the rembak backend.