Troubleshooting
When you run map coverage, you might encounter issues with report generation, missing information, or platform restrictions. Use the following information to diagnose and resolve common map coverage problems:
Coverage settings file not found
If the command-line utility reports that it cannot find the coverage settings file, verify that the mcs.json file exists in the same directory as the compiled map (.mmc) file. The file must be named exactly <map>.mcs.json, where <map> matches the map file name without the .mmc extension.
Details or Verbose report shows no rule text
Rule text is only available when the source map files
(.mms and .mdg) are accessible. Ensure
that the Source Maps location is configured in your coverage settings or that you
specified the -SOURCEMAP option on the command line. If the source
files were moved or renamed after the map was compiled, update the path
accordingly.
Interim report not generated after execution
If the interim report file (<map>.mcr~.json) is not present after running coverage, check your OnRunError setting. If a coverage run fails and OnRunError is set to Stop, subsequent runs are not executed, and the interim report might not be fully written. Set OnRunError to Continue to allow all runs to complete regardless of individual failures, and then investigate the specific failing run using the LogLevel setting.
Coverage view not appearing in Design Studio
If the Coverage tab does not appear in the properties panel after you run coverage, confirm that you activated the map coverage mode before running the map. The Map coverage toolbar button must be active and highlighted. Additionally, verify that the final report file (<map>.mcr.json) was created successfully in the map directory.
Summary tab displays a 0% coverage score
If the main map fails to run, for example, because a source is unavailable, the status displays as Not Covered with a 0% coverage score. The tab provides the specific error code associated with the failure so that you can investigate the issue.
Summary tab displays a message that no active source map is open
If you attempt to view the summary report when the source map is not currently open, the system displays a message indicating that there is no active source map open. You must open the source map to view the coverage report.
Cannot generate detailed reports on restricted platforms
Map coverage is not supported on DataPower, z/OS BATCH, or CICS. On AIX, zLinux, and z/OS USS, only Outline level reporting is supported during execution. To generate Details or Verbose reports for these platforms, port the generated interim report file (<map>.mcr~.json) to a Windows or Linux system and run the dtxcoverage utility using the -REPORTONLY option.