Understanding DDUPDATE BTG error DDPAL10001 (duplicate alias)
search cancel

Understanding DDUPDATE BTG error DDPAL10001 (duplicate alias)


Article ID: 201634


Updated On:


Datacom Datacom/DB


Running DDUPDATE to apply BTG transactions from another MUF caused a failure on an alias definition for the Area and Table I am changing. Can I just ignore the error message because I don’t need the alias and my tables look good? If not, can I just delete the line with the 1103 Alias command and do DDUPDATE BTG or I do have to run DELETE command?


Component : CA Datacom/DB



An alias in Datadictionary is used to provide an alternate name for something. In the case of a table, I might have a table called User-definitions, but then I could have an alias called Don-table. This allows me to use "Don-table" in my programs or other utilities.

There might be valid reasons to have an alias, and it might be necessary to check with your application programming teams to see why there is an alias defined for the table and areas. 

If you discover that there is no reason to have the alias definitions, then delete the 1103 ADD xxxxxx commands from your BTG file and proceed normally.

However, if you find that you do need these alias definitions, and that they point to a different entity or version (causing the duplicate error), you then need to find out if you need some other alias for the table/area, or if this table/area should have a different alias. An alias must be unique within the entity type (Table, Area, or other).

You can delete the alias in the Datadictionary by using DDUPDATE with input like this:

(signon card if needed)
-UPD AREA,<original entity name> (<ver>)
1103 DEL <aliasname>
-UPD TABLE,<original entity name> (<ver>)
1103 DEL <aliasname>

Then you can run the BTG file you have as it is.

The key here is to understand why the alias is needed, and what it is supposed to be defining. Once you know that info - if the alias is needed at all - then you can move ahead and set it up correctly


Additional Information

For more information on using the Datadictionary Alias transaction (1103), please see the DDUPDATE documentation for "1103 Alias Transaction."

As always, please contact Broadcom support for CA Datacom if you have further questions.