IBM System storage DS6000 Series, Redbook

Page: 94 / 578

70
IBM System Storage DS6000 Series: Copy Services with IBM System z
9.1 FlashCopy interfaces - overview
There are various interfaces that can be used for the configuration and management of
FlashCopy when used in a System z environment with the DS6000.
There are the DS6000 front end-provided interfaces:
򐂰
DS Storage Manager (DS SM) - A graphical user interface (GUI) running in a Web
browser that communicates with the DS6000 Storage Management Console (DS SMC).
򐂰 DS Command Line Interface (DS CLI) - Provides a set of commands that are executed on
a supported workstation communicating with the DS SMC.
򐂰
TotalStorage Productivity Center for Replication (TPC for Replication) - The TPC
Replication Manager server connects to the same network where the DS SMC is.
򐂰 DS Open Application Programming Interface (DS Open API).
Also, with z/OS the following interfaces can be used for FlashCopy management:
򐂰
DFSMSdss utility
򐂰
TSO commands
򐂰
ICKDSF utility
򐂰
ANTRQST application programming interface (API)
This chapter gives an overview of the DS CLI and the DS SM, as well as the z/OS-provided
interfaces. These interfaces are also covered in Part 2, “Interfaces” on page 15.
TotalStorage Productivity Center for Replication (TPC for Replication) provides management
of DS6000 series business continuance solutions, including FlashCopy, Metro Mirror, and
Global Mirror. TPC for Replication is covered in Chapter 31, “IBM TotalStorage Productivity
Center for Replication” on page 467. TPC for Replication includes similar functions to Global
Mirror Utility (GMU). GMU users should consider migrating to TPC for Replication.
Also, the DS Open Application Programming Interface (DS Open API), which is a set of
application programming interfaces that are available to be integrated in programs, can be
used for FlashCopy management and control. The DS Open API is not covered in this book.
For information on the DS Open API, refer to IBM System Storage DS Open Application
Programming Interface Reference, GC35-0516.
FlashCopy control with the interfaces
Independently of the interface that is used, when managing FlashCopy the following basic
sequence takes place:
1. FlashCopy is initiated by means of an interface.
The initialization process of a FlashCopy takes only some seconds. At the end of this
process FlashCopy is established based on the given parameters. This means that all the
necessary meta structures have been established. No data has yet been copied.
2. FlashCopy runs in the background.
This is the moment when FlashCopy copies—in the background—the necessary data to
create the point-in-time copy. The parameters given at initialization time define how
FlashCopy will work in the background. They also define which subsequent activities can
be performed with this FlashCopy.
3. FlashCopy terminates.
FlashCopy either terminates automatically if all tracks have been copied, or needs to be
terminated explicitly, by means of an interface, if it has been defined as persistent.