If you run the consistency check during productive hours, files will appear to be in error when they are actually fine. Instead, they are in the middle of processing (entry in TST01 but not TSP03, etc.). This can cause errors to appear on the consistency check every time the check is run, until it is run at such a time when there is no activity.
One solution is to check the log number of you last batch job and check the current spool request number (by test-printing, etc.). Then, after the consistency check, delete all jobs except those close to the current numbers.
Regards, Mike D. Martin SAP Basis Administrator SOLA Optical, USA 707-763-9911 x6106 mmartinZs...
-----Original Message----- From: Betsy Strebe [mailto:bstrebeZs...] Sent: Tuesday, January 16, 2001 10:02 AM To: sap400Zm... Subject: TemSe problems with job logs.
This morning we are having a lot of fun with TemSe issues. After the PRD system came up this morning, none of the background jobs after that time would complete. All canceled out, and the job log can not be displayed due to TemSe errors. We did a consistency check in SP12 and SPAD. The consistency check in SP12 listed errors, which we deleted. But the TemSe errors just keep coming up. The background job to cleanup spools and TemSe does run everynight, but it also crashed this morning. Any ideas?
[Non-text portions of this message have been removed]