Logs
This function provides a central access to the logs generated during data archiving. It can be called from within Archive Administration by choosing Logs or Goto → Logs, and also from Archive Management.
The following logs are written when an archiving program, such as a preprocessing, write, or delete program, is executed, and can be displayed in this function:
● Job Overview
Information on the background jobs of the archiving program
● Job Log
Log of the different steps of an individual background job
List generated by the archiving program and stored in the spool
● Application Log
Log of all processed objects (summarized and detail)
Job overview, job log and spool list are only generated by programs that are executed in the background. The application log can be generated for programs that run in the background and in dialog mode.

Whether or not the log of the processed objects is to be updated in the application log, meaning that an application log is generated, can be set in the variant maintenance of the corresponding program in the entry field Log Output. See Variant Maintenance for Archiving Jobs.

Keep in mind that not all archiving objects offer the updating of an object log (entry field Detail Log in the variant maintenance).
In the log function, the left area of the screen shows the available logs, organized by archiving object, action (for example preprocessing, write, delete, etc.), date and time. The newest log is highlighted. If cross-archiving-object logs were created, you can view them at the end of the log tree under the entry Cross-Archiving-Object (see below).
In the Process Control column, you can see whether the program was started in the test or the production mode. If the process control could not be determined, the field remains empty.
The Archiving Session column contains the number of the archiving session that was generated by the corresponding program (for write programs) or processed (for example by delete programs). If the session number could not be determined (for example by preprocessing programs), the field remains empty. In case of reload programs, the Original Session column contains the number of the reloaded session.
Due to technical reasons, the job overview, the job log and the spool lists can only be displayed as fullscreen.
The Application Log is displayed directly in the right part of the screen. It provides the user with a progress report of all business objects that he or she selected for processing. In the case of the write program, for example, the user sees which business objects have been archived and which could not be archived and for what reason.
The two tabs
provide the options of viewing a summarized and a detailed application log (if
available). If detailed information is available for an object, it can be
displayed via the looking glass symbol (
) in the Detail column. Click on the question mark
symbol (
) in the Long Text column to view the long text for
the corresponding message. If no application log was generated, a
corresponding message text appears. Possible reasons for this are, for
example, that the archiving program in question does not support this function
or that the user specified that the log output should go into the list (spool)
and not the application log.
Cross-archiving-object logs are created during the execution of the cross-archiving-object check and delete function. In the log display these logs appear at the end of the log tree under the Cross-Archiving-Object heading. The logs are sorted by action, date and time of the action, and archiving object. For example, if you want to display the logs of all archiving objects for which the system performed a cross-archiving-object check, expand the Preprocessing node in the tree structure under the above-named heading and double click the node with the desired date. In the right area of the log display the application log of the cross-archiving-object check session you have chosen appears. In the summarized view the log contains a consolidated list of all summarized log messages of the archiving object included in the check (these are listed as subnodes in the log tree). Due to performance reasons, the detail messages of the different archiving objects are not included in the detail view.
On the next lower level, meaning on the level of the archiving objects, it is not possible to display information. When you choose a node (document symbol) below the archiving object the messages for this particular archiving object are shown in the form of a summary and as detail information
● You can limit the display of the logs to one specific archiving object by entering the object in the initial screen of Archive Administration. If you want to access the logs of all archiving objects, you must leave this field empty.
● To display the log for a specific log entry, select the entry in the log entries list and with a right mouse click choose the corresponding log, for example the job log or the application log.
● To display only cross-archiving-object logs, first choose Check/Delete in Archive Administration and then Logs.
●
You can delete
selected application logs from the system via Goto → Application
Logs. This function corresponds to the central delete function of logs
using
transaction SLG2,
the only exception being that the object ARCHIVING is already entered per
default.
See also:
Variant Maintenance for Archiving Jobs