Identifying Unsupported API Calls to the Parser

Follow the instructions in the steps below and the detailed specifications in the following sections to identify unsupported API calls to the parser. For each call, you need to define an entry in \<Enterprise Analyzer Home>\Data\Legacy.xml that specifies at a minimum:

  • The name of the called program and the method of invocation in the <match> tag.
  • The program control flow in the <flow> tag, and the direction of the data flow through the parameters of interest in the <param> subtags.
  • How to represent the call in the object model repository in the <rep> tag, and in the construct model repository in the <hc> tag.

Use the optional <vars> tag to extract values of a specified type, size, and offset from a parameter for use in a <rep> or <hc> definition.

Most repository entities can be represented in a <rep> or <hc> definition with the predefined patterns in \<Enterprise Analyzer Home>\Data\Legacy.xml.api. These patterns do virtually all of the work of the specification for you, supplying the relationship of the entity to the called program, its internal name, and so forth.

The syntax for specifying predefined patterns in a <rep> or <hc> definition is described in the section for the tag. Consult Legacy.xml.api for supported patterns and for required parameters and values:

  1. Open the file \<Enterprise Analyzer Home>\Data\Legacy.xml in an editor.
  2. Locate the <GenericAPI> section for the language and dialect you use.
  3. Create entries for each unsupported API call, following the specifications in the sections below and the samples of Generic API usage in Legacy.xml.
  4. Click Options > Project Options. This opens the Options - Project properties dialog box.
  5. Click the Verification tab.
  6. In the Advanced Program Analysis group, click Advanced. This opens the Details dialog box.
  7. Check Perform Generic API Analysis.
  8. Click OK.
  9. Verify the project.
Parent topic: Identifying Interfaces for Generic API Analysis