cancel
Showing results for 
Search instead for 
Did you mean: 

Very slow processing on LSMW and IFS access

Former Member
0 Kudos

Hi all,

we have a very slow processing on LSMW and IFS access. I believe it was slow all the time in the past. This LSMW transaction only converts some data, which are stored in a flat file in the IFS and stores it again into a flat file in the IFS. It is reading the data from IFS and writing again the data into the IFS.

IFS is not fast, I know. But do you have an similar experiences with such LOAD ?!

R/3 Enterprise 4.70 shows with transaction SM50 the following lon running job:

 4  BGD  65988    waiting         Yes                                                      
 5  BGD  65989    waiting         Yes                                                      
 6  DIA  85421    running         Yes                    1      SAPLTHFB   100  USER1    
 7  DIA  65993    running         Yes                    11500  /1CADMC/SA 100 USER2    
 8  DIA  65994    waiting         Yes                                                      
 9  DIA  65995    waiting         Yes                                                      

The WRKACTJOB Display shows:

This means for me the job is not doing so much with the database. Only 439 I/O's in 21 minutes. This is nothing. I have tried to give to this job Priority 19, but this is not the reason, the job is not going faster.

Work with Active Jobs                                                                                
02.07.08  1
CPU %:    89,0     Elapsed time:   00:21:25     Active jobs:   895                                                                                
Subsystem/Job  Type  Pool  Pty      CPU  Int    Rsp  AuxIO  CPU % 
      WP06         BCI     2   20     395,2                136    0,0 
      WP07         BCI     2   19   10274,0                439   12,7 
      WP08         BCI     2   20    1156,0                  8    0,0 
      WP09         BCI     2   20     874,3                  6    0,0

The WRKSYSSTS Display shows: This means for me, the is no memory lack.

Sys      Pool   Reserved    Max  ----DB-----  --Non-DB---  Act-   Wait-  Act-  
Pool    Size M   Size M     Act  Fault Pages  Fault Pages  Wait   Inel   Inel  
  1    5000,00   1448,43  +++++    0,0   0,0    0,4   0,5   94,9    0,0    0,0 
  2   60340,00     44,65   3500   51,6  6335  113,4 364,1   7887    0,0    0,0 
  3     128,00      0,00     10    0,0   1,3    0,2   0,8   17,2    0,0    0,0

The WRKDSKSTS Display shows no problem in DASD.

I/O   Request   Read  Write   Read  Write    %   
  Rqs  Size (K)    Rqs   Rqs     (K)   (K)   Busy  
 11,5     12,4     3,0    8,4   13,2   12,1     2  
 13,2     10,2     1,5   11,6    7,0   10,6     1  
 10,6      8,8     3,5    7,0    8,2    9,2     2  
 13,8     12,4     4,2    9,5   10,1   13,5     2  
  8,3     71,3     7,5    0,8   78,4    7,4     5  
 17,7    123,6    17,5    0,2  125,2    4,0     9  
 27,0     83,1    25,7    1,3   87,1    4,3    10  
 26,9     95,0    25,6    1,3   99,6    5,8     9  
 16,9    115,4    16,2    0,7  120,3    4,0     8  
 37,3    116,7    37,0    0,2  117,3   18,0    13  
 21,4     94,0    20,3    1,0   98,6    6,2     7  
 12,7     72,8    11,5    1,1   77,6   26,8     6  
 13,5     85,1    12,3    1,1   92,0   12,8     5

Any idea, here ???

best regrads,

Carsten Schulz

Teamleader SAP-Basis, ebmpapst Mulfingen, Gemany

Accepted Solutions (0)

Answers (4)

Answers (4)

0 Kudos

Hi Carsten,

you could try narrowing down reasons for the slow processing by using the DSPJOBPERF tool that is provided through SAP Note 1074177. You need to execute the command twice for the work process. The first time, all values get initialized with 0, then you wait a while (e.g. one minute) and execute the command again. From the output you can see where the time is spent - whether it is disk I/O, CPU time, or any kind of lock wait. You could also post the output here, so that we can discuss the next steps.

Kind regards,

Christian Bartels.

Former Member
0 Kudos

Hi together,

thanks for answering so fast.

The jobs read from the sysbas-IFS /usr/sap/a/b/ and writes to /usr/sap/SID/DVEBMGS00/work/ also in the sysbas-IFS.This IFS is not remote. Not through the QfileSrv.400 mechanism.

And yes, we have a HA solution. We have two IASP's on two different iSeries and are using XSM to mirror the data.

I have tried to increase the speed by switching off the XSM mirroring, but the speed does not increase. Sorry.

best regards,

Carsten Schulz

Former Member
0 Kudos

Hi Carsten,

I think the aux-ios in WRKACTJOB should include the IFS access as well and not just the database, so 400+ io's in 20 minutes is really very little if all the program does is read an IFS file and write another IFS file.... I wonder if you have any kind of HA solution active on this system? We have sometimes seen that the replication blocks IFS processing in such cases.

Regards,

Sally Power

Dev. Support for SAP on IBM i

Former Member
0 Kudos

Hi Carsten,

if you are talking on a remote IFS portion, the stuff is very slow - perhaps you could increase the TCP buffers ... but yes, the local IFS performance is a "known issue" - I would say, that this is always that slow ;-(((

Regards

Volker Gueldenpfennig, consolut international ag

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de