How can an Assembler Macro be mapped so that Enterprise Analyzer treats it as a call statement?

Problem

How can an Assembler Macro be mapped so that Enterprise Analyzer treats it as a call statement?

Resolution

Within Enterprise Analyzer (EA) there are two ways to extend how the assembler treats user defined macros that are used to change the way that assembler works.

The first is to use legacy.xml and the generic mapping section of the assembler section of the legacy.xml. For more information on that approach see this wiki: How can an Assembler Macro be mapped to a call statement in Enterprise Analyzer using Legacy.xml?

The second is to use Architecture Modeller (AM) to create the relationship and the instance of the program entry point entity, that is required for this relationship. For more information on that approach see this wiki: How can an Assembler Macro be mapped to a call statement in Enterprise Analyzer using Architecture Modeller?

The advantage of legacy.xml approach is that it is easy to setup and if the macro that needs to be mapped is not very complex it should provide the functionality required.

The AM route is more complex, but is more flexible as any relationship required can be mapped . AM needs to be used when the macro is more complex and will not fit in the legacy.xml approach.

Incident # 2692079