Re: SQL Connection Issue

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 09/12/2017
02:23:46 PM:

<Dave>
... is there a different way that I
can assure that I am connected to the local database in our standard SQL

error utility in lieu of issuing the CONNECT RESET statement?
</Dave>

Why not running the log Utility in a named ACTGRP of its own?

Hmmm, in this case, I guess I could do that -- maybe. This
standard SQL error utility is part of our SQL utilities service program.
Any problem with calling a service program in a different activation
group? If I do this, I presume this means that a new activation group
would automatically be connected to the local database and I wouldn't even
have to worry about performing a CONNECT RESET at all? Otherwise, besides
the performance overhead of starting up a new (additional) activation
group, are there any other caveats I should be aware of with calling
programs in a different activation group? Thanks.

Sincerely,

Dave Clark