Service Report SAPreg GoingLivetrade Check Verification Session
Confidential
SAP System ID PRD
SAP Product SAP ERP 60
Status Productive
DB System DB2 UDB for iSeries V5R4M0
Processed on SSP
Release SOLUTION MANAGER 71
Service Tool 701_2010_1 SP25 - Service Content Update on 24072015
Date of Service 06082015 Session No 0010000000035
Date of Report 06082015 Installation No 0020265956
This report contains confidential customer data and may be viewed only by SAP AGS employees authorized SAP partners and customer employees Do not distribute it to other parties
SAPreg GoingLivetrade Check - Verification Session 06082015
1 Contents
1 Contents 1
2 Service Summary 4
Performance Indicators for PRD 5
3 Landscape 7
31 Products and Components in current Landscape 7
32 Servers in current Landscape 7
33 Hardware Configuration 7
4 Software Configuration For PRD 8
41 SAP Application Release - Maintenance Phases 8
42 Support Package Maintenance - ABAP 8
43 SAP Kernel Release 9
431 Downward Compatible Kernel 9
432 Issues with current SAP Kernel 10
433 Additional Remarks 10
5 Service Preparation and Data Quality of PRD 11
51 Service Data Quality 11
511 Quality of Data in Service Data Control Center (SDCC) 11
512 Quality of Service Data in Solution Manager Diagnostics - BW 11
52 ST-PI and ST-API Plug-Ins 11
53 Service Preparation Check (RTCCTOOL) 12
54 Performance DB (ST03 ST06) 12
55 Hardware Utilization Data 12
6 Hardware Capacity 14
61 Overview System PRD 14
7 Workload of System PRD 15
71 Workload By Users 15
72 Workload Distribution PRD 15
721 Workload by Application Module 15
722 DB Load Profile 16
8 Performance Overview PRD 18
Confidential Contents 139
SAPreg GoingLivetrade Check - Verification Session 06082015
81 Performance Evaluation 18
82 Transaction Profile Check 18
821 Transactions by Total Workload 19
822 Transactions by DB Load 19
83 RFC Load by Initiating Action 20
9 SAP System Operating PRD 22
91 Availability based on Collector Protocols 22
92 Update Errors 22
93 Table Reorganization 22
94 Program Errors (ABAP Dumps) 23
10 Security 24
101 ABAP Stack of PRD 24
1011 System Recommendations (ABAP) 24
1012 Default Passwords of Standard Users 24
1013 ABAP Password Policy 24
1014 Gateway and Message Server Security 25
1015 Users with Critical Authorizations 25
11 Software Change and Transport Management of PRD 27
111 SAP Netweaver Application Server ABAP of PRD 27
1111 Number of Changes 27
12 Data Volume Management (DVM) 28
13 ABAP Stack Configuration for PRD 29
131 Configuration for Central ABAP Instance sap1r3p_PRD_00 29
1311 Buffer Configuration 29
1312 Client Server Communication 29
1313 Enqueue Handling 29
1314 Obsolete Codepage Parameters 30
14 IBM i Database Checks 31
141 Important SAP Notes for IBM i 31
142 Reorganize Physical File Member 31
143 Missing Indexes 31
Confidential Contents 239
SAPreg GoingLivetrade Check - Verification Session 06082015
144 Disk arm utilization 31
145 Database Size 31
146 Backup Strategy 32
15 IBM i Specific Server Checks 33
151 iASP Configuration Check 33
152 Disk status 33
153 Data Protection in System ASP (ASP1) 33
154 Free space in System ASP (ASP1) 33
155 PTF Check 34
156 Disk Service Time 34
157 IBM i System parameters 34
158 SHRPOOL Pool 34
159 Paging Option 35
16 Trend Analysis 36
161 System Activity 36
162 Response Times 37
163 Application profile 37
164 System Operation 38
165 Hardware Capacity 38
Confidential Contents 339
SAPreg GoingLivetrade Check - Verification Session 06082015
2 Service Summary
The SAP reg GoingLivetrade Check (Verification Session) has detected severe problems that may cause you to lose business
We recommend that you take corrective action immediately
This report provides the results of the SAP reg GoingLivetrade Check (Verification Session) that was conducted on your SAP ERPsystem PRD Note The numbers in the Performance Overview PRD and Workload of System PRD sections refer to the time interval between 27072015 and 02082015 There is at least one area with critical performance system stability or security issues
The alert overview below summarizes the most important issues to be addressed Take corrective actions in these areas as soon as possible
ALERTS DECISIVE FOR RED REPORT
With the SAP kernel of your ABAP system the stability or consistency is at risk
ALERT OVERVIEW
A large number of deleted records have been found on the system
We found more than 30 ABAP dumps in your system
Standard users have default password
Secure password policy is not sufficiently enforced
A high number of users has critical authorizations
Perform the following Guided Self Services
Guided Self Service FAQ SAP Note
Security Optimization Service 696478
For more information about Guided Self-Services see SAP Enterprise Support Academy Register for an Expert-Guided Implementation Session for the Guided Self-Service at SAP Enterprise Support Academy - Learning Studio - Calendar
CHECK OVERVIEW
Topic Rating Topic Subtopic Rating Subtopic
SAP System Configuration
Performance Overview
Performance Evaluation
Workload Distribution
Workload by Application Module
DB Load Profile
SAP System Operating
Availability based on Collector Protocols
Confidential Service Summary 439
SAPreg GoingLivetrade Check - Verification Session 06082015
Topic Rating Topic Subtopic Rating Subtopic
Program Errors (ABAP Dumps)
Update Errors
Table Reorganization
Hardware Capacity
IBM i Database Checks
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
Security
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
Software Change Management
Number of Changes
Note All recommendations provided in this report are based on our general experience We advise that you test our recommendations before using them in your production system
Note If you have any questions about the accuracy of the checks in this report or the correct configuration of the SAP Solution Manager SAP reg GoingLivetrade Check (Verification Session) service create a customer message on component SV-SMG-SER
Note If you require assistance in resolving any concerns about the performance of the system or if you require a technical analysis ofother aspects of your system as highlighted in this report create a customer message on component SV-BO For details of how to set the appropriate priority level see SAP Note 67739
Performance Indicators for PRD
The following table shows the relevant performance indicators in various system areas
Area Indicators Value Trend
System Performance Active Users (gt400 steps) 30
Avg Availability per Week 100
Avg Response Time in Dialog Task 735 ms
Max Dialog Steps per Hour 1554
Avg Response Time at Peak Dialog Hour 676 ms
Avg Response Time in RFC Task 1383 ms
Max Number of RFCs per Hour 388
Avg RFC Response Time at Peak Hour 1370 ms
Hardware Capacity Max CPU Utilization on DB Server 37
Database Performance Avg DB Request Time in Dialog Task 268 ms
Confidential Service Summary 539
SAPreg GoingLivetrade Check - Verification Session 06082015
Area Indicators Value Trend
Avg DB Request Time for RFC 158 ms
Avg DB Request Time in Update Task 239 ms
Database Space Management DB Size 137091 GB
DB Growth Last Month 0 GB
Confidential Service Summary 639
SAPreg GoingLivetrade Check - Verification Session 06082015
3 Landscape
31 Products and Components in current Landscape
PRODUCT
SID SAP Product Product Version
PRD SAP ERP 60
MAIN INSTANCES (ABAP OR JAVA BASED)
SID Main Instance
PRD SAP ECC Server
DATABASES
SID Database System Database Version
PRD DB2 UDB for iSeries V5R4M0
32 Servers in current Landscape
SAP APPLICATION SERVERS
SID Host Instance Name Logical Host ABAP JAVA
PRD sap1r3p sap1r3p_PRD_00 SAP1R3P
DB SERVERS
SID Host Logical Host (SAPDBHOST)
PRD sap1r3p SAP1R3P
33 Hardware Configuration
HOST OVERVIEW
Host Operating System CPUs Memory in MB
sap1r3p OS400 54 0 0
Confidential Landscape 739
SAPreg GoingLivetrade Check - Verification Session 06082015
4 Software Configuration For PRD
We have listed important recommendations concerning the current software configuration on your system These recommendations should be implemented at the earliest opportunity
Your systems software versions are checked If known issues with the software versions installed are identified they are highlighted
41 SAP Application Release - Maintenance Phases
SAP Product Version End of Mainstream Maintenance Status
SAP ERP 60 31122025
In October 2014 SAP announced a maintenance extension for SAP Business Suite 7 core application releases to 2025 If you are running a relevant release see SAP Note httpsservicesapcomsapsupportnotes1648480[1648480] for more details and applicable restrictions
42 Support Package Maintenance - ABAP
The following table shows an overview of currently installed software components
SUPPORT PACKAGES
Software Component
Version Patch Level
Latest Avail Patch Level
Support Package Component Description
EA-APPL 600 8 27 SAPKGPAD08 SAP R3 Enterprise PLM SCM Finance
EA-DFPS 600 8 27 SAPKGPDD08 SAP R3 Enterprise Defense Forces amp Public Security
EA-FINSERV 600 8 28 SAPKGPFD08 SAP R3 Enterprise Financial Services
EA-GLTRADE 600 8 27 SAPKGPGD08 SAP R3 Enterprise Global Trade
EA-HR 600 15 123 SAPKGPHD15 SAP R3 Enterprise Human Resources
EA-IPPE 400 8 27 SAPKGPID08 SAP R3 Enterprise Integrated Product and Process Engineering
EA-PS 600 8 27 SAPKGPPD08 SAP R3 Enterprise Public Services
EA-RETAIL 600 8 27 SAPKGPRD08 SAP R3 Enterprise Retail
ECC-DIMP 600 8 27 SAPK-60008INECCDIMP ECC Discrete Industries Mill Products
ERECRUIT 600 8 27 SAPK-60008INERECRUIT SAP E-Recruiting
FI-CA 600 8 8 SAPK-60008INFICA FI-CA Contract Accounts Receivable and Payable (virtuell)
FI-CAX 600 8 27 SAPK-60008INFICAX FI-CAX Extended FI-CA
FINBASIS 600 8 27 SAPK-60008INFINBASIS SAP R3 Enterprise FINBASIS
INSURANCE 600 8 27 SAPK-60008ININSURANC INSURANCE SAP Insurance
IS-CWM 600 8 27 SAPK-60008INISCWM IS-CWM Catch Weight Management
IS-H 600 8 40 SAPK-60008INISH IS-Hospital
IS-M 600 8 27 SAPK-60008INISM IS Media
IS-OIL 600 8 27 SAPK-60008INISOIL IS-OIL SAP OIL amp GAS Upstream Downstream
IS-PS-CA 600 8 27 SAPK-60008INISPSCA IS-PS-CA TaxampRevenue Campus Management
Confidential Software Configuration For PRD 839
SAPreg GoingLivetrade Check - Verification Session 06082015
Software Component
Version Patch Level
Latest Avail Patch Level
Support Package Component Description
IS-UT 600 8 27 SAPK-60008INISUT IS-UT
LSOFE 600 8 27 SAPK-60008INLSOFE Learning Solution - Front End
PI_BASIS 2005_1_700 11 26 SAPKIPYJ7B SAP R3 Basis Plug-In
SAP_ABA 700 11 32 SAPKA70011 SAP Application Basis
SAP_AP 700 8 33 SAPKNA7008 SAP Application Platform
SAP_APPL 600 8 27 SAPKH60008 SAP R3 Standard
SAP_BASIS 700 11 32 SAPKB70011 SAP Basis Component
SAP_BW 700 12 34 SAPKW70012 SAP Business Information Warehouse
SAP_HR 600 15 123 SAPKE60015 SAP R3 Standard HR
SEM-BW 600 8 27 SAPKGS6008 SAP SEM Server
ST-API 01L_ECC600 0 SAP Service Tools for Applications Plug-In
ST-PI 2008_1_700 0 12 SAP Solution Tools Plug-In
43 SAP Kernel Release
Instance SAP Kernel Release Patch Level
sap1r3p 00 700 135
Instance(s) SAP Kernel Release Patch Level Age in Months OS Family
sap1r3p_PRD_00 700 135 94
431 Downward Compatible Kernel
You are running an SAP kernel version that has been outdated since Q32012 This kernel version was replaced by the downward-compatible kernel You can continue to use your current kernel version but if an issue occurs with your current kernel a fix will be provided for SAP kernel 721 only Recommendation To avoid the potential risks associated with running an outdated SAP kernel version you should replace this version with downward-compatible SAP kernel 721 The downward-compatible kernel is a special validated SAP kernel that improves the stability of your system Requirements and prerequisites to install the downward-compatible kernel are summarized below
SAP Note Number
What to Do Description
1222907 Implement SAP note or SP Runtime object with incorrect alignment
1610716 Implement SAP note or SP and execute report Correcting runtime objects with incorrect alignment
1716826 Information Usage of the downward compatible Kernel 721 (EXT)
1713986 Installation instructions Installation of Kernel 721 (EXT)
1744209 Information SAP Kernel 720 and 721 Versions and Kernel Patch Levels
For security reasons the programs rfcexec and startrfc are no longer shipped together with the 720 kernel If you run scenarios that require these programs we recommend that you download and install the corresponding files from the NW RFC SDK 720 For details refer to SAP Note 1581595
4311 Required Implementation in SAP_BASIS
You must implement the SAP Notes mentioned in this section before installing the downward-compatible kernel
Confidential Software Configuration For PRD 939
SAPreg GoingLivetrade Check - Verification Session 06082015
4312 Required Parameter Settings
As a prerequisite for running the downward-compatible kernel the following parameters need to be set
Parameter Description Current Value Recommendation
rslgnew_layout System Log Format 9
432 Issues with current SAP Kernel
Your SAP kernel release may encounter serious problems
SAP tests all SAP kernels that are released However your patch level has been found to be unstable in certain cases and is therefore not recommended For more information see the release information for each SAP kernel patch on SAP Service Marketplace
For more information about issues concerning your current SAP kernel see the SAP Notes in the table below
Recommendation If the SAP kernel shipped with the latest Support Package stack of your product has the same issue as listed below install a more recent SAP kernel available in the Patches section of SAP Service Marketplace
SAP Note Short Text Risk
1132350 Incomplete update records
1150058 Incomplete update records
1223994 Composite SAP note Incomplete update records
433 Additional Remarks
SAP releases Support Package stacks (including SAP kernel patches) on a regular basis for most products (generally 2ndash4 times a year) We recommend that you base your software maintenance strategy on these stacks
You should only consider using a more recent SAP kernel patch than that shipped with the latest Support Package Stack for your product if specific errors occur
For more information see SAP Service Marketplace at httpssupportsapcomsoftwarepatchesstackshtml (SAP SupportPackage Stack information) and httpssupportsapcompatches (patchinformation)
Confidential Software Configuration For PRD 1039
SAPreg GoingLivetrade Check - Verification Session 06082015
5 Service Preparation and Data Quality of PRD
SAP ERP system PRD is not fully prepared for delivery of future remote services
Rating Check Performed
Service Data Quality
ST-PI and ST-API Plug-Ins
Service Preparation Check (RTCCTOOL)
Service Data Control Center
Hardware Utilization Data
In preparation for SAP services ensure that connections collectors and service tools are up to date These functionalities are explained in SAP Notes httpsservicesapcomsapsupportnotes91488[91488] and 1172939
51 Service Data Quality
For this service data of high importance is missing The service data is collected by the Service Data Control Center (SDCCN) or read from the Solution Managers BW or Configuration and Change Database (CCDB) This section comprehensively shows issues with the data quality and provides hints on how to resolve them
LEGEND FOR PRIORITY IN SERVICE DATA QUALITY
Prio Explanation Impact of Missing or Erroneous Data
Overall important data are missing Detecting a critical situation may fail Report cannot be rated green or yellow
Data for an important chapter are missing Some issues may not be detected Report cannot be rated green
Some important check could not be processed The report can be rated green nevertheless
Only checks of minor importance are affected
An optional check was skipped
511 Quality of Data in Service Data Control Center (SDCC)
QUALITY OF SERVICE DATA IN ST-PI
Prio Report Area affected Details and Related ST-PI Logical Function SAP Note
System Monitoring of Server (host) sap1r3p
During hardware data collection no SAPOSCOL was found It is either not running or not accessible ST-PI function EWA_GET_HARDWARE_INFO used in section Hardware Capacity
1309499
512 Quality of Service Data in Solution Manager Diagnostics - BW
Prio Report Area affected
Details and Related Infocube SAP Note
Workload of ABAP System PRD
Reading performance data from BW returned neither data nor an error code A timeout may have occurred Infocube 0CCMSMTPH used in section Workload Overview PRD
1332428
Confidential Service Preparation and Data Quality of PRD 1139
SAPreg GoingLivetrade Check - Verification Session 06082015
52 ST-PI and ST-API Plug-Ins
The table below shows the service plug-ins implemented and their releases and patch levels These recommendations are derived from report RTCCTOOL For more information about RTCCTOOL see SAP Note 309711
Rating Plug-In Release Patch Level Release Rec Patch Level Rec
ST-API 01L_ECC600 0 01R_700 1
ST-PI 2008_1_700 0 2008_1_700 11
Recommendation The Service Tools for Applications Plug-In (ST-API) is not up-to-date For more information see SAP Note 69455 The Solution Tools Plug-In (ST-PI) is not up-to-date For more information see SAP Note 539977
53 Service Preparation Check (RTCCTOOL)
Before we can ship any services the latest version of the SAP Service tools must be implemented in your system Report RTCCTOOL was last run on 06082015 During the check the tool detected issues for which a RED rating was set
Overall Status SAP Note Title Tool Status Manual Status
69455 [Note 69455] Addon ST-API 01R_700
69455 [Note 69455] ST-API 01R_700 Support Package 1
539977 [Note 539977] ST-PI 2008_1_700 Support Package 11
69455 [Note 69455] Proc after addon impl
539977 [Note 539977] Addon ST-PI 2008_1_700
539977 Note 1300023 for ST-PI
539977 Note 1312413 for ST-PI
539977 Note 1293657 for ST-PI
12103 [Note 12103] Collectors and TCOLL
207223 [Note 207223] EWAlert setup
Recommendation [Note 69455] Addon ST-API 01R_700 Servicetools for Applications Plug-In for NetWeaver 04s Basis 70x From httpsupportsapcomsupporttools- gtST-API-gtInstallationsampUpgrades download the installation ST-API 01R_700 Upload to tx SAINT and install as per note 69455 Then restart report RTCCTOOL and choose List-gtRefresh from SAPNet
[Note 69455] ST-API 01R_700 Support Package 1 Addon supportpackage level 1 for ST-API 01R_700 for NetWeaver 04s Basis 70x From httpsupportsapcomsupporttools- gtST-API-gtSupport packages-gtST-API 01R_700 download patches up to SAPKITAB7N For basis gt=700 use the Maintenance optimizer to release the download Upload from frontend to transaction SPAM define a queue and import
[Note 539977] ST-PI 2008_1_700 Support Package 11 Addon supportpackage level 11 for ST-PI 2008_1_700 for 700 [patches up to level 11 for Basis tools for services] Open httpsupportsapcomsupporttools- gtST-PI supportpk-gt ST-PI2008_1_700 Add patch SAPKITLRDL (and predecessors if not yet implemented) download basket Release basket via Maintenance optimizer Upload from frontend into transaction SPAM define a queue and import the queue
54 Performance DB (ST03 ST06)
Analysis of ST06 and history data indicate some problems with SAPOSCOL Check SAPOSCOL and see SAP Note 1309499
Confidential Service Preparation and Data Quality of PRD 1239
SAPreg GoingLivetrade Check - Verification Session 06082015
55 Hardware Utilization Data
Host Operating System Performance Data
sap1r3p OS not detected OK
Hardware capacity checks could not be run successfully due to missing data See SAP Note 1309499
Confidential Service Preparation and Data Quality of PRD 1339
SAPreg GoingLivetrade Check - Verification Session 06082015
6 Hardware Capacity
We have checked your system for potential CPU bottlenecks and found that the hardware is sufficient for the current workload
Note Hardware Capacity evaluation is based on hosts for which data is least partially available
61 Overview System PRD
General This analysis focuses on the workload during the peak working hours (9-11 13) and is based on the hourly averages collected by SAPOSCOL For information about the definition of peak working hours see SAP Note 1251291
CPU If the average CPU load exceeds 75 temporary CPU bottlenecks are likely to occur An average CPU load of more than 90 is a strong indicator of a CPU bottleneck
Memory If your hardware cannot handle the maximum memory consumption this causes a memory bottleneck in your SAP system that can impair performance The paging rating depends on the ratio of paging activity to physical memory A ratio exceeding 25 indicates high memory usage (if Java has been detected 0 ) and values above 50 (Java 10 ) demonstrate a main memory bottleneck
Server Max CPU load [] Date Rating RAM [MB]
sap1r3p 37 21072015 0
Note In case of virtualization or IaaS scenarios (eg IBM PowerVM VMware Amazon AWS ) it might be that for some hosts the CPU rating is yellow or red although the utilization value is quite low In this case the relevant host could not use maximum usable capacity due to a resource shortage within the virtualized infrastructure (eg IBM PowerVM Shared Pool CPU utilization)
Confidential Hardware Capacity 1439
SAPreg GoingLivetrade Check - Verification Session 06082015
7 Workload of System PRD
This chart displays the main task types and indicates how their workload is distributed in the system The table below lists the detailed KPIs
RESPONSE TIME COMPONENTS IN HOURS
Task Type Response Time Wait Time CPU Time DB Time GUI Time
DIALOG 55 00 20 20 07
BATCH 51 00 24 26 00
RFC 29 00 04 03 00
UPDATE 04 00 01 02 00
Others 02 00 00 00 00
71 Workload By Users
User activity is measured in the workload monitor Only users of at least medium activity are counted as active users
Users Low Activity Medium Activity High Activity Total Users
dialog steps per week 1 to 399 400 to 4799 4800 or more
measured in system 82 29 1 112
72 Workload Distribution PRD
The performance of your system was analyzed with respect to the workload distribution We did not detect any major problems that could affect the performance of your SAP system
721 Workload by Application Module
Confidential Workload of System PRD 1539
SAPreg GoingLivetrade Check - Verification Session 06082015
The following diagrams show how each application module contributes to the total system workload Two workload aspects are shown
- CPU time total CPU load on all servers in the system landscape
- Database time total database load generated by the application
All programs that are not classified in the SAP Application Hierarchy (transaction SE81) are summarized in the Un-Assigned category Customer programs industry solutions and third-party add-on developments fall into this category
722 DB Load Profile
Confidential Workload of System PRD 1639
SAPreg GoingLivetrade Check - Verification Session 06082015
The number of work processes creating database load in parallel is not significantly high
The following diagram shows the DB load caused by dialog RFC HTTP(S) and background tasks over different time frames The data provided in the diagram represents the average number of database processes occupied by each task type in the database during the specified time frames These statistics are calculated as a weekly average the average values over six working days with a unit of one hour Periods between 0000-0600 and 2100-2400 contain an average value per hour as these are not core business hours You can enable 24-hour monitoring by implementing SAP Note 17750 With 24-hour monitoring the time profile returns the workload of the system or application server on an hourly basis rather than returning an average value per hour for the periods 0000ndash0600 and 2100ndash2400 By comparing the load profiles for dialog and background activity you can get an overview of the volume of background activity during online working hours
Confidential Workload of System PRD 1739
SAPreg GoingLivetrade Check - Verification Session 06082015
8 Performance Overview PRD
The performance of your system was analyzed with respect to the average response times and total workload We did not detect any major problems that could affect the performance of your system
Rating Check
Performance Evaluation
The following table shows the average response times for various task types
AVERAGES OF RESPONSE TIME COMPONENTS IN MS
Task type Dialog Steps Response Time CPU Time Wait Time Load Time DB Time GUI Time
DIALOG 27390 7350 2584 56 60 2679 936
RFC 7535 13832 1702 33 53 1582 00
UPDATE 3114 4477 1392 12 97 2394 00
UPDATE2 2004 2029 665 12 41 878 00
BATCH 8357 21896 10330 07 105 11007 00
SPOOL 1221 5755 262 58 08 188 00
81 Performance Evaluation
The measured times are compared against reference times to provide a rating - If the number of dialog steps in an hour is less than 1000 this hour is not considered - If the total number of transaction steps is less than 20000 the rating for the task is not performed (indicated by a gray icon in the table) - RED if at least three time ranges are rated RED - YELLOW if two time ranges are rated RED or at least three time ranges are rated YELLOW
The table below shows that no problem is expected on the application or database servers
Task Steps Application Server Performance Database Server Performance
Dia 27389
Upd 3114
HTTP 0
HTTPS 0
The ratings in the table above are determined by comparisons against the reference table below If the dialog response times are very poor it will cause a RED rating for the entire check
Task Reference for Avg Response Time (ms) Yellow Rating
Reference for Avg Response Time (ms) Red Rating
Reference for Avg DB time (ms) Yellow Rating
Reference for Avg DB time (ms) Red Rating
Dia 1200 3600 600 1800
Upd 2400 3600 1200 1800
HTTP 1200 3600 600 1800
HTTPS 1200 3600 600 1800
Confidential Performance Overview PRD 1839
SAPreg GoingLivetrade Check - Verification Session 06082015
82 Transaction Profile Check
The following tables show the response times and the number of dialog steps for the transactions that cause the heaviest workload in your system
821 Transactions by Total Workload
The following tables list the activities with the highest contribution to the total workload
WORKLOAD BY TRANSACTION (DIALOG HTTP(S)WS-HTTP )
Transaction Type Dialog Steps Total Resp Time in
Avg Resp Time in ms
Avg CPU Time in ms
Avg DB Time in ms
Avg GUI Time in ms
VL71 DIA 83 61 297185 178782 263658 71
FBL5N DIA 2919 33 4626 1991 1330 242
VA01 DIA 2034 32 6258 2092 1164 1764
VA02 DIA 2183 29 5306 2194 1287 639
ZSDP0023 DIA 365 22 24427 2144 19871 2116
ZWMSCP01 DIA 130 21 65254 13125 10103 649
ME22 DIA 167 17 41818 22914 3250 07
VT01N DIA 235 15 25864 13412 1976 2443
SESSION_MANAGER DIA 1078 14 5202 663 844 2716
VKM1 DIA 478 12 9796 3358 3746 86
43 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
WORKLOAD BY TRANSACTION (BATCH)
Transaction Dialog Steps Total Resp Time in
Total Resp Time in s
Total CPU Time in s
Total DB Time in s
ZFIP0102 156 109 44040 25240 42295
ZFIP0115 260 97 39320 21180 23386
ZSD_CREATE_ORDER_BY_REF 125 75 30160 13100 7000
ZWMS_FILE_MANAGER2 784 37 14820 930 612
ZSDP0031 8 33 13260 6780 2783
ZFIP0105 390 16 6560 4350 383
ZFIP0106 78 15 6010 4140 5722
RSBTCRTE 2412 12 4820 1240 336
ZSDP0063 2 10 4050 2130 1318
(BATCH) 3197 09 3750 810 506
392 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
822 Transactions by DB Load
The following transaction profiles list the transactions that have the greatest share in the database load sorted by percentage of total database access times
DATABASE LOAD BY TRANSACTIONS (DIALOG HTTP(S) )
Confidential Performance Overview PRD 1939
SAPreg GoingLivetrade Check - Verification Session 06082015
Transaction Type Dialog Steps Total DB Time in Avg DB Time in ms
VL71 DIA 83 127 263658
ZSDP0023 DIA 365 42 19871
FBL5N DIA 2919 22 1330
VA02 DIA 2183 16 1287
ZVC2 DIA 1360 15 1953
ZMMP0008 DIA 64 14 37798
VA01 DIA 2034 14 1164
ZSDP0013 DIA 47 12 43947
VKM1 DIA 478 10 3746
ZWMSCP01 DIA 130 08 10103
91 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
DATABASE LOAD BY TRANSACTIONS (BATCH)
Transaction Dialog Steps Total DB Time in Total DB Time in s
ZFIP0102 156 245 42300
ZFIP0115 260 135 23390
ZSD_CREATE_ORDER_BY_REF 125 41 7000
ZFIP0106 78 33 5720
ZSDP0031 8 16 2780
RSDB4UPD 2 12 2070
ZFII0002 1 09 1580
ZSDP0063 2 08 1320
ZSD_GENERATE_INFO_CONDITIONS 7 08 1320
ZFIP0101 263 07 1290
502 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
83 RFC Load by Initiating Action
The load in task type RFC is shown In the workload monitor this information is shown as Load from External Systems The calling system can be an application server of the system itself or any external system using the RFC interface The Initial Action is the calling program initiating the RFC The total response time for each initial action is shown as an absolute value and as a percentage compared to the total RFC load considered in this table The average times (per dialog step) are shown in milliseconds [ms] Calls from external systems are shown if they account for at least 8h or 5 of the total RFC load Local calls are shown if they account for at least 24h or 20 of the total RFC load
LOAD OVERVIEW
Initial System Load [s] Load
Local system PRD 4450 9957
Sum of external systems 19 043
RFC load (sum of above) 4469 10000
Confidential Performance Overview PRD 2039
SAPreg GoingLivetrade Check - Verification Session 06082015
Initial System Load [s] Load
RFC load in Performance Overview 10422 23321
Load of all task types in Performance Overview 51694 115668
TOP 20 RFC CALLS FROM LOCAL SYSTEM - AVERAGE TIMES [MS]
Initial System
Initial Action Total Resp
Time in s
of RFC Load
Avg Response
Time
Avg CPU Time
Avg DB Time
Avg Roll Wait Time
PRD RK2A1000_POST 892 1996 13097 147 87 20
PRD VF01 491 1099 25854 8767 14305 23
PRD VA01 468 1047 8402 170 543 14
PRD SAPLARFC 256 574 10505 208 305 17
PRD CA_QUEUE_ENTRY_BCS============CP 226 505 4628 1068 1398 251
PRD VA02 178 399 6343 1215 1490 14
PRD VL71 136 304 8330 698 330 118
PRD SAP_COLLECTOR_FOR_PERFMONITOR 132 295 33749 13108 7127 188
PRD VL02N 127 284 11757 2595 7164 18
PRD VL10X 96 215 4341 553 433 10
PRD VKM1 70 157 3532 813 930 35
PRD ZSDP0049 55 124 61422 1167 1553 64
PRD STMS 52 116 18555 1911 2091 77
PRD ZP01_FROM_ZP05_944988 52 115 171827 3233 1053 03
PRD ZSDP0010 45 100 74582 31983 32785 10
PRD XD02 43 097 403 116 126 05
PRD FB1D 42 093 1999 406 1263 06
PRD FBL5N 41 091 8700 630 866 14
PRD ZP01_FROM_ZP05_942398 38 086 63795 1867 2482 65
PRD FBZ5 32 071 319430 400 510 00
Confidential Performance Overview PRD 2139
SAPreg GoingLivetrade Check - Verification Session 06082015
9 SAP System Operating PRD
The daily operation of your system was analyzed We detected some problems that may impair system operation and stability
91 Availability based on Collector Protocols
A value of 100 means that the collector was available all day Available in the context of this report means that at least one SAP instance was running If the SAP collector was not running correctly the values in the table and graphics may be incorrect To check these logs call transaction ST03N (expert mode) and choose Collector and Performance DB -gt Performance Monitor Collector -gt Log
This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR that runs every hour The job does NOT check availability it carries out only general system tasks such as collecting and aggregating SAP performance data for all serversinstances The log does not contain any direct information about availability it contains only information about the status of the hourly statistical data collection
As of SAP Basis 640 system availability information is available in the CCMS (Computing Center Management System) of an SAP System in Service Level Reporting of SAP Solution Manager
This function is provided by the relevant Solution Manager Support Packages as an advanced development For more information refer to SAP Note 944496 which also lists the prerequisites that must be fulfilled before implementation can take place
92 Update Errors
In a system running under normal conditions only a small number of update errors should occur To set the rating for this check the number of active users is also taken into consideration
We did not detect any problems
Confidential SAP System Operating PRD 2239
SAPreg GoingLivetrade Check - Verification Session 06082015
93 Table Reorganization
The largest tables andor rapidly growing tables of system PRDwere checked No standard SAP recommendations for the applicable data volume management were found
94 Program Errors (ABAP Dumps)
50 ABAP dumps have been recorded in your system in the period 30072015 to 05082015 ABAP dumps are generally deleted after 7 days by default To view the ABAP dumps in your system call transaction ST22 and choose Selection Then select a timeframe
Date Number of Dumps
30072015 19
31072015 15
01082015 0
02082015 1
03082015 4
04082015 5
05082015 6
Name of Runtime Error Dumps Server (eg) User (eg) Date (eg) Time (eg)
TIME_OUT 1 SAP1R3P_PRD_00 EMOROCHO 30072015 104804
CALL_FUNCTION_SINGLE_LOGIN_REJ 2 SAP1R3P_PRD_00 SAPSYS 30072015 170339
DYNPRO_FIELD_CONVERSION 6 SAP1R3P_PRD_00 LORTEGA 31072015 172039
DBIF_RSQL_INVALID_RSQL 5 SAP1R3P_PRD_00 PREDROBAN 02082015 060047
CALL_FUNCTION_SEND_ERROR 2 SAP1R3P_PRD_00 JPVEND 03082015 073533
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY 3 SAP1R3P_PRD_00 LORTEGA 04082015 123208
RAISE_EXCEPTION 14 SAP1R3P_PRD_00 KCASTRO 05082015 094209
CONVT_NO_NUMBER 1 SAP1R3P_PRD_00 KABARCA 05082015 143511
UNCAUGHT_EXCEPTION 1 SAP1R3P_PRD_00 CBANCHON 05082015 150325
TSV_TNEW_PAGE_ALLOC_FAILED 5 SAP1R3P_PRD_00 FLUCAS 05082015 190338
MESSAGE_TYPE_X 10 SAP1R3P_PRD_00 INTERFASES 05082015 210129
It is important that you monitor ABAP dumps using transaction ST22 on a regular basis If ABAP dumps occur you should determine the cause as soon as possible Based on our analysis we found several ABAP dumps that need your attention Evaluate and resolve the above dumps If you cannot find a solution send a customer message to SAP to request support
Confidential SAP System Operating PRD 2339
SAPreg GoingLivetrade Check - Verification Session 06082015
10 Security
Critical security issues were found in your system
See the information in the following sections
Rating Check
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
101 ABAP Stack of PRD
1011 System Recommendations (ABAP)
System Recommendations is not used at all
Recommendation SAP strongly recommends applying important security fixes as soon as possible The System Recommendations application provides a detailed recommendation regarding which SAP security notes (ABAP and non-ABAP) should be implemented based on the actual status of the system and the notes already implemented This is a mandatory prerequisite for setting up a strong security patch process For more information go to httpservicesapcomsysrec
1012 Default Passwords of Standard Users
Standard users have default passwords
Recommendation Run report RSUSR003 to check the usage of default passwords by standard users
Ensure that users SAP (must exist in all clients) SAPCPIC and EARLYWATCH have non-default passwords in all clients For more information see Protecting Standard Users either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
Make sure that the standard password for user TMSADM has been changed in client 000 and delete this user in any other client SAP Note httpsservicesapcomsapsupportnotes1414256[1414256] describes a support tool to change the password of user TMSADM in all systems of the transport domain SAP Note httpsservicesapcomsapsupportnotes1552894[1552894] shows how to update the report RSUSR003 to show the status of user TMSADM
1013 ABAP Password Policy
If password login is allowed for specific instances only the password policy is checked only for these instances
10131 Password Complexity
PARAMETER LOGINMIN_PASSWORD_LNG
Confidential Security 2439
SAPreg GoingLivetrade Check - Verification Session 06082015
Rating Instance Current Value(s) Recommended Value
sap1r3p_PRD_00 6 8
The current system settings allow a password length of fewer than 8 characters This allows weak passwords Attackers may successfully recover these passwords and gain unauthorized access to the system
Recommendation Assign a minimum value of 8 to the profile parameter loginmin_password_lng
In addition SAP provides options to enforce complex passwords Find the current settings of the corresponding profile parameters in the following table
Parameter Instance Current Value(s)
loginmin_password_digits sap1r3p_PRD_00 0
loginmin_password_letters sap1r3p_PRD_00 0
loginmin_password_lowercase sap1r3p_PRD_00 0
loginmin_password_uppercase sap1r3p_PRD_00 0
loginmin_password_specials sap1r3p_PRD_00 0
Recommendation Enforce a minimum of 3 independent character categories using the corresponding profile parameters For more information see SAP Note httpsservicesapcomsapsupportnotes862989[862989] and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
1014 Gateway and Message Server Security
10141 Kernel Patch Level
Rating Kernel Release Current Kernel Patch Level Minimal Required Kernel Patch Level
700 135 260
To enable certain gateway security functionality a minimum kernel patch level is required Your system does not currently meet this requirement
Recommendation Update the kernel of your system to the newest kernel patch level available Update to a kernel patch level equal to or higher than the minimum required kernel patch level specified above For more information see SAP Note 1298433
10142 Gateway Security
Gateway Security Properties
The parameter GWREG_NO_CONN_INFO controls the activation of certain security properties of the SAP gateway It is defined as a bit mask with one bit per property
SAP Note httpsservicesapcomsapsupportnotes1298433[1298433] ldquoBypassing security in reginfo amp secinfordquo is not activated in your system The bit mask value for bit 1 is not set
Recommendation Enable the missing property by adding the bitmask value to the current value of GWREG_NO_CONN_INFO For more information about GWREG_NO_CONN_INFO see SAP Note 1444282
Confidential Security 2539
SAPreg GoingLivetrade Check - Verification Session 06082015
1015 Users with Critical Authorizations
For more information about the following check results see SAP Note 863362
Recommendation Depending on your environment review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations You can use the User Information System (transaction SUIM) to check the results For each check you can review the roles or profiles that include the authorization objects listed in the corresponding section
10151 Users Authorized to Start all Reports
This authorization allows critical functions and reports that do not contain their own authorization checks to be executed The specified number of users for each client have the checked authorization
Client No of Users Having This Authorization No of Valid Users Rating
001 2 3
400 147 160
Authorization objects
Object 1 S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2 S_PROGRAM with P_ACTION=SUBMIT P_GROUP=
Confidential Security 2639
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
1 Contents
1 Contents 1
2 Service Summary 4
Performance Indicators for PRD 5
3 Landscape 7
31 Products and Components in current Landscape 7
32 Servers in current Landscape 7
33 Hardware Configuration 7
4 Software Configuration For PRD 8
41 SAP Application Release - Maintenance Phases 8
42 Support Package Maintenance - ABAP 8
43 SAP Kernel Release 9
431 Downward Compatible Kernel 9
432 Issues with current SAP Kernel 10
433 Additional Remarks 10
5 Service Preparation and Data Quality of PRD 11
51 Service Data Quality 11
511 Quality of Data in Service Data Control Center (SDCC) 11
512 Quality of Service Data in Solution Manager Diagnostics - BW 11
52 ST-PI and ST-API Plug-Ins 11
53 Service Preparation Check (RTCCTOOL) 12
54 Performance DB (ST03 ST06) 12
55 Hardware Utilization Data 12
6 Hardware Capacity 14
61 Overview System PRD 14
7 Workload of System PRD 15
71 Workload By Users 15
72 Workload Distribution PRD 15
721 Workload by Application Module 15
722 DB Load Profile 16
8 Performance Overview PRD 18
Confidential Contents 139
SAPreg GoingLivetrade Check - Verification Session 06082015
81 Performance Evaluation 18
82 Transaction Profile Check 18
821 Transactions by Total Workload 19
822 Transactions by DB Load 19
83 RFC Load by Initiating Action 20
9 SAP System Operating PRD 22
91 Availability based on Collector Protocols 22
92 Update Errors 22
93 Table Reorganization 22
94 Program Errors (ABAP Dumps) 23
10 Security 24
101 ABAP Stack of PRD 24
1011 System Recommendations (ABAP) 24
1012 Default Passwords of Standard Users 24
1013 ABAP Password Policy 24
1014 Gateway and Message Server Security 25
1015 Users with Critical Authorizations 25
11 Software Change and Transport Management of PRD 27
111 SAP Netweaver Application Server ABAP of PRD 27
1111 Number of Changes 27
12 Data Volume Management (DVM) 28
13 ABAP Stack Configuration for PRD 29
131 Configuration for Central ABAP Instance sap1r3p_PRD_00 29
1311 Buffer Configuration 29
1312 Client Server Communication 29
1313 Enqueue Handling 29
1314 Obsolete Codepage Parameters 30
14 IBM i Database Checks 31
141 Important SAP Notes for IBM i 31
142 Reorganize Physical File Member 31
143 Missing Indexes 31
Confidential Contents 239
SAPreg GoingLivetrade Check - Verification Session 06082015
144 Disk arm utilization 31
145 Database Size 31
146 Backup Strategy 32
15 IBM i Specific Server Checks 33
151 iASP Configuration Check 33
152 Disk status 33
153 Data Protection in System ASP (ASP1) 33
154 Free space in System ASP (ASP1) 33
155 PTF Check 34
156 Disk Service Time 34
157 IBM i System parameters 34
158 SHRPOOL Pool 34
159 Paging Option 35
16 Trend Analysis 36
161 System Activity 36
162 Response Times 37
163 Application profile 37
164 System Operation 38
165 Hardware Capacity 38
Confidential Contents 339
SAPreg GoingLivetrade Check - Verification Session 06082015
2 Service Summary
The SAP reg GoingLivetrade Check (Verification Session) has detected severe problems that may cause you to lose business
We recommend that you take corrective action immediately
This report provides the results of the SAP reg GoingLivetrade Check (Verification Session) that was conducted on your SAP ERPsystem PRD Note The numbers in the Performance Overview PRD and Workload of System PRD sections refer to the time interval between 27072015 and 02082015 There is at least one area with critical performance system stability or security issues
The alert overview below summarizes the most important issues to be addressed Take corrective actions in these areas as soon as possible
ALERTS DECISIVE FOR RED REPORT
With the SAP kernel of your ABAP system the stability or consistency is at risk
ALERT OVERVIEW
A large number of deleted records have been found on the system
We found more than 30 ABAP dumps in your system
Standard users have default password
Secure password policy is not sufficiently enforced
A high number of users has critical authorizations
Perform the following Guided Self Services
Guided Self Service FAQ SAP Note
Security Optimization Service 696478
For more information about Guided Self-Services see SAP Enterprise Support Academy Register for an Expert-Guided Implementation Session for the Guided Self-Service at SAP Enterprise Support Academy - Learning Studio - Calendar
CHECK OVERVIEW
Topic Rating Topic Subtopic Rating Subtopic
SAP System Configuration
Performance Overview
Performance Evaluation
Workload Distribution
Workload by Application Module
DB Load Profile
SAP System Operating
Availability based on Collector Protocols
Confidential Service Summary 439
SAPreg GoingLivetrade Check - Verification Session 06082015
Topic Rating Topic Subtopic Rating Subtopic
Program Errors (ABAP Dumps)
Update Errors
Table Reorganization
Hardware Capacity
IBM i Database Checks
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
Security
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
Software Change Management
Number of Changes
Note All recommendations provided in this report are based on our general experience We advise that you test our recommendations before using them in your production system
Note If you have any questions about the accuracy of the checks in this report or the correct configuration of the SAP Solution Manager SAP reg GoingLivetrade Check (Verification Session) service create a customer message on component SV-SMG-SER
Note If you require assistance in resolving any concerns about the performance of the system or if you require a technical analysis ofother aspects of your system as highlighted in this report create a customer message on component SV-BO For details of how to set the appropriate priority level see SAP Note 67739
Performance Indicators for PRD
The following table shows the relevant performance indicators in various system areas
Area Indicators Value Trend
System Performance Active Users (gt400 steps) 30
Avg Availability per Week 100
Avg Response Time in Dialog Task 735 ms
Max Dialog Steps per Hour 1554
Avg Response Time at Peak Dialog Hour 676 ms
Avg Response Time in RFC Task 1383 ms
Max Number of RFCs per Hour 388
Avg RFC Response Time at Peak Hour 1370 ms
Hardware Capacity Max CPU Utilization on DB Server 37
Database Performance Avg DB Request Time in Dialog Task 268 ms
Confidential Service Summary 539
SAPreg GoingLivetrade Check - Verification Session 06082015
Area Indicators Value Trend
Avg DB Request Time for RFC 158 ms
Avg DB Request Time in Update Task 239 ms
Database Space Management DB Size 137091 GB
DB Growth Last Month 0 GB
Confidential Service Summary 639
SAPreg GoingLivetrade Check - Verification Session 06082015
3 Landscape
31 Products and Components in current Landscape
PRODUCT
SID SAP Product Product Version
PRD SAP ERP 60
MAIN INSTANCES (ABAP OR JAVA BASED)
SID Main Instance
PRD SAP ECC Server
DATABASES
SID Database System Database Version
PRD DB2 UDB for iSeries V5R4M0
32 Servers in current Landscape
SAP APPLICATION SERVERS
SID Host Instance Name Logical Host ABAP JAVA
PRD sap1r3p sap1r3p_PRD_00 SAP1R3P
DB SERVERS
SID Host Logical Host (SAPDBHOST)
PRD sap1r3p SAP1R3P
33 Hardware Configuration
HOST OVERVIEW
Host Operating System CPUs Memory in MB
sap1r3p OS400 54 0 0
Confidential Landscape 739
SAPreg GoingLivetrade Check - Verification Session 06082015
4 Software Configuration For PRD
We have listed important recommendations concerning the current software configuration on your system These recommendations should be implemented at the earliest opportunity
Your systems software versions are checked If known issues with the software versions installed are identified they are highlighted
41 SAP Application Release - Maintenance Phases
SAP Product Version End of Mainstream Maintenance Status
SAP ERP 60 31122025
In October 2014 SAP announced a maintenance extension for SAP Business Suite 7 core application releases to 2025 If you are running a relevant release see SAP Note httpsservicesapcomsapsupportnotes1648480[1648480] for more details and applicable restrictions
42 Support Package Maintenance - ABAP
The following table shows an overview of currently installed software components
SUPPORT PACKAGES
Software Component
Version Patch Level
Latest Avail Patch Level
Support Package Component Description
EA-APPL 600 8 27 SAPKGPAD08 SAP R3 Enterprise PLM SCM Finance
EA-DFPS 600 8 27 SAPKGPDD08 SAP R3 Enterprise Defense Forces amp Public Security
EA-FINSERV 600 8 28 SAPKGPFD08 SAP R3 Enterprise Financial Services
EA-GLTRADE 600 8 27 SAPKGPGD08 SAP R3 Enterprise Global Trade
EA-HR 600 15 123 SAPKGPHD15 SAP R3 Enterprise Human Resources
EA-IPPE 400 8 27 SAPKGPID08 SAP R3 Enterprise Integrated Product and Process Engineering
EA-PS 600 8 27 SAPKGPPD08 SAP R3 Enterprise Public Services
EA-RETAIL 600 8 27 SAPKGPRD08 SAP R3 Enterprise Retail
ECC-DIMP 600 8 27 SAPK-60008INECCDIMP ECC Discrete Industries Mill Products
ERECRUIT 600 8 27 SAPK-60008INERECRUIT SAP E-Recruiting
FI-CA 600 8 8 SAPK-60008INFICA FI-CA Contract Accounts Receivable and Payable (virtuell)
FI-CAX 600 8 27 SAPK-60008INFICAX FI-CAX Extended FI-CA
FINBASIS 600 8 27 SAPK-60008INFINBASIS SAP R3 Enterprise FINBASIS
INSURANCE 600 8 27 SAPK-60008ININSURANC INSURANCE SAP Insurance
IS-CWM 600 8 27 SAPK-60008INISCWM IS-CWM Catch Weight Management
IS-H 600 8 40 SAPK-60008INISH IS-Hospital
IS-M 600 8 27 SAPK-60008INISM IS Media
IS-OIL 600 8 27 SAPK-60008INISOIL IS-OIL SAP OIL amp GAS Upstream Downstream
IS-PS-CA 600 8 27 SAPK-60008INISPSCA IS-PS-CA TaxampRevenue Campus Management
Confidential Software Configuration For PRD 839
SAPreg GoingLivetrade Check - Verification Session 06082015
Software Component
Version Patch Level
Latest Avail Patch Level
Support Package Component Description
IS-UT 600 8 27 SAPK-60008INISUT IS-UT
LSOFE 600 8 27 SAPK-60008INLSOFE Learning Solution - Front End
PI_BASIS 2005_1_700 11 26 SAPKIPYJ7B SAP R3 Basis Plug-In
SAP_ABA 700 11 32 SAPKA70011 SAP Application Basis
SAP_AP 700 8 33 SAPKNA7008 SAP Application Platform
SAP_APPL 600 8 27 SAPKH60008 SAP R3 Standard
SAP_BASIS 700 11 32 SAPKB70011 SAP Basis Component
SAP_BW 700 12 34 SAPKW70012 SAP Business Information Warehouse
SAP_HR 600 15 123 SAPKE60015 SAP R3 Standard HR
SEM-BW 600 8 27 SAPKGS6008 SAP SEM Server
ST-API 01L_ECC600 0 SAP Service Tools for Applications Plug-In
ST-PI 2008_1_700 0 12 SAP Solution Tools Plug-In
43 SAP Kernel Release
Instance SAP Kernel Release Patch Level
sap1r3p 00 700 135
Instance(s) SAP Kernel Release Patch Level Age in Months OS Family
sap1r3p_PRD_00 700 135 94
431 Downward Compatible Kernel
You are running an SAP kernel version that has been outdated since Q32012 This kernel version was replaced by the downward-compatible kernel You can continue to use your current kernel version but if an issue occurs with your current kernel a fix will be provided for SAP kernel 721 only Recommendation To avoid the potential risks associated with running an outdated SAP kernel version you should replace this version with downward-compatible SAP kernel 721 The downward-compatible kernel is a special validated SAP kernel that improves the stability of your system Requirements and prerequisites to install the downward-compatible kernel are summarized below
SAP Note Number
What to Do Description
1222907 Implement SAP note or SP Runtime object with incorrect alignment
1610716 Implement SAP note or SP and execute report Correcting runtime objects with incorrect alignment
1716826 Information Usage of the downward compatible Kernel 721 (EXT)
1713986 Installation instructions Installation of Kernel 721 (EXT)
1744209 Information SAP Kernel 720 and 721 Versions and Kernel Patch Levels
For security reasons the programs rfcexec and startrfc are no longer shipped together with the 720 kernel If you run scenarios that require these programs we recommend that you download and install the corresponding files from the NW RFC SDK 720 For details refer to SAP Note 1581595
4311 Required Implementation in SAP_BASIS
You must implement the SAP Notes mentioned in this section before installing the downward-compatible kernel
Confidential Software Configuration For PRD 939
SAPreg GoingLivetrade Check - Verification Session 06082015
4312 Required Parameter Settings
As a prerequisite for running the downward-compatible kernel the following parameters need to be set
Parameter Description Current Value Recommendation
rslgnew_layout System Log Format 9
432 Issues with current SAP Kernel
Your SAP kernel release may encounter serious problems
SAP tests all SAP kernels that are released However your patch level has been found to be unstable in certain cases and is therefore not recommended For more information see the release information for each SAP kernel patch on SAP Service Marketplace
For more information about issues concerning your current SAP kernel see the SAP Notes in the table below
Recommendation If the SAP kernel shipped with the latest Support Package stack of your product has the same issue as listed below install a more recent SAP kernel available in the Patches section of SAP Service Marketplace
SAP Note Short Text Risk
1132350 Incomplete update records
1150058 Incomplete update records
1223994 Composite SAP note Incomplete update records
433 Additional Remarks
SAP releases Support Package stacks (including SAP kernel patches) on a regular basis for most products (generally 2ndash4 times a year) We recommend that you base your software maintenance strategy on these stacks
You should only consider using a more recent SAP kernel patch than that shipped with the latest Support Package Stack for your product if specific errors occur
For more information see SAP Service Marketplace at httpssupportsapcomsoftwarepatchesstackshtml (SAP SupportPackage Stack information) and httpssupportsapcompatches (patchinformation)
Confidential Software Configuration For PRD 1039
SAPreg GoingLivetrade Check - Verification Session 06082015
5 Service Preparation and Data Quality of PRD
SAP ERP system PRD is not fully prepared for delivery of future remote services
Rating Check Performed
Service Data Quality
ST-PI and ST-API Plug-Ins
Service Preparation Check (RTCCTOOL)
Service Data Control Center
Hardware Utilization Data
In preparation for SAP services ensure that connections collectors and service tools are up to date These functionalities are explained in SAP Notes httpsservicesapcomsapsupportnotes91488[91488] and 1172939
51 Service Data Quality
For this service data of high importance is missing The service data is collected by the Service Data Control Center (SDCCN) or read from the Solution Managers BW or Configuration and Change Database (CCDB) This section comprehensively shows issues with the data quality and provides hints on how to resolve them
LEGEND FOR PRIORITY IN SERVICE DATA QUALITY
Prio Explanation Impact of Missing or Erroneous Data
Overall important data are missing Detecting a critical situation may fail Report cannot be rated green or yellow
Data for an important chapter are missing Some issues may not be detected Report cannot be rated green
Some important check could not be processed The report can be rated green nevertheless
Only checks of minor importance are affected
An optional check was skipped
511 Quality of Data in Service Data Control Center (SDCC)
QUALITY OF SERVICE DATA IN ST-PI
Prio Report Area affected Details and Related ST-PI Logical Function SAP Note
System Monitoring of Server (host) sap1r3p
During hardware data collection no SAPOSCOL was found It is either not running or not accessible ST-PI function EWA_GET_HARDWARE_INFO used in section Hardware Capacity
1309499
512 Quality of Service Data in Solution Manager Diagnostics - BW
Prio Report Area affected
Details and Related Infocube SAP Note
Workload of ABAP System PRD
Reading performance data from BW returned neither data nor an error code A timeout may have occurred Infocube 0CCMSMTPH used in section Workload Overview PRD
1332428
Confidential Service Preparation and Data Quality of PRD 1139
SAPreg GoingLivetrade Check - Verification Session 06082015
52 ST-PI and ST-API Plug-Ins
The table below shows the service plug-ins implemented and their releases and patch levels These recommendations are derived from report RTCCTOOL For more information about RTCCTOOL see SAP Note 309711
Rating Plug-In Release Patch Level Release Rec Patch Level Rec
ST-API 01L_ECC600 0 01R_700 1
ST-PI 2008_1_700 0 2008_1_700 11
Recommendation The Service Tools for Applications Plug-In (ST-API) is not up-to-date For more information see SAP Note 69455 The Solution Tools Plug-In (ST-PI) is not up-to-date For more information see SAP Note 539977
53 Service Preparation Check (RTCCTOOL)
Before we can ship any services the latest version of the SAP Service tools must be implemented in your system Report RTCCTOOL was last run on 06082015 During the check the tool detected issues for which a RED rating was set
Overall Status SAP Note Title Tool Status Manual Status
69455 [Note 69455] Addon ST-API 01R_700
69455 [Note 69455] ST-API 01R_700 Support Package 1
539977 [Note 539977] ST-PI 2008_1_700 Support Package 11
69455 [Note 69455] Proc after addon impl
539977 [Note 539977] Addon ST-PI 2008_1_700
539977 Note 1300023 for ST-PI
539977 Note 1312413 for ST-PI
539977 Note 1293657 for ST-PI
12103 [Note 12103] Collectors and TCOLL
207223 [Note 207223] EWAlert setup
Recommendation [Note 69455] Addon ST-API 01R_700 Servicetools for Applications Plug-In for NetWeaver 04s Basis 70x From httpsupportsapcomsupporttools- gtST-API-gtInstallationsampUpgrades download the installation ST-API 01R_700 Upload to tx SAINT and install as per note 69455 Then restart report RTCCTOOL and choose List-gtRefresh from SAPNet
[Note 69455] ST-API 01R_700 Support Package 1 Addon supportpackage level 1 for ST-API 01R_700 for NetWeaver 04s Basis 70x From httpsupportsapcomsupporttools- gtST-API-gtSupport packages-gtST-API 01R_700 download patches up to SAPKITAB7N For basis gt=700 use the Maintenance optimizer to release the download Upload from frontend to transaction SPAM define a queue and import
[Note 539977] ST-PI 2008_1_700 Support Package 11 Addon supportpackage level 11 for ST-PI 2008_1_700 for 700 [patches up to level 11 for Basis tools for services] Open httpsupportsapcomsupporttools- gtST-PI supportpk-gt ST-PI2008_1_700 Add patch SAPKITLRDL (and predecessors if not yet implemented) download basket Release basket via Maintenance optimizer Upload from frontend into transaction SPAM define a queue and import the queue
54 Performance DB (ST03 ST06)
Analysis of ST06 and history data indicate some problems with SAPOSCOL Check SAPOSCOL and see SAP Note 1309499
Confidential Service Preparation and Data Quality of PRD 1239
SAPreg GoingLivetrade Check - Verification Session 06082015
55 Hardware Utilization Data
Host Operating System Performance Data
sap1r3p OS not detected OK
Hardware capacity checks could not be run successfully due to missing data See SAP Note 1309499
Confidential Service Preparation and Data Quality of PRD 1339
SAPreg GoingLivetrade Check - Verification Session 06082015
6 Hardware Capacity
We have checked your system for potential CPU bottlenecks and found that the hardware is sufficient for the current workload
Note Hardware Capacity evaluation is based on hosts for which data is least partially available
61 Overview System PRD
General This analysis focuses on the workload during the peak working hours (9-11 13) and is based on the hourly averages collected by SAPOSCOL For information about the definition of peak working hours see SAP Note 1251291
CPU If the average CPU load exceeds 75 temporary CPU bottlenecks are likely to occur An average CPU load of more than 90 is a strong indicator of a CPU bottleneck
Memory If your hardware cannot handle the maximum memory consumption this causes a memory bottleneck in your SAP system that can impair performance The paging rating depends on the ratio of paging activity to physical memory A ratio exceeding 25 indicates high memory usage (if Java has been detected 0 ) and values above 50 (Java 10 ) demonstrate a main memory bottleneck
Server Max CPU load [] Date Rating RAM [MB]
sap1r3p 37 21072015 0
Note In case of virtualization or IaaS scenarios (eg IBM PowerVM VMware Amazon AWS ) it might be that for some hosts the CPU rating is yellow or red although the utilization value is quite low In this case the relevant host could not use maximum usable capacity due to a resource shortage within the virtualized infrastructure (eg IBM PowerVM Shared Pool CPU utilization)
Confidential Hardware Capacity 1439
SAPreg GoingLivetrade Check - Verification Session 06082015
7 Workload of System PRD
This chart displays the main task types and indicates how their workload is distributed in the system The table below lists the detailed KPIs
RESPONSE TIME COMPONENTS IN HOURS
Task Type Response Time Wait Time CPU Time DB Time GUI Time
DIALOG 55 00 20 20 07
BATCH 51 00 24 26 00
RFC 29 00 04 03 00
UPDATE 04 00 01 02 00
Others 02 00 00 00 00
71 Workload By Users
User activity is measured in the workload monitor Only users of at least medium activity are counted as active users
Users Low Activity Medium Activity High Activity Total Users
dialog steps per week 1 to 399 400 to 4799 4800 or more
measured in system 82 29 1 112
72 Workload Distribution PRD
The performance of your system was analyzed with respect to the workload distribution We did not detect any major problems that could affect the performance of your SAP system
721 Workload by Application Module
Confidential Workload of System PRD 1539
SAPreg GoingLivetrade Check - Verification Session 06082015
The following diagrams show how each application module contributes to the total system workload Two workload aspects are shown
- CPU time total CPU load on all servers in the system landscape
- Database time total database load generated by the application
All programs that are not classified in the SAP Application Hierarchy (transaction SE81) are summarized in the Un-Assigned category Customer programs industry solutions and third-party add-on developments fall into this category
722 DB Load Profile
Confidential Workload of System PRD 1639
SAPreg GoingLivetrade Check - Verification Session 06082015
The number of work processes creating database load in parallel is not significantly high
The following diagram shows the DB load caused by dialog RFC HTTP(S) and background tasks over different time frames The data provided in the diagram represents the average number of database processes occupied by each task type in the database during the specified time frames These statistics are calculated as a weekly average the average values over six working days with a unit of one hour Periods between 0000-0600 and 2100-2400 contain an average value per hour as these are not core business hours You can enable 24-hour monitoring by implementing SAP Note 17750 With 24-hour monitoring the time profile returns the workload of the system or application server on an hourly basis rather than returning an average value per hour for the periods 0000ndash0600 and 2100ndash2400 By comparing the load profiles for dialog and background activity you can get an overview of the volume of background activity during online working hours
Confidential Workload of System PRD 1739
SAPreg GoingLivetrade Check - Verification Session 06082015
8 Performance Overview PRD
The performance of your system was analyzed with respect to the average response times and total workload We did not detect any major problems that could affect the performance of your system
Rating Check
Performance Evaluation
The following table shows the average response times for various task types
AVERAGES OF RESPONSE TIME COMPONENTS IN MS
Task type Dialog Steps Response Time CPU Time Wait Time Load Time DB Time GUI Time
DIALOG 27390 7350 2584 56 60 2679 936
RFC 7535 13832 1702 33 53 1582 00
UPDATE 3114 4477 1392 12 97 2394 00
UPDATE2 2004 2029 665 12 41 878 00
BATCH 8357 21896 10330 07 105 11007 00
SPOOL 1221 5755 262 58 08 188 00
81 Performance Evaluation
The measured times are compared against reference times to provide a rating - If the number of dialog steps in an hour is less than 1000 this hour is not considered - If the total number of transaction steps is less than 20000 the rating for the task is not performed (indicated by a gray icon in the table) - RED if at least three time ranges are rated RED - YELLOW if two time ranges are rated RED or at least three time ranges are rated YELLOW
The table below shows that no problem is expected on the application or database servers
Task Steps Application Server Performance Database Server Performance
Dia 27389
Upd 3114
HTTP 0
HTTPS 0
The ratings in the table above are determined by comparisons against the reference table below If the dialog response times are very poor it will cause a RED rating for the entire check
Task Reference for Avg Response Time (ms) Yellow Rating
Reference for Avg Response Time (ms) Red Rating
Reference for Avg DB time (ms) Yellow Rating
Reference for Avg DB time (ms) Red Rating
Dia 1200 3600 600 1800
Upd 2400 3600 1200 1800
HTTP 1200 3600 600 1800
HTTPS 1200 3600 600 1800
Confidential Performance Overview PRD 1839
SAPreg GoingLivetrade Check - Verification Session 06082015
82 Transaction Profile Check
The following tables show the response times and the number of dialog steps for the transactions that cause the heaviest workload in your system
821 Transactions by Total Workload
The following tables list the activities with the highest contribution to the total workload
WORKLOAD BY TRANSACTION (DIALOG HTTP(S)WS-HTTP )
Transaction Type Dialog Steps Total Resp Time in
Avg Resp Time in ms
Avg CPU Time in ms
Avg DB Time in ms
Avg GUI Time in ms
VL71 DIA 83 61 297185 178782 263658 71
FBL5N DIA 2919 33 4626 1991 1330 242
VA01 DIA 2034 32 6258 2092 1164 1764
VA02 DIA 2183 29 5306 2194 1287 639
ZSDP0023 DIA 365 22 24427 2144 19871 2116
ZWMSCP01 DIA 130 21 65254 13125 10103 649
ME22 DIA 167 17 41818 22914 3250 07
VT01N DIA 235 15 25864 13412 1976 2443
SESSION_MANAGER DIA 1078 14 5202 663 844 2716
VKM1 DIA 478 12 9796 3358 3746 86
43 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
WORKLOAD BY TRANSACTION (BATCH)
Transaction Dialog Steps Total Resp Time in
Total Resp Time in s
Total CPU Time in s
Total DB Time in s
ZFIP0102 156 109 44040 25240 42295
ZFIP0115 260 97 39320 21180 23386
ZSD_CREATE_ORDER_BY_REF 125 75 30160 13100 7000
ZWMS_FILE_MANAGER2 784 37 14820 930 612
ZSDP0031 8 33 13260 6780 2783
ZFIP0105 390 16 6560 4350 383
ZFIP0106 78 15 6010 4140 5722
RSBTCRTE 2412 12 4820 1240 336
ZSDP0063 2 10 4050 2130 1318
(BATCH) 3197 09 3750 810 506
392 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
822 Transactions by DB Load
The following transaction profiles list the transactions that have the greatest share in the database load sorted by percentage of total database access times
DATABASE LOAD BY TRANSACTIONS (DIALOG HTTP(S) )
Confidential Performance Overview PRD 1939
SAPreg GoingLivetrade Check - Verification Session 06082015
Transaction Type Dialog Steps Total DB Time in Avg DB Time in ms
VL71 DIA 83 127 263658
ZSDP0023 DIA 365 42 19871
FBL5N DIA 2919 22 1330
VA02 DIA 2183 16 1287
ZVC2 DIA 1360 15 1953
ZMMP0008 DIA 64 14 37798
VA01 DIA 2034 14 1164
ZSDP0013 DIA 47 12 43947
VKM1 DIA 478 10 3746
ZWMSCP01 DIA 130 08 10103
91 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
DATABASE LOAD BY TRANSACTIONS (BATCH)
Transaction Dialog Steps Total DB Time in Total DB Time in s
ZFIP0102 156 245 42300
ZFIP0115 260 135 23390
ZSD_CREATE_ORDER_BY_REF 125 41 7000
ZFIP0106 78 33 5720
ZSDP0031 8 16 2780
RSDB4UPD 2 12 2070
ZFII0002 1 09 1580
ZSDP0063 2 08 1320
ZSD_GENERATE_INFO_CONDITIONS 7 08 1320
ZFIP0101 263 07 1290
502 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
83 RFC Load by Initiating Action
The load in task type RFC is shown In the workload monitor this information is shown as Load from External Systems The calling system can be an application server of the system itself or any external system using the RFC interface The Initial Action is the calling program initiating the RFC The total response time for each initial action is shown as an absolute value and as a percentage compared to the total RFC load considered in this table The average times (per dialog step) are shown in milliseconds [ms] Calls from external systems are shown if they account for at least 8h or 5 of the total RFC load Local calls are shown if they account for at least 24h or 20 of the total RFC load
LOAD OVERVIEW
Initial System Load [s] Load
Local system PRD 4450 9957
Sum of external systems 19 043
RFC load (sum of above) 4469 10000
Confidential Performance Overview PRD 2039
SAPreg GoingLivetrade Check - Verification Session 06082015
Initial System Load [s] Load
RFC load in Performance Overview 10422 23321
Load of all task types in Performance Overview 51694 115668
TOP 20 RFC CALLS FROM LOCAL SYSTEM - AVERAGE TIMES [MS]
Initial System
Initial Action Total Resp
Time in s
of RFC Load
Avg Response
Time
Avg CPU Time
Avg DB Time
Avg Roll Wait Time
PRD RK2A1000_POST 892 1996 13097 147 87 20
PRD VF01 491 1099 25854 8767 14305 23
PRD VA01 468 1047 8402 170 543 14
PRD SAPLARFC 256 574 10505 208 305 17
PRD CA_QUEUE_ENTRY_BCS============CP 226 505 4628 1068 1398 251
PRD VA02 178 399 6343 1215 1490 14
PRD VL71 136 304 8330 698 330 118
PRD SAP_COLLECTOR_FOR_PERFMONITOR 132 295 33749 13108 7127 188
PRD VL02N 127 284 11757 2595 7164 18
PRD VL10X 96 215 4341 553 433 10
PRD VKM1 70 157 3532 813 930 35
PRD ZSDP0049 55 124 61422 1167 1553 64
PRD STMS 52 116 18555 1911 2091 77
PRD ZP01_FROM_ZP05_944988 52 115 171827 3233 1053 03
PRD ZSDP0010 45 100 74582 31983 32785 10
PRD XD02 43 097 403 116 126 05
PRD FB1D 42 093 1999 406 1263 06
PRD FBL5N 41 091 8700 630 866 14
PRD ZP01_FROM_ZP05_942398 38 086 63795 1867 2482 65
PRD FBZ5 32 071 319430 400 510 00
Confidential Performance Overview PRD 2139
SAPreg GoingLivetrade Check - Verification Session 06082015
9 SAP System Operating PRD
The daily operation of your system was analyzed We detected some problems that may impair system operation and stability
91 Availability based on Collector Protocols
A value of 100 means that the collector was available all day Available in the context of this report means that at least one SAP instance was running If the SAP collector was not running correctly the values in the table and graphics may be incorrect To check these logs call transaction ST03N (expert mode) and choose Collector and Performance DB -gt Performance Monitor Collector -gt Log
This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR that runs every hour The job does NOT check availability it carries out only general system tasks such as collecting and aggregating SAP performance data for all serversinstances The log does not contain any direct information about availability it contains only information about the status of the hourly statistical data collection
As of SAP Basis 640 system availability information is available in the CCMS (Computing Center Management System) of an SAP System in Service Level Reporting of SAP Solution Manager
This function is provided by the relevant Solution Manager Support Packages as an advanced development For more information refer to SAP Note 944496 which also lists the prerequisites that must be fulfilled before implementation can take place
92 Update Errors
In a system running under normal conditions only a small number of update errors should occur To set the rating for this check the number of active users is also taken into consideration
We did not detect any problems
Confidential SAP System Operating PRD 2239
SAPreg GoingLivetrade Check - Verification Session 06082015
93 Table Reorganization
The largest tables andor rapidly growing tables of system PRDwere checked No standard SAP recommendations for the applicable data volume management were found
94 Program Errors (ABAP Dumps)
50 ABAP dumps have been recorded in your system in the period 30072015 to 05082015 ABAP dumps are generally deleted after 7 days by default To view the ABAP dumps in your system call transaction ST22 and choose Selection Then select a timeframe
Date Number of Dumps
30072015 19
31072015 15
01082015 0
02082015 1
03082015 4
04082015 5
05082015 6
Name of Runtime Error Dumps Server (eg) User (eg) Date (eg) Time (eg)
TIME_OUT 1 SAP1R3P_PRD_00 EMOROCHO 30072015 104804
CALL_FUNCTION_SINGLE_LOGIN_REJ 2 SAP1R3P_PRD_00 SAPSYS 30072015 170339
DYNPRO_FIELD_CONVERSION 6 SAP1R3P_PRD_00 LORTEGA 31072015 172039
DBIF_RSQL_INVALID_RSQL 5 SAP1R3P_PRD_00 PREDROBAN 02082015 060047
CALL_FUNCTION_SEND_ERROR 2 SAP1R3P_PRD_00 JPVEND 03082015 073533
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY 3 SAP1R3P_PRD_00 LORTEGA 04082015 123208
RAISE_EXCEPTION 14 SAP1R3P_PRD_00 KCASTRO 05082015 094209
CONVT_NO_NUMBER 1 SAP1R3P_PRD_00 KABARCA 05082015 143511
UNCAUGHT_EXCEPTION 1 SAP1R3P_PRD_00 CBANCHON 05082015 150325
TSV_TNEW_PAGE_ALLOC_FAILED 5 SAP1R3P_PRD_00 FLUCAS 05082015 190338
MESSAGE_TYPE_X 10 SAP1R3P_PRD_00 INTERFASES 05082015 210129
It is important that you monitor ABAP dumps using transaction ST22 on a regular basis If ABAP dumps occur you should determine the cause as soon as possible Based on our analysis we found several ABAP dumps that need your attention Evaluate and resolve the above dumps If you cannot find a solution send a customer message to SAP to request support
Confidential SAP System Operating PRD 2339
SAPreg GoingLivetrade Check - Verification Session 06082015
10 Security
Critical security issues were found in your system
See the information in the following sections
Rating Check
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
101 ABAP Stack of PRD
1011 System Recommendations (ABAP)
System Recommendations is not used at all
Recommendation SAP strongly recommends applying important security fixes as soon as possible The System Recommendations application provides a detailed recommendation regarding which SAP security notes (ABAP and non-ABAP) should be implemented based on the actual status of the system and the notes already implemented This is a mandatory prerequisite for setting up a strong security patch process For more information go to httpservicesapcomsysrec
1012 Default Passwords of Standard Users
Standard users have default passwords
Recommendation Run report RSUSR003 to check the usage of default passwords by standard users
Ensure that users SAP (must exist in all clients) SAPCPIC and EARLYWATCH have non-default passwords in all clients For more information see Protecting Standard Users either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
Make sure that the standard password for user TMSADM has been changed in client 000 and delete this user in any other client SAP Note httpsservicesapcomsapsupportnotes1414256[1414256] describes a support tool to change the password of user TMSADM in all systems of the transport domain SAP Note httpsservicesapcomsapsupportnotes1552894[1552894] shows how to update the report RSUSR003 to show the status of user TMSADM
1013 ABAP Password Policy
If password login is allowed for specific instances only the password policy is checked only for these instances
10131 Password Complexity
PARAMETER LOGINMIN_PASSWORD_LNG
Confidential Security 2439
SAPreg GoingLivetrade Check - Verification Session 06082015
Rating Instance Current Value(s) Recommended Value
sap1r3p_PRD_00 6 8
The current system settings allow a password length of fewer than 8 characters This allows weak passwords Attackers may successfully recover these passwords and gain unauthorized access to the system
Recommendation Assign a minimum value of 8 to the profile parameter loginmin_password_lng
In addition SAP provides options to enforce complex passwords Find the current settings of the corresponding profile parameters in the following table
Parameter Instance Current Value(s)
loginmin_password_digits sap1r3p_PRD_00 0
loginmin_password_letters sap1r3p_PRD_00 0
loginmin_password_lowercase sap1r3p_PRD_00 0
loginmin_password_uppercase sap1r3p_PRD_00 0
loginmin_password_specials sap1r3p_PRD_00 0
Recommendation Enforce a minimum of 3 independent character categories using the corresponding profile parameters For more information see SAP Note httpsservicesapcomsapsupportnotes862989[862989] and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
1014 Gateway and Message Server Security
10141 Kernel Patch Level
Rating Kernel Release Current Kernel Patch Level Minimal Required Kernel Patch Level
700 135 260
To enable certain gateway security functionality a minimum kernel patch level is required Your system does not currently meet this requirement
Recommendation Update the kernel of your system to the newest kernel patch level available Update to a kernel patch level equal to or higher than the minimum required kernel patch level specified above For more information see SAP Note 1298433
10142 Gateway Security
Gateway Security Properties
The parameter GWREG_NO_CONN_INFO controls the activation of certain security properties of the SAP gateway It is defined as a bit mask with one bit per property
SAP Note httpsservicesapcomsapsupportnotes1298433[1298433] ldquoBypassing security in reginfo amp secinfordquo is not activated in your system The bit mask value for bit 1 is not set
Recommendation Enable the missing property by adding the bitmask value to the current value of GWREG_NO_CONN_INFO For more information about GWREG_NO_CONN_INFO see SAP Note 1444282
Confidential Security 2539
SAPreg GoingLivetrade Check - Verification Session 06082015
1015 Users with Critical Authorizations
For more information about the following check results see SAP Note 863362
Recommendation Depending on your environment review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations You can use the User Information System (transaction SUIM) to check the results For each check you can review the roles or profiles that include the authorization objects listed in the corresponding section
10151 Users Authorized to Start all Reports
This authorization allows critical functions and reports that do not contain their own authorization checks to be executed The specified number of users for each client have the checked authorization
Client No of Users Having This Authorization No of Valid Users Rating
001 2 3
400 147 160
Authorization objects
Object 1 S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2 S_PROGRAM with P_ACTION=SUBMIT P_GROUP=
Confidential Security 2639
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
81 Performance Evaluation 18
82 Transaction Profile Check 18
821 Transactions by Total Workload 19
822 Transactions by DB Load 19
83 RFC Load by Initiating Action 20
9 SAP System Operating PRD 22
91 Availability based on Collector Protocols 22
92 Update Errors 22
93 Table Reorganization 22
94 Program Errors (ABAP Dumps) 23
10 Security 24
101 ABAP Stack of PRD 24
1011 System Recommendations (ABAP) 24
1012 Default Passwords of Standard Users 24
1013 ABAP Password Policy 24
1014 Gateway and Message Server Security 25
1015 Users with Critical Authorizations 25
11 Software Change and Transport Management of PRD 27
111 SAP Netweaver Application Server ABAP of PRD 27
1111 Number of Changes 27
12 Data Volume Management (DVM) 28
13 ABAP Stack Configuration for PRD 29
131 Configuration for Central ABAP Instance sap1r3p_PRD_00 29
1311 Buffer Configuration 29
1312 Client Server Communication 29
1313 Enqueue Handling 29
1314 Obsolete Codepage Parameters 30
14 IBM i Database Checks 31
141 Important SAP Notes for IBM i 31
142 Reorganize Physical File Member 31
143 Missing Indexes 31
Confidential Contents 239
SAPreg GoingLivetrade Check - Verification Session 06082015
144 Disk arm utilization 31
145 Database Size 31
146 Backup Strategy 32
15 IBM i Specific Server Checks 33
151 iASP Configuration Check 33
152 Disk status 33
153 Data Protection in System ASP (ASP1) 33
154 Free space in System ASP (ASP1) 33
155 PTF Check 34
156 Disk Service Time 34
157 IBM i System parameters 34
158 SHRPOOL Pool 34
159 Paging Option 35
16 Trend Analysis 36
161 System Activity 36
162 Response Times 37
163 Application profile 37
164 System Operation 38
165 Hardware Capacity 38
Confidential Contents 339
SAPreg GoingLivetrade Check - Verification Session 06082015
2 Service Summary
The SAP reg GoingLivetrade Check (Verification Session) has detected severe problems that may cause you to lose business
We recommend that you take corrective action immediately
This report provides the results of the SAP reg GoingLivetrade Check (Verification Session) that was conducted on your SAP ERPsystem PRD Note The numbers in the Performance Overview PRD and Workload of System PRD sections refer to the time interval between 27072015 and 02082015 There is at least one area with critical performance system stability or security issues
The alert overview below summarizes the most important issues to be addressed Take corrective actions in these areas as soon as possible
ALERTS DECISIVE FOR RED REPORT
With the SAP kernel of your ABAP system the stability or consistency is at risk
ALERT OVERVIEW
A large number of deleted records have been found on the system
We found more than 30 ABAP dumps in your system
Standard users have default password
Secure password policy is not sufficiently enforced
A high number of users has critical authorizations
Perform the following Guided Self Services
Guided Self Service FAQ SAP Note
Security Optimization Service 696478
For more information about Guided Self-Services see SAP Enterprise Support Academy Register for an Expert-Guided Implementation Session for the Guided Self-Service at SAP Enterprise Support Academy - Learning Studio - Calendar
CHECK OVERVIEW
Topic Rating Topic Subtopic Rating Subtopic
SAP System Configuration
Performance Overview
Performance Evaluation
Workload Distribution
Workload by Application Module
DB Load Profile
SAP System Operating
Availability based on Collector Protocols
Confidential Service Summary 439
SAPreg GoingLivetrade Check - Verification Session 06082015
Topic Rating Topic Subtopic Rating Subtopic
Program Errors (ABAP Dumps)
Update Errors
Table Reorganization
Hardware Capacity
IBM i Database Checks
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
Security
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
Software Change Management
Number of Changes
Note All recommendations provided in this report are based on our general experience We advise that you test our recommendations before using them in your production system
Note If you have any questions about the accuracy of the checks in this report or the correct configuration of the SAP Solution Manager SAP reg GoingLivetrade Check (Verification Session) service create a customer message on component SV-SMG-SER
Note If you require assistance in resolving any concerns about the performance of the system or if you require a technical analysis ofother aspects of your system as highlighted in this report create a customer message on component SV-BO For details of how to set the appropriate priority level see SAP Note 67739
Performance Indicators for PRD
The following table shows the relevant performance indicators in various system areas
Area Indicators Value Trend
System Performance Active Users (gt400 steps) 30
Avg Availability per Week 100
Avg Response Time in Dialog Task 735 ms
Max Dialog Steps per Hour 1554
Avg Response Time at Peak Dialog Hour 676 ms
Avg Response Time in RFC Task 1383 ms
Max Number of RFCs per Hour 388
Avg RFC Response Time at Peak Hour 1370 ms
Hardware Capacity Max CPU Utilization on DB Server 37
Database Performance Avg DB Request Time in Dialog Task 268 ms
Confidential Service Summary 539
SAPreg GoingLivetrade Check - Verification Session 06082015
Area Indicators Value Trend
Avg DB Request Time for RFC 158 ms
Avg DB Request Time in Update Task 239 ms
Database Space Management DB Size 137091 GB
DB Growth Last Month 0 GB
Confidential Service Summary 639
SAPreg GoingLivetrade Check - Verification Session 06082015
3 Landscape
31 Products and Components in current Landscape
PRODUCT
SID SAP Product Product Version
PRD SAP ERP 60
MAIN INSTANCES (ABAP OR JAVA BASED)
SID Main Instance
PRD SAP ECC Server
DATABASES
SID Database System Database Version
PRD DB2 UDB for iSeries V5R4M0
32 Servers in current Landscape
SAP APPLICATION SERVERS
SID Host Instance Name Logical Host ABAP JAVA
PRD sap1r3p sap1r3p_PRD_00 SAP1R3P
DB SERVERS
SID Host Logical Host (SAPDBHOST)
PRD sap1r3p SAP1R3P
33 Hardware Configuration
HOST OVERVIEW
Host Operating System CPUs Memory in MB
sap1r3p OS400 54 0 0
Confidential Landscape 739
SAPreg GoingLivetrade Check - Verification Session 06082015
4 Software Configuration For PRD
We have listed important recommendations concerning the current software configuration on your system These recommendations should be implemented at the earliest opportunity
Your systems software versions are checked If known issues with the software versions installed are identified they are highlighted
41 SAP Application Release - Maintenance Phases
SAP Product Version End of Mainstream Maintenance Status
SAP ERP 60 31122025
In October 2014 SAP announced a maintenance extension for SAP Business Suite 7 core application releases to 2025 If you are running a relevant release see SAP Note httpsservicesapcomsapsupportnotes1648480[1648480] for more details and applicable restrictions
42 Support Package Maintenance - ABAP
The following table shows an overview of currently installed software components
SUPPORT PACKAGES
Software Component
Version Patch Level
Latest Avail Patch Level
Support Package Component Description
EA-APPL 600 8 27 SAPKGPAD08 SAP R3 Enterprise PLM SCM Finance
EA-DFPS 600 8 27 SAPKGPDD08 SAP R3 Enterprise Defense Forces amp Public Security
EA-FINSERV 600 8 28 SAPKGPFD08 SAP R3 Enterprise Financial Services
EA-GLTRADE 600 8 27 SAPKGPGD08 SAP R3 Enterprise Global Trade
EA-HR 600 15 123 SAPKGPHD15 SAP R3 Enterprise Human Resources
EA-IPPE 400 8 27 SAPKGPID08 SAP R3 Enterprise Integrated Product and Process Engineering
EA-PS 600 8 27 SAPKGPPD08 SAP R3 Enterprise Public Services
EA-RETAIL 600 8 27 SAPKGPRD08 SAP R3 Enterprise Retail
ECC-DIMP 600 8 27 SAPK-60008INECCDIMP ECC Discrete Industries Mill Products
ERECRUIT 600 8 27 SAPK-60008INERECRUIT SAP E-Recruiting
FI-CA 600 8 8 SAPK-60008INFICA FI-CA Contract Accounts Receivable and Payable (virtuell)
FI-CAX 600 8 27 SAPK-60008INFICAX FI-CAX Extended FI-CA
FINBASIS 600 8 27 SAPK-60008INFINBASIS SAP R3 Enterprise FINBASIS
INSURANCE 600 8 27 SAPK-60008ININSURANC INSURANCE SAP Insurance
IS-CWM 600 8 27 SAPK-60008INISCWM IS-CWM Catch Weight Management
IS-H 600 8 40 SAPK-60008INISH IS-Hospital
IS-M 600 8 27 SAPK-60008INISM IS Media
IS-OIL 600 8 27 SAPK-60008INISOIL IS-OIL SAP OIL amp GAS Upstream Downstream
IS-PS-CA 600 8 27 SAPK-60008INISPSCA IS-PS-CA TaxampRevenue Campus Management
Confidential Software Configuration For PRD 839
SAPreg GoingLivetrade Check - Verification Session 06082015
Software Component
Version Patch Level
Latest Avail Patch Level
Support Package Component Description
IS-UT 600 8 27 SAPK-60008INISUT IS-UT
LSOFE 600 8 27 SAPK-60008INLSOFE Learning Solution - Front End
PI_BASIS 2005_1_700 11 26 SAPKIPYJ7B SAP R3 Basis Plug-In
SAP_ABA 700 11 32 SAPKA70011 SAP Application Basis
SAP_AP 700 8 33 SAPKNA7008 SAP Application Platform
SAP_APPL 600 8 27 SAPKH60008 SAP R3 Standard
SAP_BASIS 700 11 32 SAPKB70011 SAP Basis Component
SAP_BW 700 12 34 SAPKW70012 SAP Business Information Warehouse
SAP_HR 600 15 123 SAPKE60015 SAP R3 Standard HR
SEM-BW 600 8 27 SAPKGS6008 SAP SEM Server
ST-API 01L_ECC600 0 SAP Service Tools for Applications Plug-In
ST-PI 2008_1_700 0 12 SAP Solution Tools Plug-In
43 SAP Kernel Release
Instance SAP Kernel Release Patch Level
sap1r3p 00 700 135
Instance(s) SAP Kernel Release Patch Level Age in Months OS Family
sap1r3p_PRD_00 700 135 94
431 Downward Compatible Kernel
You are running an SAP kernel version that has been outdated since Q32012 This kernel version was replaced by the downward-compatible kernel You can continue to use your current kernel version but if an issue occurs with your current kernel a fix will be provided for SAP kernel 721 only Recommendation To avoid the potential risks associated with running an outdated SAP kernel version you should replace this version with downward-compatible SAP kernel 721 The downward-compatible kernel is a special validated SAP kernel that improves the stability of your system Requirements and prerequisites to install the downward-compatible kernel are summarized below
SAP Note Number
What to Do Description
1222907 Implement SAP note or SP Runtime object with incorrect alignment
1610716 Implement SAP note or SP and execute report Correcting runtime objects with incorrect alignment
1716826 Information Usage of the downward compatible Kernel 721 (EXT)
1713986 Installation instructions Installation of Kernel 721 (EXT)
1744209 Information SAP Kernel 720 and 721 Versions and Kernel Patch Levels
For security reasons the programs rfcexec and startrfc are no longer shipped together with the 720 kernel If you run scenarios that require these programs we recommend that you download and install the corresponding files from the NW RFC SDK 720 For details refer to SAP Note 1581595
4311 Required Implementation in SAP_BASIS
You must implement the SAP Notes mentioned in this section before installing the downward-compatible kernel
Confidential Software Configuration For PRD 939
SAPreg GoingLivetrade Check - Verification Session 06082015
4312 Required Parameter Settings
As a prerequisite for running the downward-compatible kernel the following parameters need to be set
Parameter Description Current Value Recommendation
rslgnew_layout System Log Format 9
432 Issues with current SAP Kernel
Your SAP kernel release may encounter serious problems
SAP tests all SAP kernels that are released However your patch level has been found to be unstable in certain cases and is therefore not recommended For more information see the release information for each SAP kernel patch on SAP Service Marketplace
For more information about issues concerning your current SAP kernel see the SAP Notes in the table below
Recommendation If the SAP kernel shipped with the latest Support Package stack of your product has the same issue as listed below install a more recent SAP kernel available in the Patches section of SAP Service Marketplace
SAP Note Short Text Risk
1132350 Incomplete update records
1150058 Incomplete update records
1223994 Composite SAP note Incomplete update records
433 Additional Remarks
SAP releases Support Package stacks (including SAP kernel patches) on a regular basis for most products (generally 2ndash4 times a year) We recommend that you base your software maintenance strategy on these stacks
You should only consider using a more recent SAP kernel patch than that shipped with the latest Support Package Stack for your product if specific errors occur
For more information see SAP Service Marketplace at httpssupportsapcomsoftwarepatchesstackshtml (SAP SupportPackage Stack information) and httpssupportsapcompatches (patchinformation)
Confidential Software Configuration For PRD 1039
SAPreg GoingLivetrade Check - Verification Session 06082015
5 Service Preparation and Data Quality of PRD
SAP ERP system PRD is not fully prepared for delivery of future remote services
Rating Check Performed
Service Data Quality
ST-PI and ST-API Plug-Ins
Service Preparation Check (RTCCTOOL)
Service Data Control Center
Hardware Utilization Data
In preparation for SAP services ensure that connections collectors and service tools are up to date These functionalities are explained in SAP Notes httpsservicesapcomsapsupportnotes91488[91488] and 1172939
51 Service Data Quality
For this service data of high importance is missing The service data is collected by the Service Data Control Center (SDCCN) or read from the Solution Managers BW or Configuration and Change Database (CCDB) This section comprehensively shows issues with the data quality and provides hints on how to resolve them
LEGEND FOR PRIORITY IN SERVICE DATA QUALITY
Prio Explanation Impact of Missing or Erroneous Data
Overall important data are missing Detecting a critical situation may fail Report cannot be rated green or yellow
Data for an important chapter are missing Some issues may not be detected Report cannot be rated green
Some important check could not be processed The report can be rated green nevertheless
Only checks of minor importance are affected
An optional check was skipped
511 Quality of Data in Service Data Control Center (SDCC)
QUALITY OF SERVICE DATA IN ST-PI
Prio Report Area affected Details and Related ST-PI Logical Function SAP Note
System Monitoring of Server (host) sap1r3p
During hardware data collection no SAPOSCOL was found It is either not running or not accessible ST-PI function EWA_GET_HARDWARE_INFO used in section Hardware Capacity
1309499
512 Quality of Service Data in Solution Manager Diagnostics - BW
Prio Report Area affected
Details and Related Infocube SAP Note
Workload of ABAP System PRD
Reading performance data from BW returned neither data nor an error code A timeout may have occurred Infocube 0CCMSMTPH used in section Workload Overview PRD
1332428
Confidential Service Preparation and Data Quality of PRD 1139
SAPreg GoingLivetrade Check - Verification Session 06082015
52 ST-PI and ST-API Plug-Ins
The table below shows the service plug-ins implemented and their releases and patch levels These recommendations are derived from report RTCCTOOL For more information about RTCCTOOL see SAP Note 309711
Rating Plug-In Release Patch Level Release Rec Patch Level Rec
ST-API 01L_ECC600 0 01R_700 1
ST-PI 2008_1_700 0 2008_1_700 11
Recommendation The Service Tools for Applications Plug-In (ST-API) is not up-to-date For more information see SAP Note 69455 The Solution Tools Plug-In (ST-PI) is not up-to-date For more information see SAP Note 539977
53 Service Preparation Check (RTCCTOOL)
Before we can ship any services the latest version of the SAP Service tools must be implemented in your system Report RTCCTOOL was last run on 06082015 During the check the tool detected issues for which a RED rating was set
Overall Status SAP Note Title Tool Status Manual Status
69455 [Note 69455] Addon ST-API 01R_700
69455 [Note 69455] ST-API 01R_700 Support Package 1
539977 [Note 539977] ST-PI 2008_1_700 Support Package 11
69455 [Note 69455] Proc after addon impl
539977 [Note 539977] Addon ST-PI 2008_1_700
539977 Note 1300023 for ST-PI
539977 Note 1312413 for ST-PI
539977 Note 1293657 for ST-PI
12103 [Note 12103] Collectors and TCOLL
207223 [Note 207223] EWAlert setup
Recommendation [Note 69455] Addon ST-API 01R_700 Servicetools for Applications Plug-In for NetWeaver 04s Basis 70x From httpsupportsapcomsupporttools- gtST-API-gtInstallationsampUpgrades download the installation ST-API 01R_700 Upload to tx SAINT and install as per note 69455 Then restart report RTCCTOOL and choose List-gtRefresh from SAPNet
[Note 69455] ST-API 01R_700 Support Package 1 Addon supportpackage level 1 for ST-API 01R_700 for NetWeaver 04s Basis 70x From httpsupportsapcomsupporttools- gtST-API-gtSupport packages-gtST-API 01R_700 download patches up to SAPKITAB7N For basis gt=700 use the Maintenance optimizer to release the download Upload from frontend to transaction SPAM define a queue and import
[Note 539977] ST-PI 2008_1_700 Support Package 11 Addon supportpackage level 11 for ST-PI 2008_1_700 for 700 [patches up to level 11 for Basis tools for services] Open httpsupportsapcomsupporttools- gtST-PI supportpk-gt ST-PI2008_1_700 Add patch SAPKITLRDL (and predecessors if not yet implemented) download basket Release basket via Maintenance optimizer Upload from frontend into transaction SPAM define a queue and import the queue
54 Performance DB (ST03 ST06)
Analysis of ST06 and history data indicate some problems with SAPOSCOL Check SAPOSCOL and see SAP Note 1309499
Confidential Service Preparation and Data Quality of PRD 1239
SAPreg GoingLivetrade Check - Verification Session 06082015
55 Hardware Utilization Data
Host Operating System Performance Data
sap1r3p OS not detected OK
Hardware capacity checks could not be run successfully due to missing data See SAP Note 1309499
Confidential Service Preparation and Data Quality of PRD 1339
SAPreg GoingLivetrade Check - Verification Session 06082015
6 Hardware Capacity
We have checked your system for potential CPU bottlenecks and found that the hardware is sufficient for the current workload
Note Hardware Capacity evaluation is based on hosts for which data is least partially available
61 Overview System PRD
General This analysis focuses on the workload during the peak working hours (9-11 13) and is based on the hourly averages collected by SAPOSCOL For information about the definition of peak working hours see SAP Note 1251291
CPU If the average CPU load exceeds 75 temporary CPU bottlenecks are likely to occur An average CPU load of more than 90 is a strong indicator of a CPU bottleneck
Memory If your hardware cannot handle the maximum memory consumption this causes a memory bottleneck in your SAP system that can impair performance The paging rating depends on the ratio of paging activity to physical memory A ratio exceeding 25 indicates high memory usage (if Java has been detected 0 ) and values above 50 (Java 10 ) demonstrate a main memory bottleneck
Server Max CPU load [] Date Rating RAM [MB]
sap1r3p 37 21072015 0
Note In case of virtualization or IaaS scenarios (eg IBM PowerVM VMware Amazon AWS ) it might be that for some hosts the CPU rating is yellow or red although the utilization value is quite low In this case the relevant host could not use maximum usable capacity due to a resource shortage within the virtualized infrastructure (eg IBM PowerVM Shared Pool CPU utilization)
Confidential Hardware Capacity 1439
SAPreg GoingLivetrade Check - Verification Session 06082015
7 Workload of System PRD
This chart displays the main task types and indicates how their workload is distributed in the system The table below lists the detailed KPIs
RESPONSE TIME COMPONENTS IN HOURS
Task Type Response Time Wait Time CPU Time DB Time GUI Time
DIALOG 55 00 20 20 07
BATCH 51 00 24 26 00
RFC 29 00 04 03 00
UPDATE 04 00 01 02 00
Others 02 00 00 00 00
71 Workload By Users
User activity is measured in the workload monitor Only users of at least medium activity are counted as active users
Users Low Activity Medium Activity High Activity Total Users
dialog steps per week 1 to 399 400 to 4799 4800 or more
measured in system 82 29 1 112
72 Workload Distribution PRD
The performance of your system was analyzed with respect to the workload distribution We did not detect any major problems that could affect the performance of your SAP system
721 Workload by Application Module
Confidential Workload of System PRD 1539
SAPreg GoingLivetrade Check - Verification Session 06082015
The following diagrams show how each application module contributes to the total system workload Two workload aspects are shown
- CPU time total CPU load on all servers in the system landscape
- Database time total database load generated by the application
All programs that are not classified in the SAP Application Hierarchy (transaction SE81) are summarized in the Un-Assigned category Customer programs industry solutions and third-party add-on developments fall into this category
722 DB Load Profile
Confidential Workload of System PRD 1639
SAPreg GoingLivetrade Check - Verification Session 06082015
The number of work processes creating database load in parallel is not significantly high
The following diagram shows the DB load caused by dialog RFC HTTP(S) and background tasks over different time frames The data provided in the diagram represents the average number of database processes occupied by each task type in the database during the specified time frames These statistics are calculated as a weekly average the average values over six working days with a unit of one hour Periods between 0000-0600 and 2100-2400 contain an average value per hour as these are not core business hours You can enable 24-hour monitoring by implementing SAP Note 17750 With 24-hour monitoring the time profile returns the workload of the system or application server on an hourly basis rather than returning an average value per hour for the periods 0000ndash0600 and 2100ndash2400 By comparing the load profiles for dialog and background activity you can get an overview of the volume of background activity during online working hours
Confidential Workload of System PRD 1739
SAPreg GoingLivetrade Check - Verification Session 06082015
8 Performance Overview PRD
The performance of your system was analyzed with respect to the average response times and total workload We did not detect any major problems that could affect the performance of your system
Rating Check
Performance Evaluation
The following table shows the average response times for various task types
AVERAGES OF RESPONSE TIME COMPONENTS IN MS
Task type Dialog Steps Response Time CPU Time Wait Time Load Time DB Time GUI Time
DIALOG 27390 7350 2584 56 60 2679 936
RFC 7535 13832 1702 33 53 1582 00
UPDATE 3114 4477 1392 12 97 2394 00
UPDATE2 2004 2029 665 12 41 878 00
BATCH 8357 21896 10330 07 105 11007 00
SPOOL 1221 5755 262 58 08 188 00
81 Performance Evaluation
The measured times are compared against reference times to provide a rating - If the number of dialog steps in an hour is less than 1000 this hour is not considered - If the total number of transaction steps is less than 20000 the rating for the task is not performed (indicated by a gray icon in the table) - RED if at least three time ranges are rated RED - YELLOW if two time ranges are rated RED or at least three time ranges are rated YELLOW
The table below shows that no problem is expected on the application or database servers
Task Steps Application Server Performance Database Server Performance
Dia 27389
Upd 3114
HTTP 0
HTTPS 0
The ratings in the table above are determined by comparisons against the reference table below If the dialog response times are very poor it will cause a RED rating for the entire check
Task Reference for Avg Response Time (ms) Yellow Rating
Reference for Avg Response Time (ms) Red Rating
Reference for Avg DB time (ms) Yellow Rating
Reference for Avg DB time (ms) Red Rating
Dia 1200 3600 600 1800
Upd 2400 3600 1200 1800
HTTP 1200 3600 600 1800
HTTPS 1200 3600 600 1800
Confidential Performance Overview PRD 1839
SAPreg GoingLivetrade Check - Verification Session 06082015
82 Transaction Profile Check
The following tables show the response times and the number of dialog steps for the transactions that cause the heaviest workload in your system
821 Transactions by Total Workload
The following tables list the activities with the highest contribution to the total workload
WORKLOAD BY TRANSACTION (DIALOG HTTP(S)WS-HTTP )
Transaction Type Dialog Steps Total Resp Time in
Avg Resp Time in ms
Avg CPU Time in ms
Avg DB Time in ms
Avg GUI Time in ms
VL71 DIA 83 61 297185 178782 263658 71
FBL5N DIA 2919 33 4626 1991 1330 242
VA01 DIA 2034 32 6258 2092 1164 1764
VA02 DIA 2183 29 5306 2194 1287 639
ZSDP0023 DIA 365 22 24427 2144 19871 2116
ZWMSCP01 DIA 130 21 65254 13125 10103 649
ME22 DIA 167 17 41818 22914 3250 07
VT01N DIA 235 15 25864 13412 1976 2443
SESSION_MANAGER DIA 1078 14 5202 663 844 2716
VKM1 DIA 478 12 9796 3358 3746 86
43 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
WORKLOAD BY TRANSACTION (BATCH)
Transaction Dialog Steps Total Resp Time in
Total Resp Time in s
Total CPU Time in s
Total DB Time in s
ZFIP0102 156 109 44040 25240 42295
ZFIP0115 260 97 39320 21180 23386
ZSD_CREATE_ORDER_BY_REF 125 75 30160 13100 7000
ZWMS_FILE_MANAGER2 784 37 14820 930 612
ZSDP0031 8 33 13260 6780 2783
ZFIP0105 390 16 6560 4350 383
ZFIP0106 78 15 6010 4140 5722
RSBTCRTE 2412 12 4820 1240 336
ZSDP0063 2 10 4050 2130 1318
(BATCH) 3197 09 3750 810 506
392 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
822 Transactions by DB Load
The following transaction profiles list the transactions that have the greatest share in the database load sorted by percentage of total database access times
DATABASE LOAD BY TRANSACTIONS (DIALOG HTTP(S) )
Confidential Performance Overview PRD 1939
SAPreg GoingLivetrade Check - Verification Session 06082015
Transaction Type Dialog Steps Total DB Time in Avg DB Time in ms
VL71 DIA 83 127 263658
ZSDP0023 DIA 365 42 19871
FBL5N DIA 2919 22 1330
VA02 DIA 2183 16 1287
ZVC2 DIA 1360 15 1953
ZMMP0008 DIA 64 14 37798
VA01 DIA 2034 14 1164
ZSDP0013 DIA 47 12 43947
VKM1 DIA 478 10 3746
ZWMSCP01 DIA 130 08 10103
91 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
DATABASE LOAD BY TRANSACTIONS (BATCH)
Transaction Dialog Steps Total DB Time in Total DB Time in s
ZFIP0102 156 245 42300
ZFIP0115 260 135 23390
ZSD_CREATE_ORDER_BY_REF 125 41 7000
ZFIP0106 78 33 5720
ZSDP0031 8 16 2780
RSDB4UPD 2 12 2070
ZFII0002 1 09 1580
ZSDP0063 2 08 1320
ZSD_GENERATE_INFO_CONDITIONS 7 08 1320
ZFIP0101 263 07 1290
502 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
83 RFC Load by Initiating Action
The load in task type RFC is shown In the workload monitor this information is shown as Load from External Systems The calling system can be an application server of the system itself or any external system using the RFC interface The Initial Action is the calling program initiating the RFC The total response time for each initial action is shown as an absolute value and as a percentage compared to the total RFC load considered in this table The average times (per dialog step) are shown in milliseconds [ms] Calls from external systems are shown if they account for at least 8h or 5 of the total RFC load Local calls are shown if they account for at least 24h or 20 of the total RFC load
LOAD OVERVIEW
Initial System Load [s] Load
Local system PRD 4450 9957
Sum of external systems 19 043
RFC load (sum of above) 4469 10000
Confidential Performance Overview PRD 2039
SAPreg GoingLivetrade Check - Verification Session 06082015
Initial System Load [s] Load
RFC load in Performance Overview 10422 23321
Load of all task types in Performance Overview 51694 115668
TOP 20 RFC CALLS FROM LOCAL SYSTEM - AVERAGE TIMES [MS]
Initial System
Initial Action Total Resp
Time in s
of RFC Load
Avg Response
Time
Avg CPU Time
Avg DB Time
Avg Roll Wait Time
PRD RK2A1000_POST 892 1996 13097 147 87 20
PRD VF01 491 1099 25854 8767 14305 23
PRD VA01 468 1047 8402 170 543 14
PRD SAPLARFC 256 574 10505 208 305 17
PRD CA_QUEUE_ENTRY_BCS============CP 226 505 4628 1068 1398 251
PRD VA02 178 399 6343 1215 1490 14
PRD VL71 136 304 8330 698 330 118
PRD SAP_COLLECTOR_FOR_PERFMONITOR 132 295 33749 13108 7127 188
PRD VL02N 127 284 11757 2595 7164 18
PRD VL10X 96 215 4341 553 433 10
PRD VKM1 70 157 3532 813 930 35
PRD ZSDP0049 55 124 61422 1167 1553 64
PRD STMS 52 116 18555 1911 2091 77
PRD ZP01_FROM_ZP05_944988 52 115 171827 3233 1053 03
PRD ZSDP0010 45 100 74582 31983 32785 10
PRD XD02 43 097 403 116 126 05
PRD FB1D 42 093 1999 406 1263 06
PRD FBL5N 41 091 8700 630 866 14
PRD ZP01_FROM_ZP05_942398 38 086 63795 1867 2482 65
PRD FBZ5 32 071 319430 400 510 00
Confidential Performance Overview PRD 2139
SAPreg GoingLivetrade Check - Verification Session 06082015
9 SAP System Operating PRD
The daily operation of your system was analyzed We detected some problems that may impair system operation and stability
91 Availability based on Collector Protocols
A value of 100 means that the collector was available all day Available in the context of this report means that at least one SAP instance was running If the SAP collector was not running correctly the values in the table and graphics may be incorrect To check these logs call transaction ST03N (expert mode) and choose Collector and Performance DB -gt Performance Monitor Collector -gt Log
This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR that runs every hour The job does NOT check availability it carries out only general system tasks such as collecting and aggregating SAP performance data for all serversinstances The log does not contain any direct information about availability it contains only information about the status of the hourly statistical data collection
As of SAP Basis 640 system availability information is available in the CCMS (Computing Center Management System) of an SAP System in Service Level Reporting of SAP Solution Manager
This function is provided by the relevant Solution Manager Support Packages as an advanced development For more information refer to SAP Note 944496 which also lists the prerequisites that must be fulfilled before implementation can take place
92 Update Errors
In a system running under normal conditions only a small number of update errors should occur To set the rating for this check the number of active users is also taken into consideration
We did not detect any problems
Confidential SAP System Operating PRD 2239
SAPreg GoingLivetrade Check - Verification Session 06082015
93 Table Reorganization
The largest tables andor rapidly growing tables of system PRDwere checked No standard SAP recommendations for the applicable data volume management were found
94 Program Errors (ABAP Dumps)
50 ABAP dumps have been recorded in your system in the period 30072015 to 05082015 ABAP dumps are generally deleted after 7 days by default To view the ABAP dumps in your system call transaction ST22 and choose Selection Then select a timeframe
Date Number of Dumps
30072015 19
31072015 15
01082015 0
02082015 1
03082015 4
04082015 5
05082015 6
Name of Runtime Error Dumps Server (eg) User (eg) Date (eg) Time (eg)
TIME_OUT 1 SAP1R3P_PRD_00 EMOROCHO 30072015 104804
CALL_FUNCTION_SINGLE_LOGIN_REJ 2 SAP1R3P_PRD_00 SAPSYS 30072015 170339
DYNPRO_FIELD_CONVERSION 6 SAP1R3P_PRD_00 LORTEGA 31072015 172039
DBIF_RSQL_INVALID_RSQL 5 SAP1R3P_PRD_00 PREDROBAN 02082015 060047
CALL_FUNCTION_SEND_ERROR 2 SAP1R3P_PRD_00 JPVEND 03082015 073533
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY 3 SAP1R3P_PRD_00 LORTEGA 04082015 123208
RAISE_EXCEPTION 14 SAP1R3P_PRD_00 KCASTRO 05082015 094209
CONVT_NO_NUMBER 1 SAP1R3P_PRD_00 KABARCA 05082015 143511
UNCAUGHT_EXCEPTION 1 SAP1R3P_PRD_00 CBANCHON 05082015 150325
TSV_TNEW_PAGE_ALLOC_FAILED 5 SAP1R3P_PRD_00 FLUCAS 05082015 190338
MESSAGE_TYPE_X 10 SAP1R3P_PRD_00 INTERFASES 05082015 210129
It is important that you monitor ABAP dumps using transaction ST22 on a regular basis If ABAP dumps occur you should determine the cause as soon as possible Based on our analysis we found several ABAP dumps that need your attention Evaluate and resolve the above dumps If you cannot find a solution send a customer message to SAP to request support
Confidential SAP System Operating PRD 2339
SAPreg GoingLivetrade Check - Verification Session 06082015
10 Security
Critical security issues were found in your system
See the information in the following sections
Rating Check
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
101 ABAP Stack of PRD
1011 System Recommendations (ABAP)
System Recommendations is not used at all
Recommendation SAP strongly recommends applying important security fixes as soon as possible The System Recommendations application provides a detailed recommendation regarding which SAP security notes (ABAP and non-ABAP) should be implemented based on the actual status of the system and the notes already implemented This is a mandatory prerequisite for setting up a strong security patch process For more information go to httpservicesapcomsysrec
1012 Default Passwords of Standard Users
Standard users have default passwords
Recommendation Run report RSUSR003 to check the usage of default passwords by standard users
Ensure that users SAP (must exist in all clients) SAPCPIC and EARLYWATCH have non-default passwords in all clients For more information see Protecting Standard Users either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
Make sure that the standard password for user TMSADM has been changed in client 000 and delete this user in any other client SAP Note httpsservicesapcomsapsupportnotes1414256[1414256] describes a support tool to change the password of user TMSADM in all systems of the transport domain SAP Note httpsservicesapcomsapsupportnotes1552894[1552894] shows how to update the report RSUSR003 to show the status of user TMSADM
1013 ABAP Password Policy
If password login is allowed for specific instances only the password policy is checked only for these instances
10131 Password Complexity
PARAMETER LOGINMIN_PASSWORD_LNG
Confidential Security 2439
SAPreg GoingLivetrade Check - Verification Session 06082015
Rating Instance Current Value(s) Recommended Value
sap1r3p_PRD_00 6 8
The current system settings allow a password length of fewer than 8 characters This allows weak passwords Attackers may successfully recover these passwords and gain unauthorized access to the system
Recommendation Assign a minimum value of 8 to the profile parameter loginmin_password_lng
In addition SAP provides options to enforce complex passwords Find the current settings of the corresponding profile parameters in the following table
Parameter Instance Current Value(s)
loginmin_password_digits sap1r3p_PRD_00 0
loginmin_password_letters sap1r3p_PRD_00 0
loginmin_password_lowercase sap1r3p_PRD_00 0
loginmin_password_uppercase sap1r3p_PRD_00 0
loginmin_password_specials sap1r3p_PRD_00 0
Recommendation Enforce a minimum of 3 independent character categories using the corresponding profile parameters For more information see SAP Note httpsservicesapcomsapsupportnotes862989[862989] and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
1014 Gateway and Message Server Security
10141 Kernel Patch Level
Rating Kernel Release Current Kernel Patch Level Minimal Required Kernel Patch Level
700 135 260
To enable certain gateway security functionality a minimum kernel patch level is required Your system does not currently meet this requirement
Recommendation Update the kernel of your system to the newest kernel patch level available Update to a kernel patch level equal to or higher than the minimum required kernel patch level specified above For more information see SAP Note 1298433
10142 Gateway Security
Gateway Security Properties
The parameter GWREG_NO_CONN_INFO controls the activation of certain security properties of the SAP gateway It is defined as a bit mask with one bit per property
SAP Note httpsservicesapcomsapsupportnotes1298433[1298433] ldquoBypassing security in reginfo amp secinfordquo is not activated in your system The bit mask value for bit 1 is not set
Recommendation Enable the missing property by adding the bitmask value to the current value of GWREG_NO_CONN_INFO For more information about GWREG_NO_CONN_INFO see SAP Note 1444282
Confidential Security 2539
SAPreg GoingLivetrade Check - Verification Session 06082015
1015 Users with Critical Authorizations
For more information about the following check results see SAP Note 863362
Recommendation Depending on your environment review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations You can use the User Information System (transaction SUIM) to check the results For each check you can review the roles or profiles that include the authorization objects listed in the corresponding section
10151 Users Authorized to Start all Reports
This authorization allows critical functions and reports that do not contain their own authorization checks to be executed The specified number of users for each client have the checked authorization
Client No of Users Having This Authorization No of Valid Users Rating
001 2 3
400 147 160
Authorization objects
Object 1 S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2 S_PROGRAM with P_ACTION=SUBMIT P_GROUP=
Confidential Security 2639
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
144 Disk arm utilization 31
145 Database Size 31
146 Backup Strategy 32
15 IBM i Specific Server Checks 33
151 iASP Configuration Check 33
152 Disk status 33
153 Data Protection in System ASP (ASP1) 33
154 Free space in System ASP (ASP1) 33
155 PTF Check 34
156 Disk Service Time 34
157 IBM i System parameters 34
158 SHRPOOL Pool 34
159 Paging Option 35
16 Trend Analysis 36
161 System Activity 36
162 Response Times 37
163 Application profile 37
164 System Operation 38
165 Hardware Capacity 38
Confidential Contents 339
SAPreg GoingLivetrade Check - Verification Session 06082015
2 Service Summary
The SAP reg GoingLivetrade Check (Verification Session) has detected severe problems that may cause you to lose business
We recommend that you take corrective action immediately
This report provides the results of the SAP reg GoingLivetrade Check (Verification Session) that was conducted on your SAP ERPsystem PRD Note The numbers in the Performance Overview PRD and Workload of System PRD sections refer to the time interval between 27072015 and 02082015 There is at least one area with critical performance system stability or security issues
The alert overview below summarizes the most important issues to be addressed Take corrective actions in these areas as soon as possible
ALERTS DECISIVE FOR RED REPORT
With the SAP kernel of your ABAP system the stability or consistency is at risk
ALERT OVERVIEW
A large number of deleted records have been found on the system
We found more than 30 ABAP dumps in your system
Standard users have default password
Secure password policy is not sufficiently enforced
A high number of users has critical authorizations
Perform the following Guided Self Services
Guided Self Service FAQ SAP Note
Security Optimization Service 696478
For more information about Guided Self-Services see SAP Enterprise Support Academy Register for an Expert-Guided Implementation Session for the Guided Self-Service at SAP Enterprise Support Academy - Learning Studio - Calendar
CHECK OVERVIEW
Topic Rating Topic Subtopic Rating Subtopic
SAP System Configuration
Performance Overview
Performance Evaluation
Workload Distribution
Workload by Application Module
DB Load Profile
SAP System Operating
Availability based on Collector Protocols
Confidential Service Summary 439
SAPreg GoingLivetrade Check - Verification Session 06082015
Topic Rating Topic Subtopic Rating Subtopic
Program Errors (ABAP Dumps)
Update Errors
Table Reorganization
Hardware Capacity
IBM i Database Checks
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
Security
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
Software Change Management
Number of Changes
Note All recommendations provided in this report are based on our general experience We advise that you test our recommendations before using them in your production system
Note If you have any questions about the accuracy of the checks in this report or the correct configuration of the SAP Solution Manager SAP reg GoingLivetrade Check (Verification Session) service create a customer message on component SV-SMG-SER
Note If you require assistance in resolving any concerns about the performance of the system or if you require a technical analysis ofother aspects of your system as highlighted in this report create a customer message on component SV-BO For details of how to set the appropriate priority level see SAP Note 67739
Performance Indicators for PRD
The following table shows the relevant performance indicators in various system areas
Area Indicators Value Trend
System Performance Active Users (gt400 steps) 30
Avg Availability per Week 100
Avg Response Time in Dialog Task 735 ms
Max Dialog Steps per Hour 1554
Avg Response Time at Peak Dialog Hour 676 ms
Avg Response Time in RFC Task 1383 ms
Max Number of RFCs per Hour 388
Avg RFC Response Time at Peak Hour 1370 ms
Hardware Capacity Max CPU Utilization on DB Server 37
Database Performance Avg DB Request Time in Dialog Task 268 ms
Confidential Service Summary 539
SAPreg GoingLivetrade Check - Verification Session 06082015
Area Indicators Value Trend
Avg DB Request Time for RFC 158 ms
Avg DB Request Time in Update Task 239 ms
Database Space Management DB Size 137091 GB
DB Growth Last Month 0 GB
Confidential Service Summary 639
SAPreg GoingLivetrade Check - Verification Session 06082015
3 Landscape
31 Products and Components in current Landscape
PRODUCT
SID SAP Product Product Version
PRD SAP ERP 60
MAIN INSTANCES (ABAP OR JAVA BASED)
SID Main Instance
PRD SAP ECC Server
DATABASES
SID Database System Database Version
PRD DB2 UDB for iSeries V5R4M0
32 Servers in current Landscape
SAP APPLICATION SERVERS
SID Host Instance Name Logical Host ABAP JAVA
PRD sap1r3p sap1r3p_PRD_00 SAP1R3P
DB SERVERS
SID Host Logical Host (SAPDBHOST)
PRD sap1r3p SAP1R3P
33 Hardware Configuration
HOST OVERVIEW
Host Operating System CPUs Memory in MB
sap1r3p OS400 54 0 0
Confidential Landscape 739
SAPreg GoingLivetrade Check - Verification Session 06082015
4 Software Configuration For PRD
We have listed important recommendations concerning the current software configuration on your system These recommendations should be implemented at the earliest opportunity
Your systems software versions are checked If known issues with the software versions installed are identified they are highlighted
41 SAP Application Release - Maintenance Phases
SAP Product Version End of Mainstream Maintenance Status
SAP ERP 60 31122025
In October 2014 SAP announced a maintenance extension for SAP Business Suite 7 core application releases to 2025 If you are running a relevant release see SAP Note httpsservicesapcomsapsupportnotes1648480[1648480] for more details and applicable restrictions
42 Support Package Maintenance - ABAP
The following table shows an overview of currently installed software components
SUPPORT PACKAGES
Software Component
Version Patch Level
Latest Avail Patch Level
Support Package Component Description
EA-APPL 600 8 27 SAPKGPAD08 SAP R3 Enterprise PLM SCM Finance
EA-DFPS 600 8 27 SAPKGPDD08 SAP R3 Enterprise Defense Forces amp Public Security
EA-FINSERV 600 8 28 SAPKGPFD08 SAP R3 Enterprise Financial Services
EA-GLTRADE 600 8 27 SAPKGPGD08 SAP R3 Enterprise Global Trade
EA-HR 600 15 123 SAPKGPHD15 SAP R3 Enterprise Human Resources
EA-IPPE 400 8 27 SAPKGPID08 SAP R3 Enterprise Integrated Product and Process Engineering
EA-PS 600 8 27 SAPKGPPD08 SAP R3 Enterprise Public Services
EA-RETAIL 600 8 27 SAPKGPRD08 SAP R3 Enterprise Retail
ECC-DIMP 600 8 27 SAPK-60008INECCDIMP ECC Discrete Industries Mill Products
ERECRUIT 600 8 27 SAPK-60008INERECRUIT SAP E-Recruiting
FI-CA 600 8 8 SAPK-60008INFICA FI-CA Contract Accounts Receivable and Payable (virtuell)
FI-CAX 600 8 27 SAPK-60008INFICAX FI-CAX Extended FI-CA
FINBASIS 600 8 27 SAPK-60008INFINBASIS SAP R3 Enterprise FINBASIS
INSURANCE 600 8 27 SAPK-60008ININSURANC INSURANCE SAP Insurance
IS-CWM 600 8 27 SAPK-60008INISCWM IS-CWM Catch Weight Management
IS-H 600 8 40 SAPK-60008INISH IS-Hospital
IS-M 600 8 27 SAPK-60008INISM IS Media
IS-OIL 600 8 27 SAPK-60008INISOIL IS-OIL SAP OIL amp GAS Upstream Downstream
IS-PS-CA 600 8 27 SAPK-60008INISPSCA IS-PS-CA TaxampRevenue Campus Management
Confidential Software Configuration For PRD 839
SAPreg GoingLivetrade Check - Verification Session 06082015
Software Component
Version Patch Level
Latest Avail Patch Level
Support Package Component Description
IS-UT 600 8 27 SAPK-60008INISUT IS-UT
LSOFE 600 8 27 SAPK-60008INLSOFE Learning Solution - Front End
PI_BASIS 2005_1_700 11 26 SAPKIPYJ7B SAP R3 Basis Plug-In
SAP_ABA 700 11 32 SAPKA70011 SAP Application Basis
SAP_AP 700 8 33 SAPKNA7008 SAP Application Platform
SAP_APPL 600 8 27 SAPKH60008 SAP R3 Standard
SAP_BASIS 700 11 32 SAPKB70011 SAP Basis Component
SAP_BW 700 12 34 SAPKW70012 SAP Business Information Warehouse
SAP_HR 600 15 123 SAPKE60015 SAP R3 Standard HR
SEM-BW 600 8 27 SAPKGS6008 SAP SEM Server
ST-API 01L_ECC600 0 SAP Service Tools for Applications Plug-In
ST-PI 2008_1_700 0 12 SAP Solution Tools Plug-In
43 SAP Kernel Release
Instance SAP Kernel Release Patch Level
sap1r3p 00 700 135
Instance(s) SAP Kernel Release Patch Level Age in Months OS Family
sap1r3p_PRD_00 700 135 94
431 Downward Compatible Kernel
You are running an SAP kernel version that has been outdated since Q32012 This kernel version was replaced by the downward-compatible kernel You can continue to use your current kernel version but if an issue occurs with your current kernel a fix will be provided for SAP kernel 721 only Recommendation To avoid the potential risks associated with running an outdated SAP kernel version you should replace this version with downward-compatible SAP kernel 721 The downward-compatible kernel is a special validated SAP kernel that improves the stability of your system Requirements and prerequisites to install the downward-compatible kernel are summarized below
SAP Note Number
What to Do Description
1222907 Implement SAP note or SP Runtime object with incorrect alignment
1610716 Implement SAP note or SP and execute report Correcting runtime objects with incorrect alignment
1716826 Information Usage of the downward compatible Kernel 721 (EXT)
1713986 Installation instructions Installation of Kernel 721 (EXT)
1744209 Information SAP Kernel 720 and 721 Versions and Kernel Patch Levels
For security reasons the programs rfcexec and startrfc are no longer shipped together with the 720 kernel If you run scenarios that require these programs we recommend that you download and install the corresponding files from the NW RFC SDK 720 For details refer to SAP Note 1581595
4311 Required Implementation in SAP_BASIS
You must implement the SAP Notes mentioned in this section before installing the downward-compatible kernel
Confidential Software Configuration For PRD 939
SAPreg GoingLivetrade Check - Verification Session 06082015
4312 Required Parameter Settings
As a prerequisite for running the downward-compatible kernel the following parameters need to be set
Parameter Description Current Value Recommendation
rslgnew_layout System Log Format 9
432 Issues with current SAP Kernel
Your SAP kernel release may encounter serious problems
SAP tests all SAP kernels that are released However your patch level has been found to be unstable in certain cases and is therefore not recommended For more information see the release information for each SAP kernel patch on SAP Service Marketplace
For more information about issues concerning your current SAP kernel see the SAP Notes in the table below
Recommendation If the SAP kernel shipped with the latest Support Package stack of your product has the same issue as listed below install a more recent SAP kernel available in the Patches section of SAP Service Marketplace
SAP Note Short Text Risk
1132350 Incomplete update records
1150058 Incomplete update records
1223994 Composite SAP note Incomplete update records
433 Additional Remarks
SAP releases Support Package stacks (including SAP kernel patches) on a regular basis for most products (generally 2ndash4 times a year) We recommend that you base your software maintenance strategy on these stacks
You should only consider using a more recent SAP kernel patch than that shipped with the latest Support Package Stack for your product if specific errors occur
For more information see SAP Service Marketplace at httpssupportsapcomsoftwarepatchesstackshtml (SAP SupportPackage Stack information) and httpssupportsapcompatches (patchinformation)
Confidential Software Configuration For PRD 1039
SAPreg GoingLivetrade Check - Verification Session 06082015
5 Service Preparation and Data Quality of PRD
SAP ERP system PRD is not fully prepared for delivery of future remote services
Rating Check Performed
Service Data Quality
ST-PI and ST-API Plug-Ins
Service Preparation Check (RTCCTOOL)
Service Data Control Center
Hardware Utilization Data
In preparation for SAP services ensure that connections collectors and service tools are up to date These functionalities are explained in SAP Notes httpsservicesapcomsapsupportnotes91488[91488] and 1172939
51 Service Data Quality
For this service data of high importance is missing The service data is collected by the Service Data Control Center (SDCCN) or read from the Solution Managers BW or Configuration and Change Database (CCDB) This section comprehensively shows issues with the data quality and provides hints on how to resolve them
LEGEND FOR PRIORITY IN SERVICE DATA QUALITY
Prio Explanation Impact of Missing or Erroneous Data
Overall important data are missing Detecting a critical situation may fail Report cannot be rated green or yellow
Data for an important chapter are missing Some issues may not be detected Report cannot be rated green
Some important check could not be processed The report can be rated green nevertheless
Only checks of minor importance are affected
An optional check was skipped
511 Quality of Data in Service Data Control Center (SDCC)
QUALITY OF SERVICE DATA IN ST-PI
Prio Report Area affected Details and Related ST-PI Logical Function SAP Note
System Monitoring of Server (host) sap1r3p
During hardware data collection no SAPOSCOL was found It is either not running or not accessible ST-PI function EWA_GET_HARDWARE_INFO used in section Hardware Capacity
1309499
512 Quality of Service Data in Solution Manager Diagnostics - BW
Prio Report Area affected
Details and Related Infocube SAP Note
Workload of ABAP System PRD
Reading performance data from BW returned neither data nor an error code A timeout may have occurred Infocube 0CCMSMTPH used in section Workload Overview PRD
1332428
Confidential Service Preparation and Data Quality of PRD 1139
SAPreg GoingLivetrade Check - Verification Session 06082015
52 ST-PI and ST-API Plug-Ins
The table below shows the service plug-ins implemented and their releases and patch levels These recommendations are derived from report RTCCTOOL For more information about RTCCTOOL see SAP Note 309711
Rating Plug-In Release Patch Level Release Rec Patch Level Rec
ST-API 01L_ECC600 0 01R_700 1
ST-PI 2008_1_700 0 2008_1_700 11
Recommendation The Service Tools for Applications Plug-In (ST-API) is not up-to-date For more information see SAP Note 69455 The Solution Tools Plug-In (ST-PI) is not up-to-date For more information see SAP Note 539977
53 Service Preparation Check (RTCCTOOL)
Before we can ship any services the latest version of the SAP Service tools must be implemented in your system Report RTCCTOOL was last run on 06082015 During the check the tool detected issues for which a RED rating was set
Overall Status SAP Note Title Tool Status Manual Status
69455 [Note 69455] Addon ST-API 01R_700
69455 [Note 69455] ST-API 01R_700 Support Package 1
539977 [Note 539977] ST-PI 2008_1_700 Support Package 11
69455 [Note 69455] Proc after addon impl
539977 [Note 539977] Addon ST-PI 2008_1_700
539977 Note 1300023 for ST-PI
539977 Note 1312413 for ST-PI
539977 Note 1293657 for ST-PI
12103 [Note 12103] Collectors and TCOLL
207223 [Note 207223] EWAlert setup
Recommendation [Note 69455] Addon ST-API 01R_700 Servicetools for Applications Plug-In for NetWeaver 04s Basis 70x From httpsupportsapcomsupporttools- gtST-API-gtInstallationsampUpgrades download the installation ST-API 01R_700 Upload to tx SAINT and install as per note 69455 Then restart report RTCCTOOL and choose List-gtRefresh from SAPNet
[Note 69455] ST-API 01R_700 Support Package 1 Addon supportpackage level 1 for ST-API 01R_700 for NetWeaver 04s Basis 70x From httpsupportsapcomsupporttools- gtST-API-gtSupport packages-gtST-API 01R_700 download patches up to SAPKITAB7N For basis gt=700 use the Maintenance optimizer to release the download Upload from frontend to transaction SPAM define a queue and import
[Note 539977] ST-PI 2008_1_700 Support Package 11 Addon supportpackage level 11 for ST-PI 2008_1_700 for 700 [patches up to level 11 for Basis tools for services] Open httpsupportsapcomsupporttools- gtST-PI supportpk-gt ST-PI2008_1_700 Add patch SAPKITLRDL (and predecessors if not yet implemented) download basket Release basket via Maintenance optimizer Upload from frontend into transaction SPAM define a queue and import the queue
54 Performance DB (ST03 ST06)
Analysis of ST06 and history data indicate some problems with SAPOSCOL Check SAPOSCOL and see SAP Note 1309499
Confidential Service Preparation and Data Quality of PRD 1239
SAPreg GoingLivetrade Check - Verification Session 06082015
55 Hardware Utilization Data
Host Operating System Performance Data
sap1r3p OS not detected OK
Hardware capacity checks could not be run successfully due to missing data See SAP Note 1309499
Confidential Service Preparation and Data Quality of PRD 1339
SAPreg GoingLivetrade Check - Verification Session 06082015
6 Hardware Capacity
We have checked your system for potential CPU bottlenecks and found that the hardware is sufficient for the current workload
Note Hardware Capacity evaluation is based on hosts for which data is least partially available
61 Overview System PRD
General This analysis focuses on the workload during the peak working hours (9-11 13) and is based on the hourly averages collected by SAPOSCOL For information about the definition of peak working hours see SAP Note 1251291
CPU If the average CPU load exceeds 75 temporary CPU bottlenecks are likely to occur An average CPU load of more than 90 is a strong indicator of a CPU bottleneck
Memory If your hardware cannot handle the maximum memory consumption this causes a memory bottleneck in your SAP system that can impair performance The paging rating depends on the ratio of paging activity to physical memory A ratio exceeding 25 indicates high memory usage (if Java has been detected 0 ) and values above 50 (Java 10 ) demonstrate a main memory bottleneck
Server Max CPU load [] Date Rating RAM [MB]
sap1r3p 37 21072015 0
Note In case of virtualization or IaaS scenarios (eg IBM PowerVM VMware Amazon AWS ) it might be that for some hosts the CPU rating is yellow or red although the utilization value is quite low In this case the relevant host could not use maximum usable capacity due to a resource shortage within the virtualized infrastructure (eg IBM PowerVM Shared Pool CPU utilization)
Confidential Hardware Capacity 1439
SAPreg GoingLivetrade Check - Verification Session 06082015
7 Workload of System PRD
This chart displays the main task types and indicates how their workload is distributed in the system The table below lists the detailed KPIs
RESPONSE TIME COMPONENTS IN HOURS
Task Type Response Time Wait Time CPU Time DB Time GUI Time
DIALOG 55 00 20 20 07
BATCH 51 00 24 26 00
RFC 29 00 04 03 00
UPDATE 04 00 01 02 00
Others 02 00 00 00 00
71 Workload By Users
User activity is measured in the workload monitor Only users of at least medium activity are counted as active users
Users Low Activity Medium Activity High Activity Total Users
dialog steps per week 1 to 399 400 to 4799 4800 or more
measured in system 82 29 1 112
72 Workload Distribution PRD
The performance of your system was analyzed with respect to the workload distribution We did not detect any major problems that could affect the performance of your SAP system
721 Workload by Application Module
Confidential Workload of System PRD 1539
SAPreg GoingLivetrade Check - Verification Session 06082015
The following diagrams show how each application module contributes to the total system workload Two workload aspects are shown
- CPU time total CPU load on all servers in the system landscape
- Database time total database load generated by the application
All programs that are not classified in the SAP Application Hierarchy (transaction SE81) are summarized in the Un-Assigned category Customer programs industry solutions and third-party add-on developments fall into this category
722 DB Load Profile
Confidential Workload of System PRD 1639
SAPreg GoingLivetrade Check - Verification Session 06082015
The number of work processes creating database load in parallel is not significantly high
The following diagram shows the DB load caused by dialog RFC HTTP(S) and background tasks over different time frames The data provided in the diagram represents the average number of database processes occupied by each task type in the database during the specified time frames These statistics are calculated as a weekly average the average values over six working days with a unit of one hour Periods between 0000-0600 and 2100-2400 contain an average value per hour as these are not core business hours You can enable 24-hour monitoring by implementing SAP Note 17750 With 24-hour monitoring the time profile returns the workload of the system or application server on an hourly basis rather than returning an average value per hour for the periods 0000ndash0600 and 2100ndash2400 By comparing the load profiles for dialog and background activity you can get an overview of the volume of background activity during online working hours
Confidential Workload of System PRD 1739
SAPreg GoingLivetrade Check - Verification Session 06082015
8 Performance Overview PRD
The performance of your system was analyzed with respect to the average response times and total workload We did not detect any major problems that could affect the performance of your system
Rating Check
Performance Evaluation
The following table shows the average response times for various task types
AVERAGES OF RESPONSE TIME COMPONENTS IN MS
Task type Dialog Steps Response Time CPU Time Wait Time Load Time DB Time GUI Time
DIALOG 27390 7350 2584 56 60 2679 936
RFC 7535 13832 1702 33 53 1582 00
UPDATE 3114 4477 1392 12 97 2394 00
UPDATE2 2004 2029 665 12 41 878 00
BATCH 8357 21896 10330 07 105 11007 00
SPOOL 1221 5755 262 58 08 188 00
81 Performance Evaluation
The measured times are compared against reference times to provide a rating - If the number of dialog steps in an hour is less than 1000 this hour is not considered - If the total number of transaction steps is less than 20000 the rating for the task is not performed (indicated by a gray icon in the table) - RED if at least three time ranges are rated RED - YELLOW if two time ranges are rated RED or at least three time ranges are rated YELLOW
The table below shows that no problem is expected on the application or database servers
Task Steps Application Server Performance Database Server Performance
Dia 27389
Upd 3114
HTTP 0
HTTPS 0
The ratings in the table above are determined by comparisons against the reference table below If the dialog response times are very poor it will cause a RED rating for the entire check
Task Reference for Avg Response Time (ms) Yellow Rating
Reference for Avg Response Time (ms) Red Rating
Reference for Avg DB time (ms) Yellow Rating
Reference for Avg DB time (ms) Red Rating
Dia 1200 3600 600 1800
Upd 2400 3600 1200 1800
HTTP 1200 3600 600 1800
HTTPS 1200 3600 600 1800
Confidential Performance Overview PRD 1839
SAPreg GoingLivetrade Check - Verification Session 06082015
82 Transaction Profile Check
The following tables show the response times and the number of dialog steps for the transactions that cause the heaviest workload in your system
821 Transactions by Total Workload
The following tables list the activities with the highest contribution to the total workload
WORKLOAD BY TRANSACTION (DIALOG HTTP(S)WS-HTTP )
Transaction Type Dialog Steps Total Resp Time in
Avg Resp Time in ms
Avg CPU Time in ms
Avg DB Time in ms
Avg GUI Time in ms
VL71 DIA 83 61 297185 178782 263658 71
FBL5N DIA 2919 33 4626 1991 1330 242
VA01 DIA 2034 32 6258 2092 1164 1764
VA02 DIA 2183 29 5306 2194 1287 639
ZSDP0023 DIA 365 22 24427 2144 19871 2116
ZWMSCP01 DIA 130 21 65254 13125 10103 649
ME22 DIA 167 17 41818 22914 3250 07
VT01N DIA 235 15 25864 13412 1976 2443
SESSION_MANAGER DIA 1078 14 5202 663 844 2716
VKM1 DIA 478 12 9796 3358 3746 86
43 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
WORKLOAD BY TRANSACTION (BATCH)
Transaction Dialog Steps Total Resp Time in
Total Resp Time in s
Total CPU Time in s
Total DB Time in s
ZFIP0102 156 109 44040 25240 42295
ZFIP0115 260 97 39320 21180 23386
ZSD_CREATE_ORDER_BY_REF 125 75 30160 13100 7000
ZWMS_FILE_MANAGER2 784 37 14820 930 612
ZSDP0031 8 33 13260 6780 2783
ZFIP0105 390 16 6560 4350 383
ZFIP0106 78 15 6010 4140 5722
RSBTCRTE 2412 12 4820 1240 336
ZSDP0063 2 10 4050 2130 1318
(BATCH) 3197 09 3750 810 506
392 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
822 Transactions by DB Load
The following transaction profiles list the transactions that have the greatest share in the database load sorted by percentage of total database access times
DATABASE LOAD BY TRANSACTIONS (DIALOG HTTP(S) )
Confidential Performance Overview PRD 1939
SAPreg GoingLivetrade Check - Verification Session 06082015
Transaction Type Dialog Steps Total DB Time in Avg DB Time in ms
VL71 DIA 83 127 263658
ZSDP0023 DIA 365 42 19871
FBL5N DIA 2919 22 1330
VA02 DIA 2183 16 1287
ZVC2 DIA 1360 15 1953
ZMMP0008 DIA 64 14 37798
VA01 DIA 2034 14 1164
ZSDP0013 DIA 47 12 43947
VKM1 DIA 478 10 3746
ZWMSCP01 DIA 130 08 10103
91 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
DATABASE LOAD BY TRANSACTIONS (BATCH)
Transaction Dialog Steps Total DB Time in Total DB Time in s
ZFIP0102 156 245 42300
ZFIP0115 260 135 23390
ZSD_CREATE_ORDER_BY_REF 125 41 7000
ZFIP0106 78 33 5720
ZSDP0031 8 16 2780
RSDB4UPD 2 12 2070
ZFII0002 1 09 1580
ZSDP0063 2 08 1320
ZSD_GENERATE_INFO_CONDITIONS 7 08 1320
ZFIP0101 263 07 1290
502 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
83 RFC Load by Initiating Action
The load in task type RFC is shown In the workload monitor this information is shown as Load from External Systems The calling system can be an application server of the system itself or any external system using the RFC interface The Initial Action is the calling program initiating the RFC The total response time for each initial action is shown as an absolute value and as a percentage compared to the total RFC load considered in this table The average times (per dialog step) are shown in milliseconds [ms] Calls from external systems are shown if they account for at least 8h or 5 of the total RFC load Local calls are shown if they account for at least 24h or 20 of the total RFC load
LOAD OVERVIEW
Initial System Load [s] Load
Local system PRD 4450 9957
Sum of external systems 19 043
RFC load (sum of above) 4469 10000
Confidential Performance Overview PRD 2039
SAPreg GoingLivetrade Check - Verification Session 06082015
Initial System Load [s] Load
RFC load in Performance Overview 10422 23321
Load of all task types in Performance Overview 51694 115668
TOP 20 RFC CALLS FROM LOCAL SYSTEM - AVERAGE TIMES [MS]
Initial System
Initial Action Total Resp
Time in s
of RFC Load
Avg Response
Time
Avg CPU Time
Avg DB Time
Avg Roll Wait Time
PRD RK2A1000_POST 892 1996 13097 147 87 20
PRD VF01 491 1099 25854 8767 14305 23
PRD VA01 468 1047 8402 170 543 14
PRD SAPLARFC 256 574 10505 208 305 17
PRD CA_QUEUE_ENTRY_BCS============CP 226 505 4628 1068 1398 251
PRD VA02 178 399 6343 1215 1490 14
PRD VL71 136 304 8330 698 330 118
PRD SAP_COLLECTOR_FOR_PERFMONITOR 132 295 33749 13108 7127 188
PRD VL02N 127 284 11757 2595 7164 18
PRD VL10X 96 215 4341 553 433 10
PRD VKM1 70 157 3532 813 930 35
PRD ZSDP0049 55 124 61422 1167 1553 64
PRD STMS 52 116 18555 1911 2091 77
PRD ZP01_FROM_ZP05_944988 52 115 171827 3233 1053 03
PRD ZSDP0010 45 100 74582 31983 32785 10
PRD XD02 43 097 403 116 126 05
PRD FB1D 42 093 1999 406 1263 06
PRD FBL5N 41 091 8700 630 866 14
PRD ZP01_FROM_ZP05_942398 38 086 63795 1867 2482 65
PRD FBZ5 32 071 319430 400 510 00
Confidential Performance Overview PRD 2139
SAPreg GoingLivetrade Check - Verification Session 06082015
9 SAP System Operating PRD
The daily operation of your system was analyzed We detected some problems that may impair system operation and stability
91 Availability based on Collector Protocols
A value of 100 means that the collector was available all day Available in the context of this report means that at least one SAP instance was running If the SAP collector was not running correctly the values in the table and graphics may be incorrect To check these logs call transaction ST03N (expert mode) and choose Collector and Performance DB -gt Performance Monitor Collector -gt Log
This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR that runs every hour The job does NOT check availability it carries out only general system tasks such as collecting and aggregating SAP performance data for all serversinstances The log does not contain any direct information about availability it contains only information about the status of the hourly statistical data collection
As of SAP Basis 640 system availability information is available in the CCMS (Computing Center Management System) of an SAP System in Service Level Reporting of SAP Solution Manager
This function is provided by the relevant Solution Manager Support Packages as an advanced development For more information refer to SAP Note 944496 which also lists the prerequisites that must be fulfilled before implementation can take place
92 Update Errors
In a system running under normal conditions only a small number of update errors should occur To set the rating for this check the number of active users is also taken into consideration
We did not detect any problems
Confidential SAP System Operating PRD 2239
SAPreg GoingLivetrade Check - Verification Session 06082015
93 Table Reorganization
The largest tables andor rapidly growing tables of system PRDwere checked No standard SAP recommendations for the applicable data volume management were found
94 Program Errors (ABAP Dumps)
50 ABAP dumps have been recorded in your system in the period 30072015 to 05082015 ABAP dumps are generally deleted after 7 days by default To view the ABAP dumps in your system call transaction ST22 and choose Selection Then select a timeframe
Date Number of Dumps
30072015 19
31072015 15
01082015 0
02082015 1
03082015 4
04082015 5
05082015 6
Name of Runtime Error Dumps Server (eg) User (eg) Date (eg) Time (eg)
TIME_OUT 1 SAP1R3P_PRD_00 EMOROCHO 30072015 104804
CALL_FUNCTION_SINGLE_LOGIN_REJ 2 SAP1R3P_PRD_00 SAPSYS 30072015 170339
DYNPRO_FIELD_CONVERSION 6 SAP1R3P_PRD_00 LORTEGA 31072015 172039
DBIF_RSQL_INVALID_RSQL 5 SAP1R3P_PRD_00 PREDROBAN 02082015 060047
CALL_FUNCTION_SEND_ERROR 2 SAP1R3P_PRD_00 JPVEND 03082015 073533
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY 3 SAP1R3P_PRD_00 LORTEGA 04082015 123208
RAISE_EXCEPTION 14 SAP1R3P_PRD_00 KCASTRO 05082015 094209
CONVT_NO_NUMBER 1 SAP1R3P_PRD_00 KABARCA 05082015 143511
UNCAUGHT_EXCEPTION 1 SAP1R3P_PRD_00 CBANCHON 05082015 150325
TSV_TNEW_PAGE_ALLOC_FAILED 5 SAP1R3P_PRD_00 FLUCAS 05082015 190338
MESSAGE_TYPE_X 10 SAP1R3P_PRD_00 INTERFASES 05082015 210129
It is important that you monitor ABAP dumps using transaction ST22 on a regular basis If ABAP dumps occur you should determine the cause as soon as possible Based on our analysis we found several ABAP dumps that need your attention Evaluate and resolve the above dumps If you cannot find a solution send a customer message to SAP to request support
Confidential SAP System Operating PRD 2339
SAPreg GoingLivetrade Check - Verification Session 06082015
10 Security
Critical security issues were found in your system
See the information in the following sections
Rating Check
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
101 ABAP Stack of PRD
1011 System Recommendations (ABAP)
System Recommendations is not used at all
Recommendation SAP strongly recommends applying important security fixes as soon as possible The System Recommendations application provides a detailed recommendation regarding which SAP security notes (ABAP and non-ABAP) should be implemented based on the actual status of the system and the notes already implemented This is a mandatory prerequisite for setting up a strong security patch process For more information go to httpservicesapcomsysrec
1012 Default Passwords of Standard Users
Standard users have default passwords
Recommendation Run report RSUSR003 to check the usage of default passwords by standard users
Ensure that users SAP (must exist in all clients) SAPCPIC and EARLYWATCH have non-default passwords in all clients For more information see Protecting Standard Users either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
Make sure that the standard password for user TMSADM has been changed in client 000 and delete this user in any other client SAP Note httpsservicesapcomsapsupportnotes1414256[1414256] describes a support tool to change the password of user TMSADM in all systems of the transport domain SAP Note httpsservicesapcomsapsupportnotes1552894[1552894] shows how to update the report RSUSR003 to show the status of user TMSADM
1013 ABAP Password Policy
If password login is allowed for specific instances only the password policy is checked only for these instances
10131 Password Complexity
PARAMETER LOGINMIN_PASSWORD_LNG
Confidential Security 2439
SAPreg GoingLivetrade Check - Verification Session 06082015
Rating Instance Current Value(s) Recommended Value
sap1r3p_PRD_00 6 8
The current system settings allow a password length of fewer than 8 characters This allows weak passwords Attackers may successfully recover these passwords and gain unauthorized access to the system
Recommendation Assign a minimum value of 8 to the profile parameter loginmin_password_lng
In addition SAP provides options to enforce complex passwords Find the current settings of the corresponding profile parameters in the following table
Parameter Instance Current Value(s)
loginmin_password_digits sap1r3p_PRD_00 0
loginmin_password_letters sap1r3p_PRD_00 0
loginmin_password_lowercase sap1r3p_PRD_00 0
loginmin_password_uppercase sap1r3p_PRD_00 0
loginmin_password_specials sap1r3p_PRD_00 0
Recommendation Enforce a minimum of 3 independent character categories using the corresponding profile parameters For more information see SAP Note httpsservicesapcomsapsupportnotes862989[862989] and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
1014 Gateway and Message Server Security
10141 Kernel Patch Level
Rating Kernel Release Current Kernel Patch Level Minimal Required Kernel Patch Level
700 135 260
To enable certain gateway security functionality a minimum kernel patch level is required Your system does not currently meet this requirement
Recommendation Update the kernel of your system to the newest kernel patch level available Update to a kernel patch level equal to or higher than the minimum required kernel patch level specified above For more information see SAP Note 1298433
10142 Gateway Security
Gateway Security Properties
The parameter GWREG_NO_CONN_INFO controls the activation of certain security properties of the SAP gateway It is defined as a bit mask with one bit per property
SAP Note httpsservicesapcomsapsupportnotes1298433[1298433] ldquoBypassing security in reginfo amp secinfordquo is not activated in your system The bit mask value for bit 1 is not set
Recommendation Enable the missing property by adding the bitmask value to the current value of GWREG_NO_CONN_INFO For more information about GWREG_NO_CONN_INFO see SAP Note 1444282
Confidential Security 2539
SAPreg GoingLivetrade Check - Verification Session 06082015
1015 Users with Critical Authorizations
For more information about the following check results see SAP Note 863362
Recommendation Depending on your environment review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations You can use the User Information System (transaction SUIM) to check the results For each check you can review the roles or profiles that include the authorization objects listed in the corresponding section
10151 Users Authorized to Start all Reports
This authorization allows critical functions and reports that do not contain their own authorization checks to be executed The specified number of users for each client have the checked authorization
Client No of Users Having This Authorization No of Valid Users Rating
001 2 3
400 147 160
Authorization objects
Object 1 S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2 S_PROGRAM with P_ACTION=SUBMIT P_GROUP=
Confidential Security 2639
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
2 Service Summary
The SAP reg GoingLivetrade Check (Verification Session) has detected severe problems that may cause you to lose business
We recommend that you take corrective action immediately
This report provides the results of the SAP reg GoingLivetrade Check (Verification Session) that was conducted on your SAP ERPsystem PRD Note The numbers in the Performance Overview PRD and Workload of System PRD sections refer to the time interval between 27072015 and 02082015 There is at least one area with critical performance system stability or security issues
The alert overview below summarizes the most important issues to be addressed Take corrective actions in these areas as soon as possible
ALERTS DECISIVE FOR RED REPORT
With the SAP kernel of your ABAP system the stability or consistency is at risk
ALERT OVERVIEW
A large number of deleted records have been found on the system
We found more than 30 ABAP dumps in your system
Standard users have default password
Secure password policy is not sufficiently enforced
A high number of users has critical authorizations
Perform the following Guided Self Services
Guided Self Service FAQ SAP Note
Security Optimization Service 696478
For more information about Guided Self-Services see SAP Enterprise Support Academy Register for an Expert-Guided Implementation Session for the Guided Self-Service at SAP Enterprise Support Academy - Learning Studio - Calendar
CHECK OVERVIEW
Topic Rating Topic Subtopic Rating Subtopic
SAP System Configuration
Performance Overview
Performance Evaluation
Workload Distribution
Workload by Application Module
DB Load Profile
SAP System Operating
Availability based on Collector Protocols
Confidential Service Summary 439
SAPreg GoingLivetrade Check - Verification Session 06082015
Topic Rating Topic Subtopic Rating Subtopic
Program Errors (ABAP Dumps)
Update Errors
Table Reorganization
Hardware Capacity
IBM i Database Checks
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
Security
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
Software Change Management
Number of Changes
Note All recommendations provided in this report are based on our general experience We advise that you test our recommendations before using them in your production system
Note If you have any questions about the accuracy of the checks in this report or the correct configuration of the SAP Solution Manager SAP reg GoingLivetrade Check (Verification Session) service create a customer message on component SV-SMG-SER
Note If you require assistance in resolving any concerns about the performance of the system or if you require a technical analysis ofother aspects of your system as highlighted in this report create a customer message on component SV-BO For details of how to set the appropriate priority level see SAP Note 67739
Performance Indicators for PRD
The following table shows the relevant performance indicators in various system areas
Area Indicators Value Trend
System Performance Active Users (gt400 steps) 30
Avg Availability per Week 100
Avg Response Time in Dialog Task 735 ms
Max Dialog Steps per Hour 1554
Avg Response Time at Peak Dialog Hour 676 ms
Avg Response Time in RFC Task 1383 ms
Max Number of RFCs per Hour 388
Avg RFC Response Time at Peak Hour 1370 ms
Hardware Capacity Max CPU Utilization on DB Server 37
Database Performance Avg DB Request Time in Dialog Task 268 ms
Confidential Service Summary 539
SAPreg GoingLivetrade Check - Verification Session 06082015
Area Indicators Value Trend
Avg DB Request Time for RFC 158 ms
Avg DB Request Time in Update Task 239 ms
Database Space Management DB Size 137091 GB
DB Growth Last Month 0 GB
Confidential Service Summary 639
SAPreg GoingLivetrade Check - Verification Session 06082015
3 Landscape
31 Products and Components in current Landscape
PRODUCT
SID SAP Product Product Version
PRD SAP ERP 60
MAIN INSTANCES (ABAP OR JAVA BASED)
SID Main Instance
PRD SAP ECC Server
DATABASES
SID Database System Database Version
PRD DB2 UDB for iSeries V5R4M0
32 Servers in current Landscape
SAP APPLICATION SERVERS
SID Host Instance Name Logical Host ABAP JAVA
PRD sap1r3p sap1r3p_PRD_00 SAP1R3P
DB SERVERS
SID Host Logical Host (SAPDBHOST)
PRD sap1r3p SAP1R3P
33 Hardware Configuration
HOST OVERVIEW
Host Operating System CPUs Memory in MB
sap1r3p OS400 54 0 0
Confidential Landscape 739
SAPreg GoingLivetrade Check - Verification Session 06082015
4 Software Configuration For PRD
We have listed important recommendations concerning the current software configuration on your system These recommendations should be implemented at the earliest opportunity
Your systems software versions are checked If known issues with the software versions installed are identified they are highlighted
41 SAP Application Release - Maintenance Phases
SAP Product Version End of Mainstream Maintenance Status
SAP ERP 60 31122025
In October 2014 SAP announced a maintenance extension for SAP Business Suite 7 core application releases to 2025 If you are running a relevant release see SAP Note httpsservicesapcomsapsupportnotes1648480[1648480] for more details and applicable restrictions
42 Support Package Maintenance - ABAP
The following table shows an overview of currently installed software components
SUPPORT PACKAGES
Software Component
Version Patch Level
Latest Avail Patch Level
Support Package Component Description
EA-APPL 600 8 27 SAPKGPAD08 SAP R3 Enterprise PLM SCM Finance
EA-DFPS 600 8 27 SAPKGPDD08 SAP R3 Enterprise Defense Forces amp Public Security
EA-FINSERV 600 8 28 SAPKGPFD08 SAP R3 Enterprise Financial Services
EA-GLTRADE 600 8 27 SAPKGPGD08 SAP R3 Enterprise Global Trade
EA-HR 600 15 123 SAPKGPHD15 SAP R3 Enterprise Human Resources
EA-IPPE 400 8 27 SAPKGPID08 SAP R3 Enterprise Integrated Product and Process Engineering
EA-PS 600 8 27 SAPKGPPD08 SAP R3 Enterprise Public Services
EA-RETAIL 600 8 27 SAPKGPRD08 SAP R3 Enterprise Retail
ECC-DIMP 600 8 27 SAPK-60008INECCDIMP ECC Discrete Industries Mill Products
ERECRUIT 600 8 27 SAPK-60008INERECRUIT SAP E-Recruiting
FI-CA 600 8 8 SAPK-60008INFICA FI-CA Contract Accounts Receivable and Payable (virtuell)
FI-CAX 600 8 27 SAPK-60008INFICAX FI-CAX Extended FI-CA
FINBASIS 600 8 27 SAPK-60008INFINBASIS SAP R3 Enterprise FINBASIS
INSURANCE 600 8 27 SAPK-60008ININSURANC INSURANCE SAP Insurance
IS-CWM 600 8 27 SAPK-60008INISCWM IS-CWM Catch Weight Management
IS-H 600 8 40 SAPK-60008INISH IS-Hospital
IS-M 600 8 27 SAPK-60008INISM IS Media
IS-OIL 600 8 27 SAPK-60008INISOIL IS-OIL SAP OIL amp GAS Upstream Downstream
IS-PS-CA 600 8 27 SAPK-60008INISPSCA IS-PS-CA TaxampRevenue Campus Management
Confidential Software Configuration For PRD 839
SAPreg GoingLivetrade Check - Verification Session 06082015
Software Component
Version Patch Level
Latest Avail Patch Level
Support Package Component Description
IS-UT 600 8 27 SAPK-60008INISUT IS-UT
LSOFE 600 8 27 SAPK-60008INLSOFE Learning Solution - Front End
PI_BASIS 2005_1_700 11 26 SAPKIPYJ7B SAP R3 Basis Plug-In
SAP_ABA 700 11 32 SAPKA70011 SAP Application Basis
SAP_AP 700 8 33 SAPKNA7008 SAP Application Platform
SAP_APPL 600 8 27 SAPKH60008 SAP R3 Standard
SAP_BASIS 700 11 32 SAPKB70011 SAP Basis Component
SAP_BW 700 12 34 SAPKW70012 SAP Business Information Warehouse
SAP_HR 600 15 123 SAPKE60015 SAP R3 Standard HR
SEM-BW 600 8 27 SAPKGS6008 SAP SEM Server
ST-API 01L_ECC600 0 SAP Service Tools for Applications Plug-In
ST-PI 2008_1_700 0 12 SAP Solution Tools Plug-In
43 SAP Kernel Release
Instance SAP Kernel Release Patch Level
sap1r3p 00 700 135
Instance(s) SAP Kernel Release Patch Level Age in Months OS Family
sap1r3p_PRD_00 700 135 94
431 Downward Compatible Kernel
You are running an SAP kernel version that has been outdated since Q32012 This kernel version was replaced by the downward-compatible kernel You can continue to use your current kernel version but if an issue occurs with your current kernel a fix will be provided for SAP kernel 721 only Recommendation To avoid the potential risks associated with running an outdated SAP kernel version you should replace this version with downward-compatible SAP kernel 721 The downward-compatible kernel is a special validated SAP kernel that improves the stability of your system Requirements and prerequisites to install the downward-compatible kernel are summarized below
SAP Note Number
What to Do Description
1222907 Implement SAP note or SP Runtime object with incorrect alignment
1610716 Implement SAP note or SP and execute report Correcting runtime objects with incorrect alignment
1716826 Information Usage of the downward compatible Kernel 721 (EXT)
1713986 Installation instructions Installation of Kernel 721 (EXT)
1744209 Information SAP Kernel 720 and 721 Versions and Kernel Patch Levels
For security reasons the programs rfcexec and startrfc are no longer shipped together with the 720 kernel If you run scenarios that require these programs we recommend that you download and install the corresponding files from the NW RFC SDK 720 For details refer to SAP Note 1581595
4311 Required Implementation in SAP_BASIS
You must implement the SAP Notes mentioned in this section before installing the downward-compatible kernel
Confidential Software Configuration For PRD 939
SAPreg GoingLivetrade Check - Verification Session 06082015
4312 Required Parameter Settings
As a prerequisite for running the downward-compatible kernel the following parameters need to be set
Parameter Description Current Value Recommendation
rslgnew_layout System Log Format 9
432 Issues with current SAP Kernel
Your SAP kernel release may encounter serious problems
SAP tests all SAP kernels that are released However your patch level has been found to be unstable in certain cases and is therefore not recommended For more information see the release information for each SAP kernel patch on SAP Service Marketplace
For more information about issues concerning your current SAP kernel see the SAP Notes in the table below
Recommendation If the SAP kernel shipped with the latest Support Package stack of your product has the same issue as listed below install a more recent SAP kernel available in the Patches section of SAP Service Marketplace
SAP Note Short Text Risk
1132350 Incomplete update records
1150058 Incomplete update records
1223994 Composite SAP note Incomplete update records
433 Additional Remarks
SAP releases Support Package stacks (including SAP kernel patches) on a regular basis for most products (generally 2ndash4 times a year) We recommend that you base your software maintenance strategy on these stacks
You should only consider using a more recent SAP kernel patch than that shipped with the latest Support Package Stack for your product if specific errors occur
For more information see SAP Service Marketplace at httpssupportsapcomsoftwarepatchesstackshtml (SAP SupportPackage Stack information) and httpssupportsapcompatches (patchinformation)
Confidential Software Configuration For PRD 1039
SAPreg GoingLivetrade Check - Verification Session 06082015
5 Service Preparation and Data Quality of PRD
SAP ERP system PRD is not fully prepared for delivery of future remote services
Rating Check Performed
Service Data Quality
ST-PI and ST-API Plug-Ins
Service Preparation Check (RTCCTOOL)
Service Data Control Center
Hardware Utilization Data
In preparation for SAP services ensure that connections collectors and service tools are up to date These functionalities are explained in SAP Notes httpsservicesapcomsapsupportnotes91488[91488] and 1172939
51 Service Data Quality
For this service data of high importance is missing The service data is collected by the Service Data Control Center (SDCCN) or read from the Solution Managers BW or Configuration and Change Database (CCDB) This section comprehensively shows issues with the data quality and provides hints on how to resolve them
LEGEND FOR PRIORITY IN SERVICE DATA QUALITY
Prio Explanation Impact of Missing or Erroneous Data
Overall important data are missing Detecting a critical situation may fail Report cannot be rated green or yellow
Data for an important chapter are missing Some issues may not be detected Report cannot be rated green
Some important check could not be processed The report can be rated green nevertheless
Only checks of minor importance are affected
An optional check was skipped
511 Quality of Data in Service Data Control Center (SDCC)
QUALITY OF SERVICE DATA IN ST-PI
Prio Report Area affected Details and Related ST-PI Logical Function SAP Note
System Monitoring of Server (host) sap1r3p
During hardware data collection no SAPOSCOL was found It is either not running or not accessible ST-PI function EWA_GET_HARDWARE_INFO used in section Hardware Capacity
1309499
512 Quality of Service Data in Solution Manager Diagnostics - BW
Prio Report Area affected
Details and Related Infocube SAP Note
Workload of ABAP System PRD
Reading performance data from BW returned neither data nor an error code A timeout may have occurred Infocube 0CCMSMTPH used in section Workload Overview PRD
1332428
Confidential Service Preparation and Data Quality of PRD 1139
SAPreg GoingLivetrade Check - Verification Session 06082015
52 ST-PI and ST-API Plug-Ins
The table below shows the service plug-ins implemented and their releases and patch levels These recommendations are derived from report RTCCTOOL For more information about RTCCTOOL see SAP Note 309711
Rating Plug-In Release Patch Level Release Rec Patch Level Rec
ST-API 01L_ECC600 0 01R_700 1
ST-PI 2008_1_700 0 2008_1_700 11
Recommendation The Service Tools for Applications Plug-In (ST-API) is not up-to-date For more information see SAP Note 69455 The Solution Tools Plug-In (ST-PI) is not up-to-date For more information see SAP Note 539977
53 Service Preparation Check (RTCCTOOL)
Before we can ship any services the latest version of the SAP Service tools must be implemented in your system Report RTCCTOOL was last run on 06082015 During the check the tool detected issues for which a RED rating was set
Overall Status SAP Note Title Tool Status Manual Status
69455 [Note 69455] Addon ST-API 01R_700
69455 [Note 69455] ST-API 01R_700 Support Package 1
539977 [Note 539977] ST-PI 2008_1_700 Support Package 11
69455 [Note 69455] Proc after addon impl
539977 [Note 539977] Addon ST-PI 2008_1_700
539977 Note 1300023 for ST-PI
539977 Note 1312413 for ST-PI
539977 Note 1293657 for ST-PI
12103 [Note 12103] Collectors and TCOLL
207223 [Note 207223] EWAlert setup
Recommendation [Note 69455] Addon ST-API 01R_700 Servicetools for Applications Plug-In for NetWeaver 04s Basis 70x From httpsupportsapcomsupporttools- gtST-API-gtInstallationsampUpgrades download the installation ST-API 01R_700 Upload to tx SAINT and install as per note 69455 Then restart report RTCCTOOL and choose List-gtRefresh from SAPNet
[Note 69455] ST-API 01R_700 Support Package 1 Addon supportpackage level 1 for ST-API 01R_700 for NetWeaver 04s Basis 70x From httpsupportsapcomsupporttools- gtST-API-gtSupport packages-gtST-API 01R_700 download patches up to SAPKITAB7N For basis gt=700 use the Maintenance optimizer to release the download Upload from frontend to transaction SPAM define a queue and import
[Note 539977] ST-PI 2008_1_700 Support Package 11 Addon supportpackage level 11 for ST-PI 2008_1_700 for 700 [patches up to level 11 for Basis tools for services] Open httpsupportsapcomsupporttools- gtST-PI supportpk-gt ST-PI2008_1_700 Add patch SAPKITLRDL (and predecessors if not yet implemented) download basket Release basket via Maintenance optimizer Upload from frontend into transaction SPAM define a queue and import the queue
54 Performance DB (ST03 ST06)
Analysis of ST06 and history data indicate some problems with SAPOSCOL Check SAPOSCOL and see SAP Note 1309499
Confidential Service Preparation and Data Quality of PRD 1239
SAPreg GoingLivetrade Check - Verification Session 06082015
55 Hardware Utilization Data
Host Operating System Performance Data
sap1r3p OS not detected OK
Hardware capacity checks could not be run successfully due to missing data See SAP Note 1309499
Confidential Service Preparation and Data Quality of PRD 1339
SAPreg GoingLivetrade Check - Verification Session 06082015
6 Hardware Capacity
We have checked your system for potential CPU bottlenecks and found that the hardware is sufficient for the current workload
Note Hardware Capacity evaluation is based on hosts for which data is least partially available
61 Overview System PRD
General This analysis focuses on the workload during the peak working hours (9-11 13) and is based on the hourly averages collected by SAPOSCOL For information about the definition of peak working hours see SAP Note 1251291
CPU If the average CPU load exceeds 75 temporary CPU bottlenecks are likely to occur An average CPU load of more than 90 is a strong indicator of a CPU bottleneck
Memory If your hardware cannot handle the maximum memory consumption this causes a memory bottleneck in your SAP system that can impair performance The paging rating depends on the ratio of paging activity to physical memory A ratio exceeding 25 indicates high memory usage (if Java has been detected 0 ) and values above 50 (Java 10 ) demonstrate a main memory bottleneck
Server Max CPU load [] Date Rating RAM [MB]
sap1r3p 37 21072015 0
Note In case of virtualization or IaaS scenarios (eg IBM PowerVM VMware Amazon AWS ) it might be that for some hosts the CPU rating is yellow or red although the utilization value is quite low In this case the relevant host could not use maximum usable capacity due to a resource shortage within the virtualized infrastructure (eg IBM PowerVM Shared Pool CPU utilization)
Confidential Hardware Capacity 1439
SAPreg GoingLivetrade Check - Verification Session 06082015
7 Workload of System PRD
This chart displays the main task types and indicates how their workload is distributed in the system The table below lists the detailed KPIs
RESPONSE TIME COMPONENTS IN HOURS
Task Type Response Time Wait Time CPU Time DB Time GUI Time
DIALOG 55 00 20 20 07
BATCH 51 00 24 26 00
RFC 29 00 04 03 00
UPDATE 04 00 01 02 00
Others 02 00 00 00 00
71 Workload By Users
User activity is measured in the workload monitor Only users of at least medium activity are counted as active users
Users Low Activity Medium Activity High Activity Total Users
dialog steps per week 1 to 399 400 to 4799 4800 or more
measured in system 82 29 1 112
72 Workload Distribution PRD
The performance of your system was analyzed with respect to the workload distribution We did not detect any major problems that could affect the performance of your SAP system
721 Workload by Application Module
Confidential Workload of System PRD 1539
SAPreg GoingLivetrade Check - Verification Session 06082015
The following diagrams show how each application module contributes to the total system workload Two workload aspects are shown
- CPU time total CPU load on all servers in the system landscape
- Database time total database load generated by the application
All programs that are not classified in the SAP Application Hierarchy (transaction SE81) are summarized in the Un-Assigned category Customer programs industry solutions and third-party add-on developments fall into this category
722 DB Load Profile
Confidential Workload of System PRD 1639
SAPreg GoingLivetrade Check - Verification Session 06082015
The number of work processes creating database load in parallel is not significantly high
The following diagram shows the DB load caused by dialog RFC HTTP(S) and background tasks over different time frames The data provided in the diagram represents the average number of database processes occupied by each task type in the database during the specified time frames These statistics are calculated as a weekly average the average values over six working days with a unit of one hour Periods between 0000-0600 and 2100-2400 contain an average value per hour as these are not core business hours You can enable 24-hour monitoring by implementing SAP Note 17750 With 24-hour monitoring the time profile returns the workload of the system or application server on an hourly basis rather than returning an average value per hour for the periods 0000ndash0600 and 2100ndash2400 By comparing the load profiles for dialog and background activity you can get an overview of the volume of background activity during online working hours
Confidential Workload of System PRD 1739
SAPreg GoingLivetrade Check - Verification Session 06082015
8 Performance Overview PRD
The performance of your system was analyzed with respect to the average response times and total workload We did not detect any major problems that could affect the performance of your system
Rating Check
Performance Evaluation
The following table shows the average response times for various task types
AVERAGES OF RESPONSE TIME COMPONENTS IN MS
Task type Dialog Steps Response Time CPU Time Wait Time Load Time DB Time GUI Time
DIALOG 27390 7350 2584 56 60 2679 936
RFC 7535 13832 1702 33 53 1582 00
UPDATE 3114 4477 1392 12 97 2394 00
UPDATE2 2004 2029 665 12 41 878 00
BATCH 8357 21896 10330 07 105 11007 00
SPOOL 1221 5755 262 58 08 188 00
81 Performance Evaluation
The measured times are compared against reference times to provide a rating - If the number of dialog steps in an hour is less than 1000 this hour is not considered - If the total number of transaction steps is less than 20000 the rating for the task is not performed (indicated by a gray icon in the table) - RED if at least three time ranges are rated RED - YELLOW if two time ranges are rated RED or at least three time ranges are rated YELLOW
The table below shows that no problem is expected on the application or database servers
Task Steps Application Server Performance Database Server Performance
Dia 27389
Upd 3114
HTTP 0
HTTPS 0
The ratings in the table above are determined by comparisons against the reference table below If the dialog response times are very poor it will cause a RED rating for the entire check
Task Reference for Avg Response Time (ms) Yellow Rating
Reference for Avg Response Time (ms) Red Rating
Reference for Avg DB time (ms) Yellow Rating
Reference for Avg DB time (ms) Red Rating
Dia 1200 3600 600 1800
Upd 2400 3600 1200 1800
HTTP 1200 3600 600 1800
HTTPS 1200 3600 600 1800
Confidential Performance Overview PRD 1839
SAPreg GoingLivetrade Check - Verification Session 06082015
82 Transaction Profile Check
The following tables show the response times and the number of dialog steps for the transactions that cause the heaviest workload in your system
821 Transactions by Total Workload
The following tables list the activities with the highest contribution to the total workload
WORKLOAD BY TRANSACTION (DIALOG HTTP(S)WS-HTTP )
Transaction Type Dialog Steps Total Resp Time in
Avg Resp Time in ms
Avg CPU Time in ms
Avg DB Time in ms
Avg GUI Time in ms
VL71 DIA 83 61 297185 178782 263658 71
FBL5N DIA 2919 33 4626 1991 1330 242
VA01 DIA 2034 32 6258 2092 1164 1764
VA02 DIA 2183 29 5306 2194 1287 639
ZSDP0023 DIA 365 22 24427 2144 19871 2116
ZWMSCP01 DIA 130 21 65254 13125 10103 649
ME22 DIA 167 17 41818 22914 3250 07
VT01N DIA 235 15 25864 13412 1976 2443
SESSION_MANAGER DIA 1078 14 5202 663 844 2716
VKM1 DIA 478 12 9796 3358 3746 86
43 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
WORKLOAD BY TRANSACTION (BATCH)
Transaction Dialog Steps Total Resp Time in
Total Resp Time in s
Total CPU Time in s
Total DB Time in s
ZFIP0102 156 109 44040 25240 42295
ZFIP0115 260 97 39320 21180 23386
ZSD_CREATE_ORDER_BY_REF 125 75 30160 13100 7000
ZWMS_FILE_MANAGER2 784 37 14820 930 612
ZSDP0031 8 33 13260 6780 2783
ZFIP0105 390 16 6560 4350 383
ZFIP0106 78 15 6010 4140 5722
RSBTCRTE 2412 12 4820 1240 336
ZSDP0063 2 10 4050 2130 1318
(BATCH) 3197 09 3750 810 506
392 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
822 Transactions by DB Load
The following transaction profiles list the transactions that have the greatest share in the database load sorted by percentage of total database access times
DATABASE LOAD BY TRANSACTIONS (DIALOG HTTP(S) )
Confidential Performance Overview PRD 1939
SAPreg GoingLivetrade Check - Verification Session 06082015
Transaction Type Dialog Steps Total DB Time in Avg DB Time in ms
VL71 DIA 83 127 263658
ZSDP0023 DIA 365 42 19871
FBL5N DIA 2919 22 1330
VA02 DIA 2183 16 1287
ZVC2 DIA 1360 15 1953
ZMMP0008 DIA 64 14 37798
VA01 DIA 2034 14 1164
ZSDP0013 DIA 47 12 43947
VKM1 DIA 478 10 3746
ZWMSCP01 DIA 130 08 10103
91 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
DATABASE LOAD BY TRANSACTIONS (BATCH)
Transaction Dialog Steps Total DB Time in Total DB Time in s
ZFIP0102 156 245 42300
ZFIP0115 260 135 23390
ZSD_CREATE_ORDER_BY_REF 125 41 7000
ZFIP0106 78 33 5720
ZSDP0031 8 16 2780
RSDB4UPD 2 12 2070
ZFII0002 1 09 1580
ZSDP0063 2 08 1320
ZSD_GENERATE_INFO_CONDITIONS 7 08 1320
ZFIP0101 263 07 1290
502 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
83 RFC Load by Initiating Action
The load in task type RFC is shown In the workload monitor this information is shown as Load from External Systems The calling system can be an application server of the system itself or any external system using the RFC interface The Initial Action is the calling program initiating the RFC The total response time for each initial action is shown as an absolute value and as a percentage compared to the total RFC load considered in this table The average times (per dialog step) are shown in milliseconds [ms] Calls from external systems are shown if they account for at least 8h or 5 of the total RFC load Local calls are shown if they account for at least 24h or 20 of the total RFC load
LOAD OVERVIEW
Initial System Load [s] Load
Local system PRD 4450 9957
Sum of external systems 19 043
RFC load (sum of above) 4469 10000
Confidential Performance Overview PRD 2039
SAPreg GoingLivetrade Check - Verification Session 06082015
Initial System Load [s] Load
RFC load in Performance Overview 10422 23321
Load of all task types in Performance Overview 51694 115668
TOP 20 RFC CALLS FROM LOCAL SYSTEM - AVERAGE TIMES [MS]
Initial System
Initial Action Total Resp
Time in s
of RFC Load
Avg Response
Time
Avg CPU Time
Avg DB Time
Avg Roll Wait Time
PRD RK2A1000_POST 892 1996 13097 147 87 20
PRD VF01 491 1099 25854 8767 14305 23
PRD VA01 468 1047 8402 170 543 14
PRD SAPLARFC 256 574 10505 208 305 17
PRD CA_QUEUE_ENTRY_BCS============CP 226 505 4628 1068 1398 251
PRD VA02 178 399 6343 1215 1490 14
PRD VL71 136 304 8330 698 330 118
PRD SAP_COLLECTOR_FOR_PERFMONITOR 132 295 33749 13108 7127 188
PRD VL02N 127 284 11757 2595 7164 18
PRD VL10X 96 215 4341 553 433 10
PRD VKM1 70 157 3532 813 930 35
PRD ZSDP0049 55 124 61422 1167 1553 64
PRD STMS 52 116 18555 1911 2091 77
PRD ZP01_FROM_ZP05_944988 52 115 171827 3233 1053 03
PRD ZSDP0010 45 100 74582 31983 32785 10
PRD XD02 43 097 403 116 126 05
PRD FB1D 42 093 1999 406 1263 06
PRD FBL5N 41 091 8700 630 866 14
PRD ZP01_FROM_ZP05_942398 38 086 63795 1867 2482 65
PRD FBZ5 32 071 319430 400 510 00
Confidential Performance Overview PRD 2139
SAPreg GoingLivetrade Check - Verification Session 06082015
9 SAP System Operating PRD
The daily operation of your system was analyzed We detected some problems that may impair system operation and stability
91 Availability based on Collector Protocols
A value of 100 means that the collector was available all day Available in the context of this report means that at least one SAP instance was running If the SAP collector was not running correctly the values in the table and graphics may be incorrect To check these logs call transaction ST03N (expert mode) and choose Collector and Performance DB -gt Performance Monitor Collector -gt Log
This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR that runs every hour The job does NOT check availability it carries out only general system tasks such as collecting and aggregating SAP performance data for all serversinstances The log does not contain any direct information about availability it contains only information about the status of the hourly statistical data collection
As of SAP Basis 640 system availability information is available in the CCMS (Computing Center Management System) of an SAP System in Service Level Reporting of SAP Solution Manager
This function is provided by the relevant Solution Manager Support Packages as an advanced development For more information refer to SAP Note 944496 which also lists the prerequisites that must be fulfilled before implementation can take place
92 Update Errors
In a system running under normal conditions only a small number of update errors should occur To set the rating for this check the number of active users is also taken into consideration
We did not detect any problems
Confidential SAP System Operating PRD 2239
SAPreg GoingLivetrade Check - Verification Session 06082015
93 Table Reorganization
The largest tables andor rapidly growing tables of system PRDwere checked No standard SAP recommendations for the applicable data volume management were found
94 Program Errors (ABAP Dumps)
50 ABAP dumps have been recorded in your system in the period 30072015 to 05082015 ABAP dumps are generally deleted after 7 days by default To view the ABAP dumps in your system call transaction ST22 and choose Selection Then select a timeframe
Date Number of Dumps
30072015 19
31072015 15
01082015 0
02082015 1
03082015 4
04082015 5
05082015 6
Name of Runtime Error Dumps Server (eg) User (eg) Date (eg) Time (eg)
TIME_OUT 1 SAP1R3P_PRD_00 EMOROCHO 30072015 104804
CALL_FUNCTION_SINGLE_LOGIN_REJ 2 SAP1R3P_PRD_00 SAPSYS 30072015 170339
DYNPRO_FIELD_CONVERSION 6 SAP1R3P_PRD_00 LORTEGA 31072015 172039
DBIF_RSQL_INVALID_RSQL 5 SAP1R3P_PRD_00 PREDROBAN 02082015 060047
CALL_FUNCTION_SEND_ERROR 2 SAP1R3P_PRD_00 JPVEND 03082015 073533
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY 3 SAP1R3P_PRD_00 LORTEGA 04082015 123208
RAISE_EXCEPTION 14 SAP1R3P_PRD_00 KCASTRO 05082015 094209
CONVT_NO_NUMBER 1 SAP1R3P_PRD_00 KABARCA 05082015 143511
UNCAUGHT_EXCEPTION 1 SAP1R3P_PRD_00 CBANCHON 05082015 150325
TSV_TNEW_PAGE_ALLOC_FAILED 5 SAP1R3P_PRD_00 FLUCAS 05082015 190338
MESSAGE_TYPE_X 10 SAP1R3P_PRD_00 INTERFASES 05082015 210129
It is important that you monitor ABAP dumps using transaction ST22 on a regular basis If ABAP dumps occur you should determine the cause as soon as possible Based on our analysis we found several ABAP dumps that need your attention Evaluate and resolve the above dumps If you cannot find a solution send a customer message to SAP to request support
Confidential SAP System Operating PRD 2339
SAPreg GoingLivetrade Check - Verification Session 06082015
10 Security
Critical security issues were found in your system
See the information in the following sections
Rating Check
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
101 ABAP Stack of PRD
1011 System Recommendations (ABAP)
System Recommendations is not used at all
Recommendation SAP strongly recommends applying important security fixes as soon as possible The System Recommendations application provides a detailed recommendation regarding which SAP security notes (ABAP and non-ABAP) should be implemented based on the actual status of the system and the notes already implemented This is a mandatory prerequisite for setting up a strong security patch process For more information go to httpservicesapcomsysrec
1012 Default Passwords of Standard Users
Standard users have default passwords
Recommendation Run report RSUSR003 to check the usage of default passwords by standard users
Ensure that users SAP (must exist in all clients) SAPCPIC and EARLYWATCH have non-default passwords in all clients For more information see Protecting Standard Users either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
Make sure that the standard password for user TMSADM has been changed in client 000 and delete this user in any other client SAP Note httpsservicesapcomsapsupportnotes1414256[1414256] describes a support tool to change the password of user TMSADM in all systems of the transport domain SAP Note httpsservicesapcomsapsupportnotes1552894[1552894] shows how to update the report RSUSR003 to show the status of user TMSADM
1013 ABAP Password Policy
If password login is allowed for specific instances only the password policy is checked only for these instances
10131 Password Complexity
PARAMETER LOGINMIN_PASSWORD_LNG
Confidential Security 2439
SAPreg GoingLivetrade Check - Verification Session 06082015
Rating Instance Current Value(s) Recommended Value
sap1r3p_PRD_00 6 8
The current system settings allow a password length of fewer than 8 characters This allows weak passwords Attackers may successfully recover these passwords and gain unauthorized access to the system
Recommendation Assign a minimum value of 8 to the profile parameter loginmin_password_lng
In addition SAP provides options to enforce complex passwords Find the current settings of the corresponding profile parameters in the following table
Parameter Instance Current Value(s)
loginmin_password_digits sap1r3p_PRD_00 0
loginmin_password_letters sap1r3p_PRD_00 0
loginmin_password_lowercase sap1r3p_PRD_00 0
loginmin_password_uppercase sap1r3p_PRD_00 0
loginmin_password_specials sap1r3p_PRD_00 0
Recommendation Enforce a minimum of 3 independent character categories using the corresponding profile parameters For more information see SAP Note httpsservicesapcomsapsupportnotes862989[862989] and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
1014 Gateway and Message Server Security
10141 Kernel Patch Level
Rating Kernel Release Current Kernel Patch Level Minimal Required Kernel Patch Level
700 135 260
To enable certain gateway security functionality a minimum kernel patch level is required Your system does not currently meet this requirement
Recommendation Update the kernel of your system to the newest kernel patch level available Update to a kernel patch level equal to or higher than the minimum required kernel patch level specified above For more information see SAP Note 1298433
10142 Gateway Security
Gateway Security Properties
The parameter GWREG_NO_CONN_INFO controls the activation of certain security properties of the SAP gateway It is defined as a bit mask with one bit per property
SAP Note httpsservicesapcomsapsupportnotes1298433[1298433] ldquoBypassing security in reginfo amp secinfordquo is not activated in your system The bit mask value for bit 1 is not set
Recommendation Enable the missing property by adding the bitmask value to the current value of GWREG_NO_CONN_INFO For more information about GWREG_NO_CONN_INFO see SAP Note 1444282
Confidential Security 2539
SAPreg GoingLivetrade Check - Verification Session 06082015
1015 Users with Critical Authorizations
For more information about the following check results see SAP Note 863362
Recommendation Depending on your environment review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations You can use the User Information System (transaction SUIM) to check the results For each check you can review the roles or profiles that include the authorization objects listed in the corresponding section
10151 Users Authorized to Start all Reports
This authorization allows critical functions and reports that do not contain their own authorization checks to be executed The specified number of users for each client have the checked authorization
Client No of Users Having This Authorization No of Valid Users Rating
001 2 3
400 147 160
Authorization objects
Object 1 S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2 S_PROGRAM with P_ACTION=SUBMIT P_GROUP=
Confidential Security 2639
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
Topic Rating Topic Subtopic Rating Subtopic
Program Errors (ABAP Dumps)
Update Errors
Table Reorganization
Hardware Capacity
IBM i Database Checks
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
Security
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
Software Change Management
Number of Changes
Note All recommendations provided in this report are based on our general experience We advise that you test our recommendations before using them in your production system
Note If you have any questions about the accuracy of the checks in this report or the correct configuration of the SAP Solution Manager SAP reg GoingLivetrade Check (Verification Session) service create a customer message on component SV-SMG-SER
Note If you require assistance in resolving any concerns about the performance of the system or if you require a technical analysis ofother aspects of your system as highlighted in this report create a customer message on component SV-BO For details of how to set the appropriate priority level see SAP Note 67739
Performance Indicators for PRD
The following table shows the relevant performance indicators in various system areas
Area Indicators Value Trend
System Performance Active Users (gt400 steps) 30
Avg Availability per Week 100
Avg Response Time in Dialog Task 735 ms
Max Dialog Steps per Hour 1554
Avg Response Time at Peak Dialog Hour 676 ms
Avg Response Time in RFC Task 1383 ms
Max Number of RFCs per Hour 388
Avg RFC Response Time at Peak Hour 1370 ms
Hardware Capacity Max CPU Utilization on DB Server 37
Database Performance Avg DB Request Time in Dialog Task 268 ms
Confidential Service Summary 539
SAPreg GoingLivetrade Check - Verification Session 06082015
Area Indicators Value Trend
Avg DB Request Time for RFC 158 ms
Avg DB Request Time in Update Task 239 ms
Database Space Management DB Size 137091 GB
DB Growth Last Month 0 GB
Confidential Service Summary 639
SAPreg GoingLivetrade Check - Verification Session 06082015
3 Landscape
31 Products and Components in current Landscape
PRODUCT
SID SAP Product Product Version
PRD SAP ERP 60
MAIN INSTANCES (ABAP OR JAVA BASED)
SID Main Instance
PRD SAP ECC Server
DATABASES
SID Database System Database Version
PRD DB2 UDB for iSeries V5R4M0
32 Servers in current Landscape
SAP APPLICATION SERVERS
SID Host Instance Name Logical Host ABAP JAVA
PRD sap1r3p sap1r3p_PRD_00 SAP1R3P
DB SERVERS
SID Host Logical Host (SAPDBHOST)
PRD sap1r3p SAP1R3P
33 Hardware Configuration
HOST OVERVIEW
Host Operating System CPUs Memory in MB
sap1r3p OS400 54 0 0
Confidential Landscape 739
SAPreg GoingLivetrade Check - Verification Session 06082015
4 Software Configuration For PRD
We have listed important recommendations concerning the current software configuration on your system These recommendations should be implemented at the earliest opportunity
Your systems software versions are checked If known issues with the software versions installed are identified they are highlighted
41 SAP Application Release - Maintenance Phases
SAP Product Version End of Mainstream Maintenance Status
SAP ERP 60 31122025
In October 2014 SAP announced a maintenance extension for SAP Business Suite 7 core application releases to 2025 If you are running a relevant release see SAP Note httpsservicesapcomsapsupportnotes1648480[1648480] for more details and applicable restrictions
42 Support Package Maintenance - ABAP
The following table shows an overview of currently installed software components
SUPPORT PACKAGES
Software Component
Version Patch Level
Latest Avail Patch Level
Support Package Component Description
EA-APPL 600 8 27 SAPKGPAD08 SAP R3 Enterprise PLM SCM Finance
EA-DFPS 600 8 27 SAPKGPDD08 SAP R3 Enterprise Defense Forces amp Public Security
EA-FINSERV 600 8 28 SAPKGPFD08 SAP R3 Enterprise Financial Services
EA-GLTRADE 600 8 27 SAPKGPGD08 SAP R3 Enterprise Global Trade
EA-HR 600 15 123 SAPKGPHD15 SAP R3 Enterprise Human Resources
EA-IPPE 400 8 27 SAPKGPID08 SAP R3 Enterprise Integrated Product and Process Engineering
EA-PS 600 8 27 SAPKGPPD08 SAP R3 Enterprise Public Services
EA-RETAIL 600 8 27 SAPKGPRD08 SAP R3 Enterprise Retail
ECC-DIMP 600 8 27 SAPK-60008INECCDIMP ECC Discrete Industries Mill Products
ERECRUIT 600 8 27 SAPK-60008INERECRUIT SAP E-Recruiting
FI-CA 600 8 8 SAPK-60008INFICA FI-CA Contract Accounts Receivable and Payable (virtuell)
FI-CAX 600 8 27 SAPK-60008INFICAX FI-CAX Extended FI-CA
FINBASIS 600 8 27 SAPK-60008INFINBASIS SAP R3 Enterprise FINBASIS
INSURANCE 600 8 27 SAPK-60008ININSURANC INSURANCE SAP Insurance
IS-CWM 600 8 27 SAPK-60008INISCWM IS-CWM Catch Weight Management
IS-H 600 8 40 SAPK-60008INISH IS-Hospital
IS-M 600 8 27 SAPK-60008INISM IS Media
IS-OIL 600 8 27 SAPK-60008INISOIL IS-OIL SAP OIL amp GAS Upstream Downstream
IS-PS-CA 600 8 27 SAPK-60008INISPSCA IS-PS-CA TaxampRevenue Campus Management
Confidential Software Configuration For PRD 839
SAPreg GoingLivetrade Check - Verification Session 06082015
Software Component
Version Patch Level
Latest Avail Patch Level
Support Package Component Description
IS-UT 600 8 27 SAPK-60008INISUT IS-UT
LSOFE 600 8 27 SAPK-60008INLSOFE Learning Solution - Front End
PI_BASIS 2005_1_700 11 26 SAPKIPYJ7B SAP R3 Basis Plug-In
SAP_ABA 700 11 32 SAPKA70011 SAP Application Basis
SAP_AP 700 8 33 SAPKNA7008 SAP Application Platform
SAP_APPL 600 8 27 SAPKH60008 SAP R3 Standard
SAP_BASIS 700 11 32 SAPKB70011 SAP Basis Component
SAP_BW 700 12 34 SAPKW70012 SAP Business Information Warehouse
SAP_HR 600 15 123 SAPKE60015 SAP R3 Standard HR
SEM-BW 600 8 27 SAPKGS6008 SAP SEM Server
ST-API 01L_ECC600 0 SAP Service Tools for Applications Plug-In
ST-PI 2008_1_700 0 12 SAP Solution Tools Plug-In
43 SAP Kernel Release
Instance SAP Kernel Release Patch Level
sap1r3p 00 700 135
Instance(s) SAP Kernel Release Patch Level Age in Months OS Family
sap1r3p_PRD_00 700 135 94
431 Downward Compatible Kernel
You are running an SAP kernel version that has been outdated since Q32012 This kernel version was replaced by the downward-compatible kernel You can continue to use your current kernel version but if an issue occurs with your current kernel a fix will be provided for SAP kernel 721 only Recommendation To avoid the potential risks associated with running an outdated SAP kernel version you should replace this version with downward-compatible SAP kernel 721 The downward-compatible kernel is a special validated SAP kernel that improves the stability of your system Requirements and prerequisites to install the downward-compatible kernel are summarized below
SAP Note Number
What to Do Description
1222907 Implement SAP note or SP Runtime object with incorrect alignment
1610716 Implement SAP note or SP and execute report Correcting runtime objects with incorrect alignment
1716826 Information Usage of the downward compatible Kernel 721 (EXT)
1713986 Installation instructions Installation of Kernel 721 (EXT)
1744209 Information SAP Kernel 720 and 721 Versions and Kernel Patch Levels
For security reasons the programs rfcexec and startrfc are no longer shipped together with the 720 kernel If you run scenarios that require these programs we recommend that you download and install the corresponding files from the NW RFC SDK 720 For details refer to SAP Note 1581595
4311 Required Implementation in SAP_BASIS
You must implement the SAP Notes mentioned in this section before installing the downward-compatible kernel
Confidential Software Configuration For PRD 939
SAPreg GoingLivetrade Check - Verification Session 06082015
4312 Required Parameter Settings
As a prerequisite for running the downward-compatible kernel the following parameters need to be set
Parameter Description Current Value Recommendation
rslgnew_layout System Log Format 9
432 Issues with current SAP Kernel
Your SAP kernel release may encounter serious problems
SAP tests all SAP kernels that are released However your patch level has been found to be unstable in certain cases and is therefore not recommended For more information see the release information for each SAP kernel patch on SAP Service Marketplace
For more information about issues concerning your current SAP kernel see the SAP Notes in the table below
Recommendation If the SAP kernel shipped with the latest Support Package stack of your product has the same issue as listed below install a more recent SAP kernel available in the Patches section of SAP Service Marketplace
SAP Note Short Text Risk
1132350 Incomplete update records
1150058 Incomplete update records
1223994 Composite SAP note Incomplete update records
433 Additional Remarks
SAP releases Support Package stacks (including SAP kernel patches) on a regular basis for most products (generally 2ndash4 times a year) We recommend that you base your software maintenance strategy on these stacks
You should only consider using a more recent SAP kernel patch than that shipped with the latest Support Package Stack for your product if specific errors occur
For more information see SAP Service Marketplace at httpssupportsapcomsoftwarepatchesstackshtml (SAP SupportPackage Stack information) and httpssupportsapcompatches (patchinformation)
Confidential Software Configuration For PRD 1039
SAPreg GoingLivetrade Check - Verification Session 06082015
5 Service Preparation and Data Quality of PRD
SAP ERP system PRD is not fully prepared for delivery of future remote services
Rating Check Performed
Service Data Quality
ST-PI and ST-API Plug-Ins
Service Preparation Check (RTCCTOOL)
Service Data Control Center
Hardware Utilization Data
In preparation for SAP services ensure that connections collectors and service tools are up to date These functionalities are explained in SAP Notes httpsservicesapcomsapsupportnotes91488[91488] and 1172939
51 Service Data Quality
For this service data of high importance is missing The service data is collected by the Service Data Control Center (SDCCN) or read from the Solution Managers BW or Configuration and Change Database (CCDB) This section comprehensively shows issues with the data quality and provides hints on how to resolve them
LEGEND FOR PRIORITY IN SERVICE DATA QUALITY
Prio Explanation Impact of Missing or Erroneous Data
Overall important data are missing Detecting a critical situation may fail Report cannot be rated green or yellow
Data for an important chapter are missing Some issues may not be detected Report cannot be rated green
Some important check could not be processed The report can be rated green nevertheless
Only checks of minor importance are affected
An optional check was skipped
511 Quality of Data in Service Data Control Center (SDCC)
QUALITY OF SERVICE DATA IN ST-PI
Prio Report Area affected Details and Related ST-PI Logical Function SAP Note
System Monitoring of Server (host) sap1r3p
During hardware data collection no SAPOSCOL was found It is either not running or not accessible ST-PI function EWA_GET_HARDWARE_INFO used in section Hardware Capacity
1309499
512 Quality of Service Data in Solution Manager Diagnostics - BW
Prio Report Area affected
Details and Related Infocube SAP Note
Workload of ABAP System PRD
Reading performance data from BW returned neither data nor an error code A timeout may have occurred Infocube 0CCMSMTPH used in section Workload Overview PRD
1332428
Confidential Service Preparation and Data Quality of PRD 1139
SAPreg GoingLivetrade Check - Verification Session 06082015
52 ST-PI and ST-API Plug-Ins
The table below shows the service plug-ins implemented and their releases and patch levels These recommendations are derived from report RTCCTOOL For more information about RTCCTOOL see SAP Note 309711
Rating Plug-In Release Patch Level Release Rec Patch Level Rec
ST-API 01L_ECC600 0 01R_700 1
ST-PI 2008_1_700 0 2008_1_700 11
Recommendation The Service Tools for Applications Plug-In (ST-API) is not up-to-date For more information see SAP Note 69455 The Solution Tools Plug-In (ST-PI) is not up-to-date For more information see SAP Note 539977
53 Service Preparation Check (RTCCTOOL)
Before we can ship any services the latest version of the SAP Service tools must be implemented in your system Report RTCCTOOL was last run on 06082015 During the check the tool detected issues for which a RED rating was set
Overall Status SAP Note Title Tool Status Manual Status
69455 [Note 69455] Addon ST-API 01R_700
69455 [Note 69455] ST-API 01R_700 Support Package 1
539977 [Note 539977] ST-PI 2008_1_700 Support Package 11
69455 [Note 69455] Proc after addon impl
539977 [Note 539977] Addon ST-PI 2008_1_700
539977 Note 1300023 for ST-PI
539977 Note 1312413 for ST-PI
539977 Note 1293657 for ST-PI
12103 [Note 12103] Collectors and TCOLL
207223 [Note 207223] EWAlert setup
Recommendation [Note 69455] Addon ST-API 01R_700 Servicetools for Applications Plug-In for NetWeaver 04s Basis 70x From httpsupportsapcomsupporttools- gtST-API-gtInstallationsampUpgrades download the installation ST-API 01R_700 Upload to tx SAINT and install as per note 69455 Then restart report RTCCTOOL and choose List-gtRefresh from SAPNet
[Note 69455] ST-API 01R_700 Support Package 1 Addon supportpackage level 1 for ST-API 01R_700 for NetWeaver 04s Basis 70x From httpsupportsapcomsupporttools- gtST-API-gtSupport packages-gtST-API 01R_700 download patches up to SAPKITAB7N For basis gt=700 use the Maintenance optimizer to release the download Upload from frontend to transaction SPAM define a queue and import
[Note 539977] ST-PI 2008_1_700 Support Package 11 Addon supportpackage level 11 for ST-PI 2008_1_700 for 700 [patches up to level 11 for Basis tools for services] Open httpsupportsapcomsupporttools- gtST-PI supportpk-gt ST-PI2008_1_700 Add patch SAPKITLRDL (and predecessors if not yet implemented) download basket Release basket via Maintenance optimizer Upload from frontend into transaction SPAM define a queue and import the queue
54 Performance DB (ST03 ST06)
Analysis of ST06 and history data indicate some problems with SAPOSCOL Check SAPOSCOL and see SAP Note 1309499
Confidential Service Preparation and Data Quality of PRD 1239
SAPreg GoingLivetrade Check - Verification Session 06082015
55 Hardware Utilization Data
Host Operating System Performance Data
sap1r3p OS not detected OK
Hardware capacity checks could not be run successfully due to missing data See SAP Note 1309499
Confidential Service Preparation and Data Quality of PRD 1339
SAPreg GoingLivetrade Check - Verification Session 06082015
6 Hardware Capacity
We have checked your system for potential CPU bottlenecks and found that the hardware is sufficient for the current workload
Note Hardware Capacity evaluation is based on hosts for which data is least partially available
61 Overview System PRD
General This analysis focuses on the workload during the peak working hours (9-11 13) and is based on the hourly averages collected by SAPOSCOL For information about the definition of peak working hours see SAP Note 1251291
CPU If the average CPU load exceeds 75 temporary CPU bottlenecks are likely to occur An average CPU load of more than 90 is a strong indicator of a CPU bottleneck
Memory If your hardware cannot handle the maximum memory consumption this causes a memory bottleneck in your SAP system that can impair performance The paging rating depends on the ratio of paging activity to physical memory A ratio exceeding 25 indicates high memory usage (if Java has been detected 0 ) and values above 50 (Java 10 ) demonstrate a main memory bottleneck
Server Max CPU load [] Date Rating RAM [MB]
sap1r3p 37 21072015 0
Note In case of virtualization or IaaS scenarios (eg IBM PowerVM VMware Amazon AWS ) it might be that for some hosts the CPU rating is yellow or red although the utilization value is quite low In this case the relevant host could not use maximum usable capacity due to a resource shortage within the virtualized infrastructure (eg IBM PowerVM Shared Pool CPU utilization)
Confidential Hardware Capacity 1439
SAPreg GoingLivetrade Check - Verification Session 06082015
7 Workload of System PRD
This chart displays the main task types and indicates how their workload is distributed in the system The table below lists the detailed KPIs
RESPONSE TIME COMPONENTS IN HOURS
Task Type Response Time Wait Time CPU Time DB Time GUI Time
DIALOG 55 00 20 20 07
BATCH 51 00 24 26 00
RFC 29 00 04 03 00
UPDATE 04 00 01 02 00
Others 02 00 00 00 00
71 Workload By Users
User activity is measured in the workload monitor Only users of at least medium activity are counted as active users
Users Low Activity Medium Activity High Activity Total Users
dialog steps per week 1 to 399 400 to 4799 4800 or more
measured in system 82 29 1 112
72 Workload Distribution PRD
The performance of your system was analyzed with respect to the workload distribution We did not detect any major problems that could affect the performance of your SAP system
721 Workload by Application Module
Confidential Workload of System PRD 1539
SAPreg GoingLivetrade Check - Verification Session 06082015
The following diagrams show how each application module contributes to the total system workload Two workload aspects are shown
- CPU time total CPU load on all servers in the system landscape
- Database time total database load generated by the application
All programs that are not classified in the SAP Application Hierarchy (transaction SE81) are summarized in the Un-Assigned category Customer programs industry solutions and third-party add-on developments fall into this category
722 DB Load Profile
Confidential Workload of System PRD 1639
SAPreg GoingLivetrade Check - Verification Session 06082015
The number of work processes creating database load in parallel is not significantly high
The following diagram shows the DB load caused by dialog RFC HTTP(S) and background tasks over different time frames The data provided in the diagram represents the average number of database processes occupied by each task type in the database during the specified time frames These statistics are calculated as a weekly average the average values over six working days with a unit of one hour Periods between 0000-0600 and 2100-2400 contain an average value per hour as these are not core business hours You can enable 24-hour monitoring by implementing SAP Note 17750 With 24-hour monitoring the time profile returns the workload of the system or application server on an hourly basis rather than returning an average value per hour for the periods 0000ndash0600 and 2100ndash2400 By comparing the load profiles for dialog and background activity you can get an overview of the volume of background activity during online working hours
Confidential Workload of System PRD 1739
SAPreg GoingLivetrade Check - Verification Session 06082015
8 Performance Overview PRD
The performance of your system was analyzed with respect to the average response times and total workload We did not detect any major problems that could affect the performance of your system
Rating Check
Performance Evaluation
The following table shows the average response times for various task types
AVERAGES OF RESPONSE TIME COMPONENTS IN MS
Task type Dialog Steps Response Time CPU Time Wait Time Load Time DB Time GUI Time
DIALOG 27390 7350 2584 56 60 2679 936
RFC 7535 13832 1702 33 53 1582 00
UPDATE 3114 4477 1392 12 97 2394 00
UPDATE2 2004 2029 665 12 41 878 00
BATCH 8357 21896 10330 07 105 11007 00
SPOOL 1221 5755 262 58 08 188 00
81 Performance Evaluation
The measured times are compared against reference times to provide a rating - If the number of dialog steps in an hour is less than 1000 this hour is not considered - If the total number of transaction steps is less than 20000 the rating for the task is not performed (indicated by a gray icon in the table) - RED if at least three time ranges are rated RED - YELLOW if two time ranges are rated RED or at least three time ranges are rated YELLOW
The table below shows that no problem is expected on the application or database servers
Task Steps Application Server Performance Database Server Performance
Dia 27389
Upd 3114
HTTP 0
HTTPS 0
The ratings in the table above are determined by comparisons against the reference table below If the dialog response times are very poor it will cause a RED rating for the entire check
Task Reference for Avg Response Time (ms) Yellow Rating
Reference for Avg Response Time (ms) Red Rating
Reference for Avg DB time (ms) Yellow Rating
Reference for Avg DB time (ms) Red Rating
Dia 1200 3600 600 1800
Upd 2400 3600 1200 1800
HTTP 1200 3600 600 1800
HTTPS 1200 3600 600 1800
Confidential Performance Overview PRD 1839
SAPreg GoingLivetrade Check - Verification Session 06082015
82 Transaction Profile Check
The following tables show the response times and the number of dialog steps for the transactions that cause the heaviest workload in your system
821 Transactions by Total Workload
The following tables list the activities with the highest contribution to the total workload
WORKLOAD BY TRANSACTION (DIALOG HTTP(S)WS-HTTP )
Transaction Type Dialog Steps Total Resp Time in
Avg Resp Time in ms
Avg CPU Time in ms
Avg DB Time in ms
Avg GUI Time in ms
VL71 DIA 83 61 297185 178782 263658 71
FBL5N DIA 2919 33 4626 1991 1330 242
VA01 DIA 2034 32 6258 2092 1164 1764
VA02 DIA 2183 29 5306 2194 1287 639
ZSDP0023 DIA 365 22 24427 2144 19871 2116
ZWMSCP01 DIA 130 21 65254 13125 10103 649
ME22 DIA 167 17 41818 22914 3250 07
VT01N DIA 235 15 25864 13412 1976 2443
SESSION_MANAGER DIA 1078 14 5202 663 844 2716
VKM1 DIA 478 12 9796 3358 3746 86
43 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
WORKLOAD BY TRANSACTION (BATCH)
Transaction Dialog Steps Total Resp Time in
Total Resp Time in s
Total CPU Time in s
Total DB Time in s
ZFIP0102 156 109 44040 25240 42295
ZFIP0115 260 97 39320 21180 23386
ZSD_CREATE_ORDER_BY_REF 125 75 30160 13100 7000
ZWMS_FILE_MANAGER2 784 37 14820 930 612
ZSDP0031 8 33 13260 6780 2783
ZFIP0105 390 16 6560 4350 383
ZFIP0106 78 15 6010 4140 5722
RSBTCRTE 2412 12 4820 1240 336
ZSDP0063 2 10 4050 2130 1318
(BATCH) 3197 09 3750 810 506
392 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
822 Transactions by DB Load
The following transaction profiles list the transactions that have the greatest share in the database load sorted by percentage of total database access times
DATABASE LOAD BY TRANSACTIONS (DIALOG HTTP(S) )
Confidential Performance Overview PRD 1939
SAPreg GoingLivetrade Check - Verification Session 06082015
Transaction Type Dialog Steps Total DB Time in Avg DB Time in ms
VL71 DIA 83 127 263658
ZSDP0023 DIA 365 42 19871
FBL5N DIA 2919 22 1330
VA02 DIA 2183 16 1287
ZVC2 DIA 1360 15 1953
ZMMP0008 DIA 64 14 37798
VA01 DIA 2034 14 1164
ZSDP0013 DIA 47 12 43947
VKM1 DIA 478 10 3746
ZWMSCP01 DIA 130 08 10103
91 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
DATABASE LOAD BY TRANSACTIONS (BATCH)
Transaction Dialog Steps Total DB Time in Total DB Time in s
ZFIP0102 156 245 42300
ZFIP0115 260 135 23390
ZSD_CREATE_ORDER_BY_REF 125 41 7000
ZFIP0106 78 33 5720
ZSDP0031 8 16 2780
RSDB4UPD 2 12 2070
ZFII0002 1 09 1580
ZSDP0063 2 08 1320
ZSD_GENERATE_INFO_CONDITIONS 7 08 1320
ZFIP0101 263 07 1290
502 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
83 RFC Load by Initiating Action
The load in task type RFC is shown In the workload monitor this information is shown as Load from External Systems The calling system can be an application server of the system itself or any external system using the RFC interface The Initial Action is the calling program initiating the RFC The total response time for each initial action is shown as an absolute value and as a percentage compared to the total RFC load considered in this table The average times (per dialog step) are shown in milliseconds [ms] Calls from external systems are shown if they account for at least 8h or 5 of the total RFC load Local calls are shown if they account for at least 24h or 20 of the total RFC load
LOAD OVERVIEW
Initial System Load [s] Load
Local system PRD 4450 9957
Sum of external systems 19 043
RFC load (sum of above) 4469 10000
Confidential Performance Overview PRD 2039
SAPreg GoingLivetrade Check - Verification Session 06082015
Initial System Load [s] Load
RFC load in Performance Overview 10422 23321
Load of all task types in Performance Overview 51694 115668
TOP 20 RFC CALLS FROM LOCAL SYSTEM - AVERAGE TIMES [MS]
Initial System
Initial Action Total Resp
Time in s
of RFC Load
Avg Response
Time
Avg CPU Time
Avg DB Time
Avg Roll Wait Time
PRD RK2A1000_POST 892 1996 13097 147 87 20
PRD VF01 491 1099 25854 8767 14305 23
PRD VA01 468 1047 8402 170 543 14
PRD SAPLARFC 256 574 10505 208 305 17
PRD CA_QUEUE_ENTRY_BCS============CP 226 505 4628 1068 1398 251
PRD VA02 178 399 6343 1215 1490 14
PRD VL71 136 304 8330 698 330 118
PRD SAP_COLLECTOR_FOR_PERFMONITOR 132 295 33749 13108 7127 188
PRD VL02N 127 284 11757 2595 7164 18
PRD VL10X 96 215 4341 553 433 10
PRD VKM1 70 157 3532 813 930 35
PRD ZSDP0049 55 124 61422 1167 1553 64
PRD STMS 52 116 18555 1911 2091 77
PRD ZP01_FROM_ZP05_944988 52 115 171827 3233 1053 03
PRD ZSDP0010 45 100 74582 31983 32785 10
PRD XD02 43 097 403 116 126 05
PRD FB1D 42 093 1999 406 1263 06
PRD FBL5N 41 091 8700 630 866 14
PRD ZP01_FROM_ZP05_942398 38 086 63795 1867 2482 65
PRD FBZ5 32 071 319430 400 510 00
Confidential Performance Overview PRD 2139
SAPreg GoingLivetrade Check - Verification Session 06082015
9 SAP System Operating PRD
The daily operation of your system was analyzed We detected some problems that may impair system operation and stability
91 Availability based on Collector Protocols
A value of 100 means that the collector was available all day Available in the context of this report means that at least one SAP instance was running If the SAP collector was not running correctly the values in the table and graphics may be incorrect To check these logs call transaction ST03N (expert mode) and choose Collector and Performance DB -gt Performance Monitor Collector -gt Log
This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR that runs every hour The job does NOT check availability it carries out only general system tasks such as collecting and aggregating SAP performance data for all serversinstances The log does not contain any direct information about availability it contains only information about the status of the hourly statistical data collection
As of SAP Basis 640 system availability information is available in the CCMS (Computing Center Management System) of an SAP System in Service Level Reporting of SAP Solution Manager
This function is provided by the relevant Solution Manager Support Packages as an advanced development For more information refer to SAP Note 944496 which also lists the prerequisites that must be fulfilled before implementation can take place
92 Update Errors
In a system running under normal conditions only a small number of update errors should occur To set the rating for this check the number of active users is also taken into consideration
We did not detect any problems
Confidential SAP System Operating PRD 2239
SAPreg GoingLivetrade Check - Verification Session 06082015
93 Table Reorganization
The largest tables andor rapidly growing tables of system PRDwere checked No standard SAP recommendations for the applicable data volume management were found
94 Program Errors (ABAP Dumps)
50 ABAP dumps have been recorded in your system in the period 30072015 to 05082015 ABAP dumps are generally deleted after 7 days by default To view the ABAP dumps in your system call transaction ST22 and choose Selection Then select a timeframe
Date Number of Dumps
30072015 19
31072015 15
01082015 0
02082015 1
03082015 4
04082015 5
05082015 6
Name of Runtime Error Dumps Server (eg) User (eg) Date (eg) Time (eg)
TIME_OUT 1 SAP1R3P_PRD_00 EMOROCHO 30072015 104804
CALL_FUNCTION_SINGLE_LOGIN_REJ 2 SAP1R3P_PRD_00 SAPSYS 30072015 170339
DYNPRO_FIELD_CONVERSION 6 SAP1R3P_PRD_00 LORTEGA 31072015 172039
DBIF_RSQL_INVALID_RSQL 5 SAP1R3P_PRD_00 PREDROBAN 02082015 060047
CALL_FUNCTION_SEND_ERROR 2 SAP1R3P_PRD_00 JPVEND 03082015 073533
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY 3 SAP1R3P_PRD_00 LORTEGA 04082015 123208
RAISE_EXCEPTION 14 SAP1R3P_PRD_00 KCASTRO 05082015 094209
CONVT_NO_NUMBER 1 SAP1R3P_PRD_00 KABARCA 05082015 143511
UNCAUGHT_EXCEPTION 1 SAP1R3P_PRD_00 CBANCHON 05082015 150325
TSV_TNEW_PAGE_ALLOC_FAILED 5 SAP1R3P_PRD_00 FLUCAS 05082015 190338
MESSAGE_TYPE_X 10 SAP1R3P_PRD_00 INTERFASES 05082015 210129
It is important that you monitor ABAP dumps using transaction ST22 on a regular basis If ABAP dumps occur you should determine the cause as soon as possible Based on our analysis we found several ABAP dumps that need your attention Evaluate and resolve the above dumps If you cannot find a solution send a customer message to SAP to request support
Confidential SAP System Operating PRD 2339
SAPreg GoingLivetrade Check - Verification Session 06082015
10 Security
Critical security issues were found in your system
See the information in the following sections
Rating Check
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
101 ABAP Stack of PRD
1011 System Recommendations (ABAP)
System Recommendations is not used at all
Recommendation SAP strongly recommends applying important security fixes as soon as possible The System Recommendations application provides a detailed recommendation regarding which SAP security notes (ABAP and non-ABAP) should be implemented based on the actual status of the system and the notes already implemented This is a mandatory prerequisite for setting up a strong security patch process For more information go to httpservicesapcomsysrec
1012 Default Passwords of Standard Users
Standard users have default passwords
Recommendation Run report RSUSR003 to check the usage of default passwords by standard users
Ensure that users SAP (must exist in all clients) SAPCPIC and EARLYWATCH have non-default passwords in all clients For more information see Protecting Standard Users either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
Make sure that the standard password for user TMSADM has been changed in client 000 and delete this user in any other client SAP Note httpsservicesapcomsapsupportnotes1414256[1414256] describes a support tool to change the password of user TMSADM in all systems of the transport domain SAP Note httpsservicesapcomsapsupportnotes1552894[1552894] shows how to update the report RSUSR003 to show the status of user TMSADM
1013 ABAP Password Policy
If password login is allowed for specific instances only the password policy is checked only for these instances
10131 Password Complexity
PARAMETER LOGINMIN_PASSWORD_LNG
Confidential Security 2439
SAPreg GoingLivetrade Check - Verification Session 06082015
Rating Instance Current Value(s) Recommended Value
sap1r3p_PRD_00 6 8
The current system settings allow a password length of fewer than 8 characters This allows weak passwords Attackers may successfully recover these passwords and gain unauthorized access to the system
Recommendation Assign a minimum value of 8 to the profile parameter loginmin_password_lng
In addition SAP provides options to enforce complex passwords Find the current settings of the corresponding profile parameters in the following table
Parameter Instance Current Value(s)
loginmin_password_digits sap1r3p_PRD_00 0
loginmin_password_letters sap1r3p_PRD_00 0
loginmin_password_lowercase sap1r3p_PRD_00 0
loginmin_password_uppercase sap1r3p_PRD_00 0
loginmin_password_specials sap1r3p_PRD_00 0
Recommendation Enforce a minimum of 3 independent character categories using the corresponding profile parameters For more information see SAP Note httpsservicesapcomsapsupportnotes862989[862989] and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
1014 Gateway and Message Server Security
10141 Kernel Patch Level
Rating Kernel Release Current Kernel Patch Level Minimal Required Kernel Patch Level
700 135 260
To enable certain gateway security functionality a minimum kernel patch level is required Your system does not currently meet this requirement
Recommendation Update the kernel of your system to the newest kernel patch level available Update to a kernel patch level equal to or higher than the minimum required kernel patch level specified above For more information see SAP Note 1298433
10142 Gateway Security
Gateway Security Properties
The parameter GWREG_NO_CONN_INFO controls the activation of certain security properties of the SAP gateway It is defined as a bit mask with one bit per property
SAP Note httpsservicesapcomsapsupportnotes1298433[1298433] ldquoBypassing security in reginfo amp secinfordquo is not activated in your system The bit mask value for bit 1 is not set
Recommendation Enable the missing property by adding the bitmask value to the current value of GWREG_NO_CONN_INFO For more information about GWREG_NO_CONN_INFO see SAP Note 1444282
Confidential Security 2539
SAPreg GoingLivetrade Check - Verification Session 06082015
1015 Users with Critical Authorizations
For more information about the following check results see SAP Note 863362
Recommendation Depending on your environment review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations You can use the User Information System (transaction SUIM) to check the results For each check you can review the roles or profiles that include the authorization objects listed in the corresponding section
10151 Users Authorized to Start all Reports
This authorization allows critical functions and reports that do not contain their own authorization checks to be executed The specified number of users for each client have the checked authorization
Client No of Users Having This Authorization No of Valid Users Rating
001 2 3
400 147 160
Authorization objects
Object 1 S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2 S_PROGRAM with P_ACTION=SUBMIT P_GROUP=
Confidential Security 2639
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
Area Indicators Value Trend
Avg DB Request Time for RFC 158 ms
Avg DB Request Time in Update Task 239 ms
Database Space Management DB Size 137091 GB
DB Growth Last Month 0 GB
Confidential Service Summary 639
SAPreg GoingLivetrade Check - Verification Session 06082015
3 Landscape
31 Products and Components in current Landscape
PRODUCT
SID SAP Product Product Version
PRD SAP ERP 60
MAIN INSTANCES (ABAP OR JAVA BASED)
SID Main Instance
PRD SAP ECC Server
DATABASES
SID Database System Database Version
PRD DB2 UDB for iSeries V5R4M0
32 Servers in current Landscape
SAP APPLICATION SERVERS
SID Host Instance Name Logical Host ABAP JAVA
PRD sap1r3p sap1r3p_PRD_00 SAP1R3P
DB SERVERS
SID Host Logical Host (SAPDBHOST)
PRD sap1r3p SAP1R3P
33 Hardware Configuration
HOST OVERVIEW
Host Operating System CPUs Memory in MB
sap1r3p OS400 54 0 0
Confidential Landscape 739
SAPreg GoingLivetrade Check - Verification Session 06082015
4 Software Configuration For PRD
We have listed important recommendations concerning the current software configuration on your system These recommendations should be implemented at the earliest opportunity
Your systems software versions are checked If known issues with the software versions installed are identified they are highlighted
41 SAP Application Release - Maintenance Phases
SAP Product Version End of Mainstream Maintenance Status
SAP ERP 60 31122025
In October 2014 SAP announced a maintenance extension for SAP Business Suite 7 core application releases to 2025 If you are running a relevant release see SAP Note httpsservicesapcomsapsupportnotes1648480[1648480] for more details and applicable restrictions
42 Support Package Maintenance - ABAP
The following table shows an overview of currently installed software components
SUPPORT PACKAGES
Software Component
Version Patch Level
Latest Avail Patch Level
Support Package Component Description
EA-APPL 600 8 27 SAPKGPAD08 SAP R3 Enterprise PLM SCM Finance
EA-DFPS 600 8 27 SAPKGPDD08 SAP R3 Enterprise Defense Forces amp Public Security
EA-FINSERV 600 8 28 SAPKGPFD08 SAP R3 Enterprise Financial Services
EA-GLTRADE 600 8 27 SAPKGPGD08 SAP R3 Enterprise Global Trade
EA-HR 600 15 123 SAPKGPHD15 SAP R3 Enterprise Human Resources
EA-IPPE 400 8 27 SAPKGPID08 SAP R3 Enterprise Integrated Product and Process Engineering
EA-PS 600 8 27 SAPKGPPD08 SAP R3 Enterprise Public Services
EA-RETAIL 600 8 27 SAPKGPRD08 SAP R3 Enterprise Retail
ECC-DIMP 600 8 27 SAPK-60008INECCDIMP ECC Discrete Industries Mill Products
ERECRUIT 600 8 27 SAPK-60008INERECRUIT SAP E-Recruiting
FI-CA 600 8 8 SAPK-60008INFICA FI-CA Contract Accounts Receivable and Payable (virtuell)
FI-CAX 600 8 27 SAPK-60008INFICAX FI-CAX Extended FI-CA
FINBASIS 600 8 27 SAPK-60008INFINBASIS SAP R3 Enterprise FINBASIS
INSURANCE 600 8 27 SAPK-60008ININSURANC INSURANCE SAP Insurance
IS-CWM 600 8 27 SAPK-60008INISCWM IS-CWM Catch Weight Management
IS-H 600 8 40 SAPK-60008INISH IS-Hospital
IS-M 600 8 27 SAPK-60008INISM IS Media
IS-OIL 600 8 27 SAPK-60008INISOIL IS-OIL SAP OIL amp GAS Upstream Downstream
IS-PS-CA 600 8 27 SAPK-60008INISPSCA IS-PS-CA TaxampRevenue Campus Management
Confidential Software Configuration For PRD 839
SAPreg GoingLivetrade Check - Verification Session 06082015
Software Component
Version Patch Level
Latest Avail Patch Level
Support Package Component Description
IS-UT 600 8 27 SAPK-60008INISUT IS-UT
LSOFE 600 8 27 SAPK-60008INLSOFE Learning Solution - Front End
PI_BASIS 2005_1_700 11 26 SAPKIPYJ7B SAP R3 Basis Plug-In
SAP_ABA 700 11 32 SAPKA70011 SAP Application Basis
SAP_AP 700 8 33 SAPKNA7008 SAP Application Platform
SAP_APPL 600 8 27 SAPKH60008 SAP R3 Standard
SAP_BASIS 700 11 32 SAPKB70011 SAP Basis Component
SAP_BW 700 12 34 SAPKW70012 SAP Business Information Warehouse
SAP_HR 600 15 123 SAPKE60015 SAP R3 Standard HR
SEM-BW 600 8 27 SAPKGS6008 SAP SEM Server
ST-API 01L_ECC600 0 SAP Service Tools for Applications Plug-In
ST-PI 2008_1_700 0 12 SAP Solution Tools Plug-In
43 SAP Kernel Release
Instance SAP Kernel Release Patch Level
sap1r3p 00 700 135
Instance(s) SAP Kernel Release Patch Level Age in Months OS Family
sap1r3p_PRD_00 700 135 94
431 Downward Compatible Kernel
You are running an SAP kernel version that has been outdated since Q32012 This kernel version was replaced by the downward-compatible kernel You can continue to use your current kernel version but if an issue occurs with your current kernel a fix will be provided for SAP kernel 721 only Recommendation To avoid the potential risks associated with running an outdated SAP kernel version you should replace this version with downward-compatible SAP kernel 721 The downward-compatible kernel is a special validated SAP kernel that improves the stability of your system Requirements and prerequisites to install the downward-compatible kernel are summarized below
SAP Note Number
What to Do Description
1222907 Implement SAP note or SP Runtime object with incorrect alignment
1610716 Implement SAP note or SP and execute report Correcting runtime objects with incorrect alignment
1716826 Information Usage of the downward compatible Kernel 721 (EXT)
1713986 Installation instructions Installation of Kernel 721 (EXT)
1744209 Information SAP Kernel 720 and 721 Versions and Kernel Patch Levels
For security reasons the programs rfcexec and startrfc are no longer shipped together with the 720 kernel If you run scenarios that require these programs we recommend that you download and install the corresponding files from the NW RFC SDK 720 For details refer to SAP Note 1581595
4311 Required Implementation in SAP_BASIS
You must implement the SAP Notes mentioned in this section before installing the downward-compatible kernel
Confidential Software Configuration For PRD 939
SAPreg GoingLivetrade Check - Verification Session 06082015
4312 Required Parameter Settings
As a prerequisite for running the downward-compatible kernel the following parameters need to be set
Parameter Description Current Value Recommendation
rslgnew_layout System Log Format 9
432 Issues with current SAP Kernel
Your SAP kernel release may encounter serious problems
SAP tests all SAP kernels that are released However your patch level has been found to be unstable in certain cases and is therefore not recommended For more information see the release information for each SAP kernel patch on SAP Service Marketplace
For more information about issues concerning your current SAP kernel see the SAP Notes in the table below
Recommendation If the SAP kernel shipped with the latest Support Package stack of your product has the same issue as listed below install a more recent SAP kernel available in the Patches section of SAP Service Marketplace
SAP Note Short Text Risk
1132350 Incomplete update records
1150058 Incomplete update records
1223994 Composite SAP note Incomplete update records
433 Additional Remarks
SAP releases Support Package stacks (including SAP kernel patches) on a regular basis for most products (generally 2ndash4 times a year) We recommend that you base your software maintenance strategy on these stacks
You should only consider using a more recent SAP kernel patch than that shipped with the latest Support Package Stack for your product if specific errors occur
For more information see SAP Service Marketplace at httpssupportsapcomsoftwarepatchesstackshtml (SAP SupportPackage Stack information) and httpssupportsapcompatches (patchinformation)
Confidential Software Configuration For PRD 1039
SAPreg GoingLivetrade Check - Verification Session 06082015
5 Service Preparation and Data Quality of PRD
SAP ERP system PRD is not fully prepared for delivery of future remote services
Rating Check Performed
Service Data Quality
ST-PI and ST-API Plug-Ins
Service Preparation Check (RTCCTOOL)
Service Data Control Center
Hardware Utilization Data
In preparation for SAP services ensure that connections collectors and service tools are up to date These functionalities are explained in SAP Notes httpsservicesapcomsapsupportnotes91488[91488] and 1172939
51 Service Data Quality
For this service data of high importance is missing The service data is collected by the Service Data Control Center (SDCCN) or read from the Solution Managers BW or Configuration and Change Database (CCDB) This section comprehensively shows issues with the data quality and provides hints on how to resolve them
LEGEND FOR PRIORITY IN SERVICE DATA QUALITY
Prio Explanation Impact of Missing or Erroneous Data
Overall important data are missing Detecting a critical situation may fail Report cannot be rated green or yellow
Data for an important chapter are missing Some issues may not be detected Report cannot be rated green
Some important check could not be processed The report can be rated green nevertheless
Only checks of minor importance are affected
An optional check was skipped
511 Quality of Data in Service Data Control Center (SDCC)
QUALITY OF SERVICE DATA IN ST-PI
Prio Report Area affected Details and Related ST-PI Logical Function SAP Note
System Monitoring of Server (host) sap1r3p
During hardware data collection no SAPOSCOL was found It is either not running or not accessible ST-PI function EWA_GET_HARDWARE_INFO used in section Hardware Capacity
1309499
512 Quality of Service Data in Solution Manager Diagnostics - BW
Prio Report Area affected
Details and Related Infocube SAP Note
Workload of ABAP System PRD
Reading performance data from BW returned neither data nor an error code A timeout may have occurred Infocube 0CCMSMTPH used in section Workload Overview PRD
1332428
Confidential Service Preparation and Data Quality of PRD 1139
SAPreg GoingLivetrade Check - Verification Session 06082015
52 ST-PI and ST-API Plug-Ins
The table below shows the service plug-ins implemented and their releases and patch levels These recommendations are derived from report RTCCTOOL For more information about RTCCTOOL see SAP Note 309711
Rating Plug-In Release Patch Level Release Rec Patch Level Rec
ST-API 01L_ECC600 0 01R_700 1
ST-PI 2008_1_700 0 2008_1_700 11
Recommendation The Service Tools for Applications Plug-In (ST-API) is not up-to-date For more information see SAP Note 69455 The Solution Tools Plug-In (ST-PI) is not up-to-date For more information see SAP Note 539977
53 Service Preparation Check (RTCCTOOL)
Before we can ship any services the latest version of the SAP Service tools must be implemented in your system Report RTCCTOOL was last run on 06082015 During the check the tool detected issues for which a RED rating was set
Overall Status SAP Note Title Tool Status Manual Status
69455 [Note 69455] Addon ST-API 01R_700
69455 [Note 69455] ST-API 01R_700 Support Package 1
539977 [Note 539977] ST-PI 2008_1_700 Support Package 11
69455 [Note 69455] Proc after addon impl
539977 [Note 539977] Addon ST-PI 2008_1_700
539977 Note 1300023 for ST-PI
539977 Note 1312413 for ST-PI
539977 Note 1293657 for ST-PI
12103 [Note 12103] Collectors and TCOLL
207223 [Note 207223] EWAlert setup
Recommendation [Note 69455] Addon ST-API 01R_700 Servicetools for Applications Plug-In for NetWeaver 04s Basis 70x From httpsupportsapcomsupporttools- gtST-API-gtInstallationsampUpgrades download the installation ST-API 01R_700 Upload to tx SAINT and install as per note 69455 Then restart report RTCCTOOL and choose List-gtRefresh from SAPNet
[Note 69455] ST-API 01R_700 Support Package 1 Addon supportpackage level 1 for ST-API 01R_700 for NetWeaver 04s Basis 70x From httpsupportsapcomsupporttools- gtST-API-gtSupport packages-gtST-API 01R_700 download patches up to SAPKITAB7N For basis gt=700 use the Maintenance optimizer to release the download Upload from frontend to transaction SPAM define a queue and import
[Note 539977] ST-PI 2008_1_700 Support Package 11 Addon supportpackage level 11 for ST-PI 2008_1_700 for 700 [patches up to level 11 for Basis tools for services] Open httpsupportsapcomsupporttools- gtST-PI supportpk-gt ST-PI2008_1_700 Add patch SAPKITLRDL (and predecessors if not yet implemented) download basket Release basket via Maintenance optimizer Upload from frontend into transaction SPAM define a queue and import the queue
54 Performance DB (ST03 ST06)
Analysis of ST06 and history data indicate some problems with SAPOSCOL Check SAPOSCOL and see SAP Note 1309499
Confidential Service Preparation and Data Quality of PRD 1239
SAPreg GoingLivetrade Check - Verification Session 06082015
55 Hardware Utilization Data
Host Operating System Performance Data
sap1r3p OS not detected OK
Hardware capacity checks could not be run successfully due to missing data See SAP Note 1309499
Confidential Service Preparation and Data Quality of PRD 1339
SAPreg GoingLivetrade Check - Verification Session 06082015
6 Hardware Capacity
We have checked your system for potential CPU bottlenecks and found that the hardware is sufficient for the current workload
Note Hardware Capacity evaluation is based on hosts for which data is least partially available
61 Overview System PRD
General This analysis focuses on the workload during the peak working hours (9-11 13) and is based on the hourly averages collected by SAPOSCOL For information about the definition of peak working hours see SAP Note 1251291
CPU If the average CPU load exceeds 75 temporary CPU bottlenecks are likely to occur An average CPU load of more than 90 is a strong indicator of a CPU bottleneck
Memory If your hardware cannot handle the maximum memory consumption this causes a memory bottleneck in your SAP system that can impair performance The paging rating depends on the ratio of paging activity to physical memory A ratio exceeding 25 indicates high memory usage (if Java has been detected 0 ) and values above 50 (Java 10 ) demonstrate a main memory bottleneck
Server Max CPU load [] Date Rating RAM [MB]
sap1r3p 37 21072015 0
Note In case of virtualization or IaaS scenarios (eg IBM PowerVM VMware Amazon AWS ) it might be that for some hosts the CPU rating is yellow or red although the utilization value is quite low In this case the relevant host could not use maximum usable capacity due to a resource shortage within the virtualized infrastructure (eg IBM PowerVM Shared Pool CPU utilization)
Confidential Hardware Capacity 1439
SAPreg GoingLivetrade Check - Verification Session 06082015
7 Workload of System PRD
This chart displays the main task types and indicates how their workload is distributed in the system The table below lists the detailed KPIs
RESPONSE TIME COMPONENTS IN HOURS
Task Type Response Time Wait Time CPU Time DB Time GUI Time
DIALOG 55 00 20 20 07
BATCH 51 00 24 26 00
RFC 29 00 04 03 00
UPDATE 04 00 01 02 00
Others 02 00 00 00 00
71 Workload By Users
User activity is measured in the workload monitor Only users of at least medium activity are counted as active users
Users Low Activity Medium Activity High Activity Total Users
dialog steps per week 1 to 399 400 to 4799 4800 or more
measured in system 82 29 1 112
72 Workload Distribution PRD
The performance of your system was analyzed with respect to the workload distribution We did not detect any major problems that could affect the performance of your SAP system
721 Workload by Application Module
Confidential Workload of System PRD 1539
SAPreg GoingLivetrade Check - Verification Session 06082015
The following diagrams show how each application module contributes to the total system workload Two workload aspects are shown
- CPU time total CPU load on all servers in the system landscape
- Database time total database load generated by the application
All programs that are not classified in the SAP Application Hierarchy (transaction SE81) are summarized in the Un-Assigned category Customer programs industry solutions and third-party add-on developments fall into this category
722 DB Load Profile
Confidential Workload of System PRD 1639
SAPreg GoingLivetrade Check - Verification Session 06082015
The number of work processes creating database load in parallel is not significantly high
The following diagram shows the DB load caused by dialog RFC HTTP(S) and background tasks over different time frames The data provided in the diagram represents the average number of database processes occupied by each task type in the database during the specified time frames These statistics are calculated as a weekly average the average values over six working days with a unit of one hour Periods between 0000-0600 and 2100-2400 contain an average value per hour as these are not core business hours You can enable 24-hour monitoring by implementing SAP Note 17750 With 24-hour monitoring the time profile returns the workload of the system or application server on an hourly basis rather than returning an average value per hour for the periods 0000ndash0600 and 2100ndash2400 By comparing the load profiles for dialog and background activity you can get an overview of the volume of background activity during online working hours
Confidential Workload of System PRD 1739
SAPreg GoingLivetrade Check - Verification Session 06082015
8 Performance Overview PRD
The performance of your system was analyzed with respect to the average response times and total workload We did not detect any major problems that could affect the performance of your system
Rating Check
Performance Evaluation
The following table shows the average response times for various task types
AVERAGES OF RESPONSE TIME COMPONENTS IN MS
Task type Dialog Steps Response Time CPU Time Wait Time Load Time DB Time GUI Time
DIALOG 27390 7350 2584 56 60 2679 936
RFC 7535 13832 1702 33 53 1582 00
UPDATE 3114 4477 1392 12 97 2394 00
UPDATE2 2004 2029 665 12 41 878 00
BATCH 8357 21896 10330 07 105 11007 00
SPOOL 1221 5755 262 58 08 188 00
81 Performance Evaluation
The measured times are compared against reference times to provide a rating - If the number of dialog steps in an hour is less than 1000 this hour is not considered - If the total number of transaction steps is less than 20000 the rating for the task is not performed (indicated by a gray icon in the table) - RED if at least three time ranges are rated RED - YELLOW if two time ranges are rated RED or at least three time ranges are rated YELLOW
The table below shows that no problem is expected on the application or database servers
Task Steps Application Server Performance Database Server Performance
Dia 27389
Upd 3114
HTTP 0
HTTPS 0
The ratings in the table above are determined by comparisons against the reference table below If the dialog response times are very poor it will cause a RED rating for the entire check
Task Reference for Avg Response Time (ms) Yellow Rating
Reference for Avg Response Time (ms) Red Rating
Reference for Avg DB time (ms) Yellow Rating
Reference for Avg DB time (ms) Red Rating
Dia 1200 3600 600 1800
Upd 2400 3600 1200 1800
HTTP 1200 3600 600 1800
HTTPS 1200 3600 600 1800
Confidential Performance Overview PRD 1839
SAPreg GoingLivetrade Check - Verification Session 06082015
82 Transaction Profile Check
The following tables show the response times and the number of dialog steps for the transactions that cause the heaviest workload in your system
821 Transactions by Total Workload
The following tables list the activities with the highest contribution to the total workload
WORKLOAD BY TRANSACTION (DIALOG HTTP(S)WS-HTTP )
Transaction Type Dialog Steps Total Resp Time in
Avg Resp Time in ms
Avg CPU Time in ms
Avg DB Time in ms
Avg GUI Time in ms
VL71 DIA 83 61 297185 178782 263658 71
FBL5N DIA 2919 33 4626 1991 1330 242
VA01 DIA 2034 32 6258 2092 1164 1764
VA02 DIA 2183 29 5306 2194 1287 639
ZSDP0023 DIA 365 22 24427 2144 19871 2116
ZWMSCP01 DIA 130 21 65254 13125 10103 649
ME22 DIA 167 17 41818 22914 3250 07
VT01N DIA 235 15 25864 13412 1976 2443
SESSION_MANAGER DIA 1078 14 5202 663 844 2716
VKM1 DIA 478 12 9796 3358 3746 86
43 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
WORKLOAD BY TRANSACTION (BATCH)
Transaction Dialog Steps Total Resp Time in
Total Resp Time in s
Total CPU Time in s
Total DB Time in s
ZFIP0102 156 109 44040 25240 42295
ZFIP0115 260 97 39320 21180 23386
ZSD_CREATE_ORDER_BY_REF 125 75 30160 13100 7000
ZWMS_FILE_MANAGER2 784 37 14820 930 612
ZSDP0031 8 33 13260 6780 2783
ZFIP0105 390 16 6560 4350 383
ZFIP0106 78 15 6010 4140 5722
RSBTCRTE 2412 12 4820 1240 336
ZSDP0063 2 10 4050 2130 1318
(BATCH) 3197 09 3750 810 506
392 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
822 Transactions by DB Load
The following transaction profiles list the transactions that have the greatest share in the database load sorted by percentage of total database access times
DATABASE LOAD BY TRANSACTIONS (DIALOG HTTP(S) )
Confidential Performance Overview PRD 1939
SAPreg GoingLivetrade Check - Verification Session 06082015
Transaction Type Dialog Steps Total DB Time in Avg DB Time in ms
VL71 DIA 83 127 263658
ZSDP0023 DIA 365 42 19871
FBL5N DIA 2919 22 1330
VA02 DIA 2183 16 1287
ZVC2 DIA 1360 15 1953
ZMMP0008 DIA 64 14 37798
VA01 DIA 2034 14 1164
ZSDP0013 DIA 47 12 43947
VKM1 DIA 478 10 3746
ZWMSCP01 DIA 130 08 10103
91 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
DATABASE LOAD BY TRANSACTIONS (BATCH)
Transaction Dialog Steps Total DB Time in Total DB Time in s
ZFIP0102 156 245 42300
ZFIP0115 260 135 23390
ZSD_CREATE_ORDER_BY_REF 125 41 7000
ZFIP0106 78 33 5720
ZSDP0031 8 16 2780
RSDB4UPD 2 12 2070
ZFII0002 1 09 1580
ZSDP0063 2 08 1320
ZSD_GENERATE_INFO_CONDITIONS 7 08 1320
ZFIP0101 263 07 1290
502 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
83 RFC Load by Initiating Action
The load in task type RFC is shown In the workload monitor this information is shown as Load from External Systems The calling system can be an application server of the system itself or any external system using the RFC interface The Initial Action is the calling program initiating the RFC The total response time for each initial action is shown as an absolute value and as a percentage compared to the total RFC load considered in this table The average times (per dialog step) are shown in milliseconds [ms] Calls from external systems are shown if they account for at least 8h or 5 of the total RFC load Local calls are shown if they account for at least 24h or 20 of the total RFC load
LOAD OVERVIEW
Initial System Load [s] Load
Local system PRD 4450 9957
Sum of external systems 19 043
RFC load (sum of above) 4469 10000
Confidential Performance Overview PRD 2039
SAPreg GoingLivetrade Check - Verification Session 06082015
Initial System Load [s] Load
RFC load in Performance Overview 10422 23321
Load of all task types in Performance Overview 51694 115668
TOP 20 RFC CALLS FROM LOCAL SYSTEM - AVERAGE TIMES [MS]
Initial System
Initial Action Total Resp
Time in s
of RFC Load
Avg Response
Time
Avg CPU Time
Avg DB Time
Avg Roll Wait Time
PRD RK2A1000_POST 892 1996 13097 147 87 20
PRD VF01 491 1099 25854 8767 14305 23
PRD VA01 468 1047 8402 170 543 14
PRD SAPLARFC 256 574 10505 208 305 17
PRD CA_QUEUE_ENTRY_BCS============CP 226 505 4628 1068 1398 251
PRD VA02 178 399 6343 1215 1490 14
PRD VL71 136 304 8330 698 330 118
PRD SAP_COLLECTOR_FOR_PERFMONITOR 132 295 33749 13108 7127 188
PRD VL02N 127 284 11757 2595 7164 18
PRD VL10X 96 215 4341 553 433 10
PRD VKM1 70 157 3532 813 930 35
PRD ZSDP0049 55 124 61422 1167 1553 64
PRD STMS 52 116 18555 1911 2091 77
PRD ZP01_FROM_ZP05_944988 52 115 171827 3233 1053 03
PRD ZSDP0010 45 100 74582 31983 32785 10
PRD XD02 43 097 403 116 126 05
PRD FB1D 42 093 1999 406 1263 06
PRD FBL5N 41 091 8700 630 866 14
PRD ZP01_FROM_ZP05_942398 38 086 63795 1867 2482 65
PRD FBZ5 32 071 319430 400 510 00
Confidential Performance Overview PRD 2139
SAPreg GoingLivetrade Check - Verification Session 06082015
9 SAP System Operating PRD
The daily operation of your system was analyzed We detected some problems that may impair system operation and stability
91 Availability based on Collector Protocols
A value of 100 means that the collector was available all day Available in the context of this report means that at least one SAP instance was running If the SAP collector was not running correctly the values in the table and graphics may be incorrect To check these logs call transaction ST03N (expert mode) and choose Collector and Performance DB -gt Performance Monitor Collector -gt Log
This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR that runs every hour The job does NOT check availability it carries out only general system tasks such as collecting and aggregating SAP performance data for all serversinstances The log does not contain any direct information about availability it contains only information about the status of the hourly statistical data collection
As of SAP Basis 640 system availability information is available in the CCMS (Computing Center Management System) of an SAP System in Service Level Reporting of SAP Solution Manager
This function is provided by the relevant Solution Manager Support Packages as an advanced development For more information refer to SAP Note 944496 which also lists the prerequisites that must be fulfilled before implementation can take place
92 Update Errors
In a system running under normal conditions only a small number of update errors should occur To set the rating for this check the number of active users is also taken into consideration
We did not detect any problems
Confidential SAP System Operating PRD 2239
SAPreg GoingLivetrade Check - Verification Session 06082015
93 Table Reorganization
The largest tables andor rapidly growing tables of system PRDwere checked No standard SAP recommendations for the applicable data volume management were found
94 Program Errors (ABAP Dumps)
50 ABAP dumps have been recorded in your system in the period 30072015 to 05082015 ABAP dumps are generally deleted after 7 days by default To view the ABAP dumps in your system call transaction ST22 and choose Selection Then select a timeframe
Date Number of Dumps
30072015 19
31072015 15
01082015 0
02082015 1
03082015 4
04082015 5
05082015 6
Name of Runtime Error Dumps Server (eg) User (eg) Date (eg) Time (eg)
TIME_OUT 1 SAP1R3P_PRD_00 EMOROCHO 30072015 104804
CALL_FUNCTION_SINGLE_LOGIN_REJ 2 SAP1R3P_PRD_00 SAPSYS 30072015 170339
DYNPRO_FIELD_CONVERSION 6 SAP1R3P_PRD_00 LORTEGA 31072015 172039
DBIF_RSQL_INVALID_RSQL 5 SAP1R3P_PRD_00 PREDROBAN 02082015 060047
CALL_FUNCTION_SEND_ERROR 2 SAP1R3P_PRD_00 JPVEND 03082015 073533
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY 3 SAP1R3P_PRD_00 LORTEGA 04082015 123208
RAISE_EXCEPTION 14 SAP1R3P_PRD_00 KCASTRO 05082015 094209
CONVT_NO_NUMBER 1 SAP1R3P_PRD_00 KABARCA 05082015 143511
UNCAUGHT_EXCEPTION 1 SAP1R3P_PRD_00 CBANCHON 05082015 150325
TSV_TNEW_PAGE_ALLOC_FAILED 5 SAP1R3P_PRD_00 FLUCAS 05082015 190338
MESSAGE_TYPE_X 10 SAP1R3P_PRD_00 INTERFASES 05082015 210129
It is important that you monitor ABAP dumps using transaction ST22 on a regular basis If ABAP dumps occur you should determine the cause as soon as possible Based on our analysis we found several ABAP dumps that need your attention Evaluate and resolve the above dumps If you cannot find a solution send a customer message to SAP to request support
Confidential SAP System Operating PRD 2339
SAPreg GoingLivetrade Check - Verification Session 06082015
10 Security
Critical security issues were found in your system
See the information in the following sections
Rating Check
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
101 ABAP Stack of PRD
1011 System Recommendations (ABAP)
System Recommendations is not used at all
Recommendation SAP strongly recommends applying important security fixes as soon as possible The System Recommendations application provides a detailed recommendation regarding which SAP security notes (ABAP and non-ABAP) should be implemented based on the actual status of the system and the notes already implemented This is a mandatory prerequisite for setting up a strong security patch process For more information go to httpservicesapcomsysrec
1012 Default Passwords of Standard Users
Standard users have default passwords
Recommendation Run report RSUSR003 to check the usage of default passwords by standard users
Ensure that users SAP (must exist in all clients) SAPCPIC and EARLYWATCH have non-default passwords in all clients For more information see Protecting Standard Users either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
Make sure that the standard password for user TMSADM has been changed in client 000 and delete this user in any other client SAP Note httpsservicesapcomsapsupportnotes1414256[1414256] describes a support tool to change the password of user TMSADM in all systems of the transport domain SAP Note httpsservicesapcomsapsupportnotes1552894[1552894] shows how to update the report RSUSR003 to show the status of user TMSADM
1013 ABAP Password Policy
If password login is allowed for specific instances only the password policy is checked only for these instances
10131 Password Complexity
PARAMETER LOGINMIN_PASSWORD_LNG
Confidential Security 2439
SAPreg GoingLivetrade Check - Verification Session 06082015
Rating Instance Current Value(s) Recommended Value
sap1r3p_PRD_00 6 8
The current system settings allow a password length of fewer than 8 characters This allows weak passwords Attackers may successfully recover these passwords and gain unauthorized access to the system
Recommendation Assign a minimum value of 8 to the profile parameter loginmin_password_lng
In addition SAP provides options to enforce complex passwords Find the current settings of the corresponding profile parameters in the following table
Parameter Instance Current Value(s)
loginmin_password_digits sap1r3p_PRD_00 0
loginmin_password_letters sap1r3p_PRD_00 0
loginmin_password_lowercase sap1r3p_PRD_00 0
loginmin_password_uppercase sap1r3p_PRD_00 0
loginmin_password_specials sap1r3p_PRD_00 0
Recommendation Enforce a minimum of 3 independent character categories using the corresponding profile parameters For more information see SAP Note httpsservicesapcomsapsupportnotes862989[862989] and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
1014 Gateway and Message Server Security
10141 Kernel Patch Level
Rating Kernel Release Current Kernel Patch Level Minimal Required Kernel Patch Level
700 135 260
To enable certain gateway security functionality a minimum kernel patch level is required Your system does not currently meet this requirement
Recommendation Update the kernel of your system to the newest kernel patch level available Update to a kernel patch level equal to or higher than the minimum required kernel patch level specified above For more information see SAP Note 1298433
10142 Gateway Security
Gateway Security Properties
The parameter GWREG_NO_CONN_INFO controls the activation of certain security properties of the SAP gateway It is defined as a bit mask with one bit per property
SAP Note httpsservicesapcomsapsupportnotes1298433[1298433] ldquoBypassing security in reginfo amp secinfordquo is not activated in your system The bit mask value for bit 1 is not set
Recommendation Enable the missing property by adding the bitmask value to the current value of GWREG_NO_CONN_INFO For more information about GWREG_NO_CONN_INFO see SAP Note 1444282
Confidential Security 2539
SAPreg GoingLivetrade Check - Verification Session 06082015
1015 Users with Critical Authorizations
For more information about the following check results see SAP Note 863362
Recommendation Depending on your environment review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations You can use the User Information System (transaction SUIM) to check the results For each check you can review the roles or profiles that include the authorization objects listed in the corresponding section
10151 Users Authorized to Start all Reports
This authorization allows critical functions and reports that do not contain their own authorization checks to be executed The specified number of users for each client have the checked authorization
Client No of Users Having This Authorization No of Valid Users Rating
001 2 3
400 147 160
Authorization objects
Object 1 S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2 S_PROGRAM with P_ACTION=SUBMIT P_GROUP=
Confidential Security 2639
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
3 Landscape
31 Products and Components in current Landscape
PRODUCT
SID SAP Product Product Version
PRD SAP ERP 60
MAIN INSTANCES (ABAP OR JAVA BASED)
SID Main Instance
PRD SAP ECC Server
DATABASES
SID Database System Database Version
PRD DB2 UDB for iSeries V5R4M0
32 Servers in current Landscape
SAP APPLICATION SERVERS
SID Host Instance Name Logical Host ABAP JAVA
PRD sap1r3p sap1r3p_PRD_00 SAP1R3P
DB SERVERS
SID Host Logical Host (SAPDBHOST)
PRD sap1r3p SAP1R3P
33 Hardware Configuration
HOST OVERVIEW
Host Operating System CPUs Memory in MB
sap1r3p OS400 54 0 0
Confidential Landscape 739
SAPreg GoingLivetrade Check - Verification Session 06082015
4 Software Configuration For PRD
We have listed important recommendations concerning the current software configuration on your system These recommendations should be implemented at the earliest opportunity
Your systems software versions are checked If known issues with the software versions installed are identified they are highlighted
41 SAP Application Release - Maintenance Phases
SAP Product Version End of Mainstream Maintenance Status
SAP ERP 60 31122025
In October 2014 SAP announced a maintenance extension for SAP Business Suite 7 core application releases to 2025 If you are running a relevant release see SAP Note httpsservicesapcomsapsupportnotes1648480[1648480] for more details and applicable restrictions
42 Support Package Maintenance - ABAP
The following table shows an overview of currently installed software components
SUPPORT PACKAGES
Software Component
Version Patch Level
Latest Avail Patch Level
Support Package Component Description
EA-APPL 600 8 27 SAPKGPAD08 SAP R3 Enterprise PLM SCM Finance
EA-DFPS 600 8 27 SAPKGPDD08 SAP R3 Enterprise Defense Forces amp Public Security
EA-FINSERV 600 8 28 SAPKGPFD08 SAP R3 Enterprise Financial Services
EA-GLTRADE 600 8 27 SAPKGPGD08 SAP R3 Enterprise Global Trade
EA-HR 600 15 123 SAPKGPHD15 SAP R3 Enterprise Human Resources
EA-IPPE 400 8 27 SAPKGPID08 SAP R3 Enterprise Integrated Product and Process Engineering
EA-PS 600 8 27 SAPKGPPD08 SAP R3 Enterprise Public Services
EA-RETAIL 600 8 27 SAPKGPRD08 SAP R3 Enterprise Retail
ECC-DIMP 600 8 27 SAPK-60008INECCDIMP ECC Discrete Industries Mill Products
ERECRUIT 600 8 27 SAPK-60008INERECRUIT SAP E-Recruiting
FI-CA 600 8 8 SAPK-60008INFICA FI-CA Contract Accounts Receivable and Payable (virtuell)
FI-CAX 600 8 27 SAPK-60008INFICAX FI-CAX Extended FI-CA
FINBASIS 600 8 27 SAPK-60008INFINBASIS SAP R3 Enterprise FINBASIS
INSURANCE 600 8 27 SAPK-60008ININSURANC INSURANCE SAP Insurance
IS-CWM 600 8 27 SAPK-60008INISCWM IS-CWM Catch Weight Management
IS-H 600 8 40 SAPK-60008INISH IS-Hospital
IS-M 600 8 27 SAPK-60008INISM IS Media
IS-OIL 600 8 27 SAPK-60008INISOIL IS-OIL SAP OIL amp GAS Upstream Downstream
IS-PS-CA 600 8 27 SAPK-60008INISPSCA IS-PS-CA TaxampRevenue Campus Management
Confidential Software Configuration For PRD 839
SAPreg GoingLivetrade Check - Verification Session 06082015
Software Component
Version Patch Level
Latest Avail Patch Level
Support Package Component Description
IS-UT 600 8 27 SAPK-60008INISUT IS-UT
LSOFE 600 8 27 SAPK-60008INLSOFE Learning Solution - Front End
PI_BASIS 2005_1_700 11 26 SAPKIPYJ7B SAP R3 Basis Plug-In
SAP_ABA 700 11 32 SAPKA70011 SAP Application Basis
SAP_AP 700 8 33 SAPKNA7008 SAP Application Platform
SAP_APPL 600 8 27 SAPKH60008 SAP R3 Standard
SAP_BASIS 700 11 32 SAPKB70011 SAP Basis Component
SAP_BW 700 12 34 SAPKW70012 SAP Business Information Warehouse
SAP_HR 600 15 123 SAPKE60015 SAP R3 Standard HR
SEM-BW 600 8 27 SAPKGS6008 SAP SEM Server
ST-API 01L_ECC600 0 SAP Service Tools for Applications Plug-In
ST-PI 2008_1_700 0 12 SAP Solution Tools Plug-In
43 SAP Kernel Release
Instance SAP Kernel Release Patch Level
sap1r3p 00 700 135
Instance(s) SAP Kernel Release Patch Level Age in Months OS Family
sap1r3p_PRD_00 700 135 94
431 Downward Compatible Kernel
You are running an SAP kernel version that has been outdated since Q32012 This kernel version was replaced by the downward-compatible kernel You can continue to use your current kernel version but if an issue occurs with your current kernel a fix will be provided for SAP kernel 721 only Recommendation To avoid the potential risks associated with running an outdated SAP kernel version you should replace this version with downward-compatible SAP kernel 721 The downward-compatible kernel is a special validated SAP kernel that improves the stability of your system Requirements and prerequisites to install the downward-compatible kernel are summarized below
SAP Note Number
What to Do Description
1222907 Implement SAP note or SP Runtime object with incorrect alignment
1610716 Implement SAP note or SP and execute report Correcting runtime objects with incorrect alignment
1716826 Information Usage of the downward compatible Kernel 721 (EXT)
1713986 Installation instructions Installation of Kernel 721 (EXT)
1744209 Information SAP Kernel 720 and 721 Versions and Kernel Patch Levels
For security reasons the programs rfcexec and startrfc are no longer shipped together with the 720 kernel If you run scenarios that require these programs we recommend that you download and install the corresponding files from the NW RFC SDK 720 For details refer to SAP Note 1581595
4311 Required Implementation in SAP_BASIS
You must implement the SAP Notes mentioned in this section before installing the downward-compatible kernel
Confidential Software Configuration For PRD 939
SAPreg GoingLivetrade Check - Verification Session 06082015
4312 Required Parameter Settings
As a prerequisite for running the downward-compatible kernel the following parameters need to be set
Parameter Description Current Value Recommendation
rslgnew_layout System Log Format 9
432 Issues with current SAP Kernel
Your SAP kernel release may encounter serious problems
SAP tests all SAP kernels that are released However your patch level has been found to be unstable in certain cases and is therefore not recommended For more information see the release information for each SAP kernel patch on SAP Service Marketplace
For more information about issues concerning your current SAP kernel see the SAP Notes in the table below
Recommendation If the SAP kernel shipped with the latest Support Package stack of your product has the same issue as listed below install a more recent SAP kernel available in the Patches section of SAP Service Marketplace
SAP Note Short Text Risk
1132350 Incomplete update records
1150058 Incomplete update records
1223994 Composite SAP note Incomplete update records
433 Additional Remarks
SAP releases Support Package stacks (including SAP kernel patches) on a regular basis for most products (generally 2ndash4 times a year) We recommend that you base your software maintenance strategy on these stacks
You should only consider using a more recent SAP kernel patch than that shipped with the latest Support Package Stack for your product if specific errors occur
For more information see SAP Service Marketplace at httpssupportsapcomsoftwarepatchesstackshtml (SAP SupportPackage Stack information) and httpssupportsapcompatches (patchinformation)
Confidential Software Configuration For PRD 1039
SAPreg GoingLivetrade Check - Verification Session 06082015
5 Service Preparation and Data Quality of PRD
SAP ERP system PRD is not fully prepared for delivery of future remote services
Rating Check Performed
Service Data Quality
ST-PI and ST-API Plug-Ins
Service Preparation Check (RTCCTOOL)
Service Data Control Center
Hardware Utilization Data
In preparation for SAP services ensure that connections collectors and service tools are up to date These functionalities are explained in SAP Notes httpsservicesapcomsapsupportnotes91488[91488] and 1172939
51 Service Data Quality
For this service data of high importance is missing The service data is collected by the Service Data Control Center (SDCCN) or read from the Solution Managers BW or Configuration and Change Database (CCDB) This section comprehensively shows issues with the data quality and provides hints on how to resolve them
LEGEND FOR PRIORITY IN SERVICE DATA QUALITY
Prio Explanation Impact of Missing or Erroneous Data
Overall important data are missing Detecting a critical situation may fail Report cannot be rated green or yellow
Data for an important chapter are missing Some issues may not be detected Report cannot be rated green
Some important check could not be processed The report can be rated green nevertheless
Only checks of minor importance are affected
An optional check was skipped
511 Quality of Data in Service Data Control Center (SDCC)
QUALITY OF SERVICE DATA IN ST-PI
Prio Report Area affected Details and Related ST-PI Logical Function SAP Note
System Monitoring of Server (host) sap1r3p
During hardware data collection no SAPOSCOL was found It is either not running or not accessible ST-PI function EWA_GET_HARDWARE_INFO used in section Hardware Capacity
1309499
512 Quality of Service Data in Solution Manager Diagnostics - BW
Prio Report Area affected
Details and Related Infocube SAP Note
Workload of ABAP System PRD
Reading performance data from BW returned neither data nor an error code A timeout may have occurred Infocube 0CCMSMTPH used in section Workload Overview PRD
1332428
Confidential Service Preparation and Data Quality of PRD 1139
SAPreg GoingLivetrade Check - Verification Session 06082015
52 ST-PI and ST-API Plug-Ins
The table below shows the service plug-ins implemented and their releases and patch levels These recommendations are derived from report RTCCTOOL For more information about RTCCTOOL see SAP Note 309711
Rating Plug-In Release Patch Level Release Rec Patch Level Rec
ST-API 01L_ECC600 0 01R_700 1
ST-PI 2008_1_700 0 2008_1_700 11
Recommendation The Service Tools for Applications Plug-In (ST-API) is not up-to-date For more information see SAP Note 69455 The Solution Tools Plug-In (ST-PI) is not up-to-date For more information see SAP Note 539977
53 Service Preparation Check (RTCCTOOL)
Before we can ship any services the latest version of the SAP Service tools must be implemented in your system Report RTCCTOOL was last run on 06082015 During the check the tool detected issues for which a RED rating was set
Overall Status SAP Note Title Tool Status Manual Status
69455 [Note 69455] Addon ST-API 01R_700
69455 [Note 69455] ST-API 01R_700 Support Package 1
539977 [Note 539977] ST-PI 2008_1_700 Support Package 11
69455 [Note 69455] Proc after addon impl
539977 [Note 539977] Addon ST-PI 2008_1_700
539977 Note 1300023 for ST-PI
539977 Note 1312413 for ST-PI
539977 Note 1293657 for ST-PI
12103 [Note 12103] Collectors and TCOLL
207223 [Note 207223] EWAlert setup
Recommendation [Note 69455] Addon ST-API 01R_700 Servicetools for Applications Plug-In for NetWeaver 04s Basis 70x From httpsupportsapcomsupporttools- gtST-API-gtInstallationsampUpgrades download the installation ST-API 01R_700 Upload to tx SAINT and install as per note 69455 Then restart report RTCCTOOL and choose List-gtRefresh from SAPNet
[Note 69455] ST-API 01R_700 Support Package 1 Addon supportpackage level 1 for ST-API 01R_700 for NetWeaver 04s Basis 70x From httpsupportsapcomsupporttools- gtST-API-gtSupport packages-gtST-API 01R_700 download patches up to SAPKITAB7N For basis gt=700 use the Maintenance optimizer to release the download Upload from frontend to transaction SPAM define a queue and import
[Note 539977] ST-PI 2008_1_700 Support Package 11 Addon supportpackage level 11 for ST-PI 2008_1_700 for 700 [patches up to level 11 for Basis tools for services] Open httpsupportsapcomsupporttools- gtST-PI supportpk-gt ST-PI2008_1_700 Add patch SAPKITLRDL (and predecessors if not yet implemented) download basket Release basket via Maintenance optimizer Upload from frontend into transaction SPAM define a queue and import the queue
54 Performance DB (ST03 ST06)
Analysis of ST06 and history data indicate some problems with SAPOSCOL Check SAPOSCOL and see SAP Note 1309499
Confidential Service Preparation and Data Quality of PRD 1239
SAPreg GoingLivetrade Check - Verification Session 06082015
55 Hardware Utilization Data
Host Operating System Performance Data
sap1r3p OS not detected OK
Hardware capacity checks could not be run successfully due to missing data See SAP Note 1309499
Confidential Service Preparation and Data Quality of PRD 1339
SAPreg GoingLivetrade Check - Verification Session 06082015
6 Hardware Capacity
We have checked your system for potential CPU bottlenecks and found that the hardware is sufficient for the current workload
Note Hardware Capacity evaluation is based on hosts for which data is least partially available
61 Overview System PRD
General This analysis focuses on the workload during the peak working hours (9-11 13) and is based on the hourly averages collected by SAPOSCOL For information about the definition of peak working hours see SAP Note 1251291
CPU If the average CPU load exceeds 75 temporary CPU bottlenecks are likely to occur An average CPU load of more than 90 is a strong indicator of a CPU bottleneck
Memory If your hardware cannot handle the maximum memory consumption this causes a memory bottleneck in your SAP system that can impair performance The paging rating depends on the ratio of paging activity to physical memory A ratio exceeding 25 indicates high memory usage (if Java has been detected 0 ) and values above 50 (Java 10 ) demonstrate a main memory bottleneck
Server Max CPU load [] Date Rating RAM [MB]
sap1r3p 37 21072015 0
Note In case of virtualization or IaaS scenarios (eg IBM PowerVM VMware Amazon AWS ) it might be that for some hosts the CPU rating is yellow or red although the utilization value is quite low In this case the relevant host could not use maximum usable capacity due to a resource shortage within the virtualized infrastructure (eg IBM PowerVM Shared Pool CPU utilization)
Confidential Hardware Capacity 1439
SAPreg GoingLivetrade Check - Verification Session 06082015
7 Workload of System PRD
This chart displays the main task types and indicates how their workload is distributed in the system The table below lists the detailed KPIs
RESPONSE TIME COMPONENTS IN HOURS
Task Type Response Time Wait Time CPU Time DB Time GUI Time
DIALOG 55 00 20 20 07
BATCH 51 00 24 26 00
RFC 29 00 04 03 00
UPDATE 04 00 01 02 00
Others 02 00 00 00 00
71 Workload By Users
User activity is measured in the workload monitor Only users of at least medium activity are counted as active users
Users Low Activity Medium Activity High Activity Total Users
dialog steps per week 1 to 399 400 to 4799 4800 or more
measured in system 82 29 1 112
72 Workload Distribution PRD
The performance of your system was analyzed with respect to the workload distribution We did not detect any major problems that could affect the performance of your SAP system
721 Workload by Application Module
Confidential Workload of System PRD 1539
SAPreg GoingLivetrade Check - Verification Session 06082015
The following diagrams show how each application module contributes to the total system workload Two workload aspects are shown
- CPU time total CPU load on all servers in the system landscape
- Database time total database load generated by the application
All programs that are not classified in the SAP Application Hierarchy (transaction SE81) are summarized in the Un-Assigned category Customer programs industry solutions and third-party add-on developments fall into this category
722 DB Load Profile
Confidential Workload of System PRD 1639
SAPreg GoingLivetrade Check - Verification Session 06082015
The number of work processes creating database load in parallel is not significantly high
The following diagram shows the DB load caused by dialog RFC HTTP(S) and background tasks over different time frames The data provided in the diagram represents the average number of database processes occupied by each task type in the database during the specified time frames These statistics are calculated as a weekly average the average values over six working days with a unit of one hour Periods between 0000-0600 and 2100-2400 contain an average value per hour as these are not core business hours You can enable 24-hour monitoring by implementing SAP Note 17750 With 24-hour monitoring the time profile returns the workload of the system or application server on an hourly basis rather than returning an average value per hour for the periods 0000ndash0600 and 2100ndash2400 By comparing the load profiles for dialog and background activity you can get an overview of the volume of background activity during online working hours
Confidential Workload of System PRD 1739
SAPreg GoingLivetrade Check - Verification Session 06082015
8 Performance Overview PRD
The performance of your system was analyzed with respect to the average response times and total workload We did not detect any major problems that could affect the performance of your system
Rating Check
Performance Evaluation
The following table shows the average response times for various task types
AVERAGES OF RESPONSE TIME COMPONENTS IN MS
Task type Dialog Steps Response Time CPU Time Wait Time Load Time DB Time GUI Time
DIALOG 27390 7350 2584 56 60 2679 936
RFC 7535 13832 1702 33 53 1582 00
UPDATE 3114 4477 1392 12 97 2394 00
UPDATE2 2004 2029 665 12 41 878 00
BATCH 8357 21896 10330 07 105 11007 00
SPOOL 1221 5755 262 58 08 188 00
81 Performance Evaluation
The measured times are compared against reference times to provide a rating - If the number of dialog steps in an hour is less than 1000 this hour is not considered - If the total number of transaction steps is less than 20000 the rating for the task is not performed (indicated by a gray icon in the table) - RED if at least three time ranges are rated RED - YELLOW if two time ranges are rated RED or at least three time ranges are rated YELLOW
The table below shows that no problem is expected on the application or database servers
Task Steps Application Server Performance Database Server Performance
Dia 27389
Upd 3114
HTTP 0
HTTPS 0
The ratings in the table above are determined by comparisons against the reference table below If the dialog response times are very poor it will cause a RED rating for the entire check
Task Reference for Avg Response Time (ms) Yellow Rating
Reference for Avg Response Time (ms) Red Rating
Reference for Avg DB time (ms) Yellow Rating
Reference for Avg DB time (ms) Red Rating
Dia 1200 3600 600 1800
Upd 2400 3600 1200 1800
HTTP 1200 3600 600 1800
HTTPS 1200 3600 600 1800
Confidential Performance Overview PRD 1839
SAPreg GoingLivetrade Check - Verification Session 06082015
82 Transaction Profile Check
The following tables show the response times and the number of dialog steps for the transactions that cause the heaviest workload in your system
821 Transactions by Total Workload
The following tables list the activities with the highest contribution to the total workload
WORKLOAD BY TRANSACTION (DIALOG HTTP(S)WS-HTTP )
Transaction Type Dialog Steps Total Resp Time in
Avg Resp Time in ms
Avg CPU Time in ms
Avg DB Time in ms
Avg GUI Time in ms
VL71 DIA 83 61 297185 178782 263658 71
FBL5N DIA 2919 33 4626 1991 1330 242
VA01 DIA 2034 32 6258 2092 1164 1764
VA02 DIA 2183 29 5306 2194 1287 639
ZSDP0023 DIA 365 22 24427 2144 19871 2116
ZWMSCP01 DIA 130 21 65254 13125 10103 649
ME22 DIA 167 17 41818 22914 3250 07
VT01N DIA 235 15 25864 13412 1976 2443
SESSION_MANAGER DIA 1078 14 5202 663 844 2716
VKM1 DIA 478 12 9796 3358 3746 86
43 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
WORKLOAD BY TRANSACTION (BATCH)
Transaction Dialog Steps Total Resp Time in
Total Resp Time in s
Total CPU Time in s
Total DB Time in s
ZFIP0102 156 109 44040 25240 42295
ZFIP0115 260 97 39320 21180 23386
ZSD_CREATE_ORDER_BY_REF 125 75 30160 13100 7000
ZWMS_FILE_MANAGER2 784 37 14820 930 612
ZSDP0031 8 33 13260 6780 2783
ZFIP0105 390 16 6560 4350 383
ZFIP0106 78 15 6010 4140 5722
RSBTCRTE 2412 12 4820 1240 336
ZSDP0063 2 10 4050 2130 1318
(BATCH) 3197 09 3750 810 506
392 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
822 Transactions by DB Load
The following transaction profiles list the transactions that have the greatest share in the database load sorted by percentage of total database access times
DATABASE LOAD BY TRANSACTIONS (DIALOG HTTP(S) )
Confidential Performance Overview PRD 1939
SAPreg GoingLivetrade Check - Verification Session 06082015
Transaction Type Dialog Steps Total DB Time in Avg DB Time in ms
VL71 DIA 83 127 263658
ZSDP0023 DIA 365 42 19871
FBL5N DIA 2919 22 1330
VA02 DIA 2183 16 1287
ZVC2 DIA 1360 15 1953
ZMMP0008 DIA 64 14 37798
VA01 DIA 2034 14 1164
ZSDP0013 DIA 47 12 43947
VKM1 DIA 478 10 3746
ZWMSCP01 DIA 130 08 10103
91 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
DATABASE LOAD BY TRANSACTIONS (BATCH)
Transaction Dialog Steps Total DB Time in Total DB Time in s
ZFIP0102 156 245 42300
ZFIP0115 260 135 23390
ZSD_CREATE_ORDER_BY_REF 125 41 7000
ZFIP0106 78 33 5720
ZSDP0031 8 16 2780
RSDB4UPD 2 12 2070
ZFII0002 1 09 1580
ZSDP0063 2 08 1320
ZSD_GENERATE_INFO_CONDITIONS 7 08 1320
ZFIP0101 263 07 1290
502 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
83 RFC Load by Initiating Action
The load in task type RFC is shown In the workload monitor this information is shown as Load from External Systems The calling system can be an application server of the system itself or any external system using the RFC interface The Initial Action is the calling program initiating the RFC The total response time for each initial action is shown as an absolute value and as a percentage compared to the total RFC load considered in this table The average times (per dialog step) are shown in milliseconds [ms] Calls from external systems are shown if they account for at least 8h or 5 of the total RFC load Local calls are shown if they account for at least 24h or 20 of the total RFC load
LOAD OVERVIEW
Initial System Load [s] Load
Local system PRD 4450 9957
Sum of external systems 19 043
RFC load (sum of above) 4469 10000
Confidential Performance Overview PRD 2039
SAPreg GoingLivetrade Check - Verification Session 06082015
Initial System Load [s] Load
RFC load in Performance Overview 10422 23321
Load of all task types in Performance Overview 51694 115668
TOP 20 RFC CALLS FROM LOCAL SYSTEM - AVERAGE TIMES [MS]
Initial System
Initial Action Total Resp
Time in s
of RFC Load
Avg Response
Time
Avg CPU Time
Avg DB Time
Avg Roll Wait Time
PRD RK2A1000_POST 892 1996 13097 147 87 20
PRD VF01 491 1099 25854 8767 14305 23
PRD VA01 468 1047 8402 170 543 14
PRD SAPLARFC 256 574 10505 208 305 17
PRD CA_QUEUE_ENTRY_BCS============CP 226 505 4628 1068 1398 251
PRD VA02 178 399 6343 1215 1490 14
PRD VL71 136 304 8330 698 330 118
PRD SAP_COLLECTOR_FOR_PERFMONITOR 132 295 33749 13108 7127 188
PRD VL02N 127 284 11757 2595 7164 18
PRD VL10X 96 215 4341 553 433 10
PRD VKM1 70 157 3532 813 930 35
PRD ZSDP0049 55 124 61422 1167 1553 64
PRD STMS 52 116 18555 1911 2091 77
PRD ZP01_FROM_ZP05_944988 52 115 171827 3233 1053 03
PRD ZSDP0010 45 100 74582 31983 32785 10
PRD XD02 43 097 403 116 126 05
PRD FB1D 42 093 1999 406 1263 06
PRD FBL5N 41 091 8700 630 866 14
PRD ZP01_FROM_ZP05_942398 38 086 63795 1867 2482 65
PRD FBZ5 32 071 319430 400 510 00
Confidential Performance Overview PRD 2139
SAPreg GoingLivetrade Check - Verification Session 06082015
9 SAP System Operating PRD
The daily operation of your system was analyzed We detected some problems that may impair system operation and stability
91 Availability based on Collector Protocols
A value of 100 means that the collector was available all day Available in the context of this report means that at least one SAP instance was running If the SAP collector was not running correctly the values in the table and graphics may be incorrect To check these logs call transaction ST03N (expert mode) and choose Collector and Performance DB -gt Performance Monitor Collector -gt Log
This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR that runs every hour The job does NOT check availability it carries out only general system tasks such as collecting and aggregating SAP performance data for all serversinstances The log does not contain any direct information about availability it contains only information about the status of the hourly statistical data collection
As of SAP Basis 640 system availability information is available in the CCMS (Computing Center Management System) of an SAP System in Service Level Reporting of SAP Solution Manager
This function is provided by the relevant Solution Manager Support Packages as an advanced development For more information refer to SAP Note 944496 which also lists the prerequisites that must be fulfilled before implementation can take place
92 Update Errors
In a system running under normal conditions only a small number of update errors should occur To set the rating for this check the number of active users is also taken into consideration
We did not detect any problems
Confidential SAP System Operating PRD 2239
SAPreg GoingLivetrade Check - Verification Session 06082015
93 Table Reorganization
The largest tables andor rapidly growing tables of system PRDwere checked No standard SAP recommendations for the applicable data volume management were found
94 Program Errors (ABAP Dumps)
50 ABAP dumps have been recorded in your system in the period 30072015 to 05082015 ABAP dumps are generally deleted after 7 days by default To view the ABAP dumps in your system call transaction ST22 and choose Selection Then select a timeframe
Date Number of Dumps
30072015 19
31072015 15
01082015 0
02082015 1
03082015 4
04082015 5
05082015 6
Name of Runtime Error Dumps Server (eg) User (eg) Date (eg) Time (eg)
TIME_OUT 1 SAP1R3P_PRD_00 EMOROCHO 30072015 104804
CALL_FUNCTION_SINGLE_LOGIN_REJ 2 SAP1R3P_PRD_00 SAPSYS 30072015 170339
DYNPRO_FIELD_CONVERSION 6 SAP1R3P_PRD_00 LORTEGA 31072015 172039
DBIF_RSQL_INVALID_RSQL 5 SAP1R3P_PRD_00 PREDROBAN 02082015 060047
CALL_FUNCTION_SEND_ERROR 2 SAP1R3P_PRD_00 JPVEND 03082015 073533
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY 3 SAP1R3P_PRD_00 LORTEGA 04082015 123208
RAISE_EXCEPTION 14 SAP1R3P_PRD_00 KCASTRO 05082015 094209
CONVT_NO_NUMBER 1 SAP1R3P_PRD_00 KABARCA 05082015 143511
UNCAUGHT_EXCEPTION 1 SAP1R3P_PRD_00 CBANCHON 05082015 150325
TSV_TNEW_PAGE_ALLOC_FAILED 5 SAP1R3P_PRD_00 FLUCAS 05082015 190338
MESSAGE_TYPE_X 10 SAP1R3P_PRD_00 INTERFASES 05082015 210129
It is important that you monitor ABAP dumps using transaction ST22 on a regular basis If ABAP dumps occur you should determine the cause as soon as possible Based on our analysis we found several ABAP dumps that need your attention Evaluate and resolve the above dumps If you cannot find a solution send a customer message to SAP to request support
Confidential SAP System Operating PRD 2339
SAPreg GoingLivetrade Check - Verification Session 06082015
10 Security
Critical security issues were found in your system
See the information in the following sections
Rating Check
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
101 ABAP Stack of PRD
1011 System Recommendations (ABAP)
System Recommendations is not used at all
Recommendation SAP strongly recommends applying important security fixes as soon as possible The System Recommendations application provides a detailed recommendation regarding which SAP security notes (ABAP and non-ABAP) should be implemented based on the actual status of the system and the notes already implemented This is a mandatory prerequisite for setting up a strong security patch process For more information go to httpservicesapcomsysrec
1012 Default Passwords of Standard Users
Standard users have default passwords
Recommendation Run report RSUSR003 to check the usage of default passwords by standard users
Ensure that users SAP (must exist in all clients) SAPCPIC and EARLYWATCH have non-default passwords in all clients For more information see Protecting Standard Users either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
Make sure that the standard password for user TMSADM has been changed in client 000 and delete this user in any other client SAP Note httpsservicesapcomsapsupportnotes1414256[1414256] describes a support tool to change the password of user TMSADM in all systems of the transport domain SAP Note httpsservicesapcomsapsupportnotes1552894[1552894] shows how to update the report RSUSR003 to show the status of user TMSADM
1013 ABAP Password Policy
If password login is allowed for specific instances only the password policy is checked only for these instances
10131 Password Complexity
PARAMETER LOGINMIN_PASSWORD_LNG
Confidential Security 2439
SAPreg GoingLivetrade Check - Verification Session 06082015
Rating Instance Current Value(s) Recommended Value
sap1r3p_PRD_00 6 8
The current system settings allow a password length of fewer than 8 characters This allows weak passwords Attackers may successfully recover these passwords and gain unauthorized access to the system
Recommendation Assign a minimum value of 8 to the profile parameter loginmin_password_lng
In addition SAP provides options to enforce complex passwords Find the current settings of the corresponding profile parameters in the following table
Parameter Instance Current Value(s)
loginmin_password_digits sap1r3p_PRD_00 0
loginmin_password_letters sap1r3p_PRD_00 0
loginmin_password_lowercase sap1r3p_PRD_00 0
loginmin_password_uppercase sap1r3p_PRD_00 0
loginmin_password_specials sap1r3p_PRD_00 0
Recommendation Enforce a minimum of 3 independent character categories using the corresponding profile parameters For more information see SAP Note httpsservicesapcomsapsupportnotes862989[862989] and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
1014 Gateway and Message Server Security
10141 Kernel Patch Level
Rating Kernel Release Current Kernel Patch Level Minimal Required Kernel Patch Level
700 135 260
To enable certain gateway security functionality a minimum kernel patch level is required Your system does not currently meet this requirement
Recommendation Update the kernel of your system to the newest kernel patch level available Update to a kernel patch level equal to or higher than the minimum required kernel patch level specified above For more information see SAP Note 1298433
10142 Gateway Security
Gateway Security Properties
The parameter GWREG_NO_CONN_INFO controls the activation of certain security properties of the SAP gateway It is defined as a bit mask with one bit per property
SAP Note httpsservicesapcomsapsupportnotes1298433[1298433] ldquoBypassing security in reginfo amp secinfordquo is not activated in your system The bit mask value for bit 1 is not set
Recommendation Enable the missing property by adding the bitmask value to the current value of GWREG_NO_CONN_INFO For more information about GWREG_NO_CONN_INFO see SAP Note 1444282
Confidential Security 2539
SAPreg GoingLivetrade Check - Verification Session 06082015
1015 Users with Critical Authorizations
For more information about the following check results see SAP Note 863362
Recommendation Depending on your environment review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations You can use the User Information System (transaction SUIM) to check the results For each check you can review the roles or profiles that include the authorization objects listed in the corresponding section
10151 Users Authorized to Start all Reports
This authorization allows critical functions and reports that do not contain their own authorization checks to be executed The specified number of users for each client have the checked authorization
Client No of Users Having This Authorization No of Valid Users Rating
001 2 3
400 147 160
Authorization objects
Object 1 S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2 S_PROGRAM with P_ACTION=SUBMIT P_GROUP=
Confidential Security 2639
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
4 Software Configuration For PRD
We have listed important recommendations concerning the current software configuration on your system These recommendations should be implemented at the earliest opportunity
Your systems software versions are checked If known issues with the software versions installed are identified they are highlighted
41 SAP Application Release - Maintenance Phases
SAP Product Version End of Mainstream Maintenance Status
SAP ERP 60 31122025
In October 2014 SAP announced a maintenance extension for SAP Business Suite 7 core application releases to 2025 If you are running a relevant release see SAP Note httpsservicesapcomsapsupportnotes1648480[1648480] for more details and applicable restrictions
42 Support Package Maintenance - ABAP
The following table shows an overview of currently installed software components
SUPPORT PACKAGES
Software Component
Version Patch Level
Latest Avail Patch Level
Support Package Component Description
EA-APPL 600 8 27 SAPKGPAD08 SAP R3 Enterprise PLM SCM Finance
EA-DFPS 600 8 27 SAPKGPDD08 SAP R3 Enterprise Defense Forces amp Public Security
EA-FINSERV 600 8 28 SAPKGPFD08 SAP R3 Enterprise Financial Services
EA-GLTRADE 600 8 27 SAPKGPGD08 SAP R3 Enterprise Global Trade
EA-HR 600 15 123 SAPKGPHD15 SAP R3 Enterprise Human Resources
EA-IPPE 400 8 27 SAPKGPID08 SAP R3 Enterprise Integrated Product and Process Engineering
EA-PS 600 8 27 SAPKGPPD08 SAP R3 Enterprise Public Services
EA-RETAIL 600 8 27 SAPKGPRD08 SAP R3 Enterprise Retail
ECC-DIMP 600 8 27 SAPK-60008INECCDIMP ECC Discrete Industries Mill Products
ERECRUIT 600 8 27 SAPK-60008INERECRUIT SAP E-Recruiting
FI-CA 600 8 8 SAPK-60008INFICA FI-CA Contract Accounts Receivable and Payable (virtuell)
FI-CAX 600 8 27 SAPK-60008INFICAX FI-CAX Extended FI-CA
FINBASIS 600 8 27 SAPK-60008INFINBASIS SAP R3 Enterprise FINBASIS
INSURANCE 600 8 27 SAPK-60008ININSURANC INSURANCE SAP Insurance
IS-CWM 600 8 27 SAPK-60008INISCWM IS-CWM Catch Weight Management
IS-H 600 8 40 SAPK-60008INISH IS-Hospital
IS-M 600 8 27 SAPK-60008INISM IS Media
IS-OIL 600 8 27 SAPK-60008INISOIL IS-OIL SAP OIL amp GAS Upstream Downstream
IS-PS-CA 600 8 27 SAPK-60008INISPSCA IS-PS-CA TaxampRevenue Campus Management
Confidential Software Configuration For PRD 839
SAPreg GoingLivetrade Check - Verification Session 06082015
Software Component
Version Patch Level
Latest Avail Patch Level
Support Package Component Description
IS-UT 600 8 27 SAPK-60008INISUT IS-UT
LSOFE 600 8 27 SAPK-60008INLSOFE Learning Solution - Front End
PI_BASIS 2005_1_700 11 26 SAPKIPYJ7B SAP R3 Basis Plug-In
SAP_ABA 700 11 32 SAPKA70011 SAP Application Basis
SAP_AP 700 8 33 SAPKNA7008 SAP Application Platform
SAP_APPL 600 8 27 SAPKH60008 SAP R3 Standard
SAP_BASIS 700 11 32 SAPKB70011 SAP Basis Component
SAP_BW 700 12 34 SAPKW70012 SAP Business Information Warehouse
SAP_HR 600 15 123 SAPKE60015 SAP R3 Standard HR
SEM-BW 600 8 27 SAPKGS6008 SAP SEM Server
ST-API 01L_ECC600 0 SAP Service Tools for Applications Plug-In
ST-PI 2008_1_700 0 12 SAP Solution Tools Plug-In
43 SAP Kernel Release
Instance SAP Kernel Release Patch Level
sap1r3p 00 700 135
Instance(s) SAP Kernel Release Patch Level Age in Months OS Family
sap1r3p_PRD_00 700 135 94
431 Downward Compatible Kernel
You are running an SAP kernel version that has been outdated since Q32012 This kernel version was replaced by the downward-compatible kernel You can continue to use your current kernel version but if an issue occurs with your current kernel a fix will be provided for SAP kernel 721 only Recommendation To avoid the potential risks associated with running an outdated SAP kernel version you should replace this version with downward-compatible SAP kernel 721 The downward-compatible kernel is a special validated SAP kernel that improves the stability of your system Requirements and prerequisites to install the downward-compatible kernel are summarized below
SAP Note Number
What to Do Description
1222907 Implement SAP note or SP Runtime object with incorrect alignment
1610716 Implement SAP note or SP and execute report Correcting runtime objects with incorrect alignment
1716826 Information Usage of the downward compatible Kernel 721 (EXT)
1713986 Installation instructions Installation of Kernel 721 (EXT)
1744209 Information SAP Kernel 720 and 721 Versions and Kernel Patch Levels
For security reasons the programs rfcexec and startrfc are no longer shipped together with the 720 kernel If you run scenarios that require these programs we recommend that you download and install the corresponding files from the NW RFC SDK 720 For details refer to SAP Note 1581595
4311 Required Implementation in SAP_BASIS
You must implement the SAP Notes mentioned in this section before installing the downward-compatible kernel
Confidential Software Configuration For PRD 939
SAPreg GoingLivetrade Check - Verification Session 06082015
4312 Required Parameter Settings
As a prerequisite for running the downward-compatible kernel the following parameters need to be set
Parameter Description Current Value Recommendation
rslgnew_layout System Log Format 9
432 Issues with current SAP Kernel
Your SAP kernel release may encounter serious problems
SAP tests all SAP kernels that are released However your patch level has been found to be unstable in certain cases and is therefore not recommended For more information see the release information for each SAP kernel patch on SAP Service Marketplace
For more information about issues concerning your current SAP kernel see the SAP Notes in the table below
Recommendation If the SAP kernel shipped with the latest Support Package stack of your product has the same issue as listed below install a more recent SAP kernel available in the Patches section of SAP Service Marketplace
SAP Note Short Text Risk
1132350 Incomplete update records
1150058 Incomplete update records
1223994 Composite SAP note Incomplete update records
433 Additional Remarks
SAP releases Support Package stacks (including SAP kernel patches) on a regular basis for most products (generally 2ndash4 times a year) We recommend that you base your software maintenance strategy on these stacks
You should only consider using a more recent SAP kernel patch than that shipped with the latest Support Package Stack for your product if specific errors occur
For more information see SAP Service Marketplace at httpssupportsapcomsoftwarepatchesstackshtml (SAP SupportPackage Stack information) and httpssupportsapcompatches (patchinformation)
Confidential Software Configuration For PRD 1039
SAPreg GoingLivetrade Check - Verification Session 06082015
5 Service Preparation and Data Quality of PRD
SAP ERP system PRD is not fully prepared for delivery of future remote services
Rating Check Performed
Service Data Quality
ST-PI and ST-API Plug-Ins
Service Preparation Check (RTCCTOOL)
Service Data Control Center
Hardware Utilization Data
In preparation for SAP services ensure that connections collectors and service tools are up to date These functionalities are explained in SAP Notes httpsservicesapcomsapsupportnotes91488[91488] and 1172939
51 Service Data Quality
For this service data of high importance is missing The service data is collected by the Service Data Control Center (SDCCN) or read from the Solution Managers BW or Configuration and Change Database (CCDB) This section comprehensively shows issues with the data quality and provides hints on how to resolve them
LEGEND FOR PRIORITY IN SERVICE DATA QUALITY
Prio Explanation Impact of Missing or Erroneous Data
Overall important data are missing Detecting a critical situation may fail Report cannot be rated green or yellow
Data for an important chapter are missing Some issues may not be detected Report cannot be rated green
Some important check could not be processed The report can be rated green nevertheless
Only checks of minor importance are affected
An optional check was skipped
511 Quality of Data in Service Data Control Center (SDCC)
QUALITY OF SERVICE DATA IN ST-PI
Prio Report Area affected Details and Related ST-PI Logical Function SAP Note
System Monitoring of Server (host) sap1r3p
During hardware data collection no SAPOSCOL was found It is either not running or not accessible ST-PI function EWA_GET_HARDWARE_INFO used in section Hardware Capacity
1309499
512 Quality of Service Data in Solution Manager Diagnostics - BW
Prio Report Area affected
Details and Related Infocube SAP Note
Workload of ABAP System PRD
Reading performance data from BW returned neither data nor an error code A timeout may have occurred Infocube 0CCMSMTPH used in section Workload Overview PRD
1332428
Confidential Service Preparation and Data Quality of PRD 1139
SAPreg GoingLivetrade Check - Verification Session 06082015
52 ST-PI and ST-API Plug-Ins
The table below shows the service plug-ins implemented and their releases and patch levels These recommendations are derived from report RTCCTOOL For more information about RTCCTOOL see SAP Note 309711
Rating Plug-In Release Patch Level Release Rec Patch Level Rec
ST-API 01L_ECC600 0 01R_700 1
ST-PI 2008_1_700 0 2008_1_700 11
Recommendation The Service Tools for Applications Plug-In (ST-API) is not up-to-date For more information see SAP Note 69455 The Solution Tools Plug-In (ST-PI) is not up-to-date For more information see SAP Note 539977
53 Service Preparation Check (RTCCTOOL)
Before we can ship any services the latest version of the SAP Service tools must be implemented in your system Report RTCCTOOL was last run on 06082015 During the check the tool detected issues for which a RED rating was set
Overall Status SAP Note Title Tool Status Manual Status
69455 [Note 69455] Addon ST-API 01R_700
69455 [Note 69455] ST-API 01R_700 Support Package 1
539977 [Note 539977] ST-PI 2008_1_700 Support Package 11
69455 [Note 69455] Proc after addon impl
539977 [Note 539977] Addon ST-PI 2008_1_700
539977 Note 1300023 for ST-PI
539977 Note 1312413 for ST-PI
539977 Note 1293657 for ST-PI
12103 [Note 12103] Collectors and TCOLL
207223 [Note 207223] EWAlert setup
Recommendation [Note 69455] Addon ST-API 01R_700 Servicetools for Applications Plug-In for NetWeaver 04s Basis 70x From httpsupportsapcomsupporttools- gtST-API-gtInstallationsampUpgrades download the installation ST-API 01R_700 Upload to tx SAINT and install as per note 69455 Then restart report RTCCTOOL and choose List-gtRefresh from SAPNet
[Note 69455] ST-API 01R_700 Support Package 1 Addon supportpackage level 1 for ST-API 01R_700 for NetWeaver 04s Basis 70x From httpsupportsapcomsupporttools- gtST-API-gtSupport packages-gtST-API 01R_700 download patches up to SAPKITAB7N For basis gt=700 use the Maintenance optimizer to release the download Upload from frontend to transaction SPAM define a queue and import
[Note 539977] ST-PI 2008_1_700 Support Package 11 Addon supportpackage level 11 for ST-PI 2008_1_700 for 700 [patches up to level 11 for Basis tools for services] Open httpsupportsapcomsupporttools- gtST-PI supportpk-gt ST-PI2008_1_700 Add patch SAPKITLRDL (and predecessors if not yet implemented) download basket Release basket via Maintenance optimizer Upload from frontend into transaction SPAM define a queue and import the queue
54 Performance DB (ST03 ST06)
Analysis of ST06 and history data indicate some problems with SAPOSCOL Check SAPOSCOL and see SAP Note 1309499
Confidential Service Preparation and Data Quality of PRD 1239
SAPreg GoingLivetrade Check - Verification Session 06082015
55 Hardware Utilization Data
Host Operating System Performance Data
sap1r3p OS not detected OK
Hardware capacity checks could not be run successfully due to missing data See SAP Note 1309499
Confidential Service Preparation and Data Quality of PRD 1339
SAPreg GoingLivetrade Check - Verification Session 06082015
6 Hardware Capacity
We have checked your system for potential CPU bottlenecks and found that the hardware is sufficient for the current workload
Note Hardware Capacity evaluation is based on hosts for which data is least partially available
61 Overview System PRD
General This analysis focuses on the workload during the peak working hours (9-11 13) and is based on the hourly averages collected by SAPOSCOL For information about the definition of peak working hours see SAP Note 1251291
CPU If the average CPU load exceeds 75 temporary CPU bottlenecks are likely to occur An average CPU load of more than 90 is a strong indicator of a CPU bottleneck
Memory If your hardware cannot handle the maximum memory consumption this causes a memory bottleneck in your SAP system that can impair performance The paging rating depends on the ratio of paging activity to physical memory A ratio exceeding 25 indicates high memory usage (if Java has been detected 0 ) and values above 50 (Java 10 ) demonstrate a main memory bottleneck
Server Max CPU load [] Date Rating RAM [MB]
sap1r3p 37 21072015 0
Note In case of virtualization or IaaS scenarios (eg IBM PowerVM VMware Amazon AWS ) it might be that for some hosts the CPU rating is yellow or red although the utilization value is quite low In this case the relevant host could not use maximum usable capacity due to a resource shortage within the virtualized infrastructure (eg IBM PowerVM Shared Pool CPU utilization)
Confidential Hardware Capacity 1439
SAPreg GoingLivetrade Check - Verification Session 06082015
7 Workload of System PRD
This chart displays the main task types and indicates how their workload is distributed in the system The table below lists the detailed KPIs
RESPONSE TIME COMPONENTS IN HOURS
Task Type Response Time Wait Time CPU Time DB Time GUI Time
DIALOG 55 00 20 20 07
BATCH 51 00 24 26 00
RFC 29 00 04 03 00
UPDATE 04 00 01 02 00
Others 02 00 00 00 00
71 Workload By Users
User activity is measured in the workload monitor Only users of at least medium activity are counted as active users
Users Low Activity Medium Activity High Activity Total Users
dialog steps per week 1 to 399 400 to 4799 4800 or more
measured in system 82 29 1 112
72 Workload Distribution PRD
The performance of your system was analyzed with respect to the workload distribution We did not detect any major problems that could affect the performance of your SAP system
721 Workload by Application Module
Confidential Workload of System PRD 1539
SAPreg GoingLivetrade Check - Verification Session 06082015
The following diagrams show how each application module contributes to the total system workload Two workload aspects are shown
- CPU time total CPU load on all servers in the system landscape
- Database time total database load generated by the application
All programs that are not classified in the SAP Application Hierarchy (transaction SE81) are summarized in the Un-Assigned category Customer programs industry solutions and third-party add-on developments fall into this category
722 DB Load Profile
Confidential Workload of System PRD 1639
SAPreg GoingLivetrade Check - Verification Session 06082015
The number of work processes creating database load in parallel is not significantly high
The following diagram shows the DB load caused by dialog RFC HTTP(S) and background tasks over different time frames The data provided in the diagram represents the average number of database processes occupied by each task type in the database during the specified time frames These statistics are calculated as a weekly average the average values over six working days with a unit of one hour Periods between 0000-0600 and 2100-2400 contain an average value per hour as these are not core business hours You can enable 24-hour monitoring by implementing SAP Note 17750 With 24-hour monitoring the time profile returns the workload of the system or application server on an hourly basis rather than returning an average value per hour for the periods 0000ndash0600 and 2100ndash2400 By comparing the load profiles for dialog and background activity you can get an overview of the volume of background activity during online working hours
Confidential Workload of System PRD 1739
SAPreg GoingLivetrade Check - Verification Session 06082015
8 Performance Overview PRD
The performance of your system was analyzed with respect to the average response times and total workload We did not detect any major problems that could affect the performance of your system
Rating Check
Performance Evaluation
The following table shows the average response times for various task types
AVERAGES OF RESPONSE TIME COMPONENTS IN MS
Task type Dialog Steps Response Time CPU Time Wait Time Load Time DB Time GUI Time
DIALOG 27390 7350 2584 56 60 2679 936
RFC 7535 13832 1702 33 53 1582 00
UPDATE 3114 4477 1392 12 97 2394 00
UPDATE2 2004 2029 665 12 41 878 00
BATCH 8357 21896 10330 07 105 11007 00
SPOOL 1221 5755 262 58 08 188 00
81 Performance Evaluation
The measured times are compared against reference times to provide a rating - If the number of dialog steps in an hour is less than 1000 this hour is not considered - If the total number of transaction steps is less than 20000 the rating for the task is not performed (indicated by a gray icon in the table) - RED if at least three time ranges are rated RED - YELLOW if two time ranges are rated RED or at least three time ranges are rated YELLOW
The table below shows that no problem is expected on the application or database servers
Task Steps Application Server Performance Database Server Performance
Dia 27389
Upd 3114
HTTP 0
HTTPS 0
The ratings in the table above are determined by comparisons against the reference table below If the dialog response times are very poor it will cause a RED rating for the entire check
Task Reference for Avg Response Time (ms) Yellow Rating
Reference for Avg Response Time (ms) Red Rating
Reference for Avg DB time (ms) Yellow Rating
Reference for Avg DB time (ms) Red Rating
Dia 1200 3600 600 1800
Upd 2400 3600 1200 1800
HTTP 1200 3600 600 1800
HTTPS 1200 3600 600 1800
Confidential Performance Overview PRD 1839
SAPreg GoingLivetrade Check - Verification Session 06082015
82 Transaction Profile Check
The following tables show the response times and the number of dialog steps for the transactions that cause the heaviest workload in your system
821 Transactions by Total Workload
The following tables list the activities with the highest contribution to the total workload
WORKLOAD BY TRANSACTION (DIALOG HTTP(S)WS-HTTP )
Transaction Type Dialog Steps Total Resp Time in
Avg Resp Time in ms
Avg CPU Time in ms
Avg DB Time in ms
Avg GUI Time in ms
VL71 DIA 83 61 297185 178782 263658 71
FBL5N DIA 2919 33 4626 1991 1330 242
VA01 DIA 2034 32 6258 2092 1164 1764
VA02 DIA 2183 29 5306 2194 1287 639
ZSDP0023 DIA 365 22 24427 2144 19871 2116
ZWMSCP01 DIA 130 21 65254 13125 10103 649
ME22 DIA 167 17 41818 22914 3250 07
VT01N DIA 235 15 25864 13412 1976 2443
SESSION_MANAGER DIA 1078 14 5202 663 844 2716
VKM1 DIA 478 12 9796 3358 3746 86
43 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
WORKLOAD BY TRANSACTION (BATCH)
Transaction Dialog Steps Total Resp Time in
Total Resp Time in s
Total CPU Time in s
Total DB Time in s
ZFIP0102 156 109 44040 25240 42295
ZFIP0115 260 97 39320 21180 23386
ZSD_CREATE_ORDER_BY_REF 125 75 30160 13100 7000
ZWMS_FILE_MANAGER2 784 37 14820 930 612
ZSDP0031 8 33 13260 6780 2783
ZFIP0105 390 16 6560 4350 383
ZFIP0106 78 15 6010 4140 5722
RSBTCRTE 2412 12 4820 1240 336
ZSDP0063 2 10 4050 2130 1318
(BATCH) 3197 09 3750 810 506
392 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
822 Transactions by DB Load
The following transaction profiles list the transactions that have the greatest share in the database load sorted by percentage of total database access times
DATABASE LOAD BY TRANSACTIONS (DIALOG HTTP(S) )
Confidential Performance Overview PRD 1939
SAPreg GoingLivetrade Check - Verification Session 06082015
Transaction Type Dialog Steps Total DB Time in Avg DB Time in ms
VL71 DIA 83 127 263658
ZSDP0023 DIA 365 42 19871
FBL5N DIA 2919 22 1330
VA02 DIA 2183 16 1287
ZVC2 DIA 1360 15 1953
ZMMP0008 DIA 64 14 37798
VA01 DIA 2034 14 1164
ZSDP0013 DIA 47 12 43947
VKM1 DIA 478 10 3746
ZWMSCP01 DIA 130 08 10103
91 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
DATABASE LOAD BY TRANSACTIONS (BATCH)
Transaction Dialog Steps Total DB Time in Total DB Time in s
ZFIP0102 156 245 42300
ZFIP0115 260 135 23390
ZSD_CREATE_ORDER_BY_REF 125 41 7000
ZFIP0106 78 33 5720
ZSDP0031 8 16 2780
RSDB4UPD 2 12 2070
ZFII0002 1 09 1580
ZSDP0063 2 08 1320
ZSD_GENERATE_INFO_CONDITIONS 7 08 1320
ZFIP0101 263 07 1290
502 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
83 RFC Load by Initiating Action
The load in task type RFC is shown In the workload monitor this information is shown as Load from External Systems The calling system can be an application server of the system itself or any external system using the RFC interface The Initial Action is the calling program initiating the RFC The total response time for each initial action is shown as an absolute value and as a percentage compared to the total RFC load considered in this table The average times (per dialog step) are shown in milliseconds [ms] Calls from external systems are shown if they account for at least 8h or 5 of the total RFC load Local calls are shown if they account for at least 24h or 20 of the total RFC load
LOAD OVERVIEW
Initial System Load [s] Load
Local system PRD 4450 9957
Sum of external systems 19 043
RFC load (sum of above) 4469 10000
Confidential Performance Overview PRD 2039
SAPreg GoingLivetrade Check - Verification Session 06082015
Initial System Load [s] Load
RFC load in Performance Overview 10422 23321
Load of all task types in Performance Overview 51694 115668
TOP 20 RFC CALLS FROM LOCAL SYSTEM - AVERAGE TIMES [MS]
Initial System
Initial Action Total Resp
Time in s
of RFC Load
Avg Response
Time
Avg CPU Time
Avg DB Time
Avg Roll Wait Time
PRD RK2A1000_POST 892 1996 13097 147 87 20
PRD VF01 491 1099 25854 8767 14305 23
PRD VA01 468 1047 8402 170 543 14
PRD SAPLARFC 256 574 10505 208 305 17
PRD CA_QUEUE_ENTRY_BCS============CP 226 505 4628 1068 1398 251
PRD VA02 178 399 6343 1215 1490 14
PRD VL71 136 304 8330 698 330 118
PRD SAP_COLLECTOR_FOR_PERFMONITOR 132 295 33749 13108 7127 188
PRD VL02N 127 284 11757 2595 7164 18
PRD VL10X 96 215 4341 553 433 10
PRD VKM1 70 157 3532 813 930 35
PRD ZSDP0049 55 124 61422 1167 1553 64
PRD STMS 52 116 18555 1911 2091 77
PRD ZP01_FROM_ZP05_944988 52 115 171827 3233 1053 03
PRD ZSDP0010 45 100 74582 31983 32785 10
PRD XD02 43 097 403 116 126 05
PRD FB1D 42 093 1999 406 1263 06
PRD FBL5N 41 091 8700 630 866 14
PRD ZP01_FROM_ZP05_942398 38 086 63795 1867 2482 65
PRD FBZ5 32 071 319430 400 510 00
Confidential Performance Overview PRD 2139
SAPreg GoingLivetrade Check - Verification Session 06082015
9 SAP System Operating PRD
The daily operation of your system was analyzed We detected some problems that may impair system operation and stability
91 Availability based on Collector Protocols
A value of 100 means that the collector was available all day Available in the context of this report means that at least one SAP instance was running If the SAP collector was not running correctly the values in the table and graphics may be incorrect To check these logs call transaction ST03N (expert mode) and choose Collector and Performance DB -gt Performance Monitor Collector -gt Log
This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR that runs every hour The job does NOT check availability it carries out only general system tasks such as collecting and aggregating SAP performance data for all serversinstances The log does not contain any direct information about availability it contains only information about the status of the hourly statistical data collection
As of SAP Basis 640 system availability information is available in the CCMS (Computing Center Management System) of an SAP System in Service Level Reporting of SAP Solution Manager
This function is provided by the relevant Solution Manager Support Packages as an advanced development For more information refer to SAP Note 944496 which also lists the prerequisites that must be fulfilled before implementation can take place
92 Update Errors
In a system running under normal conditions only a small number of update errors should occur To set the rating for this check the number of active users is also taken into consideration
We did not detect any problems
Confidential SAP System Operating PRD 2239
SAPreg GoingLivetrade Check - Verification Session 06082015
93 Table Reorganization
The largest tables andor rapidly growing tables of system PRDwere checked No standard SAP recommendations for the applicable data volume management were found
94 Program Errors (ABAP Dumps)
50 ABAP dumps have been recorded in your system in the period 30072015 to 05082015 ABAP dumps are generally deleted after 7 days by default To view the ABAP dumps in your system call transaction ST22 and choose Selection Then select a timeframe
Date Number of Dumps
30072015 19
31072015 15
01082015 0
02082015 1
03082015 4
04082015 5
05082015 6
Name of Runtime Error Dumps Server (eg) User (eg) Date (eg) Time (eg)
TIME_OUT 1 SAP1R3P_PRD_00 EMOROCHO 30072015 104804
CALL_FUNCTION_SINGLE_LOGIN_REJ 2 SAP1R3P_PRD_00 SAPSYS 30072015 170339
DYNPRO_FIELD_CONVERSION 6 SAP1R3P_PRD_00 LORTEGA 31072015 172039
DBIF_RSQL_INVALID_RSQL 5 SAP1R3P_PRD_00 PREDROBAN 02082015 060047
CALL_FUNCTION_SEND_ERROR 2 SAP1R3P_PRD_00 JPVEND 03082015 073533
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY 3 SAP1R3P_PRD_00 LORTEGA 04082015 123208
RAISE_EXCEPTION 14 SAP1R3P_PRD_00 KCASTRO 05082015 094209
CONVT_NO_NUMBER 1 SAP1R3P_PRD_00 KABARCA 05082015 143511
UNCAUGHT_EXCEPTION 1 SAP1R3P_PRD_00 CBANCHON 05082015 150325
TSV_TNEW_PAGE_ALLOC_FAILED 5 SAP1R3P_PRD_00 FLUCAS 05082015 190338
MESSAGE_TYPE_X 10 SAP1R3P_PRD_00 INTERFASES 05082015 210129
It is important that you monitor ABAP dumps using transaction ST22 on a regular basis If ABAP dumps occur you should determine the cause as soon as possible Based on our analysis we found several ABAP dumps that need your attention Evaluate and resolve the above dumps If you cannot find a solution send a customer message to SAP to request support
Confidential SAP System Operating PRD 2339
SAPreg GoingLivetrade Check - Verification Session 06082015
10 Security
Critical security issues were found in your system
See the information in the following sections
Rating Check
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
101 ABAP Stack of PRD
1011 System Recommendations (ABAP)
System Recommendations is not used at all
Recommendation SAP strongly recommends applying important security fixes as soon as possible The System Recommendations application provides a detailed recommendation regarding which SAP security notes (ABAP and non-ABAP) should be implemented based on the actual status of the system and the notes already implemented This is a mandatory prerequisite for setting up a strong security patch process For more information go to httpservicesapcomsysrec
1012 Default Passwords of Standard Users
Standard users have default passwords
Recommendation Run report RSUSR003 to check the usage of default passwords by standard users
Ensure that users SAP (must exist in all clients) SAPCPIC and EARLYWATCH have non-default passwords in all clients For more information see Protecting Standard Users either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
Make sure that the standard password for user TMSADM has been changed in client 000 and delete this user in any other client SAP Note httpsservicesapcomsapsupportnotes1414256[1414256] describes a support tool to change the password of user TMSADM in all systems of the transport domain SAP Note httpsservicesapcomsapsupportnotes1552894[1552894] shows how to update the report RSUSR003 to show the status of user TMSADM
1013 ABAP Password Policy
If password login is allowed for specific instances only the password policy is checked only for these instances
10131 Password Complexity
PARAMETER LOGINMIN_PASSWORD_LNG
Confidential Security 2439
SAPreg GoingLivetrade Check - Verification Session 06082015
Rating Instance Current Value(s) Recommended Value
sap1r3p_PRD_00 6 8
The current system settings allow a password length of fewer than 8 characters This allows weak passwords Attackers may successfully recover these passwords and gain unauthorized access to the system
Recommendation Assign a minimum value of 8 to the profile parameter loginmin_password_lng
In addition SAP provides options to enforce complex passwords Find the current settings of the corresponding profile parameters in the following table
Parameter Instance Current Value(s)
loginmin_password_digits sap1r3p_PRD_00 0
loginmin_password_letters sap1r3p_PRD_00 0
loginmin_password_lowercase sap1r3p_PRD_00 0
loginmin_password_uppercase sap1r3p_PRD_00 0
loginmin_password_specials sap1r3p_PRD_00 0
Recommendation Enforce a minimum of 3 independent character categories using the corresponding profile parameters For more information see SAP Note httpsservicesapcomsapsupportnotes862989[862989] and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
1014 Gateway and Message Server Security
10141 Kernel Patch Level
Rating Kernel Release Current Kernel Patch Level Minimal Required Kernel Patch Level
700 135 260
To enable certain gateway security functionality a minimum kernel patch level is required Your system does not currently meet this requirement
Recommendation Update the kernel of your system to the newest kernel patch level available Update to a kernel patch level equal to or higher than the minimum required kernel patch level specified above For more information see SAP Note 1298433
10142 Gateway Security
Gateway Security Properties
The parameter GWREG_NO_CONN_INFO controls the activation of certain security properties of the SAP gateway It is defined as a bit mask with one bit per property
SAP Note httpsservicesapcomsapsupportnotes1298433[1298433] ldquoBypassing security in reginfo amp secinfordquo is not activated in your system The bit mask value for bit 1 is not set
Recommendation Enable the missing property by adding the bitmask value to the current value of GWREG_NO_CONN_INFO For more information about GWREG_NO_CONN_INFO see SAP Note 1444282
Confidential Security 2539
SAPreg GoingLivetrade Check - Verification Session 06082015
1015 Users with Critical Authorizations
For more information about the following check results see SAP Note 863362
Recommendation Depending on your environment review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations You can use the User Information System (transaction SUIM) to check the results For each check you can review the roles or profiles that include the authorization objects listed in the corresponding section
10151 Users Authorized to Start all Reports
This authorization allows critical functions and reports that do not contain their own authorization checks to be executed The specified number of users for each client have the checked authorization
Client No of Users Having This Authorization No of Valid Users Rating
001 2 3
400 147 160
Authorization objects
Object 1 S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2 S_PROGRAM with P_ACTION=SUBMIT P_GROUP=
Confidential Security 2639
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
Software Component
Version Patch Level
Latest Avail Patch Level
Support Package Component Description
IS-UT 600 8 27 SAPK-60008INISUT IS-UT
LSOFE 600 8 27 SAPK-60008INLSOFE Learning Solution - Front End
PI_BASIS 2005_1_700 11 26 SAPKIPYJ7B SAP R3 Basis Plug-In
SAP_ABA 700 11 32 SAPKA70011 SAP Application Basis
SAP_AP 700 8 33 SAPKNA7008 SAP Application Platform
SAP_APPL 600 8 27 SAPKH60008 SAP R3 Standard
SAP_BASIS 700 11 32 SAPKB70011 SAP Basis Component
SAP_BW 700 12 34 SAPKW70012 SAP Business Information Warehouse
SAP_HR 600 15 123 SAPKE60015 SAP R3 Standard HR
SEM-BW 600 8 27 SAPKGS6008 SAP SEM Server
ST-API 01L_ECC600 0 SAP Service Tools for Applications Plug-In
ST-PI 2008_1_700 0 12 SAP Solution Tools Plug-In
43 SAP Kernel Release
Instance SAP Kernel Release Patch Level
sap1r3p 00 700 135
Instance(s) SAP Kernel Release Patch Level Age in Months OS Family
sap1r3p_PRD_00 700 135 94
431 Downward Compatible Kernel
You are running an SAP kernel version that has been outdated since Q32012 This kernel version was replaced by the downward-compatible kernel You can continue to use your current kernel version but if an issue occurs with your current kernel a fix will be provided for SAP kernel 721 only Recommendation To avoid the potential risks associated with running an outdated SAP kernel version you should replace this version with downward-compatible SAP kernel 721 The downward-compatible kernel is a special validated SAP kernel that improves the stability of your system Requirements and prerequisites to install the downward-compatible kernel are summarized below
SAP Note Number
What to Do Description
1222907 Implement SAP note or SP Runtime object with incorrect alignment
1610716 Implement SAP note or SP and execute report Correcting runtime objects with incorrect alignment
1716826 Information Usage of the downward compatible Kernel 721 (EXT)
1713986 Installation instructions Installation of Kernel 721 (EXT)
1744209 Information SAP Kernel 720 and 721 Versions and Kernel Patch Levels
For security reasons the programs rfcexec and startrfc are no longer shipped together with the 720 kernel If you run scenarios that require these programs we recommend that you download and install the corresponding files from the NW RFC SDK 720 For details refer to SAP Note 1581595
4311 Required Implementation in SAP_BASIS
You must implement the SAP Notes mentioned in this section before installing the downward-compatible kernel
Confidential Software Configuration For PRD 939
SAPreg GoingLivetrade Check - Verification Session 06082015
4312 Required Parameter Settings
As a prerequisite for running the downward-compatible kernel the following parameters need to be set
Parameter Description Current Value Recommendation
rslgnew_layout System Log Format 9
432 Issues with current SAP Kernel
Your SAP kernel release may encounter serious problems
SAP tests all SAP kernels that are released However your patch level has been found to be unstable in certain cases and is therefore not recommended For more information see the release information for each SAP kernel patch on SAP Service Marketplace
For more information about issues concerning your current SAP kernel see the SAP Notes in the table below
Recommendation If the SAP kernel shipped with the latest Support Package stack of your product has the same issue as listed below install a more recent SAP kernel available in the Patches section of SAP Service Marketplace
SAP Note Short Text Risk
1132350 Incomplete update records
1150058 Incomplete update records
1223994 Composite SAP note Incomplete update records
433 Additional Remarks
SAP releases Support Package stacks (including SAP kernel patches) on a regular basis for most products (generally 2ndash4 times a year) We recommend that you base your software maintenance strategy on these stacks
You should only consider using a more recent SAP kernel patch than that shipped with the latest Support Package Stack for your product if specific errors occur
For more information see SAP Service Marketplace at httpssupportsapcomsoftwarepatchesstackshtml (SAP SupportPackage Stack information) and httpssupportsapcompatches (patchinformation)
Confidential Software Configuration For PRD 1039
SAPreg GoingLivetrade Check - Verification Session 06082015
5 Service Preparation and Data Quality of PRD
SAP ERP system PRD is not fully prepared for delivery of future remote services
Rating Check Performed
Service Data Quality
ST-PI and ST-API Plug-Ins
Service Preparation Check (RTCCTOOL)
Service Data Control Center
Hardware Utilization Data
In preparation for SAP services ensure that connections collectors and service tools are up to date These functionalities are explained in SAP Notes httpsservicesapcomsapsupportnotes91488[91488] and 1172939
51 Service Data Quality
For this service data of high importance is missing The service data is collected by the Service Data Control Center (SDCCN) or read from the Solution Managers BW or Configuration and Change Database (CCDB) This section comprehensively shows issues with the data quality and provides hints on how to resolve them
LEGEND FOR PRIORITY IN SERVICE DATA QUALITY
Prio Explanation Impact of Missing or Erroneous Data
Overall important data are missing Detecting a critical situation may fail Report cannot be rated green or yellow
Data for an important chapter are missing Some issues may not be detected Report cannot be rated green
Some important check could not be processed The report can be rated green nevertheless
Only checks of minor importance are affected
An optional check was skipped
511 Quality of Data in Service Data Control Center (SDCC)
QUALITY OF SERVICE DATA IN ST-PI
Prio Report Area affected Details and Related ST-PI Logical Function SAP Note
System Monitoring of Server (host) sap1r3p
During hardware data collection no SAPOSCOL was found It is either not running or not accessible ST-PI function EWA_GET_HARDWARE_INFO used in section Hardware Capacity
1309499
512 Quality of Service Data in Solution Manager Diagnostics - BW
Prio Report Area affected
Details and Related Infocube SAP Note
Workload of ABAP System PRD
Reading performance data from BW returned neither data nor an error code A timeout may have occurred Infocube 0CCMSMTPH used in section Workload Overview PRD
1332428
Confidential Service Preparation and Data Quality of PRD 1139
SAPreg GoingLivetrade Check - Verification Session 06082015
52 ST-PI and ST-API Plug-Ins
The table below shows the service plug-ins implemented and their releases and patch levels These recommendations are derived from report RTCCTOOL For more information about RTCCTOOL see SAP Note 309711
Rating Plug-In Release Patch Level Release Rec Patch Level Rec
ST-API 01L_ECC600 0 01R_700 1
ST-PI 2008_1_700 0 2008_1_700 11
Recommendation The Service Tools for Applications Plug-In (ST-API) is not up-to-date For more information see SAP Note 69455 The Solution Tools Plug-In (ST-PI) is not up-to-date For more information see SAP Note 539977
53 Service Preparation Check (RTCCTOOL)
Before we can ship any services the latest version of the SAP Service tools must be implemented in your system Report RTCCTOOL was last run on 06082015 During the check the tool detected issues for which a RED rating was set
Overall Status SAP Note Title Tool Status Manual Status
69455 [Note 69455] Addon ST-API 01R_700
69455 [Note 69455] ST-API 01R_700 Support Package 1
539977 [Note 539977] ST-PI 2008_1_700 Support Package 11
69455 [Note 69455] Proc after addon impl
539977 [Note 539977] Addon ST-PI 2008_1_700
539977 Note 1300023 for ST-PI
539977 Note 1312413 for ST-PI
539977 Note 1293657 for ST-PI
12103 [Note 12103] Collectors and TCOLL
207223 [Note 207223] EWAlert setup
Recommendation [Note 69455] Addon ST-API 01R_700 Servicetools for Applications Plug-In for NetWeaver 04s Basis 70x From httpsupportsapcomsupporttools- gtST-API-gtInstallationsampUpgrades download the installation ST-API 01R_700 Upload to tx SAINT and install as per note 69455 Then restart report RTCCTOOL and choose List-gtRefresh from SAPNet
[Note 69455] ST-API 01R_700 Support Package 1 Addon supportpackage level 1 for ST-API 01R_700 for NetWeaver 04s Basis 70x From httpsupportsapcomsupporttools- gtST-API-gtSupport packages-gtST-API 01R_700 download patches up to SAPKITAB7N For basis gt=700 use the Maintenance optimizer to release the download Upload from frontend to transaction SPAM define a queue and import
[Note 539977] ST-PI 2008_1_700 Support Package 11 Addon supportpackage level 11 for ST-PI 2008_1_700 for 700 [patches up to level 11 for Basis tools for services] Open httpsupportsapcomsupporttools- gtST-PI supportpk-gt ST-PI2008_1_700 Add patch SAPKITLRDL (and predecessors if not yet implemented) download basket Release basket via Maintenance optimizer Upload from frontend into transaction SPAM define a queue and import the queue
54 Performance DB (ST03 ST06)
Analysis of ST06 and history data indicate some problems with SAPOSCOL Check SAPOSCOL and see SAP Note 1309499
Confidential Service Preparation and Data Quality of PRD 1239
SAPreg GoingLivetrade Check - Verification Session 06082015
55 Hardware Utilization Data
Host Operating System Performance Data
sap1r3p OS not detected OK
Hardware capacity checks could not be run successfully due to missing data See SAP Note 1309499
Confidential Service Preparation and Data Quality of PRD 1339
SAPreg GoingLivetrade Check - Verification Session 06082015
6 Hardware Capacity
We have checked your system for potential CPU bottlenecks and found that the hardware is sufficient for the current workload
Note Hardware Capacity evaluation is based on hosts for which data is least partially available
61 Overview System PRD
General This analysis focuses on the workload during the peak working hours (9-11 13) and is based on the hourly averages collected by SAPOSCOL For information about the definition of peak working hours see SAP Note 1251291
CPU If the average CPU load exceeds 75 temporary CPU bottlenecks are likely to occur An average CPU load of more than 90 is a strong indicator of a CPU bottleneck
Memory If your hardware cannot handle the maximum memory consumption this causes a memory bottleneck in your SAP system that can impair performance The paging rating depends on the ratio of paging activity to physical memory A ratio exceeding 25 indicates high memory usage (if Java has been detected 0 ) and values above 50 (Java 10 ) demonstrate a main memory bottleneck
Server Max CPU load [] Date Rating RAM [MB]
sap1r3p 37 21072015 0
Note In case of virtualization or IaaS scenarios (eg IBM PowerVM VMware Amazon AWS ) it might be that for some hosts the CPU rating is yellow or red although the utilization value is quite low In this case the relevant host could not use maximum usable capacity due to a resource shortage within the virtualized infrastructure (eg IBM PowerVM Shared Pool CPU utilization)
Confidential Hardware Capacity 1439
SAPreg GoingLivetrade Check - Verification Session 06082015
7 Workload of System PRD
This chart displays the main task types and indicates how their workload is distributed in the system The table below lists the detailed KPIs
RESPONSE TIME COMPONENTS IN HOURS
Task Type Response Time Wait Time CPU Time DB Time GUI Time
DIALOG 55 00 20 20 07
BATCH 51 00 24 26 00
RFC 29 00 04 03 00
UPDATE 04 00 01 02 00
Others 02 00 00 00 00
71 Workload By Users
User activity is measured in the workload monitor Only users of at least medium activity are counted as active users
Users Low Activity Medium Activity High Activity Total Users
dialog steps per week 1 to 399 400 to 4799 4800 or more
measured in system 82 29 1 112
72 Workload Distribution PRD
The performance of your system was analyzed with respect to the workload distribution We did not detect any major problems that could affect the performance of your SAP system
721 Workload by Application Module
Confidential Workload of System PRD 1539
SAPreg GoingLivetrade Check - Verification Session 06082015
The following diagrams show how each application module contributes to the total system workload Two workload aspects are shown
- CPU time total CPU load on all servers in the system landscape
- Database time total database load generated by the application
All programs that are not classified in the SAP Application Hierarchy (transaction SE81) are summarized in the Un-Assigned category Customer programs industry solutions and third-party add-on developments fall into this category
722 DB Load Profile
Confidential Workload of System PRD 1639
SAPreg GoingLivetrade Check - Verification Session 06082015
The number of work processes creating database load in parallel is not significantly high
The following diagram shows the DB load caused by dialog RFC HTTP(S) and background tasks over different time frames The data provided in the diagram represents the average number of database processes occupied by each task type in the database during the specified time frames These statistics are calculated as a weekly average the average values over six working days with a unit of one hour Periods between 0000-0600 and 2100-2400 contain an average value per hour as these are not core business hours You can enable 24-hour monitoring by implementing SAP Note 17750 With 24-hour monitoring the time profile returns the workload of the system or application server on an hourly basis rather than returning an average value per hour for the periods 0000ndash0600 and 2100ndash2400 By comparing the load profiles for dialog and background activity you can get an overview of the volume of background activity during online working hours
Confidential Workload of System PRD 1739
SAPreg GoingLivetrade Check - Verification Session 06082015
8 Performance Overview PRD
The performance of your system was analyzed with respect to the average response times and total workload We did not detect any major problems that could affect the performance of your system
Rating Check
Performance Evaluation
The following table shows the average response times for various task types
AVERAGES OF RESPONSE TIME COMPONENTS IN MS
Task type Dialog Steps Response Time CPU Time Wait Time Load Time DB Time GUI Time
DIALOG 27390 7350 2584 56 60 2679 936
RFC 7535 13832 1702 33 53 1582 00
UPDATE 3114 4477 1392 12 97 2394 00
UPDATE2 2004 2029 665 12 41 878 00
BATCH 8357 21896 10330 07 105 11007 00
SPOOL 1221 5755 262 58 08 188 00
81 Performance Evaluation
The measured times are compared against reference times to provide a rating - If the number of dialog steps in an hour is less than 1000 this hour is not considered - If the total number of transaction steps is less than 20000 the rating for the task is not performed (indicated by a gray icon in the table) - RED if at least three time ranges are rated RED - YELLOW if two time ranges are rated RED or at least three time ranges are rated YELLOW
The table below shows that no problem is expected on the application or database servers
Task Steps Application Server Performance Database Server Performance
Dia 27389
Upd 3114
HTTP 0
HTTPS 0
The ratings in the table above are determined by comparisons against the reference table below If the dialog response times are very poor it will cause a RED rating for the entire check
Task Reference for Avg Response Time (ms) Yellow Rating
Reference for Avg Response Time (ms) Red Rating
Reference for Avg DB time (ms) Yellow Rating
Reference for Avg DB time (ms) Red Rating
Dia 1200 3600 600 1800
Upd 2400 3600 1200 1800
HTTP 1200 3600 600 1800
HTTPS 1200 3600 600 1800
Confidential Performance Overview PRD 1839
SAPreg GoingLivetrade Check - Verification Session 06082015
82 Transaction Profile Check
The following tables show the response times and the number of dialog steps for the transactions that cause the heaviest workload in your system
821 Transactions by Total Workload
The following tables list the activities with the highest contribution to the total workload
WORKLOAD BY TRANSACTION (DIALOG HTTP(S)WS-HTTP )
Transaction Type Dialog Steps Total Resp Time in
Avg Resp Time in ms
Avg CPU Time in ms
Avg DB Time in ms
Avg GUI Time in ms
VL71 DIA 83 61 297185 178782 263658 71
FBL5N DIA 2919 33 4626 1991 1330 242
VA01 DIA 2034 32 6258 2092 1164 1764
VA02 DIA 2183 29 5306 2194 1287 639
ZSDP0023 DIA 365 22 24427 2144 19871 2116
ZWMSCP01 DIA 130 21 65254 13125 10103 649
ME22 DIA 167 17 41818 22914 3250 07
VT01N DIA 235 15 25864 13412 1976 2443
SESSION_MANAGER DIA 1078 14 5202 663 844 2716
VKM1 DIA 478 12 9796 3358 3746 86
43 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
WORKLOAD BY TRANSACTION (BATCH)
Transaction Dialog Steps Total Resp Time in
Total Resp Time in s
Total CPU Time in s
Total DB Time in s
ZFIP0102 156 109 44040 25240 42295
ZFIP0115 260 97 39320 21180 23386
ZSD_CREATE_ORDER_BY_REF 125 75 30160 13100 7000
ZWMS_FILE_MANAGER2 784 37 14820 930 612
ZSDP0031 8 33 13260 6780 2783
ZFIP0105 390 16 6560 4350 383
ZFIP0106 78 15 6010 4140 5722
RSBTCRTE 2412 12 4820 1240 336
ZSDP0063 2 10 4050 2130 1318
(BATCH) 3197 09 3750 810 506
392 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
822 Transactions by DB Load
The following transaction profiles list the transactions that have the greatest share in the database load sorted by percentage of total database access times
DATABASE LOAD BY TRANSACTIONS (DIALOG HTTP(S) )
Confidential Performance Overview PRD 1939
SAPreg GoingLivetrade Check - Verification Session 06082015
Transaction Type Dialog Steps Total DB Time in Avg DB Time in ms
VL71 DIA 83 127 263658
ZSDP0023 DIA 365 42 19871
FBL5N DIA 2919 22 1330
VA02 DIA 2183 16 1287
ZVC2 DIA 1360 15 1953
ZMMP0008 DIA 64 14 37798
VA01 DIA 2034 14 1164
ZSDP0013 DIA 47 12 43947
VKM1 DIA 478 10 3746
ZWMSCP01 DIA 130 08 10103
91 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
DATABASE LOAD BY TRANSACTIONS (BATCH)
Transaction Dialog Steps Total DB Time in Total DB Time in s
ZFIP0102 156 245 42300
ZFIP0115 260 135 23390
ZSD_CREATE_ORDER_BY_REF 125 41 7000
ZFIP0106 78 33 5720
ZSDP0031 8 16 2780
RSDB4UPD 2 12 2070
ZFII0002 1 09 1580
ZSDP0063 2 08 1320
ZSD_GENERATE_INFO_CONDITIONS 7 08 1320
ZFIP0101 263 07 1290
502 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
83 RFC Load by Initiating Action
The load in task type RFC is shown In the workload monitor this information is shown as Load from External Systems The calling system can be an application server of the system itself or any external system using the RFC interface The Initial Action is the calling program initiating the RFC The total response time for each initial action is shown as an absolute value and as a percentage compared to the total RFC load considered in this table The average times (per dialog step) are shown in milliseconds [ms] Calls from external systems are shown if they account for at least 8h or 5 of the total RFC load Local calls are shown if they account for at least 24h or 20 of the total RFC load
LOAD OVERVIEW
Initial System Load [s] Load
Local system PRD 4450 9957
Sum of external systems 19 043
RFC load (sum of above) 4469 10000
Confidential Performance Overview PRD 2039
SAPreg GoingLivetrade Check - Verification Session 06082015
Initial System Load [s] Load
RFC load in Performance Overview 10422 23321
Load of all task types in Performance Overview 51694 115668
TOP 20 RFC CALLS FROM LOCAL SYSTEM - AVERAGE TIMES [MS]
Initial System
Initial Action Total Resp
Time in s
of RFC Load
Avg Response
Time
Avg CPU Time
Avg DB Time
Avg Roll Wait Time
PRD RK2A1000_POST 892 1996 13097 147 87 20
PRD VF01 491 1099 25854 8767 14305 23
PRD VA01 468 1047 8402 170 543 14
PRD SAPLARFC 256 574 10505 208 305 17
PRD CA_QUEUE_ENTRY_BCS============CP 226 505 4628 1068 1398 251
PRD VA02 178 399 6343 1215 1490 14
PRD VL71 136 304 8330 698 330 118
PRD SAP_COLLECTOR_FOR_PERFMONITOR 132 295 33749 13108 7127 188
PRD VL02N 127 284 11757 2595 7164 18
PRD VL10X 96 215 4341 553 433 10
PRD VKM1 70 157 3532 813 930 35
PRD ZSDP0049 55 124 61422 1167 1553 64
PRD STMS 52 116 18555 1911 2091 77
PRD ZP01_FROM_ZP05_944988 52 115 171827 3233 1053 03
PRD ZSDP0010 45 100 74582 31983 32785 10
PRD XD02 43 097 403 116 126 05
PRD FB1D 42 093 1999 406 1263 06
PRD FBL5N 41 091 8700 630 866 14
PRD ZP01_FROM_ZP05_942398 38 086 63795 1867 2482 65
PRD FBZ5 32 071 319430 400 510 00
Confidential Performance Overview PRD 2139
SAPreg GoingLivetrade Check - Verification Session 06082015
9 SAP System Operating PRD
The daily operation of your system was analyzed We detected some problems that may impair system operation and stability
91 Availability based on Collector Protocols
A value of 100 means that the collector was available all day Available in the context of this report means that at least one SAP instance was running If the SAP collector was not running correctly the values in the table and graphics may be incorrect To check these logs call transaction ST03N (expert mode) and choose Collector and Performance DB -gt Performance Monitor Collector -gt Log
This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR that runs every hour The job does NOT check availability it carries out only general system tasks such as collecting and aggregating SAP performance data for all serversinstances The log does not contain any direct information about availability it contains only information about the status of the hourly statistical data collection
As of SAP Basis 640 system availability information is available in the CCMS (Computing Center Management System) of an SAP System in Service Level Reporting of SAP Solution Manager
This function is provided by the relevant Solution Manager Support Packages as an advanced development For more information refer to SAP Note 944496 which also lists the prerequisites that must be fulfilled before implementation can take place
92 Update Errors
In a system running under normal conditions only a small number of update errors should occur To set the rating for this check the number of active users is also taken into consideration
We did not detect any problems
Confidential SAP System Operating PRD 2239
SAPreg GoingLivetrade Check - Verification Session 06082015
93 Table Reorganization
The largest tables andor rapidly growing tables of system PRDwere checked No standard SAP recommendations for the applicable data volume management were found
94 Program Errors (ABAP Dumps)
50 ABAP dumps have been recorded in your system in the period 30072015 to 05082015 ABAP dumps are generally deleted after 7 days by default To view the ABAP dumps in your system call transaction ST22 and choose Selection Then select a timeframe
Date Number of Dumps
30072015 19
31072015 15
01082015 0
02082015 1
03082015 4
04082015 5
05082015 6
Name of Runtime Error Dumps Server (eg) User (eg) Date (eg) Time (eg)
TIME_OUT 1 SAP1R3P_PRD_00 EMOROCHO 30072015 104804
CALL_FUNCTION_SINGLE_LOGIN_REJ 2 SAP1R3P_PRD_00 SAPSYS 30072015 170339
DYNPRO_FIELD_CONVERSION 6 SAP1R3P_PRD_00 LORTEGA 31072015 172039
DBIF_RSQL_INVALID_RSQL 5 SAP1R3P_PRD_00 PREDROBAN 02082015 060047
CALL_FUNCTION_SEND_ERROR 2 SAP1R3P_PRD_00 JPVEND 03082015 073533
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY 3 SAP1R3P_PRD_00 LORTEGA 04082015 123208
RAISE_EXCEPTION 14 SAP1R3P_PRD_00 KCASTRO 05082015 094209
CONVT_NO_NUMBER 1 SAP1R3P_PRD_00 KABARCA 05082015 143511
UNCAUGHT_EXCEPTION 1 SAP1R3P_PRD_00 CBANCHON 05082015 150325
TSV_TNEW_PAGE_ALLOC_FAILED 5 SAP1R3P_PRD_00 FLUCAS 05082015 190338
MESSAGE_TYPE_X 10 SAP1R3P_PRD_00 INTERFASES 05082015 210129
It is important that you monitor ABAP dumps using transaction ST22 on a regular basis If ABAP dumps occur you should determine the cause as soon as possible Based on our analysis we found several ABAP dumps that need your attention Evaluate and resolve the above dumps If you cannot find a solution send a customer message to SAP to request support
Confidential SAP System Operating PRD 2339
SAPreg GoingLivetrade Check - Verification Session 06082015
10 Security
Critical security issues were found in your system
See the information in the following sections
Rating Check
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
101 ABAP Stack of PRD
1011 System Recommendations (ABAP)
System Recommendations is not used at all
Recommendation SAP strongly recommends applying important security fixes as soon as possible The System Recommendations application provides a detailed recommendation regarding which SAP security notes (ABAP and non-ABAP) should be implemented based on the actual status of the system and the notes already implemented This is a mandatory prerequisite for setting up a strong security patch process For more information go to httpservicesapcomsysrec
1012 Default Passwords of Standard Users
Standard users have default passwords
Recommendation Run report RSUSR003 to check the usage of default passwords by standard users
Ensure that users SAP (must exist in all clients) SAPCPIC and EARLYWATCH have non-default passwords in all clients For more information see Protecting Standard Users either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
Make sure that the standard password for user TMSADM has been changed in client 000 and delete this user in any other client SAP Note httpsservicesapcomsapsupportnotes1414256[1414256] describes a support tool to change the password of user TMSADM in all systems of the transport domain SAP Note httpsservicesapcomsapsupportnotes1552894[1552894] shows how to update the report RSUSR003 to show the status of user TMSADM
1013 ABAP Password Policy
If password login is allowed for specific instances only the password policy is checked only for these instances
10131 Password Complexity
PARAMETER LOGINMIN_PASSWORD_LNG
Confidential Security 2439
SAPreg GoingLivetrade Check - Verification Session 06082015
Rating Instance Current Value(s) Recommended Value
sap1r3p_PRD_00 6 8
The current system settings allow a password length of fewer than 8 characters This allows weak passwords Attackers may successfully recover these passwords and gain unauthorized access to the system
Recommendation Assign a minimum value of 8 to the profile parameter loginmin_password_lng
In addition SAP provides options to enforce complex passwords Find the current settings of the corresponding profile parameters in the following table
Parameter Instance Current Value(s)
loginmin_password_digits sap1r3p_PRD_00 0
loginmin_password_letters sap1r3p_PRD_00 0
loginmin_password_lowercase sap1r3p_PRD_00 0
loginmin_password_uppercase sap1r3p_PRD_00 0
loginmin_password_specials sap1r3p_PRD_00 0
Recommendation Enforce a minimum of 3 independent character categories using the corresponding profile parameters For more information see SAP Note httpsservicesapcomsapsupportnotes862989[862989] and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
1014 Gateway and Message Server Security
10141 Kernel Patch Level
Rating Kernel Release Current Kernel Patch Level Minimal Required Kernel Patch Level
700 135 260
To enable certain gateway security functionality a minimum kernel patch level is required Your system does not currently meet this requirement
Recommendation Update the kernel of your system to the newest kernel patch level available Update to a kernel patch level equal to or higher than the minimum required kernel patch level specified above For more information see SAP Note 1298433
10142 Gateway Security
Gateway Security Properties
The parameter GWREG_NO_CONN_INFO controls the activation of certain security properties of the SAP gateway It is defined as a bit mask with one bit per property
SAP Note httpsservicesapcomsapsupportnotes1298433[1298433] ldquoBypassing security in reginfo amp secinfordquo is not activated in your system The bit mask value for bit 1 is not set
Recommendation Enable the missing property by adding the bitmask value to the current value of GWREG_NO_CONN_INFO For more information about GWREG_NO_CONN_INFO see SAP Note 1444282
Confidential Security 2539
SAPreg GoingLivetrade Check - Verification Session 06082015
1015 Users with Critical Authorizations
For more information about the following check results see SAP Note 863362
Recommendation Depending on your environment review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations You can use the User Information System (transaction SUIM) to check the results For each check you can review the roles or profiles that include the authorization objects listed in the corresponding section
10151 Users Authorized to Start all Reports
This authorization allows critical functions and reports that do not contain their own authorization checks to be executed The specified number of users for each client have the checked authorization
Client No of Users Having This Authorization No of Valid Users Rating
001 2 3
400 147 160
Authorization objects
Object 1 S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2 S_PROGRAM with P_ACTION=SUBMIT P_GROUP=
Confidential Security 2639
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
4312 Required Parameter Settings
As a prerequisite for running the downward-compatible kernel the following parameters need to be set
Parameter Description Current Value Recommendation
rslgnew_layout System Log Format 9
432 Issues with current SAP Kernel
Your SAP kernel release may encounter serious problems
SAP tests all SAP kernels that are released However your patch level has been found to be unstable in certain cases and is therefore not recommended For more information see the release information for each SAP kernel patch on SAP Service Marketplace
For more information about issues concerning your current SAP kernel see the SAP Notes in the table below
Recommendation If the SAP kernel shipped with the latest Support Package stack of your product has the same issue as listed below install a more recent SAP kernel available in the Patches section of SAP Service Marketplace
SAP Note Short Text Risk
1132350 Incomplete update records
1150058 Incomplete update records
1223994 Composite SAP note Incomplete update records
433 Additional Remarks
SAP releases Support Package stacks (including SAP kernel patches) on a regular basis for most products (generally 2ndash4 times a year) We recommend that you base your software maintenance strategy on these stacks
You should only consider using a more recent SAP kernel patch than that shipped with the latest Support Package Stack for your product if specific errors occur
For more information see SAP Service Marketplace at httpssupportsapcomsoftwarepatchesstackshtml (SAP SupportPackage Stack information) and httpssupportsapcompatches (patchinformation)
Confidential Software Configuration For PRD 1039
SAPreg GoingLivetrade Check - Verification Session 06082015
5 Service Preparation and Data Quality of PRD
SAP ERP system PRD is not fully prepared for delivery of future remote services
Rating Check Performed
Service Data Quality
ST-PI and ST-API Plug-Ins
Service Preparation Check (RTCCTOOL)
Service Data Control Center
Hardware Utilization Data
In preparation for SAP services ensure that connections collectors and service tools are up to date These functionalities are explained in SAP Notes httpsservicesapcomsapsupportnotes91488[91488] and 1172939
51 Service Data Quality
For this service data of high importance is missing The service data is collected by the Service Data Control Center (SDCCN) or read from the Solution Managers BW or Configuration and Change Database (CCDB) This section comprehensively shows issues with the data quality and provides hints on how to resolve them
LEGEND FOR PRIORITY IN SERVICE DATA QUALITY
Prio Explanation Impact of Missing or Erroneous Data
Overall important data are missing Detecting a critical situation may fail Report cannot be rated green or yellow
Data for an important chapter are missing Some issues may not be detected Report cannot be rated green
Some important check could not be processed The report can be rated green nevertheless
Only checks of minor importance are affected
An optional check was skipped
511 Quality of Data in Service Data Control Center (SDCC)
QUALITY OF SERVICE DATA IN ST-PI
Prio Report Area affected Details and Related ST-PI Logical Function SAP Note
System Monitoring of Server (host) sap1r3p
During hardware data collection no SAPOSCOL was found It is either not running or not accessible ST-PI function EWA_GET_HARDWARE_INFO used in section Hardware Capacity
1309499
512 Quality of Service Data in Solution Manager Diagnostics - BW
Prio Report Area affected
Details and Related Infocube SAP Note
Workload of ABAP System PRD
Reading performance data from BW returned neither data nor an error code A timeout may have occurred Infocube 0CCMSMTPH used in section Workload Overview PRD
1332428
Confidential Service Preparation and Data Quality of PRD 1139
SAPreg GoingLivetrade Check - Verification Session 06082015
52 ST-PI and ST-API Plug-Ins
The table below shows the service plug-ins implemented and their releases and patch levels These recommendations are derived from report RTCCTOOL For more information about RTCCTOOL see SAP Note 309711
Rating Plug-In Release Patch Level Release Rec Patch Level Rec
ST-API 01L_ECC600 0 01R_700 1
ST-PI 2008_1_700 0 2008_1_700 11
Recommendation The Service Tools for Applications Plug-In (ST-API) is not up-to-date For more information see SAP Note 69455 The Solution Tools Plug-In (ST-PI) is not up-to-date For more information see SAP Note 539977
53 Service Preparation Check (RTCCTOOL)
Before we can ship any services the latest version of the SAP Service tools must be implemented in your system Report RTCCTOOL was last run on 06082015 During the check the tool detected issues for which a RED rating was set
Overall Status SAP Note Title Tool Status Manual Status
69455 [Note 69455] Addon ST-API 01R_700
69455 [Note 69455] ST-API 01R_700 Support Package 1
539977 [Note 539977] ST-PI 2008_1_700 Support Package 11
69455 [Note 69455] Proc after addon impl
539977 [Note 539977] Addon ST-PI 2008_1_700
539977 Note 1300023 for ST-PI
539977 Note 1312413 for ST-PI
539977 Note 1293657 for ST-PI
12103 [Note 12103] Collectors and TCOLL
207223 [Note 207223] EWAlert setup
Recommendation [Note 69455] Addon ST-API 01R_700 Servicetools for Applications Plug-In for NetWeaver 04s Basis 70x From httpsupportsapcomsupporttools- gtST-API-gtInstallationsampUpgrades download the installation ST-API 01R_700 Upload to tx SAINT and install as per note 69455 Then restart report RTCCTOOL and choose List-gtRefresh from SAPNet
[Note 69455] ST-API 01R_700 Support Package 1 Addon supportpackage level 1 for ST-API 01R_700 for NetWeaver 04s Basis 70x From httpsupportsapcomsupporttools- gtST-API-gtSupport packages-gtST-API 01R_700 download patches up to SAPKITAB7N For basis gt=700 use the Maintenance optimizer to release the download Upload from frontend to transaction SPAM define a queue and import
[Note 539977] ST-PI 2008_1_700 Support Package 11 Addon supportpackage level 11 for ST-PI 2008_1_700 for 700 [patches up to level 11 for Basis tools for services] Open httpsupportsapcomsupporttools- gtST-PI supportpk-gt ST-PI2008_1_700 Add patch SAPKITLRDL (and predecessors if not yet implemented) download basket Release basket via Maintenance optimizer Upload from frontend into transaction SPAM define a queue and import the queue
54 Performance DB (ST03 ST06)
Analysis of ST06 and history data indicate some problems with SAPOSCOL Check SAPOSCOL and see SAP Note 1309499
Confidential Service Preparation and Data Quality of PRD 1239
SAPreg GoingLivetrade Check - Verification Session 06082015
55 Hardware Utilization Data
Host Operating System Performance Data
sap1r3p OS not detected OK
Hardware capacity checks could not be run successfully due to missing data See SAP Note 1309499
Confidential Service Preparation and Data Quality of PRD 1339
SAPreg GoingLivetrade Check - Verification Session 06082015
6 Hardware Capacity
We have checked your system for potential CPU bottlenecks and found that the hardware is sufficient for the current workload
Note Hardware Capacity evaluation is based on hosts for which data is least partially available
61 Overview System PRD
General This analysis focuses on the workload during the peak working hours (9-11 13) and is based on the hourly averages collected by SAPOSCOL For information about the definition of peak working hours see SAP Note 1251291
CPU If the average CPU load exceeds 75 temporary CPU bottlenecks are likely to occur An average CPU load of more than 90 is a strong indicator of a CPU bottleneck
Memory If your hardware cannot handle the maximum memory consumption this causes a memory bottleneck in your SAP system that can impair performance The paging rating depends on the ratio of paging activity to physical memory A ratio exceeding 25 indicates high memory usage (if Java has been detected 0 ) and values above 50 (Java 10 ) demonstrate a main memory bottleneck
Server Max CPU load [] Date Rating RAM [MB]
sap1r3p 37 21072015 0
Note In case of virtualization or IaaS scenarios (eg IBM PowerVM VMware Amazon AWS ) it might be that for some hosts the CPU rating is yellow or red although the utilization value is quite low In this case the relevant host could not use maximum usable capacity due to a resource shortage within the virtualized infrastructure (eg IBM PowerVM Shared Pool CPU utilization)
Confidential Hardware Capacity 1439
SAPreg GoingLivetrade Check - Verification Session 06082015
7 Workload of System PRD
This chart displays the main task types and indicates how their workload is distributed in the system The table below lists the detailed KPIs
RESPONSE TIME COMPONENTS IN HOURS
Task Type Response Time Wait Time CPU Time DB Time GUI Time
DIALOG 55 00 20 20 07
BATCH 51 00 24 26 00
RFC 29 00 04 03 00
UPDATE 04 00 01 02 00
Others 02 00 00 00 00
71 Workload By Users
User activity is measured in the workload monitor Only users of at least medium activity are counted as active users
Users Low Activity Medium Activity High Activity Total Users
dialog steps per week 1 to 399 400 to 4799 4800 or more
measured in system 82 29 1 112
72 Workload Distribution PRD
The performance of your system was analyzed with respect to the workload distribution We did not detect any major problems that could affect the performance of your SAP system
721 Workload by Application Module
Confidential Workload of System PRD 1539
SAPreg GoingLivetrade Check - Verification Session 06082015
The following diagrams show how each application module contributes to the total system workload Two workload aspects are shown
- CPU time total CPU load on all servers in the system landscape
- Database time total database load generated by the application
All programs that are not classified in the SAP Application Hierarchy (transaction SE81) are summarized in the Un-Assigned category Customer programs industry solutions and third-party add-on developments fall into this category
722 DB Load Profile
Confidential Workload of System PRD 1639
SAPreg GoingLivetrade Check - Verification Session 06082015
The number of work processes creating database load in parallel is not significantly high
The following diagram shows the DB load caused by dialog RFC HTTP(S) and background tasks over different time frames The data provided in the diagram represents the average number of database processes occupied by each task type in the database during the specified time frames These statistics are calculated as a weekly average the average values over six working days with a unit of one hour Periods between 0000-0600 and 2100-2400 contain an average value per hour as these are not core business hours You can enable 24-hour monitoring by implementing SAP Note 17750 With 24-hour monitoring the time profile returns the workload of the system or application server on an hourly basis rather than returning an average value per hour for the periods 0000ndash0600 and 2100ndash2400 By comparing the load profiles for dialog and background activity you can get an overview of the volume of background activity during online working hours
Confidential Workload of System PRD 1739
SAPreg GoingLivetrade Check - Verification Session 06082015
8 Performance Overview PRD
The performance of your system was analyzed with respect to the average response times and total workload We did not detect any major problems that could affect the performance of your system
Rating Check
Performance Evaluation
The following table shows the average response times for various task types
AVERAGES OF RESPONSE TIME COMPONENTS IN MS
Task type Dialog Steps Response Time CPU Time Wait Time Load Time DB Time GUI Time
DIALOG 27390 7350 2584 56 60 2679 936
RFC 7535 13832 1702 33 53 1582 00
UPDATE 3114 4477 1392 12 97 2394 00
UPDATE2 2004 2029 665 12 41 878 00
BATCH 8357 21896 10330 07 105 11007 00
SPOOL 1221 5755 262 58 08 188 00
81 Performance Evaluation
The measured times are compared against reference times to provide a rating - If the number of dialog steps in an hour is less than 1000 this hour is not considered - If the total number of transaction steps is less than 20000 the rating for the task is not performed (indicated by a gray icon in the table) - RED if at least three time ranges are rated RED - YELLOW if two time ranges are rated RED or at least three time ranges are rated YELLOW
The table below shows that no problem is expected on the application or database servers
Task Steps Application Server Performance Database Server Performance
Dia 27389
Upd 3114
HTTP 0
HTTPS 0
The ratings in the table above are determined by comparisons against the reference table below If the dialog response times are very poor it will cause a RED rating for the entire check
Task Reference for Avg Response Time (ms) Yellow Rating
Reference for Avg Response Time (ms) Red Rating
Reference for Avg DB time (ms) Yellow Rating
Reference for Avg DB time (ms) Red Rating
Dia 1200 3600 600 1800
Upd 2400 3600 1200 1800
HTTP 1200 3600 600 1800
HTTPS 1200 3600 600 1800
Confidential Performance Overview PRD 1839
SAPreg GoingLivetrade Check - Verification Session 06082015
82 Transaction Profile Check
The following tables show the response times and the number of dialog steps for the transactions that cause the heaviest workload in your system
821 Transactions by Total Workload
The following tables list the activities with the highest contribution to the total workload
WORKLOAD BY TRANSACTION (DIALOG HTTP(S)WS-HTTP )
Transaction Type Dialog Steps Total Resp Time in
Avg Resp Time in ms
Avg CPU Time in ms
Avg DB Time in ms
Avg GUI Time in ms
VL71 DIA 83 61 297185 178782 263658 71
FBL5N DIA 2919 33 4626 1991 1330 242
VA01 DIA 2034 32 6258 2092 1164 1764
VA02 DIA 2183 29 5306 2194 1287 639
ZSDP0023 DIA 365 22 24427 2144 19871 2116
ZWMSCP01 DIA 130 21 65254 13125 10103 649
ME22 DIA 167 17 41818 22914 3250 07
VT01N DIA 235 15 25864 13412 1976 2443
SESSION_MANAGER DIA 1078 14 5202 663 844 2716
VKM1 DIA 478 12 9796 3358 3746 86
43 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
WORKLOAD BY TRANSACTION (BATCH)
Transaction Dialog Steps Total Resp Time in
Total Resp Time in s
Total CPU Time in s
Total DB Time in s
ZFIP0102 156 109 44040 25240 42295
ZFIP0115 260 97 39320 21180 23386
ZSD_CREATE_ORDER_BY_REF 125 75 30160 13100 7000
ZWMS_FILE_MANAGER2 784 37 14820 930 612
ZSDP0031 8 33 13260 6780 2783
ZFIP0105 390 16 6560 4350 383
ZFIP0106 78 15 6010 4140 5722
RSBTCRTE 2412 12 4820 1240 336
ZSDP0063 2 10 4050 2130 1318
(BATCH) 3197 09 3750 810 506
392 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
822 Transactions by DB Load
The following transaction profiles list the transactions that have the greatest share in the database load sorted by percentage of total database access times
DATABASE LOAD BY TRANSACTIONS (DIALOG HTTP(S) )
Confidential Performance Overview PRD 1939
SAPreg GoingLivetrade Check - Verification Session 06082015
Transaction Type Dialog Steps Total DB Time in Avg DB Time in ms
VL71 DIA 83 127 263658
ZSDP0023 DIA 365 42 19871
FBL5N DIA 2919 22 1330
VA02 DIA 2183 16 1287
ZVC2 DIA 1360 15 1953
ZMMP0008 DIA 64 14 37798
VA01 DIA 2034 14 1164
ZSDP0013 DIA 47 12 43947
VKM1 DIA 478 10 3746
ZWMSCP01 DIA 130 08 10103
91 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
DATABASE LOAD BY TRANSACTIONS (BATCH)
Transaction Dialog Steps Total DB Time in Total DB Time in s
ZFIP0102 156 245 42300
ZFIP0115 260 135 23390
ZSD_CREATE_ORDER_BY_REF 125 41 7000
ZFIP0106 78 33 5720
ZSDP0031 8 16 2780
RSDB4UPD 2 12 2070
ZFII0002 1 09 1580
ZSDP0063 2 08 1320
ZSD_GENERATE_INFO_CONDITIONS 7 08 1320
ZFIP0101 263 07 1290
502 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
83 RFC Load by Initiating Action
The load in task type RFC is shown In the workload monitor this information is shown as Load from External Systems The calling system can be an application server of the system itself or any external system using the RFC interface The Initial Action is the calling program initiating the RFC The total response time for each initial action is shown as an absolute value and as a percentage compared to the total RFC load considered in this table The average times (per dialog step) are shown in milliseconds [ms] Calls from external systems are shown if they account for at least 8h or 5 of the total RFC load Local calls are shown if they account for at least 24h or 20 of the total RFC load
LOAD OVERVIEW
Initial System Load [s] Load
Local system PRD 4450 9957
Sum of external systems 19 043
RFC load (sum of above) 4469 10000
Confidential Performance Overview PRD 2039
SAPreg GoingLivetrade Check - Verification Session 06082015
Initial System Load [s] Load
RFC load in Performance Overview 10422 23321
Load of all task types in Performance Overview 51694 115668
TOP 20 RFC CALLS FROM LOCAL SYSTEM - AVERAGE TIMES [MS]
Initial System
Initial Action Total Resp
Time in s
of RFC Load
Avg Response
Time
Avg CPU Time
Avg DB Time
Avg Roll Wait Time
PRD RK2A1000_POST 892 1996 13097 147 87 20
PRD VF01 491 1099 25854 8767 14305 23
PRD VA01 468 1047 8402 170 543 14
PRD SAPLARFC 256 574 10505 208 305 17
PRD CA_QUEUE_ENTRY_BCS============CP 226 505 4628 1068 1398 251
PRD VA02 178 399 6343 1215 1490 14
PRD VL71 136 304 8330 698 330 118
PRD SAP_COLLECTOR_FOR_PERFMONITOR 132 295 33749 13108 7127 188
PRD VL02N 127 284 11757 2595 7164 18
PRD VL10X 96 215 4341 553 433 10
PRD VKM1 70 157 3532 813 930 35
PRD ZSDP0049 55 124 61422 1167 1553 64
PRD STMS 52 116 18555 1911 2091 77
PRD ZP01_FROM_ZP05_944988 52 115 171827 3233 1053 03
PRD ZSDP0010 45 100 74582 31983 32785 10
PRD XD02 43 097 403 116 126 05
PRD FB1D 42 093 1999 406 1263 06
PRD FBL5N 41 091 8700 630 866 14
PRD ZP01_FROM_ZP05_942398 38 086 63795 1867 2482 65
PRD FBZ5 32 071 319430 400 510 00
Confidential Performance Overview PRD 2139
SAPreg GoingLivetrade Check - Verification Session 06082015
9 SAP System Operating PRD
The daily operation of your system was analyzed We detected some problems that may impair system operation and stability
91 Availability based on Collector Protocols
A value of 100 means that the collector was available all day Available in the context of this report means that at least one SAP instance was running If the SAP collector was not running correctly the values in the table and graphics may be incorrect To check these logs call transaction ST03N (expert mode) and choose Collector and Performance DB -gt Performance Monitor Collector -gt Log
This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR that runs every hour The job does NOT check availability it carries out only general system tasks such as collecting and aggregating SAP performance data for all serversinstances The log does not contain any direct information about availability it contains only information about the status of the hourly statistical data collection
As of SAP Basis 640 system availability information is available in the CCMS (Computing Center Management System) of an SAP System in Service Level Reporting of SAP Solution Manager
This function is provided by the relevant Solution Manager Support Packages as an advanced development For more information refer to SAP Note 944496 which also lists the prerequisites that must be fulfilled before implementation can take place
92 Update Errors
In a system running under normal conditions only a small number of update errors should occur To set the rating for this check the number of active users is also taken into consideration
We did not detect any problems
Confidential SAP System Operating PRD 2239
SAPreg GoingLivetrade Check - Verification Session 06082015
93 Table Reorganization
The largest tables andor rapidly growing tables of system PRDwere checked No standard SAP recommendations for the applicable data volume management were found
94 Program Errors (ABAP Dumps)
50 ABAP dumps have been recorded in your system in the period 30072015 to 05082015 ABAP dumps are generally deleted after 7 days by default To view the ABAP dumps in your system call transaction ST22 and choose Selection Then select a timeframe
Date Number of Dumps
30072015 19
31072015 15
01082015 0
02082015 1
03082015 4
04082015 5
05082015 6
Name of Runtime Error Dumps Server (eg) User (eg) Date (eg) Time (eg)
TIME_OUT 1 SAP1R3P_PRD_00 EMOROCHO 30072015 104804
CALL_FUNCTION_SINGLE_LOGIN_REJ 2 SAP1R3P_PRD_00 SAPSYS 30072015 170339
DYNPRO_FIELD_CONVERSION 6 SAP1R3P_PRD_00 LORTEGA 31072015 172039
DBIF_RSQL_INVALID_RSQL 5 SAP1R3P_PRD_00 PREDROBAN 02082015 060047
CALL_FUNCTION_SEND_ERROR 2 SAP1R3P_PRD_00 JPVEND 03082015 073533
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY 3 SAP1R3P_PRD_00 LORTEGA 04082015 123208
RAISE_EXCEPTION 14 SAP1R3P_PRD_00 KCASTRO 05082015 094209
CONVT_NO_NUMBER 1 SAP1R3P_PRD_00 KABARCA 05082015 143511
UNCAUGHT_EXCEPTION 1 SAP1R3P_PRD_00 CBANCHON 05082015 150325
TSV_TNEW_PAGE_ALLOC_FAILED 5 SAP1R3P_PRD_00 FLUCAS 05082015 190338
MESSAGE_TYPE_X 10 SAP1R3P_PRD_00 INTERFASES 05082015 210129
It is important that you monitor ABAP dumps using transaction ST22 on a regular basis If ABAP dumps occur you should determine the cause as soon as possible Based on our analysis we found several ABAP dumps that need your attention Evaluate and resolve the above dumps If you cannot find a solution send a customer message to SAP to request support
Confidential SAP System Operating PRD 2339
SAPreg GoingLivetrade Check - Verification Session 06082015
10 Security
Critical security issues were found in your system
See the information in the following sections
Rating Check
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
101 ABAP Stack of PRD
1011 System Recommendations (ABAP)
System Recommendations is not used at all
Recommendation SAP strongly recommends applying important security fixes as soon as possible The System Recommendations application provides a detailed recommendation regarding which SAP security notes (ABAP and non-ABAP) should be implemented based on the actual status of the system and the notes already implemented This is a mandatory prerequisite for setting up a strong security patch process For more information go to httpservicesapcomsysrec
1012 Default Passwords of Standard Users
Standard users have default passwords
Recommendation Run report RSUSR003 to check the usage of default passwords by standard users
Ensure that users SAP (must exist in all clients) SAPCPIC and EARLYWATCH have non-default passwords in all clients For more information see Protecting Standard Users either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
Make sure that the standard password for user TMSADM has been changed in client 000 and delete this user in any other client SAP Note httpsservicesapcomsapsupportnotes1414256[1414256] describes a support tool to change the password of user TMSADM in all systems of the transport domain SAP Note httpsservicesapcomsapsupportnotes1552894[1552894] shows how to update the report RSUSR003 to show the status of user TMSADM
1013 ABAP Password Policy
If password login is allowed for specific instances only the password policy is checked only for these instances
10131 Password Complexity
PARAMETER LOGINMIN_PASSWORD_LNG
Confidential Security 2439
SAPreg GoingLivetrade Check - Verification Session 06082015
Rating Instance Current Value(s) Recommended Value
sap1r3p_PRD_00 6 8
The current system settings allow a password length of fewer than 8 characters This allows weak passwords Attackers may successfully recover these passwords and gain unauthorized access to the system
Recommendation Assign a minimum value of 8 to the profile parameter loginmin_password_lng
In addition SAP provides options to enforce complex passwords Find the current settings of the corresponding profile parameters in the following table
Parameter Instance Current Value(s)
loginmin_password_digits sap1r3p_PRD_00 0
loginmin_password_letters sap1r3p_PRD_00 0
loginmin_password_lowercase sap1r3p_PRD_00 0
loginmin_password_uppercase sap1r3p_PRD_00 0
loginmin_password_specials sap1r3p_PRD_00 0
Recommendation Enforce a minimum of 3 independent character categories using the corresponding profile parameters For more information see SAP Note httpsservicesapcomsapsupportnotes862989[862989] and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
1014 Gateway and Message Server Security
10141 Kernel Patch Level
Rating Kernel Release Current Kernel Patch Level Minimal Required Kernel Patch Level
700 135 260
To enable certain gateway security functionality a minimum kernel patch level is required Your system does not currently meet this requirement
Recommendation Update the kernel of your system to the newest kernel patch level available Update to a kernel patch level equal to or higher than the minimum required kernel patch level specified above For more information see SAP Note 1298433
10142 Gateway Security
Gateway Security Properties
The parameter GWREG_NO_CONN_INFO controls the activation of certain security properties of the SAP gateway It is defined as a bit mask with one bit per property
SAP Note httpsservicesapcomsapsupportnotes1298433[1298433] ldquoBypassing security in reginfo amp secinfordquo is not activated in your system The bit mask value for bit 1 is not set
Recommendation Enable the missing property by adding the bitmask value to the current value of GWREG_NO_CONN_INFO For more information about GWREG_NO_CONN_INFO see SAP Note 1444282
Confidential Security 2539
SAPreg GoingLivetrade Check - Verification Session 06082015
1015 Users with Critical Authorizations
For more information about the following check results see SAP Note 863362
Recommendation Depending on your environment review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations You can use the User Information System (transaction SUIM) to check the results For each check you can review the roles or profiles that include the authorization objects listed in the corresponding section
10151 Users Authorized to Start all Reports
This authorization allows critical functions and reports that do not contain their own authorization checks to be executed The specified number of users for each client have the checked authorization
Client No of Users Having This Authorization No of Valid Users Rating
001 2 3
400 147 160
Authorization objects
Object 1 S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2 S_PROGRAM with P_ACTION=SUBMIT P_GROUP=
Confidential Security 2639
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
5 Service Preparation and Data Quality of PRD
SAP ERP system PRD is not fully prepared for delivery of future remote services
Rating Check Performed
Service Data Quality
ST-PI and ST-API Plug-Ins
Service Preparation Check (RTCCTOOL)
Service Data Control Center
Hardware Utilization Data
In preparation for SAP services ensure that connections collectors and service tools are up to date These functionalities are explained in SAP Notes httpsservicesapcomsapsupportnotes91488[91488] and 1172939
51 Service Data Quality
For this service data of high importance is missing The service data is collected by the Service Data Control Center (SDCCN) or read from the Solution Managers BW or Configuration and Change Database (CCDB) This section comprehensively shows issues with the data quality and provides hints on how to resolve them
LEGEND FOR PRIORITY IN SERVICE DATA QUALITY
Prio Explanation Impact of Missing or Erroneous Data
Overall important data are missing Detecting a critical situation may fail Report cannot be rated green or yellow
Data for an important chapter are missing Some issues may not be detected Report cannot be rated green
Some important check could not be processed The report can be rated green nevertheless
Only checks of minor importance are affected
An optional check was skipped
511 Quality of Data in Service Data Control Center (SDCC)
QUALITY OF SERVICE DATA IN ST-PI
Prio Report Area affected Details and Related ST-PI Logical Function SAP Note
System Monitoring of Server (host) sap1r3p
During hardware data collection no SAPOSCOL was found It is either not running or not accessible ST-PI function EWA_GET_HARDWARE_INFO used in section Hardware Capacity
1309499
512 Quality of Service Data in Solution Manager Diagnostics - BW
Prio Report Area affected
Details and Related Infocube SAP Note
Workload of ABAP System PRD
Reading performance data from BW returned neither data nor an error code A timeout may have occurred Infocube 0CCMSMTPH used in section Workload Overview PRD
1332428
Confidential Service Preparation and Data Quality of PRD 1139
SAPreg GoingLivetrade Check - Verification Session 06082015
52 ST-PI and ST-API Plug-Ins
The table below shows the service plug-ins implemented and their releases and patch levels These recommendations are derived from report RTCCTOOL For more information about RTCCTOOL see SAP Note 309711
Rating Plug-In Release Patch Level Release Rec Patch Level Rec
ST-API 01L_ECC600 0 01R_700 1
ST-PI 2008_1_700 0 2008_1_700 11
Recommendation The Service Tools for Applications Plug-In (ST-API) is not up-to-date For more information see SAP Note 69455 The Solution Tools Plug-In (ST-PI) is not up-to-date For more information see SAP Note 539977
53 Service Preparation Check (RTCCTOOL)
Before we can ship any services the latest version of the SAP Service tools must be implemented in your system Report RTCCTOOL was last run on 06082015 During the check the tool detected issues for which a RED rating was set
Overall Status SAP Note Title Tool Status Manual Status
69455 [Note 69455] Addon ST-API 01R_700
69455 [Note 69455] ST-API 01R_700 Support Package 1
539977 [Note 539977] ST-PI 2008_1_700 Support Package 11
69455 [Note 69455] Proc after addon impl
539977 [Note 539977] Addon ST-PI 2008_1_700
539977 Note 1300023 for ST-PI
539977 Note 1312413 for ST-PI
539977 Note 1293657 for ST-PI
12103 [Note 12103] Collectors and TCOLL
207223 [Note 207223] EWAlert setup
Recommendation [Note 69455] Addon ST-API 01R_700 Servicetools for Applications Plug-In for NetWeaver 04s Basis 70x From httpsupportsapcomsupporttools- gtST-API-gtInstallationsampUpgrades download the installation ST-API 01R_700 Upload to tx SAINT and install as per note 69455 Then restart report RTCCTOOL and choose List-gtRefresh from SAPNet
[Note 69455] ST-API 01R_700 Support Package 1 Addon supportpackage level 1 for ST-API 01R_700 for NetWeaver 04s Basis 70x From httpsupportsapcomsupporttools- gtST-API-gtSupport packages-gtST-API 01R_700 download patches up to SAPKITAB7N For basis gt=700 use the Maintenance optimizer to release the download Upload from frontend to transaction SPAM define a queue and import
[Note 539977] ST-PI 2008_1_700 Support Package 11 Addon supportpackage level 11 for ST-PI 2008_1_700 for 700 [patches up to level 11 for Basis tools for services] Open httpsupportsapcomsupporttools- gtST-PI supportpk-gt ST-PI2008_1_700 Add patch SAPKITLRDL (and predecessors if not yet implemented) download basket Release basket via Maintenance optimizer Upload from frontend into transaction SPAM define a queue and import the queue
54 Performance DB (ST03 ST06)
Analysis of ST06 and history data indicate some problems with SAPOSCOL Check SAPOSCOL and see SAP Note 1309499
Confidential Service Preparation and Data Quality of PRD 1239
SAPreg GoingLivetrade Check - Verification Session 06082015
55 Hardware Utilization Data
Host Operating System Performance Data
sap1r3p OS not detected OK
Hardware capacity checks could not be run successfully due to missing data See SAP Note 1309499
Confidential Service Preparation and Data Quality of PRD 1339
SAPreg GoingLivetrade Check - Verification Session 06082015
6 Hardware Capacity
We have checked your system for potential CPU bottlenecks and found that the hardware is sufficient for the current workload
Note Hardware Capacity evaluation is based on hosts for which data is least partially available
61 Overview System PRD
General This analysis focuses on the workload during the peak working hours (9-11 13) and is based on the hourly averages collected by SAPOSCOL For information about the definition of peak working hours see SAP Note 1251291
CPU If the average CPU load exceeds 75 temporary CPU bottlenecks are likely to occur An average CPU load of more than 90 is a strong indicator of a CPU bottleneck
Memory If your hardware cannot handle the maximum memory consumption this causes a memory bottleneck in your SAP system that can impair performance The paging rating depends on the ratio of paging activity to physical memory A ratio exceeding 25 indicates high memory usage (if Java has been detected 0 ) and values above 50 (Java 10 ) demonstrate a main memory bottleneck
Server Max CPU load [] Date Rating RAM [MB]
sap1r3p 37 21072015 0
Note In case of virtualization or IaaS scenarios (eg IBM PowerVM VMware Amazon AWS ) it might be that for some hosts the CPU rating is yellow or red although the utilization value is quite low In this case the relevant host could not use maximum usable capacity due to a resource shortage within the virtualized infrastructure (eg IBM PowerVM Shared Pool CPU utilization)
Confidential Hardware Capacity 1439
SAPreg GoingLivetrade Check - Verification Session 06082015
7 Workload of System PRD
This chart displays the main task types and indicates how their workload is distributed in the system The table below lists the detailed KPIs
RESPONSE TIME COMPONENTS IN HOURS
Task Type Response Time Wait Time CPU Time DB Time GUI Time
DIALOG 55 00 20 20 07
BATCH 51 00 24 26 00
RFC 29 00 04 03 00
UPDATE 04 00 01 02 00
Others 02 00 00 00 00
71 Workload By Users
User activity is measured in the workload monitor Only users of at least medium activity are counted as active users
Users Low Activity Medium Activity High Activity Total Users
dialog steps per week 1 to 399 400 to 4799 4800 or more
measured in system 82 29 1 112
72 Workload Distribution PRD
The performance of your system was analyzed with respect to the workload distribution We did not detect any major problems that could affect the performance of your SAP system
721 Workload by Application Module
Confidential Workload of System PRD 1539
SAPreg GoingLivetrade Check - Verification Session 06082015
The following diagrams show how each application module contributes to the total system workload Two workload aspects are shown
- CPU time total CPU load on all servers in the system landscape
- Database time total database load generated by the application
All programs that are not classified in the SAP Application Hierarchy (transaction SE81) are summarized in the Un-Assigned category Customer programs industry solutions and third-party add-on developments fall into this category
722 DB Load Profile
Confidential Workload of System PRD 1639
SAPreg GoingLivetrade Check - Verification Session 06082015
The number of work processes creating database load in parallel is not significantly high
The following diagram shows the DB load caused by dialog RFC HTTP(S) and background tasks over different time frames The data provided in the diagram represents the average number of database processes occupied by each task type in the database during the specified time frames These statistics are calculated as a weekly average the average values over six working days with a unit of one hour Periods between 0000-0600 and 2100-2400 contain an average value per hour as these are not core business hours You can enable 24-hour monitoring by implementing SAP Note 17750 With 24-hour monitoring the time profile returns the workload of the system or application server on an hourly basis rather than returning an average value per hour for the periods 0000ndash0600 and 2100ndash2400 By comparing the load profiles for dialog and background activity you can get an overview of the volume of background activity during online working hours
Confidential Workload of System PRD 1739
SAPreg GoingLivetrade Check - Verification Session 06082015
8 Performance Overview PRD
The performance of your system was analyzed with respect to the average response times and total workload We did not detect any major problems that could affect the performance of your system
Rating Check
Performance Evaluation
The following table shows the average response times for various task types
AVERAGES OF RESPONSE TIME COMPONENTS IN MS
Task type Dialog Steps Response Time CPU Time Wait Time Load Time DB Time GUI Time
DIALOG 27390 7350 2584 56 60 2679 936
RFC 7535 13832 1702 33 53 1582 00
UPDATE 3114 4477 1392 12 97 2394 00
UPDATE2 2004 2029 665 12 41 878 00
BATCH 8357 21896 10330 07 105 11007 00
SPOOL 1221 5755 262 58 08 188 00
81 Performance Evaluation
The measured times are compared against reference times to provide a rating - If the number of dialog steps in an hour is less than 1000 this hour is not considered - If the total number of transaction steps is less than 20000 the rating for the task is not performed (indicated by a gray icon in the table) - RED if at least three time ranges are rated RED - YELLOW if two time ranges are rated RED or at least three time ranges are rated YELLOW
The table below shows that no problem is expected on the application or database servers
Task Steps Application Server Performance Database Server Performance
Dia 27389
Upd 3114
HTTP 0
HTTPS 0
The ratings in the table above are determined by comparisons against the reference table below If the dialog response times are very poor it will cause a RED rating for the entire check
Task Reference for Avg Response Time (ms) Yellow Rating
Reference for Avg Response Time (ms) Red Rating
Reference for Avg DB time (ms) Yellow Rating
Reference for Avg DB time (ms) Red Rating
Dia 1200 3600 600 1800
Upd 2400 3600 1200 1800
HTTP 1200 3600 600 1800
HTTPS 1200 3600 600 1800
Confidential Performance Overview PRD 1839
SAPreg GoingLivetrade Check - Verification Session 06082015
82 Transaction Profile Check
The following tables show the response times and the number of dialog steps for the transactions that cause the heaviest workload in your system
821 Transactions by Total Workload
The following tables list the activities with the highest contribution to the total workload
WORKLOAD BY TRANSACTION (DIALOG HTTP(S)WS-HTTP )
Transaction Type Dialog Steps Total Resp Time in
Avg Resp Time in ms
Avg CPU Time in ms
Avg DB Time in ms
Avg GUI Time in ms
VL71 DIA 83 61 297185 178782 263658 71
FBL5N DIA 2919 33 4626 1991 1330 242
VA01 DIA 2034 32 6258 2092 1164 1764
VA02 DIA 2183 29 5306 2194 1287 639
ZSDP0023 DIA 365 22 24427 2144 19871 2116
ZWMSCP01 DIA 130 21 65254 13125 10103 649
ME22 DIA 167 17 41818 22914 3250 07
VT01N DIA 235 15 25864 13412 1976 2443
SESSION_MANAGER DIA 1078 14 5202 663 844 2716
VKM1 DIA 478 12 9796 3358 3746 86
43 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
WORKLOAD BY TRANSACTION (BATCH)
Transaction Dialog Steps Total Resp Time in
Total Resp Time in s
Total CPU Time in s
Total DB Time in s
ZFIP0102 156 109 44040 25240 42295
ZFIP0115 260 97 39320 21180 23386
ZSD_CREATE_ORDER_BY_REF 125 75 30160 13100 7000
ZWMS_FILE_MANAGER2 784 37 14820 930 612
ZSDP0031 8 33 13260 6780 2783
ZFIP0105 390 16 6560 4350 383
ZFIP0106 78 15 6010 4140 5722
RSBTCRTE 2412 12 4820 1240 336
ZSDP0063 2 10 4050 2130 1318
(BATCH) 3197 09 3750 810 506
392 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
822 Transactions by DB Load
The following transaction profiles list the transactions that have the greatest share in the database load sorted by percentage of total database access times
DATABASE LOAD BY TRANSACTIONS (DIALOG HTTP(S) )
Confidential Performance Overview PRD 1939
SAPreg GoingLivetrade Check - Verification Session 06082015
Transaction Type Dialog Steps Total DB Time in Avg DB Time in ms
VL71 DIA 83 127 263658
ZSDP0023 DIA 365 42 19871
FBL5N DIA 2919 22 1330
VA02 DIA 2183 16 1287
ZVC2 DIA 1360 15 1953
ZMMP0008 DIA 64 14 37798
VA01 DIA 2034 14 1164
ZSDP0013 DIA 47 12 43947
VKM1 DIA 478 10 3746
ZWMSCP01 DIA 130 08 10103
91 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
DATABASE LOAD BY TRANSACTIONS (BATCH)
Transaction Dialog Steps Total DB Time in Total DB Time in s
ZFIP0102 156 245 42300
ZFIP0115 260 135 23390
ZSD_CREATE_ORDER_BY_REF 125 41 7000
ZFIP0106 78 33 5720
ZSDP0031 8 16 2780
RSDB4UPD 2 12 2070
ZFII0002 1 09 1580
ZSDP0063 2 08 1320
ZSD_GENERATE_INFO_CONDITIONS 7 08 1320
ZFIP0101 263 07 1290
502 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
83 RFC Load by Initiating Action
The load in task type RFC is shown In the workload monitor this information is shown as Load from External Systems The calling system can be an application server of the system itself or any external system using the RFC interface The Initial Action is the calling program initiating the RFC The total response time for each initial action is shown as an absolute value and as a percentage compared to the total RFC load considered in this table The average times (per dialog step) are shown in milliseconds [ms] Calls from external systems are shown if they account for at least 8h or 5 of the total RFC load Local calls are shown if they account for at least 24h or 20 of the total RFC load
LOAD OVERVIEW
Initial System Load [s] Load
Local system PRD 4450 9957
Sum of external systems 19 043
RFC load (sum of above) 4469 10000
Confidential Performance Overview PRD 2039
SAPreg GoingLivetrade Check - Verification Session 06082015
Initial System Load [s] Load
RFC load in Performance Overview 10422 23321
Load of all task types in Performance Overview 51694 115668
TOP 20 RFC CALLS FROM LOCAL SYSTEM - AVERAGE TIMES [MS]
Initial System
Initial Action Total Resp
Time in s
of RFC Load
Avg Response
Time
Avg CPU Time
Avg DB Time
Avg Roll Wait Time
PRD RK2A1000_POST 892 1996 13097 147 87 20
PRD VF01 491 1099 25854 8767 14305 23
PRD VA01 468 1047 8402 170 543 14
PRD SAPLARFC 256 574 10505 208 305 17
PRD CA_QUEUE_ENTRY_BCS============CP 226 505 4628 1068 1398 251
PRD VA02 178 399 6343 1215 1490 14
PRD VL71 136 304 8330 698 330 118
PRD SAP_COLLECTOR_FOR_PERFMONITOR 132 295 33749 13108 7127 188
PRD VL02N 127 284 11757 2595 7164 18
PRD VL10X 96 215 4341 553 433 10
PRD VKM1 70 157 3532 813 930 35
PRD ZSDP0049 55 124 61422 1167 1553 64
PRD STMS 52 116 18555 1911 2091 77
PRD ZP01_FROM_ZP05_944988 52 115 171827 3233 1053 03
PRD ZSDP0010 45 100 74582 31983 32785 10
PRD XD02 43 097 403 116 126 05
PRD FB1D 42 093 1999 406 1263 06
PRD FBL5N 41 091 8700 630 866 14
PRD ZP01_FROM_ZP05_942398 38 086 63795 1867 2482 65
PRD FBZ5 32 071 319430 400 510 00
Confidential Performance Overview PRD 2139
SAPreg GoingLivetrade Check - Verification Session 06082015
9 SAP System Operating PRD
The daily operation of your system was analyzed We detected some problems that may impair system operation and stability
91 Availability based on Collector Protocols
A value of 100 means that the collector was available all day Available in the context of this report means that at least one SAP instance was running If the SAP collector was not running correctly the values in the table and graphics may be incorrect To check these logs call transaction ST03N (expert mode) and choose Collector and Performance DB -gt Performance Monitor Collector -gt Log
This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR that runs every hour The job does NOT check availability it carries out only general system tasks such as collecting and aggregating SAP performance data for all serversinstances The log does not contain any direct information about availability it contains only information about the status of the hourly statistical data collection
As of SAP Basis 640 system availability information is available in the CCMS (Computing Center Management System) of an SAP System in Service Level Reporting of SAP Solution Manager
This function is provided by the relevant Solution Manager Support Packages as an advanced development For more information refer to SAP Note 944496 which also lists the prerequisites that must be fulfilled before implementation can take place
92 Update Errors
In a system running under normal conditions only a small number of update errors should occur To set the rating for this check the number of active users is also taken into consideration
We did not detect any problems
Confidential SAP System Operating PRD 2239
SAPreg GoingLivetrade Check - Verification Session 06082015
93 Table Reorganization
The largest tables andor rapidly growing tables of system PRDwere checked No standard SAP recommendations for the applicable data volume management were found
94 Program Errors (ABAP Dumps)
50 ABAP dumps have been recorded in your system in the period 30072015 to 05082015 ABAP dumps are generally deleted after 7 days by default To view the ABAP dumps in your system call transaction ST22 and choose Selection Then select a timeframe
Date Number of Dumps
30072015 19
31072015 15
01082015 0
02082015 1
03082015 4
04082015 5
05082015 6
Name of Runtime Error Dumps Server (eg) User (eg) Date (eg) Time (eg)
TIME_OUT 1 SAP1R3P_PRD_00 EMOROCHO 30072015 104804
CALL_FUNCTION_SINGLE_LOGIN_REJ 2 SAP1R3P_PRD_00 SAPSYS 30072015 170339
DYNPRO_FIELD_CONVERSION 6 SAP1R3P_PRD_00 LORTEGA 31072015 172039
DBIF_RSQL_INVALID_RSQL 5 SAP1R3P_PRD_00 PREDROBAN 02082015 060047
CALL_FUNCTION_SEND_ERROR 2 SAP1R3P_PRD_00 JPVEND 03082015 073533
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY 3 SAP1R3P_PRD_00 LORTEGA 04082015 123208
RAISE_EXCEPTION 14 SAP1R3P_PRD_00 KCASTRO 05082015 094209
CONVT_NO_NUMBER 1 SAP1R3P_PRD_00 KABARCA 05082015 143511
UNCAUGHT_EXCEPTION 1 SAP1R3P_PRD_00 CBANCHON 05082015 150325
TSV_TNEW_PAGE_ALLOC_FAILED 5 SAP1R3P_PRD_00 FLUCAS 05082015 190338
MESSAGE_TYPE_X 10 SAP1R3P_PRD_00 INTERFASES 05082015 210129
It is important that you monitor ABAP dumps using transaction ST22 on a regular basis If ABAP dumps occur you should determine the cause as soon as possible Based on our analysis we found several ABAP dumps that need your attention Evaluate and resolve the above dumps If you cannot find a solution send a customer message to SAP to request support
Confidential SAP System Operating PRD 2339
SAPreg GoingLivetrade Check - Verification Session 06082015
10 Security
Critical security issues were found in your system
See the information in the following sections
Rating Check
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
101 ABAP Stack of PRD
1011 System Recommendations (ABAP)
System Recommendations is not used at all
Recommendation SAP strongly recommends applying important security fixes as soon as possible The System Recommendations application provides a detailed recommendation regarding which SAP security notes (ABAP and non-ABAP) should be implemented based on the actual status of the system and the notes already implemented This is a mandatory prerequisite for setting up a strong security patch process For more information go to httpservicesapcomsysrec
1012 Default Passwords of Standard Users
Standard users have default passwords
Recommendation Run report RSUSR003 to check the usage of default passwords by standard users
Ensure that users SAP (must exist in all clients) SAPCPIC and EARLYWATCH have non-default passwords in all clients For more information see Protecting Standard Users either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
Make sure that the standard password for user TMSADM has been changed in client 000 and delete this user in any other client SAP Note httpsservicesapcomsapsupportnotes1414256[1414256] describes a support tool to change the password of user TMSADM in all systems of the transport domain SAP Note httpsservicesapcomsapsupportnotes1552894[1552894] shows how to update the report RSUSR003 to show the status of user TMSADM
1013 ABAP Password Policy
If password login is allowed for specific instances only the password policy is checked only for these instances
10131 Password Complexity
PARAMETER LOGINMIN_PASSWORD_LNG
Confidential Security 2439
SAPreg GoingLivetrade Check - Verification Session 06082015
Rating Instance Current Value(s) Recommended Value
sap1r3p_PRD_00 6 8
The current system settings allow a password length of fewer than 8 characters This allows weak passwords Attackers may successfully recover these passwords and gain unauthorized access to the system
Recommendation Assign a minimum value of 8 to the profile parameter loginmin_password_lng
In addition SAP provides options to enforce complex passwords Find the current settings of the corresponding profile parameters in the following table
Parameter Instance Current Value(s)
loginmin_password_digits sap1r3p_PRD_00 0
loginmin_password_letters sap1r3p_PRD_00 0
loginmin_password_lowercase sap1r3p_PRD_00 0
loginmin_password_uppercase sap1r3p_PRD_00 0
loginmin_password_specials sap1r3p_PRD_00 0
Recommendation Enforce a minimum of 3 independent character categories using the corresponding profile parameters For more information see SAP Note httpsservicesapcomsapsupportnotes862989[862989] and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
1014 Gateway and Message Server Security
10141 Kernel Patch Level
Rating Kernel Release Current Kernel Patch Level Minimal Required Kernel Patch Level
700 135 260
To enable certain gateway security functionality a minimum kernel patch level is required Your system does not currently meet this requirement
Recommendation Update the kernel of your system to the newest kernel patch level available Update to a kernel patch level equal to or higher than the minimum required kernel patch level specified above For more information see SAP Note 1298433
10142 Gateway Security
Gateway Security Properties
The parameter GWREG_NO_CONN_INFO controls the activation of certain security properties of the SAP gateway It is defined as a bit mask with one bit per property
SAP Note httpsservicesapcomsapsupportnotes1298433[1298433] ldquoBypassing security in reginfo amp secinfordquo is not activated in your system The bit mask value for bit 1 is not set
Recommendation Enable the missing property by adding the bitmask value to the current value of GWREG_NO_CONN_INFO For more information about GWREG_NO_CONN_INFO see SAP Note 1444282
Confidential Security 2539
SAPreg GoingLivetrade Check - Verification Session 06082015
1015 Users with Critical Authorizations
For more information about the following check results see SAP Note 863362
Recommendation Depending on your environment review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations You can use the User Information System (transaction SUIM) to check the results For each check you can review the roles or profiles that include the authorization objects listed in the corresponding section
10151 Users Authorized to Start all Reports
This authorization allows critical functions and reports that do not contain their own authorization checks to be executed The specified number of users for each client have the checked authorization
Client No of Users Having This Authorization No of Valid Users Rating
001 2 3
400 147 160
Authorization objects
Object 1 S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2 S_PROGRAM with P_ACTION=SUBMIT P_GROUP=
Confidential Security 2639
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
52 ST-PI and ST-API Plug-Ins
The table below shows the service plug-ins implemented and their releases and patch levels These recommendations are derived from report RTCCTOOL For more information about RTCCTOOL see SAP Note 309711
Rating Plug-In Release Patch Level Release Rec Patch Level Rec
ST-API 01L_ECC600 0 01R_700 1
ST-PI 2008_1_700 0 2008_1_700 11
Recommendation The Service Tools for Applications Plug-In (ST-API) is not up-to-date For more information see SAP Note 69455 The Solution Tools Plug-In (ST-PI) is not up-to-date For more information see SAP Note 539977
53 Service Preparation Check (RTCCTOOL)
Before we can ship any services the latest version of the SAP Service tools must be implemented in your system Report RTCCTOOL was last run on 06082015 During the check the tool detected issues for which a RED rating was set
Overall Status SAP Note Title Tool Status Manual Status
69455 [Note 69455] Addon ST-API 01R_700
69455 [Note 69455] ST-API 01R_700 Support Package 1
539977 [Note 539977] ST-PI 2008_1_700 Support Package 11
69455 [Note 69455] Proc after addon impl
539977 [Note 539977] Addon ST-PI 2008_1_700
539977 Note 1300023 for ST-PI
539977 Note 1312413 for ST-PI
539977 Note 1293657 for ST-PI
12103 [Note 12103] Collectors and TCOLL
207223 [Note 207223] EWAlert setup
Recommendation [Note 69455] Addon ST-API 01R_700 Servicetools for Applications Plug-In for NetWeaver 04s Basis 70x From httpsupportsapcomsupporttools- gtST-API-gtInstallationsampUpgrades download the installation ST-API 01R_700 Upload to tx SAINT and install as per note 69455 Then restart report RTCCTOOL and choose List-gtRefresh from SAPNet
[Note 69455] ST-API 01R_700 Support Package 1 Addon supportpackage level 1 for ST-API 01R_700 for NetWeaver 04s Basis 70x From httpsupportsapcomsupporttools- gtST-API-gtSupport packages-gtST-API 01R_700 download patches up to SAPKITAB7N For basis gt=700 use the Maintenance optimizer to release the download Upload from frontend to transaction SPAM define a queue and import
[Note 539977] ST-PI 2008_1_700 Support Package 11 Addon supportpackage level 11 for ST-PI 2008_1_700 for 700 [patches up to level 11 for Basis tools for services] Open httpsupportsapcomsupporttools- gtST-PI supportpk-gt ST-PI2008_1_700 Add patch SAPKITLRDL (and predecessors if not yet implemented) download basket Release basket via Maintenance optimizer Upload from frontend into transaction SPAM define a queue and import the queue
54 Performance DB (ST03 ST06)
Analysis of ST06 and history data indicate some problems with SAPOSCOL Check SAPOSCOL and see SAP Note 1309499
Confidential Service Preparation and Data Quality of PRD 1239
SAPreg GoingLivetrade Check - Verification Session 06082015
55 Hardware Utilization Data
Host Operating System Performance Data
sap1r3p OS not detected OK
Hardware capacity checks could not be run successfully due to missing data See SAP Note 1309499
Confidential Service Preparation and Data Quality of PRD 1339
SAPreg GoingLivetrade Check - Verification Session 06082015
6 Hardware Capacity
We have checked your system for potential CPU bottlenecks and found that the hardware is sufficient for the current workload
Note Hardware Capacity evaluation is based on hosts for which data is least partially available
61 Overview System PRD
General This analysis focuses on the workload during the peak working hours (9-11 13) and is based on the hourly averages collected by SAPOSCOL For information about the definition of peak working hours see SAP Note 1251291
CPU If the average CPU load exceeds 75 temporary CPU bottlenecks are likely to occur An average CPU load of more than 90 is a strong indicator of a CPU bottleneck
Memory If your hardware cannot handle the maximum memory consumption this causes a memory bottleneck in your SAP system that can impair performance The paging rating depends on the ratio of paging activity to physical memory A ratio exceeding 25 indicates high memory usage (if Java has been detected 0 ) and values above 50 (Java 10 ) demonstrate a main memory bottleneck
Server Max CPU load [] Date Rating RAM [MB]
sap1r3p 37 21072015 0
Note In case of virtualization or IaaS scenarios (eg IBM PowerVM VMware Amazon AWS ) it might be that for some hosts the CPU rating is yellow or red although the utilization value is quite low In this case the relevant host could not use maximum usable capacity due to a resource shortage within the virtualized infrastructure (eg IBM PowerVM Shared Pool CPU utilization)
Confidential Hardware Capacity 1439
SAPreg GoingLivetrade Check - Verification Session 06082015
7 Workload of System PRD
This chart displays the main task types and indicates how their workload is distributed in the system The table below lists the detailed KPIs
RESPONSE TIME COMPONENTS IN HOURS
Task Type Response Time Wait Time CPU Time DB Time GUI Time
DIALOG 55 00 20 20 07
BATCH 51 00 24 26 00
RFC 29 00 04 03 00
UPDATE 04 00 01 02 00
Others 02 00 00 00 00
71 Workload By Users
User activity is measured in the workload monitor Only users of at least medium activity are counted as active users
Users Low Activity Medium Activity High Activity Total Users
dialog steps per week 1 to 399 400 to 4799 4800 or more
measured in system 82 29 1 112
72 Workload Distribution PRD
The performance of your system was analyzed with respect to the workload distribution We did not detect any major problems that could affect the performance of your SAP system
721 Workload by Application Module
Confidential Workload of System PRD 1539
SAPreg GoingLivetrade Check - Verification Session 06082015
The following diagrams show how each application module contributes to the total system workload Two workload aspects are shown
- CPU time total CPU load on all servers in the system landscape
- Database time total database load generated by the application
All programs that are not classified in the SAP Application Hierarchy (transaction SE81) are summarized in the Un-Assigned category Customer programs industry solutions and third-party add-on developments fall into this category
722 DB Load Profile
Confidential Workload of System PRD 1639
SAPreg GoingLivetrade Check - Verification Session 06082015
The number of work processes creating database load in parallel is not significantly high
The following diagram shows the DB load caused by dialog RFC HTTP(S) and background tasks over different time frames The data provided in the diagram represents the average number of database processes occupied by each task type in the database during the specified time frames These statistics are calculated as a weekly average the average values over six working days with a unit of one hour Periods between 0000-0600 and 2100-2400 contain an average value per hour as these are not core business hours You can enable 24-hour monitoring by implementing SAP Note 17750 With 24-hour monitoring the time profile returns the workload of the system or application server on an hourly basis rather than returning an average value per hour for the periods 0000ndash0600 and 2100ndash2400 By comparing the load profiles for dialog and background activity you can get an overview of the volume of background activity during online working hours
Confidential Workload of System PRD 1739
SAPreg GoingLivetrade Check - Verification Session 06082015
8 Performance Overview PRD
The performance of your system was analyzed with respect to the average response times and total workload We did not detect any major problems that could affect the performance of your system
Rating Check
Performance Evaluation
The following table shows the average response times for various task types
AVERAGES OF RESPONSE TIME COMPONENTS IN MS
Task type Dialog Steps Response Time CPU Time Wait Time Load Time DB Time GUI Time
DIALOG 27390 7350 2584 56 60 2679 936
RFC 7535 13832 1702 33 53 1582 00
UPDATE 3114 4477 1392 12 97 2394 00
UPDATE2 2004 2029 665 12 41 878 00
BATCH 8357 21896 10330 07 105 11007 00
SPOOL 1221 5755 262 58 08 188 00
81 Performance Evaluation
The measured times are compared against reference times to provide a rating - If the number of dialog steps in an hour is less than 1000 this hour is not considered - If the total number of transaction steps is less than 20000 the rating for the task is not performed (indicated by a gray icon in the table) - RED if at least three time ranges are rated RED - YELLOW if two time ranges are rated RED or at least three time ranges are rated YELLOW
The table below shows that no problem is expected on the application or database servers
Task Steps Application Server Performance Database Server Performance
Dia 27389
Upd 3114
HTTP 0
HTTPS 0
The ratings in the table above are determined by comparisons against the reference table below If the dialog response times are very poor it will cause a RED rating for the entire check
Task Reference for Avg Response Time (ms) Yellow Rating
Reference for Avg Response Time (ms) Red Rating
Reference for Avg DB time (ms) Yellow Rating
Reference for Avg DB time (ms) Red Rating
Dia 1200 3600 600 1800
Upd 2400 3600 1200 1800
HTTP 1200 3600 600 1800
HTTPS 1200 3600 600 1800
Confidential Performance Overview PRD 1839
SAPreg GoingLivetrade Check - Verification Session 06082015
82 Transaction Profile Check
The following tables show the response times and the number of dialog steps for the transactions that cause the heaviest workload in your system
821 Transactions by Total Workload
The following tables list the activities with the highest contribution to the total workload
WORKLOAD BY TRANSACTION (DIALOG HTTP(S)WS-HTTP )
Transaction Type Dialog Steps Total Resp Time in
Avg Resp Time in ms
Avg CPU Time in ms
Avg DB Time in ms
Avg GUI Time in ms
VL71 DIA 83 61 297185 178782 263658 71
FBL5N DIA 2919 33 4626 1991 1330 242
VA01 DIA 2034 32 6258 2092 1164 1764
VA02 DIA 2183 29 5306 2194 1287 639
ZSDP0023 DIA 365 22 24427 2144 19871 2116
ZWMSCP01 DIA 130 21 65254 13125 10103 649
ME22 DIA 167 17 41818 22914 3250 07
VT01N DIA 235 15 25864 13412 1976 2443
SESSION_MANAGER DIA 1078 14 5202 663 844 2716
VKM1 DIA 478 12 9796 3358 3746 86
43 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
WORKLOAD BY TRANSACTION (BATCH)
Transaction Dialog Steps Total Resp Time in
Total Resp Time in s
Total CPU Time in s
Total DB Time in s
ZFIP0102 156 109 44040 25240 42295
ZFIP0115 260 97 39320 21180 23386
ZSD_CREATE_ORDER_BY_REF 125 75 30160 13100 7000
ZWMS_FILE_MANAGER2 784 37 14820 930 612
ZSDP0031 8 33 13260 6780 2783
ZFIP0105 390 16 6560 4350 383
ZFIP0106 78 15 6010 4140 5722
RSBTCRTE 2412 12 4820 1240 336
ZSDP0063 2 10 4050 2130 1318
(BATCH) 3197 09 3750 810 506
392 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
822 Transactions by DB Load
The following transaction profiles list the transactions that have the greatest share in the database load sorted by percentage of total database access times
DATABASE LOAD BY TRANSACTIONS (DIALOG HTTP(S) )
Confidential Performance Overview PRD 1939
SAPreg GoingLivetrade Check - Verification Session 06082015
Transaction Type Dialog Steps Total DB Time in Avg DB Time in ms
VL71 DIA 83 127 263658
ZSDP0023 DIA 365 42 19871
FBL5N DIA 2919 22 1330
VA02 DIA 2183 16 1287
ZVC2 DIA 1360 15 1953
ZMMP0008 DIA 64 14 37798
VA01 DIA 2034 14 1164
ZSDP0013 DIA 47 12 43947
VKM1 DIA 478 10 3746
ZWMSCP01 DIA 130 08 10103
91 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
DATABASE LOAD BY TRANSACTIONS (BATCH)
Transaction Dialog Steps Total DB Time in Total DB Time in s
ZFIP0102 156 245 42300
ZFIP0115 260 135 23390
ZSD_CREATE_ORDER_BY_REF 125 41 7000
ZFIP0106 78 33 5720
ZSDP0031 8 16 2780
RSDB4UPD 2 12 2070
ZFII0002 1 09 1580
ZSDP0063 2 08 1320
ZSD_GENERATE_INFO_CONDITIONS 7 08 1320
ZFIP0101 263 07 1290
502 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
83 RFC Load by Initiating Action
The load in task type RFC is shown In the workload monitor this information is shown as Load from External Systems The calling system can be an application server of the system itself or any external system using the RFC interface The Initial Action is the calling program initiating the RFC The total response time for each initial action is shown as an absolute value and as a percentage compared to the total RFC load considered in this table The average times (per dialog step) are shown in milliseconds [ms] Calls from external systems are shown if they account for at least 8h or 5 of the total RFC load Local calls are shown if they account for at least 24h or 20 of the total RFC load
LOAD OVERVIEW
Initial System Load [s] Load
Local system PRD 4450 9957
Sum of external systems 19 043
RFC load (sum of above) 4469 10000
Confidential Performance Overview PRD 2039
SAPreg GoingLivetrade Check - Verification Session 06082015
Initial System Load [s] Load
RFC load in Performance Overview 10422 23321
Load of all task types in Performance Overview 51694 115668
TOP 20 RFC CALLS FROM LOCAL SYSTEM - AVERAGE TIMES [MS]
Initial System
Initial Action Total Resp
Time in s
of RFC Load
Avg Response
Time
Avg CPU Time
Avg DB Time
Avg Roll Wait Time
PRD RK2A1000_POST 892 1996 13097 147 87 20
PRD VF01 491 1099 25854 8767 14305 23
PRD VA01 468 1047 8402 170 543 14
PRD SAPLARFC 256 574 10505 208 305 17
PRD CA_QUEUE_ENTRY_BCS============CP 226 505 4628 1068 1398 251
PRD VA02 178 399 6343 1215 1490 14
PRD VL71 136 304 8330 698 330 118
PRD SAP_COLLECTOR_FOR_PERFMONITOR 132 295 33749 13108 7127 188
PRD VL02N 127 284 11757 2595 7164 18
PRD VL10X 96 215 4341 553 433 10
PRD VKM1 70 157 3532 813 930 35
PRD ZSDP0049 55 124 61422 1167 1553 64
PRD STMS 52 116 18555 1911 2091 77
PRD ZP01_FROM_ZP05_944988 52 115 171827 3233 1053 03
PRD ZSDP0010 45 100 74582 31983 32785 10
PRD XD02 43 097 403 116 126 05
PRD FB1D 42 093 1999 406 1263 06
PRD FBL5N 41 091 8700 630 866 14
PRD ZP01_FROM_ZP05_942398 38 086 63795 1867 2482 65
PRD FBZ5 32 071 319430 400 510 00
Confidential Performance Overview PRD 2139
SAPreg GoingLivetrade Check - Verification Session 06082015
9 SAP System Operating PRD
The daily operation of your system was analyzed We detected some problems that may impair system operation and stability
91 Availability based on Collector Protocols
A value of 100 means that the collector was available all day Available in the context of this report means that at least one SAP instance was running If the SAP collector was not running correctly the values in the table and graphics may be incorrect To check these logs call transaction ST03N (expert mode) and choose Collector and Performance DB -gt Performance Monitor Collector -gt Log
This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR that runs every hour The job does NOT check availability it carries out only general system tasks such as collecting and aggregating SAP performance data for all serversinstances The log does not contain any direct information about availability it contains only information about the status of the hourly statistical data collection
As of SAP Basis 640 system availability information is available in the CCMS (Computing Center Management System) of an SAP System in Service Level Reporting of SAP Solution Manager
This function is provided by the relevant Solution Manager Support Packages as an advanced development For more information refer to SAP Note 944496 which also lists the prerequisites that must be fulfilled before implementation can take place
92 Update Errors
In a system running under normal conditions only a small number of update errors should occur To set the rating for this check the number of active users is also taken into consideration
We did not detect any problems
Confidential SAP System Operating PRD 2239
SAPreg GoingLivetrade Check - Verification Session 06082015
93 Table Reorganization
The largest tables andor rapidly growing tables of system PRDwere checked No standard SAP recommendations for the applicable data volume management were found
94 Program Errors (ABAP Dumps)
50 ABAP dumps have been recorded in your system in the period 30072015 to 05082015 ABAP dumps are generally deleted after 7 days by default To view the ABAP dumps in your system call transaction ST22 and choose Selection Then select a timeframe
Date Number of Dumps
30072015 19
31072015 15
01082015 0
02082015 1
03082015 4
04082015 5
05082015 6
Name of Runtime Error Dumps Server (eg) User (eg) Date (eg) Time (eg)
TIME_OUT 1 SAP1R3P_PRD_00 EMOROCHO 30072015 104804
CALL_FUNCTION_SINGLE_LOGIN_REJ 2 SAP1R3P_PRD_00 SAPSYS 30072015 170339
DYNPRO_FIELD_CONVERSION 6 SAP1R3P_PRD_00 LORTEGA 31072015 172039
DBIF_RSQL_INVALID_RSQL 5 SAP1R3P_PRD_00 PREDROBAN 02082015 060047
CALL_FUNCTION_SEND_ERROR 2 SAP1R3P_PRD_00 JPVEND 03082015 073533
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY 3 SAP1R3P_PRD_00 LORTEGA 04082015 123208
RAISE_EXCEPTION 14 SAP1R3P_PRD_00 KCASTRO 05082015 094209
CONVT_NO_NUMBER 1 SAP1R3P_PRD_00 KABARCA 05082015 143511
UNCAUGHT_EXCEPTION 1 SAP1R3P_PRD_00 CBANCHON 05082015 150325
TSV_TNEW_PAGE_ALLOC_FAILED 5 SAP1R3P_PRD_00 FLUCAS 05082015 190338
MESSAGE_TYPE_X 10 SAP1R3P_PRD_00 INTERFASES 05082015 210129
It is important that you monitor ABAP dumps using transaction ST22 on a regular basis If ABAP dumps occur you should determine the cause as soon as possible Based on our analysis we found several ABAP dumps that need your attention Evaluate and resolve the above dumps If you cannot find a solution send a customer message to SAP to request support
Confidential SAP System Operating PRD 2339
SAPreg GoingLivetrade Check - Verification Session 06082015
10 Security
Critical security issues were found in your system
See the information in the following sections
Rating Check
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
101 ABAP Stack of PRD
1011 System Recommendations (ABAP)
System Recommendations is not used at all
Recommendation SAP strongly recommends applying important security fixes as soon as possible The System Recommendations application provides a detailed recommendation regarding which SAP security notes (ABAP and non-ABAP) should be implemented based on the actual status of the system and the notes already implemented This is a mandatory prerequisite for setting up a strong security patch process For more information go to httpservicesapcomsysrec
1012 Default Passwords of Standard Users
Standard users have default passwords
Recommendation Run report RSUSR003 to check the usage of default passwords by standard users
Ensure that users SAP (must exist in all clients) SAPCPIC and EARLYWATCH have non-default passwords in all clients For more information see Protecting Standard Users either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
Make sure that the standard password for user TMSADM has been changed in client 000 and delete this user in any other client SAP Note httpsservicesapcomsapsupportnotes1414256[1414256] describes a support tool to change the password of user TMSADM in all systems of the transport domain SAP Note httpsservicesapcomsapsupportnotes1552894[1552894] shows how to update the report RSUSR003 to show the status of user TMSADM
1013 ABAP Password Policy
If password login is allowed for specific instances only the password policy is checked only for these instances
10131 Password Complexity
PARAMETER LOGINMIN_PASSWORD_LNG
Confidential Security 2439
SAPreg GoingLivetrade Check - Verification Session 06082015
Rating Instance Current Value(s) Recommended Value
sap1r3p_PRD_00 6 8
The current system settings allow a password length of fewer than 8 characters This allows weak passwords Attackers may successfully recover these passwords and gain unauthorized access to the system
Recommendation Assign a minimum value of 8 to the profile parameter loginmin_password_lng
In addition SAP provides options to enforce complex passwords Find the current settings of the corresponding profile parameters in the following table
Parameter Instance Current Value(s)
loginmin_password_digits sap1r3p_PRD_00 0
loginmin_password_letters sap1r3p_PRD_00 0
loginmin_password_lowercase sap1r3p_PRD_00 0
loginmin_password_uppercase sap1r3p_PRD_00 0
loginmin_password_specials sap1r3p_PRD_00 0
Recommendation Enforce a minimum of 3 independent character categories using the corresponding profile parameters For more information see SAP Note httpsservicesapcomsapsupportnotes862989[862989] and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
1014 Gateway and Message Server Security
10141 Kernel Patch Level
Rating Kernel Release Current Kernel Patch Level Minimal Required Kernel Patch Level
700 135 260
To enable certain gateway security functionality a minimum kernel patch level is required Your system does not currently meet this requirement
Recommendation Update the kernel of your system to the newest kernel patch level available Update to a kernel patch level equal to or higher than the minimum required kernel patch level specified above For more information see SAP Note 1298433
10142 Gateway Security
Gateway Security Properties
The parameter GWREG_NO_CONN_INFO controls the activation of certain security properties of the SAP gateway It is defined as a bit mask with one bit per property
SAP Note httpsservicesapcomsapsupportnotes1298433[1298433] ldquoBypassing security in reginfo amp secinfordquo is not activated in your system The bit mask value for bit 1 is not set
Recommendation Enable the missing property by adding the bitmask value to the current value of GWREG_NO_CONN_INFO For more information about GWREG_NO_CONN_INFO see SAP Note 1444282
Confidential Security 2539
SAPreg GoingLivetrade Check - Verification Session 06082015
1015 Users with Critical Authorizations
For more information about the following check results see SAP Note 863362
Recommendation Depending on your environment review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations You can use the User Information System (transaction SUIM) to check the results For each check you can review the roles or profiles that include the authorization objects listed in the corresponding section
10151 Users Authorized to Start all Reports
This authorization allows critical functions and reports that do not contain their own authorization checks to be executed The specified number of users for each client have the checked authorization
Client No of Users Having This Authorization No of Valid Users Rating
001 2 3
400 147 160
Authorization objects
Object 1 S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2 S_PROGRAM with P_ACTION=SUBMIT P_GROUP=
Confidential Security 2639
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
55 Hardware Utilization Data
Host Operating System Performance Data
sap1r3p OS not detected OK
Hardware capacity checks could not be run successfully due to missing data See SAP Note 1309499
Confidential Service Preparation and Data Quality of PRD 1339
SAPreg GoingLivetrade Check - Verification Session 06082015
6 Hardware Capacity
We have checked your system for potential CPU bottlenecks and found that the hardware is sufficient for the current workload
Note Hardware Capacity evaluation is based on hosts for which data is least partially available
61 Overview System PRD
General This analysis focuses on the workload during the peak working hours (9-11 13) and is based on the hourly averages collected by SAPOSCOL For information about the definition of peak working hours see SAP Note 1251291
CPU If the average CPU load exceeds 75 temporary CPU bottlenecks are likely to occur An average CPU load of more than 90 is a strong indicator of a CPU bottleneck
Memory If your hardware cannot handle the maximum memory consumption this causes a memory bottleneck in your SAP system that can impair performance The paging rating depends on the ratio of paging activity to physical memory A ratio exceeding 25 indicates high memory usage (if Java has been detected 0 ) and values above 50 (Java 10 ) demonstrate a main memory bottleneck
Server Max CPU load [] Date Rating RAM [MB]
sap1r3p 37 21072015 0
Note In case of virtualization or IaaS scenarios (eg IBM PowerVM VMware Amazon AWS ) it might be that for some hosts the CPU rating is yellow or red although the utilization value is quite low In this case the relevant host could not use maximum usable capacity due to a resource shortage within the virtualized infrastructure (eg IBM PowerVM Shared Pool CPU utilization)
Confidential Hardware Capacity 1439
SAPreg GoingLivetrade Check - Verification Session 06082015
7 Workload of System PRD
This chart displays the main task types and indicates how their workload is distributed in the system The table below lists the detailed KPIs
RESPONSE TIME COMPONENTS IN HOURS
Task Type Response Time Wait Time CPU Time DB Time GUI Time
DIALOG 55 00 20 20 07
BATCH 51 00 24 26 00
RFC 29 00 04 03 00
UPDATE 04 00 01 02 00
Others 02 00 00 00 00
71 Workload By Users
User activity is measured in the workload monitor Only users of at least medium activity are counted as active users
Users Low Activity Medium Activity High Activity Total Users
dialog steps per week 1 to 399 400 to 4799 4800 or more
measured in system 82 29 1 112
72 Workload Distribution PRD
The performance of your system was analyzed with respect to the workload distribution We did not detect any major problems that could affect the performance of your SAP system
721 Workload by Application Module
Confidential Workload of System PRD 1539
SAPreg GoingLivetrade Check - Verification Session 06082015
The following diagrams show how each application module contributes to the total system workload Two workload aspects are shown
- CPU time total CPU load on all servers in the system landscape
- Database time total database load generated by the application
All programs that are not classified in the SAP Application Hierarchy (transaction SE81) are summarized in the Un-Assigned category Customer programs industry solutions and third-party add-on developments fall into this category
722 DB Load Profile
Confidential Workload of System PRD 1639
SAPreg GoingLivetrade Check - Verification Session 06082015
The number of work processes creating database load in parallel is not significantly high
The following diagram shows the DB load caused by dialog RFC HTTP(S) and background tasks over different time frames The data provided in the diagram represents the average number of database processes occupied by each task type in the database during the specified time frames These statistics are calculated as a weekly average the average values over six working days with a unit of one hour Periods between 0000-0600 and 2100-2400 contain an average value per hour as these are not core business hours You can enable 24-hour monitoring by implementing SAP Note 17750 With 24-hour monitoring the time profile returns the workload of the system or application server on an hourly basis rather than returning an average value per hour for the periods 0000ndash0600 and 2100ndash2400 By comparing the load profiles for dialog and background activity you can get an overview of the volume of background activity during online working hours
Confidential Workload of System PRD 1739
SAPreg GoingLivetrade Check - Verification Session 06082015
8 Performance Overview PRD
The performance of your system was analyzed with respect to the average response times and total workload We did not detect any major problems that could affect the performance of your system
Rating Check
Performance Evaluation
The following table shows the average response times for various task types
AVERAGES OF RESPONSE TIME COMPONENTS IN MS
Task type Dialog Steps Response Time CPU Time Wait Time Load Time DB Time GUI Time
DIALOG 27390 7350 2584 56 60 2679 936
RFC 7535 13832 1702 33 53 1582 00
UPDATE 3114 4477 1392 12 97 2394 00
UPDATE2 2004 2029 665 12 41 878 00
BATCH 8357 21896 10330 07 105 11007 00
SPOOL 1221 5755 262 58 08 188 00
81 Performance Evaluation
The measured times are compared against reference times to provide a rating - If the number of dialog steps in an hour is less than 1000 this hour is not considered - If the total number of transaction steps is less than 20000 the rating for the task is not performed (indicated by a gray icon in the table) - RED if at least three time ranges are rated RED - YELLOW if two time ranges are rated RED or at least three time ranges are rated YELLOW
The table below shows that no problem is expected on the application or database servers
Task Steps Application Server Performance Database Server Performance
Dia 27389
Upd 3114
HTTP 0
HTTPS 0
The ratings in the table above are determined by comparisons against the reference table below If the dialog response times are very poor it will cause a RED rating for the entire check
Task Reference for Avg Response Time (ms) Yellow Rating
Reference for Avg Response Time (ms) Red Rating
Reference for Avg DB time (ms) Yellow Rating
Reference for Avg DB time (ms) Red Rating
Dia 1200 3600 600 1800
Upd 2400 3600 1200 1800
HTTP 1200 3600 600 1800
HTTPS 1200 3600 600 1800
Confidential Performance Overview PRD 1839
SAPreg GoingLivetrade Check - Verification Session 06082015
82 Transaction Profile Check
The following tables show the response times and the number of dialog steps for the transactions that cause the heaviest workload in your system
821 Transactions by Total Workload
The following tables list the activities with the highest contribution to the total workload
WORKLOAD BY TRANSACTION (DIALOG HTTP(S)WS-HTTP )
Transaction Type Dialog Steps Total Resp Time in
Avg Resp Time in ms
Avg CPU Time in ms
Avg DB Time in ms
Avg GUI Time in ms
VL71 DIA 83 61 297185 178782 263658 71
FBL5N DIA 2919 33 4626 1991 1330 242
VA01 DIA 2034 32 6258 2092 1164 1764
VA02 DIA 2183 29 5306 2194 1287 639
ZSDP0023 DIA 365 22 24427 2144 19871 2116
ZWMSCP01 DIA 130 21 65254 13125 10103 649
ME22 DIA 167 17 41818 22914 3250 07
VT01N DIA 235 15 25864 13412 1976 2443
SESSION_MANAGER DIA 1078 14 5202 663 844 2716
VKM1 DIA 478 12 9796 3358 3746 86
43 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
WORKLOAD BY TRANSACTION (BATCH)
Transaction Dialog Steps Total Resp Time in
Total Resp Time in s
Total CPU Time in s
Total DB Time in s
ZFIP0102 156 109 44040 25240 42295
ZFIP0115 260 97 39320 21180 23386
ZSD_CREATE_ORDER_BY_REF 125 75 30160 13100 7000
ZWMS_FILE_MANAGER2 784 37 14820 930 612
ZSDP0031 8 33 13260 6780 2783
ZFIP0105 390 16 6560 4350 383
ZFIP0106 78 15 6010 4140 5722
RSBTCRTE 2412 12 4820 1240 336
ZSDP0063 2 10 4050 2130 1318
(BATCH) 3197 09 3750 810 506
392 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
822 Transactions by DB Load
The following transaction profiles list the transactions that have the greatest share in the database load sorted by percentage of total database access times
DATABASE LOAD BY TRANSACTIONS (DIALOG HTTP(S) )
Confidential Performance Overview PRD 1939
SAPreg GoingLivetrade Check - Verification Session 06082015
Transaction Type Dialog Steps Total DB Time in Avg DB Time in ms
VL71 DIA 83 127 263658
ZSDP0023 DIA 365 42 19871
FBL5N DIA 2919 22 1330
VA02 DIA 2183 16 1287
ZVC2 DIA 1360 15 1953
ZMMP0008 DIA 64 14 37798
VA01 DIA 2034 14 1164
ZSDP0013 DIA 47 12 43947
VKM1 DIA 478 10 3746
ZWMSCP01 DIA 130 08 10103
91 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
DATABASE LOAD BY TRANSACTIONS (BATCH)
Transaction Dialog Steps Total DB Time in Total DB Time in s
ZFIP0102 156 245 42300
ZFIP0115 260 135 23390
ZSD_CREATE_ORDER_BY_REF 125 41 7000
ZFIP0106 78 33 5720
ZSDP0031 8 16 2780
RSDB4UPD 2 12 2070
ZFII0002 1 09 1580
ZSDP0063 2 08 1320
ZSD_GENERATE_INFO_CONDITIONS 7 08 1320
ZFIP0101 263 07 1290
502 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
83 RFC Load by Initiating Action
The load in task type RFC is shown In the workload monitor this information is shown as Load from External Systems The calling system can be an application server of the system itself or any external system using the RFC interface The Initial Action is the calling program initiating the RFC The total response time for each initial action is shown as an absolute value and as a percentage compared to the total RFC load considered in this table The average times (per dialog step) are shown in milliseconds [ms] Calls from external systems are shown if they account for at least 8h or 5 of the total RFC load Local calls are shown if they account for at least 24h or 20 of the total RFC load
LOAD OVERVIEW
Initial System Load [s] Load
Local system PRD 4450 9957
Sum of external systems 19 043
RFC load (sum of above) 4469 10000
Confidential Performance Overview PRD 2039
SAPreg GoingLivetrade Check - Verification Session 06082015
Initial System Load [s] Load
RFC load in Performance Overview 10422 23321
Load of all task types in Performance Overview 51694 115668
TOP 20 RFC CALLS FROM LOCAL SYSTEM - AVERAGE TIMES [MS]
Initial System
Initial Action Total Resp
Time in s
of RFC Load
Avg Response
Time
Avg CPU Time
Avg DB Time
Avg Roll Wait Time
PRD RK2A1000_POST 892 1996 13097 147 87 20
PRD VF01 491 1099 25854 8767 14305 23
PRD VA01 468 1047 8402 170 543 14
PRD SAPLARFC 256 574 10505 208 305 17
PRD CA_QUEUE_ENTRY_BCS============CP 226 505 4628 1068 1398 251
PRD VA02 178 399 6343 1215 1490 14
PRD VL71 136 304 8330 698 330 118
PRD SAP_COLLECTOR_FOR_PERFMONITOR 132 295 33749 13108 7127 188
PRD VL02N 127 284 11757 2595 7164 18
PRD VL10X 96 215 4341 553 433 10
PRD VKM1 70 157 3532 813 930 35
PRD ZSDP0049 55 124 61422 1167 1553 64
PRD STMS 52 116 18555 1911 2091 77
PRD ZP01_FROM_ZP05_944988 52 115 171827 3233 1053 03
PRD ZSDP0010 45 100 74582 31983 32785 10
PRD XD02 43 097 403 116 126 05
PRD FB1D 42 093 1999 406 1263 06
PRD FBL5N 41 091 8700 630 866 14
PRD ZP01_FROM_ZP05_942398 38 086 63795 1867 2482 65
PRD FBZ5 32 071 319430 400 510 00
Confidential Performance Overview PRD 2139
SAPreg GoingLivetrade Check - Verification Session 06082015
9 SAP System Operating PRD
The daily operation of your system was analyzed We detected some problems that may impair system operation and stability
91 Availability based on Collector Protocols
A value of 100 means that the collector was available all day Available in the context of this report means that at least one SAP instance was running If the SAP collector was not running correctly the values in the table and graphics may be incorrect To check these logs call transaction ST03N (expert mode) and choose Collector and Performance DB -gt Performance Monitor Collector -gt Log
This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR that runs every hour The job does NOT check availability it carries out only general system tasks such as collecting and aggregating SAP performance data for all serversinstances The log does not contain any direct information about availability it contains only information about the status of the hourly statistical data collection
As of SAP Basis 640 system availability information is available in the CCMS (Computing Center Management System) of an SAP System in Service Level Reporting of SAP Solution Manager
This function is provided by the relevant Solution Manager Support Packages as an advanced development For more information refer to SAP Note 944496 which also lists the prerequisites that must be fulfilled before implementation can take place
92 Update Errors
In a system running under normal conditions only a small number of update errors should occur To set the rating for this check the number of active users is also taken into consideration
We did not detect any problems
Confidential SAP System Operating PRD 2239
SAPreg GoingLivetrade Check - Verification Session 06082015
93 Table Reorganization
The largest tables andor rapidly growing tables of system PRDwere checked No standard SAP recommendations for the applicable data volume management were found
94 Program Errors (ABAP Dumps)
50 ABAP dumps have been recorded in your system in the period 30072015 to 05082015 ABAP dumps are generally deleted after 7 days by default To view the ABAP dumps in your system call transaction ST22 and choose Selection Then select a timeframe
Date Number of Dumps
30072015 19
31072015 15
01082015 0
02082015 1
03082015 4
04082015 5
05082015 6
Name of Runtime Error Dumps Server (eg) User (eg) Date (eg) Time (eg)
TIME_OUT 1 SAP1R3P_PRD_00 EMOROCHO 30072015 104804
CALL_FUNCTION_SINGLE_LOGIN_REJ 2 SAP1R3P_PRD_00 SAPSYS 30072015 170339
DYNPRO_FIELD_CONVERSION 6 SAP1R3P_PRD_00 LORTEGA 31072015 172039
DBIF_RSQL_INVALID_RSQL 5 SAP1R3P_PRD_00 PREDROBAN 02082015 060047
CALL_FUNCTION_SEND_ERROR 2 SAP1R3P_PRD_00 JPVEND 03082015 073533
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY 3 SAP1R3P_PRD_00 LORTEGA 04082015 123208
RAISE_EXCEPTION 14 SAP1R3P_PRD_00 KCASTRO 05082015 094209
CONVT_NO_NUMBER 1 SAP1R3P_PRD_00 KABARCA 05082015 143511
UNCAUGHT_EXCEPTION 1 SAP1R3P_PRD_00 CBANCHON 05082015 150325
TSV_TNEW_PAGE_ALLOC_FAILED 5 SAP1R3P_PRD_00 FLUCAS 05082015 190338
MESSAGE_TYPE_X 10 SAP1R3P_PRD_00 INTERFASES 05082015 210129
It is important that you monitor ABAP dumps using transaction ST22 on a regular basis If ABAP dumps occur you should determine the cause as soon as possible Based on our analysis we found several ABAP dumps that need your attention Evaluate and resolve the above dumps If you cannot find a solution send a customer message to SAP to request support
Confidential SAP System Operating PRD 2339
SAPreg GoingLivetrade Check - Verification Session 06082015
10 Security
Critical security issues were found in your system
See the information in the following sections
Rating Check
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
101 ABAP Stack of PRD
1011 System Recommendations (ABAP)
System Recommendations is not used at all
Recommendation SAP strongly recommends applying important security fixes as soon as possible The System Recommendations application provides a detailed recommendation regarding which SAP security notes (ABAP and non-ABAP) should be implemented based on the actual status of the system and the notes already implemented This is a mandatory prerequisite for setting up a strong security patch process For more information go to httpservicesapcomsysrec
1012 Default Passwords of Standard Users
Standard users have default passwords
Recommendation Run report RSUSR003 to check the usage of default passwords by standard users
Ensure that users SAP (must exist in all clients) SAPCPIC and EARLYWATCH have non-default passwords in all clients For more information see Protecting Standard Users either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
Make sure that the standard password for user TMSADM has been changed in client 000 and delete this user in any other client SAP Note httpsservicesapcomsapsupportnotes1414256[1414256] describes a support tool to change the password of user TMSADM in all systems of the transport domain SAP Note httpsservicesapcomsapsupportnotes1552894[1552894] shows how to update the report RSUSR003 to show the status of user TMSADM
1013 ABAP Password Policy
If password login is allowed for specific instances only the password policy is checked only for these instances
10131 Password Complexity
PARAMETER LOGINMIN_PASSWORD_LNG
Confidential Security 2439
SAPreg GoingLivetrade Check - Verification Session 06082015
Rating Instance Current Value(s) Recommended Value
sap1r3p_PRD_00 6 8
The current system settings allow a password length of fewer than 8 characters This allows weak passwords Attackers may successfully recover these passwords and gain unauthorized access to the system
Recommendation Assign a minimum value of 8 to the profile parameter loginmin_password_lng
In addition SAP provides options to enforce complex passwords Find the current settings of the corresponding profile parameters in the following table
Parameter Instance Current Value(s)
loginmin_password_digits sap1r3p_PRD_00 0
loginmin_password_letters sap1r3p_PRD_00 0
loginmin_password_lowercase sap1r3p_PRD_00 0
loginmin_password_uppercase sap1r3p_PRD_00 0
loginmin_password_specials sap1r3p_PRD_00 0
Recommendation Enforce a minimum of 3 independent character categories using the corresponding profile parameters For more information see SAP Note httpsservicesapcomsapsupportnotes862989[862989] and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
1014 Gateway and Message Server Security
10141 Kernel Patch Level
Rating Kernel Release Current Kernel Patch Level Minimal Required Kernel Patch Level
700 135 260
To enable certain gateway security functionality a minimum kernel patch level is required Your system does not currently meet this requirement
Recommendation Update the kernel of your system to the newest kernel patch level available Update to a kernel patch level equal to or higher than the minimum required kernel patch level specified above For more information see SAP Note 1298433
10142 Gateway Security
Gateway Security Properties
The parameter GWREG_NO_CONN_INFO controls the activation of certain security properties of the SAP gateway It is defined as a bit mask with one bit per property
SAP Note httpsservicesapcomsapsupportnotes1298433[1298433] ldquoBypassing security in reginfo amp secinfordquo is not activated in your system The bit mask value for bit 1 is not set
Recommendation Enable the missing property by adding the bitmask value to the current value of GWREG_NO_CONN_INFO For more information about GWREG_NO_CONN_INFO see SAP Note 1444282
Confidential Security 2539
SAPreg GoingLivetrade Check - Verification Session 06082015
1015 Users with Critical Authorizations
For more information about the following check results see SAP Note 863362
Recommendation Depending on your environment review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations You can use the User Information System (transaction SUIM) to check the results For each check you can review the roles or profiles that include the authorization objects listed in the corresponding section
10151 Users Authorized to Start all Reports
This authorization allows critical functions and reports that do not contain their own authorization checks to be executed The specified number of users for each client have the checked authorization
Client No of Users Having This Authorization No of Valid Users Rating
001 2 3
400 147 160
Authorization objects
Object 1 S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2 S_PROGRAM with P_ACTION=SUBMIT P_GROUP=
Confidential Security 2639
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
6 Hardware Capacity
We have checked your system for potential CPU bottlenecks and found that the hardware is sufficient for the current workload
Note Hardware Capacity evaluation is based on hosts for which data is least partially available
61 Overview System PRD
General This analysis focuses on the workload during the peak working hours (9-11 13) and is based on the hourly averages collected by SAPOSCOL For information about the definition of peak working hours see SAP Note 1251291
CPU If the average CPU load exceeds 75 temporary CPU bottlenecks are likely to occur An average CPU load of more than 90 is a strong indicator of a CPU bottleneck
Memory If your hardware cannot handle the maximum memory consumption this causes a memory bottleneck in your SAP system that can impair performance The paging rating depends on the ratio of paging activity to physical memory A ratio exceeding 25 indicates high memory usage (if Java has been detected 0 ) and values above 50 (Java 10 ) demonstrate a main memory bottleneck
Server Max CPU load [] Date Rating RAM [MB]
sap1r3p 37 21072015 0
Note In case of virtualization or IaaS scenarios (eg IBM PowerVM VMware Amazon AWS ) it might be that for some hosts the CPU rating is yellow or red although the utilization value is quite low In this case the relevant host could not use maximum usable capacity due to a resource shortage within the virtualized infrastructure (eg IBM PowerVM Shared Pool CPU utilization)
Confidential Hardware Capacity 1439
SAPreg GoingLivetrade Check - Verification Session 06082015
7 Workload of System PRD
This chart displays the main task types and indicates how their workload is distributed in the system The table below lists the detailed KPIs
RESPONSE TIME COMPONENTS IN HOURS
Task Type Response Time Wait Time CPU Time DB Time GUI Time
DIALOG 55 00 20 20 07
BATCH 51 00 24 26 00
RFC 29 00 04 03 00
UPDATE 04 00 01 02 00
Others 02 00 00 00 00
71 Workload By Users
User activity is measured in the workload monitor Only users of at least medium activity are counted as active users
Users Low Activity Medium Activity High Activity Total Users
dialog steps per week 1 to 399 400 to 4799 4800 or more
measured in system 82 29 1 112
72 Workload Distribution PRD
The performance of your system was analyzed with respect to the workload distribution We did not detect any major problems that could affect the performance of your SAP system
721 Workload by Application Module
Confidential Workload of System PRD 1539
SAPreg GoingLivetrade Check - Verification Session 06082015
The following diagrams show how each application module contributes to the total system workload Two workload aspects are shown
- CPU time total CPU load on all servers in the system landscape
- Database time total database load generated by the application
All programs that are not classified in the SAP Application Hierarchy (transaction SE81) are summarized in the Un-Assigned category Customer programs industry solutions and third-party add-on developments fall into this category
722 DB Load Profile
Confidential Workload of System PRD 1639
SAPreg GoingLivetrade Check - Verification Session 06082015
The number of work processes creating database load in parallel is not significantly high
The following diagram shows the DB load caused by dialog RFC HTTP(S) and background tasks over different time frames The data provided in the diagram represents the average number of database processes occupied by each task type in the database during the specified time frames These statistics are calculated as a weekly average the average values over six working days with a unit of one hour Periods between 0000-0600 and 2100-2400 contain an average value per hour as these are not core business hours You can enable 24-hour monitoring by implementing SAP Note 17750 With 24-hour monitoring the time profile returns the workload of the system or application server on an hourly basis rather than returning an average value per hour for the periods 0000ndash0600 and 2100ndash2400 By comparing the load profiles for dialog and background activity you can get an overview of the volume of background activity during online working hours
Confidential Workload of System PRD 1739
SAPreg GoingLivetrade Check - Verification Session 06082015
8 Performance Overview PRD
The performance of your system was analyzed with respect to the average response times and total workload We did not detect any major problems that could affect the performance of your system
Rating Check
Performance Evaluation
The following table shows the average response times for various task types
AVERAGES OF RESPONSE TIME COMPONENTS IN MS
Task type Dialog Steps Response Time CPU Time Wait Time Load Time DB Time GUI Time
DIALOG 27390 7350 2584 56 60 2679 936
RFC 7535 13832 1702 33 53 1582 00
UPDATE 3114 4477 1392 12 97 2394 00
UPDATE2 2004 2029 665 12 41 878 00
BATCH 8357 21896 10330 07 105 11007 00
SPOOL 1221 5755 262 58 08 188 00
81 Performance Evaluation
The measured times are compared against reference times to provide a rating - If the number of dialog steps in an hour is less than 1000 this hour is not considered - If the total number of transaction steps is less than 20000 the rating for the task is not performed (indicated by a gray icon in the table) - RED if at least three time ranges are rated RED - YELLOW if two time ranges are rated RED or at least three time ranges are rated YELLOW
The table below shows that no problem is expected on the application or database servers
Task Steps Application Server Performance Database Server Performance
Dia 27389
Upd 3114
HTTP 0
HTTPS 0
The ratings in the table above are determined by comparisons against the reference table below If the dialog response times are very poor it will cause a RED rating for the entire check
Task Reference for Avg Response Time (ms) Yellow Rating
Reference for Avg Response Time (ms) Red Rating
Reference for Avg DB time (ms) Yellow Rating
Reference for Avg DB time (ms) Red Rating
Dia 1200 3600 600 1800
Upd 2400 3600 1200 1800
HTTP 1200 3600 600 1800
HTTPS 1200 3600 600 1800
Confidential Performance Overview PRD 1839
SAPreg GoingLivetrade Check - Verification Session 06082015
82 Transaction Profile Check
The following tables show the response times and the number of dialog steps for the transactions that cause the heaviest workload in your system
821 Transactions by Total Workload
The following tables list the activities with the highest contribution to the total workload
WORKLOAD BY TRANSACTION (DIALOG HTTP(S)WS-HTTP )
Transaction Type Dialog Steps Total Resp Time in
Avg Resp Time in ms
Avg CPU Time in ms
Avg DB Time in ms
Avg GUI Time in ms
VL71 DIA 83 61 297185 178782 263658 71
FBL5N DIA 2919 33 4626 1991 1330 242
VA01 DIA 2034 32 6258 2092 1164 1764
VA02 DIA 2183 29 5306 2194 1287 639
ZSDP0023 DIA 365 22 24427 2144 19871 2116
ZWMSCP01 DIA 130 21 65254 13125 10103 649
ME22 DIA 167 17 41818 22914 3250 07
VT01N DIA 235 15 25864 13412 1976 2443
SESSION_MANAGER DIA 1078 14 5202 663 844 2716
VKM1 DIA 478 12 9796 3358 3746 86
43 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
WORKLOAD BY TRANSACTION (BATCH)
Transaction Dialog Steps Total Resp Time in
Total Resp Time in s
Total CPU Time in s
Total DB Time in s
ZFIP0102 156 109 44040 25240 42295
ZFIP0115 260 97 39320 21180 23386
ZSD_CREATE_ORDER_BY_REF 125 75 30160 13100 7000
ZWMS_FILE_MANAGER2 784 37 14820 930 612
ZSDP0031 8 33 13260 6780 2783
ZFIP0105 390 16 6560 4350 383
ZFIP0106 78 15 6010 4140 5722
RSBTCRTE 2412 12 4820 1240 336
ZSDP0063 2 10 4050 2130 1318
(BATCH) 3197 09 3750 810 506
392 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
822 Transactions by DB Load
The following transaction profiles list the transactions that have the greatest share in the database load sorted by percentage of total database access times
DATABASE LOAD BY TRANSACTIONS (DIALOG HTTP(S) )
Confidential Performance Overview PRD 1939
SAPreg GoingLivetrade Check - Verification Session 06082015
Transaction Type Dialog Steps Total DB Time in Avg DB Time in ms
VL71 DIA 83 127 263658
ZSDP0023 DIA 365 42 19871
FBL5N DIA 2919 22 1330
VA02 DIA 2183 16 1287
ZVC2 DIA 1360 15 1953
ZMMP0008 DIA 64 14 37798
VA01 DIA 2034 14 1164
ZSDP0013 DIA 47 12 43947
VKM1 DIA 478 10 3746
ZWMSCP01 DIA 130 08 10103
91 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
DATABASE LOAD BY TRANSACTIONS (BATCH)
Transaction Dialog Steps Total DB Time in Total DB Time in s
ZFIP0102 156 245 42300
ZFIP0115 260 135 23390
ZSD_CREATE_ORDER_BY_REF 125 41 7000
ZFIP0106 78 33 5720
ZSDP0031 8 16 2780
RSDB4UPD 2 12 2070
ZFII0002 1 09 1580
ZSDP0063 2 08 1320
ZSD_GENERATE_INFO_CONDITIONS 7 08 1320
ZFIP0101 263 07 1290
502 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
83 RFC Load by Initiating Action
The load in task type RFC is shown In the workload monitor this information is shown as Load from External Systems The calling system can be an application server of the system itself or any external system using the RFC interface The Initial Action is the calling program initiating the RFC The total response time for each initial action is shown as an absolute value and as a percentage compared to the total RFC load considered in this table The average times (per dialog step) are shown in milliseconds [ms] Calls from external systems are shown if they account for at least 8h or 5 of the total RFC load Local calls are shown if they account for at least 24h or 20 of the total RFC load
LOAD OVERVIEW
Initial System Load [s] Load
Local system PRD 4450 9957
Sum of external systems 19 043
RFC load (sum of above) 4469 10000
Confidential Performance Overview PRD 2039
SAPreg GoingLivetrade Check - Verification Session 06082015
Initial System Load [s] Load
RFC load in Performance Overview 10422 23321
Load of all task types in Performance Overview 51694 115668
TOP 20 RFC CALLS FROM LOCAL SYSTEM - AVERAGE TIMES [MS]
Initial System
Initial Action Total Resp
Time in s
of RFC Load
Avg Response
Time
Avg CPU Time
Avg DB Time
Avg Roll Wait Time
PRD RK2A1000_POST 892 1996 13097 147 87 20
PRD VF01 491 1099 25854 8767 14305 23
PRD VA01 468 1047 8402 170 543 14
PRD SAPLARFC 256 574 10505 208 305 17
PRD CA_QUEUE_ENTRY_BCS============CP 226 505 4628 1068 1398 251
PRD VA02 178 399 6343 1215 1490 14
PRD VL71 136 304 8330 698 330 118
PRD SAP_COLLECTOR_FOR_PERFMONITOR 132 295 33749 13108 7127 188
PRD VL02N 127 284 11757 2595 7164 18
PRD VL10X 96 215 4341 553 433 10
PRD VKM1 70 157 3532 813 930 35
PRD ZSDP0049 55 124 61422 1167 1553 64
PRD STMS 52 116 18555 1911 2091 77
PRD ZP01_FROM_ZP05_944988 52 115 171827 3233 1053 03
PRD ZSDP0010 45 100 74582 31983 32785 10
PRD XD02 43 097 403 116 126 05
PRD FB1D 42 093 1999 406 1263 06
PRD FBL5N 41 091 8700 630 866 14
PRD ZP01_FROM_ZP05_942398 38 086 63795 1867 2482 65
PRD FBZ5 32 071 319430 400 510 00
Confidential Performance Overview PRD 2139
SAPreg GoingLivetrade Check - Verification Session 06082015
9 SAP System Operating PRD
The daily operation of your system was analyzed We detected some problems that may impair system operation and stability
91 Availability based on Collector Protocols
A value of 100 means that the collector was available all day Available in the context of this report means that at least one SAP instance was running If the SAP collector was not running correctly the values in the table and graphics may be incorrect To check these logs call transaction ST03N (expert mode) and choose Collector and Performance DB -gt Performance Monitor Collector -gt Log
This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR that runs every hour The job does NOT check availability it carries out only general system tasks such as collecting and aggregating SAP performance data for all serversinstances The log does not contain any direct information about availability it contains only information about the status of the hourly statistical data collection
As of SAP Basis 640 system availability information is available in the CCMS (Computing Center Management System) of an SAP System in Service Level Reporting of SAP Solution Manager
This function is provided by the relevant Solution Manager Support Packages as an advanced development For more information refer to SAP Note 944496 which also lists the prerequisites that must be fulfilled before implementation can take place
92 Update Errors
In a system running under normal conditions only a small number of update errors should occur To set the rating for this check the number of active users is also taken into consideration
We did not detect any problems
Confidential SAP System Operating PRD 2239
SAPreg GoingLivetrade Check - Verification Session 06082015
93 Table Reorganization
The largest tables andor rapidly growing tables of system PRDwere checked No standard SAP recommendations for the applicable data volume management were found
94 Program Errors (ABAP Dumps)
50 ABAP dumps have been recorded in your system in the period 30072015 to 05082015 ABAP dumps are generally deleted after 7 days by default To view the ABAP dumps in your system call transaction ST22 and choose Selection Then select a timeframe
Date Number of Dumps
30072015 19
31072015 15
01082015 0
02082015 1
03082015 4
04082015 5
05082015 6
Name of Runtime Error Dumps Server (eg) User (eg) Date (eg) Time (eg)
TIME_OUT 1 SAP1R3P_PRD_00 EMOROCHO 30072015 104804
CALL_FUNCTION_SINGLE_LOGIN_REJ 2 SAP1R3P_PRD_00 SAPSYS 30072015 170339
DYNPRO_FIELD_CONVERSION 6 SAP1R3P_PRD_00 LORTEGA 31072015 172039
DBIF_RSQL_INVALID_RSQL 5 SAP1R3P_PRD_00 PREDROBAN 02082015 060047
CALL_FUNCTION_SEND_ERROR 2 SAP1R3P_PRD_00 JPVEND 03082015 073533
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY 3 SAP1R3P_PRD_00 LORTEGA 04082015 123208
RAISE_EXCEPTION 14 SAP1R3P_PRD_00 KCASTRO 05082015 094209
CONVT_NO_NUMBER 1 SAP1R3P_PRD_00 KABARCA 05082015 143511
UNCAUGHT_EXCEPTION 1 SAP1R3P_PRD_00 CBANCHON 05082015 150325
TSV_TNEW_PAGE_ALLOC_FAILED 5 SAP1R3P_PRD_00 FLUCAS 05082015 190338
MESSAGE_TYPE_X 10 SAP1R3P_PRD_00 INTERFASES 05082015 210129
It is important that you monitor ABAP dumps using transaction ST22 on a regular basis If ABAP dumps occur you should determine the cause as soon as possible Based on our analysis we found several ABAP dumps that need your attention Evaluate and resolve the above dumps If you cannot find a solution send a customer message to SAP to request support
Confidential SAP System Operating PRD 2339
SAPreg GoingLivetrade Check - Verification Session 06082015
10 Security
Critical security issues were found in your system
See the information in the following sections
Rating Check
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
101 ABAP Stack of PRD
1011 System Recommendations (ABAP)
System Recommendations is not used at all
Recommendation SAP strongly recommends applying important security fixes as soon as possible The System Recommendations application provides a detailed recommendation regarding which SAP security notes (ABAP and non-ABAP) should be implemented based on the actual status of the system and the notes already implemented This is a mandatory prerequisite for setting up a strong security patch process For more information go to httpservicesapcomsysrec
1012 Default Passwords of Standard Users
Standard users have default passwords
Recommendation Run report RSUSR003 to check the usage of default passwords by standard users
Ensure that users SAP (must exist in all clients) SAPCPIC and EARLYWATCH have non-default passwords in all clients For more information see Protecting Standard Users either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
Make sure that the standard password for user TMSADM has been changed in client 000 and delete this user in any other client SAP Note httpsservicesapcomsapsupportnotes1414256[1414256] describes a support tool to change the password of user TMSADM in all systems of the transport domain SAP Note httpsservicesapcomsapsupportnotes1552894[1552894] shows how to update the report RSUSR003 to show the status of user TMSADM
1013 ABAP Password Policy
If password login is allowed for specific instances only the password policy is checked only for these instances
10131 Password Complexity
PARAMETER LOGINMIN_PASSWORD_LNG
Confidential Security 2439
SAPreg GoingLivetrade Check - Verification Session 06082015
Rating Instance Current Value(s) Recommended Value
sap1r3p_PRD_00 6 8
The current system settings allow a password length of fewer than 8 characters This allows weak passwords Attackers may successfully recover these passwords and gain unauthorized access to the system
Recommendation Assign a minimum value of 8 to the profile parameter loginmin_password_lng
In addition SAP provides options to enforce complex passwords Find the current settings of the corresponding profile parameters in the following table
Parameter Instance Current Value(s)
loginmin_password_digits sap1r3p_PRD_00 0
loginmin_password_letters sap1r3p_PRD_00 0
loginmin_password_lowercase sap1r3p_PRD_00 0
loginmin_password_uppercase sap1r3p_PRD_00 0
loginmin_password_specials sap1r3p_PRD_00 0
Recommendation Enforce a minimum of 3 independent character categories using the corresponding profile parameters For more information see SAP Note httpsservicesapcomsapsupportnotes862989[862989] and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
1014 Gateway and Message Server Security
10141 Kernel Patch Level
Rating Kernel Release Current Kernel Patch Level Minimal Required Kernel Patch Level
700 135 260
To enable certain gateway security functionality a minimum kernel patch level is required Your system does not currently meet this requirement
Recommendation Update the kernel of your system to the newest kernel patch level available Update to a kernel patch level equal to or higher than the minimum required kernel patch level specified above For more information see SAP Note 1298433
10142 Gateway Security
Gateway Security Properties
The parameter GWREG_NO_CONN_INFO controls the activation of certain security properties of the SAP gateway It is defined as a bit mask with one bit per property
SAP Note httpsservicesapcomsapsupportnotes1298433[1298433] ldquoBypassing security in reginfo amp secinfordquo is not activated in your system The bit mask value for bit 1 is not set
Recommendation Enable the missing property by adding the bitmask value to the current value of GWREG_NO_CONN_INFO For more information about GWREG_NO_CONN_INFO see SAP Note 1444282
Confidential Security 2539
SAPreg GoingLivetrade Check - Verification Session 06082015
1015 Users with Critical Authorizations
For more information about the following check results see SAP Note 863362
Recommendation Depending on your environment review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations You can use the User Information System (transaction SUIM) to check the results For each check you can review the roles or profiles that include the authorization objects listed in the corresponding section
10151 Users Authorized to Start all Reports
This authorization allows critical functions and reports that do not contain their own authorization checks to be executed The specified number of users for each client have the checked authorization
Client No of Users Having This Authorization No of Valid Users Rating
001 2 3
400 147 160
Authorization objects
Object 1 S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2 S_PROGRAM with P_ACTION=SUBMIT P_GROUP=
Confidential Security 2639
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
7 Workload of System PRD
This chart displays the main task types and indicates how their workload is distributed in the system The table below lists the detailed KPIs
RESPONSE TIME COMPONENTS IN HOURS
Task Type Response Time Wait Time CPU Time DB Time GUI Time
DIALOG 55 00 20 20 07
BATCH 51 00 24 26 00
RFC 29 00 04 03 00
UPDATE 04 00 01 02 00
Others 02 00 00 00 00
71 Workload By Users
User activity is measured in the workload monitor Only users of at least medium activity are counted as active users
Users Low Activity Medium Activity High Activity Total Users
dialog steps per week 1 to 399 400 to 4799 4800 or more
measured in system 82 29 1 112
72 Workload Distribution PRD
The performance of your system was analyzed with respect to the workload distribution We did not detect any major problems that could affect the performance of your SAP system
721 Workload by Application Module
Confidential Workload of System PRD 1539
SAPreg GoingLivetrade Check - Verification Session 06082015
The following diagrams show how each application module contributes to the total system workload Two workload aspects are shown
- CPU time total CPU load on all servers in the system landscape
- Database time total database load generated by the application
All programs that are not classified in the SAP Application Hierarchy (transaction SE81) are summarized in the Un-Assigned category Customer programs industry solutions and third-party add-on developments fall into this category
722 DB Load Profile
Confidential Workload of System PRD 1639
SAPreg GoingLivetrade Check - Verification Session 06082015
The number of work processes creating database load in parallel is not significantly high
The following diagram shows the DB load caused by dialog RFC HTTP(S) and background tasks over different time frames The data provided in the diagram represents the average number of database processes occupied by each task type in the database during the specified time frames These statistics are calculated as a weekly average the average values over six working days with a unit of one hour Periods between 0000-0600 and 2100-2400 contain an average value per hour as these are not core business hours You can enable 24-hour monitoring by implementing SAP Note 17750 With 24-hour monitoring the time profile returns the workload of the system or application server on an hourly basis rather than returning an average value per hour for the periods 0000ndash0600 and 2100ndash2400 By comparing the load profiles for dialog and background activity you can get an overview of the volume of background activity during online working hours
Confidential Workload of System PRD 1739
SAPreg GoingLivetrade Check - Verification Session 06082015
8 Performance Overview PRD
The performance of your system was analyzed with respect to the average response times and total workload We did not detect any major problems that could affect the performance of your system
Rating Check
Performance Evaluation
The following table shows the average response times for various task types
AVERAGES OF RESPONSE TIME COMPONENTS IN MS
Task type Dialog Steps Response Time CPU Time Wait Time Load Time DB Time GUI Time
DIALOG 27390 7350 2584 56 60 2679 936
RFC 7535 13832 1702 33 53 1582 00
UPDATE 3114 4477 1392 12 97 2394 00
UPDATE2 2004 2029 665 12 41 878 00
BATCH 8357 21896 10330 07 105 11007 00
SPOOL 1221 5755 262 58 08 188 00
81 Performance Evaluation
The measured times are compared against reference times to provide a rating - If the number of dialog steps in an hour is less than 1000 this hour is not considered - If the total number of transaction steps is less than 20000 the rating for the task is not performed (indicated by a gray icon in the table) - RED if at least three time ranges are rated RED - YELLOW if two time ranges are rated RED or at least three time ranges are rated YELLOW
The table below shows that no problem is expected on the application or database servers
Task Steps Application Server Performance Database Server Performance
Dia 27389
Upd 3114
HTTP 0
HTTPS 0
The ratings in the table above are determined by comparisons against the reference table below If the dialog response times are very poor it will cause a RED rating for the entire check
Task Reference for Avg Response Time (ms) Yellow Rating
Reference for Avg Response Time (ms) Red Rating
Reference for Avg DB time (ms) Yellow Rating
Reference for Avg DB time (ms) Red Rating
Dia 1200 3600 600 1800
Upd 2400 3600 1200 1800
HTTP 1200 3600 600 1800
HTTPS 1200 3600 600 1800
Confidential Performance Overview PRD 1839
SAPreg GoingLivetrade Check - Verification Session 06082015
82 Transaction Profile Check
The following tables show the response times and the number of dialog steps for the transactions that cause the heaviest workload in your system
821 Transactions by Total Workload
The following tables list the activities with the highest contribution to the total workload
WORKLOAD BY TRANSACTION (DIALOG HTTP(S)WS-HTTP )
Transaction Type Dialog Steps Total Resp Time in
Avg Resp Time in ms
Avg CPU Time in ms
Avg DB Time in ms
Avg GUI Time in ms
VL71 DIA 83 61 297185 178782 263658 71
FBL5N DIA 2919 33 4626 1991 1330 242
VA01 DIA 2034 32 6258 2092 1164 1764
VA02 DIA 2183 29 5306 2194 1287 639
ZSDP0023 DIA 365 22 24427 2144 19871 2116
ZWMSCP01 DIA 130 21 65254 13125 10103 649
ME22 DIA 167 17 41818 22914 3250 07
VT01N DIA 235 15 25864 13412 1976 2443
SESSION_MANAGER DIA 1078 14 5202 663 844 2716
VKM1 DIA 478 12 9796 3358 3746 86
43 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
WORKLOAD BY TRANSACTION (BATCH)
Transaction Dialog Steps Total Resp Time in
Total Resp Time in s
Total CPU Time in s
Total DB Time in s
ZFIP0102 156 109 44040 25240 42295
ZFIP0115 260 97 39320 21180 23386
ZSD_CREATE_ORDER_BY_REF 125 75 30160 13100 7000
ZWMS_FILE_MANAGER2 784 37 14820 930 612
ZSDP0031 8 33 13260 6780 2783
ZFIP0105 390 16 6560 4350 383
ZFIP0106 78 15 6010 4140 5722
RSBTCRTE 2412 12 4820 1240 336
ZSDP0063 2 10 4050 2130 1318
(BATCH) 3197 09 3750 810 506
392 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
822 Transactions by DB Load
The following transaction profiles list the transactions that have the greatest share in the database load sorted by percentage of total database access times
DATABASE LOAD BY TRANSACTIONS (DIALOG HTTP(S) )
Confidential Performance Overview PRD 1939
SAPreg GoingLivetrade Check - Verification Session 06082015
Transaction Type Dialog Steps Total DB Time in Avg DB Time in ms
VL71 DIA 83 127 263658
ZSDP0023 DIA 365 42 19871
FBL5N DIA 2919 22 1330
VA02 DIA 2183 16 1287
ZVC2 DIA 1360 15 1953
ZMMP0008 DIA 64 14 37798
VA01 DIA 2034 14 1164
ZSDP0013 DIA 47 12 43947
VKM1 DIA 478 10 3746
ZWMSCP01 DIA 130 08 10103
91 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
DATABASE LOAD BY TRANSACTIONS (BATCH)
Transaction Dialog Steps Total DB Time in Total DB Time in s
ZFIP0102 156 245 42300
ZFIP0115 260 135 23390
ZSD_CREATE_ORDER_BY_REF 125 41 7000
ZFIP0106 78 33 5720
ZSDP0031 8 16 2780
RSDB4UPD 2 12 2070
ZFII0002 1 09 1580
ZSDP0063 2 08 1320
ZSD_GENERATE_INFO_CONDITIONS 7 08 1320
ZFIP0101 263 07 1290
502 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
83 RFC Load by Initiating Action
The load in task type RFC is shown In the workload monitor this information is shown as Load from External Systems The calling system can be an application server of the system itself or any external system using the RFC interface The Initial Action is the calling program initiating the RFC The total response time for each initial action is shown as an absolute value and as a percentage compared to the total RFC load considered in this table The average times (per dialog step) are shown in milliseconds [ms] Calls from external systems are shown if they account for at least 8h or 5 of the total RFC load Local calls are shown if they account for at least 24h or 20 of the total RFC load
LOAD OVERVIEW
Initial System Load [s] Load
Local system PRD 4450 9957
Sum of external systems 19 043
RFC load (sum of above) 4469 10000
Confidential Performance Overview PRD 2039
SAPreg GoingLivetrade Check - Verification Session 06082015
Initial System Load [s] Load
RFC load in Performance Overview 10422 23321
Load of all task types in Performance Overview 51694 115668
TOP 20 RFC CALLS FROM LOCAL SYSTEM - AVERAGE TIMES [MS]
Initial System
Initial Action Total Resp
Time in s
of RFC Load
Avg Response
Time
Avg CPU Time
Avg DB Time
Avg Roll Wait Time
PRD RK2A1000_POST 892 1996 13097 147 87 20
PRD VF01 491 1099 25854 8767 14305 23
PRD VA01 468 1047 8402 170 543 14
PRD SAPLARFC 256 574 10505 208 305 17
PRD CA_QUEUE_ENTRY_BCS============CP 226 505 4628 1068 1398 251
PRD VA02 178 399 6343 1215 1490 14
PRD VL71 136 304 8330 698 330 118
PRD SAP_COLLECTOR_FOR_PERFMONITOR 132 295 33749 13108 7127 188
PRD VL02N 127 284 11757 2595 7164 18
PRD VL10X 96 215 4341 553 433 10
PRD VKM1 70 157 3532 813 930 35
PRD ZSDP0049 55 124 61422 1167 1553 64
PRD STMS 52 116 18555 1911 2091 77
PRD ZP01_FROM_ZP05_944988 52 115 171827 3233 1053 03
PRD ZSDP0010 45 100 74582 31983 32785 10
PRD XD02 43 097 403 116 126 05
PRD FB1D 42 093 1999 406 1263 06
PRD FBL5N 41 091 8700 630 866 14
PRD ZP01_FROM_ZP05_942398 38 086 63795 1867 2482 65
PRD FBZ5 32 071 319430 400 510 00
Confidential Performance Overview PRD 2139
SAPreg GoingLivetrade Check - Verification Session 06082015
9 SAP System Operating PRD
The daily operation of your system was analyzed We detected some problems that may impair system operation and stability
91 Availability based on Collector Protocols
A value of 100 means that the collector was available all day Available in the context of this report means that at least one SAP instance was running If the SAP collector was not running correctly the values in the table and graphics may be incorrect To check these logs call transaction ST03N (expert mode) and choose Collector and Performance DB -gt Performance Monitor Collector -gt Log
This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR that runs every hour The job does NOT check availability it carries out only general system tasks such as collecting and aggregating SAP performance data for all serversinstances The log does not contain any direct information about availability it contains only information about the status of the hourly statistical data collection
As of SAP Basis 640 system availability information is available in the CCMS (Computing Center Management System) of an SAP System in Service Level Reporting of SAP Solution Manager
This function is provided by the relevant Solution Manager Support Packages as an advanced development For more information refer to SAP Note 944496 which also lists the prerequisites that must be fulfilled before implementation can take place
92 Update Errors
In a system running under normal conditions only a small number of update errors should occur To set the rating for this check the number of active users is also taken into consideration
We did not detect any problems
Confidential SAP System Operating PRD 2239
SAPreg GoingLivetrade Check - Verification Session 06082015
93 Table Reorganization
The largest tables andor rapidly growing tables of system PRDwere checked No standard SAP recommendations for the applicable data volume management were found
94 Program Errors (ABAP Dumps)
50 ABAP dumps have been recorded in your system in the period 30072015 to 05082015 ABAP dumps are generally deleted after 7 days by default To view the ABAP dumps in your system call transaction ST22 and choose Selection Then select a timeframe
Date Number of Dumps
30072015 19
31072015 15
01082015 0
02082015 1
03082015 4
04082015 5
05082015 6
Name of Runtime Error Dumps Server (eg) User (eg) Date (eg) Time (eg)
TIME_OUT 1 SAP1R3P_PRD_00 EMOROCHO 30072015 104804
CALL_FUNCTION_SINGLE_LOGIN_REJ 2 SAP1R3P_PRD_00 SAPSYS 30072015 170339
DYNPRO_FIELD_CONVERSION 6 SAP1R3P_PRD_00 LORTEGA 31072015 172039
DBIF_RSQL_INVALID_RSQL 5 SAP1R3P_PRD_00 PREDROBAN 02082015 060047
CALL_FUNCTION_SEND_ERROR 2 SAP1R3P_PRD_00 JPVEND 03082015 073533
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY 3 SAP1R3P_PRD_00 LORTEGA 04082015 123208
RAISE_EXCEPTION 14 SAP1R3P_PRD_00 KCASTRO 05082015 094209
CONVT_NO_NUMBER 1 SAP1R3P_PRD_00 KABARCA 05082015 143511
UNCAUGHT_EXCEPTION 1 SAP1R3P_PRD_00 CBANCHON 05082015 150325
TSV_TNEW_PAGE_ALLOC_FAILED 5 SAP1R3P_PRD_00 FLUCAS 05082015 190338
MESSAGE_TYPE_X 10 SAP1R3P_PRD_00 INTERFASES 05082015 210129
It is important that you monitor ABAP dumps using transaction ST22 on a regular basis If ABAP dumps occur you should determine the cause as soon as possible Based on our analysis we found several ABAP dumps that need your attention Evaluate and resolve the above dumps If you cannot find a solution send a customer message to SAP to request support
Confidential SAP System Operating PRD 2339
SAPreg GoingLivetrade Check - Verification Session 06082015
10 Security
Critical security issues were found in your system
See the information in the following sections
Rating Check
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
101 ABAP Stack of PRD
1011 System Recommendations (ABAP)
System Recommendations is not used at all
Recommendation SAP strongly recommends applying important security fixes as soon as possible The System Recommendations application provides a detailed recommendation regarding which SAP security notes (ABAP and non-ABAP) should be implemented based on the actual status of the system and the notes already implemented This is a mandatory prerequisite for setting up a strong security patch process For more information go to httpservicesapcomsysrec
1012 Default Passwords of Standard Users
Standard users have default passwords
Recommendation Run report RSUSR003 to check the usage of default passwords by standard users
Ensure that users SAP (must exist in all clients) SAPCPIC and EARLYWATCH have non-default passwords in all clients For more information see Protecting Standard Users either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
Make sure that the standard password for user TMSADM has been changed in client 000 and delete this user in any other client SAP Note httpsservicesapcomsapsupportnotes1414256[1414256] describes a support tool to change the password of user TMSADM in all systems of the transport domain SAP Note httpsservicesapcomsapsupportnotes1552894[1552894] shows how to update the report RSUSR003 to show the status of user TMSADM
1013 ABAP Password Policy
If password login is allowed for specific instances only the password policy is checked only for these instances
10131 Password Complexity
PARAMETER LOGINMIN_PASSWORD_LNG
Confidential Security 2439
SAPreg GoingLivetrade Check - Verification Session 06082015
Rating Instance Current Value(s) Recommended Value
sap1r3p_PRD_00 6 8
The current system settings allow a password length of fewer than 8 characters This allows weak passwords Attackers may successfully recover these passwords and gain unauthorized access to the system
Recommendation Assign a minimum value of 8 to the profile parameter loginmin_password_lng
In addition SAP provides options to enforce complex passwords Find the current settings of the corresponding profile parameters in the following table
Parameter Instance Current Value(s)
loginmin_password_digits sap1r3p_PRD_00 0
loginmin_password_letters sap1r3p_PRD_00 0
loginmin_password_lowercase sap1r3p_PRD_00 0
loginmin_password_uppercase sap1r3p_PRD_00 0
loginmin_password_specials sap1r3p_PRD_00 0
Recommendation Enforce a minimum of 3 independent character categories using the corresponding profile parameters For more information see SAP Note httpsservicesapcomsapsupportnotes862989[862989] and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
1014 Gateway and Message Server Security
10141 Kernel Patch Level
Rating Kernel Release Current Kernel Patch Level Minimal Required Kernel Patch Level
700 135 260
To enable certain gateway security functionality a minimum kernel patch level is required Your system does not currently meet this requirement
Recommendation Update the kernel of your system to the newest kernel patch level available Update to a kernel patch level equal to or higher than the minimum required kernel patch level specified above For more information see SAP Note 1298433
10142 Gateway Security
Gateway Security Properties
The parameter GWREG_NO_CONN_INFO controls the activation of certain security properties of the SAP gateway It is defined as a bit mask with one bit per property
SAP Note httpsservicesapcomsapsupportnotes1298433[1298433] ldquoBypassing security in reginfo amp secinfordquo is not activated in your system The bit mask value for bit 1 is not set
Recommendation Enable the missing property by adding the bitmask value to the current value of GWREG_NO_CONN_INFO For more information about GWREG_NO_CONN_INFO see SAP Note 1444282
Confidential Security 2539
SAPreg GoingLivetrade Check - Verification Session 06082015
1015 Users with Critical Authorizations
For more information about the following check results see SAP Note 863362
Recommendation Depending on your environment review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations You can use the User Information System (transaction SUIM) to check the results For each check you can review the roles or profiles that include the authorization objects listed in the corresponding section
10151 Users Authorized to Start all Reports
This authorization allows critical functions and reports that do not contain their own authorization checks to be executed The specified number of users for each client have the checked authorization
Client No of Users Having This Authorization No of Valid Users Rating
001 2 3
400 147 160
Authorization objects
Object 1 S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2 S_PROGRAM with P_ACTION=SUBMIT P_GROUP=
Confidential Security 2639
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
The following diagrams show how each application module contributes to the total system workload Two workload aspects are shown
- CPU time total CPU load on all servers in the system landscape
- Database time total database load generated by the application
All programs that are not classified in the SAP Application Hierarchy (transaction SE81) are summarized in the Un-Assigned category Customer programs industry solutions and third-party add-on developments fall into this category
722 DB Load Profile
Confidential Workload of System PRD 1639
SAPreg GoingLivetrade Check - Verification Session 06082015
The number of work processes creating database load in parallel is not significantly high
The following diagram shows the DB load caused by dialog RFC HTTP(S) and background tasks over different time frames The data provided in the diagram represents the average number of database processes occupied by each task type in the database during the specified time frames These statistics are calculated as a weekly average the average values over six working days with a unit of one hour Periods between 0000-0600 and 2100-2400 contain an average value per hour as these are not core business hours You can enable 24-hour monitoring by implementing SAP Note 17750 With 24-hour monitoring the time profile returns the workload of the system or application server on an hourly basis rather than returning an average value per hour for the periods 0000ndash0600 and 2100ndash2400 By comparing the load profiles for dialog and background activity you can get an overview of the volume of background activity during online working hours
Confidential Workload of System PRD 1739
SAPreg GoingLivetrade Check - Verification Session 06082015
8 Performance Overview PRD
The performance of your system was analyzed with respect to the average response times and total workload We did not detect any major problems that could affect the performance of your system
Rating Check
Performance Evaluation
The following table shows the average response times for various task types
AVERAGES OF RESPONSE TIME COMPONENTS IN MS
Task type Dialog Steps Response Time CPU Time Wait Time Load Time DB Time GUI Time
DIALOG 27390 7350 2584 56 60 2679 936
RFC 7535 13832 1702 33 53 1582 00
UPDATE 3114 4477 1392 12 97 2394 00
UPDATE2 2004 2029 665 12 41 878 00
BATCH 8357 21896 10330 07 105 11007 00
SPOOL 1221 5755 262 58 08 188 00
81 Performance Evaluation
The measured times are compared against reference times to provide a rating - If the number of dialog steps in an hour is less than 1000 this hour is not considered - If the total number of transaction steps is less than 20000 the rating for the task is not performed (indicated by a gray icon in the table) - RED if at least three time ranges are rated RED - YELLOW if two time ranges are rated RED or at least three time ranges are rated YELLOW
The table below shows that no problem is expected on the application or database servers
Task Steps Application Server Performance Database Server Performance
Dia 27389
Upd 3114
HTTP 0
HTTPS 0
The ratings in the table above are determined by comparisons against the reference table below If the dialog response times are very poor it will cause a RED rating for the entire check
Task Reference for Avg Response Time (ms) Yellow Rating
Reference for Avg Response Time (ms) Red Rating
Reference for Avg DB time (ms) Yellow Rating
Reference for Avg DB time (ms) Red Rating
Dia 1200 3600 600 1800
Upd 2400 3600 1200 1800
HTTP 1200 3600 600 1800
HTTPS 1200 3600 600 1800
Confidential Performance Overview PRD 1839
SAPreg GoingLivetrade Check - Verification Session 06082015
82 Transaction Profile Check
The following tables show the response times and the number of dialog steps for the transactions that cause the heaviest workload in your system
821 Transactions by Total Workload
The following tables list the activities with the highest contribution to the total workload
WORKLOAD BY TRANSACTION (DIALOG HTTP(S)WS-HTTP )
Transaction Type Dialog Steps Total Resp Time in
Avg Resp Time in ms
Avg CPU Time in ms
Avg DB Time in ms
Avg GUI Time in ms
VL71 DIA 83 61 297185 178782 263658 71
FBL5N DIA 2919 33 4626 1991 1330 242
VA01 DIA 2034 32 6258 2092 1164 1764
VA02 DIA 2183 29 5306 2194 1287 639
ZSDP0023 DIA 365 22 24427 2144 19871 2116
ZWMSCP01 DIA 130 21 65254 13125 10103 649
ME22 DIA 167 17 41818 22914 3250 07
VT01N DIA 235 15 25864 13412 1976 2443
SESSION_MANAGER DIA 1078 14 5202 663 844 2716
VKM1 DIA 478 12 9796 3358 3746 86
43 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
WORKLOAD BY TRANSACTION (BATCH)
Transaction Dialog Steps Total Resp Time in
Total Resp Time in s
Total CPU Time in s
Total DB Time in s
ZFIP0102 156 109 44040 25240 42295
ZFIP0115 260 97 39320 21180 23386
ZSD_CREATE_ORDER_BY_REF 125 75 30160 13100 7000
ZWMS_FILE_MANAGER2 784 37 14820 930 612
ZSDP0031 8 33 13260 6780 2783
ZFIP0105 390 16 6560 4350 383
ZFIP0106 78 15 6010 4140 5722
RSBTCRTE 2412 12 4820 1240 336
ZSDP0063 2 10 4050 2130 1318
(BATCH) 3197 09 3750 810 506
392 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
822 Transactions by DB Load
The following transaction profiles list the transactions that have the greatest share in the database load sorted by percentage of total database access times
DATABASE LOAD BY TRANSACTIONS (DIALOG HTTP(S) )
Confidential Performance Overview PRD 1939
SAPreg GoingLivetrade Check - Verification Session 06082015
Transaction Type Dialog Steps Total DB Time in Avg DB Time in ms
VL71 DIA 83 127 263658
ZSDP0023 DIA 365 42 19871
FBL5N DIA 2919 22 1330
VA02 DIA 2183 16 1287
ZVC2 DIA 1360 15 1953
ZMMP0008 DIA 64 14 37798
VA01 DIA 2034 14 1164
ZSDP0013 DIA 47 12 43947
VKM1 DIA 478 10 3746
ZWMSCP01 DIA 130 08 10103
91 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
DATABASE LOAD BY TRANSACTIONS (BATCH)
Transaction Dialog Steps Total DB Time in Total DB Time in s
ZFIP0102 156 245 42300
ZFIP0115 260 135 23390
ZSD_CREATE_ORDER_BY_REF 125 41 7000
ZFIP0106 78 33 5720
ZSDP0031 8 16 2780
RSDB4UPD 2 12 2070
ZFII0002 1 09 1580
ZSDP0063 2 08 1320
ZSD_GENERATE_INFO_CONDITIONS 7 08 1320
ZFIP0101 263 07 1290
502 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
83 RFC Load by Initiating Action
The load in task type RFC is shown In the workload monitor this information is shown as Load from External Systems The calling system can be an application server of the system itself or any external system using the RFC interface The Initial Action is the calling program initiating the RFC The total response time for each initial action is shown as an absolute value and as a percentage compared to the total RFC load considered in this table The average times (per dialog step) are shown in milliseconds [ms] Calls from external systems are shown if they account for at least 8h or 5 of the total RFC load Local calls are shown if they account for at least 24h or 20 of the total RFC load
LOAD OVERVIEW
Initial System Load [s] Load
Local system PRD 4450 9957
Sum of external systems 19 043
RFC load (sum of above) 4469 10000
Confidential Performance Overview PRD 2039
SAPreg GoingLivetrade Check - Verification Session 06082015
Initial System Load [s] Load
RFC load in Performance Overview 10422 23321
Load of all task types in Performance Overview 51694 115668
TOP 20 RFC CALLS FROM LOCAL SYSTEM - AVERAGE TIMES [MS]
Initial System
Initial Action Total Resp
Time in s
of RFC Load
Avg Response
Time
Avg CPU Time
Avg DB Time
Avg Roll Wait Time
PRD RK2A1000_POST 892 1996 13097 147 87 20
PRD VF01 491 1099 25854 8767 14305 23
PRD VA01 468 1047 8402 170 543 14
PRD SAPLARFC 256 574 10505 208 305 17
PRD CA_QUEUE_ENTRY_BCS============CP 226 505 4628 1068 1398 251
PRD VA02 178 399 6343 1215 1490 14
PRD VL71 136 304 8330 698 330 118
PRD SAP_COLLECTOR_FOR_PERFMONITOR 132 295 33749 13108 7127 188
PRD VL02N 127 284 11757 2595 7164 18
PRD VL10X 96 215 4341 553 433 10
PRD VKM1 70 157 3532 813 930 35
PRD ZSDP0049 55 124 61422 1167 1553 64
PRD STMS 52 116 18555 1911 2091 77
PRD ZP01_FROM_ZP05_944988 52 115 171827 3233 1053 03
PRD ZSDP0010 45 100 74582 31983 32785 10
PRD XD02 43 097 403 116 126 05
PRD FB1D 42 093 1999 406 1263 06
PRD FBL5N 41 091 8700 630 866 14
PRD ZP01_FROM_ZP05_942398 38 086 63795 1867 2482 65
PRD FBZ5 32 071 319430 400 510 00
Confidential Performance Overview PRD 2139
SAPreg GoingLivetrade Check - Verification Session 06082015
9 SAP System Operating PRD
The daily operation of your system was analyzed We detected some problems that may impair system operation and stability
91 Availability based on Collector Protocols
A value of 100 means that the collector was available all day Available in the context of this report means that at least one SAP instance was running If the SAP collector was not running correctly the values in the table and graphics may be incorrect To check these logs call transaction ST03N (expert mode) and choose Collector and Performance DB -gt Performance Monitor Collector -gt Log
This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR that runs every hour The job does NOT check availability it carries out only general system tasks such as collecting and aggregating SAP performance data for all serversinstances The log does not contain any direct information about availability it contains only information about the status of the hourly statistical data collection
As of SAP Basis 640 system availability information is available in the CCMS (Computing Center Management System) of an SAP System in Service Level Reporting of SAP Solution Manager
This function is provided by the relevant Solution Manager Support Packages as an advanced development For more information refer to SAP Note 944496 which also lists the prerequisites that must be fulfilled before implementation can take place
92 Update Errors
In a system running under normal conditions only a small number of update errors should occur To set the rating for this check the number of active users is also taken into consideration
We did not detect any problems
Confidential SAP System Operating PRD 2239
SAPreg GoingLivetrade Check - Verification Session 06082015
93 Table Reorganization
The largest tables andor rapidly growing tables of system PRDwere checked No standard SAP recommendations for the applicable data volume management were found
94 Program Errors (ABAP Dumps)
50 ABAP dumps have been recorded in your system in the period 30072015 to 05082015 ABAP dumps are generally deleted after 7 days by default To view the ABAP dumps in your system call transaction ST22 and choose Selection Then select a timeframe
Date Number of Dumps
30072015 19
31072015 15
01082015 0
02082015 1
03082015 4
04082015 5
05082015 6
Name of Runtime Error Dumps Server (eg) User (eg) Date (eg) Time (eg)
TIME_OUT 1 SAP1R3P_PRD_00 EMOROCHO 30072015 104804
CALL_FUNCTION_SINGLE_LOGIN_REJ 2 SAP1R3P_PRD_00 SAPSYS 30072015 170339
DYNPRO_FIELD_CONVERSION 6 SAP1R3P_PRD_00 LORTEGA 31072015 172039
DBIF_RSQL_INVALID_RSQL 5 SAP1R3P_PRD_00 PREDROBAN 02082015 060047
CALL_FUNCTION_SEND_ERROR 2 SAP1R3P_PRD_00 JPVEND 03082015 073533
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY 3 SAP1R3P_PRD_00 LORTEGA 04082015 123208
RAISE_EXCEPTION 14 SAP1R3P_PRD_00 KCASTRO 05082015 094209
CONVT_NO_NUMBER 1 SAP1R3P_PRD_00 KABARCA 05082015 143511
UNCAUGHT_EXCEPTION 1 SAP1R3P_PRD_00 CBANCHON 05082015 150325
TSV_TNEW_PAGE_ALLOC_FAILED 5 SAP1R3P_PRD_00 FLUCAS 05082015 190338
MESSAGE_TYPE_X 10 SAP1R3P_PRD_00 INTERFASES 05082015 210129
It is important that you monitor ABAP dumps using transaction ST22 on a regular basis If ABAP dumps occur you should determine the cause as soon as possible Based on our analysis we found several ABAP dumps that need your attention Evaluate and resolve the above dumps If you cannot find a solution send a customer message to SAP to request support
Confidential SAP System Operating PRD 2339
SAPreg GoingLivetrade Check - Verification Session 06082015
10 Security
Critical security issues were found in your system
See the information in the following sections
Rating Check
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
101 ABAP Stack of PRD
1011 System Recommendations (ABAP)
System Recommendations is not used at all
Recommendation SAP strongly recommends applying important security fixes as soon as possible The System Recommendations application provides a detailed recommendation regarding which SAP security notes (ABAP and non-ABAP) should be implemented based on the actual status of the system and the notes already implemented This is a mandatory prerequisite for setting up a strong security patch process For more information go to httpservicesapcomsysrec
1012 Default Passwords of Standard Users
Standard users have default passwords
Recommendation Run report RSUSR003 to check the usage of default passwords by standard users
Ensure that users SAP (must exist in all clients) SAPCPIC and EARLYWATCH have non-default passwords in all clients For more information see Protecting Standard Users either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
Make sure that the standard password for user TMSADM has been changed in client 000 and delete this user in any other client SAP Note httpsservicesapcomsapsupportnotes1414256[1414256] describes a support tool to change the password of user TMSADM in all systems of the transport domain SAP Note httpsservicesapcomsapsupportnotes1552894[1552894] shows how to update the report RSUSR003 to show the status of user TMSADM
1013 ABAP Password Policy
If password login is allowed for specific instances only the password policy is checked only for these instances
10131 Password Complexity
PARAMETER LOGINMIN_PASSWORD_LNG
Confidential Security 2439
SAPreg GoingLivetrade Check - Verification Session 06082015
Rating Instance Current Value(s) Recommended Value
sap1r3p_PRD_00 6 8
The current system settings allow a password length of fewer than 8 characters This allows weak passwords Attackers may successfully recover these passwords and gain unauthorized access to the system
Recommendation Assign a minimum value of 8 to the profile parameter loginmin_password_lng
In addition SAP provides options to enforce complex passwords Find the current settings of the corresponding profile parameters in the following table
Parameter Instance Current Value(s)
loginmin_password_digits sap1r3p_PRD_00 0
loginmin_password_letters sap1r3p_PRD_00 0
loginmin_password_lowercase sap1r3p_PRD_00 0
loginmin_password_uppercase sap1r3p_PRD_00 0
loginmin_password_specials sap1r3p_PRD_00 0
Recommendation Enforce a minimum of 3 independent character categories using the corresponding profile parameters For more information see SAP Note httpsservicesapcomsapsupportnotes862989[862989] and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
1014 Gateway and Message Server Security
10141 Kernel Patch Level
Rating Kernel Release Current Kernel Patch Level Minimal Required Kernel Patch Level
700 135 260
To enable certain gateway security functionality a minimum kernel patch level is required Your system does not currently meet this requirement
Recommendation Update the kernel of your system to the newest kernel patch level available Update to a kernel patch level equal to or higher than the minimum required kernel patch level specified above For more information see SAP Note 1298433
10142 Gateway Security
Gateway Security Properties
The parameter GWREG_NO_CONN_INFO controls the activation of certain security properties of the SAP gateway It is defined as a bit mask with one bit per property
SAP Note httpsservicesapcomsapsupportnotes1298433[1298433] ldquoBypassing security in reginfo amp secinfordquo is not activated in your system The bit mask value for bit 1 is not set
Recommendation Enable the missing property by adding the bitmask value to the current value of GWREG_NO_CONN_INFO For more information about GWREG_NO_CONN_INFO see SAP Note 1444282
Confidential Security 2539
SAPreg GoingLivetrade Check - Verification Session 06082015
1015 Users with Critical Authorizations
For more information about the following check results see SAP Note 863362
Recommendation Depending on your environment review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations You can use the User Information System (transaction SUIM) to check the results For each check you can review the roles or profiles that include the authorization objects listed in the corresponding section
10151 Users Authorized to Start all Reports
This authorization allows critical functions and reports that do not contain their own authorization checks to be executed The specified number of users for each client have the checked authorization
Client No of Users Having This Authorization No of Valid Users Rating
001 2 3
400 147 160
Authorization objects
Object 1 S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2 S_PROGRAM with P_ACTION=SUBMIT P_GROUP=
Confidential Security 2639
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
The number of work processes creating database load in parallel is not significantly high
The following diagram shows the DB load caused by dialog RFC HTTP(S) and background tasks over different time frames The data provided in the diagram represents the average number of database processes occupied by each task type in the database during the specified time frames These statistics are calculated as a weekly average the average values over six working days with a unit of one hour Periods between 0000-0600 and 2100-2400 contain an average value per hour as these are not core business hours You can enable 24-hour monitoring by implementing SAP Note 17750 With 24-hour monitoring the time profile returns the workload of the system or application server on an hourly basis rather than returning an average value per hour for the periods 0000ndash0600 and 2100ndash2400 By comparing the load profiles for dialog and background activity you can get an overview of the volume of background activity during online working hours
Confidential Workload of System PRD 1739
SAPreg GoingLivetrade Check - Verification Session 06082015
8 Performance Overview PRD
The performance of your system was analyzed with respect to the average response times and total workload We did not detect any major problems that could affect the performance of your system
Rating Check
Performance Evaluation
The following table shows the average response times for various task types
AVERAGES OF RESPONSE TIME COMPONENTS IN MS
Task type Dialog Steps Response Time CPU Time Wait Time Load Time DB Time GUI Time
DIALOG 27390 7350 2584 56 60 2679 936
RFC 7535 13832 1702 33 53 1582 00
UPDATE 3114 4477 1392 12 97 2394 00
UPDATE2 2004 2029 665 12 41 878 00
BATCH 8357 21896 10330 07 105 11007 00
SPOOL 1221 5755 262 58 08 188 00
81 Performance Evaluation
The measured times are compared against reference times to provide a rating - If the number of dialog steps in an hour is less than 1000 this hour is not considered - If the total number of transaction steps is less than 20000 the rating for the task is not performed (indicated by a gray icon in the table) - RED if at least three time ranges are rated RED - YELLOW if two time ranges are rated RED or at least three time ranges are rated YELLOW
The table below shows that no problem is expected on the application or database servers
Task Steps Application Server Performance Database Server Performance
Dia 27389
Upd 3114
HTTP 0
HTTPS 0
The ratings in the table above are determined by comparisons against the reference table below If the dialog response times are very poor it will cause a RED rating for the entire check
Task Reference for Avg Response Time (ms) Yellow Rating
Reference for Avg Response Time (ms) Red Rating
Reference for Avg DB time (ms) Yellow Rating
Reference for Avg DB time (ms) Red Rating
Dia 1200 3600 600 1800
Upd 2400 3600 1200 1800
HTTP 1200 3600 600 1800
HTTPS 1200 3600 600 1800
Confidential Performance Overview PRD 1839
SAPreg GoingLivetrade Check - Verification Session 06082015
82 Transaction Profile Check
The following tables show the response times and the number of dialog steps for the transactions that cause the heaviest workload in your system
821 Transactions by Total Workload
The following tables list the activities with the highest contribution to the total workload
WORKLOAD BY TRANSACTION (DIALOG HTTP(S)WS-HTTP )
Transaction Type Dialog Steps Total Resp Time in
Avg Resp Time in ms
Avg CPU Time in ms
Avg DB Time in ms
Avg GUI Time in ms
VL71 DIA 83 61 297185 178782 263658 71
FBL5N DIA 2919 33 4626 1991 1330 242
VA01 DIA 2034 32 6258 2092 1164 1764
VA02 DIA 2183 29 5306 2194 1287 639
ZSDP0023 DIA 365 22 24427 2144 19871 2116
ZWMSCP01 DIA 130 21 65254 13125 10103 649
ME22 DIA 167 17 41818 22914 3250 07
VT01N DIA 235 15 25864 13412 1976 2443
SESSION_MANAGER DIA 1078 14 5202 663 844 2716
VKM1 DIA 478 12 9796 3358 3746 86
43 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
WORKLOAD BY TRANSACTION (BATCH)
Transaction Dialog Steps Total Resp Time in
Total Resp Time in s
Total CPU Time in s
Total DB Time in s
ZFIP0102 156 109 44040 25240 42295
ZFIP0115 260 97 39320 21180 23386
ZSD_CREATE_ORDER_BY_REF 125 75 30160 13100 7000
ZWMS_FILE_MANAGER2 784 37 14820 930 612
ZSDP0031 8 33 13260 6780 2783
ZFIP0105 390 16 6560 4350 383
ZFIP0106 78 15 6010 4140 5722
RSBTCRTE 2412 12 4820 1240 336
ZSDP0063 2 10 4050 2130 1318
(BATCH) 3197 09 3750 810 506
392 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
822 Transactions by DB Load
The following transaction profiles list the transactions that have the greatest share in the database load sorted by percentage of total database access times
DATABASE LOAD BY TRANSACTIONS (DIALOG HTTP(S) )
Confidential Performance Overview PRD 1939
SAPreg GoingLivetrade Check - Verification Session 06082015
Transaction Type Dialog Steps Total DB Time in Avg DB Time in ms
VL71 DIA 83 127 263658
ZSDP0023 DIA 365 42 19871
FBL5N DIA 2919 22 1330
VA02 DIA 2183 16 1287
ZVC2 DIA 1360 15 1953
ZMMP0008 DIA 64 14 37798
VA01 DIA 2034 14 1164
ZSDP0013 DIA 47 12 43947
VKM1 DIA 478 10 3746
ZWMSCP01 DIA 130 08 10103
91 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
DATABASE LOAD BY TRANSACTIONS (BATCH)
Transaction Dialog Steps Total DB Time in Total DB Time in s
ZFIP0102 156 245 42300
ZFIP0115 260 135 23390
ZSD_CREATE_ORDER_BY_REF 125 41 7000
ZFIP0106 78 33 5720
ZSDP0031 8 16 2780
RSDB4UPD 2 12 2070
ZFII0002 1 09 1580
ZSDP0063 2 08 1320
ZSD_GENERATE_INFO_CONDITIONS 7 08 1320
ZFIP0101 263 07 1290
502 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
83 RFC Load by Initiating Action
The load in task type RFC is shown In the workload monitor this information is shown as Load from External Systems The calling system can be an application server of the system itself or any external system using the RFC interface The Initial Action is the calling program initiating the RFC The total response time for each initial action is shown as an absolute value and as a percentage compared to the total RFC load considered in this table The average times (per dialog step) are shown in milliseconds [ms] Calls from external systems are shown if they account for at least 8h or 5 of the total RFC load Local calls are shown if they account for at least 24h or 20 of the total RFC load
LOAD OVERVIEW
Initial System Load [s] Load
Local system PRD 4450 9957
Sum of external systems 19 043
RFC load (sum of above) 4469 10000
Confidential Performance Overview PRD 2039
SAPreg GoingLivetrade Check - Verification Session 06082015
Initial System Load [s] Load
RFC load in Performance Overview 10422 23321
Load of all task types in Performance Overview 51694 115668
TOP 20 RFC CALLS FROM LOCAL SYSTEM - AVERAGE TIMES [MS]
Initial System
Initial Action Total Resp
Time in s
of RFC Load
Avg Response
Time
Avg CPU Time
Avg DB Time
Avg Roll Wait Time
PRD RK2A1000_POST 892 1996 13097 147 87 20
PRD VF01 491 1099 25854 8767 14305 23
PRD VA01 468 1047 8402 170 543 14
PRD SAPLARFC 256 574 10505 208 305 17
PRD CA_QUEUE_ENTRY_BCS============CP 226 505 4628 1068 1398 251
PRD VA02 178 399 6343 1215 1490 14
PRD VL71 136 304 8330 698 330 118
PRD SAP_COLLECTOR_FOR_PERFMONITOR 132 295 33749 13108 7127 188
PRD VL02N 127 284 11757 2595 7164 18
PRD VL10X 96 215 4341 553 433 10
PRD VKM1 70 157 3532 813 930 35
PRD ZSDP0049 55 124 61422 1167 1553 64
PRD STMS 52 116 18555 1911 2091 77
PRD ZP01_FROM_ZP05_944988 52 115 171827 3233 1053 03
PRD ZSDP0010 45 100 74582 31983 32785 10
PRD XD02 43 097 403 116 126 05
PRD FB1D 42 093 1999 406 1263 06
PRD FBL5N 41 091 8700 630 866 14
PRD ZP01_FROM_ZP05_942398 38 086 63795 1867 2482 65
PRD FBZ5 32 071 319430 400 510 00
Confidential Performance Overview PRD 2139
SAPreg GoingLivetrade Check - Verification Session 06082015
9 SAP System Operating PRD
The daily operation of your system was analyzed We detected some problems that may impair system operation and stability
91 Availability based on Collector Protocols
A value of 100 means that the collector was available all day Available in the context of this report means that at least one SAP instance was running If the SAP collector was not running correctly the values in the table and graphics may be incorrect To check these logs call transaction ST03N (expert mode) and choose Collector and Performance DB -gt Performance Monitor Collector -gt Log
This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR that runs every hour The job does NOT check availability it carries out only general system tasks such as collecting and aggregating SAP performance data for all serversinstances The log does not contain any direct information about availability it contains only information about the status of the hourly statistical data collection
As of SAP Basis 640 system availability information is available in the CCMS (Computing Center Management System) of an SAP System in Service Level Reporting of SAP Solution Manager
This function is provided by the relevant Solution Manager Support Packages as an advanced development For more information refer to SAP Note 944496 which also lists the prerequisites that must be fulfilled before implementation can take place
92 Update Errors
In a system running under normal conditions only a small number of update errors should occur To set the rating for this check the number of active users is also taken into consideration
We did not detect any problems
Confidential SAP System Operating PRD 2239
SAPreg GoingLivetrade Check - Verification Session 06082015
93 Table Reorganization
The largest tables andor rapidly growing tables of system PRDwere checked No standard SAP recommendations for the applicable data volume management were found
94 Program Errors (ABAP Dumps)
50 ABAP dumps have been recorded in your system in the period 30072015 to 05082015 ABAP dumps are generally deleted after 7 days by default To view the ABAP dumps in your system call transaction ST22 and choose Selection Then select a timeframe
Date Number of Dumps
30072015 19
31072015 15
01082015 0
02082015 1
03082015 4
04082015 5
05082015 6
Name of Runtime Error Dumps Server (eg) User (eg) Date (eg) Time (eg)
TIME_OUT 1 SAP1R3P_PRD_00 EMOROCHO 30072015 104804
CALL_FUNCTION_SINGLE_LOGIN_REJ 2 SAP1R3P_PRD_00 SAPSYS 30072015 170339
DYNPRO_FIELD_CONVERSION 6 SAP1R3P_PRD_00 LORTEGA 31072015 172039
DBIF_RSQL_INVALID_RSQL 5 SAP1R3P_PRD_00 PREDROBAN 02082015 060047
CALL_FUNCTION_SEND_ERROR 2 SAP1R3P_PRD_00 JPVEND 03082015 073533
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY 3 SAP1R3P_PRD_00 LORTEGA 04082015 123208
RAISE_EXCEPTION 14 SAP1R3P_PRD_00 KCASTRO 05082015 094209
CONVT_NO_NUMBER 1 SAP1R3P_PRD_00 KABARCA 05082015 143511
UNCAUGHT_EXCEPTION 1 SAP1R3P_PRD_00 CBANCHON 05082015 150325
TSV_TNEW_PAGE_ALLOC_FAILED 5 SAP1R3P_PRD_00 FLUCAS 05082015 190338
MESSAGE_TYPE_X 10 SAP1R3P_PRD_00 INTERFASES 05082015 210129
It is important that you monitor ABAP dumps using transaction ST22 on a regular basis If ABAP dumps occur you should determine the cause as soon as possible Based on our analysis we found several ABAP dumps that need your attention Evaluate and resolve the above dumps If you cannot find a solution send a customer message to SAP to request support
Confidential SAP System Operating PRD 2339
SAPreg GoingLivetrade Check - Verification Session 06082015
10 Security
Critical security issues were found in your system
See the information in the following sections
Rating Check
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
101 ABAP Stack of PRD
1011 System Recommendations (ABAP)
System Recommendations is not used at all
Recommendation SAP strongly recommends applying important security fixes as soon as possible The System Recommendations application provides a detailed recommendation regarding which SAP security notes (ABAP and non-ABAP) should be implemented based on the actual status of the system and the notes already implemented This is a mandatory prerequisite for setting up a strong security patch process For more information go to httpservicesapcomsysrec
1012 Default Passwords of Standard Users
Standard users have default passwords
Recommendation Run report RSUSR003 to check the usage of default passwords by standard users
Ensure that users SAP (must exist in all clients) SAPCPIC and EARLYWATCH have non-default passwords in all clients For more information see Protecting Standard Users either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
Make sure that the standard password for user TMSADM has been changed in client 000 and delete this user in any other client SAP Note httpsservicesapcomsapsupportnotes1414256[1414256] describes a support tool to change the password of user TMSADM in all systems of the transport domain SAP Note httpsservicesapcomsapsupportnotes1552894[1552894] shows how to update the report RSUSR003 to show the status of user TMSADM
1013 ABAP Password Policy
If password login is allowed for specific instances only the password policy is checked only for these instances
10131 Password Complexity
PARAMETER LOGINMIN_PASSWORD_LNG
Confidential Security 2439
SAPreg GoingLivetrade Check - Verification Session 06082015
Rating Instance Current Value(s) Recommended Value
sap1r3p_PRD_00 6 8
The current system settings allow a password length of fewer than 8 characters This allows weak passwords Attackers may successfully recover these passwords and gain unauthorized access to the system
Recommendation Assign a minimum value of 8 to the profile parameter loginmin_password_lng
In addition SAP provides options to enforce complex passwords Find the current settings of the corresponding profile parameters in the following table
Parameter Instance Current Value(s)
loginmin_password_digits sap1r3p_PRD_00 0
loginmin_password_letters sap1r3p_PRD_00 0
loginmin_password_lowercase sap1r3p_PRD_00 0
loginmin_password_uppercase sap1r3p_PRD_00 0
loginmin_password_specials sap1r3p_PRD_00 0
Recommendation Enforce a minimum of 3 independent character categories using the corresponding profile parameters For more information see SAP Note httpsservicesapcomsapsupportnotes862989[862989] and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
1014 Gateway and Message Server Security
10141 Kernel Patch Level
Rating Kernel Release Current Kernel Patch Level Minimal Required Kernel Patch Level
700 135 260
To enable certain gateway security functionality a minimum kernel patch level is required Your system does not currently meet this requirement
Recommendation Update the kernel of your system to the newest kernel patch level available Update to a kernel patch level equal to or higher than the minimum required kernel patch level specified above For more information see SAP Note 1298433
10142 Gateway Security
Gateway Security Properties
The parameter GWREG_NO_CONN_INFO controls the activation of certain security properties of the SAP gateway It is defined as a bit mask with one bit per property
SAP Note httpsservicesapcomsapsupportnotes1298433[1298433] ldquoBypassing security in reginfo amp secinfordquo is not activated in your system The bit mask value for bit 1 is not set
Recommendation Enable the missing property by adding the bitmask value to the current value of GWREG_NO_CONN_INFO For more information about GWREG_NO_CONN_INFO see SAP Note 1444282
Confidential Security 2539
SAPreg GoingLivetrade Check - Verification Session 06082015
1015 Users with Critical Authorizations
For more information about the following check results see SAP Note 863362
Recommendation Depending on your environment review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations You can use the User Information System (transaction SUIM) to check the results For each check you can review the roles or profiles that include the authorization objects listed in the corresponding section
10151 Users Authorized to Start all Reports
This authorization allows critical functions and reports that do not contain their own authorization checks to be executed The specified number of users for each client have the checked authorization
Client No of Users Having This Authorization No of Valid Users Rating
001 2 3
400 147 160
Authorization objects
Object 1 S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2 S_PROGRAM with P_ACTION=SUBMIT P_GROUP=
Confidential Security 2639
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
8 Performance Overview PRD
The performance of your system was analyzed with respect to the average response times and total workload We did not detect any major problems that could affect the performance of your system
Rating Check
Performance Evaluation
The following table shows the average response times for various task types
AVERAGES OF RESPONSE TIME COMPONENTS IN MS
Task type Dialog Steps Response Time CPU Time Wait Time Load Time DB Time GUI Time
DIALOG 27390 7350 2584 56 60 2679 936
RFC 7535 13832 1702 33 53 1582 00
UPDATE 3114 4477 1392 12 97 2394 00
UPDATE2 2004 2029 665 12 41 878 00
BATCH 8357 21896 10330 07 105 11007 00
SPOOL 1221 5755 262 58 08 188 00
81 Performance Evaluation
The measured times are compared against reference times to provide a rating - If the number of dialog steps in an hour is less than 1000 this hour is not considered - If the total number of transaction steps is less than 20000 the rating for the task is not performed (indicated by a gray icon in the table) - RED if at least three time ranges are rated RED - YELLOW if two time ranges are rated RED or at least three time ranges are rated YELLOW
The table below shows that no problem is expected on the application or database servers
Task Steps Application Server Performance Database Server Performance
Dia 27389
Upd 3114
HTTP 0
HTTPS 0
The ratings in the table above are determined by comparisons against the reference table below If the dialog response times are very poor it will cause a RED rating for the entire check
Task Reference for Avg Response Time (ms) Yellow Rating
Reference for Avg Response Time (ms) Red Rating
Reference for Avg DB time (ms) Yellow Rating
Reference for Avg DB time (ms) Red Rating
Dia 1200 3600 600 1800
Upd 2400 3600 1200 1800
HTTP 1200 3600 600 1800
HTTPS 1200 3600 600 1800
Confidential Performance Overview PRD 1839
SAPreg GoingLivetrade Check - Verification Session 06082015
82 Transaction Profile Check
The following tables show the response times and the number of dialog steps for the transactions that cause the heaviest workload in your system
821 Transactions by Total Workload
The following tables list the activities with the highest contribution to the total workload
WORKLOAD BY TRANSACTION (DIALOG HTTP(S)WS-HTTP )
Transaction Type Dialog Steps Total Resp Time in
Avg Resp Time in ms
Avg CPU Time in ms
Avg DB Time in ms
Avg GUI Time in ms
VL71 DIA 83 61 297185 178782 263658 71
FBL5N DIA 2919 33 4626 1991 1330 242
VA01 DIA 2034 32 6258 2092 1164 1764
VA02 DIA 2183 29 5306 2194 1287 639
ZSDP0023 DIA 365 22 24427 2144 19871 2116
ZWMSCP01 DIA 130 21 65254 13125 10103 649
ME22 DIA 167 17 41818 22914 3250 07
VT01N DIA 235 15 25864 13412 1976 2443
SESSION_MANAGER DIA 1078 14 5202 663 844 2716
VKM1 DIA 478 12 9796 3358 3746 86
43 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
WORKLOAD BY TRANSACTION (BATCH)
Transaction Dialog Steps Total Resp Time in
Total Resp Time in s
Total CPU Time in s
Total DB Time in s
ZFIP0102 156 109 44040 25240 42295
ZFIP0115 260 97 39320 21180 23386
ZSD_CREATE_ORDER_BY_REF 125 75 30160 13100 7000
ZWMS_FILE_MANAGER2 784 37 14820 930 612
ZSDP0031 8 33 13260 6780 2783
ZFIP0105 390 16 6560 4350 383
ZFIP0106 78 15 6010 4140 5722
RSBTCRTE 2412 12 4820 1240 336
ZSDP0063 2 10 4050 2130 1318
(BATCH) 3197 09 3750 810 506
392 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
822 Transactions by DB Load
The following transaction profiles list the transactions that have the greatest share in the database load sorted by percentage of total database access times
DATABASE LOAD BY TRANSACTIONS (DIALOG HTTP(S) )
Confidential Performance Overview PRD 1939
SAPreg GoingLivetrade Check - Verification Session 06082015
Transaction Type Dialog Steps Total DB Time in Avg DB Time in ms
VL71 DIA 83 127 263658
ZSDP0023 DIA 365 42 19871
FBL5N DIA 2919 22 1330
VA02 DIA 2183 16 1287
ZVC2 DIA 1360 15 1953
ZMMP0008 DIA 64 14 37798
VA01 DIA 2034 14 1164
ZSDP0013 DIA 47 12 43947
VKM1 DIA 478 10 3746
ZWMSCP01 DIA 130 08 10103
91 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
DATABASE LOAD BY TRANSACTIONS (BATCH)
Transaction Dialog Steps Total DB Time in Total DB Time in s
ZFIP0102 156 245 42300
ZFIP0115 260 135 23390
ZSD_CREATE_ORDER_BY_REF 125 41 7000
ZFIP0106 78 33 5720
ZSDP0031 8 16 2780
RSDB4UPD 2 12 2070
ZFII0002 1 09 1580
ZSDP0063 2 08 1320
ZSD_GENERATE_INFO_CONDITIONS 7 08 1320
ZFIP0101 263 07 1290
502 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
83 RFC Load by Initiating Action
The load in task type RFC is shown In the workload monitor this information is shown as Load from External Systems The calling system can be an application server of the system itself or any external system using the RFC interface The Initial Action is the calling program initiating the RFC The total response time for each initial action is shown as an absolute value and as a percentage compared to the total RFC load considered in this table The average times (per dialog step) are shown in milliseconds [ms] Calls from external systems are shown if they account for at least 8h or 5 of the total RFC load Local calls are shown if they account for at least 24h or 20 of the total RFC load
LOAD OVERVIEW
Initial System Load [s] Load
Local system PRD 4450 9957
Sum of external systems 19 043
RFC load (sum of above) 4469 10000
Confidential Performance Overview PRD 2039
SAPreg GoingLivetrade Check - Verification Session 06082015
Initial System Load [s] Load
RFC load in Performance Overview 10422 23321
Load of all task types in Performance Overview 51694 115668
TOP 20 RFC CALLS FROM LOCAL SYSTEM - AVERAGE TIMES [MS]
Initial System
Initial Action Total Resp
Time in s
of RFC Load
Avg Response
Time
Avg CPU Time
Avg DB Time
Avg Roll Wait Time
PRD RK2A1000_POST 892 1996 13097 147 87 20
PRD VF01 491 1099 25854 8767 14305 23
PRD VA01 468 1047 8402 170 543 14
PRD SAPLARFC 256 574 10505 208 305 17
PRD CA_QUEUE_ENTRY_BCS============CP 226 505 4628 1068 1398 251
PRD VA02 178 399 6343 1215 1490 14
PRD VL71 136 304 8330 698 330 118
PRD SAP_COLLECTOR_FOR_PERFMONITOR 132 295 33749 13108 7127 188
PRD VL02N 127 284 11757 2595 7164 18
PRD VL10X 96 215 4341 553 433 10
PRD VKM1 70 157 3532 813 930 35
PRD ZSDP0049 55 124 61422 1167 1553 64
PRD STMS 52 116 18555 1911 2091 77
PRD ZP01_FROM_ZP05_944988 52 115 171827 3233 1053 03
PRD ZSDP0010 45 100 74582 31983 32785 10
PRD XD02 43 097 403 116 126 05
PRD FB1D 42 093 1999 406 1263 06
PRD FBL5N 41 091 8700 630 866 14
PRD ZP01_FROM_ZP05_942398 38 086 63795 1867 2482 65
PRD FBZ5 32 071 319430 400 510 00
Confidential Performance Overview PRD 2139
SAPreg GoingLivetrade Check - Verification Session 06082015
9 SAP System Operating PRD
The daily operation of your system was analyzed We detected some problems that may impair system operation and stability
91 Availability based on Collector Protocols
A value of 100 means that the collector was available all day Available in the context of this report means that at least one SAP instance was running If the SAP collector was not running correctly the values in the table and graphics may be incorrect To check these logs call transaction ST03N (expert mode) and choose Collector and Performance DB -gt Performance Monitor Collector -gt Log
This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR that runs every hour The job does NOT check availability it carries out only general system tasks such as collecting and aggregating SAP performance data for all serversinstances The log does not contain any direct information about availability it contains only information about the status of the hourly statistical data collection
As of SAP Basis 640 system availability information is available in the CCMS (Computing Center Management System) of an SAP System in Service Level Reporting of SAP Solution Manager
This function is provided by the relevant Solution Manager Support Packages as an advanced development For more information refer to SAP Note 944496 which also lists the prerequisites that must be fulfilled before implementation can take place
92 Update Errors
In a system running under normal conditions only a small number of update errors should occur To set the rating for this check the number of active users is also taken into consideration
We did not detect any problems
Confidential SAP System Operating PRD 2239
SAPreg GoingLivetrade Check - Verification Session 06082015
93 Table Reorganization
The largest tables andor rapidly growing tables of system PRDwere checked No standard SAP recommendations for the applicable data volume management were found
94 Program Errors (ABAP Dumps)
50 ABAP dumps have been recorded in your system in the period 30072015 to 05082015 ABAP dumps are generally deleted after 7 days by default To view the ABAP dumps in your system call transaction ST22 and choose Selection Then select a timeframe
Date Number of Dumps
30072015 19
31072015 15
01082015 0
02082015 1
03082015 4
04082015 5
05082015 6
Name of Runtime Error Dumps Server (eg) User (eg) Date (eg) Time (eg)
TIME_OUT 1 SAP1R3P_PRD_00 EMOROCHO 30072015 104804
CALL_FUNCTION_SINGLE_LOGIN_REJ 2 SAP1R3P_PRD_00 SAPSYS 30072015 170339
DYNPRO_FIELD_CONVERSION 6 SAP1R3P_PRD_00 LORTEGA 31072015 172039
DBIF_RSQL_INVALID_RSQL 5 SAP1R3P_PRD_00 PREDROBAN 02082015 060047
CALL_FUNCTION_SEND_ERROR 2 SAP1R3P_PRD_00 JPVEND 03082015 073533
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY 3 SAP1R3P_PRD_00 LORTEGA 04082015 123208
RAISE_EXCEPTION 14 SAP1R3P_PRD_00 KCASTRO 05082015 094209
CONVT_NO_NUMBER 1 SAP1R3P_PRD_00 KABARCA 05082015 143511
UNCAUGHT_EXCEPTION 1 SAP1R3P_PRD_00 CBANCHON 05082015 150325
TSV_TNEW_PAGE_ALLOC_FAILED 5 SAP1R3P_PRD_00 FLUCAS 05082015 190338
MESSAGE_TYPE_X 10 SAP1R3P_PRD_00 INTERFASES 05082015 210129
It is important that you monitor ABAP dumps using transaction ST22 on a regular basis If ABAP dumps occur you should determine the cause as soon as possible Based on our analysis we found several ABAP dumps that need your attention Evaluate and resolve the above dumps If you cannot find a solution send a customer message to SAP to request support
Confidential SAP System Operating PRD 2339
SAPreg GoingLivetrade Check - Verification Session 06082015
10 Security
Critical security issues were found in your system
See the information in the following sections
Rating Check
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
101 ABAP Stack of PRD
1011 System Recommendations (ABAP)
System Recommendations is not used at all
Recommendation SAP strongly recommends applying important security fixes as soon as possible The System Recommendations application provides a detailed recommendation regarding which SAP security notes (ABAP and non-ABAP) should be implemented based on the actual status of the system and the notes already implemented This is a mandatory prerequisite for setting up a strong security patch process For more information go to httpservicesapcomsysrec
1012 Default Passwords of Standard Users
Standard users have default passwords
Recommendation Run report RSUSR003 to check the usage of default passwords by standard users
Ensure that users SAP (must exist in all clients) SAPCPIC and EARLYWATCH have non-default passwords in all clients For more information see Protecting Standard Users either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
Make sure that the standard password for user TMSADM has been changed in client 000 and delete this user in any other client SAP Note httpsservicesapcomsapsupportnotes1414256[1414256] describes a support tool to change the password of user TMSADM in all systems of the transport domain SAP Note httpsservicesapcomsapsupportnotes1552894[1552894] shows how to update the report RSUSR003 to show the status of user TMSADM
1013 ABAP Password Policy
If password login is allowed for specific instances only the password policy is checked only for these instances
10131 Password Complexity
PARAMETER LOGINMIN_PASSWORD_LNG
Confidential Security 2439
SAPreg GoingLivetrade Check - Verification Session 06082015
Rating Instance Current Value(s) Recommended Value
sap1r3p_PRD_00 6 8
The current system settings allow a password length of fewer than 8 characters This allows weak passwords Attackers may successfully recover these passwords and gain unauthorized access to the system
Recommendation Assign a minimum value of 8 to the profile parameter loginmin_password_lng
In addition SAP provides options to enforce complex passwords Find the current settings of the corresponding profile parameters in the following table
Parameter Instance Current Value(s)
loginmin_password_digits sap1r3p_PRD_00 0
loginmin_password_letters sap1r3p_PRD_00 0
loginmin_password_lowercase sap1r3p_PRD_00 0
loginmin_password_uppercase sap1r3p_PRD_00 0
loginmin_password_specials sap1r3p_PRD_00 0
Recommendation Enforce a minimum of 3 independent character categories using the corresponding profile parameters For more information see SAP Note httpsservicesapcomsapsupportnotes862989[862989] and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
1014 Gateway and Message Server Security
10141 Kernel Patch Level
Rating Kernel Release Current Kernel Patch Level Minimal Required Kernel Patch Level
700 135 260
To enable certain gateway security functionality a minimum kernel patch level is required Your system does not currently meet this requirement
Recommendation Update the kernel of your system to the newest kernel patch level available Update to a kernel patch level equal to or higher than the minimum required kernel patch level specified above For more information see SAP Note 1298433
10142 Gateway Security
Gateway Security Properties
The parameter GWREG_NO_CONN_INFO controls the activation of certain security properties of the SAP gateway It is defined as a bit mask with one bit per property
SAP Note httpsservicesapcomsapsupportnotes1298433[1298433] ldquoBypassing security in reginfo amp secinfordquo is not activated in your system The bit mask value for bit 1 is not set
Recommendation Enable the missing property by adding the bitmask value to the current value of GWREG_NO_CONN_INFO For more information about GWREG_NO_CONN_INFO see SAP Note 1444282
Confidential Security 2539
SAPreg GoingLivetrade Check - Verification Session 06082015
1015 Users with Critical Authorizations
For more information about the following check results see SAP Note 863362
Recommendation Depending on your environment review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations You can use the User Information System (transaction SUIM) to check the results For each check you can review the roles or profiles that include the authorization objects listed in the corresponding section
10151 Users Authorized to Start all Reports
This authorization allows critical functions and reports that do not contain their own authorization checks to be executed The specified number of users for each client have the checked authorization
Client No of Users Having This Authorization No of Valid Users Rating
001 2 3
400 147 160
Authorization objects
Object 1 S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2 S_PROGRAM with P_ACTION=SUBMIT P_GROUP=
Confidential Security 2639
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
82 Transaction Profile Check
The following tables show the response times and the number of dialog steps for the transactions that cause the heaviest workload in your system
821 Transactions by Total Workload
The following tables list the activities with the highest contribution to the total workload
WORKLOAD BY TRANSACTION (DIALOG HTTP(S)WS-HTTP )
Transaction Type Dialog Steps Total Resp Time in
Avg Resp Time in ms
Avg CPU Time in ms
Avg DB Time in ms
Avg GUI Time in ms
VL71 DIA 83 61 297185 178782 263658 71
FBL5N DIA 2919 33 4626 1991 1330 242
VA01 DIA 2034 32 6258 2092 1164 1764
VA02 DIA 2183 29 5306 2194 1287 639
ZSDP0023 DIA 365 22 24427 2144 19871 2116
ZWMSCP01 DIA 130 21 65254 13125 10103 649
ME22 DIA 167 17 41818 22914 3250 07
VT01N DIA 235 15 25864 13412 1976 2443
SESSION_MANAGER DIA 1078 14 5202 663 844 2716
VKM1 DIA 478 12 9796 3358 3746 86
43 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
WORKLOAD BY TRANSACTION (BATCH)
Transaction Dialog Steps Total Resp Time in
Total Resp Time in s
Total CPU Time in s
Total DB Time in s
ZFIP0102 156 109 44040 25240 42295
ZFIP0115 260 97 39320 21180 23386
ZSD_CREATE_ORDER_BY_REF 125 75 30160 13100 7000
ZWMS_FILE_MANAGER2 784 37 14820 930 612
ZSDP0031 8 33 13260 6780 2783
ZFIP0105 390 16 6560 4350 383
ZFIP0106 78 15 6010 4140 5722
RSBTCRTE 2412 12 4820 1240 336
ZSDP0063 2 10 4050 2130 1318
(BATCH) 3197 09 3750 810 506
392 of the total response time in the above table is caused by customer transactions If response times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
822 Transactions by DB Load
The following transaction profiles list the transactions that have the greatest share in the database load sorted by percentage of total database access times
DATABASE LOAD BY TRANSACTIONS (DIALOG HTTP(S) )
Confidential Performance Overview PRD 1939
SAPreg GoingLivetrade Check - Verification Session 06082015
Transaction Type Dialog Steps Total DB Time in Avg DB Time in ms
VL71 DIA 83 127 263658
ZSDP0023 DIA 365 42 19871
FBL5N DIA 2919 22 1330
VA02 DIA 2183 16 1287
ZVC2 DIA 1360 15 1953
ZMMP0008 DIA 64 14 37798
VA01 DIA 2034 14 1164
ZSDP0013 DIA 47 12 43947
VKM1 DIA 478 10 3746
ZWMSCP01 DIA 130 08 10103
91 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
DATABASE LOAD BY TRANSACTIONS (BATCH)
Transaction Dialog Steps Total DB Time in Total DB Time in s
ZFIP0102 156 245 42300
ZFIP0115 260 135 23390
ZSD_CREATE_ORDER_BY_REF 125 41 7000
ZFIP0106 78 33 5720
ZSDP0031 8 16 2780
RSDB4UPD 2 12 2070
ZFII0002 1 09 1580
ZSDP0063 2 08 1320
ZSD_GENERATE_INFO_CONDITIONS 7 08 1320
ZFIP0101 263 07 1290
502 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
83 RFC Load by Initiating Action
The load in task type RFC is shown In the workload monitor this information is shown as Load from External Systems The calling system can be an application server of the system itself or any external system using the RFC interface The Initial Action is the calling program initiating the RFC The total response time for each initial action is shown as an absolute value and as a percentage compared to the total RFC load considered in this table The average times (per dialog step) are shown in milliseconds [ms] Calls from external systems are shown if they account for at least 8h or 5 of the total RFC load Local calls are shown if they account for at least 24h or 20 of the total RFC load
LOAD OVERVIEW
Initial System Load [s] Load
Local system PRD 4450 9957
Sum of external systems 19 043
RFC load (sum of above) 4469 10000
Confidential Performance Overview PRD 2039
SAPreg GoingLivetrade Check - Verification Session 06082015
Initial System Load [s] Load
RFC load in Performance Overview 10422 23321
Load of all task types in Performance Overview 51694 115668
TOP 20 RFC CALLS FROM LOCAL SYSTEM - AVERAGE TIMES [MS]
Initial System
Initial Action Total Resp
Time in s
of RFC Load
Avg Response
Time
Avg CPU Time
Avg DB Time
Avg Roll Wait Time
PRD RK2A1000_POST 892 1996 13097 147 87 20
PRD VF01 491 1099 25854 8767 14305 23
PRD VA01 468 1047 8402 170 543 14
PRD SAPLARFC 256 574 10505 208 305 17
PRD CA_QUEUE_ENTRY_BCS============CP 226 505 4628 1068 1398 251
PRD VA02 178 399 6343 1215 1490 14
PRD VL71 136 304 8330 698 330 118
PRD SAP_COLLECTOR_FOR_PERFMONITOR 132 295 33749 13108 7127 188
PRD VL02N 127 284 11757 2595 7164 18
PRD VL10X 96 215 4341 553 433 10
PRD VKM1 70 157 3532 813 930 35
PRD ZSDP0049 55 124 61422 1167 1553 64
PRD STMS 52 116 18555 1911 2091 77
PRD ZP01_FROM_ZP05_944988 52 115 171827 3233 1053 03
PRD ZSDP0010 45 100 74582 31983 32785 10
PRD XD02 43 097 403 116 126 05
PRD FB1D 42 093 1999 406 1263 06
PRD FBL5N 41 091 8700 630 866 14
PRD ZP01_FROM_ZP05_942398 38 086 63795 1867 2482 65
PRD FBZ5 32 071 319430 400 510 00
Confidential Performance Overview PRD 2139
SAPreg GoingLivetrade Check - Verification Session 06082015
9 SAP System Operating PRD
The daily operation of your system was analyzed We detected some problems that may impair system operation and stability
91 Availability based on Collector Protocols
A value of 100 means that the collector was available all day Available in the context of this report means that at least one SAP instance was running If the SAP collector was not running correctly the values in the table and graphics may be incorrect To check these logs call transaction ST03N (expert mode) and choose Collector and Performance DB -gt Performance Monitor Collector -gt Log
This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR that runs every hour The job does NOT check availability it carries out only general system tasks such as collecting and aggregating SAP performance data for all serversinstances The log does not contain any direct information about availability it contains only information about the status of the hourly statistical data collection
As of SAP Basis 640 system availability information is available in the CCMS (Computing Center Management System) of an SAP System in Service Level Reporting of SAP Solution Manager
This function is provided by the relevant Solution Manager Support Packages as an advanced development For more information refer to SAP Note 944496 which also lists the prerequisites that must be fulfilled before implementation can take place
92 Update Errors
In a system running under normal conditions only a small number of update errors should occur To set the rating for this check the number of active users is also taken into consideration
We did not detect any problems
Confidential SAP System Operating PRD 2239
SAPreg GoingLivetrade Check - Verification Session 06082015
93 Table Reorganization
The largest tables andor rapidly growing tables of system PRDwere checked No standard SAP recommendations for the applicable data volume management were found
94 Program Errors (ABAP Dumps)
50 ABAP dumps have been recorded in your system in the period 30072015 to 05082015 ABAP dumps are generally deleted after 7 days by default To view the ABAP dumps in your system call transaction ST22 and choose Selection Then select a timeframe
Date Number of Dumps
30072015 19
31072015 15
01082015 0
02082015 1
03082015 4
04082015 5
05082015 6
Name of Runtime Error Dumps Server (eg) User (eg) Date (eg) Time (eg)
TIME_OUT 1 SAP1R3P_PRD_00 EMOROCHO 30072015 104804
CALL_FUNCTION_SINGLE_LOGIN_REJ 2 SAP1R3P_PRD_00 SAPSYS 30072015 170339
DYNPRO_FIELD_CONVERSION 6 SAP1R3P_PRD_00 LORTEGA 31072015 172039
DBIF_RSQL_INVALID_RSQL 5 SAP1R3P_PRD_00 PREDROBAN 02082015 060047
CALL_FUNCTION_SEND_ERROR 2 SAP1R3P_PRD_00 JPVEND 03082015 073533
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY 3 SAP1R3P_PRD_00 LORTEGA 04082015 123208
RAISE_EXCEPTION 14 SAP1R3P_PRD_00 KCASTRO 05082015 094209
CONVT_NO_NUMBER 1 SAP1R3P_PRD_00 KABARCA 05082015 143511
UNCAUGHT_EXCEPTION 1 SAP1R3P_PRD_00 CBANCHON 05082015 150325
TSV_TNEW_PAGE_ALLOC_FAILED 5 SAP1R3P_PRD_00 FLUCAS 05082015 190338
MESSAGE_TYPE_X 10 SAP1R3P_PRD_00 INTERFASES 05082015 210129
It is important that you monitor ABAP dumps using transaction ST22 on a regular basis If ABAP dumps occur you should determine the cause as soon as possible Based on our analysis we found several ABAP dumps that need your attention Evaluate and resolve the above dumps If you cannot find a solution send a customer message to SAP to request support
Confidential SAP System Operating PRD 2339
SAPreg GoingLivetrade Check - Verification Session 06082015
10 Security
Critical security issues were found in your system
See the information in the following sections
Rating Check
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
101 ABAP Stack of PRD
1011 System Recommendations (ABAP)
System Recommendations is not used at all
Recommendation SAP strongly recommends applying important security fixes as soon as possible The System Recommendations application provides a detailed recommendation regarding which SAP security notes (ABAP and non-ABAP) should be implemented based on the actual status of the system and the notes already implemented This is a mandatory prerequisite for setting up a strong security patch process For more information go to httpservicesapcomsysrec
1012 Default Passwords of Standard Users
Standard users have default passwords
Recommendation Run report RSUSR003 to check the usage of default passwords by standard users
Ensure that users SAP (must exist in all clients) SAPCPIC and EARLYWATCH have non-default passwords in all clients For more information see Protecting Standard Users either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
Make sure that the standard password for user TMSADM has been changed in client 000 and delete this user in any other client SAP Note httpsservicesapcomsapsupportnotes1414256[1414256] describes a support tool to change the password of user TMSADM in all systems of the transport domain SAP Note httpsservicesapcomsapsupportnotes1552894[1552894] shows how to update the report RSUSR003 to show the status of user TMSADM
1013 ABAP Password Policy
If password login is allowed for specific instances only the password policy is checked only for these instances
10131 Password Complexity
PARAMETER LOGINMIN_PASSWORD_LNG
Confidential Security 2439
SAPreg GoingLivetrade Check - Verification Session 06082015
Rating Instance Current Value(s) Recommended Value
sap1r3p_PRD_00 6 8
The current system settings allow a password length of fewer than 8 characters This allows weak passwords Attackers may successfully recover these passwords and gain unauthorized access to the system
Recommendation Assign a minimum value of 8 to the profile parameter loginmin_password_lng
In addition SAP provides options to enforce complex passwords Find the current settings of the corresponding profile parameters in the following table
Parameter Instance Current Value(s)
loginmin_password_digits sap1r3p_PRD_00 0
loginmin_password_letters sap1r3p_PRD_00 0
loginmin_password_lowercase sap1r3p_PRD_00 0
loginmin_password_uppercase sap1r3p_PRD_00 0
loginmin_password_specials sap1r3p_PRD_00 0
Recommendation Enforce a minimum of 3 independent character categories using the corresponding profile parameters For more information see SAP Note httpsservicesapcomsapsupportnotes862989[862989] and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
1014 Gateway and Message Server Security
10141 Kernel Patch Level
Rating Kernel Release Current Kernel Patch Level Minimal Required Kernel Patch Level
700 135 260
To enable certain gateway security functionality a minimum kernel patch level is required Your system does not currently meet this requirement
Recommendation Update the kernel of your system to the newest kernel patch level available Update to a kernel patch level equal to or higher than the minimum required kernel patch level specified above For more information see SAP Note 1298433
10142 Gateway Security
Gateway Security Properties
The parameter GWREG_NO_CONN_INFO controls the activation of certain security properties of the SAP gateway It is defined as a bit mask with one bit per property
SAP Note httpsservicesapcomsapsupportnotes1298433[1298433] ldquoBypassing security in reginfo amp secinfordquo is not activated in your system The bit mask value for bit 1 is not set
Recommendation Enable the missing property by adding the bitmask value to the current value of GWREG_NO_CONN_INFO For more information about GWREG_NO_CONN_INFO see SAP Note 1444282
Confidential Security 2539
SAPreg GoingLivetrade Check - Verification Session 06082015
1015 Users with Critical Authorizations
For more information about the following check results see SAP Note 863362
Recommendation Depending on your environment review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations You can use the User Information System (transaction SUIM) to check the results For each check you can review the roles or profiles that include the authorization objects listed in the corresponding section
10151 Users Authorized to Start all Reports
This authorization allows critical functions and reports that do not contain their own authorization checks to be executed The specified number of users for each client have the checked authorization
Client No of Users Having This Authorization No of Valid Users Rating
001 2 3
400 147 160
Authorization objects
Object 1 S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2 S_PROGRAM with P_ACTION=SUBMIT P_GROUP=
Confidential Security 2639
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
Transaction Type Dialog Steps Total DB Time in Avg DB Time in ms
VL71 DIA 83 127 263658
ZSDP0023 DIA 365 42 19871
FBL5N DIA 2919 22 1330
VA02 DIA 2183 16 1287
ZVC2 DIA 1360 15 1953
ZMMP0008 DIA 64 14 37798
VA01 DIA 2034 14 1164
ZSDP0013 DIA 47 12 43947
VKM1 DIA 478 10 3746
ZWMSCP01 DIA 130 08 10103
91 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
DATABASE LOAD BY TRANSACTIONS (BATCH)
Transaction Dialog Steps Total DB Time in Total DB Time in s
ZFIP0102 156 245 42300
ZFIP0115 260 135 23390
ZSD_CREATE_ORDER_BY_REF 125 41 7000
ZFIP0106 78 33 5720
ZSDP0031 8 16 2780
RSDB4UPD 2 12 2070
ZFII0002 1 09 1580
ZSDP0063 2 08 1320
ZSD_GENERATE_INFO_CONDITIONS 7 08 1320
ZFIP0101 263 07 1290
502 of the total database time in the above table is caused by customer transactions If average database times are outside acceptable boundaries and you are unhappy with the performance of a transaction contact your in-house developers about possible optimization potential and open a message under component SV-BO if required
83 RFC Load by Initiating Action
The load in task type RFC is shown In the workload monitor this information is shown as Load from External Systems The calling system can be an application server of the system itself or any external system using the RFC interface The Initial Action is the calling program initiating the RFC The total response time for each initial action is shown as an absolute value and as a percentage compared to the total RFC load considered in this table The average times (per dialog step) are shown in milliseconds [ms] Calls from external systems are shown if they account for at least 8h or 5 of the total RFC load Local calls are shown if they account for at least 24h or 20 of the total RFC load
LOAD OVERVIEW
Initial System Load [s] Load
Local system PRD 4450 9957
Sum of external systems 19 043
RFC load (sum of above) 4469 10000
Confidential Performance Overview PRD 2039
SAPreg GoingLivetrade Check - Verification Session 06082015
Initial System Load [s] Load
RFC load in Performance Overview 10422 23321
Load of all task types in Performance Overview 51694 115668
TOP 20 RFC CALLS FROM LOCAL SYSTEM - AVERAGE TIMES [MS]
Initial System
Initial Action Total Resp
Time in s
of RFC Load
Avg Response
Time
Avg CPU Time
Avg DB Time
Avg Roll Wait Time
PRD RK2A1000_POST 892 1996 13097 147 87 20
PRD VF01 491 1099 25854 8767 14305 23
PRD VA01 468 1047 8402 170 543 14
PRD SAPLARFC 256 574 10505 208 305 17
PRD CA_QUEUE_ENTRY_BCS============CP 226 505 4628 1068 1398 251
PRD VA02 178 399 6343 1215 1490 14
PRD VL71 136 304 8330 698 330 118
PRD SAP_COLLECTOR_FOR_PERFMONITOR 132 295 33749 13108 7127 188
PRD VL02N 127 284 11757 2595 7164 18
PRD VL10X 96 215 4341 553 433 10
PRD VKM1 70 157 3532 813 930 35
PRD ZSDP0049 55 124 61422 1167 1553 64
PRD STMS 52 116 18555 1911 2091 77
PRD ZP01_FROM_ZP05_944988 52 115 171827 3233 1053 03
PRD ZSDP0010 45 100 74582 31983 32785 10
PRD XD02 43 097 403 116 126 05
PRD FB1D 42 093 1999 406 1263 06
PRD FBL5N 41 091 8700 630 866 14
PRD ZP01_FROM_ZP05_942398 38 086 63795 1867 2482 65
PRD FBZ5 32 071 319430 400 510 00
Confidential Performance Overview PRD 2139
SAPreg GoingLivetrade Check - Verification Session 06082015
9 SAP System Operating PRD
The daily operation of your system was analyzed We detected some problems that may impair system operation and stability
91 Availability based on Collector Protocols
A value of 100 means that the collector was available all day Available in the context of this report means that at least one SAP instance was running If the SAP collector was not running correctly the values in the table and graphics may be incorrect To check these logs call transaction ST03N (expert mode) and choose Collector and Performance DB -gt Performance Monitor Collector -gt Log
This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR that runs every hour The job does NOT check availability it carries out only general system tasks such as collecting and aggregating SAP performance data for all serversinstances The log does not contain any direct information about availability it contains only information about the status of the hourly statistical data collection
As of SAP Basis 640 system availability information is available in the CCMS (Computing Center Management System) of an SAP System in Service Level Reporting of SAP Solution Manager
This function is provided by the relevant Solution Manager Support Packages as an advanced development For more information refer to SAP Note 944496 which also lists the prerequisites that must be fulfilled before implementation can take place
92 Update Errors
In a system running under normal conditions only a small number of update errors should occur To set the rating for this check the number of active users is also taken into consideration
We did not detect any problems
Confidential SAP System Operating PRD 2239
SAPreg GoingLivetrade Check - Verification Session 06082015
93 Table Reorganization
The largest tables andor rapidly growing tables of system PRDwere checked No standard SAP recommendations for the applicable data volume management were found
94 Program Errors (ABAP Dumps)
50 ABAP dumps have been recorded in your system in the period 30072015 to 05082015 ABAP dumps are generally deleted after 7 days by default To view the ABAP dumps in your system call transaction ST22 and choose Selection Then select a timeframe
Date Number of Dumps
30072015 19
31072015 15
01082015 0
02082015 1
03082015 4
04082015 5
05082015 6
Name of Runtime Error Dumps Server (eg) User (eg) Date (eg) Time (eg)
TIME_OUT 1 SAP1R3P_PRD_00 EMOROCHO 30072015 104804
CALL_FUNCTION_SINGLE_LOGIN_REJ 2 SAP1R3P_PRD_00 SAPSYS 30072015 170339
DYNPRO_FIELD_CONVERSION 6 SAP1R3P_PRD_00 LORTEGA 31072015 172039
DBIF_RSQL_INVALID_RSQL 5 SAP1R3P_PRD_00 PREDROBAN 02082015 060047
CALL_FUNCTION_SEND_ERROR 2 SAP1R3P_PRD_00 JPVEND 03082015 073533
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY 3 SAP1R3P_PRD_00 LORTEGA 04082015 123208
RAISE_EXCEPTION 14 SAP1R3P_PRD_00 KCASTRO 05082015 094209
CONVT_NO_NUMBER 1 SAP1R3P_PRD_00 KABARCA 05082015 143511
UNCAUGHT_EXCEPTION 1 SAP1R3P_PRD_00 CBANCHON 05082015 150325
TSV_TNEW_PAGE_ALLOC_FAILED 5 SAP1R3P_PRD_00 FLUCAS 05082015 190338
MESSAGE_TYPE_X 10 SAP1R3P_PRD_00 INTERFASES 05082015 210129
It is important that you monitor ABAP dumps using transaction ST22 on a regular basis If ABAP dumps occur you should determine the cause as soon as possible Based on our analysis we found several ABAP dumps that need your attention Evaluate and resolve the above dumps If you cannot find a solution send a customer message to SAP to request support
Confidential SAP System Operating PRD 2339
SAPreg GoingLivetrade Check - Verification Session 06082015
10 Security
Critical security issues were found in your system
See the information in the following sections
Rating Check
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
101 ABAP Stack of PRD
1011 System Recommendations (ABAP)
System Recommendations is not used at all
Recommendation SAP strongly recommends applying important security fixes as soon as possible The System Recommendations application provides a detailed recommendation regarding which SAP security notes (ABAP and non-ABAP) should be implemented based on the actual status of the system and the notes already implemented This is a mandatory prerequisite for setting up a strong security patch process For more information go to httpservicesapcomsysrec
1012 Default Passwords of Standard Users
Standard users have default passwords
Recommendation Run report RSUSR003 to check the usage of default passwords by standard users
Ensure that users SAP (must exist in all clients) SAPCPIC and EARLYWATCH have non-default passwords in all clients For more information see Protecting Standard Users either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
Make sure that the standard password for user TMSADM has been changed in client 000 and delete this user in any other client SAP Note httpsservicesapcomsapsupportnotes1414256[1414256] describes a support tool to change the password of user TMSADM in all systems of the transport domain SAP Note httpsservicesapcomsapsupportnotes1552894[1552894] shows how to update the report RSUSR003 to show the status of user TMSADM
1013 ABAP Password Policy
If password login is allowed for specific instances only the password policy is checked only for these instances
10131 Password Complexity
PARAMETER LOGINMIN_PASSWORD_LNG
Confidential Security 2439
SAPreg GoingLivetrade Check - Verification Session 06082015
Rating Instance Current Value(s) Recommended Value
sap1r3p_PRD_00 6 8
The current system settings allow a password length of fewer than 8 characters This allows weak passwords Attackers may successfully recover these passwords and gain unauthorized access to the system
Recommendation Assign a minimum value of 8 to the profile parameter loginmin_password_lng
In addition SAP provides options to enforce complex passwords Find the current settings of the corresponding profile parameters in the following table
Parameter Instance Current Value(s)
loginmin_password_digits sap1r3p_PRD_00 0
loginmin_password_letters sap1r3p_PRD_00 0
loginmin_password_lowercase sap1r3p_PRD_00 0
loginmin_password_uppercase sap1r3p_PRD_00 0
loginmin_password_specials sap1r3p_PRD_00 0
Recommendation Enforce a minimum of 3 independent character categories using the corresponding profile parameters For more information see SAP Note httpsservicesapcomsapsupportnotes862989[862989] and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
1014 Gateway and Message Server Security
10141 Kernel Patch Level
Rating Kernel Release Current Kernel Patch Level Minimal Required Kernel Patch Level
700 135 260
To enable certain gateway security functionality a minimum kernel patch level is required Your system does not currently meet this requirement
Recommendation Update the kernel of your system to the newest kernel patch level available Update to a kernel patch level equal to or higher than the minimum required kernel patch level specified above For more information see SAP Note 1298433
10142 Gateway Security
Gateway Security Properties
The parameter GWREG_NO_CONN_INFO controls the activation of certain security properties of the SAP gateway It is defined as a bit mask with one bit per property
SAP Note httpsservicesapcomsapsupportnotes1298433[1298433] ldquoBypassing security in reginfo amp secinfordquo is not activated in your system The bit mask value for bit 1 is not set
Recommendation Enable the missing property by adding the bitmask value to the current value of GWREG_NO_CONN_INFO For more information about GWREG_NO_CONN_INFO see SAP Note 1444282
Confidential Security 2539
SAPreg GoingLivetrade Check - Verification Session 06082015
1015 Users with Critical Authorizations
For more information about the following check results see SAP Note 863362
Recommendation Depending on your environment review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations You can use the User Information System (transaction SUIM) to check the results For each check you can review the roles or profiles that include the authorization objects listed in the corresponding section
10151 Users Authorized to Start all Reports
This authorization allows critical functions and reports that do not contain their own authorization checks to be executed The specified number of users for each client have the checked authorization
Client No of Users Having This Authorization No of Valid Users Rating
001 2 3
400 147 160
Authorization objects
Object 1 S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2 S_PROGRAM with P_ACTION=SUBMIT P_GROUP=
Confidential Security 2639
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
Initial System Load [s] Load
RFC load in Performance Overview 10422 23321
Load of all task types in Performance Overview 51694 115668
TOP 20 RFC CALLS FROM LOCAL SYSTEM - AVERAGE TIMES [MS]
Initial System
Initial Action Total Resp
Time in s
of RFC Load
Avg Response
Time
Avg CPU Time
Avg DB Time
Avg Roll Wait Time
PRD RK2A1000_POST 892 1996 13097 147 87 20
PRD VF01 491 1099 25854 8767 14305 23
PRD VA01 468 1047 8402 170 543 14
PRD SAPLARFC 256 574 10505 208 305 17
PRD CA_QUEUE_ENTRY_BCS============CP 226 505 4628 1068 1398 251
PRD VA02 178 399 6343 1215 1490 14
PRD VL71 136 304 8330 698 330 118
PRD SAP_COLLECTOR_FOR_PERFMONITOR 132 295 33749 13108 7127 188
PRD VL02N 127 284 11757 2595 7164 18
PRD VL10X 96 215 4341 553 433 10
PRD VKM1 70 157 3532 813 930 35
PRD ZSDP0049 55 124 61422 1167 1553 64
PRD STMS 52 116 18555 1911 2091 77
PRD ZP01_FROM_ZP05_944988 52 115 171827 3233 1053 03
PRD ZSDP0010 45 100 74582 31983 32785 10
PRD XD02 43 097 403 116 126 05
PRD FB1D 42 093 1999 406 1263 06
PRD FBL5N 41 091 8700 630 866 14
PRD ZP01_FROM_ZP05_942398 38 086 63795 1867 2482 65
PRD FBZ5 32 071 319430 400 510 00
Confidential Performance Overview PRD 2139
SAPreg GoingLivetrade Check - Verification Session 06082015
9 SAP System Operating PRD
The daily operation of your system was analyzed We detected some problems that may impair system operation and stability
91 Availability based on Collector Protocols
A value of 100 means that the collector was available all day Available in the context of this report means that at least one SAP instance was running If the SAP collector was not running correctly the values in the table and graphics may be incorrect To check these logs call transaction ST03N (expert mode) and choose Collector and Performance DB -gt Performance Monitor Collector -gt Log
This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR that runs every hour The job does NOT check availability it carries out only general system tasks such as collecting and aggregating SAP performance data for all serversinstances The log does not contain any direct information about availability it contains only information about the status of the hourly statistical data collection
As of SAP Basis 640 system availability information is available in the CCMS (Computing Center Management System) of an SAP System in Service Level Reporting of SAP Solution Manager
This function is provided by the relevant Solution Manager Support Packages as an advanced development For more information refer to SAP Note 944496 which also lists the prerequisites that must be fulfilled before implementation can take place
92 Update Errors
In a system running under normal conditions only a small number of update errors should occur To set the rating for this check the number of active users is also taken into consideration
We did not detect any problems
Confidential SAP System Operating PRD 2239
SAPreg GoingLivetrade Check - Verification Session 06082015
93 Table Reorganization
The largest tables andor rapidly growing tables of system PRDwere checked No standard SAP recommendations for the applicable data volume management were found
94 Program Errors (ABAP Dumps)
50 ABAP dumps have been recorded in your system in the period 30072015 to 05082015 ABAP dumps are generally deleted after 7 days by default To view the ABAP dumps in your system call transaction ST22 and choose Selection Then select a timeframe
Date Number of Dumps
30072015 19
31072015 15
01082015 0
02082015 1
03082015 4
04082015 5
05082015 6
Name of Runtime Error Dumps Server (eg) User (eg) Date (eg) Time (eg)
TIME_OUT 1 SAP1R3P_PRD_00 EMOROCHO 30072015 104804
CALL_FUNCTION_SINGLE_LOGIN_REJ 2 SAP1R3P_PRD_00 SAPSYS 30072015 170339
DYNPRO_FIELD_CONVERSION 6 SAP1R3P_PRD_00 LORTEGA 31072015 172039
DBIF_RSQL_INVALID_RSQL 5 SAP1R3P_PRD_00 PREDROBAN 02082015 060047
CALL_FUNCTION_SEND_ERROR 2 SAP1R3P_PRD_00 JPVEND 03082015 073533
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY 3 SAP1R3P_PRD_00 LORTEGA 04082015 123208
RAISE_EXCEPTION 14 SAP1R3P_PRD_00 KCASTRO 05082015 094209
CONVT_NO_NUMBER 1 SAP1R3P_PRD_00 KABARCA 05082015 143511
UNCAUGHT_EXCEPTION 1 SAP1R3P_PRD_00 CBANCHON 05082015 150325
TSV_TNEW_PAGE_ALLOC_FAILED 5 SAP1R3P_PRD_00 FLUCAS 05082015 190338
MESSAGE_TYPE_X 10 SAP1R3P_PRD_00 INTERFASES 05082015 210129
It is important that you monitor ABAP dumps using transaction ST22 on a regular basis If ABAP dumps occur you should determine the cause as soon as possible Based on our analysis we found several ABAP dumps that need your attention Evaluate and resolve the above dumps If you cannot find a solution send a customer message to SAP to request support
Confidential SAP System Operating PRD 2339
SAPreg GoingLivetrade Check - Verification Session 06082015
10 Security
Critical security issues were found in your system
See the information in the following sections
Rating Check
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
101 ABAP Stack of PRD
1011 System Recommendations (ABAP)
System Recommendations is not used at all
Recommendation SAP strongly recommends applying important security fixes as soon as possible The System Recommendations application provides a detailed recommendation regarding which SAP security notes (ABAP and non-ABAP) should be implemented based on the actual status of the system and the notes already implemented This is a mandatory prerequisite for setting up a strong security patch process For more information go to httpservicesapcomsysrec
1012 Default Passwords of Standard Users
Standard users have default passwords
Recommendation Run report RSUSR003 to check the usage of default passwords by standard users
Ensure that users SAP (must exist in all clients) SAPCPIC and EARLYWATCH have non-default passwords in all clients For more information see Protecting Standard Users either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
Make sure that the standard password for user TMSADM has been changed in client 000 and delete this user in any other client SAP Note httpsservicesapcomsapsupportnotes1414256[1414256] describes a support tool to change the password of user TMSADM in all systems of the transport domain SAP Note httpsservicesapcomsapsupportnotes1552894[1552894] shows how to update the report RSUSR003 to show the status of user TMSADM
1013 ABAP Password Policy
If password login is allowed for specific instances only the password policy is checked only for these instances
10131 Password Complexity
PARAMETER LOGINMIN_PASSWORD_LNG
Confidential Security 2439
SAPreg GoingLivetrade Check - Verification Session 06082015
Rating Instance Current Value(s) Recommended Value
sap1r3p_PRD_00 6 8
The current system settings allow a password length of fewer than 8 characters This allows weak passwords Attackers may successfully recover these passwords and gain unauthorized access to the system
Recommendation Assign a minimum value of 8 to the profile parameter loginmin_password_lng
In addition SAP provides options to enforce complex passwords Find the current settings of the corresponding profile parameters in the following table
Parameter Instance Current Value(s)
loginmin_password_digits sap1r3p_PRD_00 0
loginmin_password_letters sap1r3p_PRD_00 0
loginmin_password_lowercase sap1r3p_PRD_00 0
loginmin_password_uppercase sap1r3p_PRD_00 0
loginmin_password_specials sap1r3p_PRD_00 0
Recommendation Enforce a minimum of 3 independent character categories using the corresponding profile parameters For more information see SAP Note httpsservicesapcomsapsupportnotes862989[862989] and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
1014 Gateway and Message Server Security
10141 Kernel Patch Level
Rating Kernel Release Current Kernel Patch Level Minimal Required Kernel Patch Level
700 135 260
To enable certain gateway security functionality a minimum kernel patch level is required Your system does not currently meet this requirement
Recommendation Update the kernel of your system to the newest kernel patch level available Update to a kernel patch level equal to or higher than the minimum required kernel patch level specified above For more information see SAP Note 1298433
10142 Gateway Security
Gateway Security Properties
The parameter GWREG_NO_CONN_INFO controls the activation of certain security properties of the SAP gateway It is defined as a bit mask with one bit per property
SAP Note httpsservicesapcomsapsupportnotes1298433[1298433] ldquoBypassing security in reginfo amp secinfordquo is not activated in your system The bit mask value for bit 1 is not set
Recommendation Enable the missing property by adding the bitmask value to the current value of GWREG_NO_CONN_INFO For more information about GWREG_NO_CONN_INFO see SAP Note 1444282
Confidential Security 2539
SAPreg GoingLivetrade Check - Verification Session 06082015
1015 Users with Critical Authorizations
For more information about the following check results see SAP Note 863362
Recommendation Depending on your environment review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations You can use the User Information System (transaction SUIM) to check the results For each check you can review the roles or profiles that include the authorization objects listed in the corresponding section
10151 Users Authorized to Start all Reports
This authorization allows critical functions and reports that do not contain their own authorization checks to be executed The specified number of users for each client have the checked authorization
Client No of Users Having This Authorization No of Valid Users Rating
001 2 3
400 147 160
Authorization objects
Object 1 S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2 S_PROGRAM with P_ACTION=SUBMIT P_GROUP=
Confidential Security 2639
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
9 SAP System Operating PRD
The daily operation of your system was analyzed We detected some problems that may impair system operation and stability
91 Availability based on Collector Protocols
A value of 100 means that the collector was available all day Available in the context of this report means that at least one SAP instance was running If the SAP collector was not running correctly the values in the table and graphics may be incorrect To check these logs call transaction ST03N (expert mode) and choose Collector and Performance DB -gt Performance Monitor Collector -gt Log
This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR that runs every hour The job does NOT check availability it carries out only general system tasks such as collecting and aggregating SAP performance data for all serversinstances The log does not contain any direct information about availability it contains only information about the status of the hourly statistical data collection
As of SAP Basis 640 system availability information is available in the CCMS (Computing Center Management System) of an SAP System in Service Level Reporting of SAP Solution Manager
This function is provided by the relevant Solution Manager Support Packages as an advanced development For more information refer to SAP Note 944496 which also lists the prerequisites that must be fulfilled before implementation can take place
92 Update Errors
In a system running under normal conditions only a small number of update errors should occur To set the rating for this check the number of active users is also taken into consideration
We did not detect any problems
Confidential SAP System Operating PRD 2239
SAPreg GoingLivetrade Check - Verification Session 06082015
93 Table Reorganization
The largest tables andor rapidly growing tables of system PRDwere checked No standard SAP recommendations for the applicable data volume management were found
94 Program Errors (ABAP Dumps)
50 ABAP dumps have been recorded in your system in the period 30072015 to 05082015 ABAP dumps are generally deleted after 7 days by default To view the ABAP dumps in your system call transaction ST22 and choose Selection Then select a timeframe
Date Number of Dumps
30072015 19
31072015 15
01082015 0
02082015 1
03082015 4
04082015 5
05082015 6
Name of Runtime Error Dumps Server (eg) User (eg) Date (eg) Time (eg)
TIME_OUT 1 SAP1R3P_PRD_00 EMOROCHO 30072015 104804
CALL_FUNCTION_SINGLE_LOGIN_REJ 2 SAP1R3P_PRD_00 SAPSYS 30072015 170339
DYNPRO_FIELD_CONVERSION 6 SAP1R3P_PRD_00 LORTEGA 31072015 172039
DBIF_RSQL_INVALID_RSQL 5 SAP1R3P_PRD_00 PREDROBAN 02082015 060047
CALL_FUNCTION_SEND_ERROR 2 SAP1R3P_PRD_00 JPVEND 03082015 073533
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY 3 SAP1R3P_PRD_00 LORTEGA 04082015 123208
RAISE_EXCEPTION 14 SAP1R3P_PRD_00 KCASTRO 05082015 094209
CONVT_NO_NUMBER 1 SAP1R3P_PRD_00 KABARCA 05082015 143511
UNCAUGHT_EXCEPTION 1 SAP1R3P_PRD_00 CBANCHON 05082015 150325
TSV_TNEW_PAGE_ALLOC_FAILED 5 SAP1R3P_PRD_00 FLUCAS 05082015 190338
MESSAGE_TYPE_X 10 SAP1R3P_PRD_00 INTERFASES 05082015 210129
It is important that you monitor ABAP dumps using transaction ST22 on a regular basis If ABAP dumps occur you should determine the cause as soon as possible Based on our analysis we found several ABAP dumps that need your attention Evaluate and resolve the above dumps If you cannot find a solution send a customer message to SAP to request support
Confidential SAP System Operating PRD 2339
SAPreg GoingLivetrade Check - Verification Session 06082015
10 Security
Critical security issues were found in your system
See the information in the following sections
Rating Check
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
101 ABAP Stack of PRD
1011 System Recommendations (ABAP)
System Recommendations is not used at all
Recommendation SAP strongly recommends applying important security fixes as soon as possible The System Recommendations application provides a detailed recommendation regarding which SAP security notes (ABAP and non-ABAP) should be implemented based on the actual status of the system and the notes already implemented This is a mandatory prerequisite for setting up a strong security patch process For more information go to httpservicesapcomsysrec
1012 Default Passwords of Standard Users
Standard users have default passwords
Recommendation Run report RSUSR003 to check the usage of default passwords by standard users
Ensure that users SAP (must exist in all clients) SAPCPIC and EARLYWATCH have non-default passwords in all clients For more information see Protecting Standard Users either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
Make sure that the standard password for user TMSADM has been changed in client 000 and delete this user in any other client SAP Note httpsservicesapcomsapsupportnotes1414256[1414256] describes a support tool to change the password of user TMSADM in all systems of the transport domain SAP Note httpsservicesapcomsapsupportnotes1552894[1552894] shows how to update the report RSUSR003 to show the status of user TMSADM
1013 ABAP Password Policy
If password login is allowed for specific instances only the password policy is checked only for these instances
10131 Password Complexity
PARAMETER LOGINMIN_PASSWORD_LNG
Confidential Security 2439
SAPreg GoingLivetrade Check - Verification Session 06082015
Rating Instance Current Value(s) Recommended Value
sap1r3p_PRD_00 6 8
The current system settings allow a password length of fewer than 8 characters This allows weak passwords Attackers may successfully recover these passwords and gain unauthorized access to the system
Recommendation Assign a minimum value of 8 to the profile parameter loginmin_password_lng
In addition SAP provides options to enforce complex passwords Find the current settings of the corresponding profile parameters in the following table
Parameter Instance Current Value(s)
loginmin_password_digits sap1r3p_PRD_00 0
loginmin_password_letters sap1r3p_PRD_00 0
loginmin_password_lowercase sap1r3p_PRD_00 0
loginmin_password_uppercase sap1r3p_PRD_00 0
loginmin_password_specials sap1r3p_PRD_00 0
Recommendation Enforce a minimum of 3 independent character categories using the corresponding profile parameters For more information see SAP Note httpsservicesapcomsapsupportnotes862989[862989] and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
1014 Gateway and Message Server Security
10141 Kernel Patch Level
Rating Kernel Release Current Kernel Patch Level Minimal Required Kernel Patch Level
700 135 260
To enable certain gateway security functionality a minimum kernel patch level is required Your system does not currently meet this requirement
Recommendation Update the kernel of your system to the newest kernel patch level available Update to a kernel patch level equal to or higher than the minimum required kernel patch level specified above For more information see SAP Note 1298433
10142 Gateway Security
Gateway Security Properties
The parameter GWREG_NO_CONN_INFO controls the activation of certain security properties of the SAP gateway It is defined as a bit mask with one bit per property
SAP Note httpsservicesapcomsapsupportnotes1298433[1298433] ldquoBypassing security in reginfo amp secinfordquo is not activated in your system The bit mask value for bit 1 is not set
Recommendation Enable the missing property by adding the bitmask value to the current value of GWREG_NO_CONN_INFO For more information about GWREG_NO_CONN_INFO see SAP Note 1444282
Confidential Security 2539
SAPreg GoingLivetrade Check - Verification Session 06082015
1015 Users with Critical Authorizations
For more information about the following check results see SAP Note 863362
Recommendation Depending on your environment review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations You can use the User Information System (transaction SUIM) to check the results For each check you can review the roles or profiles that include the authorization objects listed in the corresponding section
10151 Users Authorized to Start all Reports
This authorization allows critical functions and reports that do not contain their own authorization checks to be executed The specified number of users for each client have the checked authorization
Client No of Users Having This Authorization No of Valid Users Rating
001 2 3
400 147 160
Authorization objects
Object 1 S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2 S_PROGRAM with P_ACTION=SUBMIT P_GROUP=
Confidential Security 2639
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
93 Table Reorganization
The largest tables andor rapidly growing tables of system PRDwere checked No standard SAP recommendations for the applicable data volume management were found
94 Program Errors (ABAP Dumps)
50 ABAP dumps have been recorded in your system in the period 30072015 to 05082015 ABAP dumps are generally deleted after 7 days by default To view the ABAP dumps in your system call transaction ST22 and choose Selection Then select a timeframe
Date Number of Dumps
30072015 19
31072015 15
01082015 0
02082015 1
03082015 4
04082015 5
05082015 6
Name of Runtime Error Dumps Server (eg) User (eg) Date (eg) Time (eg)
TIME_OUT 1 SAP1R3P_PRD_00 EMOROCHO 30072015 104804
CALL_FUNCTION_SINGLE_LOGIN_REJ 2 SAP1R3P_PRD_00 SAPSYS 30072015 170339
DYNPRO_FIELD_CONVERSION 6 SAP1R3P_PRD_00 LORTEGA 31072015 172039
DBIF_RSQL_INVALID_RSQL 5 SAP1R3P_PRD_00 PREDROBAN 02082015 060047
CALL_FUNCTION_SEND_ERROR 2 SAP1R3P_PRD_00 JPVEND 03082015 073533
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY 3 SAP1R3P_PRD_00 LORTEGA 04082015 123208
RAISE_EXCEPTION 14 SAP1R3P_PRD_00 KCASTRO 05082015 094209
CONVT_NO_NUMBER 1 SAP1R3P_PRD_00 KABARCA 05082015 143511
UNCAUGHT_EXCEPTION 1 SAP1R3P_PRD_00 CBANCHON 05082015 150325
TSV_TNEW_PAGE_ALLOC_FAILED 5 SAP1R3P_PRD_00 FLUCAS 05082015 190338
MESSAGE_TYPE_X 10 SAP1R3P_PRD_00 INTERFASES 05082015 210129
It is important that you monitor ABAP dumps using transaction ST22 on a regular basis If ABAP dumps occur you should determine the cause as soon as possible Based on our analysis we found several ABAP dumps that need your attention Evaluate and resolve the above dumps If you cannot find a solution send a customer message to SAP to request support
Confidential SAP System Operating PRD 2339
SAPreg GoingLivetrade Check - Verification Session 06082015
10 Security
Critical security issues were found in your system
See the information in the following sections
Rating Check
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
101 ABAP Stack of PRD
1011 System Recommendations (ABAP)
System Recommendations is not used at all
Recommendation SAP strongly recommends applying important security fixes as soon as possible The System Recommendations application provides a detailed recommendation regarding which SAP security notes (ABAP and non-ABAP) should be implemented based on the actual status of the system and the notes already implemented This is a mandatory prerequisite for setting up a strong security patch process For more information go to httpservicesapcomsysrec
1012 Default Passwords of Standard Users
Standard users have default passwords
Recommendation Run report RSUSR003 to check the usage of default passwords by standard users
Ensure that users SAP (must exist in all clients) SAPCPIC and EARLYWATCH have non-default passwords in all clients For more information see Protecting Standard Users either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
Make sure that the standard password for user TMSADM has been changed in client 000 and delete this user in any other client SAP Note httpsservicesapcomsapsupportnotes1414256[1414256] describes a support tool to change the password of user TMSADM in all systems of the transport domain SAP Note httpsservicesapcomsapsupportnotes1552894[1552894] shows how to update the report RSUSR003 to show the status of user TMSADM
1013 ABAP Password Policy
If password login is allowed for specific instances only the password policy is checked only for these instances
10131 Password Complexity
PARAMETER LOGINMIN_PASSWORD_LNG
Confidential Security 2439
SAPreg GoingLivetrade Check - Verification Session 06082015
Rating Instance Current Value(s) Recommended Value
sap1r3p_PRD_00 6 8
The current system settings allow a password length of fewer than 8 characters This allows weak passwords Attackers may successfully recover these passwords and gain unauthorized access to the system
Recommendation Assign a minimum value of 8 to the profile parameter loginmin_password_lng
In addition SAP provides options to enforce complex passwords Find the current settings of the corresponding profile parameters in the following table
Parameter Instance Current Value(s)
loginmin_password_digits sap1r3p_PRD_00 0
loginmin_password_letters sap1r3p_PRD_00 0
loginmin_password_lowercase sap1r3p_PRD_00 0
loginmin_password_uppercase sap1r3p_PRD_00 0
loginmin_password_specials sap1r3p_PRD_00 0
Recommendation Enforce a minimum of 3 independent character categories using the corresponding profile parameters For more information see SAP Note httpsservicesapcomsapsupportnotes862989[862989] and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
1014 Gateway and Message Server Security
10141 Kernel Patch Level
Rating Kernel Release Current Kernel Patch Level Minimal Required Kernel Patch Level
700 135 260
To enable certain gateway security functionality a minimum kernel patch level is required Your system does not currently meet this requirement
Recommendation Update the kernel of your system to the newest kernel patch level available Update to a kernel patch level equal to or higher than the minimum required kernel patch level specified above For more information see SAP Note 1298433
10142 Gateway Security
Gateway Security Properties
The parameter GWREG_NO_CONN_INFO controls the activation of certain security properties of the SAP gateway It is defined as a bit mask with one bit per property
SAP Note httpsservicesapcomsapsupportnotes1298433[1298433] ldquoBypassing security in reginfo amp secinfordquo is not activated in your system The bit mask value for bit 1 is not set
Recommendation Enable the missing property by adding the bitmask value to the current value of GWREG_NO_CONN_INFO For more information about GWREG_NO_CONN_INFO see SAP Note 1444282
Confidential Security 2539
SAPreg GoingLivetrade Check - Verification Session 06082015
1015 Users with Critical Authorizations
For more information about the following check results see SAP Note 863362
Recommendation Depending on your environment review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations You can use the User Information System (transaction SUIM) to check the results For each check you can review the roles or profiles that include the authorization objects listed in the corresponding section
10151 Users Authorized to Start all Reports
This authorization allows critical functions and reports that do not contain their own authorization checks to be executed The specified number of users for each client have the checked authorization
Client No of Users Having This Authorization No of Valid Users Rating
001 2 3
400 147 160
Authorization objects
Object 1 S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2 S_PROGRAM with P_ACTION=SUBMIT P_GROUP=
Confidential Security 2639
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
10 Security
Critical security issues were found in your system
See the information in the following sections
Rating Check
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
101 ABAP Stack of PRD
1011 System Recommendations (ABAP)
System Recommendations is not used at all
Recommendation SAP strongly recommends applying important security fixes as soon as possible The System Recommendations application provides a detailed recommendation regarding which SAP security notes (ABAP and non-ABAP) should be implemented based on the actual status of the system and the notes already implemented This is a mandatory prerequisite for setting up a strong security patch process For more information go to httpservicesapcomsysrec
1012 Default Passwords of Standard Users
Standard users have default passwords
Recommendation Run report RSUSR003 to check the usage of default passwords by standard users
Ensure that users SAP (must exist in all clients) SAPCPIC and EARLYWATCH have non-default passwords in all clients For more information see Protecting Standard Users either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
Make sure that the standard password for user TMSADM has been changed in client 000 and delete this user in any other client SAP Note httpsservicesapcomsapsupportnotes1414256[1414256] describes a support tool to change the password of user TMSADM in all systems of the transport domain SAP Note httpsservicesapcomsapsupportnotes1552894[1552894] shows how to update the report RSUSR003 to show the status of user TMSADM
1013 ABAP Password Policy
If password login is allowed for specific instances only the password policy is checked only for these instances
10131 Password Complexity
PARAMETER LOGINMIN_PASSWORD_LNG
Confidential Security 2439
SAPreg GoingLivetrade Check - Verification Session 06082015
Rating Instance Current Value(s) Recommended Value
sap1r3p_PRD_00 6 8
The current system settings allow a password length of fewer than 8 characters This allows weak passwords Attackers may successfully recover these passwords and gain unauthorized access to the system
Recommendation Assign a minimum value of 8 to the profile parameter loginmin_password_lng
In addition SAP provides options to enforce complex passwords Find the current settings of the corresponding profile parameters in the following table
Parameter Instance Current Value(s)
loginmin_password_digits sap1r3p_PRD_00 0
loginmin_password_letters sap1r3p_PRD_00 0
loginmin_password_lowercase sap1r3p_PRD_00 0
loginmin_password_uppercase sap1r3p_PRD_00 0
loginmin_password_specials sap1r3p_PRD_00 0
Recommendation Enforce a minimum of 3 independent character categories using the corresponding profile parameters For more information see SAP Note httpsservicesapcomsapsupportnotes862989[862989] and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
1014 Gateway and Message Server Security
10141 Kernel Patch Level
Rating Kernel Release Current Kernel Patch Level Minimal Required Kernel Patch Level
700 135 260
To enable certain gateway security functionality a minimum kernel patch level is required Your system does not currently meet this requirement
Recommendation Update the kernel of your system to the newest kernel patch level available Update to a kernel patch level equal to or higher than the minimum required kernel patch level specified above For more information see SAP Note 1298433
10142 Gateway Security
Gateway Security Properties
The parameter GWREG_NO_CONN_INFO controls the activation of certain security properties of the SAP gateway It is defined as a bit mask with one bit per property
SAP Note httpsservicesapcomsapsupportnotes1298433[1298433] ldquoBypassing security in reginfo amp secinfordquo is not activated in your system The bit mask value for bit 1 is not set
Recommendation Enable the missing property by adding the bitmask value to the current value of GWREG_NO_CONN_INFO For more information about GWREG_NO_CONN_INFO see SAP Note 1444282
Confidential Security 2539
SAPreg GoingLivetrade Check - Verification Session 06082015
1015 Users with Critical Authorizations
For more information about the following check results see SAP Note 863362
Recommendation Depending on your environment review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations You can use the User Information System (transaction SUIM) to check the results For each check you can review the roles or profiles that include the authorization objects listed in the corresponding section
10151 Users Authorized to Start all Reports
This authorization allows critical functions and reports that do not contain their own authorization checks to be executed The specified number of users for each client have the checked authorization
Client No of Users Having This Authorization No of Valid Users Rating
001 2 3
400 147 160
Authorization objects
Object 1 S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2 S_PROGRAM with P_ACTION=SUBMIT P_GROUP=
Confidential Security 2639
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
Rating Instance Current Value(s) Recommended Value
sap1r3p_PRD_00 6 8
The current system settings allow a password length of fewer than 8 characters This allows weak passwords Attackers may successfully recover these passwords and gain unauthorized access to the system
Recommendation Assign a minimum value of 8 to the profile parameter loginmin_password_lng
In addition SAP provides options to enforce complex passwords Find the current settings of the corresponding profile parameters in the following table
Parameter Instance Current Value(s)
loginmin_password_digits sap1r3p_PRD_00 0
loginmin_password_letters sap1r3p_PRD_00 0
loginmin_password_lowercase sap1r3p_PRD_00 0
loginmin_password_uppercase sap1r3p_PRD_00 0
loginmin_password_specials sap1r3p_PRD_00 0
Recommendation Enforce a minimum of 3 independent character categories using the corresponding profile parameters For more information see SAP Note httpsservicesapcomsapsupportnotes862989[862989] and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide
1014 Gateway and Message Server Security
10141 Kernel Patch Level
Rating Kernel Release Current Kernel Patch Level Minimal Required Kernel Patch Level
700 135 260
To enable certain gateway security functionality a minimum kernel patch level is required Your system does not currently meet this requirement
Recommendation Update the kernel of your system to the newest kernel patch level available Update to a kernel patch level equal to or higher than the minimum required kernel patch level specified above For more information see SAP Note 1298433
10142 Gateway Security
Gateway Security Properties
The parameter GWREG_NO_CONN_INFO controls the activation of certain security properties of the SAP gateway It is defined as a bit mask with one bit per property
SAP Note httpsservicesapcomsapsupportnotes1298433[1298433] ldquoBypassing security in reginfo amp secinfordquo is not activated in your system The bit mask value for bit 1 is not set
Recommendation Enable the missing property by adding the bitmask value to the current value of GWREG_NO_CONN_INFO For more information about GWREG_NO_CONN_INFO see SAP Note 1444282
Confidential Security 2539
SAPreg GoingLivetrade Check - Verification Session 06082015
1015 Users with Critical Authorizations
For more information about the following check results see SAP Note 863362
Recommendation Depending on your environment review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations You can use the User Information System (transaction SUIM) to check the results For each check you can review the roles or profiles that include the authorization objects listed in the corresponding section
10151 Users Authorized to Start all Reports
This authorization allows critical functions and reports that do not contain their own authorization checks to be executed The specified number of users for each client have the checked authorization
Client No of Users Having This Authorization No of Valid Users Rating
001 2 3
400 147 160
Authorization objects
Object 1 S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2 S_PROGRAM with P_ACTION=SUBMIT P_GROUP=
Confidential Security 2639
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
1015 Users with Critical Authorizations
For more information about the following check results see SAP Note 863362
Recommendation Depending on your environment review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations You can use the User Information System (transaction SUIM) to check the results For each check you can review the roles or profiles that include the authorization objects listed in the corresponding section
10151 Users Authorized to Start all Reports
This authorization allows critical functions and reports that do not contain their own authorization checks to be executed The specified number of users for each client have the checked authorization
Client No of Users Having This Authorization No of Valid Users Rating
001 2 3
400 147 160
Authorization objects
Object 1 S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2 S_PROGRAM with P_ACTION=SUBMIT P_GROUP=
Confidential Security 2639
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
11 Software Change and Transport Management of PRD
Software change management issues were found in your system
See the information in the following sections
111 SAP Netweaver Application Server ABAP of PRD
Rating Check Performed
Number of Changes
1111 Number of Changes
Performing changes is an important cost driver for the IT department It is only acceptable to make a large number of software and configuration changes in exceptional situations such as during go-live for an implementation project No data from the managed system could be found in the configuration and change database (CCDB) Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465 Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services The CCDB data is required here to check the configuration of the managed system
Confidential Software Change and Transport Management of PRD 2739
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
12 Data Volume Management (DVM)
A statement regarding Data Volume Management on your system PRD could not be provided
This report does not have a Data Volume Management (DVM) section because the collection of DVM-relevant data has not been activated for your system PRD See SAP Note httpsservicesapcomsapsupportnotes2036442[2036442] for more information about how to activate the DVM content for service reports Once the DVM content has been activated information about the current state of your system PRD regarding Data Volume Management is provided along with proposals about how to reduce the database size of this system
As a workaround an attempt was made to check the database size and growth per year for your system PRD However the database size or growth per year could not be collected As a consequence a statement regarding Data Volume Management in your system PRD could not be provided
Confidential Data Volume Management (DVM) 2839
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
13 ABAP Stack Configuration for PRD
The SAP configuration checks cover the correct parameter settings for each SAP instance SAP parameters are important for ensuring the stability and performance of an SAP instance
Procedure 1 Use transaction RZ10 to maintain SAP profile parameters Note that warnings and error messages may occur Refer to the recommendations provided in this report and ignore these messages Recommendations in this report are carefully checked by your service consultant and overrule the standard checks provided by RZ10
2 Before starting the SAP instance with the new parameter settings run program SAPPFPAR (see SAP Note 166551) If any errors occur here save the output file and contact your service center for advice Restore the old parameter settings and restart the SAP instance
Note If the recommended value of any parameter in the following list is set to ltto be deletedgt delete the parameter from the parameter profile Do not simply change the parameter value to space For additional background information see FAQ Note 1979791
131 Configuration for Central ABAP Instance sap1r3p_PRD_00
Recommendation Adjust the SAP instance parameters as required in profile usrsapPRDSYSprofilePRD_DVEBMGS00_SAP1R3P
1311 Buffer Configuration
Parameter Description Current Value Recommendation
rsdbntabftabsize Field Description Buffer - Size 90000 120000
abapbuffersize Program Buffer - SizeEntries 900000 1200000
zcsapresentation_buffer_area Screen Buffer - Size 12592128 20000000
sapbufdir_entries Screen Buffer - Entries 2000 10000
zcsacalendar_ids Calendar Buffer - Entries 200 250
zcsatable_buffer_area Generic Table Buffer - Size 102400000 160000000
zcsadb_max_buftab Generic Table Buffer - Entries 5000 10000
rtbbbuffer_length Single Record Table Buffer - Size 50000 60000
rsdbobjmax_objects Ex-Import Buffer - Entries 8000 20000
1312 Client Server Communication
Parameter Description Current Value Recommendation
rdispmax_arq Max number of internal asynchronous messages 500 2000
gwmax_conn Max number of active connections 500 2000
rdisptm_max_no Max number of entries in array tm_adm 500 2000
rdispmax_comm_entries Max number of communication entries 500 2000
gwmax_overflow_size Max swap space for CPIC-requests in the gateway 10000000 25000000
gwmax_sys Max number of connected clients 300 2000
1313 Enqueue Handling
Recommendation Adjust the following parameters For more information see helpsapcom Important Profile Parameters for the Lock Concept Profile Parameters for the Enqueue Clients
Confidential ABAP Stack Configuration for PRD 2939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
Parameter Description Current Value Recommendation
enquetable_size Size of lock table 4096 20480
1314 Obsolete Codepage Parameters
Recommendation The following codepage parameters were found in your profiles and should be deleted For details refer to SAP Note 1345121
Parameter Description Current Value Recommendation
installcodepageappl_server Code pages installed on the application server 4102 ltTo be deletedgt
Confidential ABAP Stack Configuration for PRD 3039
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
14 IBM i Database Checks
Your IBM i database was analyzed with respect to the state of the database administration database setup and potential hardware problems
We have detected some problems that may have an impact on system operation and performance To ensure system stability you should take corrective action as soon as possible
Rating Check
Missing Indexes
Disk arm utilization
Backup Strategy
Reorganize Physical File Member
141 Important SAP Notes for IBM i
SAP Note Number Description
121625 AS400 Buffer sizes
428855 OS400 System values
517515 iSeries When to use ASP balancing
654801 iSeries ASP configuration of the database for ABAP and Java
789188 INST SAP Web AS 640 SR1 on IBM eServer iSeries
1083218 iSeries Analysis of plan cache for DB2 on i5OS
142 Reorganize Physical File Member
A large number of deleted records have been found in the system
Recommendation Run the command RGZPFM (SAP Note 84081) to release this disk space
Table Name Deleted
DBTABLOG 45
143 Missing Indexes
No missing indexes were found This means that the indexes defined in the SAP Data Dictionary are the same as those defined in the IBM i system catalog
144 Disk arm utilization
The table shows the top 10 disks with the greatest utilization in descending order The information is collected based on 24 hours of data and the hour of peak utilization is shown in the Time column The name of the disk the utilization and the time are shown A YELLOW rating is set automatically if the utilization is greater than 40
We have checked the disk arm utilization on the database server of the ASP system (ASP01) We did not detect busy rates that could cause an IO bottleneck
145 Database Size
Confidential IBM i Database Checks 3139
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
The table lists the current size of the database
Number of tables Number of primary keys
Number of indices
Size of tables [MBytes]
Size of primary keys [MBytes]
Size of indices [MBytes]
Total size of database [MBytes]
69041 69039 13576 1169642 117113 84159 1370914
146 Backup Strategy
Backup Date Time Status
Full 06082015 032003 Complete
Full 05082015 032123 Complete
Full 04082015 032042 Complete
Full 03082015 024309 Complete
Full 31072015 025229 Complete
Full 30072015 025107 Complete
Full 29072015 025147 Complete
The Backup Overview in the table above shows when the last complete backup was performed
Confidential IBM i Database Checks 3239
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
15 IBM i Specific Server Checks Your IBM i server was analyzed with respect to the state of the server administration parameter setup and potential problems
In the checks performed major problems regarding the administration of your server were found
Rating Check
iASP Configuration Check
Data Protection in System ASP
Disk Status for Server
IBM i Maintenance end
Free space in System ASP
IBM i PTF Check
Disk Service Time
Check for transitions to Ineligible states
Paging Option
INTERACT Pool
SHRPOOL Pool
IBM i System Values
151 iASP Configuration Check
During this service session no iASPs (independent ASPs) were detected
152 Disk status
During the session we were unable to automatically detect disks that do not have active status
Recommendation Investigate the status of your disks and contact IBM Technical Support to replace any failed disks as soon as possible
153 Data Protection in System ASP (ASP1)
During the session we were unable to check your disk protection If you have no disk protection and one disk fails all the data in the entire ASP will be lost
Recommendation Activate at least RAID5 disk protection
Note When you activate disk protection you need more disk space For RAID5 12-25 extra disk space is required for RAID1 100 extra disk space is required
154 Free space in System ASP (ASP1)
To ensure satisfactory system performance we recommend that you limit the filling ratio of system ASP to 80 In addition the system needs up to three times the size of the main memory as paging space in system ASP If you anticipate database growth provide even more freespace in system ASP of the database server
Confidential IBM i Specific Server Checks 3339
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
ASP-name Capacity [MB] Free space [MB] Free space []
0 0 0
Not enough free space is available in the ASP system (ASP1) of database server YSAP-DB_SVR
Recommendation Reorganize the data analyze the disk usage (by saving and deleting unused objects for example) and archive the data
Background When AS400 reaches the limits of the ASP system the system no longer works The only solution at this point is to perform an IPL which causes unplanned system downtime and possible data loss
155 PTF Check
Corrections from IBM are already available in the form of PTFs for many problems that occur in the IBM i operating system or in the IBM i database All recommended PTFs for the individual IBM i releases are listed in Info APARs for R3 To ensure that no new problem messages are written for problems that have already been corrected the current PTF status of your IBM i installation should be compared regularly with the corresponding Info APAR
Recommendation Install the latest Info APAR from IBM in your system To compare the latest PTF status of the system with the relevant IBM Info APAR for R3 use the command CHKR3PTF (SAP Note 144149) The PTF status can also be read from ST06 or using transaction DB4PTFCHK For more information and details about possible problems see SAP Notes 497799 and 709533
156 Disk Service Time
We checked the disks on your system ASP for a high service time We did not detect any issues that might indicate an IO performance issue
157 IBM i System parameters
Recommendation Set the following IBM i parameters to the recommended values For more information see SAP Note 428855
Parameter Description Current Value Recommendation
QBASACTLVL Base storage pool activity level 57 (See SAP Note 428855)
Parameter Description Current Value Recommendation
QMAXACTLVL Maximum activity level of system 32767
QMCHPOOL Machine storage pool size 0 or ~10 of Available memory
QDYNPTYSCD Dynamic priority scheduler 1
QPFRADJ Performance adjustment See SAP Note 49201
QSECURITY System security level Either 30 or 40
QQRYTIMLMT Query processing time limit NOMAX
QACTJOB Initial number of active jobs 1000
QADLACTJ Additional number of active jobs 500
QTOTJOB Initial number of total jobs 1000
QADLTOTJ Additional number of total jobs 1000
QQRYDEGREE Query parallel processing degree NONE
Confidential IBM i Specific Server Checks 3439
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
158 SHRPOOL Pool
Recommendation Check whether you need a separate SHRPOOL for your system
Background Since the SAP system runs in the BASE memory pool the SHRPOOL can be removed if it is not required However if you have a Java engine installed on an ABAP server it is generally very useful to create and use an additional SHRPOOL memory pool for the SAP Java workload see SAP Note 1023092
159 Paging Option
During the session we were unable to automatically check the paging option for the memory pool in which the SAP system runs
Recommendation Ensure the paging option is set to CALC for the memory pool where the SAP system runs With the paging option CALC the system dynamically adjusts the paging characteristics of the storage pool for optimum performance You can change the paging option using the command WRKSYSSTS and typing the new value into the Paging Option field
Confidential IBM i Specific Server Checks 3539
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
16 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs) Diagrams are built weekly once the EarlyWatch Alert service is activated In this report historical data for Transaction Activity System Performance and Database Performance is taken directly from workload monitor ST03 because EarlyWatch Alert data has been accumulated for less than 20 sessions
In this section a week is from Monday to Sunday The date displayed is the Sunday of the week
161 System Activity
The following diagrams show the system activity over time
The Transaction Activity diagram below depicts transaction activity in the system over time
- Total Activity Transaction steps performed each week (in thousands)
- Dialog Activity Transaction steps performed in dialog task each week (in thousands)
- Peak Activity Transaction steps (in thousands) during the peak hour this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 working days per week (Peak Activity is absent if Activity Data is taken from ST03 data directly)
Historical data for Transaction Activity is obtained from the Workload Monitor (ST03)
The User Activity diagram below shows the user activity on the system over time
- Total Users Total users that logged on in one week
- Active Users Users who performed more than 400 transaction steps in one week
Confidential Trend Analysis 3639
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
162 Response Times
The following diagrams show how the response time varies over time
The System Performance diagram below shows the average response time in dialog tasks for the previous week
Historical data for System Performance is obtained from the Workload Monitor (ST03)
The Database Performance diagram below shows the average DB response time in dialog tasks
The Top 5 transactions diagram below shows the average response time in dialog tasks for the top 5 transactions
The Transaction Code table below shows the load percentage caused by the top 5 transactions
Transaction Code Load ()
VL71 105
VA02 61
FBL5N 57
VA01 55
ZSDP0023 38
163 Application profile
In the following we analyzed the trend within the following time frames Short term From calendar week 312015 to 312015 Long term From calendar week 292015 to 312015
The table below shows the time profile of the top applications by total workload during the analyzed period
TOP APPLICATIONS BY RESPONSE TIME
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog VL71 7840 10 19121 17694 17694 16826 11240
Confidential Trend Analysis 3739
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
Task Type Application Total Resp Time in s
of Total Load
Avg Resp Time in ms
Long Term Growth
(year)
Short Term Growth
(year)
Avg DB Time in ms
Avg CPU Time in ms
Dialog FBL5N 5495 7 516 -6198 -6198 164 176
Dialog VA01 4862 6 636 -3982 -3982 152 211
Dialog ZWMSCP01 3453 4 7708 -7879 -7879 1194 1407
Dialog VA02 3344 4 478 -1719 -1719 129 187
Dialog ZSDP0013 3138 4 16259 -20833 -20833 15207 3698
Dialog VT01N 2955 4 4498 -14874 -14874 493 2258
Dialog ZSDP0023 2906 4 2469 -4113 -4113 2004 211
Dialog SESSION_MANAGER 2436 3 580 -9088 -9088 117 75
Dialog ZSDP0063 2043 3 15023 -21369 -21369 1258 7729
Dialog VKM1 1941 2 1158 -11512 -11512 477 305
Dialog F13 1905 2 8619 -20556 -20556 1275 2863
Dialog ZMMQ0008 1840 2 11645 00 00 4871 5320
Dialog VA03 1827 2 406 -4240 -4240 114 115
Dialog ZVC2 1720 2 290 -7524 -7524 196 68
Dialog ZSDP0047 1317 2 3795 -15894 -15894 2853 1430
Dialog ZMIRO 1275 2 553 -4055 -4055 107 194
Dialog FB50 1196 1 1663 -13103 -13103 61 64
Dialog FBL3N 1101 1 280 -1785 -1785 100 93
Dialog ZSAPPDF 1019 1 8154 -1579 -1579 71 347
The graph below shows how the average response time of the top five applications varies over time Data is normalized to 100 equaling the average value
164 System Operation
The following diagram or table shows important KPIs for system operation
Confidential Trend Analysis 3839
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939
SAPreg GoingLivetrade Check - Verification Session 06082015
165 Hardware Capacity
The following diagram or table shows the maximum CPU load from the database server and all application servers
Report time frame Service data was collected starting at 06082015 133018 This took 5 minutes
Confidential Trend Analysis 3939