1

Level 2 Training Table of Contents

No 1 2 3 Topic
Lock Entries (SM12) Update records (SM13) System Log (SM21)

Tasks Check and analyze unreleased Database Locks Check and analyze failed database updates

Page 2 4

Check and analyze SAP System Lo for any critical lo entries !

Background o!s (SM3")

Check and analyze failed Background Jobs to determine the cause of the termination
Check and analyze the System #ork$Process o%er%ie& for errors as &ell as the CP' usa e of the &ork$process Check and analyze failed Print )obs

11

"

#orkprocess (SM$%) Printer &ueues (SP%1) Bu''ers (ST%2) (B(P )umps (ST22)

13

( * !

1* Check and analyze buffer statistics and s&aps 2+ Check and analyze SAP A,AP Short Dumps 2"

207623304 doc

30!01!2014

1. Check and analyze unreleased database locks (SM12)

A -lock. is a mechanism that pre%ents other users from chan in the record on &hich you are &orkin / 0he e1ample belo& illustrates the importance of usin this function/ 2 /

You are changing a customer mailing address, while someone is simultaneously changing the customers telephone number. You first save your change; then the other person saves his or her change. The other persons change overwrites your change, and your change will be lost.

1/ 3n the Command field4 enter transaction S512 and choose 2nter 6or from the SAP standard menu4 choose 0ools 7 Administration 7 5onitor 7 S512$Lock entries8/ 2/ 3n Client enter 9/ 3/ Clear the 'ser name field/ 4/ Press 2nter/ "/ 3n the 0ime column4 look for locks from pre%ious days/ *utput +

207623304 doc

30!01!2014

3 Analysis (SM12) :
0he easiest &ay to locate for locks is to look for locks from prior days. 0hese locks are problematic because it prevents access or changes to the locked record.

,auses o' unre-eased -ock entries + 1/ Sudden po.er 'ai-ures 2/ 'ser &as disconnected from the network and the R/3 System/ 3/ Pro!-ems pre/enting Update 3f a problem is pre%entin the update4 the locks enerated by the update &ill not be released/ Locks set by the update function are maintained by the system until the database change has been processed or terminated prematurely. Check transaction S513 for further details on the update problems/ 4/ Premature S(P0U1 termination/ 3f a user s&itches off the PC &ithout first lo in off4 or if the SAP:'3 pro ram is terminated prematurely for some reason4 the user may remain lo ed onto the SAP System/ 0he locks held by the user &hen the problem occurred are not released/

2e-easing t3e -ock + The following process can be followed to release a lock !. "re there any processes running under the user !#$ % Transaction S&'( !!. "re there batch )obs running under the user !#$ !!!. "re there any updates in process for that user !#$ % Transaction S&3* %Transaction S&+3

Check if there is any u"dates in "rocess for this user

iv. !s the user logged on any of the servers$ % Transaction S&,- or Transaction ".(/

0heck when the user was last active in the system if you can see the user under SM04. If the user was not active for a long time, he or she may have shut down the PC without completing his/her wor or S!P"#I may have terminated prematurely. $ou can release the lock by logging off the user %under SM04& 'ut ma e sure there is no activity using the user(s I) %!nswers are *+ for the ,uestions i - iii&..his will release the lock. /owever, you have to delete the lock if you still see loc entries after logging off the user.

)e-eting a -ock + Deletin a lock is a dan erous task/ Do not delete a lock &ithout checkin first to see if it is bein used/ 3f you delete a lock that is in use4 you risk corrupting the database 1data loss 2 inconsistencies3. ;nce you kno& that there is no acti%ity usin the user<s 3D %answers are *+ for the ,uestions %i 0 iii&& 4 select the lock entry for deletion/ =rom the menu bar4 choose .ock entries 4 #elete/ 0lear only one lock entry at a time. #o not use the mass delete option 1 1oc entry )elete all&. This option will delete all the locks5 not )ust the ones for the user you have selected /

207623304 doc

30!01!2014

2. Check and analyse failed database updates (SM13)

