Skip to content

Discovery troubleshooting

Use this page when Discover Code or Discover Metrics finishes with warnings, produces large undiscovered-entities or src/maybe folders, or creates results that do not match your source inventory. Review the outputs first, correct the underlying source or configuration issue, and then rerun the affected Discovery step.


Review the first outputs

After a Discover Code run completes, verify the following before you continue to Metrics or DNA:

  • Expected languages appear under the src/ folder.
  • Module counts roughly match the source inventory that you captured during pre-discovery.
  • undiscovered-entities and src/maybe contain only exceptions, not the bulk of the source package.
  • The job log does not show unexpected warnings or repeated parse failures.
  • Expected source objects appear in the Mining project after the upload completes.

If these checks fail, fix the source package or Discovery configuration before you proceed to Discover Metrics.


Use job logs and UI feedback

Discover Code and Discover Metrics both create job logs that help you diagnose failures and partial results.

  • Eclipse downloads job logs such as discover-code-<random id>-<timestamp> and discover-metrics-<random id>-<timestamp> to the workspace.
  • The Mining Web UI Job Framework lets you review job status and open logs from the browser. See Additional features.
  • The log is the fastest way to confirm whether the issue is caused by parse errors, unresolved dependencies, upload warnings, or configuration mismatches.

Common Discover Code issues

Issue Likely cause Recommended action
Many files end up in undiscovered-entities File extensions are missing or incorrect. Normalize the extensions, split concatenated files if needed, and rerun Discover Code.
Files end up in src/maybe Source structure is ambiguous. Move files into clearer language or type folders or add the correct extensions before rerunning.
COBOL files do not parse COBOL source uses non-standard margins. Review the COBOL parser margin settings and rerun Discover Code.
Natural files are missing or incomplete The source was not extracted in SYSTRANS format. Re-extract the Natural source with SYSOBJH, replace the files, and rerun Discovery.
Unexpected language classification Extension mappings or enabled languages are too broad. Review extensions, disable languages that are not present, and rerun Discover Code.
Job log shows "Multiple possible candidates found" Discovery cannot resolve dependencies uniquely. Add or refine discovery-search-order.xml, upload the configuration, and rerun.
Utilities show up as missing modules utilities.xml is incomplete or exclude_utility is not configured. Update utilities.xml, review exclude_utility, upload the configuration, and rerun.
Upload stops at a large-file warning The encoded file content exceeds the 16 MB limit. Split the large file when possible, or allow the large-file upload only after you confirm the source is valid.

Iterate and rerun safely

Use an explicit fix-and-rerun cycle when the first Discover Code output is not usable.

  1. Compare the output against the source inventory and note the main mismatches.

  2. Correct the source package, file layout, extensions, or Discovery configuration.

  3. Upload the updated Discovery configuration with discovery > Advanced > Upload Configuration.

  4. If the source package changed significantly, force a fresh source upload with discovery > Advanced > Upload Source Code.

  5. Rerun Discover Code on the affected selection and review the output again.


Rerun Discover Metrics when structure changes

Rerun Discover Metrics after any change that affects module identity, dependencies, or Discovery configuration.

  • Rerun Metrics after you fix extensions, split files, change margins, change search-order rules, or update utilities.
  • If incremental scanning is enabled and you need a full refresh, use discovery > Advanced > Force Full Discover Metrics Scan.
  • After Metrics is consistent again, continue with Discover DNA if needed.

  • Use Pre-discovery workflow to catch package and configuration issues before the first run.
  • Use Code Discovery when you need to review configuration settings in detail.
  • Use Code Discovery when you need to rerun Discover Code or upload revised sources.