SEO

Jean-Marc,

INITFENCED starts a pool of db2fmps that will be used for not
threadsafe, non Java routines. In v8 with threading, we started
isolating different languaged routines from each other to prevent
interop problems (and to keep 'safer' languages isolated), as well as to
prevent memory bloat due to proliferation of JVMs. Java routines will
only go to fmps that have a JVM started.

I think this is documented in the admin guide config parm section.

Jean-Marc Blaise wrote:
> Hi again, Mick (it's a pleasure !),
>
> Thanks for confirming if it's deprecated. From my testing, INITFENCED=1 and
> INITFENCED_JVM=YES does not start db2fmp processes sizing the ones I find
> when I launch the 1st time a java proc (ps -elf | grep db2fmp still about
> 5666 against about 22222 bytes).
>
> The first Eclipse link works. The 2nd one seems not to be accessible.
>
> Cheers,
>
> Jean-Marc
>
> "Mick Legare" <mlegare@no-spam-ca.ibm.com> a écrit dans le message news:
> 3EF88D6B.768B5C93@no-spam-ca.ibm.com...
>
>>Hi again Jean-Marc,
>>I seem to remember that this parameter has been deprecated in V8 and
>
> should not
>
>>really show up anywhere. I'm going to check here and make sure.
>>
>>Also, regarding out last e-mails: I found the following links to our
>
> documentation
>
>>and they contain excellent search capabilities. I hope they help:
>>
>>in the Eclipse-based DB2 information center:
>> http://publib.boulder.ibm.com/infocenter/db2help
>>
>>in the HTML-based DB2 information center that gets installed with the doc
>
> CD
>
>>visible at:
>> http://rossr.torolab.ibm.com/db2doc/...htmlcd/en_US/).
>>
>>Mick
>>
>>
>>Blair Kenneth Adamache wrote:
>>
>>
>>>This is just the new new name for INITDARI_JVM:
>>>
>>>Initialize DARI Process with JVM (initdari_jvm)
>>>
>>>Configuration Type
>>>Database manager
>>>
>>>Applies to
>>>Database server with local and remote clients
>>>Database server with local clients
>>>Partitioned database server with local and remote clients
>>>Satellite database server with local clients
>>>
>>>Parameter Type
>>>Configurable
>>>
>>>Default [Range]
>>>No [ Yes; No ]
>>>
>>>Related Parameters
>>>Maximum Number of DARI Processes (maxdari)
>>>Initial Number of Fenced DARI Processes in Pool (num_initdaris)
>>>Keep DARI Process Indicator (keepdari)
>>>This parameter indicates whether each fenced DARI process will load the
>
> Java
>
>>>Virtual Machine (JVM) when starting. This parameter will reduce the
>
> initial
>
>>>startup time for fenced Java stored procedures, especially when used in
>>>conjunction with the num_initdaris parameter. This parameter could
>
> increase the
>
>>>initial load time for non-Java fenced stored procedures as they do not
>
> require
>
>>>the JVM.
>>>
>>> Jean-Marc Blaise wrote:
>>>
>>>
>>>>Hi, I would like to know if the INITFENCED_JVM option in the DBM CFG
>
> is
>
>>>>functional, right now if V8 FP2, or if it is a future enhancement,
>
> because I
>
>>>>have not found any documentation in the Information Center (FP2) ?
>>>>
>>>>Thanks in advance,
>>>>
>>>>Jean-Marc
>>
>
>

There has never bee a way to avoid jvm init time, because this var was
never enabled. :-)

We considered adding in some more knobs for this, but now that a typical
instance will have only 1 jvm running in it (using threads that are
shared between apps), the jvm startup will only happen 1x. So we didn't
consider it a big deal.

Jean-Marc Blaise wrote:
> Thanks Sean for these precisions.
>
> However, how can I overcome JVM starting time now in V8 ?
>
> I did from the same session:
> db2start
> call SQLJproc (the db2fmp is started with JVM)
> call JDBC1proc (the same db2fmp is used)
> call JDBC2proc ;another db2fmp is started with JVM: ==> why, I would have
> expected the same db2fmp to be used (I am in a multi-partition context on
> Linux with 3 nodes) ?
>
> Rem: all procs have been built with the DecCenter.
>
> Couldn't you have turned the INITFENCED_JVM from a YES/NO value to an
> INTEGER, to overcome this JVM loading time ?
>
> Thanks for your help,
>
> Jean-Marc
>
>
> "Sean McKeough" <mckeough@nospam.ca.ibm.com> a écrit dans le message news:
> bdf0f3$qhq$1@hanover.torolab.ibm.com...
>
>>Jean-Marc,
>>
>>INITFENCED starts a pool of db2fmps that will be used for not
>>threadsafe, non Java routines. In v8 with threading, we started
>>isolating different languaged routines from each other to prevent
>>interop problems (and to keep 'safer' languages isolated), as well as to
>>prevent memory bloat due to proliferation of JVMs. Java routines will
>>only go to fmps that have a JVM started.
>>
>>I think this is documented in the admin guide config parm section.
>>
>>Jean-Marc Blaise wrote:
>>
>>>Hi again, Mick (it's a pleasure !),
>>>
>>>Thanks for confirming if it's deprecated. From my testing, INITFENCED=1
>
> and
>
>>>INITFENCED_JVM=YES does not start db2fmp processes sizing the ones I
>
> find
>
>>>when I launch the 1st time a java proc (ps -elf | grep db2fmp still
>
> about
>
>>>5666 against about 22222 bytes).
>>>
>>>The first Eclipse link works. The 2nd one seems not to be accessible.
>>>
>>>Cheers,
>>>
>>>Jean-Marc
>>>
>>>"Mick Legare" <mlegare@no-spam-ca.ibm.com> a écrit dans le message news:
>>>3EF88D6B.768B5C93@no-spam-ca.ibm.com...
>>>
>>>
>>>>Hi again Jean-Marc,
>>>>I seem to remember that this parameter has been deprecated in V8 and
>>>
>>>should not
>>>
>>>
>>>>really show up anywhere. I'm going to check here and make sure.
>>>>
>>>>Also, regarding out last e-mails: I found the following links to our
>>>
>>>documentation
>>>
>>>
>>>>and they contain excellent search capabilities. I hope they help:
>>>>
>>>>in the Eclipse-based DB2 information center:
>>>> http://publib.boulder.ibm.com/infocenter/db2help
>>>>
>>>>in the HTML-based DB2 information center that gets installed with the
>
> doc
>
>>>CD
>>>
>>>
>>>>visible at:
>>>> http://rossr.torolab.ibm.com/db2doc/...htmlcd/en_US/).
>>>>
>>>>Mick
>>>>
>>>>
>>>>Blair Kenneth Adamache wrote:
>>>>
>>>>
>>>>
>>>>>This is just the new new name for INITDARI_JVM:
>>>>>
>>>>>Initialize DARI Process with JVM (initdari_jvm)
>>>>>
>>>>>Configuration Type
>>>>>Database manager
>>>>>
>>>>>Applies to
>>>>>Database server with local and remote clients
>>>>>Database server with local clients
>>>>>Partitioned database server with local and remote clients
>>>>>Satellite database server with local clients
>>>>>
>>>>>Parameter Type
>>>>>Configurable
>>>>>
>>>>>Default [Range]
>>>>>No [ Yes; No ]
>>>>>
>>>>>Related Parameters
>>>>>Maximum Number of DARI Processes (maxdari)
>>>>>Initial Number of Fenced DARI Processes in Pool (num_initdaris)
>>>>>Keep DARI Process Indicator (keepdari)
>>>>>This parameter indicates whether each fenced DARI process will load the
>>>
>>>Java
>>>
>>>
>>>>>Virtual Machine (JVM) when starting. This parameter will reduce the
>>>
>>>initial
>>>
>>>
>>>>>startup time for fenced Java stored procedures, especially when used in
>>>>>conjunction with the num_initdaris parameter. This parameter could
>>>
>>>increase the
>>>
>>>
>>>>>initial load time for non-Java fenced stored procedures as they do not
>>>
>>>require
>>>
>>>
>>>>>the JVM.
>>>>>
>>>>> Jean-Marc Blaise wrote:
>>>>>
>>>>>
>>>>>
>>>>>>Hi, I would like to know if the INITFENCED_JVM option in the DBM CFG
>>>
>>>is
>>>
>>>
>>>>>>functional, right now if V8 FP2, or if it is a future enhancement,
>>>
>>>because I
>>>
>>>
>>>>>>have not found any documentation in the Information Center (FP2) ?
>>>>>>
>>>>>>Thanks in advance,
>>>>>>
>>>>>>Jean-Marc
>>>>
>>>
>
>

Sean,

I agree that this is what should theoritically happen: only 1 JVM in the
instance. That means only 1 db2fmp process for all Java stored procs.

But then,

1) why on a single connection, do I get another db2fmp started (as explained
below) ? what does happen though is suddenly a stored proc that does not get
back to you in the expected timing. (Linux V8 FP2).

