Re: Connection Pooling - Activation Groups

[Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>]

Hello,

My responses are in-line.

> I'm trying to find out if I need to re-open my activation groups every
> time a user has executed my store procedure from the web?

I don't understand the question.  Activation groups are created 
automatically as they are needed. What do you mean by "re-open"?  How do 
you open an activation group?

> Using connection pooling, if the user connection becomes idle, would it 
> be smart to keep it open, just in case the user tries to run the next 
> transaction?

I guess it depends on what you're doing?  But in 99.99% of the situations, 
a stored procedure shouldn't reclaim an activation group.  It'd be a 
strange situation indeed where a stored procedure would want to reclaim an 
activation group.


> The store procedure allows the web user to add a customer number, and the
> data gets written to the file inside sub-procedure of the RPG program. In
> my example, the user isn't doing much I/O, but if this was the case, would
> opening/closing the activation group become a major resource problem?

It probably takes an extra 1/10 second to create the new activation group, 
re-activate the program and  re-open the files before writing the record. 
If you kept the activation group open, that wouldn't be needed.

Does that 1/10 second matter to you?  That's the real question.

If you're writing 600 records, it'd take an extra 60 seconds (1 minute). 
That's a lot when you consider how long it takes to write 600 records 
normally!  On the other hand, if you're writing 5 records per day, that's 
1/2 second spead out across the entire day's work.

That's why it's up to YOU, not US, to answer this question.  Performance 
isn't a question of "do this, not that"  it's a question of what matters 
and what doesn't matter for a particular application.  It doesn't make 
sense to complicate the environment to save 1/2 second per day.  But it 
sure makes sense to add a little complexity if it saves 1 minute per 
transaction!

> Do I need to use this parameter on my H Specification inside the RPG by
> using THREAD(*SERIALIZE)?

No.  (Unless there's somethign else going on that would mandate it!)