JSPM in NW2004S

[steven_glennie]

Hello All,

Have any of you had any issues with JSPM and i-series. I have completed the Java add-in NW2004S SR1 add-in installation and now need to apply Java Support packages.

I can start the JSPM, although performance is not great, even though I am using a remote PC that is local to the i-series, it just hangs on the Specify queue ( the bit after to select what you want to patch).

According to the logs, there are no errors and the system is waiting for me, but I can see the hour glass on the PC. I have left this for several hours and nothing happens.

We have an SRM implemenation and they have been able to apply the java support packages okay. The main difference between the systems is that they have installed Netweaver 7.0 and I have upgraded the ABAP and then performed the Java add-in to get to 7.0

Any information supplied relating to JSPM and iseries would be useful. Also, anything relating to improving performance would also be helpful.

Best regards,

Steven

[steven_glennie · Accepted solution]

The Java support packages have been applying for over 24 hours and it has applied 21 / 42 java support packs in the JSPM.

The area I see it being really slow is when it runs the QP0ZSPWP job below in qinter.

It is recommended to have qinter not very large for SAP systems, but if a lot of the JPSM is running in Qinter, then should the values for max threads and memory be increased in here at least for the application of Java support packages.

QINTER QSYS SBS .0 DEQW

QPADEV001C BWDOFR INT .0 CMD-QSH DEQW

QP0ZSPWP BWDOFR BCI .0 PGM-QZSHSH EVTW

QP0ZSPWP BWDOFR BCI .2 JVM-com.sap.sd RUN

QZSHSH BWDOFR BCI .0 PGM-QZSHSH EVTW

I have also put the wrksyssts results below and would appreciate any advice. I belive this shows our Max active threads are far to low, but we cannot increase this as this will eat up to much main memory. My guess is that we need to add more main memory.

Sys Pool Reserved Max DB F/P nonDB F/P Act-Wait

1 1583.56 344.38 +++ 0/0 1/3 202

2 14515.64 11.45 600 82/590 260/690 38657

3 30.85 .00 20 0/0 0/0 0

4 124.00 .07 38 0/0 97/741 4664

1=Machine 2=Base 3=Spool 4=Interact

With regards,

Steven

[Former Member · Accepted solution]

Hi Steve,

I can only tell you:

You are soooo correct !

But, that is exactly why I do make use of the recommendation in the notes, that you want to get rid of the extra pool for QINTER (and QSPL) and put everything to *BASE => everybody can share the memory )

I setup all systems this way.

Regards

Volker Gueldenpfennig, consolut.gmbh

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

[Former Member · Accepted solution]

Hi Steven,

Hope the following web blog would help you.

/people/sap.user72/blog/2006/07/11/remove-interact-memory-pool-on-ibm-i5iseries

Thank you,

Victor

[steven_glennie]

Hello All,

Just an update to the performance issues I exeperienced with JSPM. I made the change to the qinter and the time to apply java support packages to our test system compared to our development system went from 2 days to 9 hours. Quite an improvement.

Thanks Volker , Victor and Thomas. Although I didn't make the change Thomas suggested, this would be a solution for those not wishing to make the qinter change and something maybe SAP should deliver for i-series customers.

Many thanks & regards,

Steven

[thomas_obermeier]

Hi Steven,

I am not quite sure whether it would help to improve your performance, but if you want to run JSPM in batch there is a way: Submit the java process to batch. To do so, create a copy batch_go of the go script in the JSPM directory. In there, do the following replacement right at the end:

<u>original:</u>

[code]# Start JSPM

if [ "$platform" != 'os4' ]; then

$java_cmd -ea -Duser.dir=$rootdir -Xmx512m -cp $rootdir/lib/sdt_jspm.jar com.sap.sdt.jspm.main.Jspm -rootdir=$rootdir -tracelevel=FINEST run JSPM

else

$java_cmd -ea -Duser.dir=$rootdir -Xmx512m -cp $rootdir/lib/sdt_jspm.jar com.sap.sdt.jspm.main.Jspm -rootdir=$rootdir -tracelevel=FINEST -config=/dialog/SDTServerConnection/SDTGui/launch=false run JSPM

fi[/code]

<u>new:</u>

[code]# Start JSPM

if [ "$platform" != 'os4' ]; then

$java_cmd -ea -Duser.dir=$rootdir -Xmx512m -cp $rootdir/lib/sdt_jspm.jar com.sap.sdt.jspm.main.Jspm -rootdir=$rootdir -tracelevel=FINEST run JSPM

else

system "SBMJOB CMD(JAVA CLASS('com.sap.sdt.jspm.main.Jspm') PROP(('user.dir' '$rootdir')) GCHINL(512000) CLASSPATH('$rootdir/lib/sdt_jspm.jar') PARM('-rootdir=$rootdir' '-tracelevel=FINEST' '-config=/dialog/SDTServerConnection/SDTGui/launch=false' 'run' 'JSPM'))"

fi[/code]

Then, run [code]QSH CMD('.../batch_go')[/code] instead of [code]CMD('.../go')[/code]. When it comes to support cases, better mention this change;-)

HTH,

Thomas