HP StorageWorks XP24000 for FlashCopy Mirroring Software User's Guide Part number: T5240-96001 First edition: June 2007
Legal and notice information © Copyright 2007 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 About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . Intended Audience . . . . . . . . . . Related Documentation . . . . . . . . Document Conventions . . . . . . . . Conventions for Storage Capacity Values Window Illustrations . . . . . . . . . HP Technical Support . . . . . . . . . Subscription Service . . . . . . . . . HP Websites . . . . . . . . . . . . Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7 About Version 2 Operations . . . . . . . . . . . . . . . . . . . How Version 2 Works . . . . . . . . . . . . . . . . . . Establishing a Version 2 Relationship . . . . . . . . . . . . Copy Modes . . . . . . . . . . . . . . . . . . . . . . Copying by Volume . . . . . . . . . . . . . . . . . . . Copying by Dataset . . . . . . . . . . . . . . . . . . . Using Consistency Groups for Dataset Copies that Span Volumes Releasing Version 2 Relationships . . . . . . . . . . . . .
12 Feature Comparison with the IBM Product . . . . . . . . . . . . . Feature Comparison with the IBM Product . . . . . . Comparison of the Maximum Number of Relationships Comparison of Copying Process . . . . . . . . . . Comparison of Relationship Releasing Process . . . . Comparison of Supporting Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures 1 ..Relationship Status Transition . . . . . . . . . . . . . . . . . . . . . . . . . . 16 2 ..Possible Combination of Version 1 and ShadowImage for Mainframe Pairs . . . . . . . 18 3 ..Version 1 and TrueCopy for Mainframe: Shared T-VOL and M-VOL/R-VOL (Not Allowed) . 20 4 ..Version 1 and Universal Replicator for Mainframe: Shared T-VOL and P-VOL/S-VOL (Not Allowed) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 5 ..Pair Operation Window . . . . . . . . . . . . .
35 ..Example of the COPY FULL Command (Version 2 ) . . . . . . . . . . . . . . . . . 78 36 ..Example of the COPY FULL Command (FCCGFREEZE) . . . . . . . . . . . . . . . . 78 37 ..Example of the CGCREATE Command 78 . . . . . . . . . . . . . . . . . . . . . . 38 ..Copying All Datasets Using the COPY FULL Command (Version 2) . . . . . . . . . . 79 39 ..Dataset Copying with the EXTENTS Parameter Specified (Version 2) . . . . . . . . . . 80 40 ..
65 ..Calculation Example for the Number of the Pairs Displayed in ACT . . . . . . . . . . 98 66 ..Compatible FlashCopy Information Dialog Box . . . . . . . . . . . . . . . . . . . 99 67 ..Information Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 68 ..Typical SIM Showing the Reference Code and SIM Type . . . . . . . . . . . . . . .
Tables 1 ..Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 ..Version 1 Relationship Status Condition . . . . . . . . . . . . . . . . . . . . . . 11 17 3 .. Version 1 and Other Copy Solutions Shared Volumes . . . . . . . . . . . . . . . . 17 4 ..Compatibility of Volumes Shared by Version 1 and Security Solutions . . . . . . . . . 17 5 ..Volume Combinations for Version 1 and ShadowImage for Mainframe . . . . . . . . . 19 6 ..
38 ..Parameters for the FCWITHDR Command (Version 2) . . . . . . . . . . . . . . . . 84 39 ..Combinations of Parameters for the FCWITHDR Command (Version 2) . . . . . . . . . 85 40 ..Parameters for the FCQUERY Command (Version 2) . . . . . . . . . . . . . . . . . 96 41 ..Information Displayed by the FCQUERY Command (Version 2) . . . . . . . . . . . . 97 42 ..Check Boxes in the Compatible FlashCopy V2 Relationships . . . . . . . . . . . . . 100 43 ..Differences Between Version 1 and Version 2 . . .
About this Guide This user's guide describes and provides instructions for performing Compatible FlashCopy operations on the storage system using the Compatible FlashCopy feature option. The term storage system in this guide refers to an HP StorageWorks XP24000 Disk Array. Intended Audience This user’s guide assumes that: • The user has a background in data processing and understands RAID storage systems and their basic functions. • The user is familiar with the storage system and the Remote Web Console.
• • • • • 1 1 1 1 1 KB (kilobyte) = 1,024 bytes MB (megabyte) = 1,0242 bytes GB (gigabyte) = 1,0243 bytes TB (terabyte) = 1,0244 bytes block = 512 bytes Window Illustrations The windows shown in this guide were displayed on a Windows computer with the Internet Explorer browser. The windows may appear different on your computer depending on the operating system and browser being used. Window contents also vary depending on installed program products and the storage system being managed.
1 Overview of Version 1 HP StorageWorks XP24000 for FlashCopy Mirroring Software Version 1 (shortened to Version 1 where applicable hereafter) is functionally compatible with 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” on page 33 for further information on using PPRC TSO commands and DFSMSdss commands.
Overview of Version 1
2 About Version 1 Operations This chapter provides an overview of Version 1 operations. How Version 1 Works Version 1 provides a fast data replication capability. Version 1 allows you to create a copy of an S-VOL on a T-VOL virtually or physically. A volume pair created by Version 1 is called a relationship. Once this relationship is established, the T-VOL (the virtual or physical copy of the S-VOL) is available for both read and write operations.
Simplex 1. Establishing a relationship F-Copy S-VOL T-VOL 2. Background copy F-Copy background copy S-VOL T-VOL 3. Extent data copying is complete. Relationship is withdrawn. Simplex Figure 1 Relationship Status Transition 1. Establish a Version 1 relationship by using simplex volumes. When the relationship is established, the volume status changes to F-Copy. 2. After the relationship is established, the on-demand copy operation starts when the S-VOL is updated.
Table 2 Version 1 Relationship Status Condition Status F-COPY Description S-VOL Access Version 1 is requested with host commands. The S-VOL differential data is copied to the T-VOL in the background. When the NOCOPY option is specified, no background copy is performed. Read/write. T-VOL Access Read/write. Interoperability with Other Products and Functions This section describes the conditions and requirements that you need to know when you use Version 1 and other storage system program products.
side, an MIH may occur on the S-VOL and the processing may end abnormally when the external subsystem is powered off or when failures occur. If the host I/O to the S-VOL is more important than the host I/O to the T-VOL, make sure that the time of path blockade watch that is set for the T-VOL is smaller than the time of the MIH timer set for the S-VOL.
Figure 2 on page 18 illustrates a configuration in which you share ShadowImage for Mainframe T-VOLs and S-VOLs for the Version 1 relationships. In addition to this configuration, you may specify a ShadowImage for Mainframe S-VOL as an S-VOL of a Version 1 relationship. The following table shows the combination of the volumes when you establish a Version 1 relationship with ShadowImage for Mainframe pair volumes.
Table 6 Version 1 and TrueCopy for Mainframe Shared Volumes Version 1 TrueCopy for Mainframe M-VOL R-VOL S-VOL OK OK However, the condition depends on the command types as follows: • For the TSO command There is no additional condition. The R-VOL for TrueCopy for Mainframe can be used as the S-VOL for Version 1 to establish the relationship.
Table 7 Version 1 and Universal Replicator for Mainframe Shared Volumes Version 1 Universal Replicator for Mainframe P-VOL S-VOL S-VOL OK OK T-VOL NO When you are using the DFSMSdss command, a copy via host* will be performed. If the status of the Universal Replicator for Mainframe pair is Suspend, CC=4 is reported to the host. If the status of the Universal Replicator for Mainframe pair is other than Suspend, CC=0 is reported to the host.
Table 8 Version 1 and CC Shared Volumes Version 1 CC P-VOL S-VOL S-VOL OK OK T-VOL NO NO* * Do not share a Version 1 T-VOL and a CC secondary volume. When these two volumes are shared, data will be overwritten and destroyed.
3 Preparing for Version 1 Operations This chapter describes the requirements and preparations for performing Version 1 operations. Requirements for Version 1 You can establish a Version 1 relationship for other than simplex volumes. The following table shows other requirements for using Version 1.
Table 10 Additional Shared Memory for Differential Tables Additional Shared Memory for Version 1 or Version 2 Num. of Differential Tables Num. of Pair Tables Num.
the conditions you need to consider when calculating the number of Version 1 relationships that can be created. Use the following expression to calculate the total number of differential tables per relationship: Total number of the differential tables per relationship = ↑((X) + (Y)) × 15 ÷ (Z)↑ (X): The number of cylinders in the volume. (Y): The number of control cylinders (see Table 28 on page 56). (Z): 20,448 (the number of slots that can be managed by a differential table). ↑: Round up the number.
Installing Version 1 If Version 2 is installed, uninstall Version 2 before installing Version 1. For details about uninstalling Version 2, see “Uninstalling Version 2” on page 65. To install Version 1: 1. 2. 3. 4. 5. 6. Enter the license key for Compatible FlashCopy in the Remote Web Console window. Note: Do not click Apply yet. Perform either of the following so that Version 2 does not work. • Select Compatible FlashCopy V2 and click Uninstall in the Remote Web Console window.
4 Using the Version 1 GUI This chapter describes the items displayed in the windows used by Version 1. Pair Operation Window The Pair Operation window (see Figure 5 on page 27) displays the volume and pair information for the selected CU image on the connected subsystem.
• • • • • A message will be displayed when there is no volume or pair to be displayed. If you see a message in the Volume List, click a different icon in the Tree on the left side of the Pair Operation window. S-VOL The information for the S-VOL is displayed in XX:YY:ZZ (LDKC number:CU number:LDEV ID) format. Note: An LDEV number that ends with a # mark indicates that the LDEV is an external volume (for example, 00:00:01#).
• Relationship(S) The current state of the volume in terms of whether the Version 2 relationship is established or not. For details, see “Pair Operation Window” on page 67. When you select and right-click a volume in the Volume List, the pop-up menu will be displayed. The following table shows the available commands for Version 1. Table 12 Pop-up Menu Commands Available for Version 1 Command Description Detail You can see the detailed information for the selected volume.
• The Apply button 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. For the entire list of ShadowImage for Mainframe error codes, see the HP StorageWorks XP24000 Remote Web Console Error Codes.
• Date: Displays the date and time (YYYY/MM/DD hour/min/sec) when a Version 1 relationship or volume operation has been performed. • S-VOL: Displays the LDKC:CU:LDEV of the S-VOLs used for Version 1 relationship operations in the past. • T-VOL: Displays the LDKC:CU:LDEV of the T-VOLs used for Version 1 relationship operations in the past. • Code: Displays the reference codes for the Version 1 relationship. • Message: Displays the messages that indicate the conditions of past Version 1 relationships.
Using the Version 1 GUI
5 Performing Version 1 Operations This chapter describes how to operate Version 1. Commands for Version 1 Operations Version 1 supports both DFSMSdss commands and TSO PPRC commands to enable you to perform Version 1 operations from zSeries and S/390 host systems. This user’s guide does not provide complete instructions for using commands from the host system. For detailed information on using the DFSMSdss and TSO PPRC commands, see the IBM user documents.
Table 14 Parameters for the FCESTABL Command (Version 1) Parameter Value Description SDEVN Source device number. Specify the number (device address) of the S-VOL on which you want to perform the FCESTABL command. TDEVN Target device number. Specify the number (device address) of the T-VOL on which you want to perform the FCESTABL command. COPY Data is copied in the background. Normally, the relationship ends automatically once all of the data has been copied.
1. Check the VTOC list to confirm the VTOC (including INDEX VTOC) and the address (cylinder number and header number) of the dataset(s) that you want to copy. 2. Vary the T-VOL offline. 3. Execute the FCESTABL command. Note: You must specify the following items for the EXTENTS parameter: WARNING: If you access a dataset that is not specified by the EXTENTS parameter, the operation cannot be guaranteed.
Table 15 Parameters for the DFSMSdss Command (Version 1) Parameter Value Description COPYVOLID N/A The COPYVOLID option is used to copy the volume serial number (VOLSER). If the COPYVOLID option is specified, the volume serial number is copied to the T-VOL, and the T-VOL becomes offline automatically. This COPYVOLID option was necessary for SMS-managed volumes until the DUMPCONDITIONING parameter was added to DFSMSdss with APAR OW 45674.
When the DFSMSdss command is executed, all datasets on the source volume are copied to the T-VOL (see Figure 10 on page 37). A volume area that is not allocated as a dataset is not copied.
FCWITHDR SDEVN(X’DE80’) TDEVN(X’DE81’) Figure 11 Example of the FCWITHDR Command WARNING: If a relationship is deleted by the FCWITHDR command, the data integrity of the T-VOL cannot be guaranteed. Note: Version 1 does not support the REMOVEFCPY parameter of the ICKDSF CONTROL command. To delete all the Version 1 relationships established in the subsystem, you need to perform this operation using the ShadowImage for Mainframe’s Pair Operation window.
6 Overview of Version 2 To enable Compatible FlashCopy Version 2 (shortened to Version 2 where applicable hereafter) to function on the storage system, the Version 2 feature and software must be installed and enabled on the subsystem. For instructions on installing Version 2, see the HP StorageWorks XP24000 Remote Web Console User’s Guide. In some cases, there may be a need to install additional shared memory before installing Version 2. For details, contact your HP service representative.
Overview of Version 2
7 About Version 2 Operations This chapter provides an overview of Version 2 operations. How Version 2 Works Version 2 provides a fast data replication capability. This function allows you to copy the source data to a targeted volume virtually or physically. A pair created by Version 2 is called a relationship. Once a Version 2 relationship is created, hosts can access data that is copied to the targeted volume.
Figure 13 Examples of Multiple Relationships An extent that is already set as the copy target cannot be used as a copy source extent to create a new Version 2 relationship. In other words, you cannot create a cascaded Version 2 relationship. See the figure below for an example.
S-VOL T-VOL Cannot be created T-VOL Legend : Copy source extent : Copy target extent : Copy by Version 2 Figure 14 Example of the Case When a 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.
Legend : Time flow 1. Write request to the space from where the data is not yet copied S-VOL Host 1. Read/Write request to the space to where the data is not yet copied. T-VOL 3. Write operation S-VOL 2. Copy operation (On-demand copy) Host 3. Read or Write operation T-VOL Figure 15 On-demand Copying 1.
you select NOCOPY mode, you must withdraw the pair by using the FCWITHDR command. For details about the FCWITHDR command, see “Releasing a Version 2 Relationship Using FCWITHDR” on page 83. Copying by Volume If you do not specify the extent when you establish a relationship, the whole volume will be copied. This is called volume copying. Note that to perform volume copying, the capacity of the copy source volume must be equal to or larger than the capacity of the copy target volume.
Table 19 Compatibility between the Version 2 and User Interface Functions Functions Volume copy Dataset copy COPY mode NOCOPY mode User Interface TSO DFSMSdss Multi relationship OK OK NOCOPY mode OK OK COPY mode OK OK Multi relationship OK OK NOCOPY mode OK OK COPY mode OK OK Multi relationship OK OK Change to NOCOPY mode No No Multi relationship OK OK Change to COPY mode OK No Using Consistency Groups for Dataset Copies that Span Volumes If you use a consistency group, y
Consistency Group ＃2 ＃1 Reference ＃3 Reference Data 1 Data 2 Data 3 ＃4 ＃5 ＃6 Relationship A Relationship B Relationship C Figure 18 Example of Using a Consistency Group with Version 2: Copying Multiple Data that is Stored over Multiple Volumes Figure 17 on page 46 illustrates an example of copying data stored over volumes #1 through #3 to volumes #4 through #6. You need to establish relationships between volume #1 and #4, #2 and #5, and #3 and #6, and then copy the data.
Table 20 Version 2 and Other Copy Solutions Shared Volumes Conjunction Copy Solution Version 1 N/A ShadowImage for Mainframe TrueCopy for Mainframe Universal Replicator for Mainframe Supported CC Auto LUN N/A The following table shows whether you can or cannot set attributes to the S-VOL or the T-VOL of a Version 2 relationship by using the storage system’s other solutions.
ShadowImage for z/OS Version2 T-VOL Shared S-VOL T-VOL Figure 19 Pair Configuration Where an S-VOL of Version 2 and ShadowImage for Mainframe is Shared Usually, you need to specify a volume in Simplex status as a copy source (S-VOL) or a copy target (T-VOL). When you specify a ShadowImage for Mainframe S-VOL as a copy source, you can establish a Version 2 relationship only if the ShadowImage for Mainframe pair is not in Resync-R status.
Version 2 Relationship SIz S-VOL SIz T-VOL Copy T-VOL Cannot be created Version 2 Relationship S-VOL Copy SIz T-VOL T-VOL Cannot be created Version 2 Relationship S-VOL Copy SIz S-VOL T-VOL Cannot be created Figure 20 Version 2 and ShadowImage for Mainframe: Non-sharable Combinations When you use Version 2, you cannot create pairs sharing the volumes shown in Figure 20 on page 50.
Version 2 Relationship Copy S-VOL T-VOL Cannot be created TCz R-VOL Version 2 Relationship Copy S-VOL T-VOL Cannot be created TCz M-VOL Figure 21 Version 2 and TrueCopy for Mainframe: Non-sharable Combinations Note: 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 primary volume.
TrueCopy Synchronous for Mainframe pair is either Duplex of Pending duplex, the command will be rejected and you cannot establish a Version 2 relationship. • Results of TrueCopy Synchronous for Mainframe operations If a Version 2 relationship is established with the FREEZE option and if a TrueCopy Synchronous for Mainframe R-VOL is in the extended long busy (ELB) status, the command to create or resume a pair will be rejected. However, the command to suspend or delete a pair will be executed normally.
Note: If the same host is connected to both the 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. See the following example: COPY FULL INDYNAM(xxxxxx) OUTDYNAM(yyyyyy) FASTREP(REQ) FCCOPY For details about the DFSMS to establish a Version 2 relationship, see “Establishing Version 2 Relationships by Volumes Using the DFSMSdss Command” on page 77. 5.
Table 25 Version 2 and CC Shared Volumes CC Version 2 P-VOL S-VOL S-VOL OK OK T-VOL NO NO* Note*: Do not share the Version 2 T-VOL with the CC S-VOL. If a T-VOL (S-VOL) is shared by both Version 2 and CC, the data in the T-VOL (S-VOL) will be overwritten by the two programs and will be destroyed.
8 Preparing for Version 2 Operations This chapter describes the requirements and preparations for performing Version 2 operations. Requirements for Version 2 You can establish a Version 2 relationship not only for simplex volumes, but also for ShadowImage for Mainframe S-VOLs or T-VOLs in a status other than simplex. For information about sharing volumes with ShadowImage for Mainframe, see “Using Version 2 with ShadowImage for Mainframe” on page 48.
You can use the Compatible FlashCopy Information dialog box (see Figure 66 on page 99) to check the number of remaining resources that are currently available. Check the Compatible FlashCopy Information dialog box when you create a Version 2 relationship.
• (β) stands for the total number of resources available in the subsystem (β) = 26,176 or 57,600 or 104,768 or 146,688 or 209,600 For details, see Table 10 on page 24. • Establishing relationships by dataset copying To establish relationships between extents, the number of required resources is the same as the number of resources used per relationship, provided that no extents in the same volume overlap.
S-VOL T-VOL S-VOL Figure 24 Copying Data in Two Extents that Do Not Overlap (Two S-VOLs) S-VOL T-VOL Figure 25 Copying Data in Three Extents that Overlap (One T-VOL) T-VOL S-VOL T-VOL Figure 26 Copying Data in Two Extents that Overlap (Two T-VOLs) 58 Preparing for Version 2 Operations
Figure 27 Copying One Extent to Another in the Same Volume Table 29 on page 60 provides calculation examples for the required resources according to the patterns of copying.
Table 29 Examples for Calculating the Number of Resources Required to Create Version 2 Relationships Copy Patterns Required Number of Resources 3380-3, 3390-3 S-VOL T-VOL Total 3390-9 S-VOL T-VOL 3390-L Total S-VOL T-VOL 3390-M Total S-VOL T-VOL Total Copying Data in Two Extents that do not Overlap (One T-VOL) See Figure 22 on page 57. 1 1 2 3 3 6 9 9 18 17 17 34 Copying Data in Two Extents that do not Overlap (Two T-VOLs) See Figure 23 on page 57.
• In the case of emulation type 3390-9, the maximum number of resources that can be used as an S-VOL is 48. • In the case of emulation type 3390-L, the maximum number of resources that can be used as an S-VOL is 144. • In the case of emulation type 3390-M, the maximum number of resources that can be used as an S-VOL is 272.
B A F C Emulation type 3390-3 D E H G Emulation type 3390-L I Legend : Version 2 relationship (allow shows the direction of copy) Figure 28 Example for Calculating the Number of Relationships According to Figure 28 on page 62, the total number of resources used per pair is calculated as: Resources used for A − H = (3 + 1) + 1 + 1 + 1 + 1 + 1 + (9 x 3) + 9 + 9 = 54.
In addition, Σ(γ) ≤ 1,048,575 is: • 10 ≤ 1,048,575. Since the example shown in Figure 28 on page 62 meets the conditions shown above, you can establish all the relationships in Figure 28 on page 62. Selecting Prior Operations You can use the options in Table 30 on page 63 for Version 2 operations.
Notes: • When background copying processing of Version 2 is suppressed by the FCv2 Slower Copy2 option, the time taken for background copying increases. However, since the background copying processing time of relationships is not always the same, note that the background copying processing time will not necessarily quadruple. • If Business Copy pairs or Version 1 relationships exist in the same parity group, host I/O responses might not be improved.
7. Set the devices used by Version 1 back to online. 8. Execute the devserv command with the VALIDATE option of QDASD to the devices in the subsystem. The figure below shows an example of the devserv command. devserv QDASD, 4200, VALIDATE Figure 29 Example of the devserv Command By executing this command, you will be able to view the information for the direct access memory device 4200 and the magnetic disk controller (DASD).
Preparing for Version 2 Operations
9 Using the Version 2 GUI Version 2 shares some tabs with ShadowImage for Mainframe. This chapter describes the items on the windows that will be displayed when you click the shared tabs and Version 2’s original tab. As for other dialog boxes that will be displayed by selecting the pop-up menu commands, see “Performing Version 2 Operations” on page 75.
• The Volume List, located in the upper right on the Pair Operation window, displays the following information: • Message A message will be displayed when there is no volume or pair to be displayed. If you see a message in the Volume List, click a different icon in the Tree on the left side of the Pair Operation window. • S-VOL The information for the S-VOL is displayed in XX:YY:ZZ (LDKC number:CU number:LDEV ID) format.
When you select and right-click a volume in the Volume List, the pop-up menu will be displayed. The following table shows the available commands for Version 2. Table 32 Pop-up Menu Commands Available for Version 2 Command Description Detail You can see the detailed information for the selected volume. Information You can see the information such as number of ShadowImage for Mainframe pairs (which include the Version 1 relationships), number of Version 2 relationships, or reserved volumes.
History Window The History window (see Figure 31 on page 70) displays the past record of pair and relationship operations. For information about how to look up the operation history, see “Viewing Operation History Using Remote Web Console” on page 101. Figure 31 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.
• Message: Displays the messages that indicate the conditions of the past Version 2 relationships. For details about the messages, see Table 33 on page 71. Table 33 Version 2 Status and History Reference Codes and Messages Code Message Description 0010 COPY STARTED(FC) The Version 2 background copy operation started. 0019 INITIALIZE STARTED(FC) The Version 2 initialization process started. 0020 COPY ENDED(FC) The Version 2 background copy operation ended.
Figure 32 Option Window The items displayed in the Option window are as follows: • Select Option(s) box: When you check the check box of the option name, that option will be enabled. If you clear the check box, that option will be disabled. Note that the only options that are available for Version 2 in this box are FCv2 Slower Copy1 and FCv2 Slower Copy2. Swap & Freeze and HOST I/O Performance are the options for ShadowImage for Mainframe.
Figure 33 FCv2 Window The items displayed in the FCv2 window are as follows: • Tree When you click Subsystem, the LDKC in the subsystem will be displayed. If you click an LDKC in the tree, the information for the CUs 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 to the CUs, in seconds.
Using the Version 2 GUI
10 Performing Version 2 Operations This chapter describes how to operate Version 2. Commands for Version 2 Operations Version 2 supports both TSO PPRC commands and DFSMSdss commands to enable you to perform Version 2 operations from zSeries and S/390 host systems. The operating system versions that support Version 2 are OS/390 V2R10 and z/OS V1R0 and higher. An appropriate PTF is necessary for each.
Establishing Version 2 Relationships You need to use the FCESTABL command of PPRC TSO or the DFSMSdss command to establish Version 2 relationships. Note: The timing to copy the data when the relationship is established is different between Version 2 and IBM FlashCopy. IBM FlashCopy copies data when data in either the source or target volume is updated.
FCESTABL SDEVN(X'4202') TDEVN(X'4203') MODE(COPY) ONLINTGT (YES) Figure 34 Example of the FCESTABL Command (Version 2, COPY mode) Establishing Version 2 Relationships by Volumes Using the DFSMSdss Command The DFSMSdss command used to process the Version 2 volume copy operation is COPY FULL. The following table shows the parameters you can use with the DFSMSdss command when you establish Version 2 relationships by volumes.
Note*: For detailed information, see the IBM documents. Note: COPYVOLID and DUMPCONDITIONING cannot be specified at the same time. 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.
Copy by Version 2 Dataset 1 Dataset 1 Dataset 2 Dataset 2 Dataset 3 Dataset 3 S-VOL T-VOL Figure 38 Copying All Datasets Using the COPY FULL Command (Version 2) Note: 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 COPY command will end abnormally.
VTOC address VTOC VTOC address Copy to the same position by Version 2 VTOC Dataset 1 Dataset 2 Dataset 2 Dataset 3 S-VOL T-VOL Figure 39 Dataset Copying with the EXTENTS Parameter Specified (Version 2) When the FCESTABL command with the XTNTLTS parameter specified is executed, only the data on the copy source extent(s) specified by the XTNTLTS parameter is copied to the copy target extent(s) specified by the XTNTLTS parameter.
Note: By using the XTNTLST parameter of the FCESTABL command, you can specify the information on the source and target extents. When there are multiple extents, specify the information on all the extents of the relevant datasets. Version 2 allows you to use the XTNTLST parameter in the following ways: • You may specify multiple copy target datasets to be copied simultaneously from a single copy source dataset.
//DSSCOPY JOB //* //INSTIMG EXEC PGM=ADRDSSU //SYSPRINT DD SYSOUT=* //SYSUDUMP DD SYSOUT=V,OUTLIM=3000 //VOL1 DD UNIT=3390,VOL=SER=FCPY05,DISP=OLD //VOL2 DD UNIT=3390,VOL=SER=FCPY06,DISP=OLD //SYSIN DD * COPY DS(INCL(SAM020.**)) INDDNAME(FCPY05) OUTDDNAME(FCPY06) FASTREPLICATION(REQUIRED) FCNOCOPY DEBUG (FRMSG(DETAILED)) /* Figure 42 Example of the COPY DS Command Version 2 allows you to establish up to 16 relationships simultaneously from a single copy source extent.
4. Select and right-click the CU for which you want to change the state-change-pending time. A pop-up menu is displayed. Note: You may select multiple CUs at a time. If you select multiple CUs, you are to set the same state-change-pending time to all selected CUs. 5. Select the SCP Time Setting command from the pop-up menu. The Set SCP Time dialog box (Figure 44 on page 83) is displayed. 6. Enter the state-change-pending time you want to set. 7. Click OK.
Table 38 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 39 Combinations of Parameters for the FCWITHDR Command (Version 2) Parameters Combination SDEVN TDEVN DEVN DDSW XTNTLST Source Target ACTION Case 1 (section Case 1: TDEVN Specified, DDSW = NO on page 86) Not specified Specified Not specified NO Not specified Not specified Not specified Case 2 (section Case 2: TDEVN Specified, DDSW = NO, XTNTLST Parameter Specified on page 86) Not specified Specified Not specified NO Specified Specified Not specified Case 3 (section Case 3: SDEVN and TDEVN Spe
Case 1: TDEVN Specified, DDSW = NO All the relationships established with the copy target extents existing in the device specified by TDEVN are withdrawn. The relationships established with the copy source extents existing in the specified volume are not withdrawn. Below is an example of the command description for Case 1. This example requests the withdrawal of all the relationships established with the copy target extents existing in the device numbered 4203.
Below is an example of the command description for Case 2. This example requests the withdrawal of all the relationships established with the copy target extents included in the specified extents within the device numbered 4203. FCWITHDR TDEVN(X'4203') XTNTLST(X'00000000' X' 03000000E' X'20000000' X' 2300000E') Figure 47 Example: FCWITHDR Command Description (TDEVN Specified, DDSW = NO, XTNTLST Specified) (Case 2A) In this case, the specified extents in the device numbered 4203 are contained in Dataset 3.
FCWITHDR TDEVN(X'4203') XTNTLST(X'00000000' X' 0000000E' X'20000000' X' 2000000E') Figure 49 Example: FCWITHDR Command Description (TDEVN Specified, DDSW = NO, XTNTLST Specified) (Case 2B) By executing the command described above, the relationship established with the specified target, Dataset 3, is not withdrawn because the specified extent within the device numbered 4203 is only a part of Dataset 3.
Below is an example of the command description for Case 3. This example requests the withdrawal of all the relationships established between the device numbered 4202, which in this case is the source, and the device numbered 4203, which in this case is the target. FCWITHDR SDEVN(X'4202') TDEVN(X'4203') Figure 51 Example: FCWITHDR Command Description (SDEVN and TDEVN Specified, DDSW = NO) (Case 3) In this case, only the relationships established with Dataset 3 in the device numbered 4203 are relevant.
Dataset 3 Dataset 1 Dataset 4 Dataset 2 Dataset 6 ＃4202 ＃4203 Dataset 5 ＃4204 Executing FCWITHDR command Dataset 3 Dataset 1 Dataset 4 Dataset 2 Dataset 6 ＃4202 ＃4203 Dataset 5 ＃4204 Legend : Version 2 relationship Figure 52 Diagram of the FCWITHDR Command Processing (SDEVN and TDEVN Specified, DDSW = NO) (Case 3) Case 4: SDEVN and TDEVN Specified, DDSW = NO, XTNTLST Parameter Specified Among the relationships established between the source device specified by SDEVN and the target device spec
FCWITHDR SDEVN(X'4202') TDEVN(X'4203') XTNTLST(X'00000000' X'0300000E' X'20000000' X'2300000E') Figure 53 Example: FCWITHDR Command Description (SDEVN and TDEVN Specified, DDSW = NO, XTNTLST Specified) (Case 4A) In this case, the specified extent in the device numbered 4202 includes all of Dataset 1. Therefore, by executing the command described above, the relationship established with Dataset 1 is withdrawn.
FCWITHDR SDEVN(X'4202') TDEVN(X'4203') XTNTLST(X'00000000' X'0300000E' X'20000000' X' 2000000E') Figure 55 Example: FCWITHDR Command Description (SDEVN and TDEVN Specified, DDSW = NO, XTNTLST Specified) (Case 4B) By executing the command described above, the relationship established with Dataset 1 is not withdrawn because the specified extent in the device numbered 4202 is included as a part of Dataset 1.
FCWITHDR SDEVN(X'4202') TDEVN(X'4203') XTNTLST(X'01000000' X'0100000E' X'21000000' X'2100000E' Figure 57 Example: FCWITHDR Command Description (SDEVN and TDEVN Specified, DDSW = NO, XTNTLST Specified) (Case 4C) 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.
Dataset 3 Dataset 1 Dataset 4 Dataset 2 Dataset 6 ＃4202 ＃4203 Dataset 5 ＃4204 Executing FCWITHDR command Dataset 3 Dataset 1 Dataset 4 Dataset 2 Dataset 6 ＃4202 ＃4203 Dataset 5 ＃4204 Legend : Version 2 relationship Figure 59 Diagram of the FCWITHDR Command Processing (SDEVN and TDEVN Specified, DDSW = YES) (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
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') Figure 60 Example: FCWITHDR Command Description (SDEVN and TDEVN Specified, DDSW = YES, XTNTLST Specified) (Case 6) There are three relationships before executing the command above, and after executing the command, there is only one relationship.
FCWITHDR DEVN(X'4202') ACTION(THAW) Figure 62 Example: FCWITHDR Command Description (DEVN Specified, ACTION = THAW) (Case 7) Since no relationship is withdrawn by performing the above-mentioned command, there will be no change in the number of relationships after using the command. Note that even if you do not issue this command, the write operation to volumes may be resumed automatically if the state-change-pending time elapses.
ANTF0090IF CQUERY Formatted SERIAL DEVN SSID LSS CCA CU 4202 0102 02 02 2105 000000045029 ACT 1 MAX 1000 XC PC CC RV SEQNUM N N N N 00000000 Figure 64 Example of the FCQUERY Command Execution Result Table 41 Information Displayed by the FCQUERY Command (Version 2) Displayed item Displayed content DEVN Device number recognized by the host SSID Subsystem number LSS CU number CCA Device number CU DKC emulation type SERIAL Serial number ACT Number of active Version 2 relationships.
Dataset Version 2 relationship Dataset VOL#0 Version 2 relationship Dataset Dataset Dataset Dataset VOL#0 VOL#1 Figure 65 Calculation Example for the Number of the Pairs Displayed in ACT ACT shows the total number of the active Version 2 relationships in each extent. Therefore, in the example in Figure 65 on page 98, the total number of active Version 2 relationships in VOL#0 and VOL#1 is two, and 2 is displayed as the content of ACT.
Figure 66 Compatible FlashCopy Information Dialog Box The information in the Compatible FlashCopy Information dialog box will be needed when you calculate the number of Version 2 relationships that can be established.
• The CU drop-down list allows you to select the CU containing the volumes that you want to display in the volume list. Note that only the CUs that are in the LDKC you selected from the LDKC drop-down list will be shown in the CU drop-down list. • The check boxes allow you to select the type and status of the volumes which you want to display in the volume list. The following table shows the features of each check box.
Figure 67 Information Dialog Box The following information will be displayed in the Information dialog box: • ShadowImage for Mainframe pair(s) The number of ShadowImage for Mainframe pairs will be displayed in the format XXXX/YYYY. XXXX indicates the number of ShadowImage for Mainframe pairs, and YYYY indicates the total number of ShadowImage for Mainframe pair tables and Business Copy pair tables. Note: When the volume size is large, ShadowImage for Mainframe uses multiple pair tables per pair.
To see the history: 1. Display the History window. Notes: • If you are already displaying a ShadowImage for Mainframe window, click the History tab. For information about how to display the History window directly by starting up Remote Web Console, see the Hitachi ShadowImage for z/OS User's Guide.
11 Comparison of Versions 1 and 2 Version 1 and 2 are different regarding the following functions and usage conditions. Since Version 1 and 2 cannot co-exist in the same storage system, choose either one based on the information in the table below. Table 43 Differences Between Version 1 and Version 2 Compared Item Version 1 Version 2 Shared memory No additional shared memory is required. Additional shared memory may also be necessary.
Version 1 Version 2 DFSMSdss command The COPY FULL command is used to create a Version 1 relationship with the entire volume. The COPY FULL command is used to create a Version 2 relationship with the entire volume. The COPY DS command is used to create a Version 2 relationship with the specified dataset.
12 Feature Comparison with the IBM Product This chapter describes the differences between IBM FlashCopy and HP’s Version 2. Feature Comparison with the IBM Product The following table shows the differences between the specifications for IBM FlashCopy and HP's Version 2.
Table 45 Differences of the Maximum Number of Relationships Between IBM FlashCopy and Version 2 Compared Item IBM FlashCopy Version 2 Number of multiple relationships Up to 12 relationships can be created per extent (the smallest unit: track). Up to 16 relationships can be created per extent (the smallest unit: track).
Table 47 Differences of Relationship Releasing Process Between IBM FlashCopy and Version 2 Compared Item FCWITHDR command (DDSW = YES, XTNTLST parameter specified) IBM FlashCopy Version 2 The command withdraws the copy targets for relationships existing within the extents specified as the source, provided that: • When the copy target for the relationship is only partly included in the specified extent, only the area that is included in the extent is withdrawn.
IBM FlashCopy Version 2 FCWITHDR command (DDSW = NO, XTNTLST parameter specified) The command withdraws the copy targets for pairs existing within the extents specified as the target, provided that: • When the copy target for the relationship is only partly included in the extent specified as the target, only the area that is included in the extent is withdrawn.
• • • • • • FC • • • • • • QRYDEVC (dvcid) OPENDVCS REMOTE QRYSSID UNFORMAT Withdraw command DEVN (devno) SOURCE (srcid) TARGET (tgtid) OPENDVCS REMOTE SSID XP24000 for FlashCopy Mirroring Software User's Guide 109
Feature Comparison with the IBM Product
13 Troubleshooting 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. If Version 2 relationships are suspended, hosts may be unable to access the copy target datasets. To find whether suspended Version 2 relationships exist within the volumes, use the Pair Operation window (see “Pair Operation Window” on page 67).
Byte 0 1 2 3 4 5 6 SIM SSB 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 00 90 10 00 00 00 8F E0 44 10 00 04 00 80 04 0C 69 00 00 00 00 02 4B 20 05 10 42 C0 F1 00 02 00 SSB13 SSB22, 23 Indicates SIM. RC = 47D080 SIM Type F1: DKC SIM F2: CACHE SIM FE: DEVICE SIM FF: MEDIA SIM Figure 68 Typical SIM Showing the Reference Code and SIM Type SIMs are displayed on the host console by the reference code (RC) and severity.
A Acronyms and Abbreviations Table 49 Acronyms and Abbreviations ACP array control processor CCHH cylinder and head numbers CTG consistency group CU control unit (logical control unit) CVS custom volume size DASD direct-access storage device DFW DASD fast write DKA disk adapter DKC disk controller ECC Error Check and Correct ELB extended long busy ESCON Enterprise System Connection (IBM trademark for optical channels) LAN local-area network LDEV logical device LDKC logical DKC
SM shared memory S-VOL source volume or secondary volume SVP service processor TCz TrueCopy for Mainframe TCAz Continuous Access Asynchronous for Mainframe T-VOL target volume URz Universal Replicator for Mainframe Version 1 Compatible FlashCopy Version 1 Version 2 Compatible FlashCopy Version 2 VM virtual machine VOLSER volume serial number 114 Acronyms and Abbreviations
Index A audience, 11 B background copying, 43 C M MIH, 18, 48 Missing Interrupt Handler, 18 multiple relationship, 41 N NOCOPY mode, 43 consistency group, 46 conventions document, 11 storage capacity values, 11 COPY mode, 43 O D reference code Version 1, 31 Version 2, 71 related documentation, 11 relationship, 41 dataset copying, 45 document conventions, 11 related documentation, 11 documentation HP website, 11 providing feedback, 12 E extent, 15, 41 F F-Copy (status), 17 FCv2 Slower Copy1
W websites HP, 12 HP Subscriber's Choice for Business, 12 product manuals, 11 116
