Errors
The "Errors" page provides information about scanning errors that must be fixed. Details about scanning errors are available when you click the links on this page. To see distributed scanning errors, click the Activity log errors link.
- Context
- This section is in the upper-left corner of the page. It opens the "Bookmark this page" wizard in a separate window.
- Status messages
- This section is just below the menu on each page and is displayed only when active processing is running. Refresh the page to see the most up-to-date status. Click a message to view detailed summary about the message.
- Actions
- List of action you can perform on the current asset.
- Details
- Shows the error rate for various asset types, such as batch jobs, programs, link decks, and run units. Click a percentage rate to navigate to the asset type errors details page. Each errors details page contains a breakdown of the Analysis status results: Completed, Error, and Incomplete (if asset is on the Analysis queue). Clicking a count link will lead to an asset summary page with the appropriate advanced search filtering in effect. Certain errors details pages include more than Analysis status breakdown, such as Component type breakdown on the Program errors details page and Missing entry points on the Run unit errors details page.
- Also shows the Activity log errors count. The activity log is most useful when following up on analysis errors. Generally speaking, rows from the activity log table correspond to analysis messages displayed on the asset's details page. Clicking the count will lead to the Activity log summary page.
- Error tables
- A series of tables that show the errors by category. Select a
type of error and review and modify each asset in error. Within the
tables, you can do these tasks:
- Click on the plus (+) and minus (-) on each table to expand and collapse the table.
- Click a count to see a summary page of the assets of that type with that error.
- Missing components
- Missing entry points, missing JCL procedures, missing source include files, or missing BMS map set definitions.
- Files with analysis anomalies
- Unrecognized language or type. Language errors involve syntax that Rational® Asset Analyzer does not recognize as one of the supported source languages (COBOL, PL/I, JCL, BMS maps, z/OS® Assembler). The type is used to trigger an analysis for main assets (which are assets that are not included in other source, and are either compiled or used to execute batch jobs for JCL).
- Components with missing or ambiguous parts
- Such as a run unit with ambiguous or missing source. Possible
causes can include:
- Obsolete source
- Source that has yet to be scanned
- IMS assets that have not been scanned
- Invalid language mappings
- Components with syntax errors: batch jobs and programs. These
errors could have the following causes:
- Obsolete or invalid source
- Incorrect concatenation set
- Unsupported syntax (such as IDMS)
- Potential problem areas
- Conditions that could cause inaccurate analysis results.
- Online data stores (CICS® FILE resources or IMS database resources) without an associated data set. These are online resource names that cannot be connected to a physical data set name. Rational Asset Analyzer uses the data set name to infer impact from data that is passed through or changed in persistent data.
- Duplicate files in the inventory. Two types of duplicate files
can cause different problems:
- Duplicate COPY or INCLUDE files
- Rational Asset Analyzer attempts to automatically assign concatenation sets to COPY or INCLUDE files. If you have duplicate files in the inventory, Rational Asset Analyzer does not guess which container's copy is the correct one. You must manually create and assign a concatenation set to identify which copy Rational Asset Analyzer should consider in its analysis when a reference is discovered.
- Duplicate program files
- If the inventory contains multiple copies of a program name (that is, the PROGRAM-ID paragraph in one source code file has a name identical to the PROGRAM-ID paragraph in another source code file), the run unit builder does not guess which program is being referred to in the run unit. You need to remove the duplicate program from the inventory and then rerun postprocessing.