2) what about scalability: do you believe that only 1 db2fmp + associated
JVM will be able to treat all concurrent Java stored Procs ? I believe, from
point 1) that there should be some cases where new db2fmp processes could be
created.

In my question, I was thinking and asking if this INITFENCED_JVM could be
used as a maximum db2fmp pool for all Java Stored procs ? What about Java
Stored procs that could be created as "not threadsafe" (if we can created
some as this type) ?

Regards,

Jean-Marc

"Sean McKeough" <mckeough@nospam.ca.ibm.com> a écrit dans le message news:
bdhgbc$1m6$1@hanover.torolab.ibm.com...
> There has never bee a way to avoid jvm init time, because this var was
> never enabled. :-)
>
> We considered adding in some more knobs for this, but now that a typical
> instance will have only 1 jvm running in it (using threads that are
> shared between apps), the jvm startup will only happen 1x. So we didn't
> consider it a big deal.
>
> Jean-Marc Blaise wrote:
> > Thanks Sean for these precisions.
> >
> > However, how can I overcome JVM starting time now in V8 ?
> >
> > I did from the same session:
> > db2start
> > call SQLJproc (the db2fmp is started with JVM)
> > call JDBC1proc (the same db2fmp is used)
> > call JDBC2proc ;another db2fmp is started with JVM: ==> why, I would
have
> > expected the same db2fmp to be used (I am in a multi-partition context
on
> > Linux with 3 nodes) ?
> >
> > Rem: all procs have been built with the DecCenter.
> >
> > Couldn't you have turned the INITFENCED_JVM from a YES/NO value to an
> > INTEGER, to overcome this JVM loading time ?
> >
> > Thanks for your help,
> >
> > Jean-Marc
> >
> >
> > "Sean McKeough" <mckeough@nospam.ca.ibm.com> a écrit dans le message
news:
> > bdf0f3$qhq$1@hanover.torolab.ibm.com...
> >
> >>Jean-Marc,
> >>
> >>INITFENCED starts a pool of db2fmps that will be used for not
> >>threadsafe, non Java routines. In v8 with threading, we started
> >>isolating different languaged routines from each other to prevent
> >>interop problems (and to keep 'safer' languages isolated), as well as to
> >>prevent memory bloat due to proliferation of JVMs. Java routines will
> >>only go to fmps that have a JVM started.
> >>
> >>I think this is documented in the admin guide config parm section.
> >>
> >>Jean-Marc Blaise wrote:
> >>
> >>>Hi again, Mick (it's a pleasure !),
> >>>
> >>>Thanks for confirming if it's deprecated. From my testing, INITFENCED=1
> >
> > and
> >
> >>>INITFENCED_JVM=YES does not start db2fmp processes sizing the ones I
> >
> > find
> >
> >>>when I launch the 1st time a java proc (ps -elf | grep db2fmp still
> >
> > about
> >
> >>>5666 against about 22222 bytes).
> >>>
> >>>The first Eclipse link works. The 2nd one seems not to be accessible.
> >>>
> >>>Cheers,
> >>>
> >>>Jean-Marc
> >>>
> >>>"Mick Legare" <mlegare@no-spam-ca.ibm.com> a écrit dans le message
news:
> >>>3EF88D6B.768B5C93@no-spam-ca.ibm.com...
> >>>
> >>>
> >>>>Hi again Jean-Marc,
> >>>>I seem to remember that this parameter has been deprecated in V8 and
> >>>
> >>>should not
> >>>
> >>>
> >>>>really show up anywhere. I'm going to check here and make sure.
> >>>>
> >>>>Also, regarding out last e-mails: I found the following links to our
> >>>
> >>>documentation
> >>>
> >>>
> >>>>and they contain excellent search capabilities. I hope they help:
> >>>>
> >>>>in the Eclipse-based DB2 information center:
> >>>> http://publib.boulder.ibm.com/infocenter/db2help
> >>>>
> >>>>in the HTML-based DB2 information center that gets installed with the
> >
> > doc
> >
> >>>CD
> >>>
> >>>
> >>>>visible at:
> >>>> http://rossr.torolab.ibm.com/db2doc/...htmlcd/en_US/).
> >>>>
> >>>>Mick
> >>>>
> >>>>
> >>>>Blair Kenneth Adamache wrote:
> >>>>
> >>>>
> >>>>
> >>>>>This is just the new new name for INITDARI_JVM:
> >>>>>
> >>>>>Initialize DARI Process with JVM (initdari_jvm)
> >>>>>
> >>>>>Configuration Type
> >>>>>Database manager
> >>>>>
> >>>>>Applies to
> >>>>>Database server with local and remote clients
> >>>>>Database server with local clients
> >>>>>Partitioned database server with local and remote clients
> >>>>>Satellite database server with local clients
> >>>>>
> >>>>>Parameter Type
> >>>>>Configurable
> >>>>>
> >>>>>Default [Range]
> >>>>>No [ Yes; No ]
> >>>>>
> >>>>>Related Parameters
> >>>>>Maximum Number of DARI Processes (maxdari)
> >>>>>Initial Number of Fenced DARI Processes in Pool (num_initdaris)
> >>>>>Keep DARI Process Indicator (keepdari)
> >>>>>This parameter indicates whether each fenced DARI process will load
the
> >>>
> >>>Java
> >>>
> >>>
> >>>>>Virtual Machine (JVM) when starting. This parameter will reduce the
> >>>
> >>>initial
> >>>
> >>>
> >>>>>startup time for fenced Java stored procedures, especially when used
in
> >>>>>conjunction with the num_initdaris parameter. This parameter could
> >>>
> >>>increase the
> >>>
> >>>
> >>>>>initial load time for non-Java fenced stored procedures as they do
not
> >>>
> >>>require
> >>>
> >>>
> >>>>>the JVM.
> >>>>>
> >>>>> Jean-Marc Blaise wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>>Hi, I would like to know if the INITFENCED_JVM option in the DBM CFG
> >>>
> >>>is
> >>>
> >>>
> >>>>>>functional, right now if V8 FP2, or if it is a future enhancement,
> >>>
> >>>because I
> >>>
> >>>
> >>>>>>have not found any documentation in the Information Center (FP2) ?
> >>>>>>
> >>>>>>Thanks in advance,
> >>>>>>
> >>>>>>Jean-Marc
> >>>>
> >>>
> >
> >
>

Hi Blair,

No I am not. I just did db2start, then 3 call procs from the same session.
1st one takes 1.3s, 2nd one takes 0.2s, 3rd one takes 1.3s (new db2fmp
started).

Regards,

Jean-Marc

"Blair Kenneth Adamache" <badamache@yahootoomuchspam.com> a écrit dans le
message news: 3EFCE40B.488C213A@yahootoomuchspam.com...
> Are you running any of the tools? Most (Control Center, Command Center)
share
> the same JVM, but the Configuration Assistant requires its own JVM (at
least
> until the next release).
>
> Jean-Marc Blaise wrote:
>
> > Sean,
> >
> > I agree that this is what should theoritically happen: only 1 JVM in the
> > instance. That means only 1 db2fmp process for all Java stored procs.
> >
> > But then,
> >
> > 1) why on a single connection, do I get another db2fmp started (as
explained
> > below) ? what does happen though is suddenly a stored proc that does not
get
> > back to you in the expected timing. (Linux V8 FP2).
> >
> > 2) what about scalability: do you believe that only 1 db2fmp +
associated
> > JVM will be able to treat all concurrent Java stored Procs ? I believe,
from
> > point 1) that there should be some cases where new db2fmp processes
could be
> > created.
> >
> > In my question, I was thinking and asking if this INITFENCED_JVM could
be
> > used as a maximum db2fmp pool for all Java Stored procs ? What about
Java
> > Stored procs that could be created as "not threadsafe" (if we can
created
> > some as this type) ?
> >
> > Regards,
> >
> > Jean-Marc
> >
> > "Sean McKeough" <mckeough@nospam.ca.ibm.com> a écrit dans le message
news:
> > bdhgbc$1m6$1@hanover.torolab.ibm.com...
> > > There has never bee a way to avoid jvm init time, because this var was
> > > never enabled. :-)
> > >
> > > We considered adding in some more knobs for this, but now that a
typical
> > > instance will have only 1 jvm running in it (using threads that are
> > > shared between apps), the jvm startup will only happen 1x. So we
didn't
> > > consider it a big deal.
> > >
> > > Jean-Marc Blaise wrote:
> > > > Thanks Sean for these precisions.
> > > >
> > > > However, how can I overcome JVM starting time now in V8 ?
> > > >
> > > > I did from the same session:
> > > > db2start
> > > > call SQLJproc (the db2fmp is started with JVM)
> > > > call JDBC1proc (the same db2fmp is used)
> > > > call JDBC2proc ;another db2fmp is started with JVM: ==> why, I would
> > have
> > > > expected the same db2fmp to be used (I am in a multi-partition
context
> > on
> > > > Linux with 3 nodes) ?
> > > >
> > > > Rem: all procs have been built with the DecCenter.
> > > >
> > > > Couldn't you have turned the INITFENCED_JVM from a YES/NO value to
an
> > > > INTEGER, to overcome this JVM loading time ?
> > > >
> > > > Thanks for your help,
> > > >
> > > > Jean-Marc
> > > >
> > > >
> > > > "Sean McKeough" <mckeough@nospam.ca.ibm.com> a écrit dans le message
> > news:
> > > > bdf0f3$qhq$1@hanover.torolab.ibm.com...
> > > >
> > > >>Jean-Marc,
> > > >>
> > > >>INITFENCED starts a pool of db2fmps that will be used for not
> > > >>threadsafe, non Java routines. In v8 with threading, we started
> > > >>isolating different languaged routines from each other to prevent
> > > >>interop problems (and to keep 'safer' languages isolated), as well
as to
> > > >>prevent memory bloat due to proliferation of JVMs. Java routines
will
> > > >>only go to fmps that have a JVM started.
> > > >>
> > > >>I think this is documented in the admin guide config parm section.
> > > >>
> > > >>Jean-Marc Blaise wrote:
> > > >>
> > > >>>Hi again, Mick (it's a pleasure !),
> > > >>>
> > > >>>Thanks for confirming if it's deprecated. From my testing,
INITFENCED=1
> > > >
> > > > and
> > > >
> > > >>>INITFENCED_JVM=YES does not start db2fmp processes sizing the ones
I
> > > >
> > > > find
> > > >
> > > >>>when I launch the 1st time a java proc (ps -elf | grep db2fmp still
> > > >
> > > > about
> > > >
> > > >>>5666 against about 22222 bytes).
> > > >>>
> > > >>>The first Eclipse link works. The 2nd one seems not to be
accessible.
> > > >>>
> > > >>>Cheers,
> > > >>>
> > > >>>Jean-Marc
> > > >>>
> > > >>>"Mick Legare" <mlegare@no-spam-ca.ibm.com> a écrit dans le message
> > news:
> > > >>>3EF88D6B.768B5C93@no-spam-ca.ibm.com...
> > > >>>
> > > >>>
> > > >>>>Hi again Jean-Marc,
> > > >>>>I seem to remember that this parameter has been deprecated in V8
and
> > > >>>
> > > >>>should not
> > > >>>
> > > >>>
> > > >>>>really show up anywhere. I'm going to check here and make sure.
> > > >>>>
> > > >>>>Also, regarding out last e-mails: I found the following links to
our
> > > >>>
> > > >>>documentation
> > > >>>
> > > >>>
> > > >>>>and they contain excellent search capabilities. I hope they help:
> > > >>>>
> > > >>>>in the Eclipse-based DB2 information center:
> > > >>>> http://publib.boulder.ibm.com/infocenter/db2help
> > > >>>>
> > > >>>>in the HTML-based DB2 information center that gets installed with
the
> > > >
> > > > doc
> > > >
> > > >>>CD
> > > >>>
> > > >>>
> > > >>>>visible at:
> > > >>>> http://rossr.torolab.ibm.com/db2doc/...htmlcd/en_US/).
> > > >>>>
> > > >>>>Mick
> > > >>>>
> > > >>>>
> > > >>>>Blair Kenneth Adamache wrote:
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>>This is just the new new name for INITDARI_JVM:
> > > >>>>>
> > > >>>>>Initialize DARI Process with JVM (initdari_jvm)
> > > >>>>>
> > > >>>>>Configuration Type
> > > >>>>>Database manager
> > > >>>>>
> > > >>>>>Applies to
> > > >>>>>Database server with local and remote clients
> > > >>>>>Database server with local clients
> > > >>>>>Partitioned database server with local and remote clients
> > > >>>>>Satellite database server with local clients
> > > >>>>>
> > > >>>>>Parameter Type
> > > >>>>>Configurable
> > > >>>>>
> > > >>>>>Default [Range]
> > > >>>>>No [ Yes; No ]
> > > >>>>>
> > > >>>>>Related Parameters
> > > >>>>>Maximum Number of DARI Processes (maxdari)
> > > >>>>>Initial Number of Fenced DARI Processes in Pool (num_initdaris)
> > > >>>>>Keep DARI Process Indicator (keepdari)
> > > >>>>>This parameter indicates whether each fenced DARI process will
load
> > the
> > > >>>
> > > >>>Java
> > > >>>
> > > >>>
> > > >>>>>Virtual Machine (JVM) when starting. This parameter will reduce
the
> > > >>>
> > > >>>initial
> > > >>>
> > > >>>
> > > >>>>>startup time for fenced Java stored procedures, especially when
used
> > in
> > > >>>>>conjunction with the num_initdaris parameter. This parameter
could
> > > >>>
> > > >>>increase the
> > > >>>
> > > >>>
> > > >>>>>initial load time for non-Java fenced stored procedures as they
do
> > not
> > > >>>
> > > >>>require
> > > >>>
> > > >>>
> > > >>>>>the JVM.
> > > >>>>>
> > > >>>>> Jean-Marc Blaise wrote:
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>>>Hi, I would like to know if the INITFENCED_JVM option in the DBM
CFG
> > > >>>
> > > >>>is
> > > >>>
> > > >>>
> > > >>>>>>functional, right now if V8 FP2, or if it is a future
enhancement,
> > > >>>
> > > >>>because I
> > > >>>
> > > >>>
> > > >>>>>>have not found any documentation in the Information Center (FP2)
?
> > > >>>>>>
> > > >>>>>>Thanks in advance,
> > > >>>>>>
> > > >>>>>>Jean-Marc
> > > >>>>
> > > >>>
> > > >
> > > >
> > >
>

Jean-Marc,

Answers inline

Jean-Marc Blaise wrote:
> Sean,
>
> I agree that this is what should theoritically happen: only 1 JVM in the
> instance. That means only 1 db2fmp process for all Java stored procs.
>
> But then,
>
> 1) why on a single connection, do I get another db2fmp started (as explained
> below) ? what does happen though is suddenly a stored proc that does not get
> back to you in the expected timing. (Linux V8 FP2).