#n u"date terminate $or failed u"date% is an u"date to the database that failed &hese terminates occur when a user entry or transaction is not entered or updated in the database. 'or "erformance reasons( the database u"date is done in an asynchronous mode. )n this mode( the user continues to *ork *hile the system takes o+er the u"date "rocess and *aits for the database u"date to com"lete )n a synchronous mode( users *ould ha+e to *ait until the database has successfully u"dated before they could continue to *ork
Check the system for failed updates se%eral times a day/ Durin a dayshift4 the checks can be distributed> ? =irst thin in the mornin ? Late mornin ? 2arly afternoon ? Late afternoon

3n the Command field4 enter transaction S513 and choose 2nter 6 2efer )iagram8 6or from the SAP standard menu4 choose 0ools 7 Administration 7 5onitor 7 S513$'pdate8/ 3n Client enter 9/ 3n 'ser enter 9/ 'nder Status4 select All/ 3n =rom date4 chan e the date to pre%ious day/ Choose 3n the Status column4 look for entries &ith an Err4 0hese entries are failed updates or update terminates/

207623304 doc

30!01!2014

207623304 doc

30!01!2014

6 Analysis (SM13) :
Updates .it3 5Err6 status can !e caused !y t3e 'o--o.ing + i. #atabase overflow Database table has reached its ma6 e6tents causin the updates to be stopped@delayed/ :o to SAPD,A and add table space to the table that is runnin critical 6usually A+BC8/ ii. 7ot enough free space in "rchive directory. Chec availa'le free space in the archive directory. iii. Server disconnected from network. Derify if update status is acti%e as sho&n belo& >

3f status is not acti%e4 troubleshoot for network problems and make sure the ser%er is in the net&ork/

Change back the status to acti+e

iv. 8rogram errors

Double$click on an entry &ith an 9rr status/

207623304 doc

30!01!2014

0his screen sho&s in &hat module 1&od.name3 and &here in the process 1&od.!#3 that the update terminate occurred/ Eo& double click on the entry &ith error4 the output &ill look like >

0he abo%e e1ample tells you a =;F54 hence a SAPScript4 is not acti%ated/ Additionally4 the =;F5 in Guestion is a H94 or customer =;F5/ Contact the =unctional Area 21pert to determine &hat =;F5 to acti%ate or transport to the system/ E;02> Eot all update error solutions are found this easily or Guickly/ Iou may ha%e to di deeper 1S&:+ System .og5 ST:: #ump "nalysis5 #;(: #; Storage5 database alert log3 and &ork &ith the =unctional Area 21pert to resol%e the issue/

207623304 doc

30!01!2014

=irst4 ask the user to re<key the data/ 3f the user can re$key4 then it is okay to delete the update record %update records 3 delete 3 single&. 3f the ori inal &ork &as not posted4 the user may be able to repost/ 3f the ori inal &ork &as posted4 but there is a missin final step4 the user &ill ha%e to re%erse the document and then repost/ 3f the user cannot re$key4 %erify the fi1 really &orked/ 0hen you can use the 'pdate A ain function to reprocess a D1 update/ ,e certain that no other chan es &ere made to the database obJect after the failed update occurred/

0he lon er you &ait after the update terminate has occurred4 the more difficult it is for users to remember &hat they did &hen the update terminate occurred/ 3f you &ait too lon 4 the user &ill not remember/ Iou mi ht consider configuring an event log monitor to page you when an update terminate occurs / 0his step reduces the need to constantly check transaction S513/ 3t also reduces the e1posure bet&een the time the update terminate occurs4 &hen you find out about it4 and &hen you can et to the user/ 0he follo&in messa e appears> -Iou ha%e e1press mail in you inbo1/.

#o not attempt to reapply the failed update= 0here are conditions under &hich this reapplication can lead to corruption of the database.

207623304 doc

30!01!2014

3. Check and analyze SA syste! lo" (SM21)

