Defining alias names for programs
If you need to define an entry point as an alias to Rational® Asset Analyzer, use the information in this topic.
About this task
- Ensure that a program with the named entry point has been scanned into the database. If the program is not there, scan it using the "Collect inventory" wizard. (You must have administrative authority to perform inventory collection.)
- Define the entry point as a utility by editing the utility file. See the related topics for more information about defining a program as a utility.
- Define the entry point as an alias of some other existing entry point by editing the aliases file.
The following example illustrates a situation in which it is helpful to define an entry point as an alias. Assume you have program PGMA that calls an entry point named SORT. In your production environment, PGMA is link-edited with options that cause it to include the entry point MYSORT and rename it to SORT, enabling the entry point to resolve. In Rational Asset Analyzer, the records in the aliases file provide a similar mechanism. These records tell the run unit builder what alternative names (aliases) to search for when it cannot resolve an entry point with a given name. The aliases file is used during postprocessing.
Defining aliases on System z
Procedure
To define alias names for programs in Rational Asset Analyzer for System z®:
Results
Subsequent postprocessing uses the updated file. For the example above, when the run unit builder does not find the SORT entry point that the PGMA run unit needs, it then attempts to find an entry point named MYSORT to use when resolving the call from PGMA.
Defining aliases on Windows
Procedure
To define alias names for programs in Rational Asset Analyzer for Windows:
Results
Subsequent postprocessing uses the updated file. For the example above, when the run unit builder does not find the SORT entry point that the PGMA run unit needs, it then attempts to find an entry point named MYSORT to use when resolving the call from PGMA.