IGW01556I
(form 1) ALIAS name OF NOT-SPECIFIED PRIMARY pname HAS BEEN {COPIED | LOADED | UNLOADED} AND RENAMED FROM name2      or(form 2) ALIAS name OF NOT-SPECIFIED PRIMARY pname HAS BEEN {COPIED | LOADED | UNLOADED} AND REPLACED A PRIMARY WITH NO ALIASES      or(form 3) ALIAS name OF NOT-SPECIFIED PRIMARY pname HAS BEEN {COPIED | LOADED | UNLOADED} AND REPLACED A PRIMARY WITH ALIAS(ES)      or(form 4) ALIAS name OF NOT-SPECIFIED PRIMARY pname HAS BEEN {COPIED | LOADED | UNLOADED} AND REPLACED A PRIMARY IN AN INVALID GROUP WITH SECOND PRIMARY pname2      or(form 5) ALIAS name OF NOT-SPECIFIED PRIMARY pname HAS BEEN {COPIED | LOADED | UNLOADED} AND REPLACED AN ALIAS OF NOT-REPLACED PRIMARY pname2      or(form 6) ALIAS name OF NOT-SPECIFIED PRIMARY pname HAS BEEN {COPIED | LOADED | UNLOADED} AND REPLACED AN ALIAS OF A PRIMARY BEING REPLACED BY rname      or(form 7) ALIAS name OF NOT-SPECIFIED PRIMARY pname HAS BEEN {COPIED | LOADED | UNLOADED} AND REPLACED AN ALIAS WITH NO VALID PRIMARY      or(form 8) ALIAS name OF NOT-SPECIFIED PRIMARY pname HAS BEEN {COPIED | LOADED | UNLOADED} AND IS NOW PRIMARY      or(form 9) ALIAS name OF NOT-SPECIFIED PRIMARY pname HAS BEEN {COPIED | LOADED | UNLOADED} AND IS ALIAS OF newpname (THE NEW PRIMARY)      or(form 10) ALIAS name OF NOT-SPECIFIED PRIMARY pname HAS BEEN {COPIED | LOADED | UNLOADED} AND IS ALIAS OF newpname (THE NEW PRIMARY) WHICH WAS RENAMED FROM oldpname

Explanation

An alias name of primary member pname has been successfully processed. The primary member, however, was NOT processed because it was not specified in the list of names provided for the copy operation. Replacing and/or renaming may have occurred also.

Form 1 applies only when the alias was renamed. It may be combined with any one of forms 2-7 (replacement), and it will always be combined with one of the forms 8-10 (new primary identification).

Forms 2-7 apply only when the alias name replaces a member name or another alias name in the output data set; these forms tell the nature of that replacement. These forms may appear combined with form 1 (alias rename), and if they do appear they must be combined with one of the forms 8-10 (new primary identification).

Form 2 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 3 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 were 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, these not-replaced aliases will be deleted. If the output is a PDS, they will not be deleted.

Form 4 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 5 applies when the alias replaced an alias name of a correct member which WAS NOT replaced.

Form 6 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 7 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 3 of this message).

Forms 8-10, one of which is always required for this message, can appear alone or in combination with forms 1 and 2-7. Forms 8-10 describes the new primary in the output data set (since the old primary was not copied). If specific names were identified to be copied, then the first successfully copied name in a group of alias names in the order specified became the new primary. If specific names were not identified (and the entire data set was being copied), then the first successfully copied name in a group of alias names in collating sequence became the new primary. Form 8 applies when the alias named first in this message became the new primary.

Form 9 applies when another alias became the new primary and was NOT renamed during the copy operation.

Form 10 applies when another alias became the new primary and WAS renamed during the copy operation.

In the message text:
form
The specified form that applies to the message.
name
The specified alias name.
pname
The specified primary name.

System action

Processing of the current request continues.

Operator response

Verify that the results are as intended.

Source

DFSMSdfp and File and Attribute Management Services.

Routing code

11

Descriptor code

6