ania Howto run SAP SMSO'SMBG fo monitor SAP work process | sap-pertca sap-perf.ca How to run SAP SM50/SM66 to monitor SAP work process Posted on Saturday October 27th, 2012 This post would talk about how to run SAP SMSO and SM66 transaction, understand information from SAP SMSO and SM66 screens and what SAP SMSO and SAP SM66 can help in performance monitoring and analysis. SAP work process is a limited oritical system resource for performance like CPU and memory. Number of work processes and type of work processes on a SAP instance are controlled via SAP basis configuration. Any online transaction or background job is executed using one or multiple SAP work processes in sequence or in parallel dependent on program function and design: Running SAP transaction VAQ3 online to display sale order would need only one SAP dialog work process while running va01 online to create sales order online ‘would need one dialog process and one update process; One background job would always Use at least one background process. One background job which uses parallel processes via RFC call would need one or more dialog process as well ‘SAP SMSO and SME6 transaction provides capabilities to monitor overall status of SAP work process and status of indivdual SAP work process. So you know: 1. Overall system activities/load, 2. System work process status. 3. Individual job or online transaction execution status. 4, Memory/CPU usage of individual job or transaction wn sop- pet caltn-sap- Administration > Monitor ->System Monitoring > Process Overview. The initial SAP ‘SM50 transaction screen is a SAP work “Process Oveniew’ screen which shows status of all configured sap work processes on the current senver you are in, Double click any work process entry on the overview screen, you would see “Details Display” screen for single selected work process. That is simple, Following is a part of SAP SM50 Work process overdew screen which is showing status of all configured SAP work processes | manipulated the display to show all typical types of work process in an application instance @ Background(BGD), Dialog(DIA), Update(UPD & UP2). Figure 1-SM50 Process Overview Following is two parts of Work process details screen which shows further information on a single work process e wn sone per caltu-sap-sm0-s8) aneans How o ran SAP SMEO'SMBB to monitor SAP erkarocess | cap por.ca Detail Display 'G) Retresh 14 BoD 1812 Running Yes 21:38 1530428 @BCADH ZTAGR_WRMN_EXTRACTOR Zpake_emm_EXTRACTOR Direct Read MARA Direct Read 611,07 430038664 306,082 Roll In o o Roll Out 8 8 Roll 8 (Bytes) Page @ (Bytes) Memory (Total) © (Bytes) Memory (Total Private) 8 (Bytes) Memory (used) 8 (Bytes) Memory (Max. Transaction) 8 (Bytes) Memory (Max. Dialog Step) © (Bytes) Load Screen 9 (Bytes) reooo Figure 2— SAP SM50 Process Details wn sop- pet caltn-sap- Restart After Error-> Yes or No. Restart work process after dump? Indicates whether the terminated work process should be automatically restarted in by he dispatcher, The following values are possible: Yes : The work process is restarted No@@: The work process is not restarted (for example, if errors occur during the initialization phase). ‘You can set the work process by choosing Process -> Restart Aller Error-> Yes or No, ‘Semaphore that the work process is waiting for ‘SAP number of the semaphore which blocks the work process: It the field is green, the work process is holding the semaphore in question, the field is red, the work process waits for the semaphore in question. The numbers stand for the following semaphores @01: PXAsemaphore @02: WP_CA_ADMsemaphore @@3: APPC_CA_ADMsemaphore @04: TM_ADMsemaphore @@5:COMM_ADMsemaphore ©6: ROLL_ADMsemaphore ©7: PAGING semaphore ©08:NO_BUFFER semaphore ©09: STAT semaphore wn sop- pet caltn-sap-, then the work process, does not execute an ABAP program but a kemel action. The following values are possible: Display Explanation buffer syne> SAP database buffer refrosh ‘Auto ABAP auto th processing> Auto taskhandler ‘Administration message (ADM) Starts extemal program Update control Statistics administration DDLOG-Cleanup Delayed function Program generation Action Description of the action that the work process is currently executing Display Meaning Rall In /Roll Out, Load or save user context TOK Access ‘Access to SAP pool table Read directly Read operation on the database wn sep- pet caltn-sap-sn60-sm6) seania Sequential read Physical read Insert/ Update / Delete / Commit/ Phys. Insert / Phys. Update / Phys. Delete ‘SQL Prepare / Open Generate /@@Load report/ Load CUA/ Load dynpro Queue API Read dictionary pic Read / update matchcode Insert/delete DB Procedure AD Opcode ° Howto run SAP SMSO'SMBG fo monitor SAP work process | sap-pertca eo °e Changing operations on the database ‘SQL operations ‘SAP runtime operations °e Execute queue operations °e Communication Matchcode operations °e Execute database procedures Execute SAP kemel internal administrative functions Read directly and Sequential read - in SAP SMSO, "Read directly’ means that only cone record would be retumed by the database. Reading a table via a full keyand return one record is a “direct read’. Counting number of records which meet certain conditions would return one “number", such operation would be displayed as “direct read” in SM5O.Any other read is a "sequential read’. For example, SMSO would show “Sequential Read” when you read a table with full primary key but multiple records are returned by the database due to "OR" or"IN' or SELECT-FOR-ALL selection wn sop- pet caltn-sap-= [| _‘|sec Runtime >= sec Application selection Dialog Transaction Function Code ‘Screen Report (CUA) Reporting Report Job User seleation ‘dion selection Client Action Username ontable ‘SM66 display can be sorted according to your need @ like runtime, process type, table name ete From SM66 display screen, you can admin existing work process and start debugging as well 5. Further clarification SAP transactions are always subject to changes. Your SM50/SM66 display, layout might be different from what is showed here but Usage of SMS50 and SM66 should be the same. The process ID showed in SMSO and SM66 is the key for linking to database load session monitor(STO4 ) and CPU load monitor (OS06/OSO7/ST06). This is useful when information from SMSO/SM66 is not enough and you need further information like what provided by STO4 and OS06. wn sone per caltu-sap-sm0-s8) wienis vionorn SAP SSoSHOs te SAP kr spe Bow oc Hs This entry was posted in SAP transaction and tagged How to run SAP SM50 and SM66 transaction;SAP work process monitor; SAP SM50; SAP SM66; Difference between SAP sm50 and sm66; understand SAP SMS0 and SM66 screen by eric. Bookmark the permalink [http://www.sap-perf.ca/run-sap-sm50-sm66/] 2 THOUGHTS ON ‘HOW TO RUN SAP SMSO/SM66 TO MONITOR SAP WORK PROCESS sua chua ipad on Sunday December 16th, 2012 at 06:50 PM said: I don't even know how | ended up here, but | thought this submit was good, | don't recognise who you are but certainly you're going to a famous blogger should you are not already. Cheers! suam ipad on Saturday December 15th, 2012 at 06:52 PM said: Heya i am for the first time here. | found this board and I find It truly useful & it helped me out a lot. 'm hoping to offer something back and aid others like you aided me. wn sone per caltu-sap-sm0-s8)