HP StorageWorks Hitachi TrueCopy for z/OS user guide HP XP12000 Disk Array HP XP10000 Disk Array HP 200 Storage Virtualization System This guide explains how to use Hitachi TrueCopyTM software to pair data volumes on local and remote XP storage systems and to recover data from the remote system after a local disaster.
Legal and notice information Copyright 2005, 2009 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 Hitachi TrueCopy z/OS for HP XP12000/XP10000 and SVS 200 storage systems . . . . . 13 Hitachi TrueCopy features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other data duplication Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP XP Business Copy and Hitachi ShadowImage z/OS (SI390) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Accessing TrueCopy M-VOLs and R-VOLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Cache, NVS, and DASD Fast Write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Consistency groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Restrictions on volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Asynchronous operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To perform asynchronous operations: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing consistency group status (CT Group Status) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To display the consistency group status information: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Point-in-Time (PiT) data duplication using TrueCopy Asynchronous . . . . . . . . . . . . . . . . . . . . . . . To produce a PiT duplicate of an existing TC390A consistency group: . . . . . . . . . . . . . . . . . . Powering off/on TrueCopy components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planned outage of the MCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Change pair options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting a pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Getting pair status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selecting devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 10 TrueCopy main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 TrueCopy main window (Pair Operations window) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 List on the Pair Operations Panel . . . . . . . . . . . . . . . . . . . . .
83 84 85 86 87 Tables 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 Current load balancing control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Combination 1: MODE 85,86 = ON,OFF; Threshold 1/2/3 = 30/40/50% . . . . . . . . . . . . . . . . . Combination 2 (Default): MODE 85,86 = OFF,OFF; Threshold 1/2/3 = 40/50/60%. . . . . . . . . . .
53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 12 Script components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Script file requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Script symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example of CreateHrcPair parameters . . . . . . . . . . . . . . . .
1 Hitachi TrueCopy z/OS for HP XP12000/XP10000 and SVS 200 storage systems Hitachi TrueCopy features Hitachi TrueCopy (TC390) creates and maintains remote copies of the S/390 data stored on HP XP12000/XP10000 and SVS 200 storage systems for data duplication, backup, and disaster recovery purposes. TC390 provides synchronous and asynchronous copy modes to accommodate a wide variety of user requirements and data copy/movement scenarios.
Other data duplication Features In addition to TC390, the XP12000/XP10000 storage system provides several other data duplication features that are described below. For more information about these features, contact your HP account support representative. HP XP Business Copy and Hitachi ShadowImage z/OS (SI390) You can use HP StorageWorks XP Business Copy (BC) Software and SI390 data duplication features to set up and maintain multiple copies of logical volumes within the same XP12000/XP10000.
NOTE: The HXRC option is only required for the 2105 or 2107 CU emulation type. You can use HXRC for the 3990 controller emulation type without enabling the HXRC option. If you use HXRC with FICON, carefully set the path configuration. See Table 1. Table 1 HXRC path configuration with FICON Application Site Path (System - DKC) Record Set Transfer Path (System Data Mover - DKC) For Use ESCON ESCON No ESCON FICON Supported FICON ESCON Not Recommended1 FICON FICON Supported 1.
• TC390 volume pair status and suspend types (see page 35) • PPRC support, including P/DAS and GDPS (CGROUP) operations (see page 40) Components TC390 operations involve the XP12000/XP10000 (and/or other XP disk arrays) at the main and remote sites, the physical communications paths between the main and remote disk arrays, and the XP Command View Advanced Edition Software server or XP Remote Web Console. The main and remote disk arrays must have the same controller emulation.
Figure 2 TrueCopy components for Fibre Channel connection XP12000/XP10000 storage systems TC390 operations involve the main (primary) disk arrays and the remote (secondary) disk arrays. This chapter covers TC390 operations in which the main disk array is an XP12000/XP10000 and the remote disk array is an XP12000/XP10000 or other XP disk array. The main disk arrays contain the TC390 main volumes (M-VOLs), which contain the original data and are online to the host(s).
NOTE: This mode information was current at the time of publication of this document, but it may change. Contact your HP account support representative for the latest XP12000/XP10000 SVP system option mode information. XP12000/XP10000 performing TC390A operations (main and remote) use sidefiles in cache for storing the TC390A recordsets. HXRC also uses cache sidefiles. Disk arrays performing TC390A and/or HXRC must have sufficient cache installed to handle the increased sidefile usage.
Table 3 XP12000/XP10000 modes for TrueCopy for z/OS (continued) Mode Description 93 Graduated delay process for sidefile control (see ”Graduated delay sidefile management” on page 32): Mode 93 OFF (default) = strong delay type Mode 93 ON = soft delay type Amount of sidefileStrong delay typeSoft delay type threshold – [15-20%] (HWM)100 ms x 1 time20 ms x 1 time threshold – [10-15%]200 ms x 1 time40 ms x 1 time threshold – [5-10%]300 ms x 1 time60 ms x 1 time threshold – [0-5%]400 ms x 1 time80 ms x 1 time
Table 3 XP12000/XP10000 modes for TrueCopy for z/OS (continued) Mode Description 118 TC390A – SIM notification when the TC390A sidefile reaches high-water mark (HWM = sidefile threshold - 20%) (see mode 93). Mode 118 ON: Generate SIM. Mode 118 OFF (default): No SIM generated. NOTE: 308 The reported SIM when this mode is ON is not reported per CLPR. Allows you to select whether the Remote Copy Path status, SIM218x, will be reported to the host or not. Mode 308 ON: SIM218x will be reported to the host.
The MCU and RCU can be defined separately for each TC390 pair. The XP12000/XP10000 CU can function simultaneously as an MCU for one or more M-VOLs and as an RCU for one or more R-VOLs, provided the remote copy connections and ports are properly configured. The XP12000/XP10000 CU provides up to 32 logical CU images. TC390 operations can be performed on all logical devices (LDEVs) in all logical CU images. You can use TC390 to select a CU image in the connected MCU and specify a CU image in the RCU.
CAUTION: Do not use M-VOLs or R-VOLs from hosts that have different CU emulation types (2105 or 2107, and 3990) at the same time. If you use the M-VOLs or R-VOLs from the 2105 or 2107 and 3990 hosts simultaneously, an MIH message might be reported to the 3990 host. Remote copy connections The remote copy connections are the physical paths used by the TC390 MCUs to communicate with the TC390 RCUs.
Table 4 TC390 configuration with FICON (continued) Application Site Path (System - DKC) MCU-RCU For Use FICON ESCON Not Supported1 FICON Fibre Channel Supported 1. The configuration of FICON for channel-MCU paths and ESCON for MCU-RCU paths is not supported, because the bandwidth of FICON is greater than that of ESCON interface. If FICON is used for channel-MCU paths, use Fibre Channel interface for the MCU-RCU paths.
Two or more RCPs must be configured before you can add the RCUs and establish the TC390 volume pairs. The RCPs cannot communicate with the host processor channels and are dedicated to TC390 operations. The host channel interface paths must be connected to the other serial interface ports on the disk array. Also, the serial interface ports, 1S-1Z and 2S-2Z, cannot be specified as RCPs. The CHA package port that is added to DKA slot cannot be specified as RCPs.
When TC390 is used as a data migration tool, ERC is recommended but is not required. When TC390 is used as a disaster recovery tool, ERC is required to ensure effective disaster recovery operations. When a TC390 pair is suspended due to an error condition, the MCU generates sense information, which results in an IEA491E system console message. This information should be transferred to the remote site through ERC for effective disaster detection and recovery.
its associated update copy operation at the RCU are complete. For synchronous mode, the MCU starts the update copy operation when it receives one of the following: • The last write command in the current domain, specified by the preceding locate record command. • A write command that requires switching to the next track. • A write command that was not preceded by a locate record command.
R-VOL read option For additional flexibility, TC390 offers a special R-VOL read option. The HP representative enables the R-VOL read option on the RCU (mode 20). You can use the TC390 R-VOL read option to read a TC390 R-VOL only while the pair is suspended, without having to delete the pair. The RCU will change only the VOLSER of the suspended R-VOL so that the R-VOL can be online to the same host as the M-VOL while the pair is suspended. All other write I/Os will be rejected by the RCU.
Table 6 Maximum Pairs by Emulation Type, when pairs are created without custom volumes Emulation Type Number of Cylinders Number of Bitmap Areas Maximum Number of Pairs Maximum Number of Pairs (Added Shared Memory: 1 set) (Added Shared Memory: 2 sets) 3380-K 2,655 1 11,605 16,384 3380-3 3,339 1 11,605 16,384 3390-1 1,113 1 11,605 16,384 3390-2 2,226 1 11,605 16,384 3390-3 3,339 1 11,605 16,384 3390-9 10,017 2 5,802 14,335 3390-L 32,760 5 2,321 5,734 3390-M 65,520
CAUTION: If the type of difference management is set to "Auto", "Track" or "Cylinder" will be set automatically according to the number of cylinders of a volume that a pair will be created with. If VLL has been used, the number of cylinders that you set with VLL software is applied. If the volume that you want to create a pair with has 10,019 or more cylinders, "Cylinder" will be set. If the volume has less than 10,019 cylinders, "Track" will be set.
NOTE: The MCU does not remove the sidefile entry for a recordset from its cache until it receives an I/O completion signal (device end) from the RCU. This is true even if the MCU and RCU are connected through a channel extender product. If a recordset is lost in transmission from the MCU to the RCU, the MCU’s cylinder bitmap ensures that the missing recordset is identified and resent to the RCU.
MCU power-off sequence is initiated, and also maintain sequence numbers in periods of low host activities. Figure 4 Selecting and settling TrueCopy Async recordsets at the RCU Inflow control of recordsets As described in the previous sections, both the MCU and RCU create sidefiles for storing TC390A recordsets. Because the sidefiles occupy exclusive space in cache, both the MCU and RCU perform inflow control to prevent an overload of the disk array’s cache resources.
• Inflow control by RCU: If the RCU is not able to settle a recordset within the user-specified offloading timer value, the RCU suspends all TC390A volume pairs and resets the channel-command-retry condition to avoid hanging up the MCU. HXRC. HXRC operations use a different cache sidefile than TC390A. Table 8 on page 32 also shows the sidefile threshold values for HXRC operations and describes the actions that occur when each threshold is reached.
NOTE: If there is a network problem, lack of bandwidth, or lack of sufficient Fibre links, the sidefile will grow and the microcode will add delay to host I/O until the sidefile goes below a certain level again. Disabling this function will cause the pairs to suspend. SIM reporting for TC390A sidefile conditions is enabled only when SVP system option mode 118 or 464 is ON (see Table 3 on page 18). The reported SIMs when SVP system option mode 118 or 464 is ON, however, do not support a CLPR.
Timer Type. This group option determines how the MCU will acquire the time-stamp for the TC390A recordsets: • System. When the System timer option is selected, the MCU acquires the time-stamp information for each recordset as follows. When a TC390A pair is established, the MCU reports state-change-interrupt (SCI) to all hosts.
Group operations TC390A provides the following group-based operations to simplify and expedite disaster/failure recovery procedures: • Group operations at the MCU: • Suspend all pairs in a consistency group. For a description of the TC390A Group suspend option (supported by CSUSPEND TSO command), see ”Suspending TrueCopy pairs (Suspend Pair)” on page 131. • Resume all suspended pairs in a consistency group.
simplex, and the MCU detects the pair deletion (if the path status is normal) and changes the M-VOL status to suspended. TC390A-specific pair status The TC390A suspending and deleting transitional states occur when a request to change TC390A pair status has been accepted, but the change to the requested status (suspended or simplex) is not yet complete. These states are not reported to the host. In the case of suspending, both the user and the MCU can request the status change.
Table 9 TrueCopy volume pair status (continued) Pair Status Description Deleting This pair is not synchronized. This pair is in transition from duplex, pending duplex, or suspended to simplex. When the delete pair operation is requested (by user), the status of all affected pairs changes to deleting. When the delete pair operation is complete, the status changes to simplex. SEQCHK The RCU encountered a non-time-stamped recordset for a TC390A pair using the System timer type option.
NOTE: If you need write access to an R-VOL, you must delete the pair. Table 10 Suspend types 38 Suspend Type Applies to Description M-VOL by operator M-VOL (TC390 Sync only) The user suspended the pair from the MCU using the M-VOL Failure option. The R-VOL suspend type is by MCU. R-VOL by operator M-VOL, R-VOL The user suspended the pair from the MCU or RCU using the R-VOL option. by MCU R-VOL The RCU received a request from the MCU to suspend the volume pair.
Table 11 Consistency status for suspended TrueCopy Async R-VOLs Consistency Status Description Volume This TC390A volume pair was probably suspended alone. Update sequence consistency between this R-VOL and other R-VOLs in this consistency group is not ensured. This R-VOL cannot be used for disaster recovery at the secondary system.
following records are marked in the cylinder bitmap as modified (to be copied during the resume pair operation): • The recordsets that were created by the MCU but not yet sent to the RCU. After marking these cylinders as modified, the MCU discards these recordsets. • The recordsets that were sent to the RCU but not acknowledged by the RCU. The MCU marks these M-VOL cylinders as modified and discards these recordsets.
• You cannot use the PPRC commands to: Change the RCU options. The current default values are: minimum paths = 1, max. initial copy activity = 4, SCP delay time = 120 seconds, incident of RCU = to any host, PPRC support = yes, remote copy service SIM = not report, RIO MIH Time = 15 seconds. The TC390 software must be used to change these options. Change the TC390 async options. The current default values are: sidefile threshold = 50%, offloading timer = 5 minutes.
Mode 104 must be ON for 3990 controller emulation (not valid for 2105 and 2107 emulation). For more information on XP12000/XP10000 SVP system option mode related to TC390 operations, see Table 3 on page 18. Mode 104 must be set before any TC390 pairs are established in a GDPS environment.
Table 13 SAID Values for LINK Parameters (ports) of RMF PPRC Link-path Statistical Information (FRONT CL1) Package Location Port SAID* Package Location Port SAID* Package Location Port SAID* Package Location Port SAID* 1F CL1-E X'0010' 1H CL1-N X'0030' 1L CL9-J X'0060' 1A CL9-A X'0040' (Add1) CL3-E X'0011' (Add3) CL3-N X'0031' (Add5) CLB-J X'0061' (Add7) CLB-A X'0041' CL5-E X'0014' CL5-N X'0034' CLD-J X'0064' CLD-A X'0044' CL7-E X'0015' CL7-N X'0035' CLF-J
Table 14 SAID Values for LINK Parameters (ports) of RMF PPRC Link-path Statistical Information (REAR CL2) Package Location Port SAID* CL6-D Package Location Port SAID* X'008E' CL6-M CL8-D X'008F' 2R CL2-E X'0090' (Add1) CL4-E X'0091' CL6-E Package Location Port SAID* X'00AE' CLE-R CL8-M X'00AF' 2U CL2-N X'00A0' (Add3) CL4-N X'00B1' X'0094' CL6-N CL8-E X'0095' CL2-F Package Location Port SAID* X'00FE' CLE-H X'00DE' CLG-R X'00FF' CLG-H X'00DF' 2X CLA-J X'00E0'
NOTE: Other XP disk arrays with TC390 installed can be used as an RCU connected to an XP12000/XP10000 MCU. For assistance with mixed disk array configurations, contact your HP account support representative. TC390 can coexist with XP Continuous Access (all copy modes) in the same XP12000/XP10000. Full Fibre Channel support will allow concurrent fibre-mode XP Continuous Access and TC390 operations.
NOTE: Administrator access to the XP Command View Advanced Edition Software server or XP Remote Web Console is required to perform TC390 operations. Users without administrator access can only view TC390 information. NOTE: You must operate XP Remote Web Console in Modify mode to perform TC390 operations. Users in view mode can only view TC390 information.
CAUTION: If the volumes that will become TC390 R-VOLs are physically attached to the same system images as the production volumes that will become the TC390 M-VOLs, the following problems can occur: • When a TC390 pair is established using the TSO CESTPAIR command, the secondary volume might be online. PPRC allows this, but TC390 does not (see the following note). This could produce a duplex secondary online to a host image, the results of which are not predictable.
Accessing TrueCopy M-VOLs and R-VOLs Write operations to a TC390 M-VOL that specify normal authorization are duplicated on the R-VOL of the TC390 pair. Write operations with diagnostic or device support authorization, such as ICKDSF, are completed at the M-VOL but are not duplicated at the R-VOL. Therefore, you must suspend a TC390 volume pair before performing ICKDSF media maintenance on the M-VOL.
Installing the TrueCopy hardware Initial installation of the TC390 hardware is planned and performed by the user and the HP representative. To install the hardware required for TC390 operations: 1. User: Identify the TC390 M-VOLs and R-VOLs (main and remote volumes) so that the TC390 hardware can be installed and configured properly. 2.
use single-mode longwave optical fibre cables, fibre cables up to 30 km in length and up to two switches are required for distances greater than 10 km. TC390 operations can be performed at distances of up to 30 km (18.6 miles) using standard single-mode longwave support. Long-distance solutions are provided using approved channel extenders and communication lines.
• N port: Fab on, Point-to-Point Figure 8 Fibre Channel interface switch connection (FL port or F port) • Extender connection: Channel extenders and switches are used to connect the devices across large distances.
support. Long-distance solutions are provided, based on user requirements and workload characteristics, using approved channel extenders and communication lines. Figure 10 Serial remote copy connection configurations The ESCDs can accommodate multiple MCU-RCU remote copy connections.
NOTE: 1-to-n configurations (one main disk array and multiple remote disk arrays) are valid for TC390A, as long as a consistency group does not span remote disk arrays. In addition, the ESCDs can accommodate channel-to-MCU and channel-to-RCU connections in addition to the remote copy connections.
NOTE: At this time serial interface and Fibre Channel interface configurations cannot coexist for the same MCU. Future support is planned. Serial interface connection is not supported for this version. Serial interface configuration To configure the MCUs and RCUs for serial-interface TC390 operations: 1. Identify the volumes that will become the TC390 M-VOLs and R-VOLs.
Then register the consistency group to the MCU as shown in the following figure. For additional instructions, see ”Adding consistency groups (Add CT Group)” on page 105. Figure 15 Adding the consistency groups 7. When you are finished configuring this MCU, exit the TrueCopy main window and close XP Command View Advanced Edition Software or XP Remote Web Console. 8. Repeat step 2 - step 7 for each disk array that will function as a TC390 MCU.
5. Register the RCU(s) to the current MCU CU image using the Add RCU window. Figure 16 Add the RCUs Set the options for the registering RCU using the RCU Option window as shown in the following figure. For additional instructions, see ”Registering an RCU (Add RCU)” on page 87.
6. If you plan to create TC390A pairs with M-VOLs in this MCU, configure the MCU async options as shown in the following figure. For additional instructions, see ”Asynchronous copy option” on page 108. Figure 18 Setting the Async options Then register the consistency group(s) to the MCU as shown in the following figure. For additional instructions, see ”Adding consistency groups (Add CT Group)” on page 105. Figure 19 Adding the consistency groups 7.
Table 15 1You cannot create the TC390 pair if you enable the transfer of the host I/O time stamp from M-VOL to R-VOL.
Table 15 Using Non-TC390 and Non-TC390A Volumes as TC390 and TC390A Volumes (continued) Source volume (when volume migration is in progress) Yes Yes Yes Yes Note: If the source volume is used as M-VOL, the volume migration will stop. Note: If the source volume is used as R-VOL, the volume migration will stop. Note: If the source volume is used as M-VOL, the volume migration will stop. Note: If the source volume is used as R-VOL, the volume migration will stop.
Table 15 Using Non-TC390 and Non-TC390A Volumes as TC390 and TC390A Volumes (continued) No No No No No No No No No Secondary data volume in Suspend status Yes No No No Secondary data volume in Swapping status Yes No No No Secondary data volume that is suspended due to a failure Yes No No No No No No No Volume with Read/Write attribute Yes Yes Yes Yes Volume with Read Only attribute Yes Yes Yes Yes Volume with Protect attribute No No No No Yes Yes Yes Yes No N
Table 15 Using Non-TC390 and Non-TC390A Volumes as TC390 and TC390A Volumes (continued) Cache Residency Manager Cache Residency Manager volume Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Compatible PAV for Mainframe Compatible PAV for Mainframe volume Virtual LVI Virtual LVI volume NOTE: When TC390A, XP Continuous Access and Hitachi Universal Replicator coexist in the same XP12000/XP10000 disk array, TC390A pairs, XP Continuous Access pairs and Hitachi Universal Replicator pairs cannot b
NOTE: When TC390 and XP Continuous Access coexist in the same XP12000/XP10000, each consistency group must contain either TC390A pairs or XP Continuous Access Asynchronous pairs (not both), and TC390A and XP Continuous Access Asynchronous share the same cache sidefile area. Combining TC390 and HXRC. The following table shows the requirements and restrictions for combining TC390 and HXRC operations on the same XP12000/XP10000 device.
Table 17 Host pair status reporting for TrueCopy/ShadowImage shared volumes (continued) Number of TC390 Pairs Number of SI390 T-VOLs Pair Status Reported by XP12000/XP10000 0 2 or more ShadowImage pair status for the pair whose T-VOL has the lowest LDEV ID 1 0 TC390 pair status 1 1 TC390 pair status 1 2 or more TC390 pair status Table 18 Data currency of a shared TrueCopy/ShadowImage volume TC390 Pair Status ShadowImage Pair Status Pending Duplex Duplex Split-Pending Split Resync Suspen
• Use SI390 to provide on-site backup copies of TC390 M-VOLs and R-VOLs. Figure 22 TrueCopy and ShadowImage: shared M-VOL/S-VOL and R-VOL/S-VOL The following figure shows an example of a volume functioning as both a TC390 M-VOL and an SI390 T-VOL. NOTE: This configuration does not allow SI390 and TC390 to copy at the same time. Create the SI390 pair first, and then split the pair before creating the TC390 pair. You must suspend the TC390 pair to resync the SI pair.
Combining TrueCopy for z/OS and XP External Storage Software Using HP StorageWorks XP External Storage Software, you can assign external volumes to the TC390 M-VOL or R-VOL. When the write operation is executed to the TC390 M-VOL to which the external volume is assigned, the cache mode is always enabled regardless of the enabled or disabled setting. For further information on external storage, see the HP StorageWorks XP External Storage user guide: HP XP12000 Disk Array, HP XP10000 Disk Array.
• Adding/deleting logical paths to an RCU • Adding/deleting SSIDs for an RCU • Viewing RCU status • Deleting RCUs Asynchronous operations. The TC390A control operations (see ”Asynchronous operations” on page 102) configure the TC390A groups and options: • Setting the async options • Adding consistency group • Viewing consistency group status • Changing the consistency group options • Changing the async options • Deleting consistency groups Usage Monitor operations.
The following table shows the TC390 functions of each tab. The function menus can be displayed by right-clicking the list. To apply the settings you made on the TC390 function tabs, click Apply. Table 19 TC390 functions Tab Menu Command Description Pair Operations Pair Status Displays the CU information, path information, pair status, and settings information of the TC390 pairs. Add Pair > Synchronous Sets new TC390 Synchronous pairs. Add Pair > Asynchronous Sets new TC390A pairs.
Table 19 TC390 functions (continued) Tab Menu Command Description History Operations - Displays the operation history of TC390 volume pairs. Other Operations Clear SIM Clears all the remote copy SIMs. The following sections describe the configuration of each tab and how to use the tabs to operate the TC390 functions (see ”Performing TrueCopy pair operations” on page 120 for TC390 volume pair configuration).
The Volume list displays information for each volume of the connected disk array (see ”Volume list” on page 69). The information displayed in this list is sorted in the order of the Device number by default. The information for the volumes, which are defined for several paths, are displayed in several rows as many as the path defined. The Display Filter button opens the Display Filter window (see ”Display filter” on page 70), which you can use to select the volumes displayed on the Volume list.
• OFF: Suspended by the PS OFF by the MCU. • S/N and SSID of the other disk array (MCU or RCU) of the volume pair. • CU number of the other volume of the volume pair. NOTE: If “#” is added to the end of LDEV number (i.e. 00:3C#), the LDEV that the LDEV number indicates is an external volume. If the pair is created with TrueCopy for z/OS of the microcode program version 50-03-6x-xx or earlier, “#” is not added. For details on an external volume, see Hitachi HPAV for z/OS user guide.
NOTE: You cannot use other windows without closing the Display Filter window. a Figure 27 Display Filter window Use the CU# list to specify the number of the CU to be displayed. Use the CT Group list to specify the number of the consistency group to be displayed. This specification is available only for the Asynchronous pair. Use the Type list to specify the pair type, synchronous or asynchronous. Use the M-VOL/R-VOL list to specify the Volume type, M-VOL or R-VOL.
NOTE: If # is added to the end of an LDEV number, such as 3F#, the LDEV is an external volume. For more information about external volumes, see Hitachi HPAV for z/OS User Guide. To create a TC390 Snapshot file: 1. Click Display Filter to display the Display Filter window. 2. Select the options you want in the Display Filter window and close the window. 3. From the Pair Operations window, right-click to display the pop-up menu and click Snapshot. A confirmation dialog box is displayed. 4.
The RCU Operations window is updated when the tab is switched from one to another, when the Refresh button ( ) is clicked, and when the settings for the RCU are applied. For the RCU settings operation, see ”RCU operations” on page 82. Figure 29 RCU Operations window The Display buttons switch the contents of the tree and the list. Clicking MCU&RCU displays the CU Number tree and the MCU/RCU list (see ”CU Number tree and MCU/RCU list” on page 73).
In the CU Number tree, the CU number can be selected to display the specified information in the MCU/RCU list. You can select only one CU number on the CU Number tree. Figure 30 RCU Operations window with the MCU&RCU option button selected • CU#: CU number that is selected on the tree. • Type: MCU ( ) or RCU ( ). • S/N and SSID: Serial number and SSID of the other CU of the pair. • Paired CU#: CU number of the other CU of the pair.
Port tree and port list Clicking Port in the Display box displays Port tree and the Port list. The Port tree displays the channel adapters and the port types. Only the ports that are installed and can be selected for remote copy operations are displayed. Figure 31 RCU Operations window with the Port option button selected • Port: Cluster and port number (CL1-A to CL2-R). • Type: Port type (Initiator, Target, RCU Target, External, Internal/Exernal).
Figure 33 High-speed (2 port), two ports per row Figure 34 High-speed, four ports per row In the Port tree, the port type can be selected to display the specified information in the Port list. For example, when RCU Target is selected in the Port tree, the system looks for ports of Initiator from all the ports entered and lists the RCU Target ports in the Port list as shown in the following figure. Only one Port type can be selected in the tree.
Pending Update Data Rate is always displayed and shows the maximum cache % available for use by TC390 Async sidefiles. Offloading Timer indicates the maximum time between TC390 Async recordset transfers. Display All is selected in the Consistency Group tree when the Asynchronous Operations window is displayed. All consistency groups (00-7F) are listed in the Consistency Group list.
NOTE: You must use XP Command View Advanced Edition Software or XP Remote Web Console in Modify mode to perform TC390 operations. Users in view mode can only view TC390 information. Figure 36 Usage Monitor window The Usage Monitor window displays the following information: • Status: Displays Running when monitoring is on and displays Stop when monitoring is off. When monitoring is stopped, the usage monitor graph is closed. The usage monitor graph can only be displayed when monitoring is running.
CAUTION: Do not perform TC390 operations using the Pair Operations window while the scripting function is being executed. To perform TC390 operations on the Pair Operations window, wait until the script is complete, or verify that the script in execution is aborted. NOTE: The script file must be transferred to the SVP before executing the script. Clicking the Script Operations tab displays the Script Operations window, which shows information for the script being executed.
error in the script file, the message, which indicates the abnormal end, is displayed. When the script is stopped by the Stop command, Abort by operator is displayed. • Date: The date when the script status changed. • Line: The script file line number being executed. • Loop: The current/total repetition count for a looped command (for example, 150/300). • Macro: The macro being executed.
The History Operations window is updated when the Refresh button ( ) is clicked. The information on the History Operations window is not updated by clicking another tab and then clicking the History Operations tab again. Figure 39 History Operations window The History Operations window contains the following information: • Status displays the current status of the history file: • No history file exist. The history file does not exist. • Reading a history failed.
History information older than seven days is automatically deleted. However, if the number of operations exceeds 65,535, the oldest operations are deleted in chronological order to keep the number at 65,535, even if the operations occurred within the last week. The history file always contains the most recent operations up to a maximum of 65,535 operations. The maintenance information for an entire week may not always be available.
• Modifying the RCU options (see page 90) • Deleting RCUs (see page 97) • Adding and deleting logical paths to an RCU (see page 97) • Adding and deleting SSIDs for an RCU (see page 100) • Modifying parameters and omitting selected settings (see page 101) From the RCU Operations window (see page 72), you can perform the RCU operations. All the operations that can be performed from the RCU Operations window have a common procedure. To perform the RCU operations from the RCU Operations tab: 1.
• RCU target: The Fibre Channel ports in the RCU that will be used to communicate with the MCUs must be configured as RCU target ports. • External: This attribute can be set by the Universal Volume Manager software. The external port is used for Universal Volume Manager, not TrueCopy for z/OS. To use this port for TrueCopy for z/OS, change the attribute to the initiator, RCU target or target port.
Viewing RCU Status (RCU Status) Use the RCU Status command to display the RCU status information. To display the RCU status information: 1. Click MCU&RCU in the Display box. 2. From the CU Number/Port tree, select a CU number that includes the RCU that you want to display the status information. 3. From the MCU/RCU list, select an RCU and right-click to display the pop-up menu. Figure 41 MCU/RCU list with the RCU Status command 4. Click RCU Status from the pop-up menu. The RCU Status window is displayed.
NOTE: If you select more than one RCU in step 2, only RCU Operation can be clicked from the pop-up menu. Select one RCU in step 2 to display the status information. Figure 42 RCU Status window • Path list: • No.: Path number (serial number of the list). • Path Status: Path status. Normal is displayed when the path status is normal. • MCU Port number and RCU Port number. When the channel type is serial, the link address is listed on the RCU Port column. • RCU S/N: Serial number of the RCU.
• Last Updated: The date and time when the RCU is last updated. • SCP Time: State-Change-Pending (SCP) time. • FREEZE Option: Support for the CGROUP (FREEZE/ RUN) PPRC TSO command. • The Refresh button refreshes the information displayed on the window. The Close button closes the window. The Path Status box lists the path status and the following table describes each status. For troubleshooting information about MCU-RCU paths, see ”General TrueCopy troubleshooting” on page 151.
NOTE: If four RCUs (the maximum number of RCUs you can register) have already been registered, the Add RCU command cannot be selected. Figure 43 Add RCU windows (Fibre and Serial) Use the RCU S/N, Controller ID, and Logical Adr. (RCU CU#) boxes to enter the serial number, Controller ID (subsystem family ID), and CU number of the RCU being registered. S/N is in five-digit and CU number is 0-1F. For the Controller ID (for Fibre port type), enter “2” for an XP48/XP512 or “3” for an XP12000/XP10000.
4. From the MCU/RCU list on the RCU Operations window, right-click to display the pop-up menu. For registering RCU operation, the RCU does not have to be selected on the list. 5. From the pop-up menu, click RCU Operation and then click Add RCU (see Figure 44). The Add RCU window is displayed. Figure 44 MCU/RCU list with the RCU Operation command 6. From the Add RCU window, enter the S/N of the RCU and the Controller ID, CU number, and SSID(s) for the CU image.
RCU path parameters For serial channel interface, the RCU path parameters are similar to the channel path definitions in the I/O configuration dataset (IOCDS). In the IOCDS, a logical path is specified with a subchannel number, link destination address, and logical address for the CU. TC390 uses the “port” parameter instead of the subchannel number to specify the MCU’s port. For the XP12000/XP10000, the logical address must correspond to the CU number.
Figure 46 Add RCU window – serial interface For Fibre Channel interface, two types of Fibre Channel ports are provided: 4-port and 2-port adapters. The port mode depends on the port type. Also, each port may have a different PCB mode setting (Standard or High). Therefore, when you configure paths among the initiator ports, target ports, and RCU target ports, study the port modes and specify the correct mode for each port.
Figure 48 Add RCU window – FC interface Modifying RCU options (Change RCU option) Use the RCU Option window to set the RCU options for the connected MCU. The RCU options apply to all MCU CU images and to all RCUs connected to the MCU.
add RCU process, and can also be opened by right-clicking on the RCUs and clicking RCU Operation > Change RCU Option. Figure 49 RCU Option window (Change RCU Option) Use the Minimum Paths option to specify the minimum number of paths required for each RCU connected to the current MCU. You can specify 1, 2, 3, 4, or 8 for this option.
storage overload (see ”Inflow control of recordsets” on page 31). Make sure to set the SCP delay time after you have added all MCU-RCU paths. NOTE: SCP Delay Time of TrueCopy for z/OS and the state-change-pending time of FlashCopy Mirror Version 2 are same. To determine the SCP Delay Time of TrueCopy for z/OS, take into account the fact that if you change the SCP Delay Time setting by the CU Option panel, the state-change-pending time of FlashCopy Mirror Version 2 will change.
If you select Disable, the MCU will reject the CGROUP command. Enable the FREEZE option only after all MCU-RCU paths have been added. The Round Trip Time setting is used for Initial Copy operations. This setting gives a priority to a remote I/O for an update copy operation.
values: the initial copy pace, the max number of initial copy VOLs, the speed of the line between MCU and RCU, and the number of lines. Initial Copy response time (ms) = (1[MB]/“Speed of line between MCU-RCU[MB/ms]”1) x (“initial copy pace”2/15) x (“max number of initial copy VOLs”3/“Number of lines between MCU-RCU”4) 1. 2. 3. 4. When you connect MCU with RCU without lines etc., specify 0.17[MB/ms] in “Speed of line between MCU and RCU.” For “initial copy pace” in the formula above, see Table 21.
To modify the RCU option: 1. From the CU Number tree on the RCU Operations window, verify the correct CU image is selected. 2. From the MCU/RCU list on the RCU Operations window, select RCU whose options you want to modify. 3. Right-click to display the pop-up menu, click RCU Operation, and then click Change RCU Option. The RCU Option window is displayed. 4. From the RCU Option window, modify the RCU options. When the RCU Option window is opened, all the boxes display the current settings.
When the Add Path command is selected, the Add Path window is displayed. Use the Add Path window to set the path(s) to an RCU. Figure 50 Add Path window (for Fibre) The MCU-RCU Path box includes: • The MCU Port boxes, which you use to enter the MCU port number. The Initiator and the RCP are listed in the list and can be selected. • The RCU Port boxes, which you use to enter the RCU port number. The RCU Target port must be specified. • The Link Address boxes, which you use to enter the Link Address.
3. Right-click to display the pop-up menu, click Edit SSID(s) & Path(s), and then click Add Path (see Figure 51). The Add Path window is displayed. Figure 51 Opening the Add Path window 4. From the Add Path window, enter the new path(s). 5. Click Set in the Add Path window to set the paths. The list changes to the Path Settings Parameter list. NOTE: The options can be modified and/or canceled after you have set them. See ”Modifying parameters and omitting selected settings” on page 101. 6.
Adding and deleting SSIDs for an RCU (Add SSID and Delete SSID) Before adding an SSID, verify that the remote copy connection is properly installed. You can add three SSIDs to each RCU. Before deleting an SSID, verify the remaining SSIDs are still valid, or the connection between the MCU and RCU may be lost. When the Add SSID command is selected, the Add SSID window is displayed. Use the Add SSID window to add three SSIDs at once to the selected RCU CU image.
NOTE: The options can be modified and/or canceled after you have set them. See ”Modifying parameters and omitting selected settings” on page 101. Figure 53 Opening the Add SSID window 4. To delete the SSID(s): Right-click to display the pop-up menu, click Edit SSID(s) & Path(s), and then click Delete SSID. The list changes to the SSID Settings Parameter list. Only the RCUs that are to be deleted are listed. NOTE: The options can be modified and/or canceled after you have set them.
2. Right-click to display the pop-up menu and click Omit. The RCUs, Paths, or SSIDs selected in step 1 are deleted from the list, and the deleted RCUs, Paths, or SSIDs have been removed from the operations. 3. Click Apply on TrueCopy main window. The Cancel All command deletes all the RCUs, Paths, or SSIDs on the list, and all the RCUs, Paths, or SSIDs have been removed from the operations.
group options (CT Group Option)” on page 106), and Delete CT Group (see ”Deleting consistency groups (Delete CT Group)” on page 107). Figure 54 Consistency Group list 4. Select a command and use the window to make your settings. 5. Click Set. The Consistency Group list changes to the Consistency Group Settings Parameter list or the Asynchronous Options Settings Parameter list. Only the consistency groups selected in step 2 are listed and items in the list depend on the selected command.
2. From the Consistency Group list, select a consistency group. Select only one consistency group. Figure 55 CT Group Status window • CT Group: Consistency group number of the selected consistency group in the list. • This CU Type: Registering side (MCU or RCU) of the consistency group. • CLPR: The number and name of the CLPR to which the volumes forming pairs belong. • S/N, SSID list box: Serial number and SSID of the CUs that are the components of the selected consistency group.
Adding consistency groups (Add CT Group) The Add CT Group command adds a consistency group to the connected MCU. When the Add CT Group command is selected, the Add CT Group window is displayed. Use the Add CT Group window to select the group options for the group. Figure 56 Add CT Group window Use the Timer Type box to select the timer type option for the group. • System = system timer (CPU TOD clock) provided by the I/O time-stamping function. • Local = local timer (internal MCU TOD clock).
To add a consistency group: 1. Connect to the MCU. 2. Verify that the async options are configured as needed (see ”Asynchronous copy option” on page 108). 3. From the Consistency Group tree, select a consistency group mode that includes the consistency group that you want to add. 4. From the Consistency Group list, select the consistency group(s) to add. Make sure to select more than one group that is not registered yet. 5.
NOTE: To change the group options, you must split all pairs in the group first. Figure 57 CT Group Option window The MCU-RCU Path box indicates the selected port type (Fibre) for the remote copy connections. You cannot change the port type on the CT Group Option window. For information about the boxes you can set on the CT Group Option window, see ”Adding consistency groups (Add CT Group)” on page 105. To change the group options: 1. Connect to the MCU. 2.
The Delete CT Group command deletes the selected group from the current MCU. You cannot delete a group that still has M-VOLs in the current MCU. To delete a consistency group from an MCU: 1. Connect to the MCU. 2. From the Consistency Group tree, select a consistency group mode that includes the consistency group you want to delete. 3. From the Consistency Group list, select the consistency group(s) to delete. Make sure to select more than one consistency group whose This CU column indicates MCU. 4.
• The MCU’s I/O response is delayed. • The RCU accepts only the one specific recordset that will enable it to settle the pending recordsets in the queue(s). For all other recordsets the RCU responds to the MCU with the channel-command-retry request. NOTE: If one or more consistency groups exist (TC390 or XP Continuous Access), this setting cannot be changed. This setting can be changed only when no consistency groups are assigned. Use the Offloading Timer (min.
consistency groups are deleted (by the Cancel All command or the Omit command), the list status becomes the Volume list. For the Asynchronous Option operation, the Delete command is not available. You can either modify the options you have set or cancel all the option settings you made. NOTE: After the delete operation of the CT Group Operation command, the Modify command is not available.
2. In the graph area of the Usage Monitor window, right-click to display the pop-up menu and click Display Item. The Display Item window is displayed. Figure 59 Selecting data for Usage Monitor Graph 3. In the Select Device box of the Display Item window, click one: • Subsystem Total: The I/O statistics data of all the LDEVs in the disk array is displayed. • Device: An LDEV of the CU image can be selected. In the CU box, 00-1F can be entered. In the Device box, 00-FF can be entered.
3. Click OK. Other methods of closing the graph: • Select another tab. • Select another program product or exit XP Command View Advanced Edition Software or XP Remote Web Console. • Select Stop in the Operation box of the Usage Monitor window and click Apply. The following table lists and describes the I/O statistics that can be selected on the Monitor Data box of the Display Item window.
Table 23 I/O statistics (continued) Statistic Description Average response (ms) Average response time (msec) for asynchronous update copy remote I/Os. Synchronization Pair Synchronized (%) Percent completion of the initial copy operation (number of synchronized pairs / total number of pairs). For duplex TC390 Synchronous pairs, this value is always 100% after the initial copy operation is complete.
Changing the subsystem option settings The subsystem’s option settings are displayed by selecting Subsystem from the tree on the Other Operations panel (Figure 60).
activities setting of 64 volumes allows you to limit the impact of initial copy activities on subsystem performance. For example, if you set the maximum initial copy activities to 64 volumes and then add 65 TrueCopy z/OS pairs at the same time, the MCU starts the first 64 pairs and will not start the 65th pair until one of the first 64 pairs is synchronized (Duplex status).
Changing CU option settings CU option settings are displayed by selecting CU from the tree on the Other Operations panel (see Figure 63). Figure 63 CU option settings list • CU: Number of this CU (00 to 3F) • SIM Report: MCU reporting status for service-level remote-copy SIMs to the hosts • PPRC Support: Status of PPRC support for the host • SCP Time: Sate-change-pending (SCP) time. SCP Time of TrueCopy z/OS and the state-change-pending time of FlashCopy Mirror Version 2 are the same.
2. Select one or more CUs from the list, right-click to display the pop-up menu, and then select the CU Option button to display the CU Option panel (Figure 64). Figure 64 CU Option panel The current CU options settings are displayed: • Service SIM of Remote Copy allows you to specify whether the MCU reports the service-level remote-copy SIMs to the hosts. (The moderate-, serious-, and acute-level SIMs are always reported to the host.
3. On the CU Option panel, change the CU options. 4. Select the Set button to close the CU Option panel. The desired changes are now displayed in the preset list. Figure 65 CU Option settings preset list and pop-up menu 5. Verify the desired changes in the preset list. • To change settings, right-click the preset list, select Modify, make the desired changes, and close the panel. The preset list displays the updated information. • To omit the settings, right-click the preset list, and select Delete.
of the conditions that affect disk array performance and provides recommendations for addressing these conditions. Table 24 Optimizing TrueCopy operations and XP12000/XP10000 performance Condition Description Recommendation(s) Write-intensive workloads Write-intensive workloads, such as SPOOL volumes and database logging volumes, can have a significant impact on disk array I/O response times. Spread write-intensive data across several volumes to minimize queuing.
To discontinue all TC390 operations: 1. Delete all TC390 pairs from the MCU(s) (Delete Pair, see ”Deleting TrueCopy volume pairs (Delete Pair)” on page 136). For TC390A pairs, you can use the Delete Range-Group option to delete all pairs in a group using just one operation. Verify that the pair status has changed to Simplex for all TC390 volumes before continuing. 2. Delete the TC390A group(s) from the MCU(s) (see ”Deleting consistency groups (Delete CT Group)” on page 107).
NOTE: TC390 and SI390 can function together in the same XP12000/XP10000 to provide both internal and remote backup for your data. If you are planning to combine TC390 and SI390, read the important configuration information in ”Combining TrueCopy with other data management operations” on page 57. If you will be using the TC390 software to perform remote copy operations, the management station must be LAN-attached to the MCU of each TC390 volume pair.
• Snapshot: Creates the snapshot file (see ”Snapshot function” on page 71). Figure 66 TrueCopy main window (Pair Operations window) 4. Select a command and use the window to make your settings. 5. Click Set. NOTE: The options can be modified and/or canceled after you have set them. See ”Modifying parameters and omitting selected volumes” on page 122. 6. Click Apply on the TrueCopy main window. The status of the command (active or inactive) depends on the status of the volumes selected in the Volume list.
2. Right-click to display the pop-up menu and click Modify to modify the parameters. A window is displayed. 3. Modify the parameters and click Set. 4. Click Apply on TrueCopy main window. To omit the selected volumes: 1. Select the volumes to be omitted from the operation on the Pair Settings Parameter list. 2. Right-click to display the pop-up menu and click Omit.
• M-VOL and R-VOL: The first row: CU number and Device ID. The second row: Device emulation type The third row: Capacity (number of cylinders). • The CLPR number and CLPR name are not displayed under the volume paired with the local volume. NOTE: If # is added to the end of the device ID, such as 00:3F#, the LDEV is an external volume. If the pair created with TrueCopy for z/OS of the microcode program version 50-03-6x-xx and earlier, “#” is not added to the volume paired with the local volume.
• If DFW required is selected, the MCU will suspend the pair when DFW on the RCU is blocked. This option is recommended if you need to maintain high MCU I/O performance. CAUTION: The interaction of the DFW required setting and the M-VOL fence level setting can cause a host application to fail with a permanent I/O error when attempting to update an M-VOL. Keep track of which volume pairs have the DFW required setting and verify that the DFW to the R-VOL is not blocked.
NOTE: Make sure to select the appropriate CU image before creating any TC390 pairs.
NOTE: When you set the several pairs at once and you want to keep some of the individual settings, leave the parameter box blank. Then, only the parameters you enter are available. • M-VOL: Device ID of the M-VOL. NOTE: If # is added to the end of an LDEV number, such as 00:3F#, the LDEV is an external volume. For more information about external volumes, see the HP StorageWorks XP External Storage user guide for the XP12000/XP10000 disk array. • R-VOL: Select the R-VOL device ID for the specified M-VOL.
The 15 Tracks setting speeds up the initial copy operation, but may affect the disk array’s I/O performance if the M-VOL is experiencing high write I/O activity. This setting is functionally equivalent to the PACE=2-255 parameter for the CESTPAIR TSO command. The 3 Tracks setting slows down the initial copy operation to minimize the impact of the initial copy operation on the disk array’s I/O performance. This setting is functionally equivalent to the PACE=1 parameter for the CESTPAIR command.
NOTE: When you create a TC390 pair, and if you select only M-VOL for the CFW data option, the data set which is updated by CFW in M-VOL cannot be used in R-VOL. To use this data set in R-VOL, delete a TC390 pair, and format the data set. NOTE: If a TC390 pair is established using PPRC commands, the CFW data option is set to the Copy to R-VOL setting. NOTE: By using Remote Copy Function Switch, you can set the following option with CESTPAIR: CFW data = only M-VOL.
Group: When the specified pair is suspended, all TC390A pairs in the same consistency group will be suspended, even if the failure affects only that pair and not the entire group. Select the Group error level for all TC390A volumes that are essential to disaster recovery. Suspended TC390A R-VOLs that have the Volume error level should not be used for disaster recovery. Volume: If the failure affects only the specified pair, then only that pair will be suspended.
9. To execute the Add Pair requests quickly, select the Use Time-Saving Mode check box above the Pair Settings Parameter list (Add Pair). 10. Click Apply on the TrueCopy main window to create (start) the specified TC390 pair(s). The MCU will start the initial copy operations according to the initial copy priority and the maximum initial copy activities setting of the RCU. 11. From the TrueCopy main window, verify that the new TC390 pair(s) is/are displayed correctly (Pending status) in the Volume list.
NOTE: When you set the several pairs at once and you want to keep some of the individual settings, leave the parameter box blank. Then, only the parameters you enter are available. Use the Suspend Pair window to select the Suspend Pair options for the pair(s): • Volume: Device ID of M-VOL. NOTE: If # is added to the end of an LDEV number, such as 00:3F#, the LDEV is an external volume.
NOTE: If the RCU is not able to complete these actions within the copy pending timeout setting, the RCU will discontinue the original suspend request and forcibly suspend the affected volume pairs. Thus, you can use the copy pending timeout parameter to limit the amount of time it takes to complete the suspend/drain operation. Purge. The MCU will change the TC390A pair status from suspending to suspended as soon as the RCU accepts the suspend operation.
Resuming TrueCopy volume pairs (Resume Pair) While a TC390 pair is suspended, the MCU does not perform any update copy operations. For a suspended TC390 Synchronous pair, the MCU may or may not continue accepting write I/Os for the M-VOL depending on the M-VOL fence level and suspend option (if user-requested).
• Initial Copy Pace (3 or 15): Select the number of the tracks 3 or 15 for resume copy. The default setting is 15. • Priority (From 0 to 256): Set the priority (0-256) for the resume operation, which determines the order in which the resume operations will be performed. • Asynchronous Parameters: • Resume Range: When Group is selected, resume all split or suspended TC390A pairs in the same group as the selected pair. When Volume is selected, resume only the selected TC390A pair(s).
NOTE: The options can be modified and/or canceled after you have set them. See ”Modifying parameters and omitting selected volumes” on page 122. To resume all split/suspended TC390A pairs in a consistency group, verify that the Resume Range option on the Resume Pair window is set to Group. 7. To execute the Resume Pair requests quickly, select the Use Time-Saving Mode check box above the Pair Settings Parameter list (Resume Pair). 8. Click Apply on the TrueCopy main window to resume the specified pair(s).
Delete Pair operation from the RCU. In this case, you will find the suspended status at the MCU after the Delete Pair operation from the RCU. The Delete Pair command deletes one or more TC390 pairs. When the Delete Pair command is selected, the Delete Pair window is displayed. Use the Delete Pair window to change the Delete Pair options (by force and TC390A delete range) for the pair(s) selected on the Volume list of the Pair Operations window.
When the status of the pair that is deleted is Simplex or Deleting, the default setting is Force (cannot be changed). When the status of the pair is not Simplex or Deleting, the default setting is Normal. • Asynchronous Parameters, Delete Range: Select the TC390A delete range option. This option simplifies disaster recovery operations for TC390A consistency groups at the RCU (secondary or remote disk array). The TC390 delete range options are: • Group (MCU or RCU).
7. To execute the Delete Pair requests quickly, select the Use Time-Saving Mode check box above the Pair Settings Parameter list (Delete Pair). 8. Click Apply on the TrueCopy main window to delete the specified pair(s). 9. When deleting TC390A pairs, verify that the Delete Pair request was completed successfully by checking the detailed TC390 pair status information on the Pair Status window (should be Simplex, not Deleting or Suspended).
NOTE: If # is added to the end of a device ID, such as 00:3F#, the LDEV is an external volume. For more information about external volumes, see Hitachi HPAV for system 390 User Guide for the XP12000/XP10000. • M-VOL Fence Level (Synchronous only): Select the fence level for the new pair(s). The fence level determines the conditions under which the MCU rejects write operations to the M-VOL. Never is automatically set for an asynchronous pair.
ICKDSF on a TrueCopy M-VOL ICKDSF activities involve write I/O operations with device support authorization instead of normal authorization. Because the MCU does not duplicate write I/O operations with device support authorization at the R-VOL of a TC390 volume pair, you must suspend a TC390 pair before running ICKDSF on a TC390 M-VOL. To perform ICKDSF on a TC390 M-VOL: 1. Connect to the MCU of the volume pair, and then start the TC390 software. 2.
NOTE: TC390 operations within one XP12000/XP10000 can be performed only if the SI390 option is not active on the disk array. The TC390 initial copy operation copies the entire contents of the M-VOL to the R-VOL. The data migration is complete when the initial copy operation completes and the pair status changes from pending duplex to duplex. The P/DAS host software function is used with TC390 Synchronous to complete the data migration nondisruptively.
To produce a PiT duplicate of an existing TC390A consistency group: 1. Disable the applications accessing the TC390A M-VOLs to stop all update activity to all M-VOLs in the group. 2. After all M-VOL updates have completed, suspend the TC390A group using the Group and Drain suspend options. If you are suspending the group at the main site, issue the suspend/group command to one M-VOL in the MCU. If you are suspending the group at the remote site, issue the suspend/group command to one R-VOL in the RCU.
4. When the MCU is fully powered on and ready to resume operations, resume the TC390A pairs at all MCUs that were powered off (use the resume group option). Planned outage of the RCU or remote copy connection You must suspend all affected TC390 pairs prior to a planned outage of an RCU or of a remote copy connection component (for example, switch, or extender).
2. Install XP Command View Advanced Edition Software or XP Remote Web Console and TC390 hardware and software, and establish TC390 operations for the volumes and groups identified in step 1. Make sure to select the correct CU images to access the appropriate volumes. 3. Use the appropriate combination of TC390 options for disaster recovery: • RCU options: Incident of RCU, PPRC Support, Service SIM of Remote Copy, and FREEZE Option (see ”Registering an RCU (Add RCU)” on page 87).
R-VOL Status (CRIT=Y(PATHS)). When this fence level is selected, the M-VOL is fenced only if the MCU is not able to change the R-VOL pair status to suspended. If the MCU successfully changes the R-VOL pair status to suspended, subsequent write I/O operations to the M-VOL will be accepted and the MCU will keep track of updates to the M-VOL. This allows the volume pair to be resumed quickly using the resync (out-of-sync-cylinders) copy operation (MODE=RESYNC).
You should prepare for file and database recovery by using: • Files for file recovery (for example, DB2 log files that have been verified as current). To ensure the currency of these files, use the R-VOL Data fence level setting for the TC390 pairs that contain these important files. • The sense information with system time stamp that will be transferred through ERC. Remote copy and disaster recovery procedures are inherently complex.
NOTE: If PPRC is not installed, connect to each RCU and delete all TC390 pairs. For TC390A pairs, use the C/T delete option to delete all consistent pairs in the group at the same time. This option prevents you from accidentally using inconsistent pairs for disaster recovery. Delete all TC390 sync pairs in the MCU using the Delete by Force and Delete All Pairs options. CAUTION: After an R-VOL changes to the simplex state, you cannot distinguish it from a non-TC390 simplex volume.
Table 26 Analyzing the currency of TrueCopy Synchronous R-VOLs (continued) Status of R-VOL Fence Level Currency of R-VOL Suspended all other types Data Current. This R-VOL is synchronized with its M-VOL. Status Never Suspect. This R-VOL is not synchronized with its M-VOL if any write I/Os were issued to the M-VOL after the pair was suspended. Restore the consistency of this R-VOL and update it, if required.
To transfer operations to the main site: 1. Bring up the host system at the main (primary) site and ensure that all TC390 components are fully operational. 2. At the main site, delete all TC390 pairs at the MCUs. The Delete Pair by Force option must be used because the previous R-VOLs are now in the simplex state at the remote site. Use the Delete All Pairs option to delete all TC390 sync pairs in each CU image. Use the Delete-Group option to delete all TC390A pairs in each group.
2. Halt the applications at the remote site and vary the M-VOLs (original R-VOLs) offline at the remote site. This maintains synchronization of the TC390 Synchronous pairs. 3. At the remote site, suspend all TC390 pairs at the MCUs (original RCUs) to destage any pending data from cache. Confirm that the pairs are suspended before proceeding. If an error occurs, resolve it before proceeding. 4.
provide troubleshooting information for suspended TC390 pairs. For troubleshooting information on TC390 scripting, see ”TrueCopy scripting” on page 191. Table 29 General TrueCopy troubleshooting Error Corrective Action TC390 operations do not function properly. Verify that all TC390 requirements and restrictions are met (for example, track format, LVI, VOLSER, or DFW). See ”System requirements” on page 44 and ”Requirements and restrictions” on page 46.
Table 30 Troubleshooting RCU path status problems Path Status Description Corrective Action Initialization Failed The link initialization procedure to the RCU failed. Verify that you entered the correct RCU S/N and SSID and path parameters (Fibre: MCU port, RCU port, CU number and Controller ID. Serial: port, link address and logical address). For serial, verify that the correct MCU port is configured as an RCP and that the correct RCU port is configured as an LCP.
Table 30 Troubleshooting RCU path status problems (continued) Path Status Description Corrective Action Invalid Port The specified port is not configured as an RCP or initiator port, or this path already exists. For serial, verify that the correct MCU port is configured as an RCP and that the correct RCU port is configured as an LCP. For Fibre Channel interface, verify that the Fibre Channel topology settings of the MCU and RCU ports are correct.
Table 31 Troubleshooting suspended TrueCopy pairs (continued) Suspend Type Applies to Description Corrective Action by MCU R-VOL The RCU received a request from the MCU to suspend the pair. The M-VOL suspend type is M-VOL by Operator or R-VOL by Operator. Resume the pair from the MCU. by RCU M-VOL The MCU detected an error condition at the RCU that caused the MCU to suspend the volume pair. The R-VOL suspend type is by MCU. Clear the error condition at the RCU or R-VOL.
recordset errors. Hardware failures that affect the cache storage/shared memory of the MCU or RCU may also cause the TC390A volume pairs to be suspended. Table 32 Resolving TrueCopy Asynchronous suspension conditions Classification Causes of Suspension SIM Recovery procedure MCU/RCU hardware Hardware redundancy has been lost due to some blockade condition. As a result, MCU-RCU communication, creating or receiving recordset, or the staging or de-staging process could not complete.
XP12000/XP10000 SVP error code. If you need to call HP technical support for assistance, report the TC390 and SVP error codes. Figure 74 Example of the TC390 error message Using PPRC commands for TrueCopy Overview of PPRC commands The XP12000/XP10000 supports IBM Peer-to-Peer Remote Copy (PPRC) TSO and ICKDSF commands to perform TC390 operations from the zSeries and S/390 host system. PPRC TSO commands are issued from the system console to the M-VOL or R-VOL of a TC390 pair.
1. The path that is used before the CESTPATH command is executed, but that which is not specified in the CESTPATH command is deleted. 2. The path that is used before the CESTPATH command is executed and specified in the CESTPATH command is maintained. 3. The path that is not used before the CESTPATH command is executed, but that which is specified in the CESTPATH command is added.
Table 33 TrueCopy operations versus PPRC TSO and ICKDSF commands (continued) TC390 Operation TSO Command ICKDSF Command Command Issued to: Description Add Group ----- ----- MCU Must be performed using the TC390 software. The group options are selected during add group (see ”Adding consistency groups (Add CT Group)” on page 105). Group Status ----- ----- MCU/RCU Must be performed using the TC390 software (see ”Viewing consistency group status (CT Group Status)” on page 103).
Table 33 TrueCopy operations versus PPRC TSO and ICKDSF commands (continued) TC390 Operation TSO Command ICKDSF Command Command Issued to: Description ----- P/DAS SWAP ----- M-VOL and R-VOL Supported by TC390 Synchronous. Command is rejected by TC390A pairs. Redirects application I/Os from the M-VOL to the R-VOL. For details on using P/DAS SWAP with TC390, see ”P/DAS support” on page 41. ----- CGROUP (FREEZE/ RUN) ----- MCU (M-VOL or simplex) Supported by TC390 Synchronous.
Table 34 Typographic conventions for PPRC TSO commands (continued) Typeface/Symbol Example Usage Bold cmd_param Command/keyword names, parameters, or console outputs that involve/denote special meaning for TC390A. Square brackets [PACE(15)] Keywords/parameters that can be omitted. Vertical pipe (YES|NO) List of keywords to be selected. Underline (YES|NO) The default keywords/parameters. Strike through [QUIESCE] Invalid keywords/parameters for TC390A.
The following table describes the CESTPATH LINK parameter for the Fibre Channel interface. Table 35 CESTPATH LINK parameter (ESCON interface) LINK Parameter Fibre Channel Interface aa Bit 0-3: RCU controller ID First two digits of SAID, see Table 37 on page 163. x2-xF: Number stands for RCU controller ID. (x’4’ is specified.) Bit 4-7: FREEZE option x0:keep the status x1:Enabled x2:Disabled When there are several paths, the same values must be specified for all the paths.
Figure 75 Example of WWNN NOTE: The parameter of PRIM and SEC of CDELPATH command are indicated as same as the parameter of CESTPATH command. If the subsystem is connected to the former type subsystem that does not support the Fibre Channel interface, a unit check is reported. The following table gives the XP12000/XP10000 system adapter ID (SAID) values for the CESTPATH LINK parameter.
Table 37 SAID Values for LINK parameters (ports) (FRONT CL1) Package Location Port SAID* CL1-C Package Location Port SAID* X'0002' CL1-L CL3-C X'0022' CL5-C Package Location Port SAID* X'000A' CL9-Q CL3-L X'002A' X'0042' CL5-L CL7-C X'0062' CL1-D Package Location Port SAID* X'008E' CL9-G X'0086' CLB-Q X'00AE' CLB-Q X'00A6' X'004A' CLD-Q X'00CE' CLD-G X'00C6' CL7-L X'006A' CLF-Q X'00EE' CLF-G X'00E6' X'0003' CL1-M X'000B' CL9-R X'008F' CL9-H X'0087' CL3-D
Table 38 SAID Values for LINK parameters (ports) (REAR CL2) Package Location Port SAID* CL2-C Package Location Port SAID* X'0012' CL2-L CL4-C X'0032' CL6-C Package Location Port SAID* X'001A' CLA-Q CL4-L X'003A' X'0052' CL6-L CL8-C X'0072' CL2-D Package Location Port SAID* X'009E' CLA-G X'0096' CLC-Q X'00BE' CLC-Q X'00B6' X'005A' CLE-Q X'00DE' CLE-G X'00D6' CL8-L X'007A' CLG-Q X'00FE' CLG-G X'00F6' X'0013' CL2-M X'001B' CLA-R X'009F' CLA-H X'0097' CL4-D X'
CESTPAIR DEVN(X’dev#’) PRIM(X’ssid’ cmd_param X’cca’ X’lss’) SEC(X’ssid’ serial# X’cca’ X’lss’) [MODE(COPY|NOCOPY|RESYNC)] [PACE(pace)] [CRIT(YES|NO)] [MSGREQ(YES|NO)] Table 39 Using CESTPAIR to establish and resume TrueCopy Async pairs Parameter Contents Description cmd_param AGnnd nn = consistency group number (00-7F) or master volume number (00-FF: for dummy pair mode). Without MODE(RESYNC): Specifies the consistency group number nn to which the volume pair will belong.
• When cmd_param AGxxx is specified, this command ends before the actual pair establishment/re-establishment successfully starts. Confirmation by CQUERY or IEA494I console message is recommended after this command. CSUSPEND Table 40 on page 167 describes how to use the CSUSPEND command to suspend TC390A pairs and groups.
For 3990-3, -6 and -6E controller emulations: CDELPAIR DEVN(X’dev#’) PRIM(X’ssid’ cmd_param X’cca’ X’lss’) SEC(X’ssid’ serial# X’cca’ X’lss’) For 2105 and 2107 controller emulation (new ‘lss’ parameter for LCU number): CDELPAIR DEVN(X’dev#’) PRIM(X’ssid’ cmd_param X’cca’ X’lss’) SEC(X’ssid’ serial# X’cca’ X’lss’) Table 41 Using CDELPAIR to delete TrueCopy Async pairs/groups at the MCU Parameters Contents Description cmd_param AG000 Specifies that all pairs in the consistency group* should be deleted.
• If the first digit of the cmd_param is other than A, the disk array interprets this command as pair deletion for TC390 Synchronous or SI390. • Regardless of the number of volume pairs to be deleted, this command ends before the actual pair deletion is successfully completed. Confirmation by CQUERY or IEA494I console message is recommended after this command.
The TRACKS OUT OF SYNC field indicates the number of trucks out of sync. The TRACKS ON VOLUME field indicates the total number of tracks that the paired volumes have. The PERCENT OF COPY COMPLETE indicates the percentage of cylinders that have already been copied for pair resynchronization. See ”Viewing the status of TrueCopy volume pairs (Pair Status)” on page 123 for a more detailed description. The MCU serial number field is used to display the TC390A information shown in Figure 76.
Table 43 CQUERY output for serial and Fibre Channel LINK Parameter Fibre Channel Interface Fibre Channel Interface Mode 484 OFF Mode 484 ON aa Bit 0-3: RCU controller ID SAID of MCU x2-xF: Number stands for RCU controller ID.
The MCU serial number field is used to display the TC390A information shown in Figure 77. Figure 77 Controller emulations CQUERY for Fibre Channel interface The path types and path status for Fibre Channel remote copy connections can be displayed by the CQUERY command. The RCU controller ID can also be displayed. The following example shows the output of the CQUERY command and Table 44 on page 173 describes the parameters used in the example for both serial and Fibre Channel interface.
• If mode 484 is ON, the status of path as using the Fibre Channel interface will be displayed. If mode 484 is OFF, ESCON will be indicated for the path status. • If the former type subsystem or the subsystem of XP12000/XP10000 microcode version 50-05-XX-XX or earlier is connected, mode 484 must be OFF.
The CGROUP command has two parameters, FREEZE and RUN. The CGROUP/FREEZE command stops all host I/O operations to the specified TC390 M-VOLs as well as all TC390 update copy operations to their associated R-VOLs. The CGROUP/RUN command changes the pair status to suspended and allows the M-VOLs to start accepting host I/Os. NOTE: For 2105 and 2107 controller emulation, do not use the FREEZE option. Use the CGROUP option of the CESTPATH command (see ”CESTPATH” on page 161).
For ESCON cable : Value Port ID Freeze Option X’0000’-X’001F’ Interface 1A-2R Default X’0100’-X’011F’ Interface 1A-2R Enabled X’0200’-X’021 F’Interface 1A-2R Disabled For Fibre Channel cable: Value Port ID Freeze Option X’4000’-X’40FF’ Interface 1A-GR Default X’4100’-X’41FF Interface 1A-GR Enabled X’4200’-X’42FF’ Interface 1A-GR Disabled ll = Fibre-channel port ID of the secondary CU (RCU) from which the paths of the TCz should be established.
• FREEZE (3990 only): When CGROUP is issued with the FREEZE option, the MCU: • Blocks the logical path(s) between the specified MCU CU image and RCU CU image to stop all TC390 update copy operations to the R-VOLs in the specified RCU. • Presents state change pending (SCP) with extended long busy status to host I/O requests, which causes the host to queue I/Os for the M-VOLs. SCP is indicated until the CGROUP/RUN command is issued or until the SCP delay time expires.
5. CGROUP/FREEZE commands are issued to groups. 6. SCP sense bytes are reported if an I/O is issued to a frozen volume. 7. I/Os are queued at the host. 8. Switch to remote (secondary) site. Figure 78 Overview of GDPS operations Using PPRC TSO commands with CGROUP support CESTPATH. You can use the CESTPATH command to recover a blocked MCU-RCU path. Make sure to use the same parameters as when the path was established. CESTPAIR.
CQUERY Output Example: M-VOL/Paths/Format ****************** PPRC REMOTE COPY CQUERY - PATHS ******************** * PRIMARY UNIT: SERIAL#= 000000090217 SSID= 00F8 * * FIRST SECOND THIRD FOURTH * * SECONDARY SECONDARY SECONDARY SECONDARY * *SERIAL NO: 000000090217 ............ ............ ............
CQUERY Output Example: M-VOL/Volume/Format ************** PPRC REMOTE COPY CQUERY - VOLUME ******************** TC390 M-VOL is * (PRIMARY) (SECONDARY) * suspended by * SSID CCA SSID CCA * CGROUP/RUN. *DEVICE LEVEL STATE PATH STATUS SERIAL# SERIAL# * *------ --------- ---------- ----------- ----------------- * FREEZE option * 0F80 PRIMARY.. SUSPEND(A) INACTIVE 00F8 00 00F8 02 * is enabled. * CRIT(NO).......
NOTE: If PPRC Support = No is selected on the RCU Option window, the host generates the system console message that includes the SIM instead of the IEA494I or IEA491E message. IEA494I message Whenever a TC390 pair status changes, with the exception of the TC390A transition states suspending and deleting, the MCU reports state-change-interrupt (SCI) to all hosts. In response to the SCI, the IEA494I system console message is generated (if supported by the host).
NOTE: The PPRC Support=Yes option must be selected on the RCU option window (see ”Registering an RCU (Add RCU)” on page 87). If not, the host processor generates the system console message that includes the SIM instead of the IEA494I or IEA491E message.
Table 46 XP12000/XP10000 response characteristics to failure conditions (continued) Failure Condition TC390 Pairs Suspended? Expected Messages FREEZE Function Failure of a link between the MCU and RCU No 1. IEA480 message (SIM for TC390 path blocked) is reported when the next I/O to any device in this MCU is issued. 2. No IEA491 or IEA494 messages are displayed. Not activated Failure of NVS on the MCU; Failure of MCU read cache a. One side of MCU cache blocked due to failure No1 1.
Table 46 XP12000/XP10000 response characteristics to failure conditions (continued) Failure Condition TC390 Pairs Suspended? Expected Messages FREEZE Function Failure of NVS on the RCU; Failure of RCU read cache a. One side of RCU cache blocked due to failure No 1. The RCU reports IEA480 message (SIM for cache blocked) to either the MCU or the host processor (whichever issues the next I/O first). If MCU receives the SIM, it passes the SIM to the attached host processor.
GDPS-TC390-HXRC matrix The following table compares IBM 3990-6E GDPS support to XP disk array GDPS support, and also provides a comparison of TC390 and HXRC to PPRC and XRC. NOTE: The information shown in the following table was current at the time of publication of this document but is expected to change over time. Contact your HP account support representative for the latest GDPS-TC390-HXRC matrix information.
Table 47 GDPS-TC390-HXRC matrix (continued) zSeries and S/390 Feature IBM 3990-6E XP12000/XP10000 XP48/XP512 TSO command Support Supported Supported. Supported. Some additional options only available through the XP Command View Advanced Edition Software server or XP Remote Web Console (or SVP). Some additional options only available through the Remote Console PC (or SVP). ICKDSF command support Supported Supported. Supported.
Table 47 GDPS-TC390-HXRC matrix (continued) zSeries and S/390 Feature IBM 3990-6E XP12000/XP10000 XP48/XP512 TC-Unique Features (specified through the XP Command View Advanced Edition Software server, XP Remote Web Console, or SVP) RCU Options Minimum paths Not supported Default = 1. Default = 1. If the minimum number of MCU-RCU active paths falls below this value, all pairs will be suspended based on the Fence Level option in effect.
Table 47 GDPS-TC390-HXRC matrix (continued) zSeries and S/390 Feature IBM 3990-6E XP12000/XP10000 XP48/XP512 Primary disk array interface Parallel or ESCON ESCON only ESCON only Secondary disk array interface Parallel or ESCON Parallel or ESCON Parallel or ESCON Channel extender support Yes Contact your HP account support representative for the latest information. Contact your HP account support representative for the latest information.
also reports SIMs to the XP Command View Advanced Edition Software server or XP Remote Web Console to provide an additional source of notification for the user. During TC390 operations, the MCU and RCU will generate a service SIM each time the pair status of the M-VOL or R-VOL changes for any reason, including normal status transitions (for example, pending duplex to duplex).
This SIM is not reported to the host system when the Service SIM=Not Report RCU option is selected. Table 49 TrueCopy device SIMs Ref. Code Severity Description Reported to Host Generated by Log File 22 23 D0 0x Service TC390 started the initial copy for this volume, or was out of sync for this volume. Yes1 Once MCU SSB Log D0 D8 1x Service TC390 completed the initial copy for this volume.
Table 49 TrueCopy device SIMs (continued) Ref. Code Severity Description Reported to Host Generated by Log File 22 23 D4 3x Serious TC390 for this volume was suspended because DFW to the R-VOL was blocked. Yes2 Repeat MCU SIM Log D4 4x Serious TC390 for this volume was suspended due to an internal error condition detected by the RCU. Yes2 Repeat MCU SIM Log D4 5x Serious TC390 for this volume was suspended because the operator deleted the volume pair from the RCU.
Table 49 TrueCopy device SIMs (continued) Ref. Code Severity 22 23 D7 sx Service Description Reported to Host Generated by Log File The R-VOL has accepted/completed state change as requested by operation. The third digit of the reference code “s” indicates the events as follows: No RCU SSB Log 0: Accepted Suspend Pair operation. 1: Accepted Delete Pair operation. R-VOL is suspended. 2: Accepted Delete Pair operation. R-VOL is duplex. 3: Accepted Delete Pair operation. R-VOL is pending.
NOTE: This section assumes that the user is familiar with batch files and does not provide instructions for writing or editing batch files. The macro commands and parameters listed in this section are the only commands recognized by the TC390 scripting function. CAUTION: The user is responsible for testing the TC390 scripting function before running any TC390 scripts. If a TC390 script is run without prior testing and the script ends abnormally, data loss could occur.
Table 51 Internal macro commands for TrueCopy scripting Type Macro Description For lists SetList Set (define) a list of items. AddList Add items to a list. Start Declares the beginning of a script. End Declares the end of a script. Delay Suspends script execution for the specified length of time. If Executes a script conditionally. EndIf Terminates a script conditionally. MakeString Makes strings; converts numeric value to character string.
• An empty statement (see Table 52). The empty statement is a non-execution statement. Table 52 Syntax description Statement Name Description Blank statement Space or Tab with a return Comment statement One line beginning with // Empty statement Return only Execution statement Work variable statement (non-list type work variable = constant) Macro statement Macro name [parameter list] See ”Operation macro commands” on page 195 and ”Internal macro commands” on page 203 for macro information.
Script symbols Symbols can be used in a script to enhance or limit the power of each script command. The following table lists and describes the symbols that can be used in a script. Table 55 Script symbols Symbol1 Use Quotation mark Used to define the character constant by enclosing with it quotation marks. Space Used to delimit the before and after phrases. Comma Used to delimit the before and after phrases. This symbol must be placed by following each macro description rule.
• CT group list (numeric): consistency group number (0x00 - 0x7F). For async pairs you must specify this parameter. For sync pairs you must omit this parameter. • Priority list (numeric): priority of initial copy operation (1-256); default = 32. • Fence level list (string): “N” or “Never”, “S” or “Status” “D”, or “Data” = default = “Never”. For async pairs you must either specify N (never) or omit this parameter. • CFW flag list (numeric): 0 = copy CFW data to R-VOL; 1 = only M-VOL; default = 1.
Example: CreateHrcPair Command Start $Script="HRC",$Svr="CU-Name" // $Dev SetList $D =_ilDevA, $S = {0x0100,0x0101,0x0102,0x0103,0x0104,0x0105,0x0106,0x0107} AddList $D =_ilDevA, $S = {0x0108,0x0109,0x010A,0x010B,0x010C,0x010D,0x010E,0x010F} // $Rdev SetList $D =_ilDevB, $S = {0x1F00,0x1F01,0x1F02,0x1F03,0x1F04,0x1F05,0x1F06,0x1F07} AddList $D =_ilDevB, $S = {0x1F08,0x1F09,0x1F0A,0x1F0B,0x1F0C,0x1F0D,0x1F0E,0x1F0F} // $Priority SetList $D =_ilWorkA, $S = {1,2,3,4,16.
Example: DeleteHrcPair Command Start $Script="HRC",$Svr="CU-Name" // $Dev SetList $D =_ilDevA, $S = {0x0800,0x0901,0x0A02} AddList $D =_ilDevA, $S = {0x0B03,0x0C04,0x0D05,0x0E06} // $DelMode SetList $D = _ilWorkA, $S = {0, 1, 0} DeleteHrcPair $Dev = _ilDevA, $DelMode = _ilWorkA DeleteHrcPair $Dev = 0x124C, $DelRange = "Group" End Suspend pairs The SuspendHrcPair command suspends TC390 pairs. The SuspendHrcPair parameters include: • Device list (numeric): C x 0x100 + VV, where C=CU#, VV=vol# within the CU.
Example: SuspendHrcPair Command Start $Script="HRC",$Svr="CU-Name" // $Dev SetList $D =_ilDevA, $S = AddList $D =_ilDevA, $S = // $SusReport SetList $D = _ilWorkA, $S // $SusMode SetList $D = _slWorkA, $S {0x0100,0x0101,0x0102,0x0103} {0x0104,0x0105,0x0106,0x0107,0x0108} = {0, 1, 0} = {"R-Vol","M", "R", "M-Vol"} SuspendHrcPair $Dev = _ilDevA, $SusMode = _slWorkA, $SusReport = _ilWorkA // $Dev SetList $D =_ilDevB, $S = {0x0900,0x0901,0x0902,0x0903} // $PendData SetList $D = _slWorkC, $S = {"Drain", "Purge"
Example: ResumeHrcPair Command Start $Script="HRC",$Svr="CU-Name" // $Dev SetList $D =_ilDevA, $S = {0x0100,0x0101,0x0102,259} // $Priority SetList $D =_ilWorkC, $S = {24,32,0x13,8} ResumeHrcPair $Dev = _ilDevA, $Priority = _ilWorkC StartHrcPair // $Dev SetList $D =_ilDevB, $S = {0x0200,0x0201,0x0202,0x0203} AddList $D =_ilDevB, $S = {0x0904,0x0905,0x0906,0x0907} ResumeHrcPair $Dev = _ilDevB, $OptRsmRange = "Volume" StartHrcPair End Change pair options Use the ChangeHrcOption command to change the pair opt
Example: ChangeHrcOption Command Start $Script="HRC",$Svr="CU-Name" // $Dev SetList $D AddList $D // $OptCfw SetList $D // $Fence SetList $D =_ilDevA, $S = {0x0100,0x0101,0x0102,0x0103,0x0104} =_ilDevA, $S = {0x0117,0x0118,0x0119} = _ilWorkA, $S = {1, 1, 0} = _slWorkA, $S = {"D", "S", "N", "Data", "Status"} ChangeHrcOption $Dev = _ilDevA, $Fence = _slWorkA, $OptCfw = _ilWorkA // $Dev SetList $D =_ilDevB, $S = {0x0A00,0x0A01,0x0A02,0x0A03,0x0A04} // $OptErrLv SetList $D = _slWorkB, $S = {"G", "V", "Volume"
• Output list (list-type and numeric work variable) The SelectHrcDevice parameters include: • Device list (numeric): list of devices to be searched: C x 0x100 + VV, where C=CU#, VV=vol# within CU. Default = all possible target devices that can be specified. The maximum number of the device is 1,024. When you search for more than 1,024 devices, use this command for several times. • Serial number list (string): RCU serial number. Default = not specific. • SSID number list (numeric): RCU SSID.
Internal macro commands The internal macro commands are the connection agents that connects the functional macros together and produces a complete and functioning script. The internal macros are divided into two groups as shown in the following table: list types and non-list types. Table 58 Internal macro commands Type Macro Description For lists SetList Set (define) a list of items. AddList Add items to a list. Start Declares the beginning of a script. End Declares the end of a script.
must contain one conditional decision statement within parentheses. The string values must be compared as ASCII character codes (see Table 59).
For example, to create a MakeString statement that will convert the 16-bit numeric expression to a hexadecimal number (0 - 0xffff) and set the string as it is, with an output buffer of _sMsg, the command would be: MakeString $D=_sMsgB ,$Fmt=“EndCode=(0x%x):%s” ,$Item=_Result,_sMsgA For the MakeString command listed above: _sMsgB = “EndCode=(0x110f):Error Occurred”. SetList Use the SetList command to assign specific items to a list.
The work variable is part of an execution statement in a script. The following table provides a description and the storage type of each work variable statement for list and non-list types. Table 62 Work variables List Type Variable Type Description and Storage Type _ilDEV Numeric Stores the device number list. Expression: _ilDevA, _ilDevB, _ilDevC _ilPriority Numeric Stores the priority number list.
Table 63 Reserved result variables (continued) Variable Type Description _MsgResult Numeric Stores the execution results of a Message (internal) macro. 1 = OK, 6 = Yes, 7 = No. _SelectResult Numeric Stores the number of devices found by SelectHrcDevice macro. 0 = no devices found. Reserved status variables When a GetHrcStatus command is issued, the XP Command View Advanced Edition Software server or XP Remote Web Console obtains the status of the specified TC390 pair(s) from the XP12000/XP10000.
Table 64 Reserved status variables (continued) Variable Type Description _HrcStatus _Sync String Stores the synchronous level: “Synchronous0” = sync; “Synchronous2” = async; “Undefined” = undefined. _HrcStatus _TimeOfUpdate String Stores the pair status update time: “MM/DD/YYYY hh:mm:ss” = MM: month, DD: day, YYYY: year, hh: hour, mm: minute, ss: second.
The XP12000/XP10000 will run the script commands based only on what has been specified in the text of the script. The following table describes the syntax requirements that will be evaluated. Table 65 Syntax requirements for optional parameters Parameter Syntax Requirements Length Check that each line does not exceed the maximum length for a script statement. Phrases in a script statement A phrase is enclosed by the quotation symbols.
Table 65 Syntax requirements for optional parameters (continued) Parameter Syntax Requirements If The number of phrases matches. The parentheses are described in the correct location. Expressions 1 and 2 are correctly described. The attribute of expressions 1 and 2 matches. Specifying the right side is correct. The comparison operator is correctly described. EndIf The number of phrases matches. The macro is describe with the related If statement.
Error reporting The TC390 scripting error codes are slightly different from the general TC390 error codes. The following figure shows the format of the scripting error codes. The following table describes the TC390 scripting error messages. Table 67 on page 211 lists the TC390 scripting error codes. The message ID is the four-digit number displayed on the error message.
Table 67 TrueCopy scripting error codes (continued) Message ID Internal Code Error Message Error Description 2340 1103, 1104 Invalid command line parameter. An error is found in the startup parameter of the script monitor. The installation process may not have been complete. 2340 1105 Invalid command line parameter (1st parameter). Start parameter (the 1st parameter) is invalid. 2340 1106 Invalid command line parameter (2nd parameter). Start parameter (the 2nd parameter) is invalid.
Table 67 TrueCopy scripting error codes (continued) Message ID Internal Code Error Message Error Description 2349 2208 Required value is not found. Line = nnnn The end of line nnnn is “=”. 2350 2209, 220a Illegal ‘(‘and’)’ pair. Line = nnnn The parentheses are not matched in script line nnnn. 2351 220b, 2303 Syntax error. Line = nnnn An illegal word is included in script line nnnn. 2351 27xx Syntax error. Line = nnnn The syntax in the parameter description for script line nnnn is invalid.
Table 67 TrueCopy scripting error codes (continued) Message ID Internal Code Error Message Error Description 2361 4182 Mismatch controller name. The device names specified by the Start macro and by the execution environment file are different. 2362 5101 Parameter value error ($Dev). A functional macro parameter error was found. Check the setting value in the $Dev parameter. 2362 5102 Parameter value error ($Priority). A functional macro parameter error was found in setting $Priority.
Table 67 TrueCopy scripting error codes (continued) Message ID Internal Code Error Message Error Description 2362 5124 Parameter value error ($CopyMode!=$Sync). A functional macro parameter error is found in the $CopyMode!=$Sync settings. 2362 5132 Parameter value error ($CTG). A functional macro parameter error is found. Set the correct CT group number in the $CTG parameter. 2362 5133 Parameter value error ($OptErrLv). A functional macro parameter error is found.
Table 67 TrueCopy scripting error codes (continued) Message ID Internal Code Error Message Error Description - 5004 API error(SetCreatePair). ErrorCode=6005 xxxx An error occurred during the create pair operation. - 5005 API error(SuspendPair). ErrorCode=6005 xxxx An error occurred during the suspending pair operation. - 5006 API error(ChangePairOption). ErrorCode=6005 xxxx An error occurred during the changing pair operation. - 5007 API error(DeletePair).
Load balancing control Current load balancing control The XP12000/XP10000 has three fixed thresholds and three levels of load balancing for varying amounts of sidefile cache as follows: Threshold 1/2/3 = 40/50/60%. • Level 1: Sidefile capacity is 40% -50% of the total cache capacity. Write I/Os are blocked by “Sleep”“Wait” logic.
• The operating system must support the new DONOTBLOCK option. • Mode 61 must be ON. If Mode 61 is OFF (default), the XP12000/XP10000 performs current load balancing control. If the operating system does not support the DONOTBLOCK option, set Mode 61 = OFF. DONOTBLOCK option: The XP12000/XP10000 does not block write I/Os for the specified logical device, to avoid performance impact for application programs.
• Combination 4: MODE 85,86 = ON,ON – Threshold 1/2/3=60/70/80% Figure 84 Combination 1: MODE 85,86 = ON,OFF; Threshold 1/2/3 = 30/40/50% Figure 85 Combination 2 (Default): MODE 85,86 = OFF,OFF; Threshold 1/2/3 = 40/50/60% Hitachi TrueCopy for z/OS user guide 219
Figure 86 Combination 3: MODE 85,86 = OFF,ON – Threshold 1/2/3 = 50/60/70% Figure 87 Combination 4: MODE 85,86 = ON,ON – Threshold 1/2/3 = 60/70/80% 220 Hitachi TrueCopy z/OS for HP XP12000/XP10000 and SVS 200 storage systems
2 Support and Other Resources Supported Storage Platforms In this guide, the terms storage system and disk array refer to the following storage platforms: • HP StorageWorks XP12000 Disk Array • HP StorageWorks XP10000 Disk Array • HP StorageWorks 200 Storage Virtualization System For supported microcode versions, see the HP StorageWorks Single Point of Conectivity Knowledge (SPOCK) website: http://spock.corp.hp.com.
• http://www.hp.com/support/downloads • http://www.hp.com/support/rwc/manuals Documentation Feedback HP welcomes your feedback. To make comments and suggestions about product documentation, send a message to storagedocsFeedback@hp.com. All submissions become the property of HP.
Index A D adding consistency group 105, 106 path to RCU 98 RCU path 98 SSID to RCU 100 authorized resellers, HP 221 data migration using TC390 141 database recovery 147 deleting consistency group 108, 109 path to RCU 99 RCU 97 RCU path 99 RCUs 97 SSID from RCU 100, 101 volume pairs 138 device blocking HXRC 216 TC390 166 DFW requirements for TC390 48 disaster recovery clearing SIMs 148 consistency of async R-VOLs 149 currency of sync R-VOLs 148 file and database recovery procedures 146 M-VOL fence level 1
TC390A suspend option 132 H help HP technical support 221 HP authorized resellers 221 storage website 221 Subscriber’s choice website 221 technical support 221 HXRC 18, 175 I ICKDSF media maintenance on TC390 volumes 140 PPRCOPY commands 158 IEA491E system console message 179, 180 IEA494I system console message 147, 180 Initial Copy Activities 114 installing TC390 hardware 49 TC390 software 53 TC390 system requirements 44 L logical path.
Remote Copy monitoring starting 110 stopping 110 resuming consistency group 135 volume pairs 135 R-VOL analyzing currency of 148 analyzing TC390A consistency of 149 performing ICKDSF on 141 pinned track 187 S SCP Delay Time 117 SCP Time 116 scripting 78, 191 ChangeHrcPair command 200 components 194 CreateHrcPair command 195 DeleteHrcPair command 197 functional macro commands 192 GetHrcStatus command 201 internal macro commands 193, 203 parameter restrictions 194 result value 206 ResumeHrcPair command 199 S
troubleshooting RCU path status 153 suspended pairs 154 TC390 151 TC390A suspension conditions 155 U using TC390 Synchronous to migrate data 142 V viewing consistency group status 103 RCU status 85 Virtual LVI/LUN 61 volume pairs changing options 140 creating 130 deleting 138 resuming 135 suspending 133 volumes omitting 123 W websites HP documentation 221 HP storage 221 HP Subscriber’s choice 221 226
Figures 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 TrueCopy components for serial (ESCON) connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 TrueCopy components for Fibre Channel connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 TrueCopy remote copy operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 Selecting data for Usage Monitor Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subsystem Option Settings List and Pop-up Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Option panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subsystem Option settings preset list . . . . .
Tables 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 HXRC path configuration with FICON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 RAID Level Configurations of TC390 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 XP12000/XP10000 modes for TrueCopy for z/OS . . . . . . . . . . . . . . . . .
59 60 61 62 63 64 65 66 67 ASCII character codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . If/EndIf comparison symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MakeString expression definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Work variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
