Use the Generic API Analysis feature if your legacy program calls an unsupported API to interface with a database manager, transaction manager, or similar external facility. In this call, for example:
CALL 'XREAD' using X
where X refers to a table name, the call to XREAD is of less interest than its parameter, the table the called program reads from. But because the parser does not recognize XREAD, only the call is modeled in the EA repository.
You enable the Generic API Analysis feature by identifying unsupported APIs and their parameters in the file \<EA Home>\Data\Legacy.xml. Before you verify your application, set Perform Generic API Analysis on the Verification tab of the Project Options window. That option tells the parser to define relationships with the objects passed as parameters in the calls, in addition to relationships with the unsupported APIs themselves.
We do not recommend copying the \<EA Home>\Data\Legacy.xml file to the workspace directory and then altering it as needed, since the altered file is merged with the original file every time the parsers are required to read them. An example of a user-defined Legacy.xml is:
<Legacy> <Cobol> <OverloadedDiagnostics> <msg num="2054" sev="2"/> </OverloadedDiagnostics> </Cobol> </Legacy>