IGW01552I
(form 1) MEMBER name HAS BEEN {COPIED|LOADED|UNLOADED} AND RENAMED FROM name1      or(form 2) MEMBER name HAS BEEN {COPIED|LOADED|UNLOADED} AND REPLACED      or(form 3) MEMBER name HAS BEEN {COPIED|LOADED|UNLOADED} AND REPLACED A PRIMARY WITH ALIASES    or(form 4) MEMBER name HAS BEEN {COPIED|LOADED|UNLOADED} AND REPLACED A PRIMARY WITH SECOND PRIMARY <name>      or(form 5) MEMBER name HAS BEEN {COPIED|LOADED|UNLOADED} AND REPLACED AN ALIAS OF MEMBER name2      or(form 6) MEMBER name HAS BEEN {COPIED|LOADED|UNLOADED} AND REPLACED AN ALIAS OF REPLACED MEMBER name      or(form 7) MEMBER name HAS BEEN {COPIED|LOADED|UNLOADED} AND REPLACED AN ALIAS WITH NO VALID PRIMARY

Explanation

This message is similar to IGW01551I by reporting that a member was successfully copied. Furthermore, the member was either renamed, or it replaced something in the output data set, or both.

Form 1 applies when the member was renamed; it may appear alone or combined with any one of the other forms of this message.

Forms 2 through 7 may appear alone or combined with Form 1; they apply when the member replaced a member or when its name replaced an alias name in the output data set.

Form 2 applies when the member replaced a correct member which had no aliases; it is the most common replacement situation.

Form 3 applies when the member replaced a correct member in the output data set and the replaced member did have aliases. Any aliases of the replaced member which were also replaced will be identified in the message for the member or alias which replaced it. Any aliases of the replaced member which were not replaced will be identified in messages which appear somewhere prior to this message. 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 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 member replaced an alias name of a correct member which was not replaced.

Form 6 applies when the member replaced an alias name of a correct member which was also replaced.

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 member 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).

In the message text:
form
Indicates which form of the message applies.
name
A specified member name.

System action

Processing of the current request continues.

Operator response

Verify that the results are as intended.

Note: If the same output data set is used for a rerun, it will already include successfully copied members.

Source

DFSMSdfp and File and Attribute Management Services.

Routing code

11

Descriptor code

6