In my previous post, we dove deep into the MRI Db2 for z/OS Solutions Report from a mainframe perspective - MRI for Db2 Tips & Tricks, focusing on the top five tips to overcome common struggles with the Toolkit part. Today, let's take a break from the mainframe world and explore how to effectively utilize the web part of the MRI Db2 for z/OS Solutions Report. We'll address common issues and provide tips to help you get the most out of the reports, ultimately speeding up your work and maximizing your results.
Here are five essential tips to keep in mind:
-
Use the Correct Code Page for File Transfers from the Mainframe. When transferring the JSON file from the mainframe to your workstation, always use text mode transfer with code page 1047 Latin 1/Open Systems. Failing to do so can result in unexpected character code page translation issues, rendering you unable to generate a report from the JSON file.
-
Utilize Trending Charts. The MRI Db2 for z/OS Solutions Report supports trending charts for various data points, including APPLCOMPAT distribution, Packages with plan management, Invalid and inoperative packages, Db2 13 Readiness reports, and much more. Trending charts highlight spikes or dips in activity, helping you determine whether a data point value is increasing or decreasing over time.
For example, you can collect this data every two weeks, monthly, quarterly, or any other meaningful interval. The trending charts use interpolation algorithms to calculate data for a single data point and fill in potentially missing information. This can help you identify necessary changes in your environment or anticipate future needs. To build the trending report for multiple time points, use the MRI wizard to upload all relevant JSON files from the mainframe scans and generate the report.
- Implement a Naming Convention for Uploaded Files. Using a consistent naming convention for your uploaded JSON files is essential, especially when creating reports with trending charts. For instance, you might name your JSON files for monthly scans like this:
datacenter_A_scan_january_2024.JSON
datacenter_A_scan_february_2024.JSON
datacenter_A_scan_march_2024.JSON
datacenter_B_scan_january_2024.JSON
datacenter_B_scan_february_2024.JSON
datacenter_B_scan_march_2024.JSON
When selecting files in the Upload Files & Request Report wizard, you can type “datacenter_A” into the search box to easily filter and select all relevant files. This practice is particularly useful when you have hundreds of JSON files uploaded over the time, helping you quickly identify the desired data points.
- Analyze Recommended zParms. One valuable feature is the Recommended zParms report. This overview table shows the current settings in use at your site for each Db2 subsystem and the default values for each zParm. Additionally, it provides best practice recommendations to improve performance, potentially leading to cost savings. This information is especially useful for database administrators and system programmers planning upgrades and migrations. The recommendations are also Db2 version sensitive and may vary depending on your Db2 version.
Important: Even recommended values may not fit your organization's specific needs and should be considered as a guide. Always verify the impact of potential changes on your systems, as the recommendations may not always introduce the desired benefits.
-
Use Detailed Reports for Migration Planning. The Db2 13 Readiness report provides an overview of the challenges you may encounter during your migration to Db2 13, including trends over time. This information can help you determine if your Db2 environment is ready for migration. However, the charts offer just an overview, giving the counts of affected objects.
To fully leverage the report, you may need to know the exact names of objects affected by the migration to Db2 13. To do so, you can optionally generate detailed reports on the mainframe, listing these objects. The JCL library hlq.RPRTJCL, created during the MRI Toolkit customization process, contains tailored JCLs RP3Rssid for each Db2 subsystem. Submit the JCL for the desired subsystem to get the full Db2 13 Migration Readiness report. You can also edit the RP3Rssid member to limit the output, such as only listing table names with Inconsistent Version Numbers or Deprecated Basic Row Format Table Spaces.
We hope that you find these tips beneficial for optimizing your experience with the MRI Db2 for z/OS Solutions Report. Should you have any questions or require assistance, please do not hesitate to reach out.
Lukas Patera
Software Engineer