Title
Monitoring and Logging Archiving Runs

Purpose
The archiving monitor can display information that the archiving subproc
esses (analysis, write, delete, reload and pre-step) write in the applic
ation log and the activity log.
This means you can use the monitor to monitor current archivingprocesses and to view their progress.
You also have the option of interrupting archiving processes that arerunning, in a controlled manner.

Integration
API module APPL_LOG_DISPLAY is used to depict the application log.
The lists in the activity log are depicted by the ALV Grid Display andthe ALV List Display.
To depict the job overview, API modules BP_JOB_SELECT andBP_JOB_MANAGEMENT are used.

Prerequisites
The user has read access authorization for all archiving objects.
One of the following must be running or have run: An archiving run (anal
ysis, write, delete), reload or pre-step. The application and activity l
ogs are being or have been filled in during the process.

Features
The archiving monitor displays information that is logged during an arch
iving run. This includes the following:

• Activity log


• Application log


• Job list


• Archiving runs and archive files


• Package list

An external identification is also included in the activity log. This id
entification is used to group together the logs from related archiving s
ubprocesses (analysis, write and delete). Archiving runsbecome related if, for example, the analysis run starts the subsequentwrite job or the write job starts its delete job. These run variants aredependent on the global control of archivingand the AOBJ basic settings, and are maintained there.
Since archiving runs and pre-steps are generally long-running processes,
the archiving monitor has a refresh button on the display list for the
activity log and the package list. When you press thesebuttons, the current status or package information is read from thedatabase again and displayed immediately.
The activity log records the status of the archiving runs. The statusesare explained below:
0: The program/archiving run has been started.
10:The parallel processing for the archiving run has beenstarted. This status indicates the start of the preliminary phase ofparallel processing.
20: The "Generate Package Templates" phase has been completed inparallel processing and the mass run started immediately afterwards. Theparallel mass runs themselves cannot update a status since theconnection between the mass run and the activity log is not specifiedclearly in this phase. You can view the progress of the parallel massruns in the package list.
30: The "Mass Run" phase has been completed within parallelprocessing. The point of synchronization has been reached. If thearchiving run is not related to any subsequent runs, this statusindicates a successful end to the run.
31: This status can only be given to an analysis run. Itindicates that the subsequent write job has been started automaticallyand that the analysis run has been completed successfully.
32: This status can only be given to a write run. It indicatesthat one or more subsequent delete jobs have been started automaticallyand that the write run has been completed successfully.
40: This status indicates that parallel processing has beenterminated. To analyze the errors, you can use the application log andthe corresponding job logs from the job overview.
50: The program has been completed successfully.
During the "Generate Package Templates" phase, the system writes a statu
s entry in the database for each generated package at the start of the p
arallel processing. The packages therefore initially have thestatus "Planned". During the actual mass runs, individual packages areprocessed by the package administrators and have the status "InProcessing". The number of data records processed from the masterapplication table continues to be updated at regular intervals. When apackage is completed successfully, the status is set to "Completed".

Selection
The selection screen is divided into three areas:


• Identification

Here you can make a selection using the activity ID. The externalidentification enables you to select related archiving runs.

• Object

You can use the object name to restrict the selection of an archiving ob
ject. Other options include specifying the program name and category or
the application type. However, the application type is onlyuseful for parallel processes such as the analysis or write run.

• Restrictions

In this area, you can restrict the selection by entering the user or thedate and time of an archiving run. Today's date is set as default for th
e date. You can make other restrictions for the archiving mode (test,simulation, productive) and the archiving run status.

Output
The first basic list contains the data from the activity log. Thisincludes:


• The date and time of the archiving run


• The external identification connecting the related archiving runs


• The program name of the archiving process


• The program category to identify the archiving process (pre-step,
analysis, write, delete, reload or interrupt)

• The archiving object processed by the archiving run


• The application type from parallel processing


• The archiving mode (test, simulation, productive)


• The user who started the archiving run


• The status of the archiving run. For processes that are r

unning, this is the current status. For processes that have been complet
ed, this is the final status.

• The message object and the date of the application log. T

he date determines as of when the application log can be deleted by reor
ganization runs.
You can use the refresh button to read the current log entries from thedatabase. This means you can monitor an archiving process continuously.

Activities
You can branch from the basic list to other list displays via theGoto menu option by selecting an activity log entry. Theseare as follows:


• Application log

Here you can branch to transaction Evaluate Applicatio
n Log (SLG1).

• Job list

The job overview displays all the jobs belonging to an archiving run orto related runs. Here you are given the other standard functions of tran
saction Job Overview (SM37), such as displaying the
spool or the job log.

• Archiving runs / files

This lists the files generated by the parallel jobs during a write run,along with their higher-level archiving run assignments. This shows whic
h archiving run or group of related archiving runs has generated which f
iles.

• Package list

Here you can display the information that the parallel jobs write in the
database for each package during the mass run. The status is logged her
e (Planned, In Processing and Completed), as is the number ofdata records processed per package, the name of the job, the duration ofthe job and the limits used for the database selection. If you press therefresh button, you can read the current package list from the database,allowing you to monitor the progress of the package continuously.

• Interruption

An archiving process that is running can be terminated in a controlled m
anner. If this is done, all parallel jobs are terminated and the archivi
ng runs generated concluded. The interruption of
archiving processes is recorded in the application log.

• Archive administration

Here you can branch to transaction Archive Administra
tion (SARA).

• Sequential read program

You can use this menu option to branch to the sequential read programs s
tored for the selected archiving object in the basic setti
ngs (AOBJ). If more than one read program is
maintained there, you must first choose the program you want from a sel
ection box. The archive files belonging to the archiving runare transferred to the read program immediately, meaning you do not haveto make any other upstream selections.