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 not generated in background mode

Former Member
0 Likes
556

Hi ,

I am fine tuning a report.

I am working on a program which is collecting data and exporting data into memory id. then two other reports, are importing data from memory and displaying in AlV/list.

When i execute this report in background the spool is not getting generated.

is there any way to generate the spool?

How to measure the execution time, as the program is taking much time and some times going to dump in case of time limit.

Thanks ,

Kiran

1 ACCEPTED SOLUTION
Read only

vinod_vemuru2
Active Contributor
0 Likes
512

Hi Kiran,

For measuring runtime use SE30 transaction. When u run in back ground it wont go to Dump. It may happen only in fore ground. If at all it happend in back ground, the reason might be different. Analyze that dump n see what is going wrong. Also i dont think there is any time limit in back ground as i executed jobs that ran for 11 days!!!!. U can alos debug the batch job.

put break point in ur program, Select that batch job in SE37, enter jdbg in command promt and press enter. Control will go to debug mode.

Which ALV u r using. I think through OOPS ALV batch job will not create spool i guess. Not sure on this.

Thanks,

Vinod.

Hi Kiran,

For measuring runtime use SE30 transaction. When u run in back ground it wont go to Dump. It may happen only in fore ground. If at all it happend in back ground, the reason might be different. Analyze that dump n see what is going wrong. Also i dont think there is any time limit in back ground as i executed jobs that ran for 11 days!!!!. U can alos debug the batch job.

put break point in ur program, Select that batch job in SE37, enter jdbg in command promt and press enter. Control will go to debug mode.

Which ALV u r using. I think through OOPS ALV batch job will not create spool i guess. Not sure on this.

Thanks,

Vinod.

2 REPLIES 2
Read only

vinod_vemuru2
Active Contributor
0 Likes
513

Hi Kiran,

For measuring runtime use SE30 transaction. When u run in back ground it wont go to Dump. It may happen only in fore ground. If at all it happend in back ground, the reason might be different. Analyze that dump n see what is going wrong. Also i dont think there is any time limit in back ground as i executed jobs that ran for 11 days!!!!. U can alos debug the batch job.

put break point in ur program, Select that batch job in SE37, enter jdbg in command promt and press enter. Control will go to debug mode.

Which ALV u r using. I think through OOPS ALV batch job will not create spool i guess. Not sure on this.

Thanks,

Vinod.

Read only

Former Member
0 Likes
512

closing questions