SAP Note 13620 - Resetting periphery spool and batch input data

Symptom:

When you repeat a client copy of a previously configured client (e.g. the new client is to be overwritten), the question arises. what happens to the spool and batch input datasets?
Some of them are stored as Unix files, and are removed from at least immediate system control.

Solution

Releasing files for spool requests in an old client
----------------------------------------------------

- All spool datasets are stored in Unix subdirectory

usr/sap//sys/global/SPOOL and
" /JOBLG

where = your current 3-character system ID, e.g. C11 and = your current client. The only way to release the resources that are in use is to delete all the files in both these subdirectories. Of course, you should only delete the files after the client has just been reset.

The file names defined there are stored in SAP internal tables (TST0*). However, these tables are not changed by RSCLICOP during a client copy because they are formaly non-client specific and belong to table class L.
However, it is possible that the contents of the tables can
be deleted due to a client transport between systems or due to
a client reset (R3trans). In this case, the spool files remain
in the subdirectories, mentioned above, without any logical reference.


Releasing batch input sessions
------------------------------

Batch input sessions and logs are deleted using transaction SM35.
The folders are stored client-specific. Tables APQI and APQD contain the data. The client copy does not affect these tables, as they formally count as non-client specific.

Key word: R3SLMODCC