We have a peculiar issue with SAP Spool system. Here I am going to explain the scenario of our Production system and the issue we are facing.
In our production system we have one Central Instance and Five dialogue instances and each instance installed on separate servers of AIX.
We have created an output device with host spool access method as 'S'(Print using SAP Protocol) and had given one APP1(Dialogue instance 1) as host spool server. We have maintained IP address and host name of printer, in the hosts file of the APP1 server. We have tested the printer connection from SAP and it had worked.
When users give any print request, that request was being processed by spool server and it gets held-up in the spool and resulting in error.
Request is being processed by SAP but not sent to printer. This we have resolved by adding the IP address and hostname of the printer in hosts file of all instances of the production system.
We are unable to sort out why the spool system is working like this. As per SAP Print architecture when a print request is generated, that request is directed to the spool server and from there it is sent to the printer. As per our understanding it would be enough to maintain data in hosts file of the spool server only.( In this case APP1).
But the spool system is not working in that way. Could you please clarify on this.
Thanks & Regards,
Manoj Kumar S
Maybe this will shed some light on your issue:
If the status of a spool request has been set to Compl. or Problem but no output is printed, then:
The SAP spool system finished processing the spool request and is working normally
A problem with the data in the spool request, with the printer definition in the SAP System, or with the host system spool or printer prevented any output from appearing. You can log output data to help you analyze the problem. For information about activating this logging, see Logging Print Output Data.