This message is similar to IGW01553I in which the alias name of primary member pname has been successfully processed and the primary member was also successfully processed. This message always includes additional information: either the alias replaced something in the output data set, or renaming occurred during the copy operation.

Form 1 applies when the primary member was renamed; it may appear alone or combined with form 2 (alias renamed). Additionally it may be combined with any one of forms 3-9 (replacement).

Form 2 applies when the alias was renamed; it may appear alone or combined with form 1 (primary renamed). Additionally it may be combined with any one of forms 3-9 (replacement).

Forms 3-9 apply when the alias name replaced a member name or another alias name in the output data set. Forms 3-9 may appear alone or combined with Form 1 (primary rename), or with Form 2 (alias rename), or with both Forms 1 and 2.

Form 3 applies when an alias and its primary both replace their counterparts in the output data set; the alias name replaced an alias, and the replaced alias had a primary which was also replaced by the primary pname.

Form 4 applies when the alias name replaced a primary member name in the output data set which had no aliases. The replaced primary is no longer available.

Form 5 applies when the alias name replaced a primary member name in the output data set which did have aliases. The replaced primary is no longer available. Any aliases for this replaced primary which are also replaced in the output data set (by any alias or member from the input data set) will be identified in the message for the member or alias which replaced it. If any aliases of the replaced primary were not replaced, they will be identified in messages which appear somewhere prior to this one. If the output data set is a PDSE, any not-replaced aliases will be deleted. If the output is a PDS, they will not be deleted.

Form 6 applies only when the output data set is a PDS which had a very rare, incorrect data situation: there was another member with the same TTR number as the replaced member, but neither was identified in its directory entry as an alias.

Form 7 applies when the alias replaced an alias name of a correct member which WAS NOT replaced. That is, even though the names of the replaced and replacing aliases are the same, the names of their respective primary names are not the same.

Form 8 applies when the alias replaced an alias name of a correct member which WAS replaced. However, the replaced member was not replaced by the primary pname specified in this message. It was replaced by some other primary or alias name rname.

Form 9 applies only when the output data set is a PDS which had an incorrect data situation which can occasionally occur in a PDS with aliases. The alias replaced an alias name, but there was no correct primary for that alias. The situation may have been created in the past during a copy operation if the primary was replaced, but the alias was not (such as form 5 of this message).