Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

How can an Assembler Macro be mapped to a call statement in Enterprise Analyzer using Legacy.xml?

How can an Assembler Macro be mapped to a call statement in Enterprise Analyzer using Legacy.xml?

Problem

How can an Assembler Macro be mapped to a call statement in Enterprise Analyzer using Legacy.xml?

Resolution

Within Enterprise Analyzer (EA) by making changes to the legacy.xml file it is possible to map macros to standard program structures. The mappings that are supported in legacy.xml are:

            Defining Program Entry Points

            Loading the External Name

            Using an External Name in Calls

In this wiki the ‘Using an External Name in Calls’ option is to be used. As with any modifications to the legacy.xml, it is recommended that the legacy.xml that is created, is placed in the workspace directory and that the system legacy.xml is left untouched. This means that changes required for a workspace are maintained, as applying any Hot Fixes to EA can result in the system legacy.xml being altered.

The legacy.xml that appears in the workspace directory can be a cut down of the original legacy.xml and will be loaded for the specific workspace after the system legacy.xml. This does mean that different workspaces can have different customisations to the legacy.xml.

Mapping the routine macro to a call statement

The template to be used is the calling template within the assembler tag in the legacy.xml file. To map the macro ‘routine’ to act like a call statement, the legcy.xml entry becomes:

<!--- Add a macro called routine that acts like a call -->

     <Calling>

       <Macro name="ROUTINE">

         <!-- Parameter is the first parameter of the macro -->

         <Parameter number="1" type="String" meaning="Name"/>

       </Macro>

     </Calling>

Attached to this wiki is an example legacy.xml, showing how the mapping of routine fits into the legacy.xml file. Note: it is possible to combine this with other legacy.xml customisations by placing the whole of the assembler tag structure into another legacy.xml.

 Legacy_Assembler_Rountine_Macro.xml

Incident # 2692079

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Version history
Revision #:
1 of 1
Last update:
‎2014-08-04 13:59
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.