Hitachi TrueCopy for z/OS user guide Part number: T1711-96009 Fourth edition: June 2006
Legal and notice information © Copyright 2005, 2006 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Contents About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Supported storage platforms and firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
P/DAS Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GDPS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RMF PPRC Link -path Statistical Information Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting an RCU (Delete RCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 To delete an RCU from an MCU: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Adding and Deleting Logical Paths for an RCU (Add Path and Delete Path) . . . . . . . . . . . . . . . . . . 97 To add a new logical path from the connected MCU to an existing RCU: . . . . . . . . . . . . . . . . .
ICKDSF Considerations for TrueCopy Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ICKDSF on a TrueCopy M-VOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To perform ICKDSF on a TC390 M-VOL: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ICKDSF on a TrueCopy R-VOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Syntax Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Script File Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Script Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operation Macro Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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 8 TrueCopy main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 TrueCopy main window (Pair Operations window) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Volume 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 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 HXRC path configuration with FICON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 RAID Level Configurations of TC390 . . . . . . . . . . . . . . . . . . . .
58 59 60 61 62 63 64 65 66 67 68 10 Select device parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internal macro commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ASCII character codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . If/EndIf comparison symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About this guide This guide provides information about: • ”Overview of TrueCopy Operations” on page 17 • ”Preparing for TrueCopy Operations” on page 45 • ”Starting TrueCopy” on page 65 • ”Performing TrueCopy Configuration Operations” on page 66 • ”Performing TrueCopy Pair Operations” on page 115 • ”TrueCopy Disaster Recovery Operations” on page 140 • ”Troubleshooting” on page 147 • ”Using PPRC Commands for TrueCopy” on page 153 • ”Pinned Track Recovery for TrueCopy Volumes” on page 183 • ”SIM Reporting” on
Document conventions and symbols Table 1 Document conventions Convention Element Medium blue text: Figure 1 Cross-reference links and e-mail addresses Medium blue, underlined text (http://www.hp.
Subscription service HP recommends that you register your product at the Subscriber’s Choice for Business web site: http://www.hp.com/go/e-updates. After registering, you will receive e-mail notification of product enhancements, new driver versions, firmware updates, and other product resources. Helpful web sites For additional information, see the following HP web sites: • http://www.hp.com • http://www.hp.com/go/storage • http://www.hp.com/service_locator • http://www.hp.com/support/manuals • http://www.
HP strongly recommends that customers sign-up online using the Subscriber’s choice web site at http://www.hp.com/go/e-updates. • Subscribing to this service provides you with email updates on the latest product enhancements, newest versions of drivers, and firmware documentation updates as well as instant access to numerous other product resources. • After signing-up, you can quickly locate your products by selecting Business support and then Storage under Product Category.
1 TrueCopy for the XP1024/XP128/XP12000/XP10000 TrueCopy (TC390) creates and maintains remote copies of the S/390® data stored on the XP1024/XP128/XP12000/XP10000 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.
for zSeries and S/390 data are performed using the SI390 through Command View XP or XP Remote Web Console and can also be managed using the TSO and/or ICKDSF commands. BC operations for UNIX®/PC server-based data are performed using the licensed BC software through Command View XP or XP Remote Web Console or the Raid Manager software on the UNIX/PC server host. The RAID-protected SI390 duplicates are created within the same XP1024/XP128/XP12000/XP10000 at hardware speeds.
If you use HXRC with FICON®, carefully set the path configuration. Refer to the following table. Table 2 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.
Components TC390 operations involve the XP1024/XP128/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 Command View XP management station or XP Remote Web Console. The main and remote disk arrays must have the same controller emulation. TC390 copies the original online data at the main site to the offline backup volumes at the remote site through the dedicated Fibre Channel remote copy connections.
Figure 2 TrueCopy components for Fibre Channel connection XP1024/XP128/XP12000/XP10000 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 XP1024/XP128/XP12000/XP10000 and the remote disk array is either an XP1024/XP128/XP12000/XP10000 or other XP disk arrays. 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 XP1024/XP128/XP12000/XP10000 SVP mode information. XP1024/XP128/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 4 XP1024/XP128/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 33): 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 tim
Table 4 XP1024/XP128/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.
The MCU and RCU can be defined separately for each TC390 pair. The XP1024/XP128/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 XP1024/XP128/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.
CAUTION: Do not use M-VOLs or R-VOLs from hosts that have different CU emulation types (2105 and 3990) at the same time. If you use the M-VOLs or R-VOLs from the 2105 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 5 TC390 configuration with FICON (continued) Application Site Path (System - DKC) MCU-RCU For Use FICON ESCON Not Support1 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 7 Maximum Number of Pairs According to Each Emulation Type, when pairs are created without use of customized volume 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-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
NOTE: The parameter length and detailed specification of this TC390A channel command are different than for TC390 Synchronous RIOs. Verify that your channel extenders are capable of supporting this command. For further details, contact your HP account support representative. Storing Recordsets at the RCU The RCU maintains queues to control the storing of recordsets in the sidefile and commitment of updating records in the R-VOLs.
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 33 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 mode 118 or 464 is ON (see Table 4 on page 20). The reported SIMs when SVP mode 118 or 464 is ON, however, do not support a CLPR.
same for all MCUs that contain M-VOLs in the group. The Time Out [RCU Ready] option can be different at each MCU if necessary. 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.
can increase the Time Out [Copy Pending] value, reduce I/O workload, and/or add remote copy resources. 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 126.
When you delete a pair from the MCU, the MCU changes the status of the M-VOL and R-VOL (if the path status is normal) to simplex. When you delete a pair from the RCU, the RCU changes the R-VOL status to simplex, and the MCU detects the pair deletion (if the path status is normal) and changes the M-VOL status to suspended.
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 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.
The MCU stores a cylinder bitmap in cache for each TC390A M-VOL and the RCU stores a cylinder bitmap in cache for each TC390A R-VOL. When a TC390A pair is suspended, the cylinders that contain the 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.
CAUTION: Before issuing the CESTPATH command, verify that the relevant paths are offline from the host(s) (for example, configure the Chipid offline, deactivate the LPAR, or block the port in the ESCD). If any active logical paths still exist, the add path operation will fail because the port mode (LCP/RCP) cannot be changed. • You cannot use the PPRC commands to: Change the RCU options. The current default values are: minimum paths = 1, max.
3990). GDPS support may have additional installation requirements for the XP1024/XP128/XP12000/XP10000 TC390 MCUs and RCUs, depending on XP1024/XP128/XP12000/XP10000 microcode levels and Command View XP or XP Remote Web Console software versions. Check the following items with your HP representative: • SVP modes. For operations in a GDPS environment: Mode 64 must be OFF. Mode 104 must be ON for 3990 controller emulation (not valid for 2105 emulation).
Table 13 Package Location SAID Values for the LINK Parameters (=ports) of RMF PPRC Link-path Statistical Information (FRONT CL1 Port SAID* CL3-C Package Location Port SAID* X'0003' CL3-L CL5-C X'0006' CL7-C Package Location Port SAID* X'0023' CLB-Q CL5-L X'0026' X'0007' CL7-L CL1-D X'000A' CL3-D Package Location Port SAID* X'0073' CLB-Q X'0053' CLD-Q X'0076' CLD-G X'0056' X'0027' CLF-Q X'0077' CLF-G X'0057' CL1-M X'002A' CL9-R X'007A' CL9-H X'005A' X'000B' CL3-M
Table 14 SAID Values for the LINK Parameters (=ports) of RMF PPRC Link-path Statistical Information (REAR CL2) Package Location Port SAID* CL8-B Package Location Port SAID* X'008D' CL8-K CL2-C X'0082' CL4-C Package Location Port SAID* Package Location Port SAID* X'00AD' CLG-P X'00FD' CLG-F X'00DD' CL2-L X'00A2' CLA-Q X'00F2' CLA-G X'00D2' X'0083' CL4-L X'00A3' CLC-Q X'00F3' CLC-Q X'00D3' CL6-C X'0086' CL6-L X'00A6' CLE-Q X'00F6' CLE-G X'00D6' CL8-C X'0087' CL8-L
NOTE: Other XP disk arrays with TC390 installed can be used as an RCU connected to an XP1024/XP128/XP12000/XP10000 MCU. For assistance with mixed disk array configurations, contact your HP account support representative. TC390 can coexist with CA (all copy modes) in the same XP1024/XP128/XP12000/XP10000. Full Fibre Channel support will allow concurrent fibre-mode CA and TC390 operations.
• TC390 option(s) enabled on the XP1024/XP128/XP12000/XP10000 and on the Command View XP management station or XP Remote Web Console (see ”Installing the TrueCopy Software” on page 54).
• To avoid these problems, HP strongly recommends that the user specify OFFLINE=YES if the secondary volumes are to be generated in the production host’s IOCP and system generation. NOTE: If you cannot create a pair because the TC390 R-VOL is online with hosts, all paths must be offline from all hosts. If you cannot identify the hosts that are online, please contact your HP account support representative.
Cache, NVS, and DASD Fast Write Cache and nonvolatile storage (NVS) must be operable for both the MCU and RCU of a TC390 volume pair. If not, the Add Pair operation will fail. The remote disk array cache should be configured to adequately support the TC390 remote copy workloads as well as any local workload activity. DASD fast write (DFW) is required at the MCU and RCU only when the DFW-to-R-VOL required TC390 pair option (see ”Creating TrueCopy Volume Pairs (Add Pair)” on page 121) is specified.
array, make sure to install adequate cache to handle the increased sidefile usage. When determining the required amount of cache, you must also consider the amount of Cache LUN XP data to be stored in cache. 5. HP Representative: Verify that the necessary SVP modes are enabled. See Table 4 on page 20. 6. HP Representative: Verify the MCUs are configured to report sense information to the host(s).
NOTE: For Fibre Channel interface connections, you can use the switches as for ordinary switch connections and no special settings are required for the XP1024/XP128/XP12000/XP10000. Fibre Channel interface connection provides three different configurations: • Direct connection: Two devices are connected directly together. In the following figure: * To set ports, use LUN Management and set port topology to: Fab off, FC-AL.
• N port: Fab on, Point-to-Point Figure 9 Fibre Channel interface extender connection Serial Remote Copy Connections The following figure shows the TC390 serial remote copy connection configurations. The MCU and RCU of each TC390 pair must be connected through multimode ESCON cables. For distances greater than 3 km, single-mode cables up to 20 km in length and IBM 9032/9033 ESCDs and/or 9036 ESCON repeaters are required.
N-to-1 or 1-to-n remote copy connections (n≤4) can also be configured by using the dynamic switching capability of the ESCDs to share the physical interface cables between the components. Figure 12 N-to-1 and 1-to-n remote copy connections (n≤4) 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.
Channel Extenders for Serial Remote Copy Connections TC390A can be integrated with third-party channel extender products to provide remote data backup for distances greater than 43 km. Contact your HP account support representative for the latest information on channel extender support for TC390. Installing the TrueCopy Software The user installs the software required for TC390 operations on the Command View XP management station. To install the TC390 software: 1.
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 14 Setting the Async options 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.
NOTE: You must operate the Command View XP management station XP or XP Remote Web Console in Modify mode to perform TC390 operations. Users in view mode can only view TC390 information. 3. Click the Mainframe tab, and then click the TrueCopy button ( ) to start the TC390 software. The TrueCopy main window is displayed and the Pair Operations tab is displayed at the top. 4. Configure the Fibre Channel interface ports that are connected to the RCUs as Initiators by the Port Change operation. 5.
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. Figure 17 Configuring the RCU options 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.
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. When you are finished configuring this MCU, exit the TrueCopy main window and close Command View XP or XP Remote Web Console. 8. Repeat step 2 - step 7 for each disk array that will function as a TC390 MCU.
T-VOL No No No No Compatible Mirroring for IBM FlashCopy® Version 2 (FlashCopy® Mirror Version 2) S-VOL Yes Yes Yes Yes T-VOL No No No No Compatible Replication for IBM® XRC (XRC Replication) XRC Replication main volume Yes No No No XRC Replication remote volume Yes No No No Yes No Yes No External mainframe volume that are not used as a P-VOL or S-VOL of a Cross-System Copy pair Yes Yes Yes Yes External mainframe volume that are used as a P-VOL or S-VOL of a Cross-System Co
No No No No No No No No No Yes 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 Primary data volume in Duplex status Yes Primary data volume in Suspend status Yes Primary data volume that is suspended due to a failure Yes Secondary data volume in Pending status Yes Secondary data volume in Duplex status 60 No.
Multiplatform Backup Multiplatform Backup volume 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 No No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Volume Retention Manager Volume Security Volume registered in a security group However, if the volume is disabled for use as S-VOL, the volume cannot be used as R-VOL.
• SANtinel - S/390. SANtinel operations do not affect TC390 operations. Secure volumes can be assigned to TC390 pairs, and TC390 volumes can be assigned to secure ports and/or groups for SANtinel operations. NOTE: TC390 R-VOLs cannot be accessed by any host except when the pair is split. • HXRC. The XP1024/XP128/XP12000/XP10000 is functionally compatible with the IBM Extended Remote Copy (XRC) function. See Table 16 on page 62. • SI390.
TC390 and SI390 can be used together in the same disk array and on the same volumes to provide multiple copies of data at the main and/or remote sites. The following table describes the host pair status reporting for TC390 volumes, SI390 volumes, and TC390/SI390 shared volumes. Table 18 on page 63 shows the currency of the data on a shared TC390/SI390 volume based on TC390 and SI390 pair status. • For shared TC390/SI390 volumes, the TC390 pair status is reported to the host if you query the R-VOL.
The following figure shows an example of a volume that is functioning as both a TC390 R-VOL and an SI390 S-VOL. With this configuration, you can use SI390 to provide additional remote copies of TC390 M-VOLs. This configuration is not allowed when At-Time Split is used on SI390.
Combining TrueCopy for z/OS® and Server Priority Manager The Server Priority Manager (SPM) software can give higher priority to the I/O operations of the server that requires the high processing performance than the I/O operations of the other servers. SPM can set the priority of I/O operation to ports, but if the remote copy is performed with the fibre channel interface connection, the initiator ports do not support the Server Priority Manager option.
Performing TrueCopy Configuration Operations The TC390 configuration operations include the MCU operations, RCU operations, TC390A control operations, discontinuing TC390 operations, and scripting. The TrueCopy main window (see page 66) provides access to all TC390 configuration operations. RCU 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 115 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.
• : Suspending. The TC390A pair is being suspended. When the TC390A suspend operation is complete, suspending changes to suspended. • : Suspend. The TC390 pair has been suspended. Open the Pair Status window to view the suspend type (see ”TrueCopy Volume Pair Status” on page 36) and detailed pair status information. • : Deleting. TC390A only. This pair is not synchronized. This pair is in transition from the Duplex, Pending duplex, or Suspend state to the Simplex state.
settings on the Display Filter window available, select Subsystem in the CU Number view. The Display Filter settings are available while you are operating the TC390 software until you reset the settings. 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.
Snapshot Function The TC390 snapshot function reports the user-selected TC390 pair status information. The reported status information is determined by your selections in the Display Filter window. 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.
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 operate Command View XP 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®, please 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 147.
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.
3. From the CU number tree on the RCU Operations window, select the correct CU image. For this step, the list can be blank. You must register RCUs to each CU image separately. 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.
12.Click Apply on the TrueCopy main window. 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.
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, please 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.
overload (see ”Inflow Control of Recordsets” on page 32). 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.
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 (refer to ”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: If you want 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 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 CA), 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 Command View XP 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.
• Asynchronous copy mode (TC390A) eliminates all delays associated with TC390 Synchronous operations while providing increased protections for write-dependent applications in the event of a disaster. Write I/Os for TC390A M-VOLs are processed in the same way as writes for simplex volumes, without any increase in service or disconnect time.
Table 24 Optimizing TrueCopy operations and XP1024/XP128/XP12000/XP10000 performance Condition Description Recommendation(s) RCU capacity The performance of the RCUs directly affects the performance of the MCUs. If an RCU becomes overloaded with heavy update activity, MCU and system performance can also be degraded. Distribute TC390 remote copy operations among several remote disk arrays to avoid overloading any one RCU.
unattended, attach the RCUs to a host server at the main site so that the system administrator can monitor the operational condition of the RCUs. To prepare for TC390 volume pair operations, you need to identify the volumes by LDEV ID for which you want to establish TC390 remote copy operations. You should identify volumes that are required for system operation as well as volumes that contain important data to be backed up (for example, DB log files).
• Change Pair Option: Changes the pair option (see ”Changing the Pair Options (Change Pair Option)” on page 135). • Snapshot: Creates the snapshot file (see ”Snapshot Function” on page 72). Figure 60 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 117. 6. Click Apply on the TrueCopy main window.
To modify the parameters of a volume: 1. Select a volume whose parameters to be modified on the Pair Settings Parameter 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.
3. Right-click and click Pair Status from the pop-up menu. The Pair Status window is displayed. Figure 61 Pair Status window • 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.
operation for any reason. Status: Fences only if the MCU is not able to change the R-VOL status to the same status as the M-VOL. • R-VOL Write: Enabled (Write operation to the R-VOL is enabled) or disabled (Write operation to the R-VOL is disabled) for this pair. The Write operation to the R-VOL is enabled only when the Asynchronous pair is split. However, Enabled is not usually recommended. When R-VOL Write Enabled is required, contact your HP account support representative.
• C/T Type: Timer type of the consistency group (System, Local or None). • Consistency time: Consistency time of the group to which the TC390A pair is assigned • SEQCHK: Displayed when the TC390A pair has the SEQCHK status. This status is managed by the RCU and the MCU may not have the most current information. Always use the R-VOL pair status information displayed at the RCU for disaster recovery.
Figure 63 Add Pair (Asynchronous) window 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 Hitachi HPAV for z/OS User Guide. • R-VOL: Select the R-VOL device ID for the specified M-VOL.
• If Status is selected, the M-VOL will be fenced only if the MCU is not able to change the R-VOL pair status to suspended when an update copy operation fails. If the MCU changes the R-VOL pair status to suspended, subsequent write operations to the M-VOL will be permitted and the MCU will keep track of all updates to the M-VOL while the pair is suspended. This setting is functionally equivalent to the CRIT(YES-PATHS) parameter for the CESTPAIR command.
NOTE: The CESTPAIR TSO command does not support the initial copy priority option. When CESTPAIR is used to establish TC390 pairs, the initial copy operations are performed in the order that the CESTPAIR commands are issued. • Difference Management: Select Auto, Cylinder, or Track as the basis for managing the differential data. The default is Auto. When you select Auto, either Cylinder or Track is selected depending on the basic size of the logical volume image.
• CT Group: C/T Group. This option specifies the consistency group for the pair(s) being added (TC390A only). All TC390A pairs must be assigned to a consistency group. NOTE: Only TCzA pairs belonging to the same CLPR can be allocated to one consistency group. For more information about CLPRs, see the HP StorageWorks Command View XP User Guide for XP Disk Arrays or the HP StorageWorks XP Remote Web Console User Guide for the specific disk array.
NOTE: Pair mode specifies the update copy mode (see ”Update Copy Operations” on page 27) for the new pair(s): Synchronous or Asynchronous. The selection of mode has the greatest impact on performance and must be considered carefully. Factors in mode selection include (but are not limited to) the use of TC390 (for disaster recovery or migration), the number of pairs, and the write I/O activity to the M-VOLs. 6.
pair(s). You can split a TC390 pair only after the initial copy operation is complete. For more information on split TC390 pairs, see ”Suspended Pairs” on page 38. Figure 64 Suspend Pair window (Asynchronous) 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.
• R-VOL. The M-VOL will accept all subsequent write I/O operations and the MCU will keep track of updates while the pair is suspended. Use this setting if you need to keep the M-VOL online. This setting is functionally equivalent to CSUSPEND without the optional PRIMARY parameter. • Asynchronous Parameters: • Suspend Range: Use this option to select the TC390A suspend group operation.
(R-VOL or M-VOL failure) and fence level pair option determine whether the M-VOL will accept write I/O operations after the pair is split. CAUTION: If you need to split a pair and the M-VOL is required for system operation, do not use the M-VOL Failure suspend kind option. Make sure to use the R-VOL suspend kind option so that the M-VOL continues accepting I/Os. 6.
The Resume Pair command resumes split/suspended TC390 pairs. When the Resume Pair command is selected, the Resume Pair window is displayed. Use the Resume Pair window to change the pair options and select the resume range option (asynchronous) for the selected pair(s). Figure 65 Resume Pair window 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.
NOTE: With the setting of Volume for Resume Range, if there are Duplex status pairs and pairs other than Duplex status in the same consistency group, unexpected suspend may occur during the pair operations (Suspend, Delete, and Resume) under the heavy I/O load conditions. You can estimate whether the I/O load condition is heavy or not from the rate of sidefile cache (around 30%), or from the frequency of the host I/O if you cannot see the rate of sidefile cache.
CAUTION: If a timeout error occurs after clicking the Use Time-Saving Mode option, confirm on the TrueCopy main window for which volumes the Resume Pair operation could not be performed. Deselect the Use Time-Saving Mode option for the failed volumes and retry the Resume Pair operation. Deleting TrueCopy Volume Pairs (Delete Pair) A TC390 pair should be deleted from the MCU only when it is no longer necessary to maintain a remote copy of the M-VOL.
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. Figure 66 Delete Pair window (Asynchronous) NOTE: When you set the several pairs at once and you want to keep some of the individual settings, leave the parameter box blank.
• 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). When Group is selected, the MCU/RCU will delete all TC390A pairs in the same consistency group as the specified pair regardless of pair status and consistency status.
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). When deleting TC390 Sync pairs, verify that the Delete Pair request was completed successfully by checking the pair status on the Pair Operations tab (Simplex status). 10.
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 z/OS User Guide for the XP1024/XP128/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 XP1024/XP128/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.
3. Perform the planned outage of the TC390 MCU. 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).
hardware redundancy, dynamic sparing, and an advanced RAID-5 implementation to ensure full data integrity in the event of a sudden power outage or other failure. 2. Install the Command View XP 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.
currency of the R-VOL during disaster recovery efforts. This setting is also designed for applications that can continue to operate with another device pair (for example, IMS logger dual write log files). 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.
Because this detection/retrieval process can take a while, your disaster recovery scenario should be designed so that detection and retrieval of lost updates is performed after the application has been started at the secondary system. 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).
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 187. 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 45 and ”Requirements and Restrictions” on page 47.
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.
XP1024/XP128/XP12000/XP10000 SVP error code. If you need to call HP technical support for assistance, report the TC390 and SVP error codes. Figure 68 Example of the TC390 error message Using PPRC Commands for TrueCopy Overview of PPRC Commands The XP1024/XP128/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.
The CESTPATH RESETHP option rejects the host I/O operations. Before you use the RESETHP option of the CESTPATH command, stop the I/O operations from the host. Table 33 TrueCopy operations versus PPRC TSO and ICKDSF commands TC390 Operation TSO Command Configure Port (LCP to RCP, or RCU target to initiator) ----- ICKDSF Command Command Issued to: Description ----- If SVP mode 114 is OFF, the ports must be configured using the Command View XP management station or XP Remote Web Console (or SVP).
Table 33 TrueCopy operations versus PPRC TSO and ICKDSF commands (continued) TC390 Operation TSO Command ICKDSF Command Command Issued to: Description Add Pair CESTPAIR (MODE= COPY) PPRCOPY ESTPAIR M-VOL Establishes a TC390 pair and sets the initial copy and pair options (copy mode = synchronous or asynchronous only, priority = 0, CFW data = copy to R-VOL, DFW to R-VOL = not required). TC390 supports the optional MODE, PACE, and CRIT parameters.
CAUTION: The QUIESCE option of the CSUSPEND command has been disabled by APAR OW15247 or APAR OW15248. For detailed information on the QUIESCE option of the CSUSPEND command, refer to either of these APARs. Check with your HP account team before using the CSUSPEND command with the QUIESCE option to suspend TC390 volume pairs on an XP1024/XP128/XP12000/XP10000 (or other XP disk array).
For 2105 controller emulation (‘lss’ parameter for LCU no., CGROUP and RESETHP options): CESTPATH DEVN(X’dev#’) PRIM(X’ssid’ serial# X’lss’) SEC(X’ssid’ serial#’ X’lss’) LINK(X’aabbccdd’) [CGROUP(YES|NO) RESETHP(YES|NO)] NOTE: For fibre, do not use the RESETHP option. For serial, the RESETHP option rejects host I/O operations. Before you use this option, stop the I/O operations from the host. For 2105 emulation, use the CESTPATH CGROUP option to control freeze. Do not use the CGROUP FREEZE option.
Table 36 CESTPATH LINK Parameter (Fibre Channel Interface) LINK Parameter Details aabb SAID of MCU (x'00 and the port number ccdd SAID of RCU (x'00 and the port number) WWNN (World Wide Node Name) is the unique number for the controller and is indicated as shown in Figure 69. Figure 69 Example of WWNN NOTE: The parameter of PRIM and SEC of CDELPATH command are indicated as same as the parameter of CESTPATH command.
• For 2105 emulation, the first two digits must be 00. The CGROUP option of the CESTPATH command is used to control freeze for 2105 emulation.
Table 38 SAID Values for the LINK Parameters (=ports) (REAR CL2) Package Location Port SAID* Package Location Port SAID* Package Location Port SAID* Package Location Port SAID* 2Q CL2-A X'0010' 2T CL2-J X'00A8' 2W CLA-N X'009C' 2N CLA-E X'0094' (Basic) CL4-A X'0031' (Add 2) CL4-J X'00A8' (Add4) CLC-N X'00BC' (Add6) CLC-E X'00B4' CL6-A X'0054' CL6-J X'00A8' CLE-N X'00DC' CLE-E X'00D4' CL8-A X'0075' CL8-J X'00A8' CLG-N X'00FC' CLG-E X'00F4' CL2-B X'0011'
For 3990-3, -6 and -6E controller emulations: CESTPAIR DEVN(X’dev#’) PRIM(X’ssid’ cmd_param X’cca’) SEC(X’ssid’ serial# X’cca’) [MODE(COPY|NOCOPY|RESYNC)] [PACE(pace)] [CRIT(YES|NO)] [MSGREQ(YES|NO)] For 2105 controller emulation (new ‘lss’ parameter for LCU number): 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 Param
• If the consistency group requirements (see ”Consistency Groups” on page 49) are not satisfied, this command may/may not be rejected. • The delay option prevents command retry delay for this pair when sidefile is above the HWM (see ”Graduated Delay Sidefile Management” on page 33). If not specified correctly, command is rejected (F/M=04). • When cmd_param AGxxx is specified, this command ends before the actual pair establishment/re-establishment successfully starts.
• Regardless of the number of volume pairs to be suspended, this command ends before the actual pair suspension is successfully completed. Confirmation by CQUERY or IEA494I console message is recommended after this command. CDELPAIR The following table describes how to use the CDELPAIR command to delete TC390A pairs and groups at the MCU.
CRECOVER DEVN(X’dev#’) PRIM(X’ssid’ serial# X’cca’ X’lss’) SEC(X’ssid’ cmd_param X’cca’ X’lss’) [ID(old_volser[new_volser])] Table 42 Using CRECOVER to delete TrueCopy Async pairs/groups at the RCU Parameters Contents Description cmd_param AC000 AC000Specifies that all volume pairs (R-VOLs) in the consistency group whose consistency status is Suspended-Group should be deleted.
CQUERY Output Example: M-VOL/FORMAT/VOLUME ************* PPRC REMOTE COPY CQUERY - VOLUME ********************** * (PRIMARY) (SECONDARY) * * SSID CCA LSS SSID CCA LSS * *DEVICE LEVEL STATE PATH STATUS SERIAL# SERIAL# * *------ --------- ---------- ----------- ----------------* * 2A10 PRIMARY.. PENDING... ACTIVE.. 4300 10 00 4300 11 00 * * CRIT(NO)....... CGRPLB(NO).
The MCU serial number field is used to display the TCzA information shown in Figure 70 . Figure 70 Controller Emulations 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.
LINK Parameter Fibre Channel Interface Fibre Channel Interface Mode 484 OFF Mode 484 ON cc RCU port number (0x00-0xff) SAID of RCU dd CU number (0x00-0xff) (x'00' and the port number) Table 44 The following example shows the output of the CQUERY command with the VOLUME parameter issued to a TC390A R-VOL.
The MCU serial number field is used to display the TCzA information shown in Figure 71 Figure 71 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 45 on page 169 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 TagmaStore USP 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 controller emulation, do not use the FREEZE option. Use the CGROUP option of the CESTPATH command (see ”CESTPATH” on page 156).
pppp = Fibre Channel port ID of the primary CU (MCU) from which the TC390 paths should be established and the FREEZE option for the LCU pair. Note that the first two digits (FREEZE option) must be the same in a series of link parameters.
• The device (LDEV ID of TC390 M-VOL or simplex volume) (DEVN parameter). • The MCU (S/N and lowest SSID in CU image) (PRIM parameter). • The RCU (S/N and lowest SSID in CU image) (SEC parameter). The CGROUP TSO command has the following two options: • 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.
1. Read/write I/Os are issued from the host. 2. A failure occurs on a TC390 M-VOL and the MCU suspends the pair. 3. Suspend and extended long busy state are reported to the host. 4. Host reports IEA494I with extended long busy state. 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.
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 47 XP1024/XP128/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.
Table 47 XP1024/XP128/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 48 GDPS-TC390-HXRC matrix (continued) zSeries and S/390 Feature IBM 3990-6E XP1024/XP128/XP12000/ XP10000 XP48/XP512 TSO command Support Supported Supported. Supported. Some additional options only available through the Command View XP management station or XP Remote Web Console (or SVP). Some additional options only available through the Remote Console PC (or SVP). ICKDSF command support Supported P/DAS support Supported. Supported.
Table 48 GDPS-TC390-HXRC matrix (continued) zSeries and S/390 Feature IBM 3990-6E XP1024/XP128/XP12000/ XP10000 XP48/XP512 TC-Unique Features (specified through the Command View XP management station, 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 48 GDPS-TC390-HXRC matrix (continued) zSeries and S/390 Feature IBM 3990-6E XP1024/XP128/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.
additional alert for the user. The XP1024/XP128/XP12000/XP10000 also reports SIMs to the Command View XP management station 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 50 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 50 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 50 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 52 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 53). The empty statement is a non-execution statement. Table 53 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] Refer to ”Operation Macro Commands” on page 191 and ”Internal Macro Commands” on page 199 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 56 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 59 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.
statement. The execution statement cannot be defined on the same line as the If statement. The If statement must contain one conditional decision statement within parentheses. The string values must be compared as ASCII character codes (see Table 60).
format for the MakeString command is: MakeString $D= output buffer ,$Fmt= expression 1,$Item= expression 2 Table 62 MakeString expression definitions Expression 1 Expression 2 Expression 1 is one of three format control strings ($Fmt): Expression 2 is any expression not containing a list reserved variable (must be constant or work variable). %d Converts a 16-bit numeric expression to a decimal number (0 - 65535). %x Converts a 16-bit numeric expression to a hexadecimal number (0 - 0xffff).
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 63 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 64 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 Command View XP management station or XP Remote Web Console obtains the status of the specified TC390 pair(s) from the XP1024/XP128/XP12000/XP10000.
Table 65 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.
specified in the text of the script. The following table describes the syntax requirements that will be evaluated. Table 66 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. Use of the parentheses is correct and the number of parentheses is exact. A statement does not terminate with an equal sign.
Table 66 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 68 on page 207 lists the TC390 scripting error codes. The message ID is the four-digit number displayed on the error message.
Table 68 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 68 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.
Table 68 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 68 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 68 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 XP1024/XP128/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 XP1024/XP128/XP12000/XP10000 performs current load balancing control. If the operating system does not support the DONOTBLOCK option, set Mode 61 = OFF. DONOTBLOCK option: The XP1024/XP128/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 78 Combination 1: MODE 85,86 = ON,OFF; Threshold 1/2/3 = 30/40/50% Figure 79 Combination 2 (Default): MODE 85,86 = OFF,OFF; Threshold 1/2/3 = 40/50/60% TrueCopy for z/OS user guide 215
Figure 80 Combination 3: MODE 85,86 = OFF,ON – Threshold 1/2/3 = 50/60/70% Figure 81 Combination 4: MODE 85,86 = ON,ON – Threshold 1/2/3 = 60/70/80% 216 TrueCopy for the XP1024/XP128/XP12000/XP10000
Index A adding consistency group 105, 106 path to RCU 98 RCU path 98 SSID to RCU 100 audience, documentation 11 authorized resellers, HP 13, 14 C cache requirements for TC390 49 CDELPAIR for TC390A 163 CESTPAIR for TC390A 160 CGROUP (FREEZE/RUN) 169 FREEZE option 170, 172 GDPS environment 172 requirements 170 RUN option 172 SSID requirements 170 SVP modes 171 changing consistency group options 107 RCU options 97 volume pair options 136 configuring async options 108 MCU ports 84 MCUs and RCUs for FC 55 MCUs
H P help HP technical support 12 HP authorized resellers 13, 14 storage web site 13, 14 Subscriber’s choice web site 13, 14 technical support 12 HXRC 20, 171 pair settings operation 116 pair status during CGROUP operations 172 troubleshooting 150 parameters modifying 109 modifying volumes 118 path adding 98 deleting 99 status descriptions 87 troubleshooting 149 performing asynchronous operations 102 ICKDSF on a M-VOL 137 ICKDSF on a R-VOL 137 pair settings operation 116 planned outage of MCU and RCU 140
analyzing currency of 144 analyzing TC390A consistency of 145 performing ICKDSF on 137 pinned track 183 S scripting 78, 187 ChangeHrcPair command 196 components 190 CreateHrcPair command 191 DeleteHrcPair command 193 functional macro commands 188 GetHrcStatus command 197 internal macro commands 189, 199 parameter restrictions 190 result value 202 ResumeHrcPair command 195 SelectHrcDevice command 197 StartHrcPair command 197 SuspendHrcPair command 194 symbols 191 syntax description 190 setting asynchronous
creating 125 deleting 134 resuming 131 suspending 128 volumes omitting 118 W web sites HP documentation 11 HP storage 13, 14 HP Subscriber’s choice 13, 14 220