Defect 75802

Adding copy sets via the CSM CLI in release 6.2.3 returns syntax error looking for -r1 volume.

CSM 6.2.3 released a new session type called Safeguarded Copy. This session type requires that
an Recovery volume (r1) volume be defined in the copy set. The mkcpset was incorrectly set to
require the -r1 parm on the mkcpset command. Using the mkcpset on any session type other
than Safeguarded Copy, results in a syntax error. This fixpack provides a fix to the issue so that
mkcpset can be used on all session types.

APAR PH04726

Adding copy sets sessions or restarting sessions in a Prepared state, managing DS8000 Global
mirror may cause issues with the ability for the hardware to form consistency groups. To avoid the issue, first suspend the session prior to adding or restarting the session. If the error occurs, please issue the Start command to the session.

In Copy Services Manager version 6.2.3, an issue was introduced when adding copy sets to a
session or restarting a session in Prepared with an active Global Mirror sessions.
The issue may occur where in the process of adding the new relationships or restarting the
session while in Prepared, the Flash Copy relationship to the journal volume is removed and then
reestablished. If the relationship is removed in the middle of the hardware attempting to form a
consistency group, the Global mirror master on the hardware may go into a "fatal" condition and
fail to form additional Consistency Groups.

WORKAROUND:
To avoid this issue, suspend the session prior to adding or removing copy sets.
If the issue occurs, simply reissue the start command to the Session. The "fatal" condition will be
detected and the CSM Session will automatically clean up what's needed and restart Consistency
Group formation. If the condition persists, you may need to issue the "Free Journal Space"
command to the session while in Suspended state, prior to restarting the session.