Moving to a Profound UI environment

[HowardA]

If we implement Profound UI for all our work, and get rid of 5250 (but for a console or workstation to run backups and the like).
what are recommended changes to a system? I'm thinking that we have the majority of our workload in "interactive" now so I'm sure there's an abundance of memory allocated to interactive processing, but moving to Profound seems to use batch (or not interactive anyway).
What "tuning" would we want to do, to get the most out of our hardware dollars?
I'm assuming the amount of disk is not really much (just the new profound run time and our converted screens replace our existing 5250 screens). SO I'm thinking Memory allocation may be the thing that needs to be adjusted? If so, are there recommendations on how to do that once we're off of interactive?

[David]

You are right -- the primary 'tuning' that you'll need to do is in memory allocation. The HTTP server is, of course, much more memory-intensive than green screens.

If you are running sessions through Genie, your applications do still run in interactive jobs. If you are not running through Genie, then they run in batch jobs.

Either way, there is an additional HTTP server job associated with each application session job which manages communication with the web browser.

So, it's important to ensure that plenty of memory is available to the HTTP server. No special recommendations there, you'd use standard memory tuning techniques. I.e. adjust memory pools, monitor page faults, repeat as needed.

We've had some customers report that running the QHTTPSVR jobs in their own memory pool helps -- your hardware partner could probably advise you best there.