I'm confused about isolation level.. According to the devleoper of our
app (java, running java stored procedures) dont they have any
setTransactionIsolation in there code so the default should be CS but
... running db2pd -app -dyn shows that RS is used .. Is it something
special you have to consider when building the procs ? I'm using this
to build the procs
sqlj ${PROCEDURE}.sqlj
db2sqljcustomize -url jdbc:db2://${SYSNODE}:${DB2PORT}/${DB} -user
${DBUSER} -password ${DBPASSWD} ${PROCEDURE}_SJProfile0
/Roger

kavallin@hotmail.com wrote:

> I'm confused about isolation level.. According to the devleoper of our
> app (java, running java stored procedures) dont they have any
> setTransactionIsolation in there code so the default should be CS but
> .. running db2pd -app -dyn shows that RS is used .. Is it something
> special you have to consider when building the procs ? I'm using this
> to build the procs
> sqlj ${PROCEDURE}.sqlj
> db2sqljcustomize -url jdbc:db2://${SYSNODE}:${DB2PORT}/${DB} -user
> ${DBUSER} -password ${DBPASSWD} ${PROCEDURE}_SJProfile0

The default isolation level is determined by DB2 as is described here:
http://publib.boulder.ibm.com/infoce...n/t0005269.htm

Since you don't use an explicit isolation level in your application, DB2
resorts to whichever isolation level the CLI packages were bound. You may
want to check those.

--
Knut Stolze
DB2 Information Integration Development
IBM Germany

Knut, according to the manual for db2sqljcustomize :
"By default, four DB2 packages are created in the database: one for
each isolation level. This utility augments the profile with
DB2-specific information for use at run time, and should be run after
the SQLJ application has been translated, but before the application is
run. "

Noticed that on the development server ( where the sprocs are
developed) we have 4 packages, one for each isolation level but .. on
the prod server dont we have 4 packages so .. there is something I have
missed when I installs the sprocs on the prod server but I dont
understand what. Do you have any clues ?
I'm doing this when I installs the sprocs on the prod server :
sqlj.remove_jar to remove the old jar file
sqlj.install_jar to install the new jar file
Creates the sprocs
call sqlj.refresh_classes to refresh class files...
GRANT execute on the sprocs
/Roger

kavallin@hotmail.com wrote:

> Knut, according to the manual for db2sqljcustomize :
> "By default, four DB2 packages are created in the database: one for
> each isolation level. This utility augments the profile with
> DB2-specific information for use at run time, and should be run after
> the SQLJ application has been translated, but before the application is
> run. "

That's correct. I was talking about the CLI packages - not the SQLJ package
for your application.

> Noticed that on the development server ( where the sprocs are
> developed) we have 4 packages, one for each isolation level but .. on
> the prod server dont we have 4 packages so .. there is something I have
> missed when I installs the sprocs on the prod server but I dont
> understand what. Do you have any clues ?
> I'm doing this when I installs the sprocs on the prod server :
> sqlj.remove_jar to remove the old jar file
> sqlj.install_jar to install the new jar file
> Creates the sprocs
> call sqlj.refresh_classes to refresh class files...
> GRANT execute on the sprocs

You should explain a bit more on what you are doing on the development
system and how exactly you deploy on the production machine, i.e. which
JARs do you install, what's in them. Do you run db2sqljcustomize on the
production system?

--
Knut Stolze
DB2 Information Integration Development
IBM Germany