cancel
Showing results for 
Search instead for 
Did you mean: 

Note 1422843 - Wrong deletion date in spool request

tj_wilkinson2
Participant
0 Kudos

We got the following information from our SAP Support contact on Monday:

****

Problem as follows: As soon as the retention time of a spool request exceeds 2009/12/31, a wrong date 2100/01/01 is entered during creation of the spool request. As a consequence these spool requests will not be deleted anymore from the spool reorg jobs.

SAP Note 1422843 describes in more details and will be updated on 1/8/2010 with a kernel patch. There are corrective actions in the note, but if you have a problem with this, you can enter a message in component BC-CCM-PRN.

****

Last night our spool overflowed. I was able to manually clean up some older entries. This morning when I got into the office, I attempted to download the patch mentioned in the note, and begin moving it through the landscape, but it doesn't appear that it's available.

The note mentions SAP KERNEL 7.00 64-BIT UNICODE 238. I assume this is the dw patch 238? I didn't see any patches at level 238 available.

Our current spool limit s 99,999. We found the following parameters to be set to 99,999 and they each claim they can't be raised beyond that:

rspo/spool_id/max_numbe

rspo/spool_id/loopbreak

We also found a note (48284) that mentions we can change the max spool number by changing number range SNRO.

If we change the number range, will the max spool still be constrained by the parameters I mentioned?

Thanks for any insight you might have.

~TJ

Accepted Solutions (1)

Accepted Solutions (1)

volker_gldenpfennig
Active Participant
0 Kudos

Hi TJ,

yes, you are correct !

If you extend this value, you need to lift at least one of these parameters ...

Are you using "very old spoolfiles" in your system ? Or why is the mentioned workaround not of use for you ?

I always prefer to delete all old stuff after let's say 20-40 days and this works fine ... the question is, how fast you create the spoolfiles ...

The kernel patch will come out in the next days ... but I would at least think on a different solution ... otherwise, you have to patch up to PRD VERY fast ...

Regards

Volker Gueldenpfennig, consolut international ag

http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de

tj_wilkinson2
Participant
0 Kudos

Hello Volker, thank you for the response. We delete anything older than 10 days and use RSPO0041. However, because of the mentioned issue, it's not cleaning them up anymore. We generate alot of spool - close to 99,999 in 10 days.

Maybe I'm confused by the note. There are two steps listed and I thought we had to do both to fix the issue. It sounds like from your response there is a workaround, which would be step 2 (changing the variant to match the attachment). Is this correct?

Thank you sir.

~TJ

volker_gldenpfennig
Active Participant
0 Kudos

Hi TJ,

yes, you are more or less correct ))

But, as you are using a report RSPO0041 instead of RSPO1041, I didn't check, if the old one (since about 8-10 years no longer suggested), does support the solution as well. But, RSPO1041 works perfect ))

If you do have other questions, just give me a call ...

Regards

Volker Gueldenpfennig, consolut international ag

http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de

tj_wilkinson2
Participant
0 Kudos

Thank you for your help Volker.

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello,

Does anyone have any information on when the kernel patch for this is set to be released. This is starting to become a bit of an issue with our system Any information anyone has would be appreciated.

Thanks

Former Member
0 Kudos

Hallo,

The relevant patches have been delivered to the service marketplace for the releases 4.6D thru 7.10 with the exception of 7.00, where the patch had to be withdrawn due to an unrelated problem. The patches for release 3.1 thru 4.5B are a special case, as these releases are out of maintenance and patches will only be produced when requested under the rules for customer specific maintenance, as laid down in SAP note 52505. We will reinstate the 7.00 patch as soon as possible and are working to solve the problem.

I hope that this answers your question.

Regards,

Sally Power

For SAP on IBM i Development Support

Edited by: Sally Power on Jan 25, 2010 12:42 PM