Peter Relson wrote:
An ALIAS is expected to be associated with a "Major" name in the same data set. Almost all processing for an alias is done by tieing in to the major name's entry and taking all the "real information" from there, applying (basically) just the offset information present in the alias to determine the entry point of the alias. Here there is no information maintained about the major (as it was not built into LPA due to being a duplicate). Building the alias was apparently also not done as a result.
The current behavior is understandable, but may be neither reasonable nor desirable. Some of us would prefer that the alias entry be loaded, but treated as the major name entry, with appropriate warning messages. This would facilitate testing, and back out of changes. I haven't looked at DESERV for a while, but off-hand don't remember it giving any warning about duplicate names, either.
Gerhard Postpischil Bradford, VT ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
