Location for Storing Spool Data 
Use the following parameter to specify where the spool system is to store its data:
· rspo/store_location: Specifies whether the spool system is to store data in the SAP database or in files in the host system.
Possible values
- db: Spool requests are stored in the database in table TST03.
Advantage: Spool files are protected by the backup and recovery mechanisms of the database system.
- G: Spool requests are stored in the standard SAP "global" directory: /usr/sap/C11/SYS/global/ (UNIX Systems).
Advantage: Faster access to spool data; more flexibility. Disadvantage: Files are not protected by database backup and recovery mechanisms.
Specifying a path name other than the predefined path is not recommended. Should this be absolutely necessary, you can alter the path name in the file rsts/files/root/G. You should not change the file naming convention specified in the file.
Also ensure that the directory is accessible to all instances in your SAP system and that the directory is the same for all instances.
Enter the db and G values exactly as shown; the capitalization is important.
The reports that check spool/TemSe consistency (RSPO0041) and which reorganize the spool and TemSe (delete old spool requests, RSPO0043) are able to handle both database and file system storage.
In principle, the TemSe storage method can vary among the application servers of an SAP system. In practice, SAP recommends, however, that the entire SAP system uses a single storage method for TemSe objects.
The following table summarizes the advantages and disadvantages of each type of storage:
File System or Database Storage for TemSe Objects?
Type of |
|
|
File System |
Relatively fast: better performance |
TemSe data must be backed up and restored separately from the database using operating system tools, . In the event of problems, it can be difficult to restore consistency between the data held in files and the TemSe’s object management in the database. |
Database |
Back-up and restore with database tools. Consistency is ensured. |
Slower than file system storage. Increased database load. |
Hard disk requirements: In some cases, spool data may occupy several hundred megabytes of disk storage. If you use the G option, you must ensure that enough free disk space is available for spool data.
Naming Convention: The naming convention used for spool files, as well as all other TemSe objects (currently background processing job logs), is as follows:
- Files are stored by type and client of origin in a subdirectory with the name <client><first five characters of object name>. The object name is specified in table TST07.
Examples: 001SPOOL (spool requests directory, client 1), 001BCTLG (background processing job logs, client 1).
Within these directories, the data belonging to a TemSe object is held as a individual file. Spool data, for example, is held in files that are named with the ID numbers of the spool requests.
You can also determine
the storage location by output device.
