HP XP7 for Compatible FlashCopy Mirroring User Guide Abstract The HP XP7 for Compatible FlashCopy Mirroring User Guide describes and provides instructions for performing Compatible FlashCopy operations on HP XP7 Storage. Please read this document carefully to understand how to use this product, and maintain a copy for reference purposes.
© Copyright 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......................................................................6 About Compatible FlashCopy.....................................................................................................6 Compatibility between Compatible FlashCopy and mainframe user interface functions......................6 Establishing a Compatible FlashCopy relationship.........................................................................8 Copy modes....................................
Using PPRC TSO to establish Compatible FlashCopy relationships by volumes ...........................43 Using DFMSdss to establish Compatible FlashCopy relationships by volumes.............................45 Using ICKDSF to establish Compatible FlashCopy relationships by volumes...............................48 Creating Compatible FlashCopy relationships using Incremental FlashCopy (Reverse Restore): FLASHCPY ESTABLISH..........................................................................................
Operating when Pool is full.................................................................................................92 Managing failed states.......................................................................................................93 Pool capacity warning to the host.........................................................................................93 Notes when sharing pool with THP V-VOL..................................................................................
1 About Compatible FlashCopy This chapter provides an overview of Compatible FlashCopy operations on the HP XP7 Storage system. About Compatible FlashCopy The HP XP7 Storage is functionally compatible with the IBM FlashCopy V2 and IBM FlashCopy SE host control functions.
Table 1 Compatibility between Compatible FlashCopy and user interface functions (continued) Functions Dataset copy* COPY mode* NOCOPY mode Incremental FlashCopy* Using Consistency Groups for Dataset Copies Reverse Restore* FlashCopy to PPRC Primary Volume* User interface TSO DFSMSdss ICKDSF ANTRQST Macro COPY mode OK OK OK OK Multi relationship OK OK No OK NOCOPY mode OK OK No OK COPY mode OK OK No OK Multi relationship OK OK OK OK Change to NOCOPY mode No No No No
Establishing a Compatible FlashCopy relationship Compatible FlashCopy provides a fast data replication capability that enables you to copy the source data to a target volume virtually or physically. A copy pair created by Compatible FlashCopy is called a relationship. Once a relationship has been created, hosts can access the data that is copied to the target volume. You can specify a range of data to be copied, which is called an extent, when you establish a Compatible FlashCopy relationship.
Figure 1 Multiple copy targets per source supported Figure 2 Cascaded copy relationship not supported Copy modes When you establish a Compatible FlashCopy relationship, you select the mode, COPY or NOCOPY, for the copy operation. • COPY: When you select COPY mode, all data in the S-VOL is copied to the T-VOL. This process is called background copying. When the background copying is complete, the relationship is automatically withdrawn.
If there is a request for a write operation to an S-VOL in which the requested data is not yet copied to the target, or a request for a read/write operation to a T-VOL in which the requested data is not yet copied, 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 figures show the process of on-demand copying.
Figure 5 On-demand copy (case 3: Write request to an area in the T-VOL to which the data has not been copied) 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. When an operation as described is made to the space in the S-VOL or T-VOL where the data has not been copied, Compatible FlashCopy performs on-demand copying before the Read or Write operation.
Dataset copying can be performed when: • The position of the copy source extent is different from the position of the copy target extent and both extents are on the same volume. • The copy source extent and the copy target extent are on different volumes. • The copy source extent and the copy target extent do not overlap when they are on the same volume. • The data in a single source extent is to be copied simultaneously to multiple target extents.
Figure 8 Using Consistency Groups with Compatible FlashCopy: Copying multiple data stored over multiple volumes The first figure shows copying the data stored on volumes #1-#3 to volumes #4-#6. You need to establish relationships for volume #1 and #4, #2 and #5, and #3 and #6, then copy the data. However, if volume #1 is updated before the creation of the Relationship B (relationship of #2 and #5) is completed, the consistency of the data in the copy target cannot be maintained.
Figure 9 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. However, you cannot perform the Restore function: • When the original relationship was established without using the Incremental FlashCopy function.
You can judge whether the Reverse Restore function can be used by examining the results of the FLASHCOPY QUERY RELATIONS command of ICKDSF. For details, see (page 68). When you perform the Reverse Restore function, only the updated data is copied from newly specified S-VOL (former T-VOL) to T-VOL (former S-VOL) as with ordinary re-establishment. The updated Data 2A in the target volume is then lost.
After you re-establish a relationship by using the Fast Reverse Restore function, the contents of the new S-VOL are not ensured, as they will be changed by any host write operations. 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 (page 68).
relationships, or create Compatible FlashCopy relationships after creating Cnt Ac-S Z pairs. However, Compatible FlashCopy relationships 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 (page 28).
Figure 12 Creating Compatible FlashCopy relationship in Cnt Ac-S Z pair Figure 13 Creating Cnt Ac-S Z pair in Compatible FlashCopy relationship 18 About Compatible FlashCopy
Figure 14 Dataset copying Remote Compatible FlashCopy function The Remote Compatible FlashCopy function enables you to perform operations on Compatible FlashCopy relationships on the Cnt Ac-S Z remote storage system from the host connected to the Cnt Ac-S Z local storage system. This function can be used for both Compatible FlashCopy and Compatible FlashCopy SE relationships.
Figure 15 Remote Compatible FlashCopy function Combining Remote Compatible FlashCopy functions with other Compatible FlashCopy functions The following table shows whether the Remote Compatible FlashCopy functions can be combined with other Compatible FlashCopy functions.
Compatible FlashCopy-to-Continuous Access Journal Z primary volume function (Compatible FlashCopy only) 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. You can create Cnt Ac-J Z pairs after creating Compatible FlashCopy relationships.
Figure 16 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 relationship cannot be established in the local site. Release the relationship in the remote site, and try again. • When you use the Preserve Mirror Compatible FlashCopy function, the MIH (missing interrupt handler) value should be the same as for Cnt Ac-S Z operations (preferred MIH value for Cnt Ac-S Z is 60 seconds). Also, you should specify 30 seconds for the RIO MIH time which executes path monitoring of Cnt Ac-S Z.
Data is copied in each Compatible FlashCopy relationship, but not in the Cnt Ac-S Z pairs.If the Withdraw command is issued to release the Compatible FlashCopy relationship, P-VOL and S-VOL in Cnt Ac-S Z#2 becomes inconsistent. Figure 18 The flow of Preserve Mirror Compatible FlashCopy function (COPY mode) after the copy processsing finished Each Compatible FlashCopy relationship is released after the copying process is completed.
The following options of Compatible FlashCopy-to-PPRC primary volume must be specified at the same time: • DFSMSdss: FCTOPPRCPRIMARY • TSO: TGTPPRIM(YES) • ICKDSF: TGTOKASPPRCPRIM(YES) • ANTRQST Macro: TGTPPRIM(YES) Releasing Compatible FlashCopy relationships When you use the DFSMSdss command, keep in mind that the DFSMSdss command cannot release Compatible FlashCopy relationships.
Table 3 Performing operations on Compatible FlashCopy volumes (continued) Operations Cache Residency Compatible FlashCopy Volume Compatible FlashCopy SE Volume S-VOL T-VOL S-VOL T-VOL (TSE-VOL) Setting Read/Write enabled attribute OK OK OK OK Making data in volume reside in cache OK OK OK - The following table describes whether you can create Compatible FlashCopy or Compatible FlashCopy SE relationship to volumes used for another product.
NOTE: Consider the following important points when using external volumes with Compatible FlashCopy: • If an external volume is specified as a Compatible FlashCopy T-VOL, be careful about the setting of the time of path blockade watch, which is the time from when the external storage system is disconnected to when the path is blocked.
Figure 19 Pair configuration: Compatible FlashCopy S-VOL shared with Business Copy Z Usually, you need to specify an unpaired volume (Simplex status) as a copy source (S-VOL) or a copy target (T-VOL). When you specify an BC Z S-VOL as a copy source, you can establish a Compatible FlashCopy relationship only if the BC Z pair is not in Resync-R/REVRSY status. You can establish or release a Compatible FlashCopy relationship if you meet the requirements described above.
Table 7 Compatible FlashCopy and Cnt Ac-S Z shared volume Compatible FlashCopy Continuous Access Synchronous Z P-VOL S-VOL S-VOL OK OK T-VOL OK - Table 8 Compatible FlashCopy SE and Cnt Ac-S Z shared volume Compatible FlashCopy SE Continuous Access Synchronous Z P-VOL S-VOL S-VOL OK OK T-VOL (TSE-VOL) - - Volumes that cannot be shared: The Compatible FlashCopy and Cnt Ac-S Z shared configuration is different from the Compatible FlashCopy and PPRC shared configuration.
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 S-VOL.
Table 10 Whether 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 P-VOL OK* OK* OK* S-VOL No No No *You can perform Reverse Restore when you specify the following options. • DFSMSdss: FCTOPPRCPRIMARY (You cannot perform Fast Reverse Restore when you specify DFSMSdss.
If S-VOL and T-VOL of Compatible FlashCopy are both Thin Provisioning Z volumes, the number of pages remaining in T-VOL may differ depending on the timing. The procedures when you use a DFSMS,TSO, or ICKDSF command are as follows. You cannot perform Fast Reverse Restore when you use DFSMSdss. Using DFSMS commands to share Compatible FlashCopy and Cnt Ac-S Z volumes Note: If the status of the Cnt Ac-S Z pair is duplex, you need to use a TSO command instead of a DFSMS command.
1. 2. To maintain the consistency of data, terminate I/O operations to the volumes of Cnt Ac-S Z pairs. Establish the Compatible FlashCopy relationship. Example: FLASHCPY ESTABLISH UNIT(X'dev#') TARGETVOL(X'ssid',X'cca',lss) ONLINTGT(YES) To share a Compatible FlashCopy T-VOL and Cnt Ac-S Z P-VOL: 1. To maintain the consistency of data, terminate I/O operations to the volumes of Cnt Ac-S Z pairs. 2. Confirm that the Cnt Ac-S Z pair status is Duplex. 3. Establish the Compatible FlashCopy relationship.
Table 16 Whether a Compatible FlashCopy volume can be used as a CC or XRC volume Compatible FlashCopy CC / XRC P-VOL S-VOL S-VOL OK OK T-VOL NO NO* *Do not share Compatible FlashCopy T-VOL with a CC or XRC S-VOL.
Optimizing Volumes Volumes can be optimized by Compatible FlashCopy if you use the DEFRAG command of the DFSMSdss utility with the FASTREPLICATION option. See the IBM FlashCopy manual for details of the option. CAUTION: The DEFRAG command may generate an error because the number of relationships per volume exceeds the maximum when all the following conditions are met. • The parity group including the volume is overloaded when accessed too many times.
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 for unpaired volumes or BC Z volumes regardless of the pair status. The following table shows other requirements on using Compatible FlashCopy.
Table 20 Types of Compatible FlashCopy and Compatible FlashCopy SE options (continued) Option type Features FC Ext. Slower Copy1 Suppresses the background copy operations by Compatible FlashCopy, and prioritizes the host I/O operations. For details, see (page 37). Note: You need to set FC Ext. Slower Copy1 option invalid. FC Ext. Slower Copy2 Suppresses the background copy operations by Compatible FlashCopy, and prioritizes the host I/O operations.
is in effect and the MP operating ratio of the MP blade exceeds 50%, background copy operations are suppressed, and consequently host I/O response improves. When background copying processing of Compatible FlashCopy is suppressed by the FC Ext. Slower Copy2 option, the time taken for background copying increases. When the FC Ext. Slower Copy2 option is in effect, the FC Ext. Slower Copy1 option becomes invalid.
By executing the devserv command, you can view the information on the direct access memory device 4200 and on the magnetic disk controller. Based on the information displayed, update the information on the expanded functions that are maintained in the storage of the host processor. By these expanded functions, the host recognizes that Compatible FlashCopy is supported. 6. 7. Establish Compatible FlashCopy relationships.
track. The license capacity of these volumes cannot be renewed in real time. Therefore, the purchased license capacity can be exceeded by the multiple write requests against the pools. CAUTION: If the total volume capacity that is used in Compatible FlashCopy SE exceeds the volume capacity that you purchased, you can still continue to use Compatible FlashCopy SE for another 30 days.
3 Performing Compatible FlashCopy operations This chapter describes how to perform operations using Compatible FlashCopy. Operating commands for Compatible FlashCopy Compatible FlashCopy supports the following commands that enable you to perform operations from the mainframe host system: • PPRC TSO commands: ◦ FCESTABL ◦ FCWITHDR ◦ FCQUERY To use the PPRC TSO commands, you must add the command names to the AUTHCMD PARM of IKJTSOxx, which is a member of SYS1.
◦ FLASHCOPY WITHDRAW ◦ QUERY VIRTUAL FLASHCOPY For detailed information about using these operating commands, see the IBM user documents. Supported operating systems for Compatible FlashCopy Operating systems that support Compatible FlashCopy include the following: • z/OS V1R0 • z/VM V5R3 and higher Each operating system needs an appropriate PTF. Setting options Prerequisites • 1. 2. 3. 4. 5.
The timing to copy the data when the relationship is established is different between Compatible FlashCopy and Compatible FlashCopy SE. Compatible FlashCopy SE copies data when data is updated in either the source or target volume. CAUTION: A time-out may occur when more than 100 FlashCopy relationships are established at the same time. To avoid timeouts, divide the tasks into small groups and establish relationships at intervals of about 5 seconds per 100 relationships.
Table 21 Parameters for the FCESTABL command (Volume copying) (continued) Parameter Value Description YTW The relationship remains in effect after background copying completes. Data can be written to the T-VOL. Subsequent changes are tracked so that future operations are performed incrementally. This relationship continues until explicitly terminated with a Withdraw request. Note: The target is writable while the incremental relationship is active.
Table 21 Parameters for the FCESTABL command (Volume copying) (continued) Parameter SETGTOK* Value Description PREFERRED or PREF Establishes the relationship using the Preserve Mirror FlashCopy function. If the relationship cannot be established, the copy operation is executed using the existing FlashCopy-to-PPRC primary volume function. TGTPPRIM(YES) must be specified as well. YES Can specify the target T-VOLs as TSE-VOLs. NO Cannot specify the target T-VOLs as TSE-VOLs.
Table 22 Parameters for DFSMdss, Volume copying (continued) Parameter Value Description FASTREPLICATION PREFERRED Executes Compatible FlashCopy copy operation as a priority. If Compatible FlashCopy cannot be used, executes Concurrent Copy or copy operation via the host. When FASTREPLICATION is not specified, the copy operation will be performed in the same way when PREFERRED is specified. REQUIRED Executes Compatible FlashCopy copy operation unconditionally.
Table 22 Parameters for DFSMdss, Volume copying (continued) Parameter Value Description FCTOPPRCPRIMARY PRESMIRNONE Use FCTOPPRCPRIMARY to access the FlashCopy to PPRC primary volume function or the FlashCopy to Cnt Ac-J Z primary volume function. Specify this parameter when Compatible FlashCopy T-VOL and Cnt Ac-S Z or Cnt Ac-J Z P-VOL are shared. PRESMIRREQ Establishes the relationship using the Preserve Mirror FlashCopy function.
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).; Volume area that is not allocated as a dataset is not copied. When the FCFULLVOLUMERELATION parameter is specified, all areas on the S-VOL, including areas that are not allocated as a dataset, are copied to the T-VOL.
Table 23 Parameters for the ICKDSF command (FLASHCPY ESTABLISH) (continued) Parameter Value Description NO Establishes the relationship which covers the entire volume. The relationship will be deleted after the background copying process is completed. The default setting of this parameter is NO.
Table 23 Parameters for the ICKDSF command (FLASHCPY ESTABLISH) (continued) Parameter Value Description NO is the default setting. SOURCEVOL or SRCVOL CU number LDEV number Specifies the CU number, the LDEV number, or the device number of the S-VOL when you use the Remote FlashCopy function. Source device number PRESERVEMIRROR or PRESMIR SETGTOK* REQUIRED Establishes the relationship using the Preserve Mirror FlashCopy function.
FLASHCPY ESTABLISH UNIT(X'7000') TARGETVOL(X'00',X'01',7001) CHANOERECORDINO(YES) The relationship is created. 5. Execute the FLASHCPY ESTABLISH command (Reverse Restore), specify the RESTORE parameter, and reverse the S-VOL and the T-VOL, for example: FLASHCPY ESTABLISH UNIT(X'7001') TARGETVOL(X'00',X'00',7000) RESTORE If the S-VOL is updated before executing the Reverse Restore command, then only the data of the updated part of the S-VOL (differential data) is copied to the T-VOL.
FLASHCPY ESTABLISH UNIT(X'7000') TARGETVOL(X'00',X'01',7001) CHANOERECORDINO(YES) The relationship will be created. 5. Specify the RESTORE parameter and execute the FLASHCPY ESTABLISH command, for example: FLASHCPY ESTABLISH UNIT(X'7000') TARGETVOL(X'00',X'01',7001) RESTORE 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 from the S-VOL.
Table 24 ANTRQST macro command parameters (REQUEST=FCESTABLISH) (continued) Parameter Value Description MODE COPY All the data in the copy range of the volume specified as the source by SDEVN is copied in the background to the volume specified as the target by TDEVN. The relationship ends automatically, and the Compatible FlashCopy relationship is deleted when all the data is copied. COPY is the default setting. NOCOPY Data is not copied in the background.
Table 24 ANTRQST macro command parameters (REQUEST=FCESTABLISH) (continued) Parameter Value Description PREF Establishes the relationship using the Preserve Mirror FlashCopy function. If the relationship cannot be established, the copy operation is executed using the existing FlashCopy-to-PPRC primary volume function. TGTPPRIM=YES must be specified at the same time.
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 25 Parameters for the FCESTABL command (Compatible FlashCopy / Dataset copying) Parameter Value Description EXTENTS Extents (copy range) Specifies the extent (copy range) by setting the same starting and ending addresses of the source and target with CCHH (cylinder and head numbers).
Figure 25 Dataset copying with XTNTLTS or XXTNTLST parameter specified (Compatible FlashCopy) When you establish a Compatible FlashCopy dataset relationship per extent for a volume with CATALOG, you trigger a write operation from the host on both VTOC and CATALOG. To perform dataset copying by using the FCESTABL command: 1. Use the VTOC list stored in the S-VOL to check the VTOC (INDEX, VTOC, etc.) and the position of the extent (CCHH, BC Ze) used for the dataset copy operation. 2.
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 Compatible FlashCopy relationship. The following example shows an example of how the FCESTABL command is used.
Table 26 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 28 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.
flashcopy establish source 10 0-end target 20 0-end Command complete: FLASHCOPY 0010 0 99 TO 0020 0 9 To cancel the relationship remaining after the completion of the copy, use the FLASHCOPY WITHDRAW command. For the FLASHCOPY WITHDRAW command, see (page 88). 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.
Using z/VM FLASHCOPY TGTWRITE command to remove write-protection from an S-VOL To remove write protection from the S-VOL of a relationship, use the FLASHCOPY TGTWRITE command.
2. 3. 4. 5. 6. Click Edit SCP Time. In the Edit SCP Time window, select the CU for which you want to change the state-change-pending time and click Change SCP Time. In the Change SCP Time window, enter the state-change-pending time you want to set and click OK. Click Finish. In the Confirm window, enter a Task Name and click Apply. The Task window appears after the registration if you marked Go to tasks window for status.
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 relationships established with the specified devices. The following is an example of the FCQUERY command. This example requests information on the device numbered 4202 to be displayed. FCQUERY DEVN(1900) The following example shows the information that is displayed as a result of executing the FCQUERY command described in the previous example.
Table 35 Information displayed by the FCQUERY command (continued) Displayed item Displayed content Definition CC S Volume specified by DEVN is currently used as the S-VOL of the Concurrent Copy pair. N Volume specified by DEVN is currently used as the T-VOL of the Concurrent Copy pair, or not used for Concurrent Copy. RV - Displays whether the volume specified by DEVN is Revertible or not.
ACT shows the total number of the active Compatible FlashCopy relationships in each extent. Therefore, in the example in the figure, the total number of the active Compatible FlashCopy relationships in the VOL#0 and VOL#1 is both two, and the digit two (2) displays as the content of ACT. Example of FCQUERY command with the SHOWRELS parameter: FCQUERY DEVN(1900) SHOWRELS(ALL) The result of the FCQUERY command with the SHOWRELS parameter is shown below.
Table 36 Information displayed by the FCQUERY command (continued) Displayed item Displayed content Definition CR Y The updated part is managed as differential data if the S-VOL and T-VOL are updated. N The updated part is not managed as differential data even if the S-VOL and T-VOL are updated. Y Writing to the T-VOL is allowed. N Writing to the T-VOL is not allowed. N The T-VOL is not a TSE-VOL. F The T-VOL is a TSE-VOL. (When the pool is full, the relationship is in Failed State.
Table 37 Parameters for the ICKDSF command (continued) Command Parameter Value Description FLASHCPY QUERY RELATIONS DDNAME or DNAME JCL statement Sets the JCL statement identifying the volume. If the OS of the host server is MVS, this parameter or the UNITADDRESS parameter is required. SYSNAME SYSNAME Sets the SYSNAME in the ASSGN system control statement. If the OS of the host server is VSE, this parameter is required.
Table 38 Information displayed by the FLASHCPY QUERY command (continued) Displayed item Displayed content Meaning CAPABILITY SRC CAP The specified volume can be specified as the S-VOL of Compatible FlashCopy. TGT CAP The specified volume can be specified as the T-VOL of Compatible FlashCopy. NEITHER The specified volume cannot be specified as the S-VOL or T-VOL of Compatible FlashCopy. PPRCOPY PRI The specified volume is the copy source volume of Continuous Access Synchronous Z.
The following table shows the meaning of information displayed as a result of executing the FLASHCPY QUERY RELATIONS command. Table 39 Information displayed by the FLASHCPY QUERY RELATIONS command Displayed item Displayed content Meaning FLASHCPY SEQUENCE 00000000 NUMBER Displays the sequence number. However, since Compatible FlashCopy does not support sequence numbers, "00000000" will be always displayed for this item. For details about the sequence number, see the IBM manual.
Table 39 Information displayed by the FLASHCPY QUERY RELATIONS command (continued) Displayed item Displayed content Meaning S T This volume is a TSE-VOL. F This volume is a normal volume. T When the command is issued to the S-VOL, the T-VOL is a TSE-VOL. F When the command is issued to the S-VOL, the T-VOL is a normal volume. If the command is issued to the T-VOL, the T-VOL is a normal volume or a TSE-VOL. T When a pool of the T-VOL becomes full, the relationship will be in FAILED State.
Table 40 Parameters for the ICKDSF command (REQUEST=FCQUERY) Parameter Value Description DEVN Device number Specifies the number (device address) of the device on which you want to perform the FCQUERY command. QRYSIZE Data length Specifies the length of data obtained with QRYINFO. 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.
Viewing resource information You can check status and other details related to your relationships and pairs in the following: • View license information on the Replications window. • Page 72 Viewing consistency group information You can check the number of consistency groups and the details and individual properties for consistency groups. • View the number of consistency groups in the Summary section on the Local Replication window.
Code Description 0016 2nd or LATER NOCOPY The relationship initially established by the Incremental FlashCopy function RELATIONSHIP ESTABLISHED (RESERVE was re-established by Reverse Restore in the NOCOPY mode. RESTORE) 0019 Explanation INITIALIZE STARTED (FC) Initialization processing began. 0020 COPY ENDED (FC) The background copy operation ended. 0022 RELATIONSHIP DELETED (FC) The relationship was deleted.
History window operation messages for FCSE Code Description Explanation 0050 NOCOPY RELATIONSHIP ESTABLISHED (FCSE) Creation of the FCSE relationship in NOCOPY mode completed. 0051 RELATIONSHIP DELETED (FCSE) The relationship was deleted. 0052 RELATIONSHIP DELETED with RELEASING ALLOCATED SPACE (FCSE) The relationship was deleted by FCWITHDR command and the allocated space was released.
• ANTRQST Macro • z/VM CP CAUTION: • Observe the following cautions about releasing relationships: A time-out may occur when more than 100 FlashCopy relationships are released at the same time. To avoid timeouts, divide the tasks into small groups and release relationships at intervals of about 5 seconds per 100 relationships. It is recommended that the number of relationships per volume should not exceed 4000, even though the maximum allowable number of relationships per volume is 65,534.
Table 42 Parameters for the FCWITHDR command (Compatible FlashCopy) (continued) Parameter Value Description NO Default setting. The relationships established on the copy target are all withdrawn. The relationship is not established when the copy target is online. XTNTLST Extent (range to withdraw the relationship) Specifies the extent (the range to withdraw the relation) the starting and ending addresses of the source and the starting and ending addresses of the target with CCHH.
Table 43 Results from FCWITHDR command (continued) Setting Parameter Results Set in COPY mode DDSW parameter set to YES The relationships established with the specified copy source extents on the volume specified by SDEVN are withdrawn after the background copy is completed.
The information specified by the XTNTLST or XXTNTLST parameter is supported only when the following conditions are fully met: • The information specified by the XTNTLST parameter must be for both the source and target. If the information specified by the XTNTLST parameter is only for one of the two, the copy operation results in an error. • The size of the specified copy source and target extents must be the same.
Case 2: TDEVN Specified, DDSW = NO, XTNTLST Parameter Specified 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. The following is an example of the command description for Case 2. This example requests the withdrawal of all the relationships established with the copy target extents included in the specified extents within the device numbered 4203.
Figure 31 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 is an example of the command description for Case 3: SDEVN and TDEVN: specified, DDSW = NO.
Figure 32 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 33 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: SDEVN and TDEVN: specified, DDSW = NO, XTNTLST specified. 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 34 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: SDEVN and TDEVN specified, DDSW=NO, XTNTLST specified. Therefore, the relation established with Dataset 1 is not withdrawn.
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. As a result, there are no longer any relationships established with the device numbered 4202 after executing this command.
Figure 36 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. The following example shows the instruction to resume the write operation to the volumes that belong to the CU with device number 4202: DEVN specified, ACTION = THAW.
Table 45 Parameters for the ICKDSF command (FLASHCPY WITHDRAW) (continued) Parameter Value Description command. If the OS of the host server is MVS, this parameter or the DDNAME parameter is required. TARGETVOL or TGTVOL CU number LDEV number Target device number Specifies the CU number, LDEV number, and device number (device address) of the T-VOL on which you want to perform the FLASHCPY WITHDRAW command. This parameter is required.
1. 2. 3. 4. If the OS of the host server is MVS, do one of the following: • Specify the JCL statement in the DDNAME parameter. • Specify the S-VOL device number of the relationship that you want to delete for the UNITADDRESS parameter. If the OS of the host server is VSE, specify the SYSNAME of the ASSGN system control statement in the SYSNAME parameter. In the TARGETVOL parameter, specify the CU number, LDEV number, and device number of the T-VOL.
Table 47 Parameters for the ANTRQST macro command (REQUEST=FCWITHDRAW) (continued) Parameter Value Description DEVN Device number Specifies the number (device address) of the device on which you want to perform the FCWITHDRAW command with ACTION parameter. ACTION THAW Resumes the write operation from the host to the volumes that belong to the same CU of the device specified by the DEVN parameter. RETINFO Return value Obtains the return code and the reason code of the execution results.
Table 48 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 50 Other requirements for Using FCSE Item Requirement Controller emulation type I-2107 Available volume Compatible FlashCopy can use volumes whose LDKC:CU:LDEV (LDKC: control unit image: logical device ID) is between 00:00:00 and 00:FE:FF. Use TSE-VOLs as target volumes. Creating TSE-VOLs for Compatible FlashCopy SE After you create a TSE-VOL, the volume is in the blocked status. To resolve this issue, you must format the LDEV after creating the TSE-VOL and then initialize the volume.
Item Setting for TSE-VOLs LDEV Name Enter the name of the TSE-VOLs to be created. You can enter up to the 32 characters including the initial number. • Prefix: Enter the alphanumeric characters that are the fixed characters of the head of the TSE-VOL name. The characters are case-sensitive. • Initial Number: Enter the initial number (up to 9 digits) following the prefix name. Option Select the options for the new TSE-VOLs: • In Initial LDEV ID, make sure that LDEV ID is set.
Even if the pool is in a 100% used state (area becomes insufficient), you can create a relationship in which the T-VOL is a TSE-VOL. However, when write processing is done to the S-VOL for the relationship in this situation, the relationship enters the Failed state.
Table 51 Parameters for the FCESTABL command (FlashCopy SE / Suspending write operations to S-VOLs) Parameter Value Description ACTION FREEZE Suspend the write operations from the host to S-VOLs. Although if you establish a relationship specifying extents, the ACTION parameter will suspend the write operation to the whole volume. The following example shows how to use the FCESTABL command to suspend write operations to an S-VOL when you establish a FlashCopy SE relationship.
Example 2 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 8 Result of FLASHCPY QUERY RELATIONS command Table 39 (page 69) 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 relationship 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.
Table 53 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 13 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 14 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 16 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 56 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 57 Differences between IBM FlashCopy and HP Compatible FlashCopy Compared item IBM FlashCopy HP Compatible FlashCopy GLOBAL Mirror status Supported. Not supported. For details about GLOBAL Mirror status, see the IBM manual.
Table 59 Comparison of copying processes (continued) Compared item IBM FlashCopy HP Compatible FlashCopy operation can be performed on the created by the Incremental FlashCopy function with relationship created by the Incremental NOCOPY specified or on the relationship after FlashCopy function with NOCOPY Restore or Reverse Restore is performed. specified or on the relationship after Restore or Reverse Restore is performed.
Table 59 Comparison of copying processes (continued) Compared item IBM FlashCopy HP Compatible FlashCopy Establishing a Cnt Ac-J Z pair in NOCOPY mode whose P-VOL is a Compatible FlashCopy relationship T-VOL that you establish in NOCOPY mode The operation used when relationship-creation fails in the remote site for Preserve Mirror FlashCopy Data can be copied from the Compatible FlashCopy relationship S-VOL to T-VOL but not to the Cnt Ac-J Z S-VOL.
Note: 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. For details about scratch operations, see the IBM manual.
FC Establish command • OPENDVCS • MODE (ASYNC) FC Query command • OPENDVCS • UNFORMAT FC Withdraw command • OPENDVCS • ACTION (COMMIT/REVERT) Compatible FlashCopy does not support the following parameters of ICKDSF commands: FLASHCPY WITHDRAW command • REVERT | COMMIT Compatible FlashCopy does not support the following parameters of ANTRQST commands.
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.
2. 3. 4. Moderate 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 mainframe 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.
Table 63 SIM (continued) Reference code SSB22 SSB23 SSB13 SIM type (byte 28) Importance level Description inaccessible because the power supply was turned on while the shared memory volatilized. 7F 110 F1 Troubleshooting 05 F1 Service Once either SIM=4B2xYY or SIM=4B4xYY is output, further output of either type of SIM is inhibited for five minutes. (For example, if SIM=4B4111 is output, SIM=4B4xYY is not output for five minutes, regardless of xYY.
7 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
HP websites For additional information, see the following HP websites: • http://www.hp.com • http://www.hp.com/go/storage • http://www.hp.com/service_locator • http://www.hp.com/support/manuals • http://www.hp.com/support/downloads • http://www.hp.
Table 64 Document conventions (continued) Convention Element Monospace text • File and directory names • System output • Code • Commands, their arguments, and argument values Monospace, italic text • Code variables • Command variables Monospace, bold text WARNING! CAUTION: IMPORTANT: NOTE: TIP: Emphasized monospace text Indicates that failure to follow directions could result in bodily harm or death. Indicates that failure to follow directions could result in damage to equipment or data.
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 The Replications window displays the local and remote replication summary information and provides access to the Compatible FlashCopy operations on Remote Web Console, such as viewing operation histories and setting the system options.
Replica LDEVs tab This tab displays Compatible FlashCopy/FCSE source and target volume information.
Setting fields Item Description Copy Type • FC Z/FCSE: Compatible FlashCopy and Compatible FlashCopy SE • BC: Business Copy • FS: Fast Snap • BC Z: Business Copy Z Histories table Item Description Date Operation date and time Source Volume Displays the following source volume information: • LDEV ID: LDEV identifier of the source volume • Provisioning Type, which can be one of the following: - Basic: Internal volume - THP: THP V-VOL - External: External volume - External MF: FICON® Data Migration vo
Edit Local Replica Option wizard Related topics • Page 61 • Page 117 • Page 118 Edit Local Replica Option window Use this window to change the Compatible FlashCopy system options. BC Z/Compatible FlashCopy/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.
Item Description 50%, background copy operations are suppressed, and consequently host I/O response improves. Status Enabled or Disabled: • Enabled: If you select a system option you want to enable, the Status column displays Enabled. • Disabled: If you select a system option you want to disable, the Status column displays Disabled. Confirm window for Edit Local Replica Options Use this window to confirm your changes to the Compatible FlashCopy system options.
SCP Time table Item Description CU CU number SCP Time (sec.) 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 Use this window to enter the desired SCP time. Information Setting area Item Description SCP Time SCP (state-change-pending) time set for each CU. The range is 0-518,400 seconds (6 days).
SCP Time table Item Description CU CU number SCP Time SCP (state-change-pending) time set for each CU. The range is 0-518,400 seconds (6 days).
Glossary allocation The ratio of allocated storage capacity versus total capacity as a percentage. Allocated storage refers to those logical devices (LDEVs) that have paths assigned to them. Allocated storage capacity is the sum of the storage of these LDEVs. Total capacity is the sum of the capacity of all LDEVs on the disk array. BC P9000 or XP Business Copy. An HP application that provides volume-level, point-in-time copies in the disk array.
to be associated with 1 to 36 LDEVs. Essentially, LUSE makes it possible for applications to access a single large pool of storage. M-VOL Main volume. MCU Main control unit. OPEN-x A general term describing any of the supported OPEN emulation modes (for example, OPEN-E). There are two types of OPEN-x devices: legacy OPEN-x devices with a fixed size (such as OPEN-3, OPEN-8, OPEN-9, and OPEN-E), and OPEN-V, which has a variable size and is a CVS-based volume.
Index A O ANTRQST, 52 on-demand copying, 10 B P background copying, 9 pairs history, 72 C consistency group, 12 contacting HP, 111 conventions document, 112 storage capacity values, 112 text symbols, 113 COPY mode, 9 R D service information message, 108 SIM, 108 storage capacity values conventions, 112 subscription service, HP, 111 symbols in text, 113 dataset copying, 11 document conventions, 112 related information, 111 documentation HP website, 111 providing feedback, 111 E extent, 8 F Fast
