HP StorageWorks XP24000/XP20000 for FlashCopy Mirroring Software User Guide Abstract This guide explains how to use HP StorageWorks XP for FlashCopy Mirroring Software to create and use point-in-time copies of data stored by mainframe hosts on HP StorageWorks XP24000/XP20000 storage systems. Topics include installing the license, creating copy pairs using PPRC, TSO, DFSMSdss and ICKDSF command utilities, and restoring source volumes using reverse copy.
© Copyright 2007, 2011 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 About Version 1 Operations........................................................................6 How Version 1 Works...............................................................................................................6 Establishing a Version 1 Relationship..........................................................................................6 Releasing a Version 1 Relationship..............................................................................................
Interoperability With Other Products and Functions.....................................................................53 Using Version 2 with ShadowImage for Mainframe................................................................54 Using Version 2 with TrueCopy for Mainframe.......................................................................55 Using Version 2 with Universal Replicator for Mainframe.........................................................
Viewing Information for a Version 2 Relationship......................................................................127 Viewing Relationship Status of Version 2 Using the TSO Command.........................................127 Viewing Relationship Status of Version 2 Using the ICKDSF Command....................................132 Displaying Information on Version 2 Pairs: FLASHCPY QUERY...............................................133 Displaying Information on Version 2 Pairs: FLASHCPY QUERY RELATIONS...
1 About Version 1 Operations HP StorageWorks XP24000 and XP20000 disk arrays are functionally compatible with Version 1 of the IBM FlashCopy host software function. PPRC TSO commands and/or DFSMSdss commands may be used to perform Version 1 operations on the storage system. See “Performing Version 1 Operations” (page 24) for further information on using PPRC TSO commands and DFSMSdss commands. This chapter provides an overview of Version 1 operations.
Releasing a Version 1 Relationship Normally, a Version 1 relationship will be released automatically when the background copy of the extent data is completed. However, if you specify NOCOPY for the copy mode when you establish a relationship, the relationship will be maintained even when the copying processing completes.
1. 2. Establish a Version 1 relationship by using simplex volumes. When the relationship is established, the volume status changes to F-Copy. After the relationship is established, the on-demand copy operation starts when the S-VOL is updated. The background copy operation will not be performed when the NOCOPY option is specified. For details on the NOCOPY option, see “Parameters for the FCESTABL Command (Version 1)” (page 24). 3.
Table 3 Compatibility of Volumes Shared by Version 1 and Security Solutions Solutions Attribute Version 1 S-VOL Volume Retention Manager T-VOL Protect This attribute can be set. This attribute can be set. Read only This attribute can be set. This attribute can be set. Read/Write This attribute can be set. This attribute can be set. Volume Security Security setting that disables This setting can be made. use as T-VOL This setting can be made.
Figure 2 Possible Combination of Version 1 and ShadowImage for Mainframe Pairs • You cannot add a Version 1 L2 relationship onto a Version 1 L1 relationship. • You cannot add a third layer (L3 pair) onto a Version 1 L2 relationship or a ShadowImage for Mainframe L2 pair. • If the L2 pair is in F-Copy status, you can only suspend or delete the ShadowImage for Mainframe L1 pair.
Table 4 Volume Combinations for Version 1 and ShadowImage for Mainframe (continued) ShadowImage for Mainframe Pair Status V-Split Split Resync Resync-R Suspend ShadowImage for Mainframe Pair Version 1 Relationship S-VOL T-VOL S-VOL Yes No T-VOL No No S-VOL Yes No T-VOL Yes No S-VOL Yes No T-VOL No No S-VOL No No T-VOL No No S-VOL Yes No T-VOL No No NOTE: You cannot specify a ShadowImage for Mainframe S-VOL that already has three T-VOLs as a Version 1 copy source.
Figure 3 Version 1 and TrueCopy for Mainframe: Shared T-VOL and M-VOL/R-VOL (Not Allowed) You cannot create a TrueCopy for Mainframe pair that includes a volume functioning as both a Version 1 T-VOL and a TrueCopy for Mainframe M-VOL. For IBM FlashCopy and PPRC, you can create a PPRC pair that includes a volume functioning as both a FlashCopy T-VOL and a PPRC P-VOL (primary volume), and a PPRC pair that includes a volume functioning as both a FlashCopy T-VOL and a PPRC S-VOL (secondary volume).
Figure 4 Version 1 and Universal Replicator for Mainframe: Shared T-VOL and P-VOL/S-VOL (Not Allowed) You cannot create a Universal Replicator for Mainframe pair that includes a volume functioning as both a Version 1 T-VOL and a Universal Replicator for Mainframe P-VOL. Also, you cannot create a Universal Replicator for Mainframe pair that includes a volume functioning as both a Version 1 T-VOL and a Universal Replicator for Mainframe S-VOL.
2 Preparing for Version 1 Operations This chapter describes the requirements and preparations for performing Version 1 operations. • “Requirements for Version 1” (page 14) • “Calculating the Maximum Number of Version 1 Relationships” (page 14) • “Cautions on Turning Off the Power While Using Version 1” (page 17) • “Installing and Uninstalling Version 1” (page 17) Requirements for Version 1 You can establish a Version 1 relationship for other than simplex volumes.
Table 9 Additional Shared Memory for Differential Tables Additional Shared Memory for Version 1 or Version 2 Number of Differential Number of Pair Tables Number of Volumes in Tables Storage System No additional shared memory for Version 1 0 0 1,024 Additional shared memory for Version 1 is installed 26,176 8,192 16,384 Additional shared memory for Version 2 is installed 57,600 8,192 16,384 Extension 2 104,768 16,384 65,536 Extension 31 146,688 16,384 131,072 Extension 41 209,600 16,3
For information about how to calculate the number of differential tables and pair tables that are required for ShadowImage for Mainframe, see the Hitachi ShadowImage™ for Mainframe User Guide: HP XP24000 Disk Array, HP XP20000 Disk Array. For information about how to calculate the number of differential tables and pair tables that are required for XP Auto LUN, see the HP StorageWorks XP24000/XP20000 Auto LUN Software User Guide.
type 3390-M can only be used, if you use multiple pair tables on the mainframe system. • Conditions for the number of pairs that you can create: Maximum number of relationships that satisfies Maximum number of relationships that satisfies ( ) ◦ . means the total number of differential tables per relationship. ◦ means the number of differential tables available in the storage system. ◦ ( ) means the total number of pair tables per relationship.
When you enter the license key for Compatible FlashCopy, both Version 1 and Version 2 will be installed; therefore you need to disable Version 2. 3. 4. 5. Click Apply in the Remote Web Console window. Set the corresponding devices offline from your host. Set these devices back to online. This ensures that you have the latest device information before performing Version 1 operations. This offline/online operation is required only one time. 6.
3 Using the Version 1 GUI This chapter describes the items displayed in the windows used by Version 1. • “Pair Operation Window” (page 19) • “History Window” (page 22) Pair Operation Window The Pair Operation window displays the volume and pair information for the selected CU image on the connected storage system. An LDEV number that ends with a pound or gate symbol (#) indicates that the LDEV is an external volume (for example, 00:00:01 #).
Table 10 Pair Operation Window Details Item Description Tree Use to select a defined CU image or LDEV ID. When a CU image or LDEV ID is selected, the corresponding volume or relationship is shown in the Volume List of the Pair Operation window. No volume is shown when Subsystem is selected. Volume list Located in the upper-right corner of the Pair Operation window, shows the following: • Message: Displays a message when there is no volume or pair to be displayed.
Table 12 Menu Commands Available for Version 1 Command Description Detail Displays the detailed information for the selected volume. Delete Pair Allows you to release the Version 1 relationship. Information Displays information such as the number of ShadowImage for Mainframe pairs (which includes the Version 1 relationships) or reserved volumes.
Table 13 Commands to Display Dialog Boxes (continued) Item Description Apply Applies the ShadowImage for Mainframe operations displayed in the Preview List to the storage system. If the specified operations complete successfully, the Preview List will be cleared. If an error occurs during an operation, the failed operation will remain in the Preview List with an error icon ( ) displayed to the left of the operation name.
Table 14 History Window Details Item Description Previous To return to the previous page of the list. This button is selectable only when the number of operation histories in the storage system exceeds 16,384, which is the maximum number of histories that can be displayed on one page. The button is grayed out if the total number of operation histories in the storage system is less than 16,384. Next To turn to the next page of the list.
4 Performing Version 1 Operations This chapter describes how to operate Version 1. • “Commands for Version 1 Operations” (page 24) • “Establishing a Version 1 Relationship” (page 24) • “Releasing a Version 1 Relationship Using FCWITHDR” (page 28) • “Viewing the Relationship Status of Version 1 Using FCQUERY” (page 29) Commands for Version 1 Operations Version 1 supports both DFSMSdss commands and PPRC TSO commands to enable you to perform Version 1 operations from zSeries and S/390 host systems.
Table 16 Parameters for the FCESTABL Command (Version 1) (continued) Parameter Value Description MODE COPY Data is copied in the background. Normally, the relationship ends automatically once all of the data has been copied. NOCOPY Data is not copied in the background. It is necessary to issue the FCWITHDR command to delete the relationship specified with the NOCOPY option.
To copy one or more dataset using the FCESTABL command: 1. 2. 3. 4. Check the VTOC list to confirm the VTOC (including INDEX VTOC) and the address (cylinder number and header number) of the datasets that you want to copy. Vary the T-VOL offline. Execute the FCESTABL command. Specify the following items by the EXTENTS parameter. CAUTION: If you access a dataset that is not specified by the EXTENTS parameter, the operation cannot be guaranteed.
Table 17 Parameters for the DFSMSdss Command (Version 1) (continued) Parameter Value Description FCNOCOPY N/A This command sets the copy operation mode to NOCOPY mode. When this command is specified, the background copying process is omitted from the copy operation. FASTREPLICATION PREFERRED The Version 1 copy operation is executed as a priority. If Version 1 cannot be used, Concurrent Copy or the copy operation via the host is executed.
Figure 10 Copying All Datasets Using the COPY FULL Command (Version 1) The following conditions cause the storage system to output the ADR935W message, and end with CC = 4 (copy operation is performed via the host): • The size of the T-VOL is larger than the S-VOL within the same CU image. • The emulation types of the S-VOLs and T-VOLs are different within the same CU image.
Figure 11 FCWITHDR Command FCWITHDR SDEVN(X'DE80') TDEVN(X'DE81') CAUTION: If a relationship is deleted by the FCWITHDR command, the data integrity of the T-VOL cannot be guaranteed. Version 1 does not support the REMOVEFCPY parameter of the ICKDSF CONTROL command. To delete all of the Version 1 relationships established in the storage system, you need to perform this operation using the ShadowImage for Mainframe Pair Operation window.
5 About Version 2 Operations The storage system is functionally compatible with Version 2 of the FlashCopy host software function. PPRC TSO commands, DFSMSdss commands, DFSMSdss commands, ICKDSF commands, and/or ANTRQST Macro commands are used to perform FlashCopy Version 2 operations on the storage system. This chapter provides an overview of Version 2 operations.
To create the multiple relationships from one source is called multiple relationship. Version 2 allows you to establish up to 16 relationships from one extent, as shown in “Multiple Relationships” (page 31). Figure 13 Multiple Relationships The extent that is already set as the copy target cannot be used as a copy source extent to create a new Version 2 relationship. You cannot create a cascaded Version 2 relationship. See “Version 2 Relationship Cannot be Created” (page 32) for an example.
Figure 14 Version 2 Relationship Cannot be Created Copy Modes When you establish a relationship, Version 2 allows you to select COPY mode or NOCOPY mode. When you select COPY mode, Version 2 copies all the data in the S-VOL to the T-VOL. This process is called background copying. Version 2 automatically withdraws the pair when the background copying is complete. Note that when you select NOCOPY mode, the background copying operation will not be performed.
Figure 15 On-demand Copying As shown in “On-demand Copying” (page 33), the on-demand copying process is as follows: 1. 2. 3. From the host, there is a Write request to the space in the S-VOL from which the data is not yet copied, or there is a Read or Write request to the space in the T-VOL to which the data is not yet copied.
On-demand copy may not always be executed when there is a Read request from the host. In that case, the host will directly read the S-VOL data instead of the T-VOL data. CAUTION: When the NOCOPY mode is selected, even if all the data in the S-VOL is copied to the T-VOL by the on-demand copying process, Version 2 does not automatically withdraw the relationship. Therefore, when you select NOCOPY mode, you must first withdraw the pair by using the FCWITHDR command.
Figure 16 Overlap of Copy Source Extents • Version 2 cannot perform dataset copying when: ◦ Any one of the copy target extents is overlapping a copy source or target extent ◦ A copy target extent that already has a relationship established is used to establish a new relationship with a copy source or target extent that overlaps “Compatibility between the Version 2 and User Interface Functions” (page 35) shows the compatibility between the Version 2 functions and the user interface functions.
Table 21 Compatibility between the Version 2 and User Interface Functions (continued) Functions User Interface TSO FlashCopy to PPRC Primary Volume Fast Reverse Restore Remote FlashCopy Remote FlashCopy Preserve Mirror FlashCopy DFSMSdss ICKDSF ANTRQST Macro Multi-relationship Yes Yes Yes Yes NOCOPY mode Yes Yes Yes Yes COPY mode Yes Yes Yes Yes Multi-relationship No No No No NOCOPY mode Yes NO Yes Yes COPY mode Yes Yes Yes Yes Multi-relationship No No No No NOCO
Figure 18 Using a Consistency Group with Version 2: Copying Multiple Data that is Stored over Multiple Volumes “Using a Consistency Group with Version 2: Copying Data that is Stored over Multiple Volumes” (page 36) shows copying data stored over volumes #1 through #3 to volumes #4 through #6. You need to first establish relationships between volumes #1 and #4, #2 and #5, and #3 and #6, and then copy the data.
Figure 19 Incremental FlashCopy As shown in “Incremental FlashCopy” (page 38), Data 2A is managed as a differential data. If you re-execute the command to establish the relationship, only the differential data of Data 2A is copied to the T-VOL.
function. This reversal re-establishes the relationship with the data flowing in the opposite direction.
Figure 20 Performing Reverse Restore after Incremental FlashCopy Function is Used Fast Reverse Restore Function The Fast Reverse Restore function allows you to simplify data recovery in a time of disaster. This recovery function reverses the original S-VOL and T-VOL relationship established by the Version 2 relationships function. This reversal re-establishes the relationship, with the data flowing in the opposite direction.
You can judge whether the Fast Reverse Restore function can be used by examining the results of the FLASHCOPY QUERY RELATIONS command of ICKDSF. For details, see “Displaying Information on Version 2 Pairs: FLASHCPY QUERY” (page 133). When you perform the Fast Reverse Restore function by using the Incremental FlashCopy function, only the updated data is copied from the newly specified S-VOL to T-VOL.
Version 2 pairs after creating TrueCopy for Mainframe pairs. However, Version 2 pairs can be created after creating TrueCopy for Mainframe pairs only when the following options are used: • DFSMSdss : FCTOPPRCPRIMARY • TSO : TGTPPRIM(YES) • ICKDSF : TGTOKASPPRCPRIM(YES) • ANTRQST Macro : TGTPPRIM(YES) For details about using Version 2 with TrueCopy for Mainframe, see “Using Version 2 with TrueCopy for Mainframe” (page 55).
Figure 22 Creating Version 2 Pair in TrueCopy for Mainframe Pair FlashCopy to PPRC Primary Volume Function 43
Figure 23 Creating TrueCopy for Mainframe Pair in Version 2 Pair 44 About Version 2 Operations
Figure 24 Sample of Dataset Copying Comparison of Results of TrueCopy for Mainframe Pair Operations TrueCopy for Mainframe pair operations sometimes produce different results depending on whether differential data of the TrueCopy for Mainframe pair is stored in units of tracks or cylinders. See “Comparison of Results of TrueCopy for Mainframe Pair Operations” (page 45).
Remote FlashCopy Function The Remote FlashCopy function allows you to perform operations on Version 2 relationships on the TrueCopy for Mainframe remote storage system from the host connected to the TrueCopy for Mainframe main storage system. The Remote FlashCopy operation proceeds in the following steps: 1. 2. 3. A FlashCopy operation command is issued to the TrueCopy for Mainframe M-VOL. The command is transmitted from the MCU (Main Control Unit) to the RCU (Remote Control Unit).
Figure 25 Remote FlashCopy Function “Combination of Remote FlashCopy Function and Other FlashCopy Functions” (page 47) describes whether or not Remote FlashCopy functions can be used with other FlashCopy functions.
FlashCopy to Universal Replicator for Mainframe Primary Volume Function The FlashCopy to Universal Replicator for Mainframe Primary Volume function allows you to share Version 2 T-VOLs and Universal Replicator for Mainframe P-VOLs. When you share these volumes, the status of the Universal Replicator for Mainframe pairs must be Duplex, Pending duplex, Suspend, or Suspending.
Figure 26 Copying Version 2 data to remote site with TCz Duplex pairs The following two methods are available to establish a Version 2 relationship when you execute it by using Preserve Mirror FlashCopy function. • REQUIRED: Perform the copying operation only when the Version 2 relationship can be established using the Preserve Mirror FlashCopy function. When the relationship cannot be established, the system command is rejected.
• When using the Preserve Mirror FlashCopy function, HP recommends setting the time of MIH (Missing Interrupt Handler) timer to the setting time of MIH timer (45 seconds) when operating a TCz synchronous pair. • When using the Preserve Mirror FlashCopy function, HP recommends setting the missing interrupt handler (MIH) timer to 45 seconds when operating TCz synchronous pairs.
Figure 27 Copying Version 2 pairs Establish the Version 2 relationships by specifying the following: • M-VOL of TCz#1 in DKC#1 as S-VOL • M-VOL of TCz#2 as T-VOL • R-VOL of TCz#1 in DKC#2 as S-VOL • R-VOL of TCz#2 as T-VOL Then start the copying process (both copies are not synchronized). The state of each TCz pair is retained as Duplex at this time. The data is copied in each Version 2 pair, and the data is not copied in TCz.
Figure 28 Released version 2 pairs Each Version 2 pair is released after the copying process is completed. Table 24 describes whether Preserve Mirror FlashCopy functions can be used with other FlashCopy functions.
If the following operation or processing is executed, the FCWITHDR command may be issued automatically by a host server and relationships may be deleted: • A user deletes a dataset. • A user initializes a volume. • A temporary dataset is deleted when a job completes. Interoperability With Other Products and Functions “Version 2 and Other Copy Solutions Shared Volumes” (page 53) shows whether or not you can share Version 2 volumes with the volumes of other copy solutions.
T-VOL is blocked because of the blockade watch, and the host I/O to the S-VOL can be maintained. • If the host I/O to the T-VOL and the T-VOL data is more important than the host I/O to the S-VOL, use the default setting for the path blockade watch for the external volume that is to be specified as the T-VOL.
You can establish or release a Version 2 relationship if you meet these requirements. When there is a Version 2 relationship, you cannot perform the backward resynchronization (that is, Reverse Resync or Quick Restore) on the ShadowImage for Mainframe pair. Even if the ShadowImage for Mainframe S-VOL already has three T-VOLs, you can create up to 16 pairs by specifying the volumes of Version 2 relationships as the copy source.
Table 28 Version 2 and TrueCopy for Mainframe Shared Volumes Version 2 TrueCopy for Mainframe M-VOL • R-VOL S-VOL Yes Yes T-VOL Yes No Volumes that cannot be shared: The Version 2 and TrueCopy for Mainframe shared configuration is different from the IBM FlashCopy and PPRC shared configuration.
Table 29 Volume Share of a Version 2 S-VOL and TrueCopy for Mainframe Shared TrueCopy for Mainframe Pair Volume Status of TrueCopy for Mainframe Pair Duplex TrueCopy Synchronous for Mainframe M-VOL TrueCopy Asynchronous for Mainframe 1 Yes Pending Duplex Suspend 1 Yes 3 Yes 2 R-VOL Yes No Yes M-VOL Yes Yes1 Yes R-VOL No3 No3 Yes If a TrueCopy for Mainframe M-VOL is in pending status and you execute an ICKDSF command for Version 2, the ICKDSF job will end abnormally with CC=12 error.
1 You can perform Reverse Restore when you specify the following options: • DFSMSdss : FCTOPPRCPRIMARY (You cannot perform Fast Reverse Restore when you specify DFSMSdss.
• Similarly, a Version 2 pair, whose T-VOL is also a TrueCopy Asynchronous for Mainframe, cannot be deleted unless the TrueCopy Asynchronous for Mainframe pair is in the Suspend status. • In addition, the TrueCopy Asynchronous for Mainframe pair cannot be resynchronized during the time a volume is used both as a Version 2 T-VOL and as a TrueCopy Asynchronous for Mainframe M-VOL.
CSUSPEND DEVN(X dev#') PRIM(X ssid' cmd_param X cca X lss) SEC(X ssid' serial# X cca X lss) 3. Set the TrueCopy Asynchronous for Mainframe R-VOL to online. The host will be able to recognize the dataset on the TrueCopy Asynchronous for Mainframe R-VOL and determine the extent for establishing a Version 2 relationship. If the same host is connected to both TrueCopy Asynchronous for Mainframe M-VOL and R-VOL, the R-VOL label must be rewritten. 4. Use DFSMS to establish a Version 2 relationship.
1. 2. If you need to terminate the I/O operation on the volumes of TrueCopy Synchronous for Mainframe pairs to maintain the consistency of data, terminate the I/O operation. Use the ICKDSF command to create a Version 2 pair. See the following example: FLASHCPY ESTABLISH UNIT(X'dev#') TARGETVOL(X'ssid',X'cca',lss) ONLINTGT(YES) If the Version 2 S-VOL and TrueCopy Asynchronous for Mainframe R-VOL are shared: 1. 2.
When you use a Version 2 S-VOL as a Universal Replicator for Mainframe P-VOL and the status of the Universal Replicator for Mainframe pair is suspend, you can perform a Reverse Restore or Fast Reverse Restore. • When you use a Version 2 T-VOL as a Universal Replicator for Mainframe P-VOL When you use a Version 2 T-VOL as a Universal Replicator for Mainframe P-VOL, you can use it regardless of the status of the Universal Replicator for Mainframe pair.
Optimization of Volumes Volumes can be optimized by Version 2 if you use the DEFRAG command of the DFSMSdss utility with the FASTREPLICATION option. See the IBM manual for details about the option. CAUTION: The DEFRAG command may generate an error because the number of relationships per volume exceeds the maximum when all the following conditions are met: • The parity group that includes the volume is overloaded with many accesses. • The DEFRAG command is executed with FASTREPLICATION(REQUIRED).
6 Preparing for Version 2 Operations This chapter describes the requirements and preparations for performing Version 2 operations. • “Requirements for Version 2” (page 64) • “Calculating the Maximum Number of Version 2 Relationships” (page 65) • “Selecting Prior Operations” (page 71) • “Cautions on Turning Off the Power While Using Version 2” (page 72) • “Installing and Uninstalling Version 2” (page 72) Requirements for Version 2 CAUTION: Version 1 and Version 2 cannot be used simultaneously.
Calculating the Maximum Number of Version 2 Relationships Version 2 can establish up to 1,048,575 relationships. However, Version 2 may not be able to establish up to 1,048,575 relationships depending on the number of resources required for the copy operation, which varies according to the attributes (emulation type, capacity size of the data that is copied, position of the extent) of the volumes, and extents used for establishing the relationships.
The number of resources to be used per relationship is the total number of the resources of the copy source and copy target. For example, in the case of a volume with emulation type 3390-3, if the number of cylinders of the divided volume is 3,390 ((X) in the expression that calculates the total number of the resource), the calculation of the total number of the differential table is as follows: Copy source: (3,339 + 6) × 15 Copy target: (3,339 + 6) × 15 (639 × 32) = 2.45379 = 3 (639 × 32) = 2.
Figure 33 Copying Data in Two Extents that Do Not Overlap (Two T-VOLs) Figure 34 Copying Data in Two Extents that Do Not Overlap (Two S-VOLs) Figure 35 Copying Data in Three Extents that Overlap (One T-VOL) Calculating the Maximum Number of Version 2 Relationships 67
Figure 36 Copying Data in Two Extents that Overlap (Two T-VOLs) Figure 37 Copying One Extent to Another in the Same Volume “Referential Examples for Calculating the Number of Resources Required to Create Version 2 Relationships” (page 68) provides calculation examples for the required resources according to the patterns of copying.
Table 40 Referential Examples for Calculating the Number of Resources Required to Create Version 2 Relationships (continued) Emulation Type Copy Patterns Copying Data in Two Extents that do not Overlap (One T-VOL) Copying Data in Two Extents that do not Overlap (Two T-VOLs) See “Copying See “Copying Data in Two Data in Two Extents that Do Extents that Not Overlap Do Not (Two T-VOLs)” Overlap (One (page 67) T-VOL)” (page 66) 3390-93 3390-L4 3390-M5 1 2 3 4 5 Copying Data in Two Extents that do not Ove
Figure 38 Referential Example for Calculating the Number of Relationships As shown in “Referential Example for Calculating the Number of Relationships” (page 70), the total number of resources used per pair is calculated as: Resources used for A − H = (9 + 3) + 3 + 3 + 3 + 3 + 3 + (25 x 3) + 25 + 25 = 152.
In the case of the example shown in “Referential Example for Calculating the Number of Relationships” (page 70), ( ) ( ) is: • 54 26,176 or 57,600, or 104,768. (XP24000 disk array or XP20000 disk array) • 54 146,688, or 209,600. (XP24000 disk array) In addition, Σ(γ) • 10 1,048,575 is: 1,048,575.
processing time of relationships is not always the same, the processing time is not necessarily doubled. If XP Business Copy pairs or Version 1 relationships exist in the same parity group, host I/O responses might not be improved. FCv2 Slower Copy2 Option The FCv2 Slower Copy2 option is used to improve host I/O responses over the background copying processing time of Version 2 relationships.
In some cases, there may be a need to install additional shared memory before installing Version 2. For details, contact your HP service representative. Installing Version 2 This section describes how to install Version 2. The installation steps are different depending on whether Version 1 is installed. Note that you do not need to complete step 2 and step 3 if you do not have Version 1 installed. To install Version 2: 1. Check whether there is a need to install additional shared memory or not.
Uninstalling Version 2 This section describes how to uninstall Version 2. To uninstall Version 2: 1. 2. Withdraw all the Version 2 relationships by using a host command. Check that all the Version 2 relationships are deleted. You can use Remote Web Console or the FCQUERY command to check if all the Version 2 relationships are deleted. For details about the FCQUERY command. 3. 4. 5. 6. Set all the devices to be used with Version 2 to offline.
7 Using the Version 2 GUI Version 2 shares some tabs with ShadowImage for Mainframe. This chapter describes the items on the windows that display when you click the shared tabs and Version 2 original tab. • “Pair Operation Window” (page 75) • “History Window” (page 77) • “Option Window” (page 80) • “FCv2 Window” (page 81) Pair Operation Window The Pair Operation window displays the volume and pair information for the selected CU image on the connected storage system.
Table 42 Pair Operation Window Item Description Tree Use to select a defined CU image or LDEV ID. When a CU image or LDEV ID is selected, the corresponding volume or relationship is shown in the Volume List of the Pair Operation window. No volume is shown when Subsystem is selected. Volume list Located in the upper-right corner of the Pair Operation window, shows the following: • Message: Displays a message when there is no volume or pair to be displayed.
For detailed information about the dialog box displayed by the Detail command in , and for information about the commands that are not in “Menu Commands Available for Version 2” (page 76), see the Hitachi ShadowImage™ for Mainframe User Guide: HP XP24000 Disk Array, HP XP20000 Disk Array. Table 45 Menu Commands Item Description Display Filter To display the dialog box where you can filter the volumes displayed in the Volume List.
An LDEV number that ends with a pound or gate symbol (#) indicates that the LDEV is an external volume (for example, 00:00:01 #). For details about the external volumes, see the HP StorageWorks XP24000/XP20000 External Storage Software User Guide. Figure 41 History Window The upper area of the History window lists the operation history of ShadowImage for Mainframe pairs and Version 1 relationships, and the lower area of the window lists the operation history of Version 2 relationships.
Table 46 History Window (continued) Item Description Code Displays the reference codes of the Version 2 relationship. Message Displays the messages that indicate the conditions of past Version 2 relationships. For details about the messages, see “Version 2 Status and History Reference Codes and Messages” (page 79). Table 47 Version 2 Status and History Reference Codes and Messages Code Message Description 0010 COPY STARTED(FC) The Version 2 background copy operation started.
Table 47 Version 2 Status and History Reference Codes and Messages (continued) Code Message Description 0023 NOCOPY RELATIONSHIP ESTABLISHED(FC) The Version 2 relationship was established in NOCOPY mode. 0029 INITIALIZE ENDED NORMAL(FC) The Version 2 initialization process ended. 0024 COPY ENDED(Relationship maintained) The copying operation of the Version 2 relationship ended and the relationship is still maintained. 002A COPY ENDED ABNORMAL(FC) The Version 2 copy operation ended abnormally.
Figure 42 Option Window Table 48 Option Window Item Description Select option(s) box When you mark the check box of an option name, that option will be enabled. If you clear the check box, that option will be disabled. The only options available for Version 2 are FCv2 Slower Copy1 and FCv2 Slower Copy2. Swap & Freeze and HOST I/O Performance are the options for ShadowImage for Mainframe.
Figure 43 FCv2 Window Table 49 FCv2 Window Item Description Tree When you click Subsystem, the LDKC in the storage system will be displayed. If you click the LDKC in the tree, the CU information in that LDKC will be listed in the CU List on the right. CU List • CU: Displays the CU number (00 FE). • SCP Time(sec.): Displays the state-change-pending time that is set for the CUs, in seconds. This time is the same as the state-change-pending time for TrueCopy for Mainframe.
8 Performing Version 2 Operations This chapter describes how to operate Version 2.
REQUEST=FCQUERY Setting Options The Option window (see “Option Window” (page 81)) allows you to specify the options to expand Version 2 operations. To set options: 1. Display the Option window. If you are already displaying another window, click the Option tab. For information about how to display the Option window directly by starting up Remote Web Console, see the Hitachi ShadowImage™ for Mainframe User Guide: HP XP24000 Disk Array, HP XP20000 Disk Array. 2. 3.
Table 50 Parameters for the FCESTABL Command (Version 2/Volume Copying) (continued) Parameter Value Description MODE COPY Default setting. All the data in the copy range of the volume specified as the source by SDEVN is background-copied to the volume specified as the target by TDEVN. The relationship ends automatically, and all the data is copied. NOCOPY Data is not copied in the background. The relationship does not end automatically, even when all the data is copied.
Table 50 Parameters for the FCESTABL Command (Version 2/Volume Copying) (continued) Parameter Value Description INCREMENTAL YES Establish a relationship including all the tracks in the volume. If you specify YES for this parameter and COPY for the MODE parameter, the relationship will be maintained even after the background copying process is completed, and the differential data between the S-VOL and the T-VOL will be managed. As long as the relationship is maintained, you cannot update the T-VOL.
Table 50 Parameters for the FCESTABL Command (Version 2/Volume Copying) (continued) Parameter Value Description DEVIN TrueCopy for Mainframe source device number Specifies the TrueCopy for Mainframe source device number (device address). Use this parameter when REMOTE is YES. SOURCE Serial number, CU number, LDEV number of the S-VOL Specifies the serial number, the CU number, and the LDEV number of the S-VOL on which you want to perform the FCESTABL command. Use this parameter when REMOTE is YES.
3. Change the VOLSER of the T-VOL. When VTOC is copied, the VOLSER of the S-VOL and the T-VOL will become the same. This step must be performed before setting the volume specified as the T-VOL back to online. 4. Set the T-VOL back to online. This step is not necessary if the ONLINTGT parameter of the FCESTABL command is set to YES. “Example of the FCESTABL Command (Version 2, COPY mode)” (page 88) shows another example of how the FCESTABL command is used.
Table 51 Parameters for the DFSMSdss Command (Version 2/Volume Copying) (continued) Parameter Value Description FCCGFREEZE N/A This option is for temporarily suspending the write operation from the host to the S-VOLs when you establish relationships to maintain the consistency of data. To resume the write operation from the host to the S-VOLs, use the DFSMSdss CGCREATE command or the TSO FCWITHDR command. FCINCREMENTAL N/A To use the Incremental FlashCopy function, use FCINCREMENTAL.
When the COPY FULL command is issued, DFSMSdss checks whether the selected volumes meet the requirements for use as Version 2 volumes, and automatically determines whether to process the requested job via the host. DFSMSdss processes the COPY FULL command in a few seconds and establishes the Version 2 relationship simultaneously as it completes the processing. The completion of this process is not reported to the user.
Figure 49 Copying All Datasets Using the COPY FULL Command (Version 2) If the capacity of the copy source volume is larger than the capacity of the copy target volume, and if REQUIRED is specified for the FASTREPLICATION parameter, the ADR920I message occurs and the COPYcommand will end abnormally. In this case, perform one of the following: • Select the volume which has the same capacity as the copy source volume, and specify it as the copy target volume. • Do not specify the FASTREPLICATION parameter.
Table 52 Parameters for the ICKDSF Command (Version 2/Volume Copying) Command Parameter Value Description FLASHCPY ESTABLISH DDNAME or DNAME JCL statement Specifies the JCL statement identifying the volume. If the OS of the host server is MVS, this parameter or the UNITADDRESS parameter is required. SYSNAME SYSNAME Specifies the SYSNAME in the ASSGN system control statement. If the OS of the host server is VSE, this parameter is required.
Table 52 Parameters for the ICKDSF Command (Version 2/Volume Copying) (continued) Command Parameter Value Description Establishes the relationship which covers the entire volume. The background copying process will not be performed. FLASHCPY ESTABLISH ONLINTGT or ONTGT YES The relationship is established even when the S-VOL is online. NO The relationship is not established when the copy target is online. The default setting of this parameter is NO.
Table 52 Parameters for the ICKDSF Command (Version 2/Volume Copying) (continued) Command Parameter Value Description FASTREVERSERESTORE or FASTREVREST N/A Specify the S-VOL and the T-VOL of the relationship into reverse. • If you specify YES for CHANGERECORDING, only the updated part of the S-VOL or the T-VOL of the established relationship will be copied.
Table 52 Parameters for the ICKDSF Command (Version 2/Volume Copying) (continued) Command Parameter Value Description PRESERVEMIRROR or PRESMIR REQUIRED Establish the relationship using the Preserve Mirror FlashCopy function. If the relationship cannot be established, the command is rejected. TGTOKASPPRCPRIM(YES) must be specified at the same time. PREFERRED Establish the relationship using the Preserve Mirror FlashCopy function.
1. 2. 3. 4. Set the T-VOL to offline. Specify the JCL statement in the DDNAME parameter or specify the S-VOL device number in the UNITADDRESS parameter. Specify the CU number, LDEV number, and device number of the T-VOL for the TARGETVOL parameter. Specify YES for the CHANGERECORDING parameter, and then execute the FLASHCPY ESTABLISH command as shown in “FLASHCPY ESTABLISH Command (Incremental FlashCopy)” (page 96).
Figure 54 FLASHCPY ESTABLISH Command (Reverse Restore) FLASHCPY ESTABLISH UNIT(X'7001') TARGETVOL(X'00',X'00',7000) RESTORE If the S-VOL is updated, before performing Reverse Restore, only the data of the updated part of the S-VOL (differential data) is copied to the T-VOL. When the T-VOL is updated, before performing Reverse Restore, only the data of the updated part of the T-VOL is copied from the S-VOL. 6.
Table 53 ANTRQST Macro Command Parameters (Version 2) Command Parameter Value Description REQUEST=FCESTABLISH SDEVN Source device number Specifies the device number (device address) of the S-VOL on which you want to perform the FCESTABLISH command. TDEVN Target device number Specifies the device number (device address) of the T-VOL on which you want to perform the FCESTABLISH command. INCREMENTAL YES Establishes a relationship including all the tracks in the volume.
Table 53 ANTRQST Macro Command Parameters (Version 2) (continued) Command Parameter Value Description MODE COPY All the data in the copy range of the volume specified as the source by SDEVN is copied in the background to the volume specified as the target by TDEVN. The relationship ends automatically, and the Version 2 pair is deleted when all the data is copied. COPY is the default setting. NOCOPY Data is not copied in the background.
Table 53 ANTRQST Macro Command Parameters (Version 2) (continued) Command Parameter Value Description REQUEST=FCESTABLISH ACTION FREEZE Suspends the write operations from the host to S-VOLs. To resume the write operation, you need to issue the FCWITHDRAW command with the ACTION parameter. However, if a timeout occurs, the write operation may be resumed although you do not issue the FCWITHDRAW command. The default setting of timeout is 120 seconds (2 minutes), but you may change it.
Table 53 ANTRQST Macro Command Parameters (Version 2) (continued) Command Parameter Value Description PRESMIR NO Establish the relationship without using the Preserve Mirror FlashCopy function. If PRESMIR is not specified, NO is set by default. REQ Establish the relationship using the Preserve Mirror FlashCopy function. If the relationship cannot be established, the command is rejected. TGTPPRIM=YES must be specified at the same time.
Table 53 ANTRQST Macro Command Parameters (Version 2) (continued) Command Parameter Value Description REMOTE YES The Remote FlashCopy function is used to establish a relationship. NO You do not use the Remote FlashCopy function. The Remote FlashCopy function is not used to establish a relationship. DEVN TrueCopy for Mainframe source device number Specifies the TrueCopy for Mainframe source device number (device address). Use this parameter when REMOTE is YES.
Table 54 Parameters for the FCESTABL Command (Version 2/Dataset Copying) Parameter Value Description EXTENTS Extents (copy range) Specifies the extent (copy range) by setting the same starting and ending addresses of the source and target with CCHH (cylinder and head numbers). From the copy source, the specified data is copied to the same offset position on the copy target. Up to 32 extents can be specified. When EXTENTS is not specified, the data on all the tracks is copied.
operation processes as shown in “Dataset Copying with the XTNTLTS Parameter Specified (Version 2)” (page 104). Figure 58 Dataset Copying with the XTNTLTS Parameter Specified (Version 2) When you establish a Version 2 dataset relationship per extent for a volume with CATALOG, there will be a write operation from the host on both the VTOC and CATALOG. To perform dataset copying using the FCESTABL command: 1. 2. 3. 4. 5. Using the VTOC list stored in the S-VOL, check the VTOC (INDEX, VTOC, etc.
“FCESTABL Command (Version 2/XTNTLST and NOCOPY Are Specified)” (page 105) shows an example of how the FCESTABL command is used. In this example, the FCESTABL command specifies the following: • The data on the extent starting from CCHH'01000004' and ending at CCHH'0357000A' in the source device numbered 4202 is to be copied to the extent starting from CCHH'13000001' and ending at CCHH'15570007' in the target device numbered 4203.
Table 55 ANTRQST Macro Command Parameters (in Version 2) Command Parameter Value Description REQUEST=FCESTABLISH SRCEXTENTS Copy source extent (copy range) Specifies the copy source extent (copy range) by setting the starting and ending addresses of the source and target with CCHH (cylinder and head numbers). Up to 32 extents can be specified. When SRCEXTENTS is not specified, the data on all the tracks is copied.
Figure 61 FCESTABL Command (Version 2/ACTION Specified) FCESTABL SDEVN(X'4202') TDEVN(X'4203') ACTION(FREEZE) To resume the write operation to the S-VOLs, you need to issue the FCWITHDR command with the ACTION parameter specified. For detailed information about the FCWITHDR command, see “Releasing a Version 2 Relationship Using the TSO Command” (page 108). If a timeout occurs, the write operation may be resumed although you do not issue the FCWITHDR command.
Figure 62 Set SCP Time Dialog Box The following items are displayed in the Set SCP Time dialog box: • SCP Time(sec.) text box specifies the state-change-pending time in seconds (0 to 600 seconds). The text box displays the state-change-pending time that is set to the CU selected in the FCv2 window by default. If multiple CUs are selected and the state-change-pending time that is set to each CU is different, the text box will be blank by default.
Table 57 Parameters for the FCWITHDR Command (Version 2) Parameter Value Description SDEVN Source device number. Specify the number (device address) of the S-VOL on which you want to perform the FCWITHDR command. TDEVN Target device number. Specify the number (device address) of the T-VOL on which you want to perform the FCWITHDR command. DEVN Device number. Specify the number (device address) of the device on which you want to perform the FCWITHDR command with the ACTION parameter.
Table 57 Parameters for the FCWITHDR Command (Version 2) (continued) Parameter Value Description TARGET Serial number, CU number, LDEV number of the T-VOL Specifies the serial number, the CU number, and the LDEV number of the T-VOL on which you want to perform the FCWITHDR command. Use this parameter when TGTUCB is NO. REMOTE YES The Remote FlashCopy function is used to withdraw the relationship. NO The Remote FlashCopy function is not used to withdraw the relationship. NO is the default setting.
Table 58 Results from FCWITHDR Command (continued) Setting Parameter Results Unspecified DDSW parameter set to YES The relationships established with the specified copy target extents on the volume specified by SDEVN are withdrawn. Unspecified Without any relevant relationships to withdraw The command will do nothing and end normally. Unspecified When the existing relationships do not The FCWITHDR command will do fall within the range specified by the nothing and end normally.
Table 59 Combinations of Parameters for the FCWITHDR Command (Version 2) (continued) Combination Parameters SDEVN TDEVN DEVN DDSW XTNTLST Source ACTION Target “Case 5: Specified SDEVN and TDEVN Specified, DDSW = YES” (page 119) Specified or Not specified not specified YES Not specified Not specified Not specified “Case 6: Specified SDEVN and TDEVN Specified, DDSW = YES, XTNTLST Parameter Specified” (page 120) Specified or Not specified not specified YES Specified Not specified NO Not spec
By executing the command described in “Example: FCWITHDR Command Description (for Case 1)” (page 112), the relationship established with the specified target, Dataset 3, in the device numbered 4203, is withdrawn (see “FCWITHDR Command Processing (TDEVN Specified, DDSW = NO) (for Case 1)” (page 113)). However, the relationship established with Dataset 4 is not withdrawn because it is specified as the dataset source.
(page 113), the relationship established with Dataset 3 is withdrawn. There are two relationships before executing the FCWITHDR command; after executing the FCWITHDR command there is only one relationship. Figure 66 FCWITHDR Command Processing (TDEVN Specified, DDSW = NO, XTNTLST Specified) (for Example 2A) “Example 2B: FCWITHDR Command Description (TDEVN Specified, DDSW = NO, XTNTLST Specified)” (page 114) is another example of the command description for Case 2.
4203 is only a part of Dataset 3 as shown in “FCWITHDR Command Processing (TDEVN Specified, DDSW = NO, XTNTLST Specified) (for Example 2B)” (page 115). Figure 68 FCWITHDR Command Processing (TDEVN Specified, DDSW = NO, XTNTLST Specified) (for Example 2B) Case 3: SDEVN and TDEVN Specified, DDSW = NO All the relationships established between the source device specified by SDEVN and the target device specified by TDEVN are withdrawn.
In this case, only the relationships established with Dataset 3 in the device numbered 4203 are relevant. See “FCWITHDR Command Processing (SDEVN and TDEVN Specified, DDSW = NO) (for Case 3)” (page 116). Therefore, by executing the FCWITHDR command described in “FCWITHDR Command Description (SDEVN and TDEVN Specified, DDSW = NO) (for Case 3)” (page 115), the relationship established with Dataset 3 is withdrawn.
“FCWITHDR Command Description (SDEVN and TDEVN Specified, DDSW = NO, XTNTLST Specified) (Example 4A)” (page 117) is an example of the command description for Case 4. This example requests the withdrawal of the relationships established within the copy source extent in the device numbered 4202 and the copy target extent in the device numbered 4203.
within the copy source extent in the device numbered 4202 and the copy target extent in the device numbered 4203.
Figure 75 FCWITHDR Command Description (SDEVN and TDEVN Specified, DDSW = NO, XTNTLST Specified) (Example 4C) FCWITHDR SDEVN(X'4202') TDEVN(X'4203') XTNTLST(X'01000000' X'0100000E' X'21000000' X'2100000E' Case 5: SDEVN and TDEVN Specified, DDSW = YES All the relationships established with the extents in the source or target device specified by SDEVN are withdrawn.
Figure 77 FCWITHDR Command Processing (SDEVN and TDEVN Specified, DDSW = YES) (for Case 5) Case 6: SDEVN and TDEVN Specified, DDSW = YES, XTNTLST Parameter Specified Among the relationships established with the device specified by SDEVN, all the relationships that partly or entirely include the copy target extents specified by the XTNTLST parameter are withdrawn. The information about the specified TDEVN and the copy target extents specified by the XTNTLST parameter are ignored.
Figure 78 FCWITHDR Command Description (SDEVN and TDEVN Specified, DDSW = YES, XTNTLST Specified) (for Case 6) FCWITHDR SDEVN(X'4202') DDSW(YES) XTNTLST(X'010000000' X'1100000E' X'21000000' X'2200000E') FCWITHDR SDEVN(X'4202') TDEVN(X'4203') DDSW(YES) XTNTLST(X'010000000' X'1100000E' X'21000000' X'2200000E') There are three relationships before executing the FCWITHDR command in “FCWITHDR Command Description (SDEVN and TDEVN Specified, DDSW = YES, XTNTLST Specified) (for Case 6)” (page 121), and after execu
Figure 80 FCWITHDR Command Description (DEVN Specified, ACTION = THAW) (for Case 7) FCWITHDR DEVN(X'4202') ACTION(THAW) Because no relationship is withdrawn by performing this command, there will be no change in the number of relationships after using the command. Even if you do not issue this command, the write operation to volumes may be resumed automatically if the state-change-pending time elapses.
Table 60 Parameters for the ICKDSF Command in Version 2 (continued) Command Parameter Value Description MODE COPY Executes the background copying operation on the relationship which has a copy source in the volume specified in the DDNAME, SYSNAME, or UNITADDRESS. If YES is specified for CHANGERECORDING when creating the relationship, the relationship will be maintained after the background copying process is completed.
Table 60 Parameters for the ICKDSF Command in Version 2 (continued) Command Parameter Value Description RESETTGTWRTINHIBIT, RESETTGTWRTINHB, or RTWI — Permits to execute the writing operation on the T-VOL that is write-protected. The relationship will not be deleted. SOURCEVOL or SRCVOL CU number Specifies the CU number, the LDEV number, or the device number of the S-VOL when you use the Remote FlashCopy function.
Command and Applicable Combinations” (page 125) describes the parameters of the FLASHCPY WITHDRAW command and the applicable combinations.
Table 62 Parameters for the ANTRQST Macro Command in Version 2 (continued) Command 126 Performing Version 2 Operations Parameter Value Description ACTION THAW Resumes the write operation from the host to the volumes that belong to the same CU of the device specified by the DEVN parameter. RETINFO Return value Obtains the return code and the reason code of the execution results. For details about the codes, see the IBM manual.
Table 62 Parameters for the ANTRQST Macro Command in Version 2 (continued) Command Parameter TGTUCB Value Description YES Specifies the device number (device address) of the T-VOL on which you want to perform the FCWITHDRAW command. To specify this number, use the TDEVN parameter. YES is the default setting. NO Specifies the DKC device number (LDEV number) of the T-VOL on which you want to perform the FCWITHDRAW command.
Table 63 Parameters for the FCQUERY Command (Version 2) Parameter Value Description DEVN Device number. Specify the number (device address) of the Version 2 volume for which you want to see the status. SHOWRELS NO Displays the relationship information. If the SHOWRELS parameter is not specified, NO is set by default. ALL Displays all of the detailed relationship information. The number of relationships Specifies the number of relationships to display.
Table 64 Information Displayed by the FCQUERY Command (Version 2) (continued) Displayed item Displayed content Definition CU DKC emulation type SERIAL Serial number ACT Number of active Version 2 relationships. See “Calculation Example for the Number of the Pairs Displayed in ACT” (page 130). MAX Maximum number of pairs that can be created with the device specified by DEVN.
Table 64 Information Displayed by the FCQUERY Command (Version 2) (continued) Displayed item Displayed content Definition E N Displays that the volume specified at DEVN is one of the following: • The volume is the source of the relationship, and the target is a normal volume. • The volume is the target of the relationship. Not supported other than “N”. NOTE: If you are not sure if system option mode 20 is ON in your storage system, contact HP technical support.
Figure 86 Display Example of FCQUERY Command with the SHOWRELS parameter FCQUERY DEVN(4202) SHOWREL(ALL) ANTF0421I FCQUERY Relationship 1 DEVN SSID LSS CCA CU SERIAL ACT MAX XC PC CC RV SE SEQNUM 8400 0130 00 00 2107 000000064033 1 1000 N P N N NN 00000000 RELATIONSHIP DETAIL STARTING TRACK: 00000000 DEVICE LONG BUSY FOR CG: NO WRITE INHIBITED: NO --------------------------------------------------PARTNER SOURCE TARGET S F C C P C T S F P LSS CCA SSID START START O V O A R R W E S M --- --- ---- -------- ---
Table 65 Information Displayed by the FCQUERY Command (Version 2) (continued) Displayed item Displayed content Definition CR Y Managing the updated part as differential data if the S-VOL and T-VOL are updated. N Not managing the updated part as differential data even if the S-VOL and T-VOL are updated. Y Writing to the T-VOL is not allowed. N Writing to the T-VOL is allowed. SE N The T-VOL is a normal volume. Not supported other than “N”. FS N The relationship is in the state of normal.
Table 66 Parameters for the ICKDSF Command (in Version 2) Command Parameter Value Description FLASHCPY QUERY DDNAME or DNAME JCL statement Sets the JCL statement identifying the volume. If the OS of the host server is MVS, this parameter or the UNITADDRESS parameter is required. SYSNAME SYSNAME Sets the SYSNAME in the ASSGN system control statement. If the OS of the host server is VSE, this parameter is required.
“FLASHCPY QUERY Command Execution Result” (page 134) shows an example of information displayed as a result of executing the FLASHCPY QUERY command.
Table 67 Information Displayed By the FLASHCPY QUERY Command (continued) Displayed Item Displayed content Meaning PPRCOPY SEC The specified volume is the copy target volume of TrueCopy for Mainframe. CC SRC The specified volume is the copy source volume of the Concurrent Copy. INHIBIT The specified volume cannot be used by Version 2. MAX EXCD The maximum number of relationships that can be created in the specified volume is already created.
Figure 90 FLASHCPY QUERY RELATIONS Command Execution Result “Information Displayed By the FLASHCPY QUERY RELATIONS Command” (page 136) lists the meanings of information displayed as a result of executing the FLASHCPY QUERY RELATIONS command. Table 68 Information Displayed By the FLASHCPY QUERY RELATIONS Command Displayed item Displayed content Meaning FLASHCPY SEQUENCE NUMBER 00000000 Displays the sequence number.
Table 68 Information Displayed By the FLASHCPY QUERY RELATIONS Command (continued) Displayed item Displayed content Meaning BCP T The background copying process is running. F The background copying process is not running. T The updated part is managed as a differential data when the S-VOL and the T-VOL are updated. F The updated part is not managed as a differential data when the S-VOL and the T-VOL are updated. T It is verified whether the displayed information is the latest or not.
Table 68 Information Displayed By the FLASHCPY QUERY RELATIONS Command (continued) Displayed item Displayed content Meaning P The relationship is established by specifying “Preferred” in the Preserve Mirror FlashCopy function. R The relationship is established by specifying “Required” in the Preserve Mirror FlashCopy function. S The relationship is established between two TCz R-VOLs with the Preserve Mirror FlashCopy function.
Viewing Relationship Status of Version 2 Using the ANTRQST Macro Command “Parameters for the ICKDSF Command (in Version 2)” (page 139) shows the parameters you can use with the ANTRQST Macro command. Table 69 Parameters for the ICKDSF Command (in Version 2) Command REQUEST=FCQUERY Parameter Value Description DEVN Device number Specifies the number (device address) of the device on which you want to perform the FCQUERY command. QRYSIZE Data length Specifies the length of data obtained with QRYINFO.
Figure 91 Compatible FlashCopy Information Dialog Box You will need the information in the Compatible FlashCopy Information dialog box when you calculate the number of Version 2 relationships that can be established.
• Remaining differential table(s) displays the remaining number of differential tables in the storage system. In addition to Version 2, XP Business Copy, ShadowImage for Mainframe, XP Snapshot, and XP Auto LUN use differential tables. Therefore, if XP Business Copy, ShadowImage for Mainframe, or XP Snapshot pairs exist, or migration plans are being executed by XP Auto LUN, you can establish fewer relationships than the total number of relationships.
Viewing the Number of Relationships and License Information for Version 2 Using Remote Web Console The Information dialog box displays information such as the number of relationships in the storage system, the number of reserved volumes, and the license capacity. To display the Information dialog box: 1. Right-click anywhere on the volume list in the Pair Operation window of ShadowImage for Mainframe. A pop-up menu will be displayed. 2. Select the Information command in the pop-up menu.
The maximum number of relationships that can be created in one storage system is 1,048,575, including XP Snapshot pairs. Therefore, if XP Snapshot pairs are created in the same storage system, the maximum number of relationships that you can create may be less than 1,048,575 minus the number shown in FCv2 Relationship(s). • Reserved volume(s) The number of reserved volumes of ShadowImage for Mainframe will be displayed in the format XXXX/YYYY.
Figure 93 History Window To display the history: 1. Display the History window. If you are already displaying the other window shown by a ShadowImage for Mainframe tab, click the History tab. For more information about how to display the History window by directly starting up the Remote Web Console computer, see the Hitachi ShadowImage™ for Mainframe User Guide: HP XP24000 Disk Array, HP XP20000 Disk Array.
4. If the information on the list is not updated, click File and then Refresh on the menu bar of the Remote Web Console main window. The list will be updated to the latest information. For operations involving the copying process, the History window does not display information about the operation until the copying process starts. If you perform an operation on a relationship before the process starts, the History window will not display information about the operation. 5.
9 Comparison of Versions 1 and 2 This chapter provides a comparison of FlashCopy Versions 1 and 2. Version 1 and 2 are different regarding the following functions and usage conditions. Because Version 1 and 2 cannot co-exist in the same storage system, choose either one based on the information in the “Differences Between Version 1 and Version 2” (page 146). Table 71 Differences Between Version 1 and Version 2 Compared Item Version 1 Version 2 Shared memory No additional shared memory is required.
Table 71 Differences Between Version 1 and Version 2 (continued) Compared Item Version 1 Version 2 DFSMSdss command The COPY FULL command is used to The COPY FULL command is used to create a Version 1 relationship with create a Version 2 relationship with the the entire volume. entire volume. The COPY DS command is used to create a Version 2 relationship with the specified dataset.
10 Feature Comparison with the IBM Product This chapter describes the differences between IBM FlashCopy and HP Version 2.
Table 74 Differences of Copying Process Between IBM FlashCopy and Version 2 Compared Item IBM FlashCopy Version 2 Read access to an area not specified as the copy range in the copy target during the background copying process in NOCOPY mode The data on the tracks subject to the Sometimes the data on the tracks read operation is not copied from the subject to the read operation is copied copy source to the copy target.
Table 74 Differences of Copying Process Between IBM FlashCopy and Version 2 (continued) Compared Item IBM FlashCopy Version 2 Copying in NOCOPY mode in FlashCopy to Universal Replicator for Mainframe Primary Volume function Not supported When Version 2 pair in NOCOPY mode is created using Universal Replicator for Mainframe pair P-VOL, the copy operation is executed on Version 2 pair T-VOL and Universal Replicator for Mainframe pair S-VOL.
Table 75 Differences of Relationship Releasing Process Between IBM FlashCopy and Version 2 Compared Item IBM FlashCopy FCWITHDR command The command withdraws the copy targets for relationships existing within the extents specified as the source, provided that: (DDSW = YES, XTNTLST parameter specified) Version 2 The command withdraws the copy targets for relationships existing within the entire extents specified as the source.
Table 75 Differences of Relationship Releasing Process Between IBM FlashCopy and Version 2 (continued) Compared Item IBM FlashCopy Version 2 • When you specify the source volume for a volume relationship as the copy target, the entire volume relationship will be withdrawn. • When you specify the target volume for a volume relationship as the copy target, the volume relationship will be withdrawn.
◦ SSID ◦ ACTION (COMMIT/REVERT) Version 2 does not support the following parameters of ICKDSF commands. • • FLASHCPY ESTABLISH command ◦ SOURCEVOL ◦ SETGTOK FLASHCPY QUERY command ◦ • SOURCEVOL FLASHCPY WITHDRAW command ◦ REVERT | COMMIT ◦ SOURCEVOL ◦ RELATSPACE Version 2 does not support the following parameters of DFSMSdss commands. • COPY FULL command ◦ FCSETFTOK Version 2 does not support the following parameters of ANTRQST commands.
11 Troubleshooting This chapter provides troubleshooting information for Compatible FlashCopy and instructions for calling technical support. • “If a Version 2 Relationship is Suspended” (page 154) • “If an ICKDSF Command Ended Abnormally” (page 154) • “SIM Reporting” (page 155) • “Calling HP Technical Support” (page 156) If a Version 2 Relationship is Suspended Version 2 relationships may be suspended if a hardware or software failure occurs during a Version 2 operation.
Table 76 Avoiding Abnormal Ending of the ICKDSF Commands (for Version 2) (continued) Command FLASHCPY QUERY FLASHCPY ESTABLISH Avoiding Method • Execute the FLASHCPY QUERY or the FLASHCPY QUERY RELATIONS command to the T-VOL of Version 2. • When you are going to execute the FLASHCPY QUERY or the FLASHCPY QUERY RELATIONS command on the S-VOL of Version 2, check if a TrueCopy for Mainframe pair or ShadowImage for Mainframe pair is in duplex or suspend status, and then execute the command.
Table 77 SIMs for Version 1 and Version 2 Reference Code SSB22 4B Importance Level Descriptions SSB23 0x Moderate The copying process for Version 1 ends abnormally. The relationship is automatically withdrawn and the T-VOL becomes inaccessible. • x indicates the last digit of the T-VOL's CU number (0x0 to 0xF). • SSB13 indicates the T-VOL's LDEV number.
12 Support and Other Resources Related Documentation • HP StorageWorks XP24000/XP20000 LUN Manager User Guide • HP StorageWorks XP24000/XP20000 Disk Array Owner Guide • HP StorageWorks XP24000/XP20000 Remote Web Console User Guide • HP StorageWorks XP24000/XP20000 External Storage Software User Guide • Hitachi Universal Replicator™ for Mainframe User Guide: HP XP24000 Disk Array, HP XP20000 Disk Array • HP StorageWorks XP24000/XP20000 Business Copy Software User Guide • Hitachi ShadowImage™ for
Before contacting HP, collect the following information: • Product model names and numbers • Technical support registration number (if applicable) • Product serial numbers • Error messages • Operating system type and revision level • Detailed questions Subscription Service HP recommends that you register your product at the Subscriber’s Choice for Business website: http://www.hp.
Glossary C CCHH Cylinder, cylinder, head, head. CTG Consistency group. CU Control unit. CVS Custom volume size. D DASD Direct-access storage device. DFW DASD fast write. DKA Disk adapter. DKC Disk controller. E ECC Error check and correct. ELB Extended long busy. ESCON Enterprise systems connection An optical interface used to connect the mainframe to the control unit; a predecessor to FICON. L LD, LDEV Logical device.
S S-VOL Secondary or remote volume. The copy volume that receives the data from the primary volume. SCP State-change-pending. SI Hitachi ShadowImage. Also known as HP StorageWorks XP Business Copy. SIM Service information message. SIz ShadowImage for Mainframe. SM Shared memory. SVP Service processor. A computer built into a disk array. The SVP, used only by an HP service representative, provides a direct interface to the disk array. T T-VOL Target volume.
Index B N background copying, 32 NOCOPY mode, 32 C O consistency groups, 36 conventions storage capacity values, 157 COPY mode, 32 on-demand copying, 32 R dataset copying, 34 document related documentation, 157 documentation HP website, 157 providing feedback, 158 reference codes Version 1, 23 Version 2, 80 related documentation, 157 relationships Version 2, 30 releasing Version 2 relationships, 108 Remote FlashCopy function, 46 Reverse Restore function, 38 E S extents Version 1, 6 Version 2, 3
