Re: limit users max active jobs

Jay,

I am a BIG fan/user of "subsystem routing by user".

It can all be done on the fly (carefully), with or without an iASP, and you
decide which jobs types are included/excluded. You can really clean-up and
take control of QSERVER and QSYSWRK. I've never had to take down or
restrict any LPAR to accomplish our configuration controls.





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

should have been more specific...

not so much wrong with odbc/jdbc connections... but off platform queries
against the DB2 tables is a problem that most large companies definitely
take note of and have began restricting...
(stored procedures ok - a webservice that returns a true data object (like
JSON or XML) instead of a columned result set is even better)...


Here are some advantages I can think of for using a http endpoint that
calls an i sqlrpgle that accepts and returns a JSON/XML object...



1. queries/DB access are kept on iSeries along with database DDL and
program source code – if ever there is a change in table structures, the
dependent programs will easily be identified (via cross reference tools
-
ie. hawkeye, x-analysis, etc.)
2. Reduces required talent needs – the data can be pulled and packaged
to a json output (from an i developer) and delivered straight to a front
end ui/ux developer.
3. The sql queries within the sqlrpgle programs will be very efficiently
written by i developers who know the database the best.
4. if the http endpoint is developed a certain way it falls into the
flow of how most i shops roll out new programming in change management
systems (such as turnover). A few years back when I was at a certain
very
profitable Berkshire Hathaway company, with 100+ iSeries developers and
many .net’rs, they implemented true soap and rest webservices (with
pcml)
and this was an absolute nightmare pushing it up through the change
management system. At my next gig, their very clever solutions
architect
devised the model I speak of and it worked beautifully within the
iSeries
shop and change management system.
5. i developers will be working with newer more modern methods that are
more exciting and interesting.
6. Can very easily be leveraged into a MVC framework.



On Wed, Mar 13, 2019 at 4:56 PM Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 3/13/2019 4:06 PM, Jay Vaughn wrote:

Now if I can only convince them that the off-platform jdbc/odbc calls

are

the wrong way to pull data from the i to begin with, we will be much

better

off.

We use ODBC for thousands and thousands of web transactions. We do not
expose the database to ODBC - the underlying tables are secured against
public access. We expose information via stored procedures which adopt
appropriate authority.

With respect to the subject of the thread, if we find a performance
issue, we can work on that one program until we meet expectations. We
don't have a full suite of tests for every stored proc, but we're
working on it. Once we get there, we will be able to automatically
stress test the system after making changes.

--
--buck

http://wiki.midrange.com
Your updates make it better!

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com