SEAN> In your case below you have num_initfenced set...as explained
previously, this will start a set of fmps for not threadsafe C
routines...a db2fmp for java will still need to be started on first call.

> 2) what about scalability: do you believe that only 1 db2fmp + associated
> JVM will be able to treat all concurrent Java stored Procs ? I believe, from
> point 1) that there should be some cases where new db2fmp processes could be
> created.

SEAN> We monitor java heap usage, and will create secondary fmps when
needed...in general 1 fmp can handle the entire workload (if java heap
is set high enough).

> In my question, I was thinking and asking if this INITFENCED_JVM could be
> used as a maximum db2fmp pool for all Java Stored procs ? What about Java
> Stored procs that could be created as "not threadsafe" (if we can created
> some as this type) ?
>
SEAN> I think the most useful thing would be to start 1 fenced threaded
process with a JVM...not many customers are running not threadsafe
java...you can create these (recommended if you're hogging a lot of java
heap or using statics only).

> Regards,
>
> Jean-Marc
>
> "Sean McKeough" <mckeough@nospam.ca.ibm.com> a écrit dans le message news:
> bdhgbc$1m6$1@hanover.torolab.ibm.com...
>
>>There has never bee a way to avoid jvm init time, because this var was
>>never enabled. :-)
>>
>>We considered adding in some more knobs for this, but now that a typical
>> instance will have only 1 jvm running in it (using threads that are
>>shared between apps), the jvm startup will only happen 1x. So we didn't
>>consider it a big deal.
>>
>>Jean-Marc Blaise wrote:
>>
>>>Thanks Sean for these precisions.
>>>
>>>However, how can I overcome JVM starting time now in V8 ?
>>>
>>>I did from the same session:
>>>db2start
>>>call SQLJproc (the db2fmp is started with JVM)
>>>call JDBC1proc (the same db2fmp is used)
>>>call JDBC2proc ;another db2fmp is started with JVM: ==> why, I would
>
> have
>
>>>expected the same db2fmp to be used (I am in a multi-partition context
>
> on
>
>>>Linux with 3 nodes) ?
>>>
>>>Rem: all procs have been built with the DecCenter.
>>>
>>>Couldn't you have turned the INITFENCED_JVM from a YES/NO value to an
>>>INTEGER, to overcome this JVM loading time ?
>>>
>>>Thanks for your help,
>>>
>>>Jean-Marc
>>>
>>>
>>>"Sean McKeough" <mckeough@nospam.ca.ibm.com> a écrit dans le message
>
> news:
>
>>>bdf0f3$qhq$1@hanover.torolab.ibm.com...
>>>
>>>
>>>>Jean-Marc,
>>>>
>>>>INITFENCED starts a pool of db2fmps that will be used for not
>>>>threadsafe, non Java routines. In v8 with threading, we started
>>>>isolating different languaged routines from each other to prevent
>>>>interop problems (and to keep 'safer' languages isolated), as well as to
>>>>prevent memory bloat due to proliferation of JVMs. Java routines will
>>>>only go to fmps that have a JVM started.
>>>>
>>>>I think this is documented in the admin guide config parm section.
>>>>
>>>>Jean-Marc Blaise wrote:
>>>>
>>>>
>>>>>Hi again, Mick (it's a pleasure !),
>>>>>
>>>>>Thanks for confirming if it's deprecated. From my testing, INITFENCED=1
>>>
>>>and
>>>
>>>
>>>>>INITFENCED_JVM=YES does not start db2fmp processes sizing the ones I
>>>
>>>find
>>>
>>>
>>>>>when I launch the 1st time a java proc (ps -elf | grep db2fmp still
>>>
>>>about
>>>
>>>
>>>>>5666 against about 22222 bytes).
>>>>>
>>>>>The first Eclipse link works. The 2nd one seems not to be accessible.
>>>>>
>>>>>Cheers,
>>>>>
>>>>>Jean-Marc
>>>>>
>>>>>"Mick Legare" <mlegare@no-spam-ca.ibm.com> a écrit dans le message
>
> news:
>
>>>>>3EF88D6B.768B5C93@no-spam-ca.ibm.com...
>>>>>
>>>>>
>>>>>
>>>>>>Hi again Jean-Marc,
>>>>>>I seem to remember that this parameter has been deprecated in V8 and
>>>>>
>>>>>should not
>>>>>
>>>>>
>>>>>
>>>>>>really show up anywhere. I'm going to check here and make sure.
>>>>>>
>>>>>>Also, regarding out last e-mails: I found the following links to our
>>>>>
>>>>>documentation
>>>>>
>>>>>
>>>>>
>>>>>>and they contain excellent search capabilities. I hope they help:
>>>>>>
>>>>>>in the Eclipse-based DB2 information center:
>>>>>> http://publib.boulder.ibm.com/infocenter/db2help
>>>>>>
>>>>>>in the HTML-based DB2 information center that gets installed with the
>>>
>>>doc
>>>
>>>
>>>>>CD
>>>>>
>>>>>
>>>>>
>>>>>>visible at:
>>>>>> http://rossr.torolab.ibm.com/db2doc/...htmlcd/en_US/).
>>>>>>
>>>>>>Mick
>>>>>>
>>>>>>
>>>>>>Blair Kenneth Adamache wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>This is just the new new name for INITDARI_JVM:
>>>>>>>
>>>>>>>Initialize DARI Process with JVM (initdari_jvm)
>>>>>>>
>>>>>>>Configuration Type
>>>>>>>Database manager
>>>>>>>
>>>>>>>Applies to
>>>>>>>Database server with local and remote clients
>>>>>>>Database server with local clients
>>>>>>>Partitioned database server with local and remote clients
>>>>>>>Satellite database server with local clients
>>>>>>>
>>>>>>>Parameter Type
>>>>>>>Configurable
>>>>>>>
>>>>>>>Default [Range]
>>>>>>>No [ Yes; No ]
>>>>>>>
>>>>>>>Related Parameters
>>>>>>>Maximum Number of DARI Processes (maxdari)
>>>>>>>Initial Number of Fenced DARI Processes in Pool (num_initdaris)
>>>>>>>Keep DARI Process Indicator (keepdari)
>>>>>>>This parameter indicates whether each fenced DARI process will load
>
> the
>
>>>>>Java
>>>>>
>>>>>
>>>>>
>>>>>>>Virtual Machine (JVM) when starting. This parameter will reduce the
>>>>>
>>>>>initial
>>>>>
>>>>>
>>>>>
>>>>>>>startup time for fenced Java stored procedures, especially when used
>
> in
>
>>>>>>>conjunction with the num_initdaris parameter. This parameter could
>>>>>
>>>>>increase the
>>>>>
>>>>>
>>>>>
>>>>>>>initial load time for non-Java fenced stored procedures as they do
>
> not
>
>>>>>require
>>>>>
>>>>>
>>>>>
>>>>>>>the JVM.
>>>>>>>
>>>>>>>Jean-Marc Blaise wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>Hi, I would like to know if the INITFENCED_JVM option in the DBM CFG
>>>>>
>>>>>is
>>>>>
>>>>>
>>>>>
>>>>>>>>functional, right now if V8 FP2, or if it is a future enhancement,
>>>>>
>>>>>because I
>>>>>
>>>>>
>>>>>
>>>>>>>>have not found any documentation in the Information Center (FP2) ?
>>>>>>>>
>>>>>>>>Thanks in advance,
>>>>>>>>
>>>>>>>>Jean-Marc
>>>>>>
>>>
>
>

Sean, thanks for your inline precisions.
However, I think there is a little pb with V8 FP2.
Tested on V8 FP2 / V7 FP9 numinit_fenced/dari=0

In the same CLP session (the 3 procs do a simple SELECT PROCNAME, PROCSHEMA
from syscat.procedures either in SQLJ or JDBC):

Call proc1 ==> starts db2fmp (V8) / starts db2dari (V7)
call proc2 ==> uses same db2fmp / uses same db2dari
call proc3 ==> starts new db2fmp ** PB ** / uses same db2dari

Have you encountered similar behaviour - could the java heap size explain
that (the defaults are kept) ?

Best Regards,

Jean-Marc

"Sean McKeough" <mckeough@nospam.ca.ibm.com> a écrit dans le message news:
bdumdp$5uk$1@hanover.torolab.ibm.com...
> Jean-Marc,
>
> Answers inline
>
> Jean-Marc Blaise wrote:
> > Sean,
> >
> > I agree that this is what should theoritically happen: only 1 JVM in the
> > instance. That means only 1 db2fmp process for all Java stored procs.
> >
> > But then,
> >
> > 1) why on a single connection, do I get another db2fmp started (as
explained
> > below) ? what does happen though is suddenly a stored proc that does not
get
> > back to you in the expected timing. (Linux V8 FP2).
>
> SEAN> In your case below you have num_initfenced set...as explained
> previously, this will start a set of fmps for not threadsafe C
> routines...a db2fmp for java will still need to be started on first call.
>
> > 2) what about scalability: do you believe that only 1 db2fmp +
associated
> > JVM will be able to treat all concurrent Java stored Procs ? I believe,
from
> > point 1) that there should be some cases where new db2fmp processes
could be
> > created.
>
> SEAN> We monitor java heap usage, and will create secondary fmps when
> needed...in general 1 fmp can handle the entire workload (if java heap
> is set high enough).
>
> > In my question, I was thinking and asking if this INITFENCED_JVM could
be
> > used as a maximum db2fmp pool for all Java Stored procs ? What about
Java
> > Stored procs that could be created as "not threadsafe" (if we can
created
> > some as this type) ?
> >
> SEAN> I think the most useful thing would be to start 1 fenced threaded
> process with a JVM...not many customers are running not threadsafe
> java...you can create these (recommended if you're hogging a lot of java
> heap or using statics only).
>
> > Regards,
> >
> > Jean-Marc
> >
> > "Sean McKeough" <mckeough@nospam.ca.ibm.com> a écrit dans le message
news:
> > bdhgbc$1m6$1@hanover.torolab.ibm.com...
> >
> >>There has never bee a way to avoid jvm init time, because this var was
> >>never enabled. :-)
> >>
> >>We considered adding in some more knobs for this, but now that a typical
> >> instance will have only 1 jvm running in it (using threads that are
> >>shared between apps), the jvm startup will only happen 1x. So we didn't
> >>consider it a big deal.
> >>
> >>Jean-Marc Blaise wrote:
> >>
> >>>Thanks Sean for these precisions.
> >>>
> >>>However, how can I overcome JVM starting time now in V8 ?
> >>>
> >>>I did from the same session:
> >>>db2start
> >>>call SQLJproc (the db2fmp is started with JVM)
> >>>call JDBC1proc (the same db2fmp is used)
> >>>call JDBC2proc ;another db2fmp is started with JVM: ==> why, I would
> >
> > have
> >
> >>>expected the same db2fmp to be used (I am in a multi-partition context
> >
> > on
> >
> >>>Linux with 3 nodes) ?
> >>>
> >>>Rem: all procs have been built with the DecCenter.
> >>>
> >>>Couldn't you have turned the INITFENCED_JVM from a YES/NO value to an
> >>>INTEGER, to overcome this JVM loading time ?
> >>>
> >>>Thanks for your help,
> >>>
> >>>Jean-Marc
> >>>
> >>>
> >>>"Sean McKeough" <mckeough@nospam.ca.ibm.com> a écrit dans le message
> >
> > news:
> >
> >>>bdf0f3$qhq$1@hanover.torolab.ibm.com...
> >>>
> >>>
> >>>>Jean-Marc,
> >>>>
> >>>>INITFENCED starts a pool of db2fmps that will be used for not
> >>>>threadsafe, non Java routines. In v8 with threading, we started
> >>>>isolating different languaged routines from each other to prevent
> >>>>interop problems (and to keep 'safer' languages isolated), as well as
to
> >>>>prevent memory bloat due to proliferation of JVMs. Java routines will
> >>>>only go to fmps that have a JVM started.
> >>>>
> >>>>I think this is documented in the admin guide config parm section.
> >>>>
> >>>>Jean-Marc Blaise wrote:
> >>>>
> >>>>
> >>>>>Hi again, Mick (it's a pleasure !),
> >>>>>
> >>>>>Thanks for confirming if it's deprecated. From my testing,
INITFENCED=1
> >>>
> >>>and
> >>>
> >>>
> >>>>>INITFENCED_JVM=YES does not start db2fmp processes sizing the ones I
> >>>
> >>>find
> >>>
> >>>
> >>>>>when I launch the 1st time a java proc (ps -elf | grep db2fmp still
> >>>
> >>>about
> >>>
> >>>
> >>>>>5666 against about 22222 bytes).
> >>>>>
> >>>>>The first Eclipse link works. The 2nd one seems not to be accessible.
> >>>>>
> >>>>>Cheers,
> >>>>>
> >>>>>Jean-Marc
> >>>>>
> >>>>>"Mick Legare" <mlegare@no-spam-ca.ibm.com> a écrit dans le message
> >
> > news:
> >
> >>>>>3EF88D6B.768B5C93@no-spam-ca.ibm.com...
> >>>>>
> >>>>>
> >>>>>
> >>>>>>Hi again Jean-Marc,
> >>>>>>I seem to remember that this parameter has been deprecated in V8 and
> >>>>>
> >>>>>should not
> >>>>>
> >>>>>
> >>>>>
> >>>>>>really show up anywhere. I'm going to check here and make sure.
> >>>>>>
> >>>>>>Also, regarding out last e-mails: I found the following links to our
> >>>>>
> >>>>>documentation
> >>>>>
> >>>>>
> >>>>>
> >>>>>>and they contain excellent search capabilities. I hope they help:
> >>>>>>
> >>>>>>in the Eclipse-based DB2 information center:
> >>>>>> http://publib.boulder.ibm.com/infocenter/db2help
> >>>>>>
> >>>>>>in the HTML-based DB2 information center that gets installed with
the
> >>>
> >>>doc
> >>>
> >>>
> >>>>>CD
> >>>>>
> >>>>>
> >>>>>
> >>>>>>visible at:
> >>>>>> http://rossr.torolab.ibm.com/db2doc/...htmlcd/en_US/).
> >>>>>>
> >>>>>>Mick
> >>>>>>
> >>>>>>
> >>>>>>Blair Kenneth Adamache wrote:
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>This is just the new new name for INITDARI_JVM:
> >>>>>>>
> >>>>>>>Initialize DARI Process with JVM (initdari_jvm)
> >>>>>>>
> >>>>>>>Configuration Type
> >>>>>>>Database manager
> >>>>>>>
> >>>>>>>Applies to
> >>>>>>>Database server with local and remote clients
> >>>>>>>Database server with local clients
> >>>>>>>Partitioned database server with local and remote clients
> >>>>>>>Satellite database server with local clients
> >>>>>>>
> >>>>>>>Parameter Type
> >>>>>>>Configurable
> >>>>>>>
> >>>>>>>Default [Range]
> >>>>>>>No [ Yes; No ]
> >>>>>>>
> >>>>>>>Related Parameters
> >>>>>>>Maximum Number of DARI Processes (maxdari)
> >>>>>>>Initial Number of Fenced DARI Processes in Pool (num_initdaris)
> >>>>>>>Keep DARI Process Indicator (keepdari)
> >>>>>>>This parameter indicates whether each fenced DARI process will load
> >
> > the
> >
> >>>>>Java
> >>>>>
> >>>>>
> >>>>>
> >>>>>>>Virtual Machine (JVM) when starting. This parameter will reduce the
> >>>>>
> >>>>>initial
> >>>>>
> >>>>>
> >>>>>
> >>>>>>>startup time for fenced Java stored procedures, especially when
used
> >
> > in
> >
> >>>>>>>conjunction with the num_initdaris parameter. This parameter could
> >>>>>
> >>>>>increase the
> >>>>>
> >>>>>
> >>>>>
> >>>>>>>initial load time for non-Java fenced stored procedures as they do
> >
> > not
> >
> >>>>>require
> >>>>>
> >>>>>
> >>>>>
> >>>>>>>the JVM.
> >>>>>>>
> >>>>>>>Jean-Marc Blaise wrote:
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>>Hi, I would like to know if the INITFENCED_JVM option in the DBM
CFG
> >>>>>
> >>>>>is
> >>>>>
> >>>>>
> >>>>>
> >>>>>>>>functional, right now if V8 FP2, or if it is a future enhancement,
> >>>>>
> >>>>>because I
> >>>>>
> >>>>>
> >>>>>
> >>>>>>>>have not found any documentation in the Information Center (FP2) ?
> >>>>>>>>
> >>>>>>>>Thanks in advance,
> >>>>>>>>
> >>>>>>>>Jean-Marc
> >>>>>>
> >>>
> >
> >
>

No, I have not seen this...since you can easily repro, it'd be great it
you could take this up with service (just tried the same experiment
here, and could not get the 2nd fmp starting).

Jean-Marc Blaise wrote:
> Sean, thanks for your inline precisions.
> However, I think there is a little pb with V8 FP2.
> Tested on V8 FP2 / V7 FP9 numinit_fenced/dari=0
>
> In the same CLP session (the 3 procs do a simple SELECT PROCNAME, PROCSHEMA
> from syscat.procedures either in SQLJ or JDBC):
>
> Call proc1 ==> starts db2fmp (V8) / starts db2dari (V7)
> call proc2 ==> uses same db2fmp / uses same db2dari
> call proc3 ==> starts new db2fmp ** PB ** / uses same db2dari
>
> Have you encountered similar behaviour - could the java heap size explain
> that (the defaults are kept) ?
>
> Best Regards,
>
> Jean-Marc
>
> "Sean McKeough" <mckeough@nospam.ca.ibm.com> a écrit dans le message news:
> bdumdp$5uk$1@hanover.torolab.ibm.com...
>
>>Jean-Marc,
>>
>>Answers inline
>>
>>Jean-Marc Blaise wrote:
>>
>>>Sean,
>>>
>>>I agree that this is what should theoritically happen: only 1 JVM in the
>>>instance. That means only 1 db2fmp process for all Java stored procs.
>>>
>>>But then,
>>>
>>>1) why on a single connection, do I get another db2fmp started (as
>
> explained
>
>>>below) ? what does happen though is suddenly a stored proc that does not
>
> get
>
>>>back to you in the expected timing. (Linux V8 FP2).
>>
>>SEAN> In your case below you have num_initfenced set...as explained
>>previously, this will start a set of fmps for not threadsafe C
>>routines...a db2fmp for java will still need to be started on first call.
>>
>>
>>>2) what about scalability: do you believe that only 1 db2fmp +
>
> associated
>
>>>JVM will be able to treat all concurrent Java stored Procs ? I believe,
>
> from
>
>>>point 1) that there should be some cases where new db2fmp processes
>
> could be
>
>>>created.
>>
>>SEAN> We monitor java heap usage, and will create secondary fmps when
>>needed...in general 1 fmp can handle the entire workload (if java heap
>>is set high enough).
>>
>>
>>>In my question, I was thinking and asking if this INITFENCED_JVM could
>
> be
>
>>>used as a maximum db2fmp pool for all Java Stored procs ? What about
>
> Java
>
>>>Stored procs that could be created as "not threadsafe" (if we can
>
> created
>
>>>some as this type) ?
>>>
>>
>>SEAN> I think the most useful thing would be to start 1 fenced threaded
>>process with a JVM...not many customers are running not threadsafe
>>java...you can create these (recommended if you're hogging a lot of java
>>heap or using statics only).
>>
>>
>>>Regards,
>>>
>>>Jean-Marc
>>>
>>>"Sean McKeough" <mckeough@nospam.ca.ibm.com> a écrit dans le message
>
> news:
>
>>>bdhgbc$1m6$1@hanover.torolab.ibm.com...
>>>
>>>
>>>>There has never bee a way to avoid jvm init time, because this var was
>>>>never enabled. :-)
>>>>
>>>>We considered adding in some more knobs for this, but now that a typical
>>>> instance will have only 1 jvm running in it (using threads that are
>>>>shared between apps), the jvm startup will only happen 1x. So we didn't
>>>>consider it a big deal.
>>>>
>>>>Jean-Marc Blaise wrote:
>>>>
>>>>
>>>>>Thanks Sean for these precisions.
>>>>>
>>>>>However, how can I overcome JVM starting time now in V8 ?
>>>>>
>>>>>I did from the same session:
>>>>>db2start
>>>>>call SQLJproc (the db2fmp is started with JVM)
>>>>>call JDBC1proc (the same db2fmp is used)
>>>>>call JDBC2proc ;another db2fmp is started with JVM: ==> why, I would
>>>
>>>have
>>>
>>>
>>>>>expected the same db2fmp to be used (I am in a multi-partition context
>>>
>>>on
>>>
>>>
>>>>>Linux with 3 nodes) ?
>>>>>
>>>>>Rem: all procs have been built with the DecCenter.
>>>>>
>>>>>Couldn't you have turned the INITFENCED_JVM from a YES/NO value to an
>>>>>INTEGER, to overcome this JVM loading time ?
>>>>>
>>>>>Thanks for your help,
>>>>>
>>>>>Jean-Marc
>>>>>
>>>>>
>>>>>"Sean McKeough" <mckeough@nospam.ca.ibm.com> a écrit dans le message
>>>
>>>news:
>>>
>>>
>>>>>bdf0f3$qhq$1@hanover.torolab.ibm.com...
>>>>>
>>>>>
>>>>>
>>>>>>Jean-Marc,
>>>>>>
>>>>>>INITFENCED starts a pool of db2fmps that will be used for not
>>>>>>threadsafe, non Java routines. In v8 with threading, we started
>>>>>>isolating different languaged routines from each other to prevent
>>>>>>interop problems (and to keep 'safer' languages isolated), as well as
>
> to
>
>>>>>>prevent memory bloat due to proliferation of JVMs. Java routines will
>>>>>>only go to fmps that have a JVM started.
>>>>>>
>>>>>>I think this is documented in the admin guide config parm section.
>>>>>>
>>>>>>Jean-Marc Blaise wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Hi again, Mick (it's a pleasure !),
>>>>>>>
>>>>>>>Thanks for confirming if it's deprecated. From my testing,
>
> INITFENCED=1
>
>>>>>and
>>>>>
>>>>>
>>>>>
>>>>>>>INITFENCED_JVM=YES does not start db2fmp processes sizing the ones I
>>>>>
>>>>>find
>>>>>
>>>>>
>>>>>
>>>>>>>when I launch the 1st time a java proc (ps -elf | grep db2fmp still
>>>>>
>>>>>about
>>>>>
>>>>>
>>>>>
>>>>>>>5666 against about 22222 bytes).
>>>>>>>
>>>>>>>The first Eclipse link works. The 2nd one seems not to be accessible.
>>>>>>>
>>>>>>>Cheers,
>>>>>>>
>>>>>>>Jean-Marc
>>>>>>>
>>>>>>>"Mick Legare" <mlegare@no-spam-ca.ibm.com> a écrit dans le message
>>>
>>>news:
>>>
>>>
>>>>>>>3EF88D6B.768B5C93@no-spam-ca.ibm.com...
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>Hi again Jean-Marc,
>>>>>>>>I seem to remember that this parameter has been deprecated in V8 and
>>>>>>>
>>>>>>>should not
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>really show up anywhere. I'm going to check here and make sure.
>>>>>>>>
>>>>>>>>Also, regarding out last e-mails: I found the following links to our
>>>>>>>
>>>>>>>documentation
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>and they contain excellent search capabilities. I hope they help:
>>>>>>>>
>>>>>>>>in the Eclipse-based DB2 information center:
>>>>>>>> http://publib.boulder.ibm.com/infocenter/db2help
>>>>>>>>
>>>>>>>>in the HTML-based DB2 information center that gets installed with
>
> the
>
>>>>>doc
>>>>>
>>>>>
>>>>>
>>>>>>>CD
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>visible at:
>>>>>>>> http://rossr.torolab.ibm.com/db2doc/...htmlcd/en_US/).
>>>>>>>>
>>>>>>>>Mick
>>>>>>>>
>>>>>>>>
>>>>>>>>Blair Kenneth Adamache wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>This is just the new new name for INITDARI_JVM:
>>>>>>>>>
>>>>>>>>>Initialize DARI Process with JVM (initdari_jvm)
>>>>>>>>>
>>>>>>>>>Configuration Type
>>>>>>>>>Database manager
>>>>>>>>>
>>>>>>>>>Applies to
>>>>>>>>>Database server with local and remote clients
>>>>>>>>>Database server with local clients
>>>>>>>>>Partitioned database server with local and remote clients
>>>>>>>>>Satellite database server with local clients
>>>>>>>>>
>>>>>>>>>Parameter Type
>>>>>>>>>Configurable
>>>>>>>>>
>>>>>>>>>Default [Range]
>>>>>>>>>No [ Yes; No ]
>>>>>>>>>
>>>>>>>>>Related Parameters
>>>>>>>>>Maximum Number of DARI Processes (maxdari)
>>>>>>>>>Initial Number of Fenced DARI Processes in Pool (num_initdaris)
>>>>>>>>>Keep DARI Process Indicator (keepdari)
>>>>>>>>>This parameter indicates whether each fenced DARI process will load
>>>
>>>the
>>>
>>>
>>>>>>>Java
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>>Virtual Machine (JVM) when starting. This parameter will reduce the
>>>>>>>
>>>>>>>initial
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>>startup time for fenced Java stored procedures, especially when
>
> used
>
>>>in
>>>
>>>
>>>>>>>>>conjunction with the num_initdaris parameter. This parameter could
>>>>>>>
>>>>>>>increase the
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>>initial load time for non-Java fenced stored procedures as they do
>>>
>>>not
>>>
>>>
>>>>>>>require
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>>the JVM.
>>>>>>>>>
>>>>>>>>>Jean-Marc Blaise wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>Hi, I would like to know if the INITFENCED_JVM option in the DBM
>
> CFG
>
>>>>>>>is
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>>>functional, right now if V8 FP2, or if it is a future enhancement,
>>>>>>>
>>>>>>>because I
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>>>have not found any documentation in the Information Center (FP2) ?
>>>>>>>>>>
>>>>>>>>>>Thanks in advance,
>>>>>>>>>>
>>>>>>>>>>Jean-Marc
>>>>>>>>
>>>
>
>