Minor changes are by default collapsed in the page history.
No changes
The page does not exist yet.
Failed to load changes
Version by on
Leave Collaboration
Are you sure you want to leave the realtime collaboration and continue editing alone? The changes you save while editing alone will lead to merge conflicts with the changes auto-saved by the realtime editing session.
Setting up performance batch reports
To produce batch reports, you must first customize the Performance Reporter component. You can customize Performance Reporter during configuration, or by manually completing the following tasks in this section.
Consider the following prerequisites and tips before proceeding:
Make sure that you have the SYSADM/SYSCTRL privileges on the Db2 system containing Db2 objects for the Performance Reporter to use.
Before customizing Performance Reporter manually, create UBBPARM and UBBSAMP data sets (if they do not already exist) and copy DMRPRJCL from BBPARM to UBBSAMP.
Success
Tip
Sample members use default Db2 object names. If you change one of the object names, be sure to change every occurrence in every sample member. To ensure that you change all occurrences, use the DZPRUCNV utility.
To use this utility:
Modify the DMRPRJCL sample in UBBSAMP to site standards. (For more information see Using-product-libraries.)
Change statements for each object name:
OLD=defaultName, NEW=newName
For each object whose name you want to change, replace newName with the preferred name. When all the changes are complete, change P=NOWRITE to P=WRITE and submit the job.
