Hi bhaskar,
Please follow the instructions from SAP note <a href="http://service.sap.com/sap/support/notes/48284">48284</a> (Creating
more than 32000 spool requests) to allow more spool requests
to be created if this is currently being reached. Client
000 for transaction SNRO will show the current range for this
system. Not using client 000 for the increases is sometimes
the reason for differenece in behaviour between what
you expect and not.
I have outlined main steps below for a change in total amount of
spool requests as follows:
1) First set the current number to 0 in SNRO for SPO_NUM so that t
interval can be changed. (N.B. This must be done in client 000)
2) Change the interval upper limit as required. This is dependant
on the needs of the system as discussed in the notes. Many customers
use the 99000 limit by default.
3) Set the new current number to the old maximum value (99,000?)
- you do this to avoid duplicate spool numbers being generated.
4) Set the other parameters as detailed in the note...
rspo/spool_id/max_number also to the new value (e.g. 200,000).
Set rspo/spool_id/loopbreak to 99,000 (or new upper limit - whichever is
lowest).
Changing these parameter values using Transaction RZ10 leads to an error
message. You can ignore this message. These parameters must be set
on all instances. But these parameter values are only of use should the
number range server not be available - so spool numbers will continue
be allocated from the number range under 'normal' conditions - so you
can schedule a restart of the system at an appropriate time for these
parameters to take affect. Changes in SNRO -> SPO_NUM do not
need a restart to come into effect.
You should fully review note <a href="http://service.sap.com/sap/support/notes/48284">48284</a> before making any changes.
Regards, Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.