ENL - Limitations (Search in Code)

Search in Code - Limitations

The Search in Code feature has several language dependent limitations that must be taken into account when interpreting results.

The following languages/analyzers are NOT supported and cannot be searched:

  • Word Assistant results
  • Reference Pattern “x” type results

The following supported languages have some limitations:

  • All supported languages: You cannot search for a string that contains a comment’s begin/end tags. For example, if your code contains:

    .../*toto*/

    and you enter:

     /*toto

    as your search expression, the Search in Code feature will not return any results. You can, however, search for “toto” and in the above example, results will be returned successfully. This applies when you have chosen to search in Comments (i.e. with the Advanced > Comments option activated). See also the related Universal Analyzer item below. This limitation is also valid for the CAST Analysis Manager “Reference Pattern” feature.

  • VB: Member variables and constants are not handled

  • Java: All package and EJB objects are handled

  • Cobol: No code search for entry-points

  • T-SQL: Objects not stored on the server are not taken into account (ex: tables, indexes, types…)

  • DB2-SQL: The Search in Code feature is not available for:

    • distinct or structured UDT
    • functions without SQL code
    • table aliases
    • indexes (Mainframe only)

  • PB: When selecting the Job to search in Object Selection (Step 1) and searching for a key word that is found in a control, a window control event or in any object container, the Search in Code feature will ONLY return the object containers and NOT the controls or the window control events.

    If you select the objects to search directly in the Graphical View, Search in Code will return ALL results.

  • Oracle Forms: The Search in Code feature for Oracle Forms is based on the functioning of the Reference Pattern for Oracle Forms. The Reference Pattern for Oracle Forms in “Knowledge Base mode” uses the Code Viewer to function (it reads code using the Code Viewer). Please consult the Reference Guide for Oracle Forms in the on-line Help for Analysis Manager for more information about how the Code Viewer for Oracle Forms functions.

  • Universal Analyzer: Text that is part of begin/end tags for the analyzed language is not found by the Search in Code feature. For instance, if the begin tag for comments is defined as “! Summary” in the UA language profile, searching in comments (i.e. with the Advanced > Comments option activated) for “Summary: Make sure that” will not find any occurrence because “Summary” is part of the begin/end tag. You should search for “Make sure that” instead. This limitation is also valid for the “Reference Pattern” feature.

  • SQL Analyzer: The Search in Code feature does not function on results of SQL Analyzer analyses when the target database is either Oracle 10g or 11g.

CAST Website