Reads the system log of an SAP system during a specified time period.
Transaction: SM21
Interface: Standard
R3_GET_SYSTEMLOG
FILE=...
[,SERVER=...]
[,FROM_DATE=...]
[,FROM_TIME=...]
[,TO_DATE=...]
[,TO_TIME=...]
Syntax |
Description/Format |
---|---|
FILE= |
Name of a file to which the read SAP system log should be stored. |
SERVER= |
Name of an SAP applicationAn application is a software which helps a user to fulfill specific tasks. In the context of ARA see also: Application entity. server. The name of an SAP application server must
be specified in the form Host_SID_SYSNR: |
FROM_DATE= |
Start date of the selection from the system log. Default value: "20010101" |
FROM_TIME= |
Start time of the selection from the system log. Default value: "000000" |
TO_DATE= |
End date of the selection from the system log. Default value: current date |
TO_TIME= |
End time of the selection from the system log. Default value: "235959" |
ENCODING= |
Encoding for the generated output file (Parameter FILE=). For example: UTF-8 Default value: ISO-8859-1 When you specify an encoding that is not supported or invalid, the jobAn Automation Engine object type for a process that runs on a target system. will abort with an error message. The SAP Forms provide an input assistant for this field which lists all the supported encodings. |
This script element is used to read the system log of an SAP system as text and saving it to a file. If the name of an application server is specified, the script element supplies this server's system log. Without the name of an application server being entered, the central SAP system log is read.
You can also prepare and edit the system log using the script elements for the data sequences. R3_GET_SYSTEMLOG is used in the eventAction that is triggered if particular conditions apply. It can be an Automation Engine object type or an entry in a Policy Orchestrator EventBase. job "EVENT.R3SYSLOG" in clientA closed environment within an Automation Engine system where you can create and run objects. A client name consists of a 4-digit number that must be indicated when a user logs on to the Automation Engine system. Users and their rights are also defined in clients. A particular Automation Engine object type. 0000. The script functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,… PREP_PROCESS can be used to create a data sequenceAn internal listing of Console outputs or lines of Variable objects, etc. The lines of a data sequence can be accessed by using a PROCESS loop or the script element GET_PROCESS_LINE. The script elements PREP_PROCESS* generate data sequences. with the system log's data.
The data sequence is processed with the script statements :PROCESS and :ENDPROCESS. Each individual line of the data sequence and its columns can be accessed with the script function GET_PROCESS_LINE.
Note that by default, created files are saved on the computer on which the agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host has been installed (for example, R3_GET_JOB_SPOOL; FILE=).
The following example reads the central SAP system log of the previous week. The start date for the system log selection is calculated using the script function SUB_DAYS. The current date is the basis of this calculation.
:RSET &TODAY# =
SYS_DATE ('YYYYMMDD')
:RSET &LAST_WEEK# = SUB_DAYS ('YYYYMMDD:&TODAY#', 7)
R3_GET_SYSTEMLOG FILE = 'c:\t46_systemlog.txt', SERVER=, FROM_DATE='&LAST_WEEK#'
See also:
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |