Use the "Print Trigger Programs (PRTTRGPGM)" command to generate a report showing all physical file triggers on your system. This listing in conjunction with the "Display File Description (DSPFD)" command will provide you with detailed information about the programs and database files involved.

Remember that the worst written program in the world is not a performance issue if it is only called once during a non critical timeframe to your business. We need to identify the trigger programs that are called the most across all jobs on your system. Since these programs are called by the operating system whenever an add, update or delete occurs on these specific files, it would be appropriate to analyze the adds, updates and deletes on these files.

Using the DSPFD command with the *MBR and *OUTFILE options, you can generate a database file containing detailed information about each of the physical files on your system. The important information here is the "Activity Statistics" for each physical file that has an attached trigger program. This data will show the number of write, update and delete operations since the last IPL. Trigger programs are executed for each of these operations. It makes sense to focus on the programs that are called the most.

Using the techniques mentioned earlier on the most heavily used physical file trigger programs can provide significant improvement in the interactive and batch processing response times across your entire system. Our Disk Navigator can facilitate collection of data for this type of analysis. Our Application Optimizer can be used to show the CPU, I/O or duration impact that a trigger program is having within a specific job on your system.