HP XP P9000 for Compatible FlashCopy Mirroring User Guide Abstract This guide explains how to use HP XP P9000 FlashCopy Mirroring Software to create and use point-in-time copies of data stored by mainframe hosts on HP XP P9000 disk arrays. Topics include installing the license, creating copy pairs using PPRC, TSO, DFSMSdss and ICKDSF command utilities, and restoring source volumes using reverse copy.
© Copyright 2011, 2014 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 Compatible FlashCopy operations.......................................................7 About Compatible FlashCopy.....................................................................................................7 Establishing a Compatible FlashCopy relationship.........................................................................7 Copy modes............................................................................................................................8 Copying by volume..
Using TSO to establish Compatible FlashCopy relationships by extents .....................................58 Using DFSMSdss to establish Compatible FlashCopy relationships by extents ............................60 Using ANTRQST Macro to establish Compatible FlashCopy relationships by extents ..................60 Using z/VM CP to establish relationships for Compatible FlashCopy ............................................61 Using z/VM FlashCopy to establish relationships......................................
Commands for establishing relationships...............................................................................99 Using PPRC TSO to establish relationships.............................................................................99 Using DFSMSdss to establish relationships ..........................................................................100 Using ICKDSF to establish relationships...............................................................................
History window....................................................................................................................132 Option window....................................................................................................................135 FC Z/FCSE window..............................................................................................................136 Glossary..................................................................................................
1 About Compatible FlashCopy operations This chapter provides an overview of Compatible FlashCopy operations on the P9500 storage system. About Compatible FlashCopy The P9500 is functionally compatible with the IBM FlashCopy V2 (FCv2) and IBM FlashCopy SE (FCSE) host control functions.
Figure 1 Multiple relationships You cannot create a cascaded relationship. That is, an extent that is already set as a copy target cannot be used as a copy source to create a new relationship, as shown in the following figure. Figure 2 Cascaded Compatible FlashCopy relationship not supported Copy modes When you establish a Compatible FlashCopy relationship, you select the mode, COPY or NOCOPY, for the copy operation. NOCOPY mode can be selected only for Compatible FlashCopy SE.
the old data is copied from the S-VOL to the T-VOL first, and then the read/write operation is performed. This process is called on-demand copying. The following figure shows the process of on-demand copying. Figure 3 On-demand copying 1. 2. 3. From the host, there is a write request to an S-VOL from where the data has not been copied, or there is a Read or Write request to the space in the T-VOL to where the data has not been copied.
Copying by volume If you do not specify an extent when you establish a relationship, the entire volume is copied. This is called volume copying. 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. Only a complete volume can be copied using Compatible FlashCopy SE. Copying by dataset If you specify the extent when you establish a relationship, only a part of the volume will be copied. This is called dataset copying.
Table 1 Compatibility between Compatible FlashCopy and user interface functions Functions User interface Volume copy Dataset copy COPY mode NOCOPY mode Incremental FlashCopy Using Consistency Groups for Dataset Copies Reverse Restore FlashCopy to PPRC Primary Volume Fast Reverse Restore Remote FlashCopy Preserve Mirror FlashCopy TSO DFSMSdss ICKDSF ANTRQST Macro Multi relationship OK OK OK OK NOCOPY mode OK OK OK OK COPY mode OK OK OK OK Multi relationship OK OK No OK NO
Figure 5 Using Consistency Groups with Compatible FlashCopy: Copying data stored over multiple volumes Figure 6 Using Consistency Groups with Compatible FlashCopy: Copying multiple data stored over multiple volumes The first figure shows copying the data stored over volumes #1-#3 to volumes #4-#6. You need to establish relationships of volume #1 and #4, #2 and #5, and #3 and #6, then copy the data.
The following figure shows the workflow from establishing the relationship (using Compatible FlashCopy) to executing the update copy operation using the Incremental FlashCopy function. Figure 7 Incremental FlashCopy The previous figure shows Data 2A managed as 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.
• If the S-VOL capacity exceeds the T-VOL capacity in the relationship being reversed. • If the original relationship was reestablished using the Fast Reverse Restore function. For details about Fast Reverse Restore function, see “Fast Reverse Restore function” (page 14). You can judge whether the Reverse Restore function can be used by examining the results of the FLASHCOPY QUERY RELATIONS command of ICKDSF.
After you re-establish a relationship by using the Fast Reverse Restore function, the contents of the new S-VOL are not ensured. You can judge whether the Fast Reverse Restore function can be used by examining the results of the FLASHCOPY QUERY RELATIONS command of ICKDSF. For details, see “Displaying information about Compatible FlashCopy pairs: FLASHCPY QUERY RELATIONS” (page 71).
FlashCopy pairs can be created after creating Cnt Ac-S Z pairs only when the following options are used: • DFSMSdss: FCTOPPRCPRIMARY • TSO: TGTPPRIM (YES) • ICKDSF: TGTOKASPPRCPRIM (YES) • ANTRQST Macro: TGTPPRIM (YES) For details about using Compatible FlashCopy with Cnt Ac-S Z, see “Using Compatible FlashCopy with Continuous Access Synchronous Z” (page 27). • Cnt Ac-S Z program product is required for using the FlashCopy to PPRC Primary Volume function.
Figure 11 Creating Cnt Ac-S Z pair in Compatible FlashCopy pair Figure 12 Dataset copying Comparison of Results of Cnt Ac-S Z Pair operations Cnt Ac-S Z pair operations sometimes produce different results depending on whether differential data of the Cnt Ac-S Z pair are stored in units of tracks or cylinders. See the following table.
Table 2 Comparison of results of Cnt Ac-S Z pair operations Comparison Item If differential data of the Cnt Ac-S If differential data of the Cnt Ac-S Z Z pair are stored in units of tracks pair are stored in units of cylinders Is it possible to use Cnt Ac-S Z pair volumes that are not suspended to create FC Z relationships? Yes No Is it possible to use suspended Cnt Ac-S Z pair volumes Yes to create FC Z relationships? Yes.
Figure 13 Remote Compatible FlashCopy function The following table shows whether the Remote Compatible FlashCopy function can be combined with other Compatible FlashCopy functions.
Compatible FlashCopy to Continuous Access Journal Z Primary Volume Function The Compatible FlashCopy to Cnt Ac-J Z Primary Volume function enables you to share Compatible FlashCopy T-VOLs and Cnt Ac-J Z P-VOLs. When you share Compatible FlashCopy T-VOLs and Cnt Ac-J Z P-VOLs, the status of the Cnt Ac-J Z pairs must be Duplex, Pending duplex, Suspend or Suspending.
Figure 14 Overview for Preserve Mirror Compatible FlashCopy function The two methods to establish a Compatible FlashCopy relationship using the Preserve Mirror Compatible FlashCopy function are: • REQUIRED: Perform the copying operation only when the Compatible FlashCopy relationship can be established using the Preserve Mirror Compatible FlashCopy function. When the relationship cannot be established, the command is rejected.
the I/O pattern to the secondary volumes, system option mode 787 may improve the response performance. Caution: • When you establish Compatible FlashCopy relationships with Preserve Mirror Compatible FlashCopy function in COPY mode, a relationship in the MCU and a relationship in the RCU are established, but a progress of a copy operation for a pair in the MCU and that in the RCU are not synchronized.
Figure 16 The flow of Preserve Mirror Compatible FlashCopy function (COPY mode) after the copy processsing finished Each Compatible FlashCopy pair is released after the copying process is completed. The following table shows the Preserve Mirror Compatible FlashCopy functions that can be used with other Compatible FlashCopy functions.
Interoperability with other products and functions Compatible FlashCopy can share volumes with the following software: • Business Copy Z • Continuous Access Synchronous Z • Continuous Access Journal Z • IBM Extended Remote Copy (XRC) • IBM Concurrent Copy (CC) Compatible FlashCopy cannot share volumes with the following software: • Auto LUN The following table describes whether you can perform VSP operations of other products to the S-VOL or T-VOL of Compatible FlashCopy or Compatible FlashCopy
The following table describes whether you can set attributes to the S-VOL or T-VOL of a Compatible FlashCopy relationship by using other solutions. Table 6 Compatibility of volumes shared by Compatible FlashCopy and security solutions Solutions Compatible FlashCopy V2 Volume Compatible FlashCopy SE Volume S-VOL T-VOL S-VOL T-VOL (TSE-VOL) Cache Residency This attribute can be set. This attribute can be set. This attribute can be set. This attribute cannot be set.
Table 7 Reverse Restore and Fast Reverse Restore when a Compatible FlashCopy volume is used as volume of other solutions (continued) Solutions Compatible FlashCopy V2 Volume Compatible FlashCopy SE Volume S-VOL T-VOL S-VOL T-VOL (TSE-VOL) Thin Provisioning Z OK OK OK - Smart Tiers Z OK OK OK - The following volumes cannot be used as the S-VOL or the T-VOL of a Compatible FlashCopy pair.
Figure 18 Compatible FlashCopy and BC Z: Non-Sharable combination Using Compatible FlashCopy with Continuous Access Synchronous Z Volumes that can be shared: The following tables describe the combinations of the volumes when you share Compatible FlashCopy and Cnt Ac-S Z volumes.
Figure 19 Compatible FlashCopy and Cnt Ac-S Z: Non-Sharable combination Figure 20 Compatible FlashCopy SE and Cnt Ac-S Z: Non-Sharable combination Sharing a Compatible FlashCopy S-VOL and a Cnt Ac-S Z volume: You must do the following when you share a Compatible FlashCopy S-VOL and a Cnt Ac-S Z volume, or when you use the Remote Compatible FlashCopy function. • Specify only one Compatible FlashCopy T-VOL if the Compatible FlashCopy S-VOL is shared with Cnt Ac-S Z R-VOL.
Table 10 Shared volume: Compatible FlashCopy S-VOL and Cnt Ac-S Z Shared Cnt Ac-S Z volume Status of Cnt Ac-S Z pair Duplex Cnt Ac-S Z M-VOL 3 R-VOL OK OK Pending Duplex Suspend 1 OK 2 OK OK No Notes: 1. If a Cnt Ac-S Z M-VOL is in pending status and you execute an ICKDSF command for Compatible FlashCopy, the ICKDSF job will end abnormally with CC=12 error. For information on how to avoid that abnormal ending, see “If ICKDSF command ends abnormally” (page 113). 2.
Table 12 Whether Fast Reverse Restore can be performed when a Compatible FlashCopy S-VOL is used as a Cnt Ac-S Z volume Shared Cnt Ac-S Z pair volume Cnt Ac-S Z Status of Cnt Ac-S Z pair Duplex Pending duplex Suspend M-VOL OK* OK* OK* R-VOL No No No *You can perform Fast Reverse Restore when you specify the following options.
3. Vary the Cnt Ac-S Z R-VOL online. The host will be able to recognize the dataset on the Cnt Ac-S Z R-VOL and determine the extent for establishing a Compatible FlashCopy relationship. If the same host is connected to both Cnt Ac-S Z M-VOL and R-VOL, the R-VOL label must be rewritten. 4. Establish the Compatible FlashCopy relationship. Example: COPY FULL INDYNAM(xxxxxx) OUTDYNAM(yyyyyy) FASTREP(REQ) 5. 6. When step 4 completes, vary the Cnt Ac-S Z R-VOL offline. Resynchronize the Cnt Ac-S Z pair.
Table 15 Whether a Compatible FlashCopy V2 volume can be used as a Cnt Ac-J Z volume Compatible FlashCopy V2 Cnt Ac-J Z P-VOL S-VOL S-VOL OK NO T-VOL OK NO Table 16 Whether a Compatible FlashCopy SE volume can be used as a Cnt Ac-J Z volume Compatible FlashCopy SE Cnt Ac-J Z P-VOL S-VOL S-VOL OK NO T-VOL NO NO When you use a Compatible FlashCopy S-VOL as a Cnt Ac-J Z P-VOL You can use a Compatible FlashCopy S-VOL as a Cnt Ac-J Z P-VOL when the Cnt Ac-J Z pair is in any status.
Table 18 Whether Reverse Restore and Fast Reverse Restore can be performed when a Compatible FlashCopy volume is used as a CC or XRC volume Compatible FlashCopy CC / XRC P-VOL S-VOL S-VOL NO1 NO2 T-VOL N/A1 N/A 1. NO - cannot be performed. N/A - cannot be shared 2. Do not execute Reverse Restore or Fast Reverse Restore when an S-VOL is shared by Compatible FlashCopy and CC or XRC.
2 Preparing for Compatible FlashCopy operations This chapter describes how to prepare for Compatible FlashCopy operations. Requirements of Compatible FlashCopy You can establish a Compatible FlashCopy relationship not only for simplex volumes, but also for non-simplex BC Z S-VOLs or T-VOLs in the status other than simplex. The following table shows other requirements on using Compatible FlashCopy.
The following software programs share the resources used for copy operations: • Business Copy Z • Business Copy • Fast Snap • Snapshot • Auto LUN The resources used by Business Copy Z, Business Copy, Fast Snap, Snapshot, and Auto LUN cannot be used for Compatible FlashCopy. The resources that remain, when you exclude the resources used by Business Copy Z, Business Copy, Fast Snap, Snapshot, and Auto LUN from the total resources, are available resources for Compatible FlashCopy.
Copy source: (3339 + 6) × 15 ÷ (639 × 32) = ceil(2.45379) = 3 Copy target: (3339 + 6) × 15 ÷ (639 × 32) = ceil(2.45379)= 3 When you round up 2.45379 to the nearest whole number, it becomes 3. Therefore, the total number of the resources to be used for one relationship is 6 when emulation type is 3390-3. NOTE: For details about the calculation of the total number of the resources to be used per a relationship, see the expression described above.
Figure 23 Copying data in two extents that do not overlap (Two S-VOLs) Figure 24 Copying data in three extents that overlap (One T-VOL) Figure 25 Copying data in two extents that overlap (Two T-VOLs) Figure 26 Copying one extent to another in the same volume The following table provides the calculation examples of the required resources according to the patterns of copying.
Table 22 Reference examples for calculating the number of resources required to create the Compatible FlashCopy relationships 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) 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) Copying one extent to another in the same volume S-VOL 3
Σ(α) means the total number of resources that need to be used, (β) means the total number of resources available in the storage system, (β) = 26,176 or 104,768, or 209,600. For details, see Table 20 (page 34). And Σ(γ) stands for the total number of relationships. The following figure shows seven relationships that are created with 3390-3 volumes, and three relationships that are created with 3390-L volumes (32,769 CYL).
Selecting Prior operation You can use the options in the following table for Compatible FlashCopy V2 and Compatible FlashCopy SE operations. The available option types depend on the storage system settings. Table 23 Types of Compatible FlashCopy V2 and Compatible FlashCopy SE options Option type Features FC Slower Copy1 Suppresses the background copy operations by Compatible FlashCopy, and prioritizes the host I/O operations. For details, see topic “FC Slower Copy1 option” (page 40).
If Business Copy pair relationships exist in the same parity group, host I/O responses might not be improved. FC Ext. Slower Copy1 Option The FC Ext. Slower Copy1 option is used to prioritize host I/O response over background copying processing of Compatible FlashCopy relationships. When the FC Ext. Slower Copy1 option is in effect and the MP operating ratio of the MP blade exceeds 65%, background copy operations are suppressed, and consequently host I/O response improves.
Installing and removing Compatible FlashCopy This section describes how to install and remove Compatible FlashCopy. To enable Compatible FlashCopy to function on the storage system, the Compatible FlashCopy features and software must be installed and enabled on the storage system. In some cases, you may need to install additional shared memory before installing Compatible FlashCopy. For details, contact your HP account representative.
License Capacity Requirements The total volume capacity that is used in Compatible FlashCopy must be less than the license capacity you purchased. You need to maintain the total volume capacity that is used in Compatible FlashCopy that is less than or equal to the license capacity that you purchased. • The total capacity of P-VOL and S-VOL of Compatible FlashCopy must be less than or equal to the license capacity that you purchased.
3 Performing Compatible FlashCopy operations This chapter describes how to perform operations using Compatible FlashCopy. Operating commands for Compatible FlashCopy Compatible FlashCopy supports commands that enable you to perform operations from the zSeries and S/390 host systems. These commands include the following: • PPRC TSO • DFSMSdss • ICKDSF • ANTRQST Macro • z/VM CP For detailed information on using these operating commands, see the IBM user documents.
ANTRQST Macro commands ANTRQST macro commands include the following: • REQUEST=FCESTABLISH • REQUEST=FCWITHDRAW • REQUEST=FCQUERY z/VM CP commands z/VM CP commands include the following: • FLASHCOPY • FLASHCOPY ESTABLISH • FLASHCOPY BACKGNDCOPY • FLASHCOPY RESYNC • FLASHCOPY TGTWRITE • FLASHCOPY WITHDRAW • QUERY VIRTUAL FLASHCOPY Operating systems supporting Compatible FlashCopy Operating systems that support Compatible FlashCopy include the following: • OS/390 V2R10 • z/OS V1R0 • z
Establishing relationships by volumes for Compatible FlashCopy To establish relationships by volumes for Compatible FlashCopy, you use one of the following sets of commands: • PPRC TSO • DFSMSdss • ICKDSF • ANTRQST Macro CAUTION: A time-out may occur when more than 100 FlashCopy relationships are established at the same time with storage systems that are shared with an IBM OS or a Fujitsu OS.
Table 24 Parameters for the FCESTABL command (Volume copying) (continued) Parameter Value Description is completed, and the differential data between the S-VOL and the T-VOL will be managed. As long as the relationship is maintained, you cannot update the T-VOL. The differential data between the S-VOL and the T-VOL will be copied when you execute the FCESTABL command with INCREMENTAL parameter specified or you execute the FCESTABL command (Reverse Restore) with the S-VOL and the T-VOL reversed.
Table 24 Parameters for the FCESTABL command (Volume copying) (continued) Parameter Value Description FRR Only the copied part from the S-VOL to the T-VOL of the established relationship will be copied. You reverse the S-VOL and the T-VOL of the relationship. PRESERVEMIRROR or NO PRESMIR Establishes the relationship without using the Preserve Mirror FlashCopy function. If PRESERVEMIRROR is not specified, NO is set by default.
Table 25 Parameters for DFSMdss, Volume copying (continued) Parameter Value Description copied to the backup tape or disk. In this case, it is not necessary to specify COPYVOLID to copy the volume label. DUMPCONDITIONINO *1 N/A DUMPCONDITIONINO 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 25 Parameters for DFSMdss, Volume copying (continued) Parameter Value Description FCINCRVERIFY N/A Use FCINCRVERIFY to verify the condition established when re-executing the COPY command by specifying FCINCREMENTAL on the relationship created by using FCINCREMENTAL. NOREVERSE The copy operation will be executed only when you specify the S-VOL and the T-VOL in the same way as when the relationship was created.
//SYSPRINT DD SYSOUT=* //SYSIN DD* CGCREATE ACCESSVOLUME(FC Z00) FCCGVERIFY(FC Z00) The following example shows the COPY FULL command with FCINCREMENTAL: //SYSPRINT DD SYSOUT=* //VOL1 DD UNIT=3390,VOL=SER=FC Z00,DISP=OLD //VOL2 DD UNIT=3390,VOL=SER=FC Z01,DISP=OLD //SYSIN DD * COPY FULL INDDNAME(VOL1) OUTDDNAME(VOL2) FCINCREMENTAL When the DFSMSdss command COPY FULL is executed, all the datasets on the S-VOL are copied to the T-VOL (see the following figure).
Table 26 Parameters for the ICKDSF command (FLASHCPY ESTABLISH) (continued) Parameter Value Description TARGETVOL or TGTVOL CU number Specifies the CU number, LDEV number, and device number (device address) of the T-VOL on which you want to perform the FLASHCPY ESTABLISH command. This parameter is required. LDEV number Target device number CHANOERECORDINO, CHANOERCD, or CHRCD YES Establishes the relationship which covers the entire volume.
Table 26 Parameters for the ICKDSF command (FLASHCPY ESTABLISH) (continued) Parameter Value Description TGTCANCOMEONLINE or TGTONLINE YES The T-VOL can be set to online after the relationship is established. TGTOKASPPRCPRIM The default setting of this parameter is YES. NO The T-VOL cannot be set to online until the relationship is deleted. YES To be specified when the FC Z T-VOL and the Cnt Ac-S Z M-VOL (or Cnt Ac-J Z P-VOL) are shared.
2. 3. 4. Specify the JCL statement in the DDNAME parameter or specify the S-VOL device number in the UNITADDRESS parameter. Specify the CU number, LDEV number, and device number of the T-VOL for the TARGETVOL parameter. Execute the FLASHCPY ESTABLISH command (Incremental FlashCopy), specifying YES for the CHANOERECORDINO parameter, for example: FLASHCPY ESTABLISH UNIT(X'7000') TARGETVOL(X'00',X'01',7001) CHANOERECORDINO(YES) The pair is created. 5.
2. 3. 4. Specify the JCL statement in the DDNAME parameter or specify the S-VOL device number in the UNITADDRESS parameter. Specify the CU number, LDEV number, and device number of the T-VOL for the TARGETVOL parameter. Specify YES for the CHANOERECORDINO parameter and execute the FLASHCPY ESTABLISH command (Incremental FlashCopy), for example: FLASHCPY ESTABLISH UNIT(X'7000') TARGETVOL(X'00',X'01',7001) CHANOERECORDINO(YES) The pair will be created. 5.
Table 27 ANTRQST macro command parameters (REQUEST=FCESTABLISH) (continued) Parameter Value Description TGTPPRIM YES Specify this parameter to use the FC Z T-VOL as the Cnt Ac-S Z M-VOL (or Cnt Ac-J Z P-VOL). NO Specify this parameter not to use the FC Z T-VOL as the Cnt Ac-S Z M-VOL (or Cnt Ac-J Z P-VOL). NO is the default setting. RETINFO Return value Obtains the return code and the reason code of the execution results. For details about the codes, see the IBM manual.
Table 27 ANTRQST macro command parameters (REQUEST=FCESTABLISH) (continued) Parameter Value Description specify this number, use the TGTSERIAL, TGTLSS, TGTDVC parameters instead of TDEVN. PRESMIR NO Establishes the relationship without using the Preserve Mirror FlashCopy function. If PRESMIR is not specified, NO is set by default. REQ Establishes the relationship using the Preserve Mirror FlashCopy function. If the relationship cannot be established, the system rejects the command.
Establishing relationships by extents for Compatible FlashCopy To establish relationships by extents for Compatible FlashCopy, you use the one of the following sets of commands: • PPRC TSO • DFSMSdss • ANTQRST Using TSO to establish Compatible FlashCopy relationships by extents When you establish Compatible FlashCopy relationships by extents with the FCESTABL command, the parameters in the following table become available: Table 28 Parameters for the FCESTABL command (Compatible FlashCopy / Dataset co
When the FCESTABL command with the XTNTLTS or XXTNTLST parameter specified is executed, only the data on the copy source extents specified by the XTNTLTS or XXTNTLST parameter are copied to the copy target extents specified by the XTNTLTS or XXTNTLSTor XXTNTLST parameter.
6. 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. FCESTABL command can only be executed once per Compatible FlashCopy relationship. You cannot execute this command repeatedly for the same FC Z relationship. The following example shows an example of how the FCESTABL command is used.
Table 29 ANTRQST macro command parameters (REQUEST=FCESTABLISH) Parameter Value Description SRCEXTENTS Copy source extent (copy range) Specifies the copy source extent (copy range) by setting the starting and ending addresses of the source and target with CCHH (cylinder and head numbers). Up to 32 extents can be specified. When SRCEXTENTS is not specified, the data on all the tracks are copied. Note that you cannot specify this parameter if you specify YES for the INCREMENTAL parameter.
Table 31 Parameters available with FLASHCOPY command (continued) Parameter Value Description scyl2 Starting cylinder of target Specifies the starting cylinder of the copy destination. Specify 0 if the entire volume is the target. ecyl2 Ending cylinder of target Specifies the ending cylinder of the copy destination. END can be specified if the entire volume is the target. A usage example of the FLASHCOPY command is shown below.
NOTE: If the relationship is established with the FLASHCOPY ESTABLISH command, 0010 might be displayed as the reference code in the History dialog box of StorageNavigator regardless of the parameter. When you operate in the NOCOPY mode, code 0023 might be displayed. Using z/VM FLASHCOPY BACKGNDCOPY to start up background copying The FLASHCOPY BACKGNDCOPY command starts up the background copy of the relationship established in the NOCOPY mode.
Table 35 Parameters for the FLASHCOPY TGTWRITE command Parameter Value Description TARGET Secondary device number, Starting cylinder of target, Ending cylinder of target Specifies the device number (device address or mini disk number), the starting cylinder, and the ending cylinder of the copy destination.
Using TSO FCQuery command to view relationship states of Compatible FlashCopy The following table shows the parameter you can use with the FCQUERY command to view relationship states: Table 37 Parameters for the FCQUERY command Parameter Value Description DEVN Device number Specify the number (device address) of the FC Z volume on which you want to see its status. REMOTE YES You use the Remote FlashCopy function to establish a relationship. NO You do not use the Remote FlashCopy function.
Table 38 Information displayed by the FCQUERY command (continued) Displayed item Displayed content Definition ACT - Number of active Compatible FlashCopy V2 and Compatible FlashCopy SE relationships. See the following figure. MAX - Maximum number of pairs that can be created with the device specified by DEVN. XC S Volume specified by DEVN is in one of the following status.
Table 38 Information displayed by the FCQUERY command (continued) Displayed item Displayed content Definition SEQNUM - Displays the Sequence Number. However, since Compatible FlashCopy does not support this function, "00000000" will always be displayed for this item. For details about Sequence Number, see the IBM manual. *In case the volume is set online in more than one LPAR defined by the mainframe system host.
Table 39 Information displayed by the FCQUERY command Displayed item Definition RELATIONSHIP DETAIL STARTING TRACK CCHH number of the starting address. The CCHH number specified here is displayed if the STARTADDR parameter is specified. “00000000” is displayed if the STARTADDR 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. WRITE INHIBITED Y Writing is not allowed. N Writing is allowed.
Table 39 Information displayed by the FCQUERY command (continued) Displayed item Displayed content Definition S The relationship is established between the two Cnt Ac-S Z R-VOLs with the Preserve Mirror FlashCopy function. U The relationship is in the status where the type of the Preserve Mirror FlashCopy function (Preferred or Required) cannot be identified because the M-VOL and R-VOL of Cnt Ac-S Z are mixed. NO. OF TRACKS - The number of tracks in the relationship.
CAPABILITY ASY PVOL CC SRC INACCESS INHIBIT MAX EXCD NEITHER PPRC PRI PPRC SEC PHASE 1 SRC CAP TGT CAP XRC SRC TGT CAP LEGEND = ASYCHRONOUS PPRC REMOTE COPY PRIMARY = CONCURENT COPY SOURCE = VOLUME INACCESSIBLE, DATA NOT OBTAINABLE = FLASHCOPY INHIBITED O. THIS-VOLUME = MAXIMUM RELATIONS EXCEEDED AT-VOLUME OR ESS LEVEL = VOLUME NEITHER FC SOURCE NOR FC TARGET CAPABLE = PPRC PRIMARY = PPRC SECONDARY = PHASE 1 (VERSION 1) RELATIONSHIP EXISTS O.
Displaying information about Compatible FlashCopy pairs: FLASHCPY QUERY RELATIONS To view information about all pairs in a specified volume, execute the ICKDSF FLASHCPY QUERY RELATIONS command. See the following example. FLASHCPY QUERY RELATIONS UNIT(X'7001') The following is an example of information that is displayed by executing the FLASHCPY QUERY RELATIONS command.
Table 42 Information displayed by the FLASHCPY QUERY RELATIONS command (continued) Displayed item 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. F It is not verified whether the displayed information is the latest or not. T The writing to the S-VOL is not allowed. F The writing to the S-VOL is allowed. T The writing to the T-VOL is not allowed.
Table 42 Information displayed by the FLASHCPY QUERY RELATIONS command (continued) Displayed item Displayed content Meaning S The relationship is established between two Cnt Ac-S Z R-VOLs with the Preserve Mirror FlashCopy function. U The relationship is in the status where the type of the Preserve Mirror FlashCopy function (Preferred or Required) cannot be identified, because the M-VOL and R-VOL of Cnt Ac-S Z are mixed.
Table 43 Parameters for the ICKDSF command (REQUEST=FCQUERY) (continued) Parameter Value Description QRYLSS CU number Specifies the CU number of the S-VOL which you want to perform the FCQUERY command. Use this parameter when REMOTE is YES. QRYSSID SSID Specifies the SSID of the CU on which you establish the FlashCopy relationship. Use this parameter when REMOTE is YES.
3. The Description column displays operations that were run. The Descriptions are explained below. History window operation messages for FC Z Code Description Explanation 0010 COPY STARTED (FC) The background copy operation started. This message displays: • When the relationship is established, not when the copy operation starts • When the relationship is established without specifying the CHGRECORD option of the FLASHCOPY ESTABLISH command of z/VM.
Code Description Explanation message displays when the pair is reestablished and not when the copy operation starts. 0041 COPY STARTED (FAST REVERSE RESTORE) The Fast Reverse Restore function started a second or later incremental copy. This message displays when the pair is reestablished and not when the copy operation starts.
• ANTRQST Macro • z/VM CP CAUTION: A time-out may occur when more than 100 FlashCopy relationships are released at the same time with storage systems that are shared with an IBM OS or a Fujitsu OS. To avoid timeouts,divide the tasks into small groups and release relationships at intervals of about 5 seconds per 100 relationships.
Table 45 Parameters for the FCWITHDR command (Compatible FlashCopy) (continued) Parameter Value Description TGTUCB YES Specifies the device number (device address) of the T-VOL on which you want to perform the FCWITHDR command. To specify this number, use the TDEVN parameter. YES is the default setting. NO Specifies the serial number, the CU number, and the LDEV number of the T-VOL on which you want to perform the FCWITHDR command. To specify this number, use the TARGET parameter instead of TDEVN.
Table 46 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 fall within the range specified by the XTNTLST or XXTNTLST parameter The FCWITHDR command will do nothing and end normally. There are several effective combination patterns of the parameters of the FCWITHDR command.
By executing the command described in the example, the relationship established with the specified target, Dataset 3, in the device numbered 4203, is withdrawn (see the following figure). But the relationship established with Dataset 4 is not withdrawn because it is specified as the dataset source. In short, there are two relationships before executing the command above, and after executing the command, there is only one relationship.
Figure 35 Diagram of the FCWITHDR command processing (TDEVN: specified, DDSW = NO, XTNTLST specified) (for Example 2A) The following is another example of the command description for Case 2. Similar to the previous example, 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.
Figure 36 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. The following figure shows an example of the command description for Case 3.
Figure 37 FCWITHDR command processing (SDEVN and TDEVN: specified, DDSW = NO) (for Case 3) Case 4 (a, b): SDEVN and TDEVN Specified, DDSW = NO, XTNTLST Parameter Specified Among the relationships established between the source device specified by SDEVN and the target device specified by TDEVN, the relationships included in the extents specified by the XTNTLST parameter are withdrawn. The relationships that are only partly included in the specified extents are not withdrawn.
Figure 38 FCWITHDR command processing (SDEVN and TDEVN: specified, DDSW = NO, XTNTLST specified) (for Example 4A) The following is another example of the command description for Case 4. Similar to the previous example, this example requests the withdrawal of the relationships that are established within the copy source extent in the device numbered 4202 and the copy target extent in the device numbered 4203.
Figure 39 FCWITHDR command processing (SDEVN and TDEVN: specified, DDSW = NO, XTNTLST specified) (for Example 4B) The following is an example of the command description that indicates that the extent specified by the XTNTLST parameter is located in the center of Dataset 1, and the specified extent in the device numbered 4202 is included as a part of Dataset 1. Therefore, the relation established with Dataset 1 is not withdrawn.
examples show the same content represented by a different description, both requesting the withdrawal of all the relationships established with the device numbered 4202. Example 6 FCWITHDR command description (SDEVN and TDEVN: specified, DDSW = YES) FCWITHDR SDEVN(X'4202') DDSW(YES) FCWITHDR SDEVN(X'4202') TDEVN(X'4203') DDSW(YES) By executing the FCWITHDR command described in the example, the relations established with Dataset 1 and Dataset 2 in the device numbered 4202 are withdrawn.
Example 7 FCWITHDR command description (SDEVN and TDEVN: specified, DDSW = YES, XTNTLST specified) (for Case 6) FCWITHDR SDEVN(X'4202') DDSW(YES) XTNTLST(X'010000000' X'1100000E' X'21000000' X'2200000E') FCWITHDR SDEVN(X'4202') TDEVN(X'4203') DDSW(YES) XTNTLST(X'010000000' X'1100000E' X'21000000' X'2200000E') Before executing the FCWITHDR command in the example, there are three relationships. After executing the command, there is only one relationship.
USING ICKDSF to release Compatible FlashCopy relationships The following table shows the parameters that you can use with the ICKDSF command when you release Compatible FlashCopy relationships: Table 48 Parameters for the ICKDSF command (FLASHCPY WITHDRAW) Parameter Value Description 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 48 Parameters for the ICKDSF command (FLASHCPY WITHDRAW) (continued) Parameter RELATSPACE* Value Description NO Releases the relationship established by the Preserve Mirror FlashCopy function after the background copying process completes. If FORCE is not specified, NO is set by default. - If T-VOL is TSE-VOL, the physical capacity of the allocated TSE-VOL is released. *Valid in Compatible FlashCopy SE. Releasing pairs: FLASHCPY WITHDRAW To withdrawa pair: 1.
The background copying process is executed on the relationship when the copy source of the relationship is in the DDNAME, SYSNAME, or UNITADDRESS-VOLume. In addition, the relationship is released when its copy source is in the DDNAME, SYSNAME, or UNITADDRESS-VOLume.
The parameters that are available with the FLASHCOPY WITHDRAW command are shown in the following table: Table 51 Parameters for the FLASHCOPY WITHDRAW command Parameter Value Description SOURCE Primary device number, Starting cylinder of source, Ending cylinder of source Specifies the device number (device address or mini disk number), the starting cylinder, and the ending cylinder of the copy source.
4 Performing Compatible FlashCopy SE operations This chapter provides information about performing operations with Compatible FlashCopy SE. Overview of FlashCopy SE FlashCopy SE (FCSE) can reduce the physical volume size of the T-VOL by using a virtual volume that is a track space-efficient volume (TSE-VOL) as the FlashCopy T-VOL. Before you can use FCSE, both Compatible FlashCopy SE and Thin Provisioning Z must be installed.
Table 53 Other requirements for Using FCSE Item Requirement Controller emulation type I-2107 The controller emulation type for an S-VOL and a T-VOL must be the same. Available volume Compatible FlashCopy can use the volume whose LDKC:CU:LDEV (LDKC: control unit image: logical device ID) is between 00:00:00 and 00:FE:FF. Creating and modifying pools and TSE-VOLs for Compatible FlashCopy SE After you create a TSE-VOL, the volume is in blocked status.
8. 9. Click Option. In the Initial Pool ID text box, enter a number from 0 through 127. The smallest available non-zero number appears in the text box by default. No number appears in the text box if no available pool ID exists. When the registered pool ID is entered, the smallest available pool ID is registered. 10. In the Subscription Limit text box, enter an integer value from 0 to 65534 as the subscription rate (%) for the pool.
NOTE: states: You cannot specify a pool when creating TSE-VOLs unless the pool is in one of following • Normal state • Exceeded Threshold state • In progress of pool-capacity shrinking Perform the following steps if necessary: • Click Filter to open the menu, specify the filtering, and then Apply. • Click Options to specify the units of pools or the number of lines to be displayed. To create a TSE-VOL: 1. Click Create LDEVs. The Create LDEVs window appears. 2.
12. In the Initial SSID text box, type the 4-digit SSID of a hexadecimal number (0004 to FFFE). To confirm the created SSID, click View SSID to display the View SSID windows. 13. From the Cache Partition list, select CLPR. 14. From the Processor Blade list, select a processor blade. Select a processor blade to be used by the LDEVs. To assign a specific processor blade, select the ID of the processor blade. To allow the storage system to assign processor blades to the LDEVs being created, click Auto. 15.
5. Click Finish. The Confirm window appears. 6. Click Apply. If the Go to tasks window for status check box is selected, the Tasks window appears. Changing the TSE-VOL settings Before registering a TSE-VOL, you may need to change the TSE-VOL settings. To change the TSE-VOL settings: 1. In the Selected LDEVs table in the Create LDEVs window, select LDEV and click Change LDEV Settings. The Change LDEV Settings window appears. 2. 3.
the data that is updated in the S-VOL can be successfully copied to T-VOL if THP Z pages that are allocated to that TSE-VOL have space. When the accessed location is unallocated and the T-VOL page has no space, usually read and write processing cannot be performed. However, if the location has been already allocated, read processing can be performed.
Establishing relationships for FlashCopy SE Keeping data consistent while establishing relationships When you use the FCESTABL command to establish FlashCopy SE relationships, you can keep data consistent by suspending write operations to S-VOLs using the ACTION parameter. The ACTION parameter, which is a parameter for the FCESTABL command, is described in the following table.
Example 11 Example of the FCESTABL command (COPY mode) FCESTABL SDEVN(X'4202') TDEVN(X'4203') MODE(NOCOPY) SETGTOCK (YES) Using DFSMSdss to establish relationships The DFSMSdss copy command is used to process Compatible FlashCopy SE volume copy operations. The FCSETGTOK and FCNOCOPY parameters must be specified when performing Compatible FlashCopy SE operations.
Viewing relationship states of Compatible FlashCopy SE Using FQUERY to view relationship states The FCQUERY command can be used to display information including the attributes set to the devices specified by DEVN and the number of Compatible FlashCopy SE relationships established with the specified devices. The following example of the FCQUERY command requests information be displayed on on the device numbered 1900.
Example 17 Result of FLASHCPY QUERY RELATIONS command Table 42 (page 71) shows information that is displayed by the FLASHCPY QUERY RELATIONS command. "ADDRESSED VOLUME INFORMATION" describes the relationships inside the volume to which the FLASHCPY QUERY RELATIONS command is issued. "PARTNER VOLUME INFO" describes the volume that has relationships that are paired with the relationships in the volume to which the FLASHCPY QUERY RELATIONS command is issued.
1. 2. 3. 4. If the OS of the host server is MVS, specify the appropriate JCL DD statement in the DDNAME parameter, or specify the S-VOL device number of the 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. Execute the FLASHCPY WITHDRAW command in NOCOPY mode. See the next example.
Table 56 LISTDATA command parameters Category Parameters Description SPACEEFFICIENTVOL DEVICE Displays the information about the TSE-VOL for a device that is issuing a command. SUBSYSTEM Displays information about the TSE-VOL in the storage system that is issuing a command. ALL Displays the information about the TSE-VOLs in all of the connected storage systems. ALL is selected by default when the range to be displayed is not specified. SUMMARY Displays an summary information for all the pools.
Example 22 LISTDATA command for a pool information (summary) LISTDATA EXTENTPOOLCONFIG VOLUME(FCF6B6) UNIT(3390) SUMMARY When the above command is issued, the summary information of all the pools is displayed as follows. Example 23 A display example of LISTDATA command for a pool information (summary) 2107 STORAGE CONTROL EXTENT POOL CONFIGURATION REPORT STORAGE FACILITY IMAGE ID 002107.900.HTC.75.000000064561 ......EXTENT POOL ID 0002 SUMMARY............
Example 25 LISTDATA command for detailed pool information 2107 STORAGE CONTROL EXTENT POOL CONFIGURATION REPORT STORAGE FACILITY IMAGE ID 002107.900.HTC.75.000000064561 ......EXTENT POOL ID 0000 SUMMARY............ REPOSITORY FULL WARNING PERCENTAGE: 30 EXT POOL FULL WARNING PERCENTAGE: 30 EXTENT POOL STATUS FIXED BLOCK EXT POOL: NO REPOSITORY CONFIGURED: YES EXTENT POOL AT WARNING PERCENTAGE: NO EXTENT POOL FULL: YES ...EXTENT POOL 0000 DETAILED REPORT....
Table 59 Pool information displayed by LISTDATA command (continued) Category Contents REPOSITORY SIZE - The capacity of the pool (the number of cylinders). (The same value as in the EXTENT POOL SIZE.) REPOSITORY ALLOCATED - The number of cylinders allocated to a pool. (The same value as in the EXTENT POOL ALLOCATED.) REPOSITORY and EXT POOL indicate the same meaning as a pool.
5 Feature comparison with IBM product This chapter describes the differences between IBM FlashCopy and HP Compatible FlashCopy. Feature comparison with IBM product The following table shows the differences between IBM FlashCopy and HP Compatible FlashCopy. Table 60 Differences between IBM FlashCopy and HP Compatible FlashCopy Compared item IBM FlashCopy HP FC Z GLOBAL Mirror status Supported. Not supported. For details about GLOBAL Mirror status, see the IBM manual.
Table 62 Comparison of copying processes (continued) Compared item IBM FlashCopy HP FC Z Restore or Reverse Restore is performed with NOCOPY specified. Restore or Reverse Restore is performed with NOCOPY specified. Regardless of whether or not the option of the Incremental FlashCopy function is specified, if you perform the Fast Reverse Restore, the part of data which is copied from the S-VOL to the T-VOL will be copied from the T-VOL to the S-VOL.
Table 62 Comparison of copying processes (continued) Compared item IBM FlashCopy pair T-VOL that you establish in NOCOPY mode HP FC Z S-VOL. In this state if you release the FC Z pair, the data of Cnt Ac-J Z P-VOL and S-VOL will be different. The operation used when relationship-creation fails in the remote site for Preserve Mirror FlashCopy The relationship on the remote site is not Neither local or remote relationships are created, though the local relationship may created. be created.
Notes • Creation of relationships can fail if any of the following has been performed: ◦ A scratch operation ◦ Deletion of datasets ◦ Volume initialization Correct the situation by using the FCWITHDR command to withdraw the relationship, or by waiting until the background copy operation completes and the relationship disappears. • When only a part of the copy target relationship is included in the specified extent as the copy target, the volume relationship will not be withdrawn.
Comparison of supporting commands IBM FlashCopy supports the ICKDSF commands while Compatible FlashCopy partly supports them. However, if you execute the commands to a Cnt Ac-S Z M-VOL or BC Z S-VOL that is in pending status, the commands will end abnormally with CC=12. See “If ICKDSF command ends abnormally” (page 113) for details on how to avoid the abnormal ending.
6 Troubleshooting This chapter provides troubleshooting information for Compatible FlashCopy and instructions for calling technical support. If a Compatible FlashCopy relationship is suspended Compatible FlashCopy relationships may be suspended if a hardware or software failure occurs during operation. If Compatible FlashCopy relationships are suspended, hosts may be unable to access copy target datasets.
3. 4. Serious Acute The larger the number becomes, the more the message becomes important. The SVP reports all SIMs related to Compatible FlashCopy operations. All SIMs are stored on the SVP for use by HP personnel. The SIMs reported to the zSeries and S/390 host are logged in the SYS1.LOGREC dataset of the host operating system. Each time a SIM is generated, the amber Message LED on the control panel (under the Ready and Alarm LEDs) turns on as an additional alert for the user.
7 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
Conventions for storage capacity values HP XP P9000 disk arrays use the following values to calculate physical storage capacity values (hard disk drives): • 1 KB (kilobyte) = 1,000 bytes • 1 MB (megabyte) = 1,0002 bytes • 1 GB (gigabyte) = 1,0003 bytes • 1 TB (terabyte) = 1,0004 bytes • 1 PB (petabyte) = 1,0005 bytes • 1 EB (exabyte) = 1,0006 bytes HP XP P9000 disk arrays use the following values to calculate logical storage capacity values (logical devices): • 1 KB (kilobyte) = 1,024 bytes •
CAUTION: IMPORTANT: NOTE: TIP: Indicates that failure to follow directions could result in damage to equipment or data. Provides clarifying information or specific instructions. Provides additional information. Provides helpful hints and shortcuts.
A Compatible FlashCopy GUI reference This appendix describes the Remote Web Console windows and tabs for Compatible FlashCopy. Some of the Compatible FlashCopy windows and tabs are also used for Business Copy Z. Replications window Summary area Item Description Licensed Capacity The used capacity and the licensed capacity of each product. Number of Replica LDEVs The number of LDEVs used for local replication pairs.
Item Description Capacity The capacity of the selected LDEV.
Histories table Item Description Date The operation date and time.
BC Z/FC Z/FCSE System Options table This table is displayed when the System Type is Mainframe. Item Description System Option The system options include: • Swap & Freeze: Use this option when you want to save data immediately after Quick Restore as-is. When you enable this option and execute Quick Restore, update copying after Quick Restore is inhibited, the secondary volume in the DUPLEX status is saved without being updated.
Edit SCP Time wizard Edit SCP Time window SCP Time table Item Description CU The CU number. SCP Time (sec.) The SCP (state-change-pending) time set for each CU. The range is 0-518,400 seconds (6 days). Change SCP Time Opens the Change SCP Time dialog. Change SCP Time dialog Information Setting area 122 Item Description SCP Time The SCP (state-change-pending) time set for each CU. The range is 0-518,400 seconds (6 days).
Confirm window for Edit SCP Time SCP Time table Item Description CU The CU number. SCP Time The SCP (state-change-pending) time set for each CU. The range is 0-518,400 seconds (6 days).
B Performing Compatible FlashCopy operations (secondary window) This appendix describes how to perform Compatible FlashCopy operations using the previous version of the Remote Web Console GUI, which opens in a secondary window. Setting options (secondary window) 1. Click Actions > Local Replications > BC Z/FC Z > Option. 2. 3. Click to change to the Modify mode. In the Option window, select the check box for the option that you want to set.
Figure 43 Set SCP Time dialog box The following items display in the Set SCP Time dialog box: Table 68 Set SCP Time dialog box items Item Description SCP Time (sec.) text Specifies the state-change-pending time in seconds (0 to 518,400 seconds (6 days)). The text box displays box the state-change-pending time that is set to the CU selected in the FC Z window by default.
Figure 44 Compatible FlashCopy Information Dialog Box You need the information in the Compatible FlashCopy Information dialog box when you calculate the number of the Compatible FlashCopy relationships that can be established.
Table 69 Compatible FlashCopy Information dialog box (continued) Item Description FCSE Used Capacity (TB) Displays the license information of FCSE and will be indicated in the format of X(Y). X indicates license capacity used by FCSE, and Y indicates total license capacity reserved for FCSE. Unlimited will be displayed when there is no limited license capacity for FCSE. Compatible FlashCopy Displays the information about the Compatible FlashCopy relationships in the volume list.
3. Select the Information command in the menu. The Information dialog box is displayed. Figure 45 Information Dialog Box The Information dialog box shows the following information: Table 70 Information dialog box Item Description Business Copy Z pair(s) The number of BC Z pairs will be displayed in the format of XXXX / YYYY. XXXX indicates the number of BC Z pairs, and YYYY indicates the total number of BC Z pair tables and Business Copy pair tables.
Viewing operation history (secondary window) You use Remote Web Console to view operation history. The History window displays history of operations related to Compatible FlashCopy V2 and relationships. To view the operation history: 1. Click Actions > Local Replications > BC Z/FC Z > History to open the History window.
C Compatible FlashCopy GUI reference (secondary window) This appendix describes the Compatible FlashCopy windows and dialog boxes in the previous version of the Remote Web Console GUI, which displays in a secondary window. If you are using the current Remote Web Console GUI, click the Help button to display descriptions of the windows and dialog boxes, or see “Compatible FlashCopy GUI reference” (page 118). Some of the Compatible FlashCopy windows and tabs are also used for Business Copy Z.
Item Description on the upper right of the Pair Operation window. No volume will be displayed when you select Subsystem on the top of the Tree. Volume List Located on the upper right of the Pair Operation window, displays the following information: • Message: Displays a message when there is no volume or pair to be displayed. If you see the message in the Volume List, click a different icon in the Tree on the left area of the Pair Operation window.
Table 72 Menu command available Command Description Detail Displays detailed information about the selected volume. Information Displays information such as the number of BC Z pairs, and the number of Compatible FlashCopy V2 and Compatible FlashCopy SE relationships or reserved volumes.
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 XP P9000 External Storage for Open and Mainframe Systems User Guide. When the letter 'X' is the end of the LDEV number of P-VOL or S-VOL , the LDEV is the virtual volume for Thin Provisioning Z (e.g.: 00:00:01 X). For details about the virtual volumes, see the HP XP P9000 Provisioning for Mainframe Systems User Guide.
Item Description Code Displays the reference codes of Compatible FlashCopy V2 and Compatible FlashCopy SE. Message Displays the messages to inform the contents of operation and the conditions for Compatible FlashCopy V2 and Compatible FlashCopy SE relationship. For details about the messages, see Table 74 (page 134).
Table 74 Compatible FlashCopy status and history reference codes and messages (continued) Code Message Description 002A COPY ENDED ABNORMAL(FC) The Compatible FlashCopy copy operation ended abnormally. 002F INITIALIZE ENDED ABNORMAL(FC) The Compatible FlashCopy initialization process ended abnormally. 0030 COPY STARTED AFTER MODE CHANGED(FC) The Compatible FlashCopy background copy operation started after the Compatible FlashCopy relationship changed to copy mode.
Item Description Select Option(s) • When you check the checkbox of the option name, that option will be enabled. If you clear the checkbox, that option will be disabled. The options that are available for FC Z in this box are FC Slower Copy1, FC Slower Copy2, FC Ext. Slower Copy1, and FC Ext. Slower Copy2. Other options are available for Business Copy Z. See the HP XP P9000 Business Copy for Mainframe Systems User Guide for details about these other options.
The state-change-pending, in this case, means temporary suspension of the write operation from the host to the Compatible FlashCopy S-VOL. The period during which the write operation is stopped is called state-change-pending time. When you copy the data that is stored over several volumes by using Compatible FlashCopy, the S-VOL will not be overwritten during the time which is defined as the state-change-pending time so that the consistency of the data will be maintained.
Glossary This glossary defines the special terms used in this document. Click the letter links below to navigate. alternate path A secondary path to a logical volume, in addition to the primary path, that is used as a backup in case the primary path fails. array Another name for a RAID storage system. array controller The computer inside a RAID storage system that hosts the Remote Web Console software and is used by service personnel for configuration and maintenance of the storage system.
controller The component in a storage system that manages all storage functions. It is analogous to a computer and contains a processors, I/O devices, RAM, power supplies, cooling fans, and other sub-components as needed to support the operation of the storage system. copy pair A pair of volumes in which one volume contains original data and the other volume contains the copy of the original.
DKCMAIN disk controller main. Refers to the microcode for the RAID storage system. DKP disk processor. Refers to the microprocessors on the back-end director features of the Universal Storage Platform V. EC error code emulation The operation of the RAID storage system to emulate the characteristics of a different storage system. For device emulation the mainframe host “sees” the logical devices on the RAID storage system as 3390-x devices.
internal volume A logical volume whose data resides on drives that are physically located within the storage system. See also external volume. IO, I/O input/output IOPS I/Os per second IP internet protocol IPL initial program load JNL journal JNLG journal group journal group (JNLG) In a Continuous Access Journal system, journal groups manage data consistency between multiple primary volumes and secondary volumes. See also consistency group (CTG).
MB megabyte MB/sec, MBps megabytes per second Mb/sec, Mbps megabits per second MCU See main control unit (MCU). MF, M/F mainframe MIH missing interrupt handler modify mode The mode of operation of Remote Web Console that allows changes to the storage system configuration. See also view mode. MP microprocessor MSCS Microsoft Cluster Server multi-pathing A performance and fault-tolerant technique that uses more than one physical connection between the storage system and host system.
the backup applications run when the applications at the primary site fail, or where the primary site itself fails. primary volume The volume in a copy pair that contains the original data to be replicated. The data in the primary volume is duplicated synchronously or asynchronously on the secondary pairs.
secondary site The physical location of the storage system that contains the primary volumes of remote replication pairs at the main or primary site. The storage system at the secondary site is connected to the storage system at the main or primary site via remote copy connections. The secondary site can also be called the “remote site”. See also primary site. secondary volume The volume in a copy pair that is the copy.
and to replaced data in the pool, maintaining the point-in-time copy of the P-VOL at the time of the split operation. VM volume migration; volume manager VOL, vol volume VOLID volume ID volser volume serial number volume A logical device (LDEV), or a set of concatenated LDEVs in the case of LUSE, that has been defined to one or more hosts as a single data storage unit. A mainframe volume is called a logical volume image (LVI), and an open-systems volume is called a logical unit. (LU).
Index A N ANTRQST, 55 NOCOPY mode, 8 B O background copying, 8 on-demand copying, 9 C P consistency group, 11 contacting HP, 115 conventions document, 116 storage capacity values, 116 text symbols, 116 COPY mode, 8 Creating V-VOLs, 94 pairs history, 74 D dataset copying, 10 document conventions, 116 related information, 115 documentation HP website, 115 providing feedback, 115 E extent, 7 F Fast Reverse Restore, 14 Fast Reverse Restore Function, 14 FLASHCPY ESTABLISH (Fast Reverse Restore), 54
