Re: limit users max active jobs

I think it will depend rather heavily on what you are actually doing.
Read-only casual use or enquiries should be fine.
If you have any hard-core batch reporting/extract/update type activity with
large numbers of records then your results may differ.
JDBC/ODBC has its place but it depends on what you are trying to do.

On Thu, Mar 14, 2019 at 1:16 PM Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
wrote:

That’s encouraging.
I think this route will serve us well.

Jay.

On Mar 13, 2019, at 7:49 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

Jay,

I just wanted to express my support for your efforts to replace odbc/jdbc
with IBM i web services and to wish you well in that endeavor. I think
you're headed in the right direction.

On Wed, Mar 13, 2019 at 12:03 PM Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
wrote:

so we have a particular userProfile that executes off platform odbc/jdbc
calls. (yuk - i'm currently in negotiations with upper management to end
those and use YAJL rest instead)...

anyway in the interim... what is best way to allow user to only be able

to

have say 4 active jobs running at a single time? as you may guess, the
sessions will hang and continue running and eat up resources.

at first I considered chgusrprf LMTDEVSSN to 4 but then realized that

may

only be for interactive sessions...

tia