Re: AS400 Transaction in performance tools

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

 From the v5r4 Work Management guide - note the end of the 2nd 
paragraph, which mentions transaction count - I think transactions are 
basically hitting the Enter key. And maybe function keys that cause the 
interactive session to do some work.

Total Response Time and Number of Transactions: Following the times and 
dates are the total response time and the number of transactions. The 
total response time is in seconds and contains the accumulated value of 
all the intervals the job was processing between pressing the Enter key 
at the workstation and when the next display is shown. This information 
is similar to that shown on the Work with Active Job (WRKACTJOB) 
display. This field is only meaningful for interactive jobs.

It is also possible in the case of a system failure or abnormal job end 
that the last transaction will not be included in the total. The job end 
code in this case would be a 40 or greater. The transaction count is 
also only meaningful for interactive jobs other than the console job and 
is the number of response time intervals counted by the system during 
the job.


OK - here it is, as I search for "transaction" further into the manual -

Note: A transaction is defined as any operator interaction, like 
scrolling, pressing enter, pressing function keys, and so on. Typing at 
the workstation without pressing enter is not considered a transaction. 
If a job at the workstation does not meet the inactive criteria, the job 
is considered active.

HTH
Vern

On 8/28/2010 2:57 AM, ia ca 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!