Solution : https://service.sap.com/sap/support/notes/4572 (SAP Service marketplace login required)
Summary :
This SAP Note addresses an issue where the R/3 Spooler marks output requests as 'finished' though the corresponding UNIX printer does not execute the print job. Possible causes include an overloaded host spooler or missing spool files due to failures in the host spooler system. Solutions differ based on specific cases: waiting for the spooler to become available, employing R/3 admin tools to test and adjust UNIX print commands, or reviewing error logs for spool requests and system operations. Changes are contingent on the platform with logs located in varying system directories depending on the SAP release version.
Key words :
/usr/sap/c11/dvemsg00/work/stderr2, /usr/sap/c11/dvemsg00/work/dev_w11, sapparam parameter 'rspo/host_spool/print', additional key words unix spool, symptom key word, link type 'n', general error log, output editing program, host spooler lost, spoolerr/3 spooler registers