The iCluster Files with Constraints Report
In our post on Tuesday March 10th, we covered the Files with Triggers Report, which is option 7 from the Reports Menu. In this post we will cover the next report, File with Constraints.
Use the DMRPTCST command to access this report as below. The command will report on all files using the current node as the primary node that are in replication scope for the PAYROLL group and have constraints. The results will be placed in a database file called MYCSTFILE in MYLIB.
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 constraints.
Just like the Files with Triggers report, 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 2 files, INVENTORY in library PAYROLL and the same file in library PAYTEMP, have constraints. The constraint is a *PRIMARY key constraint on key ITEM_00001 with a system generated name of QSYS_INVENTORY_00001 in the library PAYROLL.
Note: The report indicates the number of database files processed for each group however, only those files that have constraints are listed in the report.