×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
How would
you know for sure that a job got swapped out to disk? Is this information
recorded somewhere?
I'm not technical enough to dig into the bowels, and put an exact status on
something. But you can see Elapsed AuxIO on the WRKACTJOB screen (F11). This
includes database and non-database paging. It gives you an idea that
something might need to be looked at. But, since a lot of AS400 jobs have
heavy IO it probably isn't the level of detail you are looking for.
I'm thinking of a program that we
have that uses an SQL request that functions normally then suddenly takes a
long time to execute.
SQL has some cool internal features. One is the use of temporary indexes.
These indexes speed up SQL tremendously when they exist, but can take a
while to be created. With SQL, it is important to make sure you have good
indexes across your tables and get rid of the things which cause it to use
slower methods (logicals with select/omit for example). Subscribe to the
Centerfield Technology newsletter. You will pick up some good SQL knowledge.
Performance (especially job level) is a specialized area. The perfomance
tools and associated reports will help you identify what you are looking
for. Also, there is a section on performance in the infocenter. Many
references there.
Mike Krebs
midrange.com
