Re: AS400 Transaction in performance tools

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

 HTTP is interactive to the user but is batch to the system. That is 
why when you use SQL statements in a CGI job that it optimizes for 
*ALLIO - that's a batch choice. Interactive should be *FIRSTIO - I 
recommend, and I think JDEdwards does - that a QAQQINI file be used in a 
CGI job to force *FIRSTIO. If you run that kind of thing with visual 
explain, you will see the choice made in a CGI job.

CGI jobs are not interactive because there is not 5250 screen in use. 
Generally speaking, that is.

Vern

On 8/28/2010 7:30 PM, SirJohn wrote:
>     Greetings,
>     Why would this be only interactive?  HTTP is interactive and runs in
>     batch.
>     Don't you have to consider that?  How does that get measured?
>     John
>     Kirk Goins wrote:
>
>   So it is a measure Interactive work ( No Batch ). Sounds like anytime the
>   system must interact with a display session is a transaction.
>
>
>   On Sat, Aug 28, 2010 at 12:57 AM, ia ca [1]<iaca400@xxxxxxxxx>  wrote:
>
>
>
>   Hi Guys,
>
>   I'm compiling an AS400 performance report for management and I've just been
>   asked a question which I can't provide a basic answer:
>
>   What is an AS400 transaction?
>
>   The best answer I can come up with so far is saying any database read and
>   write on the iSeries is a transaction.
>
>   What's the best way to explain an AS400 transaction?
>
>   Thanks!
>    --
>   This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>   To post a message email: [2]MIDRANGE-L@xxxxxxxxxxxx
>   To subscribe, unsubscribe, or change list options,
>   visit: [3]http://lists.midrange.com/mailman/listinfo/midrange-l
>   or email: [4]MIDRANGE-L-request@xxxxxxxxxxxx
>   Before posting, please take a moment to review the archives
>   at [5]http://archive.midrange.com/midrange-l.
>
>
>
>
>
>
>
> References
>
>     Visible links
>     1. mailto:iaca400@xxxxxxxxx
>     2. mailto:MIDRANGE-L@xxxxxxxxxxxx
>     3. http://lists.midrange.com/mailman/listinfo/midrange-l
>     4. mailto:MIDRANGE-L-request@xxxxxxxxxxxx
>     5. http://archive.midrange.com/midrange-l