0he system lo is the F@3 System<s lo of e%ents4 errors4 problems4 and other system messa es/ 0he lo is important because une1pected or unkno&n &arnin s and errors could indicate a serious problem/ 0he ability to properly monitor the system lo comes &ith e1perience/ ;%er time4 you &ill become familiar &ith &hat lo entries -normally. appear in your system lo 4 and pick out the unusual ones that need in%esti ation/

*ptions
System log entries imported Reread system log

)escription
Sho&s ho& many lo entries the system has read from the lo file/ #hen you first enter the System Lo initial screen4 this field is set to +/ Choose 2eread system log to read the lo / 0he system then reads in entries from the lo file so that you can display them/ ;y default5 the system reads the log for the last one to two hours. Choose 2edisplay only to %ie& the last system lo you displayed/ 3f you like4 you can use the Selection options alon &ith this button to refine the old system lo data &ithout re$readin the lo / 'se this option if you &ant to retain the data from this last read4 but &ant to reread the system lo &ith different selection criteria/ 0his option lets you mi1 the information from an ori inal lo access &ith a second lo access into one list/

Redisplay only

Read in Sys.og

207623304 doc

30!01!2014

10
Procedure + 3n the Command field4 enter transaction S521 and choose 4nter/ 6refer dia ram8 2nter the be innin date and time that you &ant to re%ie& from the lo in 5rom date/time/ Iou can also enter an end date and time if you &ant to %ie& a specific time period/ Choose 2eread system log/ 0o make re%ie&in the lo easier4 under Pro'lem classes select one of the follo&in 4 one at a time> K Pro'lems only K Pro'lems and warnings K !ll messages

*utput +

207623304 doc

30!01!2014

11

Analysis (SM21) :
1/ Look for unusual entries. ,ut4 before you can reco nize the unusual entries4 you &ill need to become familiar &ith -normal. entries/ 9rrors are in red and pink5 and warnings are in yellow. 2. Iou can display detailed information on a specific entry by selectin the entry and choosin 9dit #etails or 'y double clicking on the error message. 3. 'se 9dit "naly>e errors to display a detailed error analysis in the detailed %ie& if short dumps or runtime errors ha%e occurred/ Iou can use the System 1og Sort function to sort a lo report by %arious criteria/

207623304 doc

30!01!2014

12

#. Check and analyze failed back"round $obs (SM3%)

,ack round Jobs are batch Jobs scheduled to run at specific times durin the day/ 3f you are runnin critical Jobs4 you need to kno& if the Job failed because there may be other processes4 acti%ities4 or tasks that depend on these Jobs/

1/ 3n the Command field4 enter transaction S53* and choose 2nter 2/ 3n )ob name4 enter 9 to et all Jobs/ 3/ 2nter one of the follo&in options> ? 9 6for all users8 ? 'ser 3D that the batch Jobs run under 6to limit the display to those scheduled under a specific user 3D in 'ser name8/ 4/ 'nder )ob status4 select> ? Acti%e ? =inished ? Canceled "/ 3n =r/4 enter a start date/ (/ 3n 0o4 enter an end date/ */ 3n after e%ent4 choose and select 9/ !/ Choose 21ecute/

207623304 doc

30!01!2014

13

Analysis (SM37) :
Look for failed or cancelled )obs/ Analyze &hy Jobs failed or &ere cancelled and make the necessary corrections/ 0o analyse4 you should ha%e a list of all the critical )obs that are scheduled to run/ =or each of these Jobs4 you should ha%e a list that sho&s> i. ?hen the )obs are scheduled to run ii. The e6pected run time iii. "n emergency contact 1names and phone numbers3 for )ob failure or problems Ee1t4 you ha%e to check the )ob log/ 0o check a Job lo > +. Select the )ob. :. 0hoose @ob log. 3. 0heck )ob performance and record run times. Compare it &ith your list/ A deviation from the usual run time on a Job may indicate a problem and should be in%esti ated/

207623304 doc

30!01!2014

14

&. Check and analyze syste! 'orkprocess(o)er)ie' errors (SM&*)

