ABAP Job Statistics Test

This test monitors the distribution of background jobs according to the job status. Apart from monitoring the overall job execution, this test helps to debug issues that occurred due to long running jobs, aborted jobs and jobs with high start delays.

Target of the test : A SAP ABAP instance

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for every SAP ABAP instance being monitored.

Configurable parameters for the test
Parameter	Description
Test Period	How often should the test be executed
Host	Host name of the server for which the test is to be configured.
PortNo	Enter the port to which the specified host listens.
ClientName	Specify the ID of the client system as what the eG agent will be connecting to the SAP ABAP instance. To know how to determine the client ID to use, follow the instructions provided in Determining the Client ID/Name for the eG Agent to Connect to the SAP ABAP Instance.
SAPUser	Typically, to connect to a SAP ABAP instance and run tests, the eG agent requires the permissions of a SAP user who has been assigned with certain authorization objects. Ideally, you will have to create a new user role on the SAP ABAP instance for this purpose, associate the above-mentioned authorization objects with that role, and assign the new role to an existing SAP user. The procedure for the same has been provided in Creating a New User Role for Monitoring and Assigning it to a SAP User. Once the new role is assigned to a SAP user, specify the name of this user against SAPUser.
Password	The password of the specified SAPUser.
Confirm Password	Confirm the password by retyping it here.
SysNo	An indicator of the TCP/IP port at which the SAP server listens. For example, for a server that listens at port 3200, the SysNo will be ‘00’. Similarly, if the SAP server port is 3201, the SysNo will have to be specified as ‘01’. Therefore, in the SysNo text box specify the system number of the SAP server with which the specified client communicates. To know the system number for the ABAP server being monitored, follow the procedure detailed in Identifying the SAP Router String and System Number.
Router	If the SAP client with the specified ClientName exists in a network external to the SAP server, then a router will be used to enable the server-client communication. In such a case, specify the router string of the router in the Router text box. If both the client and the server exist in the same network, then specify ‘none’ against the Router text box. To know what is the SAP Router string for the ABAP server being monitored, follow the procedure detailed in Identifying the SAP Router String and System Number.
InstanceName	This is set to none by default. This implies that the eG agent automatically discovers the instance name at run time.
Timeout	Indicate the duration (in seconds) for which this test should wait for a response from the SAP ABAP instance. By default, this is set to 120 seconds.
JCO Version	The eG agent uses the SAP JCO library to connect to the SAP ABAP system and pull out metrics. To enable the eG agent to make this connection and query the metrics, you need to specify the version of the SAP JCO library that the agent needs to use. For instance, to instruct the eG agent to use JCO v2.1.19, it would suffice if you specify the ‘major version number’ alone against JCO Version – in the case of this example, this will be 2.x. Note that if you have downloaded the SAP JCO CONNECTOR files for SAP JCO version 3 from the SAP market place (as instructed by Downloading the SAP JCO Connector files Required for Monitoring ), then the JCO Version configuration should be 3.x.
MaxLogLines	In order to troubleshoot the jobs that were aborted, the eG agent facilitates collecting the last n lines of the jobs that were aborted. To achieve this, specify the number of lines of an aborted job that needs to be retrieved for troubleshooting in the MaxLogLines parameter. By default, the value of this parameter is 3.
LongRunningCutoff	Specify the time duration in hours beyond which a job is classified as a long running job in the LongRunningCutoff text box. The default value specified in this text box is 0.8 hours.
HighDelayCutoff	Generally, there may be a permissible time delay while a job is started. Specify the duration of such time delay in seconds beyond which the job is classified as a job with a higher start delay in the HighDelayCutoff text box. The default value specified in this text box is 60.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Active jobs	Indicates the number of jobs of this priority class that are currently active.	Number
Ready jobs	Indicates the number of jobs of this priority class that are waiting for execution by the background work processes.	Number	A low value is desired for this measure. If there is a sudden/gradual increase in the value of this measure, then it indicates that the background work processes are insufficient to execute the jobs. Therefore, administrators may need to check the number of background work processes and provision them accordingly.
Long running jobs	Indicates the number of jobs of this priority class that have been running for a duration longer than the cutoff time specified in the LongRunningCutoff parameter.	Number	Generally, the jobs may be classified as a long running job when the job is stuck during execution and loops the execution several times without completion. A high value for this measure is a cause of concern as long running jobs consume too much of resources thus leading to the performance degradation of the SAP instance. The detailed diagnosis of this measure if enabled, lists the name of the job, job count, report name, user details, timestamps, duration etc.,
New jobs	Indicates the number of jobs of this priority class that were started during the last measurement period.	Number	A gradual decrease in the value of this measure is a cause of concern. Administrators may need to check the number of background processes that are free and provision them according so that the background processes can execute the jobs continuously.
New jobs with start delays	Indicates the number of jobs of this priority class that started with a delay time greater than the time specified against the HighDelayCutoff parameter while configuring the test.	Number	A low value is desired for this measure. The jobs may be started with a delay due to various reasons such as unavailable background work processes, scheduling issues between the originating server and target server, other dependencies etc., This measure helps detect such issues by providing the details of these jobs including the exact start delay in milliseconds.
Aborted or cancelled jobs	Indicates the number of jobs of this priority class that were cancelled/aborted during the last measurement period.	Number	Jobs may be abruptly terminated either manually or due to underlying program errors. Program errors could in turn be due to various issues such as authentication, file access, dead locks, updates, tablespace, memory, programming errors, dependencies etc., Therefore, a sudden/gradual increase in the value is a cause of concern which indicates severe performance degradation of the target server. The detailed diagnosis of this measure if enabled, provides details and logs for the aborted/cancelled jobs in order to facilitate troubleshooting.
Average job start delay	Indicates the average time delay experienced in starting the jobs of this priority class.	Milliseconds	Comparing the value of this measure across the priority classes helps you identify the class in which the jobs experienced the maximum start delay.
Finished jobs	Indicates the number of jobs of this priority class that completed execution during the last measurement period.	Number	A high value is desired for this measure. This measure is a good indicator of the performance of the background processing system. The higher the value of this measure the greater is the performance of the target server.