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 CA repository.
You enable the Generic API Analysis feature by identifying unsupported APIs and their parameters in the \<CA Home>\Data\Legacy.xml file. In addition, before you verify your application perform the following steps:
This opens the Options - Project properties dialog box.
This opens the Details dialog box.
The Perform Generic API Analysis 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.
For modified Legacy.xml files, the Legacy.xml file that resides in the \<CA Home>\Data directory gets overwritten when a new HotFix is installed. To preserve the changes made to the file:
Micro Focus strongly recommends that you do not copy the \<CA Home>\Data\Legacy.xml file to the workspace to modify it, as the altered file is merged with the original file every time the parsers are required to read them. The following is an example of a user-defined Legacy.xml file:
<Legacy> <Cobol> <OverloadedDiagnostics> <msg num="2054" sev="2"/> </OverloadedDiagnostics> </Cobol> </Legacy>