Process o%er%ie& transactions allo& users to %ie& the status of &ork processes and monitor for problems/ 0ransaction S5"1 is a central transaction from &hich you can select the instance to monitor/ S5"1 starts transaction S5"+ for each application ser%er4 &hich is used for a system &ithout application ser%ers/ 0ransaction S5"+ is one place to look for Jobs or pro rams that may be -hun 4. &hich maybe indicated by lon run times/ 1/ 3n the Command field4 enter transaction S5"1 and choose 2nter 6choose 0ools 7 Administration 7 5onitor 7 System monitorin 7 S5"1$Ser%ers8/ 2/ Select the instance you &ant to %ie& 3n the Command field4 enter transaction S5"+ and choose 2nter 6choose 0ools 7 Administration 7 5onitor 7 System monitorin 7 S5"+$Process o%er%ie&8/

207623304 doc

30!01!2014

1,

Types o' .ork processes+

#ork Process Type 1 2 Dialo 6D3A8 'pdate 6'PD8

Use 21ecutes dialog programs 1";"83 Asynchronous database changes 6is controlled by a C;5530 #;FL statement in a dialo &ork process8 21ecutes time$dependent or e%ent$controlled background )obs 21ecutes locking operations 6if SAP transactions ha%e to synchronize themsel%es8 8rint formatting 6to printer4 file or database8

3 4 "

,ack round 6,:D8 2nGueue 62EM8 Spool 6SP;8

207623304 doc

30!01!2014

16

207623304 doc

30!01!2014

17 Analysis (SM50) :
?ork processes in 8R!A mode
3f you see &ork processes in 8R!A mode4 you need to analyze your memory mana ement strate ies and ser%er profile parameters/ Private mode is usually an indicator of serious or comple6 problems. 3f the F@3 &ork dispatcher determines your pro ram is too lar e for con%entional memory allocation or reGuires static addressin 4 the &ork process &ill be placed in private mode/ Additionally4 programs with comple6 reBuirements or improper coding techniGues can confuse the 2/6 memory managers and in%oke the pri%ate mode for relati%ely small tasks/ Pri%ate mode can also result from systemic overloading of e6tended memory 6that is4 too many reGuests for similar allocations8 and a host of other conditions/

