Spool work process

[Former Member]

Hi,

We have 2 spool workprocesses in SM50. But all the printing activity happens from one spool workprocess, 2nd spool wp always remains in Waiting.

We have not configured any operation mode. earlier it was only one spool, recently we have added another in RZ10 and restared SAP

Suggestions pls

[Former Member]

Hey James,

One spool is enough in the system to print the data unless extremely high number of prints are being sent to printer by the users.

Using one spool work process out of the two wont harm the system in any way.

Regards,

Vishi

[former_member185031]

If at the same time more then one user execute the print command then only you can see the utilization of both work process simultaneously, otherwise one will remain the free.

Regards,

Subhash

[Former Member]

Hi,

During month end activity (2 days back), I can see lot of requests waiting in SP01 and 1st spool work process either in RUNNING or ON-HOLD for more than 5000 sec and print happening from different ID one after another. 2nd Spool work process remained in WAITING status only.

Any suggestions

[Former Member]

Hi James,

When I go through ur issue its strange for the spool wp to keep quite when there are spool requests.

As with the other output methods, the spool work process performs the processing for frontend printing. Conflicts can occur in your SAP spool system between normal and frontend print requests. Even if you have classified your spool servers and output devices by the type of output for which they are to be used (such as production printing, mass printing) - as SAP recommends ‑ problems can occur with the server workload due to frontend printing.

Note:- In your case you have configured the printer to the server where you are giving the print i.e Front end printing

Kindly find the below steps.

1) first cross check the spool wp parameter rdisp/wp_no_spo and in your case it should be 2.

2) go to SPAD and cross check the spool server.

3) Imp:- go to sp01 and give * in created by and provide the client and click the execute and check whether both spool wp ids are displaying.

4) Imp:- according to your suspect with the spool wp whichis in waiting state, kindly double check whether this spool wp has occupying memory utilization.

Do send us few suspected areas so that it will be usefull todebug the cause of the error.

With Regards,

Prashanth