The iCluster files with triggers report
In our last post we covered the Replication Coverage Report, which is option 5 from the Reports Menu. In this post we will skip over Option 6 which is just the DMDSPLOG command (Event log report) and concentrate on the Files with Triggers Report Option 7.
Use the DMRPTTRG command to access this report as below:
The Files with Triggers report can be run on any node and lists for the group specified or for all groups using the current node as the Primary, the files in replication scope with triggers.
The number of parameters is small, just the Group parameter – either GROUP(*ALL) for all groups using the current node as the Primary which is the default, or a specific group name (no generics allowed). The report is always created in a spool file but the Output parameter allows for it to be optionally displayed on screen using OUTPUT(*) which is the default. Finally you have the option of putting the results into a specified database file in the OUTFILE parameter. If the file exists it will be replaced, if it does not exist it will be created. The default for the OUTFILE parameter is *NONE.
Here is a sample report.
As you can see in this report the Payroll group has 110 files that were processed and only 1 file ACUSTOMER has a trigger. The trigger is enabled and is a before update trigger running program CUSTUPD2 in library PAYROLL. The full trigger name is truncated on this display but is listed in full in the report.
Note: The report indicates the number of database files processed for each group; however, only those files that have triggers are listed in the report.