The following parameters 1related to workprocesses3 can be ad)usted with t6n RC+( according to the needs of the organi>ation rdisp7.p8no8spo rdisp7.p8no8!tc rdisp7.p8no8en9 rdisp7.p8no8dia rdisp7.p8no8/! rdisp7.p8no8/!2 rdisp7ma:8.prun8time

Number of spool work processes Number of background work processes Number of lock work processes Number of dialog work processes Number of update work processes Number of update work processes for V !a"imum run time for dialog work processes #default $ %&& seconds'

207623304 doc

30!01!2014

1-

+. Check and analyze failed print $obs (S *1)

0he spool is SAP<s output mana er/ Data is first sent to the F@3 spool and then to the operatin system for printin / 0here may be problems &ith the printer at the operating system or S"8 level/ 0hese problems need to be resol%ed immediately for time$critical print Jobs 6for e1ample4 checks4 in%oices4 shippin documents4 etc/8 or there may be an operational impact/

3n the Command field4 enter transaction SP+1 and choose 2nter > 2nter 9 in the NCreated by< field/ Set the NDate created< field to4 for e1ample a &eek a o4 or to any other date ran e to check for other problems/ 0he ran e of data &ill depend on your installation/ 3f you enerate hundreds or thousands of spools a day4 you &ould choose e%ery day/ 0his data ran e &ould be much shorter4 possibly only t&o days/ Delete information in Client/ Press =! to e1ecute

207623304 doc

30!01!2014

1.

*utput +

Analysis (SP01) :
3n the NList of Spool FeGuests< screen4 scroll throu h the display and check the status of each spool reGuest under the S0A0'S column/ Look for Jobs &ith an error in the ;utput Status column/ #ouble click on the 9rror.

207623304 doc

30!01!2014

20

Fe%ie& the error/ =rom this point4 troubleshootin depends on the specific problem/ Dse the log to investigate the problem/

,ommon pro!-ems + "ctive spool )obs that have been running for over an hour/ 0hese lon runnin Jobs could indicate a problem &ith the operatin system spool or the printer/ Spoo- data!ase a-most 'u-Fun spool reor in pro ram 2SP*%%;1 6Deletes old print jobs - sugg. older than 7 days)/ Can be scheduled to be run &eekly/

207623304 doc

30!01!2014

21

%. Check and analyze buffer statistics and s'aps (ST*2)

SAP F@3 instance buffers are memory areas of an application ser%er instance/ 0hey contain data and pro ram code that is freGuently used by all &ork processes/ 0he SAP F@3 instance buffers are important for a hi h interacti%e performance/ 0he buffer tune summary transaction 6S0+28 displays the F@3 buffer performance statistics/ 3t is used to tune buffer parameters of F@3/ 0he access to buffered data that is stored in the main memory of the application ser%er is much faster than the retrie%al of data from the database/ 0he buffer is also important because significant buffer swapping reduces performance/ Look under Swaps for red entries/ Fe ularly check these entries to establish trends and et a feel for buffer beha%ior/ 3n the Command field4 enter transaction ST%2 and choose 4nter 6or from the SAP standard menu4 choose 0ools $7 Administration $7O5onitor $7OPerformance -3 7Setup/8uffers -3S.09-8uffers&. *utput +

207623304 doc

30!01!2014

22
Bu''er types + 0hese are the important buffer types> 0his buffer contains table and field definitions of the A,AP dictionary/ 0he database access a ents of a &orkprocess consult the repository buffer before accessin a specific database table to detect &hether the contents of the table are buffered/ 0he repository buffer is also kno&n as nametab and consists of the four shared buffers 00A,4 =0A,4 3F2C and short nametab/ 0able buffers 0hese buffers store the content of database tables/ 0here are t&o types of table buffers> partial and eneric/ Partial table buffers store sin le table records or keys/ :eneric table buffers hold seGuences of records or e%en all records of sin le tables/ 0his buffer stores the compiled and4 thus4 e1ecutable %ersions of A,AP pro rams/ As the &hole business lo ic and application processin of the SAP F@3 modules is based on A,AP pro rams4 this buffer is very important/ 0here is a least recently used 6LF'8 al orithm implemented for reusin the pro ram buffer/ 0here are t&o buffers that store SAP ui obJects > Presentation buffer $ also kno&n as Screen or Dynpro buffer4 contains dynamically created SAP :'3 screens/ 5enu buffer $ contains :'3 elements4 such as menu and button definitions/ 9 0here are some more buffers for specific services4 such as dispatcher5 message5 spool, and enBueue4 and for the administration of the different SAP F@3 memory areas4 such as roll4 pa in 4 and 21tended 5emory/

8rogram buffer

SAP ui buffers

Bu''er attri!utes + ,uffer Guality 0his %alue describes the buffer hit rate in terms of database reBuests/ An application reGuest can demand se%eral sin le database reGuests/ 0he buffer Guality is the ratio bet&een the number of avoided database reBuests and the number of all database reBuests. 0he buffer Guality is more important than the hit rate because the benefit from the buffer is calculated &ith &ei hted reGuests/ 0his %alue specifies the amount of shared memory in L, that is allocated by the buffer/ 0he allocated size is independent of the current usa e of the buffer because the buffer allocates the &hole amount of memory accordin to its confi ured size durin the start of the instance/ 0his %alue pro%ides the current free buffer space in L, and percenta e of the &hole buffer size/ 3t does not consider fra mentation/ A directory entry is reGuired for e%ery buffered obJect that points to the memory address &here the obJect is stored/ 0his %alue specifies the o%erall number and number of a%ailable directory entries for the buffer/

Allocated size

=ree space Eumber of directories

207623304 doc

30!01!2014

23 Analysis (ST02) :
,efore a buffer can be tuned4 it has to be monitored for a sufficiently long period of time during normal operation / 0he buffer monitor does not pro%ide meanin ful %alues until after this period of time/ A ood %alue for the buffer Guality depends on the buffer type/ <it 2atio 0his %alue is the ratio bet&een the number of application reGuests that &ere successfully ser%ed out of the buffer and the number of all reGuests/ 0he target value is E' percent and higher/ Soon after startin the system4 this %alue is typically lo&4 because buffers are empty/ Restarting an instance should be avoided5 as all buffer contents are destroyed / 0hey are initialized4 and it &ill take a considerable time until they contain the same data a ain/ 0he hit ratio &ill increase as the system is used and the buffers are loaded/ 3t usually takes a day to load the buffers that are normally used/ S.aps 0his %alue represents the number of obJects that ha%e been s&apped out of the buffer in order to pro%ide space for ne& obJects since the start of the instance/ #e can %erify the s&aps incurred in one day by checkin on the Pistory/ Swaps occur when the necessary data is not in the buffer. .he system has to retrieve the data from the data'ase. .he swap value is reset to :ero %0& when the system is restarted. ;hen 2/6 is restarted, the 'uffers are refreshed. .his process means that the first person who accesses the 'uffered o'<ect will have a long response 'ecause the system must get the data from dis and load it into the 'uffer. .he second person will have a normal %,uic & response time. .his process repeats until all normally used o'<ects are loaded into the 'uffer, which usually takes up to a day to accomplish. 0he aim is to a%oid s&appin and ha%e a ood buffer Guality/ 2 other columns to look at in S0+2 are the Free #ir entries and Free space4 )e'ragment system memory A computer<s memory beha%es similar to a hard disk/ As different pro rams e1ecute4 they are loaded into4 and later deleted out of4 memory/ ;%er time4 like a hard disk4 the usa e of the computer<s memory becomes fra mented &ith unused spaces scattered throu hout/ At a certain point you may ha%e sufficient -free memory. 6that is4 the total of all the unused spaces84 but not a conti uous 6sin le8 piece of memory lar e enou h to allo& certain pro rams to e1ecute/ At that point4 those types of pro rams attemptin to run that need conti uous memory &ill fail because they cannot be loaded into memory/ 0his step reGuires stoppin restartin F@3 on all application and database ser%ers/

ara!eter Settin"s for SA ,uffers ;uffer configuration 0he size of the indi%idual buffers can be tuned throu h the modification of instance profile parameters 1t6n RC+(3/ 0he sapp'par too- can be used to check the buffer confi uration for an instance/ ,est to run this &hen SAP is stopped to et a realistic info/ As user ?sid7adm4 you can issue the follo&in command4 specifyin the full path to the instance profile> sappfpar pfQ@sapmnt@?S3D7@profile@?3nstanceKProfile7 check

207623304 doc

30!01!2014

24

.. Analyzin" of A,A du!ps (ST22)

An A,AP dump 6also kno&n as a short dump8 is generated when a report or transaction terminates as the result of a serious error. 0he system records the error in the system lo 6transaction SM9=8 and &rites a snapshot 6dump8 of the pro ram termination to a special table 6SN(P8/ 0his transaction can also be called from the system lo 6transaction SM9=8/ An A,AP dump is used to analy>e and determine why the error occurred and take corrective action.

1/ 3n the Command field4 enter transaction ST22 and choose 4nter 6or from the S!P standard menu4 choose .ools 7O!dministration 7OMonitor 7S.99-)ump analysis&/ 0here are t&o selection methods to display the list of dumps> ? =or a simple selection4 .oday or $esterday 6proceed to step 28 ? =or a free selection 6proceed to step "8 2/ 'nder *o. of short dumps4 if you see a %alue other than zero 6+8 in .oday or $esterday4 dumps ha%e occurred that need to be e1amined/ 3/ Select .oday/ 4/ Press =! 6Proceed to step !/8

, Choose (election

207623304 doc

30!01!2014

2,
6 /nter your selection criteria in the )*)+ ,ump )nalysis screen 7 0ress -"ecute button $'-% - 1ouble2click on the dum" you *ant to analyze

