topic Re: SPOOL_INTERNAL_ERROR spool overflow when submitting the same program in Application Development and Automation Discussions

SPOOL_INTERNAL_ERROR spool overflow when submitting the same program

SumitKundu — Mon, 11 May 2009 15:23:46 GMT

I am submitting the same program via job with different seletion screen values after JOB_OPEN, and then SUBMIT statement and JOB_CLOSE FM. But this job get cancelled with message "ABAP/4 processor: SPOOL_INTERNAL_ERROR" . The submit is as follows:

SUBMIT (sy-repid) USER sy-uname

VIA JOB 'ZTP_SAl_REG_MONITOR_JOBS'

NUMBER l_jobcount

TO SAP-SPOOL

SPOOL PARAMETERS fp_user_print_params

NEW LIST IDENTIFICATION 'X'

WITHOUT SPOOL DYNPRO

WITH rb_monit EQ 'X'

WITH s_jobcnt IN s_jobcnt

WITH p_date EQ p_date

WITH rb_row EQ rb_row

WITH rb_col EQ rb_col

AND RETURN.

Is it possible to use the same program to be scheduled....Let me include that the submit is happening with rb_monit = X and it has separate branch...so infinite looping can not happen.

Re: SPOOL_INTERNAL_ERROR spool overflow when submitting the same program

Former Member — Wed, 20 May 2009 05:07:34 GMT

Hi Sumit,

I hope that the flag is ensuring that it doesnt go into infinite loop. You may wish to check that once bcz Spool overflow seems to be bcz of infinite loop or bcz of layout issue.

Goto SP01 in the same client where you have scheduled the job.

Check the spool no. which was generated bcz of the job.

Double click on the STATUS of the spool ( it should be in red background color).

System will give a popup with status details.

Again double click on the status. System will again give a popup.

The popup will give the details of why the spool ran into errors.

Also check the layout.

Thanks,

Best regards,

Prashant

Re: SPOOL_INTERNAL_ERROR spool overflow when submitting the same program

Former Member — Wed, 20 May 2009 05:13:30 GMT

Hi,

Delete the spools generated in SP01 under your user name and check.

Regards

Raj

Re: SPOOL_INTERNAL_ERROR spool overflow when submitting the same program

SumitKundu — Thu, 05 Nov 2009 13:41:26 GMT

yes the problem was solved by deleting old spools from SP01. thanks for the help