Hitachi TrueCopy for z/OS user guide Part number: T1711-96004 Second edition: October 2005
Legal and notice information © Copyright 2005 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 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Document conventions and symbols . . . . . . . .
Preparing for TrueCopy Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements and Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Track Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
To modify the parameters:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 To omit the RCUs, Paths, or SSIDs from the operation: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Asynchronous Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 To perform the asynchronous operations: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Point-in-Time (PiT) Data Duplication Using TrueCopy Asynchronous . . . . . . . . . . . . . . . . . . . . . . . To produce a PiT duplicate of an existing TC390A consistency group: . . . . . . . . . . . . . . . . . . Powering Off/On TrueCopy Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planned Outage of the MCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Change Pair Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting a Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Getting Pair Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selecting Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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 Tables 1 2 3 4 5 6 7 8 8 RCU Operations window with the Port option button selected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Standard speed, two ports per row . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 High-speed (2 port), two ports per row . . . . . . . . . . . . . . . . . . . . . . . . . .
10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 TrueCopy volume pair status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Suspend types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Consistency status for suspended TrueCopy Async R-VOLs . . . . . . . . .
About this guide This guide provides information about: • ”Overview of TrueCopy Operations” on page 17 • ”Preparing for TrueCopy Operations” on page 43 • ”Starting TrueCopy” on page 59 • ”Performing TrueCopy Configuration Operations” on page 60 • ”Performing TrueCopy Pair Operations” on page 109 • ”TrueCopy Disaster Recovery Operations” on page 134 • ”Troubleshooting” on page 141 • ”Using PPRC Commands for TrueCopy” on page 147 • ”Pinned Track Recovery for TrueCopy Volumes” on page 172 • ”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.
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 XP128/XP1024/XP10000/XP12000 TrueCopy (TC390) creates and maintains remote copies of the S/390® data stored on the XP128/XP1024/XP10000/XP12000 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.
The RAID-protected SI390 duplicates are created within the same XP128/XP1024/XP10000/XP12000 at hardware speeds. SI390 can be used in conjunction with TC390 to maintain multiple copies of critical data at your primary and/or secondary (remote) sites. For more information on combining TC390 and SI390 operations, see ”Combining TrueCopy and ShadowImage” on page 57.
1. If you use FICON for the path of application site, you should also use FICON for the path of System Data Mover (SDM) because of the difference in performance between FICON and ESCON. Continuous Access XP As an enterprise advantage, the XP128/XP1024/XP10000/XP12000 can be concurrently connected to zSeries and S/390 and a variety of UNIX-based and PC-server hosts. Contact your HP account support representative for the latest information on platform and version support.
Figure 1 on page 18 and Figure 2 on page 19 show the TC390 components and their functions.
Figure 2 TrueCopy components for Fibre Channel connection XP128/XP1024/XP10000/XP12000 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 XP128/XP1024/XP10000/XP12000 and the remote disk array is either an XP128/XP1024/XP10000/XP12000 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).
(SCP) messages. For more information on cache usage and sidefile thresholds, see ”Inflow Control of Recordsets” on page 32. Table 3 XP128/XP1024/XP10000/XP12000 modes for TrueCopy for z/OS Mode Description 20 Enables TC390 – R-VOL read-only function (RCU only). 21 Required ON for MCUs and RCUs that connect to channel extenders. 36 TC390 Synchronous – Selects function of CRIT=Y(ALL) or CRIT=Y(PATHS). Mode 36 ON: CRIT=Y(ALL) => equivalent to Fence Level = Data.
Table 3 XP128/XP1024/XP10000/XP12000 modes for TrueCopy for z/OS (continued) Mode Description 97 HXRC – Variable Sleep Wait timer duration (see modes 45, 85, 86; see ”HXRC Device Blocking and Load Balancing” on page 201). Mode 97 OFF: Sleep Wait timer duration = 100 ms. Mode 97 ON: Sleep Wait timer duration = 10 ms. 98 HXRC – Selects SCP or session cancel (see modes 45, 85, 86; see ”HXRC Device Blocking and Load Balancing” on page 201). Mode 98 OFF: SCP. Mode 98 ON: Forced session cancel.
Table 3 XP128/XP1024/XP10000/XP12000 modes for TrueCopy for z/OS (continued) Mode Description 308 Allows you to select whether the Remote Copy Path status, SIM218x, will be reported to the host or not. Mode 308 ON: SIM218x will be reported to the host. Mode 308 OFF: SIM218x will not be reported to the host. 464 TC390A – Allows you to select whether to generate SIM when the sidefile of TC390A, XRC Replication, and CC reaches high-water mark (HWM = sidefile threshold - 20%. See mode 93).
Changing from 3990 to 2105: If you need to change the emulation from 3990 to 2105 for an XP128/XP1024/XP10000/XP12000 that has existing HXRC pairs, you must: 1. Stop all jobs and delete all HXRC pairs. 2. Change the CU emulation type of all CHA packages in the XP128/XP1024/XP10000/XP12000 to 2105. Do not intermix 3990 and 2105 emulations in the same disk array. 3. Restart jobs and re-establish HXRC pairs. NOTE: The PPRC commands are different for 3990 and 2105 emulation types.
MCU/RCU = one physical CU, including all CU images). TC390 supports the dynamic switching capability of the ESCDs that is used to share the physical interface cables between the components. The ESCDs can accommodate channel-to-MCU and channel-to-RCU connections in addition to the remote copy connections • TC390A supports 1-to-1 remote copy connections within the same consistency group. The M-VOLs and R-VOLs of the pairs in a consistency group must be located within one physical MCU and one physical RCU.
NOTE: For Fibre Channel interface, do not use the CESTPATH and CDELPATH commands at the same time as the SCSI path definition function of LUN Management. Two or more initiator ports must be configured before you can add the RCUs and create the TC390 volume pairs. The initiator ports cannot communicate with the host processor channels. To enable the host processor channels to send write I/O operations to the MCU, the host channel paths must be connected to the other Fibre Channel interface ports in the MCU.
NOTE: For information on TC390A configuration services, contact your HP account support representative. Asynchronous Consistency Groups A TC390A consistency group is a user-defined set of volume pairs across which update sequence consistency is maintained and ensured at the remote site. Each TC390A volume pair must be assigned to a consistency group.
Initial Copy Operations The initial copy operation synchronizes the M-VOL and R-VOL independently of host I/O processes. The initial copy operation is the same for TC390 Synchronous and TC390A pairs. A TC390 initial copy operation takes place when you add a new pair or resume a suspended pair.
copy is executed asynchronously, but the same scheduling conflict can occur between the asynchronous update copy (write recordset) and initial copy. Read and Write I/O Operations for TrueCopy Volumes When an MCU receives a read command for a TC390 M-VOL, the MCU completes the read from either cache or the M-VOL. If the read fails, the redundancy provided by RAID technology recovers the failure. The MCU does not read the TC390 R-VOL for recovery.
stored in the bitmap is Track or Cylinder. When adding a pair (Add Pair), you can select Track or Cylinder and you can also confirm the unit. Table 5 Operation of the unit of data stored in bitmap Program The Unit of Data Stored in Bitmap Confirmation Default (Auto)1 Track Cylinder Command View XP or XP Remote Web Console Available Available Available Available PPRC TSO Not available Not available Not available Not available 1.
• Sending recordsets to the RCU • Storing recordsets at the RCU • Selecting and settling recordsets at the RCU • Types of recordsets • Inflow control for sidefiles • Dummy pair mode Creating and Storing Recordsets at the MCU When an MCU performs an update (host-requested write I/O) on a TC390A M-VOL, the MCU creates a TC390A recordset that contains: the updated record, time-stamp information, sequence number, record location (device, cylinder, track, record number), and record length.
2. When the top of each queue contains a valid entry (recordset), the RCU selects the entry that has the earliest time-stamp value, and then settles this recordset. 3. The RCU repeats this process to select and settle TC390A recordsets. The following figure illustrates recordset selection and settling at the RCU. In this example, the top of the queue contains a valid entry: S1/T1. The RCU selects recordset S1/T1 to be settled because T1 is the earliest time-stamp.
• The “high-water mark” (HWM), which is the sidefile threshold minus 20%, indicates when graduated delay begins for TC390A volume pairs (see the following section). If SVP mode 118 is ON, a warning SIM is also generated. • The puncture threshold, which is the sidefile threshold plus 10%, indicates when the TC390A pairs will be suspended due to sidefile overflow (see ”CESTPATH” on page 150).
1. For more information on sidefile thresholds for HXRC operations, refer to ”HXRC Device Blocking and Load Balancing” on page 201. Graduated Delay Sidefile Management The following figure shows the graduated delay process for TC390A sidefile management. When the TC390A sidefile value reaches the high-water mark (threshold minus 20%), the XP128/XP1024/XP10000/XP12000 begins command retry delay for host updates to TC390A M-VOLs and reports a warning SIM to the host.
In the following figure, updates to the primary volume (A) are transferred to the device addresses of its secondary volume (A’) as well as the secondary volumes of dummy volume pairs (B’-D’) in parallel. Figure 6 Dummy pair mode The basic specifications for dummy pair mode are: • Up to three dummy pairs can be related to one real volume pair. • Volumes must be assigned in both the MCU and RCU for dummy pair. • Custom-size volumes of minimum size (one cylinder) can be used for dummy pair.
TrueCopy Asynchronous Consistency Group Operations TC390A consistency groups enable update sequence consistency to be maintained across a group of volumes. The R-VOLs of the pairs in a consistency group must be located within one RCU (n-to-1 requirement). The TC390A consistency group operations include the following: • Group options • Group consistency time • Group operations Only TCzA pairs that belong to the same CLPR can be allocated to one consistency group.
When a TC390A volume pair is suspended, the C/T of the suspended R-VOL is frozen. If the RCU can ensure the update sequence consistency between the suspended R-VOL and the other R-VOLs in the consistency group, the R-VOL C/T is frozen at the latest consistency time of the group. Otherwise, the R-VOL C/T is frozen at the time-stamp value of the most recent update that was successfully copied to the R-VOL.
TrueCopy Volume Pair Status TC390A displays the pair status for each volume in the selected logical CU image (CUI) of the connected XP128/XP1024/XP10000/XP12000. The MCU maintains the status of the M-VOL and is responsible for keeping the M-VOL and its R-VOL synchronized. The RCU maintains the status of the R-VOL. The MCU can change the pair status of the M-VOL and R-VOL. The RCU can change the pair status of the R-VOL but not the M-VOL.
Table 9 TrueCopy volume pair status (continued) Pair Status Description Suspended (see Table 10 on page 39 for suspend types) This volume pair is not synchronized: For TC390 Synchronous only, if the MCU cannot keep the pair synchronized for any reason, the MCU changes the status of the M-VOL and R-VOL (if possible) to suspended.
If a TC390 Synchronous update copy operation fails, the MCU maintains exact synchronization by reporting a unit check and decommitting the M-VOL update so that the host system and application program regard that write operation to the M-VOL as failed. For information on failed TC390A recordset operations, see ”Suspended TrueCopy Asynchronous Pairs” on page 40. When a TC390 pair is suspended, the MCU stops performing update copy operations to the R-VOL.
Table 10 Suspend types (continued) Suspend Type Applies to Description MCU P/S-OFF R-VOL (TC390A only) The RCU received a request from the MCU to suspend the R-VOL due to MCU power-off. The RCU stops expecting recordsets from that MCU. by sidefile overflow M-VOL, R-VOL (TC390A only) The amount of sidefile exceeds the specified “current pending update data rate” and the RCU data is not transferred within the specified “offloading timer”.
Table 12 TrueCopy Asynchronous suspension conditions (continued) Suspension Condition Detected by TC390A Pairs to be Suspended The RCU could not receive the recordset successfully due to a hardware failure. RCU Only the affected R-VOL. The RCU detected a logical error while selecting the recordset to be settled. RCU The RCU could not settle the recordset due to a hardware failure, a track condition, or a logical error.
NOTE: For Fibre Channel interface, do not use the CESTPATH and CDELPATH commands at the same time as the SCSI path definition function of LUN Management. The Fibre Channel interface ports need to be configured as initiator ports or RCU target ports before the CESTPATH and CDELPATH commands are issued. 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).
GDPS Support TC390 provides remote copy support for IBM’s Geographically Dispersed Parallel Sysplex (GDPS) facility. GDPS is an IBM service offering for mirroring data and balancing workload on disk arrays spread across two or more sites up to 40 km (~20 miles) apart. With this support, users who are running IBM Parallel Sysplex systems can take advantage of the XP128/XP1024/XP10000/XP12000 suite of remote copy options for data availability.
• For distances greater than 43 km (26.7 miles), approved third-party channel extender products and telecommunications lines are required. Long-distance TC390 solutions are provided based on user requirements and workload characteristics. NOTE: Use of channel extenders may require additional XP128/XP1024/XP10000/XP12000 configuration (for example, mode 21).
• Record zero (R0) must be standard format, with key length of zero and data length of eight. The MCU will abort the initial copy operation if R0 is not standard format. • The CCHH (logical cylinder address and logical head address) of R0 must be identical to the physical cylinder address and physical head address of the track. • The CCHH of each user record in a track must be unique. One-to-One Volume Copy Operations TC390 requires a one-to-one relationship between the logical volumes of the volume pairs.
NOTE: The host I/O time-stamping function is not supported by 3380 LVIs. If you plan to use TC390A pairs, the TC390A M-VOLs and R-VOLs must be 3390 LVIs. In the case that M-VOL or R-VOL is 3390-L LVI under the connection of the disk array, and the number of cylinders is more than 10,017, the capacity of the M-VOL and R-VOL must be the same.
• All TC390A pairs must be assigned to one and only one consistency group. • The maximum number of volume pairs in one consistency group is 4,096 (entire RCU). • The maximum number of consistency groups established for one MCU-RCU pair is 128. The RCU supports a maximum of 128 groups. This limit of 128 groups includes both TC390A groups and TC Asynchronous groups (for example, 64 TC390A + 64 CA Asynchronous).
flexibility and availability. The logical paths between the MCU and RCU must be separate from the logical paths between the host and RCU. For serial interface connections, all remote copy activities between two XP128/XP1024/XP10000/XP12000s, such as TC390, TC390A, CA Sync, and CA Async, can share the same remote copy connections. For Fibre Channel interface connections, only TC390 activities (Sync and Async) can share the same fibre remote copy connections (future support will eliminate this restriction).
• Switch connection: Up to three optical fibre cables are connected together through the switches to connect the devices. Up to two switches can be used. In the following figure: 1. Some switch vendors require F port (for example, McData ED5000). 2.
support. Long-distance solutions are provided, based on user requirements and workload characteristics, using approved channel extenders and communication lines. Figure 11 Serial remote copy connection configurations The ESCDs can accommodate multiple MCU-RCU remote copy connections.
NOTE: 1-to-n configurations (one main disk array and multiple remote disk arrays) are valid for TC390A, as long as a consistency group does not span remote disk arrays. In addition, the ESCDs can accommodate channel-to-MCU and channel-to-RCU connections in addition to the remote copy connections.
NOTE: At this time serial interface and Fibre Channel interface configurations cannot coexist for the same MCU. Future support is planned. Serial interface connection is not supported for this version. Serial Interface Configuration To configure the MCUs and RCUs for serial-interface TC390 operations: 1. Identify the volumes that will become the TC390 M-VOLs and R-VOLs.
Then register the consistency group to the MCU as shown in the following figure. For additional instructions, see ”Adding Consistency Groups (Add CT Group)” on page 99. Figure 16 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.
5. Register the RCU(s) to the current MCU CU image using the Add RCU window. Figure 17 Add the RCUs Set the options for the registering RCU using the RCU Option window as shown in the following figure. For additional instructions, see ”Registering an RCU (Add RCU)” on page 81.
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 102. Figure 19 Setting the Async options Then register the consistency group(s) to the MCU as shown in the following figure. For additional instructions, see ”Adding Consistency Groups (Add CT Group)” on page 99. Figure 20 Adding the consistency groups 7.
• 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 XP128/XP1024/XP10000/XP12000 is functionally compatible with the IBM Extended Remote Copy (XRC) function. See Table 13 on page 57. • SI390.
command (for example, CQUERY DEVN parameter). SI390 through Command View XP or XP Remote Web Console displays the LDEV ID and SI390 pair status of all T-VOLs associated with an S-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.
NOTE: The storage partition administrator cannot perform TrueCopy for z/OS® operations. Figure 25 TrueCopy main window CAUTION: Do not perform TC390 operations using the TrueCopy main window while the TC390 scripting function is being executed. To perform TC390 operations on the TrueCopy main window, wait until the script is complete or verify that the script in execution is aborted.
Usage Monitor operations. Use the usage monitor operations (see page 104) to collect the I/O statistics for the LDEVs on the disk array. Script operations. Use the scripting function to specify and execute a series of TC390 operations without having to issue commands separately (see ”Script Operations” on page 107). History operations. Use the history operations (see ”History Operations” on page 107) to export the remote copy history file. Other operations.
Table 16 TC390 functions (continued) Tab Menu Command RCU Operations RCU Status Description Displays the RCU status and TC390 port numbers that are already set. RCU Operation > Add RCU Registers the RCU at the remote disk array. RCU controls the R-VOL of the TC390 volume pair. RCU Operation > Delete RCU Deletes the RCU that is already registered. RCU Operation > Change RCU Option Modifies the options for RCUs that are already registered. Edit SSID(s) & Path(s) > Add Path Adds the paths to RCUs.
Information displayed on the TrueCopy main window is updated when the TrueCopy main window is opened, when the tab is switched from one to another, and when the Refresh button ( ) is clicked. Figure 26 TrueCopy main window (Pair Operations window) The TrueCopy main window consists of the CU Number tree, the Volume list (see ”Volume List” on page 63), the Display Filter button (see ”Display Filter” on page 64), and the Previous/Next button.
NOTE: To change the number of items that can be displayed without scrolling, change the font size. Figure 27 Volume list • Volume icon: Indicates the status of volumes. • : Simplex • : M-VOL • : R-VOL • CU: CU number of the main LDEV. • Device: Device number. • Status: For more information on TC390 pair status, see ”TrueCopy Volume Pair Status” on page 37. • : Simplex. The volume is not currently assigned to a TC390 pair.
NOTE: If “#” is added to the end of LDEV number (i.e. 00:3C#), the LDEV that the LDEV number indicates is an external volume. If the pair is created with TrueCopy for z/OS of the microcode program version 50-03-6x-xx or earlier, “#” is not added. For details on an external volume, please refer to Hitachi HPAV for z/OS User Guide. • Device number of the other volume of the volume pair. • Type: Pair mode, Synchronous or Asynchronous.
NOTE: You cannot use other windows without closing the Display Filter window. a Figure 28 Display Filter window Use the CU# list to specify the number of the CU to be displayed. Use the CT Group list to specify the number of the consistency group to be displayed. This specification is available only for the Asynchronous pair. Use the Type list to specify the pair type, synchronous or asynchronous. Use the M-VOL/R-VOL list to specify the Volume type, M-VOL or R-VOL.
NOTE: If # is added to the end of an LDEV number, such as 3F#, the LDEV is an external volume. For more information about external volumes, see Hitachi HPAV for z/OS User Guide. To create a TC390 snapshot file: 1. Click Display Filter to display the Display Filter window. 2. Select the options you want in the Display Filter window and close the window. 3. From the Pair Operations window, right-click to display the pop-up menu and click Snapshot. A confirmation dialog box is displayed. 4.
The RCU Operations window is updated when the tab is switched from one to another, when the Refresh button ( ) is clicked, and when the settings for the RCU are applied. For the RCU settings operation, see ”RCU Operations” on page 76. Figure 30 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 67).
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 31 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 32 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, RCP, or LCP).
Figure 34 High-speed (2 port), two ports per row Figure 35 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 37 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 40 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 84) • Deleting RCUs (see page 91) • Adding and deleting logical paths to an RCU (see page 91) • Adding and deleting SSIDs for an RCU (see page 94) • Modifying parameters and omitting selected settings (see page 95) From the RCU Operations window (see page 66), 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. The disk array serial interface ports can be configured as LCPs or RCPs. • LCP: The serial ports which will be connected to the host must be configured as LCPs (default). LCP mode is used for host processor channel interface. The serial ports in the RCU that will be used to communicate with the MCUs must also be configured as LCPs.
3. From the MCU/RCU list, select an RCU and right-click to display the pop-up menu. Figure 42 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 43 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 141.
NOTE: If four RCUs (the maximum number of RCUs you can register) have already been registered, the Add RCU command cannot be selected. Figure 44 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 45). 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 47 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 49 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 50 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. CAUTION: You must click OK on the RCU Option window to register the SCP Delay Time setting, even if you did not make any changes to the RCU options. Ensure to select the appropriate SCP delay time for your TC390 system configuration.
required for the initial copy operation is large, it means that the workload of the update copy is relatively high. Therefore, the copy pace of the initial copy will be slowed. When the time is relatively small, the copy pace will speed up to the specified value. In this way, we can curb the influence of the exclusive line use in the initial copy operation on the host performance. NOTE: This option is available only in the case of TCz pairs (In the case of TCzA pairs, this option value is invalid).
1. When a PPRC command (TSO/ICKDSF) is used and the CU emulation type is 2105, the initial copy pace specified is invalid. Therefore, the fixed value will be set. Table 19 Example setting Item No. Round Trip Time [ms] Line Speed b/w MCU/RCU [MB/ms] Number of Lines b/w MCU/RCU Initial Copy Pace Max. Number of Initial Copy VOLs Round Trip Time Specified [ms] 1 0 0.1 4 15 64 160 2 30 0.1 4 15 64 220 3 100 0.1 4 15 64 360 The Cancel button cancels the registering RCU operation.
4. From the MCU/RCU list on the RCU Operations window, select the RCU that you want to delete. 5. Right-click to display the pop-up menu, click RCU Operation, and then click Delete RCU. 6. Click Apply on the TrueCopy main window.
To add a new logical path from the connected MCU to an existing RCU: 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 the RCU to which you want to add a path. 3. Right-click to display the pop-up menu, click Edit SSID(s) & Path(s), and then click Add Path (see Figure 52). The Add Path window is displayed. Figure 52 Opening the Add Path window 4. From the Add Path window, enter the new path(s). 5.
NOTE: The options can be modified and/or canceled after you have set them. See ”Modifying Parameters and Omitting Selected Settings” on page 95. 5. Click Apply on the TrueCopy main window. 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.
NOTE: The options can be modified and/or canceled after you have set them. See ”Modifying Parameters and Omitting Selected Settings” on page 95. Figure 54 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 100), and Delete CT Group (see ”Deleting Consistency Groups (Delete CT Group)” on page 101). Figure 55 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 56 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 57 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 102). 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 58 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 99. 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 60 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 20 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.
without any increase in service or disconnect time. The asynchronous R-VOL updates are performed completely independent of all host I/O processes at the M-VOLs and there are no restrictions on subsequent read/write operations to TC390A M-VOLs. The only performance concerns for TC390A are ensuring that adequate cache resources are available for sidefiles that are used to store the recordsets at both the MCUs and RCUs, and ensuring that sufficient ESCON paths are defined for copy operations.
Table 21 Optimizing TrueCopy operations and XP128/XP1024/XP10000/XP12000 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 129). • Snapshot: Creates the snapshot file (see ”Snapshot Function” on page 66). Figure 61 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 111. 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 62 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.
• The Previous button changes the displayed pair status information to that of the previous Volume on the Volume list (the Volume of the row above). The Next button changes the displayed pair status information to that of the next Volume on the Volume list (the Volume of the row below). The Refresh button refreshes the pair status information. The Close button closes the Pair Status window. NOTE: The Display Filter settings can affect how Previous or Next is recognized.
Figure 64 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.
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: The CESTPAIR command can be used to start TC390A pairs and assign them to groups, but the groups must already be configured (using the Add C/T Group window, see ”Adding Consistency Groups (Add CT Group)” on page 99).
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 39. Figure 65 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 66 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.
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. When a TC390 volume pair is deleted from the MCU, the MCU stops all TC390 copy operations for that pair and changes the pair status of the M-VOL and R-VOL to simplex. After a pair is deleted, the MCU continues to accept all subsequent write I/O operations to the M-VOL and will not keep track of the M-VOL updates.
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 67 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.
CAUTION: Do not use this option when deleting pairs at the RCU during disaster recovery. This option is available only when one pair is selected. • C/T (RCU only). When C/T is selected, the RCU will delete all TC390A pairs that have the same consistency time. • Volume (MCU or RCU). When Volume is selected, the MCU/RCU will delete only the specified TC390A pair(s). This option can be used to remove individual volumes from consistency groups.
10.To restart a pair that was deleted from the RCU, first delete the pair from the MCU, and then use the Add Pair command with the appropriate TC390 initial copy option (Entire or No Copy) to restart the pair. NOTE: If a timeout error occurs after clicking the Use Time-Saving Mode option, confirm on the TrueCopy main window for which volumes the Delete Pair operation could not be performed. Deselect the Use Time-Saving Mode option for the failed volumes and retry the Delete Pair operation.
• Data: M-VOL is fenced when the MCU cannot successfully execute an update copy operation for any reason. • Status: M-VOL is fenced only if the MCU cannot change the R-VOL status to suspended when an update copy operation fails. • CFW Data: Specifies whether the CFW data is copied to the R-VOL. For TCPD-MF, only Copy to R-VOL is available. • Asynchronous Parameters (Async only): • Error Level: Error level for the new pair(s): Group, or Volume.
3. After the M-VOL status changes to suspended/R-VOL by operator, run ICKDSF to repair the M-VOL. 4. When volume repairs are complete, resume the TC390 pair. When resuming a suspended TC390A pair, make sure to use the appropriate Resume level pair option (see ”Resuming TrueCopy Volume Pairs (Resume Pair)” on page 123). You can also use the CESTPAIR (MODE=RESYNC) command to resume the pair.
NOTE: If you are migrating data between disk arrays using P/DAS, both disk arrays must be the same type (XP128/XP1024/XP10000/XP12000 or other XP disk arrays). If you need to migrate data from other vendors’ storage disk arrays onto the XP128/XP1024/XP10000/XP12000, contact your HP account support representative. To use TC390 Synchronous to migrate data from one volume to another: 1. Vary the R-VOL(s) offline from all attached hosts. The R-VOLs are the target volumes onto which you are migrating the data.
NOTE: The copy pending timeout setting for the group determines the maximum amount of time that the suspend/drain operation can take. 3. When the status for all TC390A pairs in the group has changed to suspended, the duplicate set of volumes is complete. If needed, you can restart the application at the main site. Powering Off/On TrueCopy Components The user is responsible for controlling power-off activities for disk arrays involved in TC390 operations.
suspend the pairs first, the MCU(s) will detect the communication failure, suspend all affected pairs, and generate SIMs and console messages reporting the failures. To perform a planned outage of a TC390 RCU or remote copy connection component: 1. Identify all TC390 M-VOLs that will be affected by the equipment outage. You need to know the MCU, CU image, and LDEV ID for each of these M-VOLs. • For RCU power-off, identify all M-VOLs that are paired with R-VOLs in the RCU to be powered off.
• RCU options: Incident of RCU, PPRC Support, Service SIM of Remote Copy, and FREEZE Option (see ”Registering an RCU (Add RCU)” on page 81). • TC390A offloading timer asynchronous option (see ”Asynchronous Copy Option” on page 102) and TC390A copy pending timeout group option (see ”Adding Consistency Groups (Add CT Group)” on page 99). The copy pending timeout group option can be used to limit the time duration during which updates may be lost.
(out-of-sync-cylinders) copy operation (MODE=RESYNC). This setting will also reduce the amount of time required to analyze the R-VOL currency during disaster recovery. Never (CRIT=NO). When this fence level is selected, the M-VOL is never fenced when the pair is suspended. This M-VOL fence level setting ensures that the M-VOL remains available to applications for updates, even if all TC390 copy operations have failed.
• Files for file recovery (for example, DB2 log files that have been verified as current). To ensure the currency of these files, use the R-VOL Data fence level setting for the TC390 pairs that contain these important files. • The sense information with system time stamp that will be transferred through ERC. Remote copy and disaster recovery procedures are inherently complex. Consult your HP account team on sense-level settings and recovery procedures.
5. If necessary, use ICKDSF REFORMAT to change the labels (VOLSERs) of the R-VOLs. 6. Verify that all required file recovery procedures have been completed before varying the R-VOLs online. If an IPL of the remote host system is not required, bring the R-VOLs online. If an IPL is required: a. Clear the remote copy SIMs from the RCUs before OS IPL. Connect to each RCU and click Clear SIM in the Other Operations window (see ”Other Operations” on page 107).
transferred through ERC or compare the contents of the R-VOL with other files that are confirmed to be current, such as DB2 log files. These R-VOLs should be recovered using the files that are confirmed to be current.
6. If you plan to use the same channel extenders, change the operating mode to the opposite direction. The boxes/nodes connected to the MCUs must be set to channel-mode and the boxes/nodes connected to the RCUs must be set to device-mode. 7. At the remote site, configure the RCU ports to enable TC390 operations in the reverse direction (change LCPs to RCPs for serial, change RCU target ports to initiator ports for fibre).
NOTE: For Fibre Channel interface, do not use the CESTPATH and CDELPATH commands at the same time as the SCSI path definition function of LUN Management. The Fibre Channel interface ports need to be configured as initiator ports or RCU target ports before the CESTPATH and CDELPATH commands are issued. 6. If you plan to use the same channel extenders, change the operating mode back to the original direction.
provide troubleshooting information for suspended TC390 pairs. For troubleshooting information on TC390 scripting, see ”TrueCopy Scripting” on page 176. Table 26 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 43 and ”Requirements and Restrictions” on page 45.
Table 27 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 27 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 28 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 29 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.
XP128/XP1024/XP10000/XP12000 SVP error code. If you need to call HP technical support for assistance, report the TC390 and SVP error codes. Figure 69 Example of the TC390 error message Using PPRC Commands for TrueCopy Overview of PPRC Commands The XP128/XP1024/XP10000/XP12000 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 30 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 30 TrueCopy operations versus PPRC TSO and ICKDSF commands (continued) TC390 Operation TSO Command ICKDSF Command Command Issued to: Description Suspend Pair CSUSPEND PPRCOPY SUSPEND M-VOL or R-VOL Suspends a TC390 pair (or TC390A group). TC390 supports the optional PRIMARY parameter. See Caution below on the QUIESCE parameter. For details on CSUSPEND for TC390A, see ”CSUSPEND” on page 154.
TC390A volumes on the XP128/XP1024/XP10000/XP12000. Table 31 on page 150 describes the typographic conventions used for the PPRC TSO commands described in this section. NOTE: PPRC TSO command parameter support depends on the emulation (for example, 2105 or 3990). PPRC command extensions are supported when running with 2105 emulation. Use the PPRC TSO Command option on the Async Option window to select the XP256-compatible format for PPRC TSO commands (groups 0-F instead of 00-3F).
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 paths still exist, the add path operation will fail because the port mode cannot be changed. NOTE: For Fibre Channel interface, do not use the CESTPATH and CDELPATH commands at the same time as the SCSI path definition function of LUN Management.
• 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.
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 34 Using CESTPAIR to establish and resume TrueCopy Async pairs Parameter Contents Description cmd_param AGnnd nn = consistency group number (00-7F) or master volume number (00-FF: for dummy pair mode). Without MODE(RESYNC): Specifies the consistency group number nn to which the volume pair will belong.
• When cmd_param AGxxx is specified, this command ends before the actual pair establishment/re-establishment successfully starts. Confirmation by CQUERY or IEA494I console message is recommended after this command. • The dummy pair for each primary volume can be established only by the PPRC command. For the use of dummy pair, note the following: • Use the dummy pair only for a limited number of the critical volumes. • The dummy pair function is only for ESCON-connected TC390A pairs.
• The D and P in cmd_param stand for the Drain and Purge options, respectively. For a detailed description of these TC390A suspend options, see ”Suspending TrueCopy Pairs (Suspend Pair)” on page 120. • When P (Purge) is specified, it is not possible to determine exactly which recordset will be settled before the addressed volume pair is suspended. • Regardless of the number of volume pairs to be suspended, this command ends before the actual pair suspension is successfully completed.
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 37 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.
The FIRST/LAST CYL OUT OF SYNC and PERCENT OF COPY COMPLETE boxes indicate the first/last cylinder number and percentage of cylinders (including R-VOL cylinders) to be copied for pair resynchronization. For a more detailed description, see ”Resuming TrueCopy Volume Pairs (Resume Pair)” on page 123. The PATHS, SSID, DEST, STATUS, and DESCRIPTION boxes show NO PATH for this volume pair instead of the actual path status. CQUERY with PATHS keyword provides the path status for this volume pair.
Output Example: CQUERY *************** PPRC REMOTE COPY CQUERY - VOLUME ********************* * (PRIMARY) (SECONDARY)* * SSID CCA SSID CCA * *DEVICE LEVEL STATE PATH STATUS SERIAL# SERIAL# * *------ --------- ---------- ----------- ----------------* * 0A32 PRIMARY.. PENDING... ACTIVE.. 7700 32 7740 12 * * CRIT(NO) A00SNG030982 000000030954 * * PATHS SAID/DEST STATUS: DESCRIPTION * * ----- --------- ------ ------------------* * 1 001D 0000 01 PATH ESTABLISHED... * * ---- ---- 00 NO PATH............
CAUTION: The XP128/XP1024/XP10000/XP12000 executes the CGROUP command on TC390 Synchronous pairs. TC390A does not support the CGROUP TSO command. If CGROUP is issued to a TC390A volume, the XP128/XP1024/XP10000/XP12000 will reject the command. CGROUP (FREEZE/RUN) operations on TC390 Synchronous pairs do not affect TC390A pairs in any way. Requirements The CGROUP command can be issued only to a TC390 Synchronous M-VOL or a simplex volume in the MCU.
For Fibre Channel cable: Value Port ID Freeze Option X’4000’-X’40FF’ Interface 1A-GR Default X’4100’-X’41FF Interface 1A-GR Enabled X’4200’-X’42FF’ Interface 1A-GR Disabled ll = For ESCON cable: ESCON destination link address. The destination port number of ESCD must be specified if the TC390 link is connected through an ESCD dynamic connection. Otherwise, “00” must be specified.
• Presents state change pending (SCP) with extended long busy status to host I/O requests, which causes the host to queue I/Os for the M-VOLs. SCP is indicated until the CGROUP/RUN command is issued or until the SCP delay time expires. NOTE: After all logical MCU-RCU paths are established, make sure to specify the SCP delay time (0-600 seconds) for the MCU using the RCU Option window. To register the SCP delay time, select OK to close the RCU Option window, even if you did not make any changes.
8. Switch to remote (secondary) site. Figure 70 Overview of GDPS operations Using PPRC TSO Commands with CGROUP Support CESTPATH. You can use the CESTPATH command to recover a blocked MCU-RCU path. Make sure to use the same parameters as when the path was established. CESTPAIR. After you re-establish the MCU-RCU path that was blocked, you can use the CESTPAIR/RESYNC command to resume the TC390 pairs suspended by the CGROUP/RUN command. CDELPAIR.
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 81). If not, the host processor generates the system console message that includes the SIM instead of the IEA494I or IEA491E message.
Table 40 XP128/XP1024/XP10000/XP12000 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 40 XP128/XP1024/XP10000/XP12000 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 41 GDPS-TC390-HXRC matrix (continued) zSeries and S/390 Feature IBM 3990-6E XP128/XP1024/XP10000/ XP12000 XP48/XP512 ICKDSF 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).
Table 41 GDPS-TC390-HXRC matrix (continued) zSeries and S/390 Feature IBM 3990-6E XP128/XP1024/XP10000/ XP12000 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 41 GDPS-TC390-HXRC matrix (continued) zSeries and S/390 Feature IBM 3990-6E XP128/XP1024/XP10000/ XP12000 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 XP128/XP1024/XP10000/XP12000 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 43 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 43 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 43 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 45 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 46). The empty statement is a non-execution statement. Table 46 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 180 and ”Internal Macro Commands” on page 188 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 49 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.
• Sync level list (string): “S0” or “Synchronous0” (0x00) = sync, “S2” or “Synchronous2” (0x02) = async; default = S0. S0 and S2 cannot be specified at the same time. • 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.
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 52 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 53).
format for the MakeString command is: MakeString $D= output buffer ,$Fmt= expression 1,$Item= expression 2 Table 55 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 56 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 57 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 XP128/XP1024/XP10000/XP12000.
Table 58 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 59 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 59 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 61 on page 196 lists the TC390 scripting error codes. The message ID is the four-digit number displayed on the error message.
Table 61 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 61 TrueCopy scripting error codes (continued) Message ID Internal Code Error Message Error Description 2349 2208 Required value is not found. Line = nnnn The end of line nnnn is “=”. 2350 2209, 220a Illegal ‘(‘and’)’ pair. Line = nnnn The parentheses are not matched in script line nnnn. 2351 220b, 2303 Syntax error. Line = nnnn An illegal word is included in script line nnnn. 2351 27xx Syntax error. Line = nnnn The parameter setting for script line nnnn is invalid.
Table 61 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 61 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 61 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 XP128/XP1024/XP10000/XP12000 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 XP128/XP1024/XP10000/XP12000 performs current load balancing control. If the operating system does not support the DONOTBLOCK option, set Mode 61 = OFF. DONOTBLOCK option: The XP128/XP1024/XP10000/XP12000 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 76 Combination 1: MODE 85,86 = ON,OFF; Threshold 1/2/3 = 30/40/50% Figure 77 Combination 2 (Default): MODE 85,86 = OFF,OFF; Threshold 1/2/3 = 40/50/60% TrueCopy for z/OS user guide 203
Figure 78 Combination 3: MODE 85,86 = OFF,ON – Threshold 1/2/3 = 50/60/70% Figure 79 Combination 4: MODE 85,86 = ON,ON – Threshold 1/2/3 = 60/70/80% 204 TrueCopy for the XP128/XP1024/XP10000/XP12000
Index A D adding consistency group 99, 100 path to RCU 92 RCU path 92 SSID to RCU 94 audience, documentation 11 authorized resellers, HP 13 data migration using TC390 131 database recovery 137 deleting consistency group 102, 103 path to RCU 93 RCU 91 RCU path 93 RCUs 91 SSID from RCU 94, 95 volume pairs 128 device blocking HXRC 201 TC390 153 DFW requirements for TC390 47 disaster recovery clearing SIMs 138 consistency of async R-VOLs 139 currency of sync R-VOLs 138 file and database recovery procedures 1
G GDPS 158 group Delete Pair option 127 Resume Pair option 124 TC390A pair option 64, 119 TC390A suspend option 122 H help HP technical support 12 HP authorized resellers 13 storage web site 13 Subscriber’s choice web site 13 technical support 12 HXRC 20, 160 I ICKDSF media maintenance on TC390 volumes 130 PPRCOPY commands 148 IEA491E system console message 164, 165 IEA494I system console message 137, 165 installing TC390 hardware 47 TC390 software 52 TC390 system requirements 43 L logical path.
R RCU adding path 92 adding SSID 94 configuring FC 53 configuring serial interface 52 deleting 91 deleting path 93 deleting SSID 95 operations 76 outage 134 path status 81 performing operations 77 registering 81 status 78 registering RCU 81 RCU to connected MCU 82 Remote Copy monitoring starting 104 stopping 104 resuming consistency group 125 volume pairs 125 R-VOL analyzing currency of 138 analyzing TC390A consistency of 139 performing ICKDSF on 131 pinned track 172 S SAID parameters 152 scripting 72, 176
TC390 pair creating (Add Pair) 115 deleting (Delete Pair) 128 resuming 125 resuming (Resume Pair) 123 suspending (Suspend Pair) 120 TC390 sync performance impact 107 technical support, HP 12 timeout copy pending 99 RCU ready 99 troubleshooting RCU path status 143 suspended pairs 144 TC390 141 TC390A suspension conditions 145 U using TC390 Synchronous to migrate data 132 V viewing consistency group status 97 RCU status 78 Virtual LVI/LUN 56 volume pairs changing options 130 creating 119 deleting 128 resumi
