On Thu, 13 December 2001, wrote:

> I have been asked to come up with a plan so that no user will ever have to 
> more than 30 seconds for an AS/400 interactive response.  The request (from 
> company president) was based on a completely out-of-context observation of one
> user who had to wait 2 minutes for a response to one particular screen on one
> occurrence.  The president's intent is good, he just does not know what he is
> asking for.

>From seeing the other posts and your responses, I don't think you need much 
>more advice. Your plan was a good one from the start. But I do have one 
>suggestion on managing expectations.

I suggest you create a couple situations guaranteed to show long response times 
and ask your president how they should be handled. For example, bring a record 
up for update in one session but don't press <Enter>, i.e., establish a lock. 
Then try to update the same record in another job. Tell the president "I need 
your ruling on some things. The user at the first session has just gone to 
lunch. The second session user cannot update that record until the first user 
comes back. How do you want me to implement the 30-second rule in this case?"

I realize JDE might handle this specific situation through application code, 
but you can create the demos in other ways. Another possibility might involve 
waiting for a message to be replied to. There are numerous possibilities.

The point would simply be to make sure it was understood that it might not 
physically be possible for you to implement the 30-second rule without causing 
side-effects worse than long response times or requiring major programming 

Tom Liotta

Tom Liotta
The PowerTech Group, Inc.
19426 68th Avenue South
Kent, WA 98032
Phone  253-872-7788
Fax  253-872-7904

The ALL NEW CS2000 from CompuServe
 Better!  Faster! More Powerful!
 250 FREE hours! Sign-on Now!

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.