Archive Reader
Information about old executions and reports can be extracted from the database using the Archive Utility. The data will be stored as text files that can read with the Archive Browser. Main restrictions of this programme are its platform-dependency (Microsoft Windows), it only has a graphical user interface and it can only read one dataset at once. The module ArchiveReader does not have one of these restrictions.
Designation
- Name
- util.ArchiveReader
- Aliases
- ArchiveReader
Configuration
- Optionen
- Ausgabe
- Archive directory (
archive-dir) - Directory containing the archive folders starting with UC_ARCHIV
- Object name (
name) - Just checks records of objects matching the pattern
- Begin timestamp (
begin) - Beginning of time period
- End timestamp (
end) - End of time period
- Fields (
fields) - Defines the fields to save in the CSV file
Valid values
Object name (name), RunID (runid), Object type (type), Activation time (time-activate), Start time (time-start), End time (time-end), Status (status), Message (message), Report Data (repdata), Report Type (reptype)
- Report Types (
report-types) - Defines the relevant report types that should be read from the archive
Valid values
Activation report (ACT), Client report (CLNT), Runtime report (LOG), SYSLST report for BS2000 jobs (LST), Object report (OBJ), Agent report (PLOG), Post-Process report (POST), Internal report (PP), Job report (REP), Script report (REV0), JCL report (REV1), Object access report (REV2), Application report for SAP jobs (ABAP jobs) (SAPL), Statistics report for SAP jobs (Java Scheduler Jobs) (SJJI), SAP system-log report for SAP jobs (SLOG), Structured job report (SREP), Spool-directory for SAP jobs (ABAP jobs) (SSPL), statistics report for SAP jobs (ABAP jobs) (SSTC), Step-list report for SAP jobs (ABAP jobs) (SSTP), RA report 001 (#001), RA report 002 (#002)
- Object Types (
object-types) - Defines the relevant object types that should be read from the archive
Valid values
Event (EVNT), File transfer (JOBF), Job (JOBS), Workflow (JOBP), Schedule (JSCH), Script (SCRI), Notification (CALL), Job group (JOBG), RemoteTaskManager (JOBQ), User (USER), Client (CLNT)
- Task states (
states) - defines the task status a task must have
Valid values
ANY_ABEND (ANY_ABEND), ANY_OK (ANY_OK), ANY_SKIPPED (ANY_SKIPPED), ENDED_CANCEL (ENDED_CANCEL), ENDED_EMPTY (ENDED_EMPTY), ENDED_INACTIVE_OBJECT (ENDED_INACTIVE_OBJECT), ENDED_INACTIVE (ENDED_INACTIVE), ENDED_NOT_OK (ENDED_NOT_OK), ENDED_OK (ENDED_OK), ENDED_OK_OR_EMPTY (ENDED_OK_OR_EMPTY), ENDED_OK_OR_INACTIV (ENDED_OK_OR_INACTIV), ENDED_SKIPPED (ENDED_SKIPPED), ENDED_TIMEOUT (ENDED_TIMEOUT), ENDED_UNDEFINED (ENDED_UNDEFINED), ENDED_VANISHED (ENDED_VANISHED), FAULT_ALREADY_RUNNING (FAULT_ALREADY_RUNNING), FAULT_NO_HOST (FAULT_NO_HOST), FAULT_OTHER (FAULT_OTHER), USER_100_200 (USER_100_200), USER_147 (USER_147), USER_201_299 (USER_201_299), USER_300 (USER_300), USER_500_600 (USER_500_600)
- Output file (
csv-file) - Filename of the output file in CSV format
- show in tabular view (
cvs-show) - Additionally to the file in CSV format the result is shown in a table
- CSV file mode (
csv-mode) - The mode 'overwrite' will overwrite existing files and the with 'append' the new data will be appended to existing files
Valid values
Overwrite (overwrite), Append (append)
- Object for structured documentation (
structured-docu) - If given the information are stored in the structured documentation of the object
- empty structured documentation first (
structured-docu-reset) - if set the structured documentation of the object is emptied first
- Connection (
structured-docu-connection) - if given the object for the structured documentation is used in the given connection
Valid values
<TabItem value="b4A Connections">
- Name of structured documentation (
structured-docu-name) - Defines the name of the tab of the structured documentation that should be used. If empty the first one is chosen.
Description
The ArchiveReader supports the reading of executions and reports. reports. The data can be filtered using the following criteria:
- Object name
- Object type
- Start and end time
- Execution status
- Report type
The results of the analysis are saved in a file in CSV format. format. In addition, the results can also be saved in the structured documentation of an object.