on 04-18-2013 12:41 AM
I have a background job that reads an input file and writes errors to the spool, we are having intermtiant problems with the spool with this job.
Most of the time this job works fine the spool thumbnail is on the job in SM37 and I an view the spool fine from SM37 or SP01.
The odd time I get spool issues, this is presented in a couple of different ways:
This job has been run daily for 4 months now, we have only seen this problem on 2 times. I can take these 2 files and run them on any of our test systems and get the same result. If I run the program in the foregound the program everything is fine.
Any ideas?
Thanks,
Jerry
Hi,
maybe here you can find a solution.
http://www.sapossnotes.com/2010/12/sap-note-11733-write-or-rollback-work.html
Vin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
I have the same issue there linked to an SAP standard program rglexe00 therefore I don't think that I can apply any development solution.
Have you found a solution to this problem ?
Best Regards, Manuel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Jerry
I just tried your code however when I use the NOCOMMIT = 'X' then the INS action does not work and I do not create the record that I need to create not sure how this is working for you ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
William, after seeing your comment I looked at this again and found that this change never made it into production. Higher priority work came up and we had to put it back on the shelf. Unfortunately I dont' have time to get into this now.
Here's a thought if you moved the WRITE outside of the INFOTYPE update loop can you remove the NOCOMMIT parm again?
Hi,
We encountered this same error message, where all the spool of one job were getting this error. But spools of other jobs in the system were fine.
In our case, the line size of the output is larger than the maximum width of the spool format (255 character). When we checked the source code, the source code is written in ALV (ABA List Viewer) format which is why the error occurs.
The permanent solution is to rewrite the source code from ALV to 'WRITE' commands so that the spool can be truncated to the first 255 characters and viewed in sp01.
A temporary workaround is to save the output of the report into the SapWorkDir via "Spool Report > Export as Text".
Br,
Prabhakar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Having the same problem, can you share how to solve it
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
CORRECTION - This change was NOT fully tested and did NOT make it into production. Higher priority work came up and we have not gone back to this. I apologize for the confusion.
Little late with a suggestion here, but on your sm37 screen can you issue a /osu53 and see if you have authorizations? Or at the very least do a su53 on both sm37 & sp01 and verify that authorizations are not your issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.