Performance Tuning
This is one of the things you might look at while trouble shooting Degradation, but in fact ought to check periodically, to avoid a problem developing and not being spotted. Doubtless someone may update this article to reflect improvements in IBM eServers in later models. The reality of what is needed will vary greatly by what you have on your 400 hardware, in terms of system load, and which version of OS/400 or i5/OS.
Al Mac has similar notes at work in FIXTUNING, an SEU "document." Some of the terminology used by Al Mac may not be the correct stuff ... instead sometimes Al Mac has assigned names to a technique learned, or figured out outside formal 400 education, and not known what name would be better.
Contents
- 1 Brain Overload
- 2 Errors and other Clues
- 3 Application Software Review
- 3.1 Batch Considerations
- 3.2 Blocking
- 3.3 CPU Sharing
- 3.4 Call Frequency
- 3.5 Data Slicing
- 3.6 Debug
- 3.7 Disk Access
- 3.8 Logicals
- 3.9 Message Over Load
- 3.10 Open Query File Optimization
- 3.11 Program Performance Optimization
- 3.12 Query
- 3.13 Random Inefficiency
- 3.14 Read Slowly
- 3.15 Run Priority
- 3.16 Screen Restructuring
- 3.17 SQL ADVISOR
- 3.18 Start Stop Start Stop to Infinity
- 3.19 Update Productively
- 3.20 Write Slowly
- 4 Backup Management
- 5 Disk Space Cleaning
- 6 Management Central
- 7 System Values
- 8 Task Scheduling
- 9 Other Resources
Brain Overload
This is a collection of complicated topics that can take a while to wrap our mind around and thoroughly "Grok", so pick one area, study it, leave the others alone, until ready to move on to something else.
Choices
Pre Requisites
What prior knowledge of the 400 is is smart for you to have some of, to help you swim in these waters?
