IBM DS6000 Series manual Data migration based on logical migration, 263

*	PRIMARY....	5005076300C09621	2.4.01.0062	*
*	SECONDARY.1	5005076300C09629		*

********************************************************************

ANTP0001I CQUERY COMMAND COMPLETED FOR DEVICE 6102. COMPLETION CODE: 00

A quick way is to open the data set which received the SYSTSPRT output from TSO in batch and exclude all data. Then an F COMPLETE ALL would only display a single line per volume and you could quickly spot when a volume is not 100% complete. This manual approach might be acceptable for a one-time effort when migrating data in small or medium sized configurations.

Example 13-4 All data is replicated

************** PPRC REMOTE COPY CQUERY - VOLUME ********************

*							(PRIMARY)	(SECONDARY) *
*							SSID CCA LSS SSID CCA LSS*
*DEVICE		LEVEL		STATE		PATH STATUS	SERIAL#	SERIAL#	*
*	------	---------		----------		----------- ---------		---------	*
* 6102		PRIMARY..		PENDING.XD		ACTIVE..	6100 02 01	8100 02 01 *
*		CRIT(NO)			CGRPLB(NO). 000000022665 000000022673*
* PATHS		PFCA	SFCA STATUS: DESCRIPTION						*
*	-----	--------- ------			-------------------				*
*	1	00A4	0020	13	PATH ESTABLISHED		...		*
*		----	----	00	NO PATH				*
*		----	----	00	NO PATH				*
*		----	----	00	NO PATH				*
*						PERCENT OF COPY COMPLETE = 100%			*
*	SUBSYSTEM			WWNN			LIC LEVEL		*
*	-----------		----------------				-----------		*
* PRIMARY....			5005076300C09621				2.4.01.0062		*
* SECONDARY.1			5005076300C09629						*

********************************************************************

ANTP0001I CQUERY COMMAND COMPLETED FOR DEVICE 6102. COMPLETION CODE: 00

Again all these approaches to utilize microcode-based mirroring capabilities require the right hardware as source and target disk servers.

For completeness it is pointed out that Global Mirror is also an option to migrate data from an ESS 750 or ESS 800 to a DS6000. This might apply to certain cases at the receiving site which require consistent data at any time, although Global Copy is used for the actual data movement. Please note that the consistent copy in the new disk server is not concurrent with the primary copy except if the application is stopped and all data is replicated.

Another approach to migrate data beyond the scope of volumes is to use software which migrates data on a logical or data set level and locates the data sets through their respective catalog entries. This approach is outlined in the following section.

13.3 Data migration based on logical migration

Data migration based on logical migration is a data set by data set migration which maintains catalog entries according to the data movement between volumes and, therefore, is not a volume-based migration. This is the cleanest way to migrate data and also allows device conversion from, for example, 3380 to 3390. It also supports transparently multivolume data sets. Logical data migration is a software-only approach and does not rely on certain volume characteristics nor on device geometries.

Chapter 13. Data Migration in zSeries environments 263