The program RSARCHD runs outstanding delete jobs for archive files from incomplete, valid archiving sessions for an archiving object. You can launched the program using transaction code SE38.
Selection
- Object name: Name of the archiving object for which delete jobs are to be run
- Max. number of files: Maximum number of files for which delete jobs are to be created
- Max. number of sessions: Maximum number of archiving sessions from which files are to be selected
- Max. number of jobs: Maximum number of delete jobs that can be run or scheduled at the same time (cross-client and cross-archiving object)
- Started by: Only archiving sessions that were run by the specified user are selected
- Background user name: User name that is used for authorization checks in connection with the delete jobs
- Test mode: Do you want to use the test mode variant instead of the live run variant of the delete program?
- Wait for job end or termination: Should RSARCHD run until all scheduled jobs end or at least one of them is terminated? (In the case of a termination, RSARCHD is also terminated.)
- Process all files: Should RSARCHD schedule delete jobs until the number of archive files indicated through the parameters Max. Number of Files and Max. Number of Sessions has been processed?
Activities
When selecting archive files for which you want to create delete jobs, these are processed in the order in which they were created: The files with the smallest key from the session with the smallest number are processed first.
Sessions marked for archiving with BC_ARCHIVE and sessions from another client in a client-specific archiving object are not selected.
Provided the maximum number of permitted delete jobs has not been exceeded, the delete jobs are scheduled to be run immediately. Otherwise, they are not scheduled at all.
If all files from [n] sessions for selection are to be processed in parallel delete jobs, no delete job is created for a file from session [n+1].
Delete jobs are carried out by the relevant server group if this has been set up in cross-archiving object Customizing; the jobs are distributed to the individual servers by the usual background processing system.
The spool parameters for the delete jobs are specified either in a user dialog box or – if RSARCHD is running (even in the background) – they are copied from the current job.
The names of the jobs are different from those that were created for delete jobs by ADK or SARA. Instead of using year and time, the first 10 letters of the archiving key is used.
