HP XP24000/XP20000 for FlashCopy Mirroring Software User Guide Abstract This guide explains how to use HP XP for FlashCopy Mirroring Software to create and use point-in-time copies of data stored by mainframe hosts on HP 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..............................................................................................
6 Preparing for Version 2 Operations.............................................................63 Requirements for Version 2.......................................................................................................63 Calculating the Maximum Number of Version 2 Relationships.......................................................64 Selecting Prior Operations.......................................................................................................70 FCv2 Slower Copy1 Option.........
9 Comparison of Versions 1 and 2..............................................................140 10 Feature Comparison with the IBM Product................................................142 Feature Comparison with the IBM Product................................................................................142 Comparison of the Maximum Number of Relationships Between IBM FlashCopy and Version 2.......142 Comparison of Copying Process........................................................................
1 About Version 1 Operations HP 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 (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 (page 24). 3. The relationship will be automatically withdrawn when the background copy operation is completed.
Table 3 Compatibility of Volumes Shared by Version 1 and Security Solutions (continued) Solutions Attribute Version 1 S-VOL Read/Write This attribute can be set. T-VOL 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. HP XP External Storage Software External Volume This setting can be made. 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 Split Resync Resync-R Suspend ShadowImage for Mainframe Pair Version 1 Relationship S-VOL T-VOL 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. • Page 14 • Page 14 • Page 17 • Page 17 Requirements for Version 1 You can establish a Version 1 relationship for other than simplex volumes. (page 14) lists other Version 1 requirements.
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
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 XP24000/XP20000 Auto LUN Software User Guide. See the HP XP24000/XP20000 Snapshot User Guide to calculate the number of differential tables that are required for XP Snapshot.
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. • Page 19 • 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 #). For details about the external volumes, see the HP XP24000/XP20000 External Storage Software User Guide.
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 (continued) Item Description 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. This button is selectable only when the number of operation histories in the storage system exceeds 16,384 volumes, which is the maximum number of histories that can be displayed on one page.
4 Performing Version 1 Operations This chapter describes how to operate Version 1. • Page 24 • Page 24 • Page 28 • Page 28 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. 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 documentation.
Table 16 Parameters for the FCESTABL Command (Version 1) (continued) Parameter Value Description 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.
3. 4. 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. • VTOC address (Cylinder 0, header 0) • VTOC If the desired datasets uses the following items, you must also specify those items by the EXTENTS parameter. • Datasets to be copied To copy multiple datasets, you must specify the extents of all of the desired datasets. 5.
Table 17 Parameters for the DFSMSdss Command (Version 1) (continued) Parameter NOTE: Value Description REQUIRED The copy operation must be executed by using Version 1. If Version 1 cannot be used, an error is reported. NONE The copy operation is not executed by using Version 1. Do not specify both the COPYVOLID option and DUMPCONDITIONING parameter at the same time.
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. When the SSID boundary is 64 LDEV and you establish a relationship between two volumes that have the same CU image but different SSIDs, copy data from S-VOL to T-VOL using the host program.
Figure 12 FCQUERY Command ANTF0090IF DEVN SSID 0A4D 2830 ____ 2830 CQUERY Formatted LSS CCA CU SERIAL 03 0D 2105 0000325476 03 07 2105 0000325476 STATUS FC . . . . . 88% FC . . . . . . . . Table 20 Status Displayed by FCQUERY Command Displayed Status Status of a Relationship or a Volume SIMPLEX The volume is in the simplex status (a status other than CC, XRC, PPRC, or FC). CC The volume is used as a P-VOL of the Concurrent Copy pair.
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 (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 (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 (page 33), the on-demand copying process is as follows: 1. 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. 2. When a request as shown in (page 33) is made to the space in the S-VOL or T-VOL from which or to which the data is not yet copied, Version 2 performs on-demand copying before the Read or Write operation.
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 (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 Fast Reverse Restore Remote FlashCopy Remote FlashCopy Preserve Mirror FlashCopy DFSMSdss ICKDSF ANTRQST Macro 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 NOCOPY mode Yes No Yes Yes COPY mode Yes No Yes Yes Multi-relationship No No No No NOCOPY mode
Figure 18 Using a Consistency Group with Version 2: Copying Multiple 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. However, if volume #1 is updated before the creation of Relationship B (the pair of #2 and #5) is completed, the consistency of the data in the copy target cannot be maintained.
Figure 19 Incremental FlashCopy As shown in (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.
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.
Figure 21 Performing Fast Reverse Restore after the Version 2 Relationship Function is Used FlashCopy to PPRC Primary Volume Function The FlashCopy to PPRC Primary Volume function allows you to share Version 2 T-VOLs and TrueCopy for Mainframe M-VOLs. When you share Version 2 T-VOLs and TrueCopy for Mainframe M-VOLs, the status of the TrueCopy for Mainframe pairs must be Duplex, Pending duplex, or Suspend.
For details about using Version 2 with TrueCopy for Mainframe, see (page 55). • TrueCopy for Mainframe program product is required for using the FlashCopy to PPRC Primary Volume function. • FlashCopy to PPRC Primary Volume function can be used by TrueCopy Synchronous for Mainframe pairs. This function can also be used for TrueCopy Asynchronous for Mainframe pairs whose status is Suspend.
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 (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. A FlashCopy operation command is issued to the TrueCopy for Mainframe M-VOL. 2. The command is transmitted from the MCU (Main Control Unit) to the RCU (Remote Control Unit). 3.
Figure 25 Remote FlashCopy Function (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 two methods available to establish a Version 2 relationship using Preserve Mirror FlashCopy function are: • 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 command is rejected.
• The Version 2 relationship can be established using Preserve Mirror FlashCopy function only when both of the TCz pairs are in Duplex status. If the TCz pairs are not in Duplex status, the operation is different depending on the specified option (PRESMIRREQ or PRESMIRRPREF). • 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.
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 the 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 (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. (page 54) describes whether you can perform Reverse Restore and Fast Reverse Restore on the S-VOL or the T-VOL of a Version 2 pair for which attributes are set by other solutions.
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. In the following cases, you cannot create ShadowImage for Mainframe pairs (see (page 55)): • The S-VOL of the Version 2 relationship and the T-VOL of the ShadowImage for Mainframe pair are shared. • The T-VOL of the Version 2 relationship and the T-VOL of the ShadowImage for Mainframe pair are shared.
• Volumes that cannot be shared: The Version 2 and TrueCopy for Mainframe shared configuration is different from the IBM FlashCopy and PPRC shared configuration. For Version 2 and TrueCopy for Mainframe, you cannot create the following pairs (see (page 56)): ◦ A TrueCopy for Mainframe pair that includes a volume functioning as both a Version 2 T-VOL and a TrueCopy for Mainframe R-VOL.
1 2 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. For information on how to avoid that abnormal ending, see (page 148).
Table 31 Whether Fast Reverse Restore Can be Performed When a Version 2 S-VOL is Used as a TrueCopy for Mainframe Volume (continued) Shared TrueCopy for Mainframe Pair Volume Status of TrueCopy for Mainframe Pair Duplex TrueCopy Asynchronous for Mainframe 1 Pending duplex Suspend M-VOL No No Yes1 R-VOL No No No You can perform Fast Reverse Restore when you specify the following options: • TSO : TGTPPRIM(YES) • ICKDSF : TGTOKASPPRCPRIM(YES) • ANTRQST Macro: TGTPPRIM(YES) • Using a volume both
Table 33 TrueCopy for Mainframe Status that Determines Whether Reverse Restore and Fast Reverse Restore Can be Performed Shared TrueCopy for Mainframe Pair Volume Status of TrueCopy for Mainframe Pair Duplex Pending duplex Suspend TrueCopy Synchronous for Mainframe M-VOL Yes Yes Yes TrueCopy Asynchronous for Mainframe N/A N/A Yes M-VOL Unlike using IBM FlashCopy Version 2 and PPRC together, you need a DFSMS command, a TSO command, or an ICKDSF command when you use a DFSMS command, a TSO command
5. 6. If step 4 completes successfully, set the TrueCopy Asynchronous for Mainframe R-VOL to offline. Resynchronize the TrueCopy Asynchronous for Mainframe pair. If the Version 2 T-VOL and TrueCopy Synchronous for Mainframe M-VOL are shared: 1. To maintain the consistency of data, terminate the I/O operation to the volumes of TrueCopy Synchronous for Mainframe pairs. The TrueCopy for Mainframe pair status is Duplex. 2. Use DFSMS to establish a Version 2 relationship.
If the Version 2 T-VOL and TrueCopy Synchronous for Mainframe M-VOL are shared: 1. To maintain the consistency of data, terminate the I/O operation to the volumes of TrueCopy Synchronous for Mainframe pairs. The TrueCopy for Mainframe pair status is Duplex. 2. Use the ICKDSF command to establish a Version 2 relationship.
Table 36 Whether Reverse Restore and Fast Reverse Restore Can be Performed When a Version 2 Volume is Used as a Concurrent Copy/Compatible XRC Volume Version 2 Concurrent Copy/Compatible XRC P-VOL S-VOL S-VOL No No1 T-VOL N/A N/A 1 Do not execute Reverse Restore and Fast Reverse Restore when an S-VOL is shared by Version 2 and Concurrent Copy or Compatible XRC.
6 Preparing for Version 2 Operations This chapter describes the requirements and preparations for performing Version 2 operations. • Page 63 • Page 64 • Page 70 • Page 71 • Page 71 Requirements for Version 2 CAUTION: Version 1 and Version 2 cannot be used simultaneously. If one or more Version 1 relationships exist in the storage system, you cannot establish any Version 2 relationships until you withdraw all existing Version 1 relationships.
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.
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.45379 = 3 When you round up 0.81836 to the nearest whole number, it becomes 1. Therefore, the total number of resources to be used for one relationship is 6 when the emulation type is 3390-3.
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) 66 Preparing for Version 2 Operations
Figure 36 Copying Data in Two Extents that Overlap (Two T-VOLs) Figure 37 Copying One Extent to Another in the Same Volume (page 67) 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 (page 66) See (page 65) 3390-M5 1 2 Copying Data in Two Extents that do not Overlap (Two S-VOLs) Copying Data in Three Extents that Overlap (One T-VOL) Copying Data in Two Extents that Overlap (Two T-VOLs) See (page 66) Se
Figure 38 Referential Example for Calculating the Number of Relationships As shown in (page 69), 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 (page 69), ( ) ( ) 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. Because the example shown in (page 69) meets the conditions, you can establish all the relationships in (page 69). Selecting Prior Operations You can use the options in (page 70) for Version 2 operations.
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. When the FCv2 Slower Copy2 option is in effect, the number of Version 2 relationships that can be copied simultaneously in the background will be suppressed to one-quarter, and consequently host I/O responses improve.
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. For details, contact your HP service representative. 2. Withdraw all the relationships to delete Version 1 relationships.
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. Select Compatible FlashCopy V2 and click Uninstall in the Remote Web Console window. Click Apply in the Remote Web Console window.
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. • Page 74 • Page 76 • Page 79 • Page 80 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 (page 75), 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. For details, see the Hitachi ShadowImage™ for Mainframe User Guide: HP XP24000 Disk Array, HP XP20000 Disk Array.
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. For details about the operation history of Version 1 relationships, see (page 22). For details about the operation history of ShadowImage for Mainframe pairs, see the Hitachi ShadowImage™ for Mainframe User Guide: HP XP24000 Disk Array, HP XP20000 Disk Array.
Table 47 Version 2 Status and History Reference Codes and Messages 78 Code Message Description 0010 COPY STARTED(FC) The Version 2 background copy operation started. Note that this message will be displayed when the relationship is established, not when the copy operation starts. 0011 1st INCREMENTAL COPY STARTED The initial copy operation of the Version 2 relationship established by the Incremental FlashCopy function has started.
Table 47 Version 2 Status and History Reference Codes and Messages (continued) Code Message Description 002A COPY ENDED ABNORMAL(FC) The Version 2 copy operation ended abnormally. 002F INITIALIZE ENDED ABNORMAL(FC) The Version 2 initialization process ended abnormally. 0030 COPY STARTED AFTER MODE CHANGED(FC) The Version 2 background copy operation started after the Version 2 relationship changed to copy mode.
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. • Page 82 • Page 83 • Page 83 • Page 105 • Page 122 Commands for Version 2 Operations Version 2 supports the PPRC TSO, DFSMSdss, ICKDSF, and ANTRQST Macro 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 V1.1 and higher.
Setting Options The Option window (see (page 80)) 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. Select the check box of the option you want to set. Click Apply.
Table 50 Parameters for the FCESTABL Command (Version 2/Volume Copying) (continued) Parameter Value Description use the FCWITHDR command. In the following data, access occurs.
Table 50 Parameters for the FCESTABL Command (Version 2/Volume Copying) (continued) Parameter Value Description NO is the default setting. TGTUCB YES Specifies the device number (device address) of the T-VOL on which you want to perform the FCESTABL command. To specify this number, use the TDEVN parameter. YES is the default setting. TARGET NO Specifies the serial number, the CU number, and the LDEV number of the T-VOL on which you want to perform the FCESTABL command.
Table 50 Parameters for the FCESTABL Command (Version 2/Volume Copying) (continued) Parameter Value Description REQUIRED or REQ Establish the relationship using the Preserve Mirror FlashCopy function. If the relationship cannot be established with the Preserve Mirror FlashCopy function, the command is rejected. TGTPPRIM(YES) must be specified at the same time. PREFERRED or PREF Establish the relationship using the Preserve Mirror FlashCopy function.
Table 51 Parameters for the DFSMSdss Command (Version 2/Volume Copying) (continued) Parameter Value Description to the backup tape or disk. In this case, it is not necessary to specify COPYVOLID to copy the volume label. DUMPCONDITIONING1 N/A DUMPCONDITIONING is used when you want to specify that the purpose of the copy operation is to create a backup copy and not for using the copied volume for application. FCNOCOPY N/A This command sets the copy operation mode to NOCOPY mode.
Table 51 Parameters for the DFSMSdss Command (Version 2/Volume Copying) (continued) Parameter Value Description REVERSE The copy operation will be executed only when you specify the S-VOL and the T-VOL in the opposite way as when the relationship was created. DEBUG FRMSG3 By specifying this option, you will be able to receive information describing the error and its causes in case Version 2 copy operation fails. You can also specify the amount of error information you want to receive.
Figure 46 COPY FULL Command (FCCGFREEZE) //SYSPRINT DD SYSOUT=* //VOL1 DD UNIT=3390,VOL=SER=FCV200,DISP=OLD //VOL2 DD UNIT=3390,VOL=SER=FCV201,DISP=OLD //SYSIN DD* COPY FULL INDDNAME(VOL1) OUTDDNAME(VOL2) FASTREP(REQ) FCCGFREEZE Figure 47 CGCREATE Command //SYSPRINT DD SYSOUT=* //SYSIN DD* CGCREATE ACCESSVOLUME(FCV200) FCCGVERIFY(FCV200) Figure 48 COPY FULL Command (FCINCREMENTAL) //SYSPRINT DD SYSOUT=* //VOL1 DD UNIT=3390,VOL=SER=FCV200,DISP=OLD //VOL2 DD UNIT=3390,VOL=SER=FCV201,DISP=OLD //SYSIN DD * CO
Establishing Version 2 Relationships by Volumes Using the ICKDSF Command (page 90) lists the parameters you can use with the ICKDSF command when you establish Version 2 relationships by volumes. 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.
Table 52 Parameters for the ICKDSF Command (Version 2/Volume Copying) (continued) Command FLASHCPY ESTABLISH Parameter ONLINTGT or ONTGT Value Description NOCOPY Establishes the relationship which covers the entire volume. The background copying process will not be performed. 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 completed. If you specify NO, or nothing, for CHANGERECORDING, the relationship will be withdrawn after the copying operation is completed. TGTCANCOMEONLINE or TGTONLINE YES The T-VOL can be set to online after the relationship is established. The default setting of this parameter is YES. TGTOKASPPRCPRIM NO The T-VOL cannot be set to online until the relationship is deleted.
Table 52 Parameters for the ICKDSF Command (Version 2/Volume Copying) (continued) Command Parameter Value Description TGTOKASPPRCPRIM(YES) must be specified at the same time. NO Establish the relationship without using the Preserve Mirror FlashCopy function. If PRESERVEMIRROR is not specified, NO is set by default. To create a Version 2 pair by using the ICKDSF FLASHCPY ESTABLISH command: 1. Set the T-VOL to offline.
When the S-VOL is updated, only the data of the updated part of the S-VOL (differential data) will be copied to the T-VOL. When the T-VOL is updated, only the data of the updated part of the T-VOL will be copied to the S-VOL. 6. Set the CHANGERECORDING parameter to YES to maintain the relationship after the copying process is completed and to manage the differential data between the S-VOL and the T-VOL.
Figure 55 FLASHCPY ESTABLISH Command (Incremental FlashCopy) FLASHCPY ESTABLISH UNIT(X'7000') TARGETVOL(X'00',X'01',7001) CHANGERECORDING(YES) The Version 2 pair will be created. 5. Execute the FLASHCPY ESTABLISH command, specifying the FASTREVREST parameter and reversing the S-VOL and the T-VOL. See (page 95).
Table 53 ANTRQST Macro Command Parameters (Version 2) (continued) Command Parameter Value Description NO The relationship will be deleted after the background copying process is completed. NO is the default setting. TGTPPRIM YES Specify this parameter to use the Version 2 T-VOL as the TrueCopy for Mainframe M-VOL (or the Universal Replicator for Mainframe P-VOL). NO Specify this parameter not to use the Version 2 T-VOL as the TrueCopy for Mainframe M-VOL. NO is the default setting.
Table 53 ANTRQST Macro Command Parameters (Version 2) (continued) Command Parameter Value Description target of the specified area (within the extent). ONLINTGT NO2CPY The relationship is made by NOCOPY mode and is copied in the background. When all the data is copied, the relationship is released automatically. YES The path group is not checked. The relationship is established even when the copy target is online. NO The path group is checked.
Table 53 ANTRQST Macro Command Parameters (Version 2) (continued) Command Parameter Value Description number, use the TDEVN parameter. YES is the default setting. PRESMIR NO Specifies the serial number, the CU number, and the LDEV number of the T-VOL on which you want to perform the FCESTABLISH command. To specify this number, use the TGTSERIAL, TGTLSS, TGTDVC parameters instead of TDEVN. NO Establish the relationship without using the Preserve Mirror FlashCopy function.
Table 53 ANTRQST Macro Command Parameters (Version 2) (continued) Command Parameter Value Description Use this parameter when the TGTUCB parameter is NO or the REMOTE parameter is YES. TGTDVC T-VOL LDEV number Specifies the LDEV number of the T-VOL on which you want to perform the FCESTABLISH command. Use this parameter when the TGTUCB parameter is NO, or the REMOTE parameter is YES. REMOTE YES The Remote FlashCopy function is used to establish a relationship.
Establishing Version 2 Relationships by Extents Using the TSO Command When you establish Version 2 relationships by extents with the FCESTABL command, the following parameters are available in addition to the parameters defined in (page 83).
When the FCESTABL command with the XTNTLTS parameter specified is executed, only the data on the copy source extents specified by the XTNTLTS parameter is copied to the copy target extents specified by the XTNTLTS parameter. For example, when you copy only dataset 2, the copy operation processes as shown in (page 101).
6. • Specify source and target datasets that differ in position. • Specify the source and target datasets that are in the same volume, provided that they do not overlap. If the T-VOL is set to offline in step 4, set this volume back to online. This step is not necessary if the ONLINTGT parameter of the FCESTABL command is set to YES. The FCESTABL command can only be executed once per Version 2 relationship. You cannot execute this command repeatedly for the same Version 2 relationship.
Establishing Version 2 Relationships by Extents Using the ANTRQST Macro Command When you establish Version 2 relationships by extents with the ANTRQST Macro command, the parameters in (page 103) are available.
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 (page 105). If a timeout occurs, the write operation may be resumed although you do not issue the FCWITHDR command. The default setting for the timeout is 120 seconds (2 minutes); however, you may change it.
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 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 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. XTNTLST parameter There are several effective combination patterns of the parameters of the FCWITHDR command.
Figure 63 Example: FCWITHDR Command Description (for Case 1) FCWITHDR TDEVN(X'4203') By executing the command described in (page 109), the relationship established with the specified target, Dataset 3, in the device numbered 4203, is withdrawn (see (page 109)). However, the relationship established with Dataset 4 is not withdrawn because it is specified as the dataset source. There are two relationships before executing the command, and only one relationship after the command is executed.
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) (page 110) is another example of the command description for Case 2.
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. (page 111) is an example of the command for Case 3.
4202, Dataset 6 is not withdrawn. In short, there are three relationships before executing the FCWITHDR command shown in (page 111), and after executing the command, there are only two relationships.
Figure 71 FCWITHDR Command Description (SDEVN and TDEVN Specified, DDSW = NO, XTNTLST Specified) (Example 4A) FCWITHDR SDEVN(X'4202') TDEVN(X'4203') XTNTLST(X'00000000' X'0300000E' X'20000000' X'2300000E') In this case, the specified extent in the device numbered 4202 includes all of Dataset 1. See (page 113). Therefore, by executing the FCWITHDR command described in (page 113), the relationship established with Dataset 1 is withdrawn.
By executing the FCWITHDR command described in (page 113), 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. See (page 114).
If the device specified by SDEVN is the source and if the relationships are set to the NOCOPY mode, the relationships are withdrawn after the copy operation mode is changed to COPY mode and then the background copy process is completed. If the device specified by SDEVN is the target, the relationships are withdrawn immediately.
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 79 FCWITHDR Command Processing (SDEVN and TDEVN Specified, DDSW = YES, XTNTLST Specified) (for Case 6) Case 7: DEVN Specified, ACTION = THAW Resume the write operation to the volumes that belong to the CU specified by the DEVN parameter. Relationships (pairs) will not be withdrawn. (page 117) shows the instruction to resume the write operation to the volumes that belong to the CU whose device number is 4202.
Table 60 Parameters for the ICKDSF Command in Version 2 118 Command Parameter Value Description FLASHCPY WITHDRAW 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 60 Parameters for the ICKDSF Command in Version 2 (continued) Command Parameter Value Description ALL Executes the background copying operation on all the relationships that have copy sources in the volume specified in DDNAME, SYSNAME, or UNITADDRESS. If YES is specified for the CHANGERECORDING when creating the relationship, the relationship will be maintained even after the background copying process completes.
1. 2. 3. 4. 5. If the OS of the host server is MVS, specify the JCL statement in the DDNAME parameter, or specify the S-VOL device number of the Version 2 pair that you want to delete for the UNITADDRESS parameter. Specify SYSNAME of the ASSGN system control statement in the SYSNAME parameter if the OS of the host server is VSE. Specify the CU number, LDEV number, and device number of the T-VOL in the TARGETVOL parameter. See (page 135) and specify any other necessary parameters.
Table 62 Parameters for the ANTRQST Macro Command in Version 2 Command REQUEST=FCWITHDRAW Parameter Value Description SDEVN Source device number Specifies the device number (device address) of the S-VOL on which you want to perform the FCWITHDRAW command. TDEVN Target device number Specifies the device number (device address) of the T-VOL on which you want to perform the FCWITHDRAW command.
Table 62 Parameters for the ANTRQST Macro Command in Version 2 (continued) Command Parameter Value Description specified, the relationships on all tracks are withdrawn. TGTUCB 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) (continued) Parameter Value Description ALL Displays all of the detailed relationship information. The number of relationships Specifies the number of relationships to display. Displays the specified number of detailed relationship information. STARTADDR CCHH number Specifies the CCHH number of the starting address. Use this parameter when the number of relationships is specified in the SHOWRELS parameter.
Table 64 Information Displayed by the FCQUERY Command (Version 2) (continued) Displayed item Displayed content Definition • M-VOL of the TrueCopy Asynchronous for Mainframe pair (Timer Type is SYSTEM or NONE, and the pair status is Duplex or Pending Duplex) • P-VOL of the Universal Replicator for Mainframe pair (Timer Type is SYSTEM or NONE, and the pair status is Duplex or Pending Duplex) PC N Volume specified by DEVN is not in the status described above, or the volume is not used.
1 In case the volume is set online in more than one LPAR defined by the mainframe system host. Figure 84 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 (page 125), 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.
Table 65 Information Displayed by the FCQUERY Command (Version 2) Displayed item Displayed content RELATIONSHIP DETAIL STARTING TRACK CCHH number of the starting address. The CCHH number specified here is displayed if the STARTDDR parameter is specified. “00000000” is displayed if the STARTDDR parameter is not specified. DEVICE LONG BUSY FOR CG Y The consistency of the extent is maintained. N The consistency of the extent is not maintained. Y Writing is not allowed. N Writing is allowed.
Table 65 Information Displayed by the FCQUERY Command (Version 2) (continued) Displayed item Displayed content Definition PM N The relationship is established without using the Preserve Mirror FlashCopy function. 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.
Table 66 Parameters for the ICKDSF Command (in Version 2) (continued) Command Parameter Value Description OS of the host server is MVS, this parameter or the UNITADDRESS parameter is required. SYSNAME SYSNAME UNITADDRESS, UNITADDR, Source device number or UNIT Sets the SYSNAME in the ASSGN system control statement. If the OS of the host server is VSE, this parameter is required. Specifies the device number (device address) of the S-VOL on which you want to perform the FLASHCPY QUERY command.
Table 67 Information Displayed By the FLASHCPY QUERY Command Displayed Item Displayed content Meaning EXISTING RELATIONS Number of relationships Displays the number of relationships in the specified volumes. MAXIMUM ALLOWED RELATIONS Number of relationships Displays the maximum number of relationships that can be created in the specified volumes.
(page 130) shows an example of information displayed as a result of executing the FLASHCPY QUERY RELATIONS command. Figure 90 FLASHCPY QUERY RELATIONS Command Execution Result (page 130) 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 U The relationship is in the status that cannot identify the type of Preserve Mirror FlashCopy function (Preferred or Required), because the M-VOL and R-VOL of TCz are mixed. START OF EXTENT(SOURCE) CCHH number Displays the starting CCHH of the extent of the copy source. START OF EXTENT(TARGET) CCHH number Displays the starting CCHH of the extent of the copy target.
Table 69 Parameters for the ICKDSF Command (in Version 2) (continued) Command Parameter Value Description which you want to perform the FCQUERY command. QRYSIZE Data length Specifies the length of data obtained with QRYINFO. FORMAT FQMAP Obtains QUERY information with the format using the ANTFQMAP macro. For details about the format, see the IBM manual. NO Obtains QUERY information with the format not using the ANTFQMAP macro command. NO is the default setting.
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.
relationship before the process starts, the History window will not display information about the operation. 5. If there are many records of operations, click the scroll button. The list will scroll and you will be able to see the operation history that has not been displayed. If you click and drag up the frame border that divides the History window into upper and lower panes, you can expand the area of the list display. 6.
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 (page 140). Table 71 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.
Table 71 Differences Between Version 1 and Version 2 (continued) Compared Item Version 1 Version 2 The COPY DS command is used to create a Version 2 relationship with the specified dataset. When the DFSMSdss command is If the copy operation is required for issued again during background copy the Version 1 volume during the copying process, the normal copy operation operation will be performed via the host.
10 Feature Comparison with the IBM Product This chapter describes the differences between IBM FlashCopy and HP Version 2. • Page 142 • Page 142 • Page 142 • Page 144 • Page 146 Feature Comparison with the IBM Product (page 142) shows the differences between IBM FlashCopy and HP Version 2. Table 72 Differences Between IBM FlashCopy and Version 2 Compared Item IBM FlashCopy HP Version 2 GLOBAL Mirror status Supported. Not supported. For details about GLOBAL Mirror status, see the IBM manual.
Table 74 Differences of Copying Process Between IBM FlashCopy and Version 2 (continued) Compared Item IBM FlashCopy Version 2 and other times the data is not copied to the target. Status of the pairs when on-demand copy is processed Relationships are withdrawn automatically when all the copy operations processed by an On-demand copy are completed. Relationships are maintained even when all the copy operations processed by an On-demand copy are completed.
Table 74 Differences of Copying Process Between IBM FlashCopy and Version 2 (continued) Compared Item IBM FlashCopy Version 2 Copy operation is not executed even if Version 2 pair is deleted. The value of BCE or BCP displays as F(FALSE) though the value of #TRACKS YET TO BE COPIED displayed by the FLASHCPY QUERY RELATIONS command of ICKDSF changes, depending on the number of tracks for which the copy has not been completed. Receiving Failover/Failback command Receives Failover/Failback command.
Table 75 Differences of Relationship Releasing Process Between IBM FlashCopy and Version 2 (continued) Compared Item IBM FlashCopy Version 2 area that is included in the extent is withdrawn. CAUTION: If one of the following operations has been performed, the creation of relationships may fail: • When only the central part of the copy target for the relationship is • A scratch operation included in the specified extent, only the area that is included is • Datasets deletion withdrawn.
Comparison of Supporting Commands IBM FlashCopy supports the ICKDSF commands, while Version partly supports. However, if you execute the commands to a TrueCopy for Mainframe M-VOL or ShadowImage for Mainframe S-VOL that is in pending status, the commands will end abnormally with CC=12. See (page 148) for details on how to avoid the abnormal ending. In addition, Version 2 does not support the following parameters of the TSO commands.
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. • Page 148 • Page 148 • Page 149 • Page 150 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.
Table 76 Avoiding Abnormal Ending of the ICKDSF Commands (for Version 2) (continued) Command Avoiding Method is in duplex or suspend status, and then execute the command. Use the CQUERY command of the TSO to check the pair status SIM Reporting The storage system reports a service information message (SIM) to the host when it is necessary to notify the user of a possible service requirement for the storage system. The SIMs are classified according to severity for reporting and logging purposes: 1.
Table 77 SIMs for Version 1 and Version 2 (continued) Reference Code SSB22 Importance Level Descriptions SSB23 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. 47 E6 Moderate The Version 1 relationship is automatically withdrawn and the T-VOL becomes inaccessible because the power supply was turned on while the shared memory volatilized. 4B 2x Moderate The copying process for Version 2 ends abnormally.
12 Support and Other Resources Related Documentation • HP XP24000/XP20000 LUN Manager User Guide • HP XP24000/XP20000 Disk Array Owner Guide • HP XP24000/XP20000 Remote Web Console User Guide • HP XP24000/XP20000 External Storage Software User Guide • Hitachi Universal Replicator™ for Mainframe User Guide: HP XP24000 Disk Array, HP XP20000 Disk Array • HP XP24000/XP20000 Business Copy Software User Guide • Hitachi ShadowImage™ for Mainframe User Guide: HP XP24000 Disk Array, HP XP20000 Disk Arr
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, 151 COPY mode, 32 on-demand copying, 32 R dataset copying, 34 document related documentation, 151 documentation HP website, 151 providing feedback, 152 reference codes Version 1, 23 Version 2, 79 related documentation, 151 relationships Version 2, 30 releasing Version 2 relationships, 105 Remote FlashCopy function, 46 Reverse Restore function, 38 E S extents Version 1, 6 Version 2, 3
