RPG program called via Websphere application server

Hi, we are experiencing problems when a RPG service program is called from
Websphere application server (version 6.0.2).

I'm no expert on WAS, If somebody can point me in the right direction , it
would be much appreciated.

We got two instances of WAS running on the same machine. One for testing
and one production version.


We got an internal and distributed environment sending in transactions that
are being serviced by Websphere application server.


As I understand it the main server job( Websphere application Server job-
QEJBSVR) , will spawn servicing jobs (qzrcsrvs), according to the workload.


The RPG service programs would then run under the spawned jobs.


This works as described above in our one WAS environments.


In the other environment, the servicing jobs are being spawned, but the RPG
service programs are running under the main Websphere application server
job, instead of the spawned jobs. I tested this by storing the job number
in my RPG service program (and debugging the main WAS job via STRSRVJOB).
It stores the different spawned job numbers in the one environment, but the
other it stores the main server job's number.


This creates problems, if an error occurs in one transaction, the whole
websphere application server comes to a standstill. It also creates other
transactional problems.


We compared the Websphere setup between the two environments, we could't
find anything different.Is there something we missed during setup of the
environment? Any help would be appreciated.


This email and all content are subject to the following disclaimer:

http://content.momentum.co.za/content/legal/disclaimer_email.htm