Storage Methods for Spool Objects in TemSe

Storage Methods for Spool Objects in TemSe Use You can use the profile parameter rspo/store_location to set up the TemSe database to store spool request data either in the SAP database (default parameter db) or in the file system of the host operating system (parameter value G).

Note Note

The default storage method for TemSe objects is specified in the system profile of each SAP application server.

You can therefore theoretically specify different storage methods for different servers. However, we strongly advise against this, as only restricted data access is possible in this case.

End of the note.

Further, you can set the storage location individually by SAP output device if required. Unless you have special requirements with respect to a particular device, it is best to use a uniform storage method across the entire SAP System.

The following table summarizes the advantages and disadvantages of each type of storage:

Storage Method	Advantages	Disadvantages
File system	Quickly Better Performance	TemSe data must be backed up and restored using operating system tools, separately from the database. In the event of problems, it can be hard to restore consistency between the data held in files and the TemSe’s object management in the database.
Database	Standard security measures Restore using database tools Consistency is ensured	Slower than file system storage Increased database load

Details for Storage in Files

If the data is stored in files, the TemSe manages object management records for its objects in the SAP database. However, it stores the object data, including the spool data, in files. By default, these files are stored in the following global SAP directories:

Unix installation: /usr/sap/<SYSTEM ID>/SYS/global
Windows: \\sapglobalhost\sapmnt\<system ID>\global

You can specify an alternative directory with the rsts/files/root/G system profile parameter.

For more information, see Storage Location for Spool Data.

Files are held in directories that are named for the client (three digits) and the type of TemSe object (five characters, as specified in table TST07).

Example Example

001JOBLG contains logs for background jobs that were performed in client 001.

026SPOOL contains spool data for client 026.

Within these directories, individual spool files are named with the spool request ID number (such as 00013152).

End of the example.

The reports that check spool/TemSe consistency (RSPO0043) and that reorganize the spool and TemSe (delete old spool requests, RSPO0041) are able to handle both database and file system storage.

More Information

TemSe Data Storage

SAP Printing Guide Start Page