0he abo%e screen sho&s the short dump >

207623304 doc

30!01!2014

26

207623304 doc

30!01!2014

27 Analysis (ST22) :
0he dump contains the follo&in information> ?hy the program has terminated ?hat caused the program termination ?here in the program code the termination occurred ?hat you can do to correct the error The values of the relevant system fields when the program terminated The calls or events that were active when the program terminated "ny other programs that are affected.

=urther solution on A,AP dumps errors enerated can be obtain from the follo&in sites>

ser/ice4sap4com7notes or 3ttps+77.e!smp1%14sap=ag4de7notes *SS Despite bein called a -short dump4. A,AP dumps may be more than *' pages long/ T3e dump s3ou-d !e sa/ed -oca--y and print out on-y t3e portion you need4 3f the SAP hotline asks for a copy of the short dump4 rather than fa1 the entire dump4 it is easier to e<mail or upload the file 6see SAP note 400948/

Some a!ap dumps -ist .it3 possi!-e causes +

Error msg
1 2 CE0LK2FF;F D,3=KFSMLKSMLK2FF;F errors on the SAP:'3

Possible Ca ses

database error or bad SML enerated need to e1tend table space occurs &hen update &as terminated background )ob &as creatin those short dumps/ 0his is due to the file &as empty not a system problem no data found for specified key in table -RRRR.

