![]() ![]() ![]() Always get the latest version and install an update whenever it is available. To start the analysis, you need to install iDoctor server package on IBMi LPAR and a client module on a Windows workstation. If it very difficult find a real problem if you work on average from 30 min intervals Definitely I do not recommend value bigger than 15min. I recommend change to 5 min if you are working on some problems. As you know PT1 can record collections in different intervals. Then, you can always move over the performance collection data from P30 to P05 and run analyses. Thus, if you run multiple P30 machines and P05, definitely the license for P05 will be a way cheaper. iDoctor is charged for an entire machine, and pricing depends on the processor tier. If a performance problem appears on the production LPAR, you definitely don’t want to utilize the LPAR more by running performance analysis. But in this post, I focus on PT1 data only with basic functionality.ĭo you need to install iDoctor on every LPAR? I run the tool only ‘non-production’ LPAR for couple of reasons. The tool has a lot of other functionality such as, illustrating VIOS data, Job Watcher collection, Plan Cache, Disk Watcher and many more. What exactly IBM iDoctor does? It illustrates data collected via Performance Tools (PT1) into nice looking graphs. Therefore you pay for every year of using the tool. Take into account that the iDoctor is sold as a service. By optimizing the application or system, you very likely would save some money on CPU licenses or an extra hardware, this is very likely also a braking point which justify investment into the tool.PDI is very likely targeted to ‘small shop’ type of customer. But iDoctor takes you to microscopic details, that is why it is widely used by IBM support, Lab Services, and business partners. The performance data can be analyzed with both tools. Thus, if you understand the logic in the iDoctor (which work flawless), you can easy switch to sluggish PDI. Which is nothing else as limited version of iDoctor integrated into IBM Navigator for i – build on Java. There is a light version of “iDoctor” embedded in every IBMi OS, know as PDI – Performance Data Investigator.Increasing a CPU would help in most situations but the real problem might be slow disk, wrongly set journaling or application locks. Most of IBMi admins get to a performance issues and personally I heard dozen of times stories “We need to buy an extra CPU because our system is slow”.Why do I even write about an iDoctor which is an extra charged product ? I do it for couple of reasons: So, you can give a try without paying a single penny, or ordering an expensive consultant. Not sure if you know, but the tool is available with 45-days free trial. I want to show you in very simple steps how to do a basic analysis. These days, I can’t live without it, and every single serious performance analysis starts with the tool. Few years ago, I didn’t know the tool either, and I’ve heard lot of wired stories what the aim is. I want to introduce IBM iDoctor tool to people who does not know it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |