Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Spool - ended with problem status

Former Member
0 Likes
1,369

Hi,

Few jobs ended with problem status but all letters got printed.

How to find out the issue ?

Thanks,

Vimal Alexnader

8 REPLIES 8
Read only

Former Member
0 Likes
1,326

Hi Vimal,

You can use the Tcode SP01 to check the details.

If you know the Spool number or other details of the Spool such as User id / Date created, etc., you can provide these details in SP01 tcode and check the Error Log.

Double-click on the Error Status and click on 'Display Log'.

You will find the Error details.

-Sowmya

Read only

0 Likes
1,326

Hi Sowmya,

I have checked the error log, Please find below screen shot.

Also i have checked line no 5823, thez nothing new.

Any other check point ?

Thanks,

Vimal Alexander

Read only

0 Likes
1,326

This message was moderated.

Read only

0 Likes
1,326

Hi Nabheet,

I have checked the link which you suggested but it is not helpful for my scenario.

My issue is " All the letters got printed but ended with problem status ".

If the letters are printed the status should be in Completed, In my case " All the letters got printed but ended with problem status ".

Thanks,

Vimal Alexander

Read only

Former Member
0 Likes
1,326

Hi,

maybe you got a spool overflow. Maybe there are no more free spool numbers in your system. In this case you have to delete old spool list entries.

Regards,

Klaus

Read only

0 Likes
1,326

Hi Klaus,

I have analyzed your point. Issue occured in the middle of the spool.

Hope it is not related with pool overflow.

FYI :

70 spool finished sucessfully.

71th spool completed with problem.

from 72 to 97 printed successfully.

Thanks,

Vimall Alexander

Read only

0 Likes
1,326

Hi,

you should check all system logs for period where the batch jobs were running. Maybe you can find some additional information there.

For example an information like "spool is full" can be found there, if this issue occurs.

Regards,

Klaus

Read only

0 Likes
1,326

Hi Klaus,

I found the reason.

Reason for failure : character set is incomplete, a missing character is replaced with " # "

Thank you for your valueable time to spend this issue.

Thanks,

Alexander