D,3=KF0A,KL2IKE;0K=;'ED

525;FIKE;K5;F2KPA:3E:

AdJust on parameter abap/buffersi>e Check the 0able space analyze S0+2 and adJust the appropriate parameters by double clickin to obtain the correct parameter to adJust/ At the ;S le%el4 o to the task mana er4 click on performance4 at the commit change bo14 make sure the total and peak are no where near the limit4 if they are reachin each other4 you need to increase your page file at the ;S le%el/ occurs &hen user e1ecutes large number of background )obs simultaneously/ system don<t kno& &hat is the error/ 0he current application tri ered a termination &ith a short dump/

" 52SA::2K0IP2KR

207623304 doc

30!01!2014

2( PRAKE;K=F22KSPAC2 Pro ram buffer size problem/ F@3 tried to load a pro ram4 but there &as no a%ailable free space/ 0he user should &ait a fe& moments and try a ain/ ;%er time4 F@3 &ill release pro rams to be cleared from the buffer/ 0ry to increase the parameters A,AP@,'==2FS3H2 and @ or A,AP@,'==2FS3H2KPAF01/ many reasonsSS/ Check SAP:'3 patches@%ersion 21ception condition TUV??W6XYZ[\W]V^?X\T raised/ short dump could not be found in the database/ may be caused by the follo&in > $ 0able SEAP is full4 $ short dump &as not &ritten due to database problems4 $ if the SEAP 0able is full> Feor anize the table %ia transaction S022 $7 :o to $7Feor anize someone kill a process manually Feflects that the process that are bein runned by the users ha%e timed out/ A protection for lon runnin dialog process/ 2 / A pro ram may ha%e e1ceeded the ma1imum permitted runtime and has therefore been terminated/ 3ncrease the timeout %alue for rdisp/ma6GwprunGtime or simply assign 0 to this parameters/ 0ry to run in back round

* FA3S2K2RC2P03;E

! SEAPKE;KE2#K2E0FI

SIS025 CAEC2LL2D

1+ 0352K;'0

0he pro ram THP=33+12K#AKC;'E0IKF2P;F0 T has e1ceeded the ma1imum permitted runtime and has therefore been terminated/ 0ime limit e1ceeded/

D,3=KFSMLK3EDAL3DKFSML C;ED0KE;KE'5,2F

FSML error 13 &hen accessin table TPA++++ T 'nable to interpret T KT as a number 'nable to interpret TP T as a number

SIS025KCAEC2L2D

0he pro ram TSAPD,PCP T &as terminated manually/ 0he current pro ram TSAPD,PCP T has been terminated by another mode

207623304 doc

30!01!2014